Scoring script should (optionally) sync scoring with target JSON file

[Mark T. Voelker]

Some time back, we adopted a simple plaintext file[1] as a means to record scoring work (note: this is considered a working document, not an official publication). This has proven a quicker, easier to grock way to visualize scoring in progress. We also added a simple script [2] to tabulate the total score for each capability in the scoring sheet according to the weights listed in the target JSON doc, and to generate a CSV file for those who prefer to view scoring work in a spreasheet program.

Recently, we added a cutoff_score field [3][4] to the JSON schema that shows the total score a Capability generally needs to achieve to be included. With this addition, we now have all the necessary information available for the script to actually add Capabilities that score sufficiently high to the JSON file, thus potentially saving human being some work and reducing the chance of human error. The same logic could also be used to validate that achievements for all Capabilities in the JSON file (new or existing) are in sync with current scoring.

We should update the script with an option to sync data into the target JSON file.

[1] http://git.openstack.org/cgit/openstack/defcore/tree/working_materials/scoring.txt
[2] http://git.openstack.org/cgit/openstack/defcore/tree/working_materials/tabulate_scores.py
[3] https://review.openstack.org/224868
[4] https://review.openstack.org/306229