)]}'
{"reference/sigs-repos.yaml":[{"author":{"_account_id":8482,"name":"Colleen Murphy","email":"colleen@gazlene.net","username":"krinkle"},"change_message_id":"2fa699ecf1310ac293fa1f87b7490452b3939d01","unresolved":false,"context_lines":[{"line_number":1,"context_line":"---"},{"line_number":2,"context_line":"# List of repositories owned by SIGs"},{"line_number":3,"context_line":"meta:"},{"line_number":4,"context_line":"  - repo: openstack/governance-sigs"}],"source_content_type":"text/x-yaml","patch_set":1,"id":"ff82abbf_6cdc07e4","line":3,"range":{"start_line":3,"start_character":0,"end_line":3,"end_character":4},"updated":"2017-11-24 10:27:56.000000000","message":"Looks like other reference lists have more human-friendly keys, like \"Enterprise Working Group\", maybe this could be \"Meta SIG\"?\n\nDoes this get rendered somewhere?","commit_id":"393c23a18e34463e57e28ea1d80dcd635dfa2bf7"},{"author":{"_account_id":308,"name":"Thierry Carrez","email":"thierry@openstack.org","username":"ttx"},"change_message_id":"2c4fbfd504c1452fdeb3a9237c7520ae885063a5","unresolved":false,"context_lines":[{"line_number":1,"context_line":"---"},{"line_number":2,"context_line":"# List of repositories owned by SIGs"},{"line_number":3,"context_line":"meta:"},{"line_number":4,"context_line":"  - repo: openstack/governance-sigs"}],"source_content_type":"text/x-yaml","patch_set":1,"id":"ff82abbf_27bdb801","line":3,"range":{"start_line":3,"start_character":0,"end_line":3,"end_character":4},"in_reply_to":"ff82abbf_6cdc07e4","updated":"2017-11-24 10:49:10.000000000","message":"The SIGs all have a shortname used as a subject prefix for the ML, so I thought I would use that as a key (less likely to change over time)... It won\u0027t get rendered. Happy to change it for longname if you think that\u0027s clearer.\n\nThe (upcoming) SIG governance website will specify longname, shortname, scope, leads... for each SIG. I didn\u0027t want to duplicate that here.","commit_id":"393c23a18e34463e57e28ea1d80dcd635dfa2bf7"}]}
