)]}'
{"/COMMIT_MSG":[{"author":{"_account_id":8556,"name":"Ghanshyam Maan","display_name":"Ghanshyam Maan","email":"gmaan.os14@gmail.com","username":"ghanshyam"},"change_message_id":"3144fdb813d067ef35ea2f3798b74f49b35f31ff","unresolved":false,"context_lines":[{"line_number":16,"context_line":"- Be generally less prescriptive and more on the \u0027best practices\u0027 side"},{"line_number":17,"context_line":"- Mention SIG statuses as part of the SIG lifecycle guidelines, rather"},{"line_number":18,"context_line":"  that on its own separate document"},{"line_number":19,"context_line":"- Remove the \"completed\" status which is redundant with the presence in"},{"line_number":20,"context_line":"  the completed-sigs.yaml file"},{"line_number":21,"context_line":""},{"line_number":22,"context_line":"Change-Id: Id1a754512f08bed55926dd7b65916c1f42fb446f"}],"source_content_type":"text/x-gerrit-commit-message","patch_set":1,"id":"9f560f44_d86072d2","line":20,"range":{"start_line":19,"start_character":0,"end_line":20,"end_character":30},"updated":"2020-08-21 13:21:48.000000000","message":"I think we should include completed-sigs.yaml also here so that \u0027completed\u0027 SIG can be seen on site otherwise people would not until they check the source code and the file completed-sigs.yaml\n\nPreviously it was here but having these SIGs on top page like other SIG are will be easy read-https://governance.openstack.org/sigs/reference/sig-status.html#complete","commit_id":"6bd9524ca92b85cb8565ec5766f8ea2eb9bc1517"}],"doc/source/index.rst":[{"author":{"_account_id":8556,"name":"Ghanshyam Maan","display_name":"Ghanshyam Maan","email":"gmaan.os14@gmail.com","username":"ghanshyam"},"change_message_id":"3144fdb813d067ef35ea2f3798b74f49b35f31ff","unresolved":false,"context_lines":[{"line_number":18,"context_line":"same way contributing to an OpenStack project team does."},{"line_number":19,"context_line":""},{"line_number":20,"context_line":".. sigtable::"},{"line_number":21,"context_line":"      :datafile: ../../sigs.yaml"},{"line_number":22,"context_line":""},{"line_number":23,"context_line":".. toctree::"},{"line_number":24,"context_line":"   :hidden:"}],"source_content_type":"text/x-rst","patch_set":1,"id":"9f560f44_f87bb688","line":21,"range":{"start_line":21,"start_character":32,"end_line":21,"end_character":32},"updated":"2020-08-21 13:21:48.000000000","message":"here we can include completed-sigs also with a separate heading.","commit_id":"6bd9524ca92b85cb8565ec5766f8ea2eb9bc1517"}],"doc/source/reference/sig-guideline.rst":[{"author":{"_account_id":17068,"name":"Jean-Philippe Evrard","email":"openstack@a.spamming.party","username":"evrardjp"},"change_message_id":"c8a2d7af6b51846ee760fcd08fc0aa5db652cc9c","unresolved":false,"context_lines":[{"line_number":44,"context_line":""},{"line_number":45,"context_line":"Once the SIG is approved, it is important to keep its filing in"},{"line_number":46,"context_line":"`SIG Governance`_  up to date. In particular, keeping the status, chairs,"},{"line_number":47,"context_line":"and scope up to date "},{"line_number":48,"context_line":""},{"line_number":49,"context_line":"SIG status may be:"},{"line_number":50,"context_line":""}],"source_content_type":"text/x-rst","patch_set":1,"id":"9f560f44_98b27a93","line":47,"range":{"start_line":47,"start_character":20,"end_line":47,"end_character":21},"updated":"2020-08-21 14:04:26.000000000","message":"nit: whitespace.","commit_id":"6bd9524ca92b85cb8565ec5766f8ea2eb9bc1517"},{"author":{"_account_id":16465,"name":"Kristi Nikolla","email":"knikolla@bu.edu","username":"knikolla"},"change_message_id":"699d6b19a3c4955683b008aa7bdc381b839e984f","unresolved":false,"context_lines":[{"line_number":57,"context_line":"active"},{"line_number":58,"context_line":"~~~~~~"},{"line_number":59,"context_line":""},{"line_number":60,"context_line":"The SIG reaches out for discussion, have plans for current"},{"line_number":61,"context_line":"cycle, host meetings or send messages about status out to the mailing-list"},{"line_number":62,"context_line":"regularly."},{"line_number":63,"context_line":""},{"line_number":64,"context_line":"advisory"},{"line_number":65,"context_line":"~~~~~~~~"}],"source_content_type":"text/x-rst","patch_set":4,"id":"9f560f44_b6166f48","line":62,"range":{"start_line":60,"start_character":0,"end_line":62,"end_character":10},"updated":"2020-08-21 14:45:50.000000000","message":"The subject of the verb is unclear. Should be split up into two sentences.","commit_id":"709a567071fc61ef85601a0719d483d3e0274d4c"},{"author":{"_account_id":308,"name":"Thierry Carrez","email":"thierry@openstack.org","username":"ttx"},"change_message_id":"b32a1bedeae06e1940b52de6a4d2ee60af9a2637","unresolved":false,"context_lines":[{"line_number":57,"context_line":"active"},{"line_number":58,"context_line":"~~~~~~"},{"line_number":59,"context_line":""},{"line_number":60,"context_line":"The SIG reaches out for discussion, have plans for current"},{"line_number":61,"context_line":"cycle, host meetings or send messages about status out to the mailing-list"},{"line_number":62,"context_line":"regularly."},{"line_number":63,"context_line":""},{"line_number":64,"context_line":"advisory"},{"line_number":65,"context_line":"~~~~~~~~"}],"source_content_type":"text/x-rst","patch_set":4,"id":"9f560f44_04dd4e6f","line":62,"range":{"start_line":60,"start_character":0,"end_line":62,"end_character":10},"in_reply_to":"9f560f44_b6166f48","updated":"2020-08-24 10:11:54.000000000","message":"I agree, I just copied the existing wording from sig-status.html though, so this is actually not part of this change.","commit_id":"709a567071fc61ef85601a0719d483d3e0274d4c"},{"author":{"_account_id":16465,"name":"Kristi Nikolla","email":"knikolla@bu.edu","username":"knikolla"},"change_message_id":"699d6b19a3c4955683b008aa7bdc381b839e984f","unresolved":false,"context_lines":[{"line_number":155,"context_line":"We encourage every SIG to participate to the Summit and PTG events if possible."},{"line_number":156,"context_line":"SIGs can have:"},{"line_number":157,"context_line":""},{"line_number":158,"context_line":"* PTG rooms for SIG in-person group discussions"},{"line_number":159,"context_line":""},{"line_number":160,"context_line":"* Forum sessions to get wider community feedback on issues within the SIG"},{"line_number":161,"context_line":"  scope."}],"source_content_type":"text/x-rst","patch_set":4,"id":"9f560f44_164e3b6e","line":158,"range":{"start_line":158,"start_character":20,"end_line":158,"end_character":29},"updated":"2020-08-21 14:45:50.000000000","message":"ah, the old days.","commit_id":"709a567071fc61ef85601a0719d483d3e0274d4c"}],"doc/source/reference/sig-status.rst":[{"author":{"_account_id":8556,"name":"Ghanshyam Maan","display_name":"Ghanshyam Maan","email":"gmaan.os14@gmail.com","username":"ghanshyam"},"change_message_id":"3144fdb813d067ef35ea2f3798b74f49b35f31ff","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"9f560f44_38240eaf","updated":"2020-08-21 13:21:48.000000000","message":"we need to add a redirect link for this page - https://governance.openstack.org/sigs/reference/sig-status.html\n\nalso need to update its current usage \n\n- https://opendev.org/openstack/governance-sigs/src/branch/master/doc/source/_exts/sigtable.py#L96","commit_id":"6bd9524ca92b85cb8565ec5766f8ea2eb9bc1517"}]}