)]}'
{"reference/role-of-the-tc.rst":[{"author":{"_account_id":4257,"name":"Zane Bitter","email":"zbitter@redhat.com","username":"zaneb"},"change_message_id":"006d0321a73f525f1a56f53f92460612eeb01434","unresolved":false,"context_lines":[{"line_number":11,"context_line":"electing their own leadership) which means that the TC is not directly"},{"line_number":12,"context_line":"in charge of organizing day-to-day work. OpenStack being an open"},{"line_number":13,"context_line":"collaboration with volunteers, the TC also does not command development"},{"line_number":14,"context_line":"resources that can be applied to priorities or to meet certain deadlines."},{"line_number":15,"context_line":""},{"line_number":16,"context_line":"So what is the role of the TC under the current OpenStack technical"},{"line_number":17,"context_line":"governance model? This living document aims to answer that question."}],"source_content_type":"text/x-rst","patch_set":1,"id":"3f79a3b5_05c5f907","line":14,"updated":"2018-12-07 03:02:25.000000000","message":"+1 I think it\u0027s great that we\u0027re stating this up-front for the benefit of even people who don\u0027t read past the first paragraph :)","commit_id":"868c70c0eb0b1e9204e9454cc0a62fc2b467b598"},{"author":{"_account_id":17068,"name":"Jean-Philippe Evrard","email":"openstack@a.spamming.party","username":"evrardjp"},"change_message_id":"74d983154d0a3726206f8908a4938df9f9ac9555","unresolved":false,"context_lines":[{"line_number":11,"context_line":"electing their own leadership) which means that the TC is not directly"},{"line_number":12,"context_line":"in charge of organizing day-to-day work. OpenStack being an open"},{"line_number":13,"context_line":"collaboration with volunteers, the TC also does not command development"},{"line_number":14,"context_line":"resources that can be applied to priorities or to meet certain deadlines."},{"line_number":15,"context_line":""},{"line_number":16,"context_line":"So what is the role of the TC under the current OpenStack technical"},{"line_number":17,"context_line":"governance model? This living document aims to answer that question."}],"source_content_type":"text/x-rst","patch_set":1,"id":"3f79a3b5_a5ecfe90","line":14,"in_reply_to":"3f79a3b5_05c5f907","updated":"2018-12-11 08:45:15.000000000","message":"Agreed","commit_id":"868c70c0eb0b1e9204e9454cc0a62fc2b467b598"},{"author":{"_account_id":4257,"name":"Zane Bitter","email":"zbitter@redhat.com","username":"zaneb"},"change_message_id":"006d0321a73f525f1a56f53f92460612eeb01434","unresolved":false,"context_lines":[{"line_number":20,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":21,"context_line":""},{"line_number":22,"context_line":"The main role of the TC is to define the model under which the OpenStack"},{"line_number":23,"context_line":"open source project is governed. Governance is (according to wikipedia)"},{"line_number":24,"context_line":"\"the processes of interaction and decision-making among the actors involved"},{"line_number":25,"context_line":"in a collective problem that lead to the creation, reinforcement, or"},{"line_number":26,"context_line":"reproduction of social norms and institutions\". It is therefore the duty of"},{"line_number":27,"context_line":"the TC to create and maintain documents describing the community structure,"},{"line_number":28,"context_line":"systems, operating principles and values. This is done in the"},{"line_number":29,"context_line":":doc:`Technical Committee charter \u003ccharter\u003e`,"}],"source_content_type":"text/x-rst","patch_set":1,"id":"3f79a3b5_480c6895","line":26,"range":{"start_line":23,"start_character":33,"end_line":26,"end_character":47},"updated":"2018-12-07 03:02:25.000000000","message":"This is just a style thing but I always cringe when elementary-school debate teams and first-time wedding toast-givers start with a dictionary definition, so if we can get the point across any other way...\n\nIt\u0027s not like the word governance was handed down to us from on high (the bylaws say \u0027management\u0027); we chose it.","commit_id":"868c70c0eb0b1e9204e9454cc0a62fc2b467b598"},{"author":{"_account_id":308,"name":"Thierry Carrez","email":"thierry@openstack.org","username":"ttx"},"change_message_id":"162159a357bbf9882b2b42038ef9707e2c49149a","unresolved":false,"context_lines":[{"line_number":20,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":21,"context_line":""},{"line_number":22,"context_line":"The main role of the TC is to define the model under which the OpenStack"},{"line_number":23,"context_line":"open source project is governed. Governance is (according to wikipedia)"},{"line_number":24,"context_line":"\"the processes of interaction and decision-making among the actors involved"},{"line_number":25,"context_line":"in a collective problem that lead to the creation, reinforcement, or"},{"line_number":26,"context_line":"reproduction of social norms and institutions\". It is therefore the duty of"},{"line_number":27,"context_line":"the TC to create and maintain documents describing the community structure,"},{"line_number":28,"context_line":"systems, operating principles and values. This is done in the"},{"line_number":29,"context_line":":doc:`Technical Committee charter \u003ccharter\u003e`,"}],"source_content_type":"text/x-rst","patch_set":1,"id":"3f79a3b5_aecbbd7c","line":26,"range":{"start_line":23,"start_character":33,"end_line":26,"end_character":47},"in_reply_to":"3f79a3b5_480c6895","updated":"2018-12-07 13:07:24.000000000","message":"Agreed! I included it to take into account Chris\u0027s important point on the brainstorm etherpad, but am open to better ways to word this.","commit_id":"868c70c0eb0b1e9204e9454cc0a62fc2b467b598"},{"author":{"_account_id":4257,"name":"Zane Bitter","email":"zbitter@redhat.com","username":"zaneb"},"change_message_id":"006d0321a73f525f1a56f53f92460612eeb01434","unresolved":false,"context_lines":[{"line_number":24,"context_line":"\"the processes of interaction and decision-making among the actors involved"},{"line_number":25,"context_line":"in a collective problem that lead to the creation, reinforcement, or"},{"line_number":26,"context_line":"reproduction of social norms and institutions\". It is therefore the duty of"},{"line_number":27,"context_line":"the TC to create and maintain documents describing the community structure,"},{"line_number":28,"context_line":"systems, operating principles and values. This is done in the"},{"line_number":29,"context_line":":doc:`Technical Committee charter \u003ccharter\u003e`,"},{"line_number":30,"context_line":"the `TC governance website`_ documents and other TC-maintained publications"}],"source_content_type":"text/x-rst","patch_set":1,"id":"3f79a3b5_4571b112","line":27,"range":{"start_line":27,"start_character":7,"end_line":27,"end_character":39},"updated":"2018-12-07 03:02:25.000000000","message":"I\u0027d like to think that this is just a means and not the end.","commit_id":"868c70c0eb0b1e9204e9454cc0a62fc2b467b598"},{"author":{"_account_id":308,"name":"Thierry Carrez","email":"thierry@openstack.org","username":"ttx"},"change_message_id":"162159a357bbf9882b2b42038ef9707e2c49149a","unresolved":false,"context_lines":[{"line_number":24,"context_line":"\"the processes of interaction and decision-making among the actors involved"},{"line_number":25,"context_line":"in a collective problem that lead to the creation, reinforcement, or"},{"line_number":26,"context_line":"reproduction of social norms and institutions\". It is therefore the duty of"},{"line_number":27,"context_line":"the TC to create and maintain documents describing the community structure,"},{"line_number":28,"context_line":"systems, operating principles and values. This is done in the"},{"line_number":29,"context_line":":doc:`Technical Committee charter \u003ccharter\u003e`,"},{"line_number":30,"context_line":"the `TC governance website`_ documents and other TC-maintained publications"}],"source_content_type":"text/x-rst","patch_set":1,"id":"3f79a3b5_aeb41df5","line":27,"range":{"start_line":27,"start_character":7,"end_line":27,"end_character":39},"in_reply_to":"3f79a3b5_4571b112","updated":"2018-12-07 13:07:24.000000000","message":"+1 ... Maybe \"...duty of the TC to describe the community structure, systems, operating principles and values by creating and maintaining corresponding documentation\" ?","commit_id":"868c70c0eb0b1e9204e9454cc0a62fc2b467b598"},{"author":{"_account_id":17068,"name":"Jean-Philippe Evrard","email":"openstack@a.spamming.party","username":"evrardjp"},"change_message_id":"74d983154d0a3726206f8908a4938df9f9ac9555","unresolved":false,"context_lines":[{"line_number":24,"context_line":"\"the processes of interaction and decision-making among the actors involved"},{"line_number":25,"context_line":"in a collective problem that lead to the creation, reinforcement, or"},{"line_number":26,"context_line":"reproduction of social norms and institutions\". It is therefore the duty of"},{"line_number":27,"context_line":"the TC to create and maintain documents describing the community structure,"},{"line_number":28,"context_line":"systems, operating principles and values. This is done in the"},{"line_number":29,"context_line":":doc:`Technical Committee charter \u003ccharter\u003e`,"},{"line_number":30,"context_line":"the `TC governance website`_ documents and other TC-maintained publications"}],"source_content_type":"text/x-rst","patch_set":1,"id":"3f79a3b5_858ea2d4","line":27,"range":{"start_line":27,"start_character":7,"end_line":27,"end_character":39},"in_reply_to":"3f79a3b5_aeb41df5","updated":"2018-12-11 08:45:15.000000000","message":"That phrase will be even better with an oxford comma ! ;)","commit_id":"868c70c0eb0b1e9204e9454cc0a62fc2b467b598"},{"author":{"_account_id":2472,"name":"Doug Hellmann","email":"dhellmann@redhat.com","username":"doug-hellmann"},"change_message_id":"cac5e60eb631efc19217d9b7b943e3bfced0534c","unresolved":false,"context_lines":[{"line_number":56,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":57,"context_line":""},{"line_number":58,"context_line":"The TC\u0027s authority over technical matters explicitly includes the authority"},{"line_number":59,"context_line":"to determine the scope of the \"OpenStack\" released software."},{"line_number":60,"context_line":""},{"line_number":61,"context_line":"Under the current governance model, that means the TC constantly refines"},{"line_number":62,"context_line":"the rules used to decide which teams are part of the project and which"}],"source_content_type":"text/x-rst","patch_set":1,"id":"3f79a3b5_9fd2d45e","line":59,"updated":"2018-12-05 18:09:23.000000000","message":"It might be useful to mention that this authority and responsibility is called out in the bylaws.","commit_id":"868c70c0eb0b1e9204e9454cc0a62fc2b467b598"},{"author":{"_account_id":11655,"name":"Julia Kreger","email":"juliaashleykreger@gmail.com","username":"jkreger","status":"Flying to the moon with a Jetpack!"},"change_message_id":"d9507b334a93b9149d2f0e8e8ed715750247a131","unresolved":false,"context_lines":[{"line_number":56,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":57,"context_line":""},{"line_number":58,"context_line":"The TC\u0027s authority over technical matters explicitly includes the authority"},{"line_number":59,"context_line":"to determine the scope of the \"OpenStack\" released software."},{"line_number":60,"context_line":""},{"line_number":61,"context_line":"Under the current governance model, that means the TC constantly refines"},{"line_number":62,"context_line":"the rules used to decide which teams are part of the project and which"}],"source_content_type":"text/x-rst","patch_set":1,"id":"3f79a3b5_c234e149","line":59,"in_reply_to":"3f79a3b5_9fd2d45e","updated":"2018-12-06 14:46:03.000000000","message":"++, we may want to also delineate branding in that statement (and possibly refer to where in the bylaws this can be found)","commit_id":"868c70c0eb0b1e9204e9454cc0a62fc2b467b598"},{"author":{"_account_id":308,"name":"Thierry Carrez","email":"thierry@openstack.org","username":"ttx"},"change_message_id":"162159a357bbf9882b2b42038ef9707e2c49149a","unresolved":false,"context_lines":[{"line_number":56,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":57,"context_line":""},{"line_number":58,"context_line":"The TC\u0027s authority over technical matters explicitly includes the authority"},{"line_number":59,"context_line":"to determine the scope of the \"OpenStack\" released software."},{"line_number":60,"context_line":""},{"line_number":61,"context_line":"Under the current governance model, that means the TC constantly refines"},{"line_number":62,"context_line":"the rules used to decide which teams are part of the project and which"}],"source_content_type":"text/x-rst","patch_set":1,"id":"3f79a3b5_8ea4c1b8","line":59,"in_reply_to":"3f79a3b5_c234e149","updated":"2018-12-07 13:07:24.000000000","message":"It\u0027s all in article 4.1, but I guess that can\u0027t hurt to mention it, especially as that bylaws article uses fuzzy legalese such as \"approved release\" and \"coordination procedures\".","commit_id":"868c70c0eb0b1e9204e9454cc0a62fc2b467b598"},{"author":{"_account_id":4257,"name":"Zane Bitter","email":"zbitter@redhat.com","username":"zaneb"},"change_message_id":"006d0321a73f525f1a56f53f92460612eeb01434","unresolved":false,"context_lines":[{"line_number":70,"context_line":"OpenStack installation in order for it to be eligible to use the \"OpenStack"},{"line_number":71,"context_line":"Powered\" trademark."},{"line_number":72,"context_line":""},{"line_number":73,"context_line":"Providing technical guidance toward a unified OpenStack experience"},{"line_number":74,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":75,"context_line":""},{"line_number":76,"context_line":"While most technical details are handled at the project team level, you"}],"source_content_type":"text/x-rst","patch_set":1,"id":"3f79a3b5_23a6eda9","line":73,"updated":"2018-12-07 03:02:25.000000000","message":"I\u0027m (very) glad that we have this section, but something about it doesn\u0027t quite sit right yet.\n\nI think it might be that it isn\u0027t up to the TC to *provide* technical guidance, but rather to... distil it?\n\nThe ideas we need are out there in the community. The TC\u0027s job is to ensure that there\u0027s space for them to be heard, to amplify the best ones, to build consensus, to ensure that decisions get made when consensus is not possible (i.e. we don\u0027t default to paralysis when reasonable people disagree), and to be electorally accountable for getting it wrong. The same is true of PTLs, but for the TC the scope is OpenStack as a whole, not just a single project.","commit_id":"868c70c0eb0b1e9204e9454cc0a62fc2b467b598"},{"author":{"_account_id":17068,"name":"Jean-Philippe Evrard","email":"openstack@a.spamming.party","username":"evrardjp"},"change_message_id":"74d983154d0a3726206f8908a4938df9f9ac9555","unresolved":false,"context_lines":[{"line_number":70,"context_line":"OpenStack installation in order for it to be eligible to use the \"OpenStack"},{"line_number":71,"context_line":"Powered\" trademark."},{"line_number":72,"context_line":""},{"line_number":73,"context_line":"Providing technical guidance toward a unified OpenStack experience"},{"line_number":74,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":75,"context_line":""},{"line_number":76,"context_line":"While most technical details are handled at the project team level, you"}],"source_content_type":"text/x-rst","patch_set":1,"id":"3f79a3b5_4562ca15","line":73,"in_reply_to":"3f79a3b5_0e699159","updated":"2018-12-11 08:45:15.000000000","message":"Agreed with Zane. \"Encouraging a unified OpenStack experience \" is fine too, but it might be missing a thing.\n\nOr completely different title \"Highlighting technicalities for projects, aiming towards unified OpenStack experience\"? I don\u0027t really know, but I am sure someone will find a good wording, if not on this patch, on a follow-up :)","commit_id":"868c70c0eb0b1e9204e9454cc0a62fc2b467b598"},{"author":{"_account_id":308,"name":"Thierry Carrez","email":"thierry@openstack.org","username":"ttx"},"change_message_id":"162159a357bbf9882b2b42038ef9707e2c49149a","unresolved":false,"context_lines":[{"line_number":70,"context_line":"OpenStack installation in order for it to be eligible to use the \"OpenStack"},{"line_number":71,"context_line":"Powered\" trademark."},{"line_number":72,"context_line":""},{"line_number":73,"context_line":"Providing technical guidance toward a unified OpenStack experience"},{"line_number":74,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":75,"context_line":""},{"line_number":76,"context_line":"While most technical details are handled at the project team level, you"}],"source_content_type":"text/x-rst","patch_set":1,"id":"3f79a3b5_0e699159","line":73,"in_reply_to":"3f79a3b5_23a6eda9","updated":"2018-12-07 13:07:24.000000000","message":"Yes, \"provide\" is a bit too... exclusive. Open to suggestions to find a better word. Maybe \"Encouraging a unified OpenStack experience\" ?","commit_id":"868c70c0eb0b1e9204e9454cc0a62fc2b467b598"},{"author":{"_account_id":2472,"name":"Doug Hellmann","email":"dhellmann@redhat.com","username":"doug-hellmann"},"change_message_id":"cac5e60eb631efc19217d9b7b943e3bfced0534c","unresolved":false,"context_lines":[{"line_number":81,"context_line":"project teams, driving a common user experience (common operational"},{"line_number":82,"context_line":"behavior, limited dependencies, base quality levels, minimum feature"},{"line_number":83,"context_line":"set...), pushing cross-project initiatives and influencing its general"},{"line_number":84,"context_line":"direction."},{"line_number":85,"context_line":""},{"line_number":86,"context_line":"Ensuring a healthy, open collaboration"},{"line_number":87,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"}],"source_content_type":"text/x-rst","patch_set":1,"id":"3f79a3b5_7fbed801","line":84,"updated":"2018-12-05 18:09:23.000000000","message":"We could link to the goals process document here as one way this is done.","commit_id":"868c70c0eb0b1e9204e9454cc0a62fc2b467b598"},{"author":{"_account_id":308,"name":"Thierry Carrez","email":"thierry@openstack.org","username":"ttx"},"change_message_id":"162159a357bbf9882b2b42038ef9707e2c49149a","unresolved":false,"context_lines":[{"line_number":81,"context_line":"project teams, driving a common user experience (common operational"},{"line_number":82,"context_line":"behavior, limited dependencies, base quality levels, minimum feature"},{"line_number":83,"context_line":"set...), pushing cross-project initiatives and influencing its general"},{"line_number":84,"context_line":"direction."},{"line_number":85,"context_line":""},{"line_number":86,"context_line":"Ensuring a healthy, open collaboration"},{"line_number":87,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"}],"source_content_type":"text/x-rst","patch_set":1,"id":"3f79a3b5_6e8da526","line":84,"in_reply_to":"3f79a3b5_7fbed801","updated":"2018-12-07 13:07:24.000000000","message":"++","commit_id":"868c70c0eb0b1e9204e9454cc0a62fc2b467b598"},{"author":{"_account_id":4257,"name":"Zane Bitter","email":"zbitter@redhat.com","username":"zaneb"},"change_message_id":"006d0321a73f525f1a56f53f92460612eeb01434","unresolved":false,"context_lines":[{"line_number":92,"context_line":"open source :doc:`licensing rules \u003clicensing\u003e`, are not artificially limiting"},{"line_number":93,"context_line":"the features of the open source software to sell a proprietary \"enterprise\""},{"line_number":94,"context_line":"version, operate in a transparent and accessible manner, and encourage"},{"line_number":95,"context_line":"contribution diversity (corporate, geographic or gender-wise)."},{"line_number":96,"context_line":""},{"line_number":97,"context_line":"Beyond that, TC members are engaged in proactively assessing the health of"},{"line_number":98,"context_line":"the various project teams, and provide advice and help to team members."}],"source_content_type":"text/x-rst","patch_set":1,"id":"3f79a3b5_632f0557","line":95,"range":{"start_line":95,"start_character":49,"end_line":95,"end_character":60},"updated":"2018-12-07 03:02:25.000000000","message":"I don\u0027t think gender diversity is the only type of individual diversity we care about encouraging. I\u0027m not sure how best to express that.","commit_id":"868c70c0eb0b1e9204e9454cc0a62fc2b467b598"},{"author":{"_account_id":5263,"name":"Jeremy Stanley","display_name":"fungi","email":"fungi@yuggoth.org","username":"fungi","status":"missing, presumed fed"},"change_message_id":"6e2d32d1d5d886c81f1e2d113aade2cc6b48f453","unresolved":false,"context_lines":[{"line_number":92,"context_line":"open source :doc:`licensing rules \u003clicensing\u003e`, are not artificially limiting"},{"line_number":93,"context_line":"the features of the open source software to sell a proprietary \"enterprise\""},{"line_number":94,"context_line":"version, operate in a transparent and accessible manner, and encourage"},{"line_number":95,"context_line":"contribution diversity (corporate, geographic or gender-wise)."},{"line_number":96,"context_line":""},{"line_number":97,"context_line":"Beyond that, TC members are engaged in proactively assessing the health of"},{"line_number":98,"context_line":"the various project teams, and provide advice and help to team members."}],"source_content_type":"text/x-rst","patch_set":1,"id":"3f79a3b5_0fe50bcf","line":95,"updated":"2018-12-07 15:23:50.000000000","message":"In past communication I\u0027ve employed the phrase \"cultural, professional and personal diversity\" to cover diversity across axes like place of residence/origin, religion, organizational affiliation, job description, race, gender identification, sexuality, et cetera.","commit_id":"868c70c0eb0b1e9204e9454cc0a62fc2b467b598"},{"author":{"_account_id":17068,"name":"Jean-Philippe Evrard","email":"openstack@a.spamming.party","username":"evrardjp"},"change_message_id":"74d983154d0a3726206f8908a4938df9f9ac9555","unresolved":false,"context_lines":[{"line_number":92,"context_line":"open source :doc:`licensing rules \u003clicensing\u003e`, are not artificially limiting"},{"line_number":93,"context_line":"the features of the open source software to sell a proprietary \"enterprise\""},{"line_number":94,"context_line":"version, operate in a transparent and accessible manner, and encourage"},{"line_number":95,"context_line":"contribution diversity (corporate, geographic or gender-wise)."},{"line_number":96,"context_line":""},{"line_number":97,"context_line":"Beyond that, TC members are engaged in proactively assessing the health of"},{"line_number":98,"context_line":"the various project teams, and provide advice and help to team members."}],"source_content_type":"text/x-rst","patch_set":1,"id":"3f79a3b5_e51e7670","line":95,"in_reply_to":"3f79a3b5_0fe50bcf","updated":"2018-12-11 08:45:15.000000000","message":"\u003e In past communication I\u0027ve employed the phrase \"cultural,\n \u003e professional and personal diversity\" \n\nThat seems better","commit_id":"868c70c0eb0b1e9204e9454cc0a62fc2b467b598"},{"author":{"_account_id":5046,"name":"Lance Bragstad","email":"lbragstad@redhat.com","username":"ldbragst"},"change_message_id":"16d279832bc3ba18b9876f3169bc3c5aed24a783","unresolved":false,"context_lines":[{"line_number":43,"context_line":"using amendments to the :doc:`TC charter \u003ccharter\u003e`, resolutions, or changes"},{"line_number":44,"context_line":"in other TC-maintained documents."},{"line_number":45,"context_line":""},{"line_number":46,"context_line":"The current governance model institutes a two-level structure with"},{"line_number":47,"context_line":":doc:`project teams \u003cprojects/index\u003e` in charge of specific sets of git"},{"line_number":48,"context_line":"repositories or tasks. The TC is reponsible for making sure the model"},{"line_number":49,"context_line":"is followed, and fair elections are held for every project team."},{"line_number":50,"context_line":"Finally, while most conflicts should be resolved at the project team level,"},{"line_number":51,"context_line":"the TC remains ultimately responsible in case issues cannot be solved at"}],"source_content_type":"text/x-rst","patch_set":2,"id":"3f79a3b5_933fbdb1","line":48,"range":{"start_line":46,"start_character":0,"end_line":48,"end_character":22},"updated":"2018-12-11 17:33:30.000000000","message":"This is a little redundant with the first paragraph of the previous section, but I\u0027m not sure I have a better recommendation for consolidating it clearly.\n\nMaybe others do though?","commit_id":"3e84503a41a3361635c27f21e73562d206f79d16"},{"author":{"_account_id":6873,"name":"Matt Riedemann","email":"mriedem.os@gmail.com","username":"mriedem"},"change_message_id":"c9ce030baef8b0f64c9f353b629f51d60aa87f8f","unresolved":false,"context_lines":[{"line_number":85,"context_line":"direction. One way to achieve that is through the definition of OpenStack"},{"line_number":86,"context_line":":doc:`release goals \u003c../goals/index\u003e`."},{"line_number":87,"context_line":""},{"line_number":88,"context_line":""},{"line_number":89,"context_line":"Ensuring a healthy, open collaboration"},{"line_number":90,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":91,"context_line":""}],"source_content_type":"text/x-rst","patch_set":2,"id":"3f79a3b5_3dc9da21","line":88,"updated":"2018-12-11 16:31:05.000000000","message":"nit: drop the extra line","commit_id":"3e84503a41a3361635c27f21e73562d206f79d16"},{"author":{"_account_id":2394,"name":"Adam Spiers","email":"aspiers@suse.com","username":"adam.spiers"},"change_message_id":"c4dd4002face7d5c50d1889de1f0d5c9de96bd91","unresolved":false,"context_lines":[{"line_number":98,"context_line":"cultural, professional and personal diversity in contributions."},{"line_number":99,"context_line":""},{"line_number":100,"context_line":"Beyond that, TC members are engaged in proactively assessing the health of"},{"line_number":101,"context_line":"the various project teams, and provide advice and help to team members."},{"line_number":102,"context_line":""},{"line_number":103,"context_line":""},{"line_number":104,"context_line":".. _OpenStack Foundation bylaws: https://www.openstack.org/legal/bylaws-of-the-openstack-foundation/"}],"source_content_type":"text/x-rst","patch_set":2,"id":"3f79a3b5_2f1aeb80","line":101,"range":{"start_line":101,"start_character":0,"end_line":101,"end_character":71},"updated":"2018-12-12 13:44:48.000000000","message":"What about the SIGs?  I would prefer them to be included here, as discussed in Berlin:\n\nhttps://etherpad.openstack.org/p/expose-sigs-and-wgs\nhttp://lists.openstack.org/pipermail/openstack-discuss/2018-December/000464.html\n\nCurrently SIGs still feel somewhat of a fringe activity, although it\u0027s getting gradually better.","commit_id":"3e84503a41a3361635c27f21e73562d206f79d16"},{"author":{"_account_id":2472,"name":"Doug Hellmann","email":"dhellmann@redhat.com","username":"doug-hellmann"},"change_message_id":"f32b4c05d6556dacfc164fb8076049d63a3587ec","unresolved":false,"context_lines":[{"line_number":98,"context_line":"cultural, professional and personal diversity in contributions."},{"line_number":99,"context_line":""},{"line_number":100,"context_line":"Beyond that, TC members are engaged in proactively assessing the health of"},{"line_number":101,"context_line":"the various project teams, and provide advice and help to team members."},{"line_number":102,"context_line":""},{"line_number":103,"context_line":""},{"line_number":104,"context_line":".. _OpenStack Foundation bylaws: https://www.openstack.org/legal/bylaws-of-the-openstack-foundation/"}],"source_content_type":"text/x-rst","patch_set":2,"id":"3f79a3b5_bab87777","line":101,"range":{"start_line":101,"start_character":0,"end_line":101,"end_character":71},"in_reply_to":"3f79a3b5_2f1aeb80","updated":"2018-12-12 14:25:59.000000000","message":"SIGs are explicitly designed to not be under the TC\u0027s management, so if we add mention of them here we should make that clear. Perhaps we can do that in a follow-up to this patch.","commit_id":"3e84503a41a3361635c27f21e73562d206f79d16"},{"author":{"_account_id":2394,"name":"Adam Spiers","email":"aspiers@suse.com","username":"adam.spiers"},"change_message_id":"8f3c0d9c64e9ee787d73ac88d02e8bd7ee9f1ba2","unresolved":false,"context_lines":[{"line_number":98,"context_line":"cultural, professional and personal diversity in contributions."},{"line_number":99,"context_line":""},{"line_number":100,"context_line":"Beyond that, TC members are engaged in proactively assessing the health of"},{"line_number":101,"context_line":"the various project teams, and provide advice and help to team members."},{"line_number":102,"context_line":""},{"line_number":103,"context_line":""},{"line_number":104,"context_line":".. _OpenStack Foundation bylaws: https://www.openstack.org/legal/bylaws-of-the-openstack-foundation/"}],"source_content_type":"text/x-rst","patch_set":2,"id":"3f79a3b5_80518c0f","line":101,"range":{"start_line":101,"start_character":0,"end_line":101,"end_character":71},"in_reply_to":"3f79a3b5_bab87777","updated":"2018-12-12 15:06:50.000000000","message":"\u003e SIGs are explicitly designed to not be under the TC\u0027s management,\n \u003e so if we add mention of them here we should make that clear.\n\nAh, thanks - I had missed (or forgotten) that!\n\n \u003e Perhaps we can do that in a follow-up to this patch.\n\nWFM.","commit_id":"3e84503a41a3361635c27f21e73562d206f79d16"}]}