)]}'
{"reference/charter.rst":[{"author":{"_account_id":2,"name":"Monty Taylor","email":"mordred@inaugust.com","username":"mordred"},"change_message_id":"56dce61d4c63e0cbc9ba78a256bea959816133ef","unresolved":false,"context_lines":[{"line_number":29,"context_line":"designated as official OpenStack projects. The projects are listed in"},{"line_number":30,"context_line":":ref:`projects`."},{"line_number":31,"context_line":""},{"line_number":32,"context_line":"Project Team Leads"},{"line_number":33,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":34,"context_line":""},{"line_number":35,"context_line":"Project Team Leads (\"PTLs\") manage day-to-day operations, drive the team goals"}],"source_content_type":"text/x-rst","patch_set":1,"id":"1fa4df85_2d0c3a41","side":"PARENT","line":32,"updated":"2020-03-12 14:52:55.000000000","message":"Maybe don\u0027t remove the whole section? Maybe some teams still want to elect a PTL?","commit_id":"ed73db7af1479151b1654245d308488eef50e5c4"},{"author":{"_account_id":2,"name":"Monty Taylor","email":"mordred@inaugust.com","username":"mordred"},"change_message_id":"56dce61d4c63e0cbc9ba78a256bea959816133ef","unresolved":false,"context_lines":[{"line_number":28,"context_line":"(see below). The TC can be called to resolve disputes within project teams,"},{"line_number":29,"context_line":"in case a consensual decision cannot be found within the team."},{"line_number":30,"context_line":""},{"line_number":31,"context_line":"The TC also has ultimate authority over which project teams are"},{"line_number":32,"context_line":"designated as official OpenStack projects. The projects are listed in"},{"line_number":33,"context_line":":ref:`projects`."},{"line_number":34,"context_line":""}],"source_content_type":"text/x-rst","patch_set":1,"id":"1fa4df85_0d2a9e8f","line":31,"updated":"2020-03-12 14:52:55.000000000","message":"I\u0027d move this around a little bit:\n\n The work of project teams...\n  The TC has ultimate ...\n  The TC can be called to resolve ...\n  Contributing ...","commit_id":"a35ed5ad6c9f3e051600100b996081f444350e46"},{"author":{"_account_id":11628,"name":"Michael Johnson","email":"johnsomor@gmail.com","username":"johnsom"},"change_message_id":"e936668dfbbe26628c8c2953cbc81de2c2018f87","unresolved":false,"context_lines":[{"line_number":131,"context_line":""},{"line_number":132,"context_line":"If a PTL seat is vacated before the end of the cycle for which the individual"},{"line_number":133,"context_line":"was elected, the TC will appoint a new PTL, in consultation with the outgoing"},{"line_number":134,"context_line":"PTL and any interested candidates, following the process for leaderless project"},{"line_number":135,"context_line":"teams (see"},{"line_number":136,"context_line":":doc:`/resolutions/20141128-elections-process-for-leaderless-programs`). An"},{"line_number":137,"context_line":"email must be sent to the ``openstack-discuss at lists.openstack.org`` mailing"}],"source_content_type":"text/x-rst","patch_set":4,"id":"1fa4df85_4029e198","side":"PARENT","line":134,"range":{"start_line":134,"start_character":61,"end_line":134,"end_character":79},"updated":"2020-03-19 00:37:21.000000000","message":"I also think the PTL role is a key indicator of a projects health and whether it should be considered for removal from \"OpenStack official\".","commit_id":"027579555b1ed1d46e9c2ccf76d35b71b24fcacf"},{"author":{"_account_id":11628,"name":"Michael Johnson","email":"johnsomor@gmail.com","username":"johnsom"},"change_message_id":"e936668dfbbe26628c8c2953cbc81de2c2018f87","unresolved":false,"context_lines":[{"line_number":131,"context_line":""},{"line_number":132,"context_line":"If a PTL seat is vacated before the end of the cycle for which the individual"},{"line_number":133,"context_line":"was elected, the TC will appoint a new PTL, in consultation with the outgoing"},{"line_number":134,"context_line":"PTL and any interested candidates, following the process for leaderless project"},{"line_number":135,"context_line":"teams (see"},{"line_number":136,"context_line":":doc:`/resolutions/20141128-elections-process-for-leaderless-programs`). An"},{"line_number":137,"context_line":"email must be sent to the ``openstack-discuss at lists.openstack.org`` mailing"},{"line_number":138,"context_line":"list announcing the change in leadership. A patch must also be submitted to the"},{"line_number":139,"context_line":":repo:`openstack/governance` repository updating the project\u0027s"}],"source_content_type":"text/x-rst","patch_set":4,"id":"1fa4df85_003449fa","side":"PARENT","line":136,"range":{"start_line":134,"start_character":49,"end_line":136,"end_character":70},"updated":"2020-03-19 00:37:21.000000000","message":"This resolution will also need to be amended as the process specifically calls out the PTL role.","commit_id":"027579555b1ed1d46e9c2ccf76d35b71b24fcacf"},{"author":{"_account_id":11628,"name":"Michael Johnson","email":"johnsomor@gmail.com","username":"johnsom"},"change_message_id":"e936668dfbbe26628c8c2953cbc81de2c2018f87","unresolved":false,"context_lines":[{"line_number":21,"context_line":"interoperable between deployments, works well at all scales, and meets"},{"line_number":22,"context_line":"the needs of users and operators of both public and private clouds.\u0027\u0027"},{"line_number":23,"context_line":"Project Teams may create any code repository and produce any deliverable they"},{"line_number":24,"context_line":"deem necessary to achieve their goals. Project Teams are self-organized and"},{"line_number":25,"context_line":"may select leadership by a method of their choosing."},{"line_number":26,"context_line":""},{"line_number":27,"context_line":"The work of project teams is performed under the oversight of the TC."},{"line_number":28,"context_line":"The TC has ultimate authority over which project teams are"}],"source_content_type":"text/x-rst","patch_set":4,"id":"1fa4df85_40c0012b","line":25,"range":{"start_line":24,"start_character":39,"end_line":25,"end_character":52},"updated":"2020-03-19 00:37:21.000000000","message":"Including none?","commit_id":"c942b0d7b19b10648ed02752363d36f2bd335e1c"},{"author":{"_account_id":11628,"name":"Michael Johnson","email":"johnsomor@gmail.com","username":"johnsom"},"change_message_id":"e936668dfbbe26628c8c2953cbc81de2c2018f87","unresolved":false,"context_lines":[{"line_number":213,"context_line":"OpenStack, a number of roles must be filled with a clear designated list"},{"line_number":214,"context_line":"of persons habilitated to speak on behalf of the team on a specific topic."},{"line_number":215,"context_line":""},{"line_number":216,"context_line":"Between one and three people may be designated for each role. The list"},{"line_number":217,"context_line":"of names may be updated at any time, and the proposed change will be"},{"line_number":218,"context_line":"accepted if it bears the approval of the previous and new role owners."},{"line_number":219,"context_line":"In case of disagreement, the dispute can be resolved by the TC."}],"source_content_type":"text/x-rst","patch_set":4,"id":"1fa4df85_40d561e4","line":216,"range":{"start_line":216,"start_character":0,"end_line":216,"end_character":60},"updated":"2020-03-19 00:37:21.000000000","message":"\"I thought you took care of that.\" \"That is a not-fun task, I will leave it for someone else to handle.\"","commit_id":"c942b0d7b19b10648ed02752363d36f2bd335e1c"},{"author":{"_account_id":11628,"name":"Michael Johnson","email":"johnsomor@gmail.com","username":"johnsom"},"change_message_id":"e936668dfbbe26628c8c2953cbc81de2c2018f87","unresolved":false,"context_lines":[{"line_number":213,"context_line":"OpenStack, a number of roles must be filled with a clear designated list"},{"line_number":214,"context_line":"of persons habilitated to speak on behalf of the team on a specific topic."},{"line_number":215,"context_line":""},{"line_number":216,"context_line":"Between one and three people may be designated for each role. The list"},{"line_number":217,"context_line":"of names may be updated at any time, and the proposed change will be"},{"line_number":218,"context_line":"accepted if it bears the approval of the previous and new role owners."},{"line_number":219,"context_line":"In case of disagreement, the dispute can be resolved by the TC."},{"line_number":220,"context_line":""},{"line_number":221,"context_line":"Those roles are:"}],"source_content_type":"text/x-rst","patch_set":4,"id":"1fa4df85_c06f11fa","line":218,"range":{"start_line":216,"start_character":62,"end_line":218,"end_character":70},"updated":"2020-03-19 00:37:21.000000000","message":"It seems like a loss to drop the election process. It provides a public and clear path for people to participate.\nEspecially for folks that are shy to assert themselves in meetings, etc.","commit_id":"c942b0d7b19b10648ed02752363d36f2bd335e1c"},{"author":{"_account_id":16708,"name":"Kendall Nelson","display_name":"Kendall (diablo_rojo)","email":"kennelson11@gmail.com","username":"kjnelson"},"change_message_id":"01d08298b0b598c0ba8b159fd2b991516ffe94ae","unresolved":false,"context_lines":[{"line_number":215,"context_line":""},{"line_number":216,"context_line":"Between one and three people may be designated for each role. The list"},{"line_number":217,"context_line":"of names may be updated at any time, and the proposed change will be"},{"line_number":218,"context_line":"accepted if it bears the approval of the previous and new role owners."},{"line_number":219,"context_line":"In case of disagreement, the dispute can be resolved by the TC."},{"line_number":220,"context_line":""},{"line_number":221,"context_line":"Those roles are:"}],"source_content_type":"text/x-rst","patch_set":4,"id":"1fa4df85_45bcd3ba","line":218,"range":{"start_line":218,"start_character":69,"end_line":218,"end_character":70},"updated":"2020-03-14 00:20:27.000000000","message":"Maybe we also have the TC liaison for that project sign off on the patch too.","commit_id":"c942b0d7b19b10648ed02752363d36f2bd335e1c"},{"author":{"_account_id":11628,"name":"Michael Johnson","email":"johnsomor@gmail.com","username":"johnsom"},"change_message_id":"e936668dfbbe26628c8c2953cbc81de2c2018f87","unresolved":false,"context_lines":[{"line_number":218,"context_line":"accepted if it bears the approval of the previous and new role owners."},{"line_number":219,"context_line":"In case of disagreement, the dispute can be resolved by the TC."},{"line_number":220,"context_line":""},{"line_number":221,"context_line":"Those roles are:"},{"line_number":222,"context_line":""},{"line_number":223,"context_line":"- Release liaison: list of people which are allowed to sign off on a release"},{"line_number":224,"context_line":"  request for a deliverable owned by the project team."}],"source_content_type":"text/x-rst","patch_set":4,"id":"1fa4df85_605f3d41","line":221,"range":{"start_line":221,"start_character":0,"end_line":221,"end_character":16},"updated":"2020-03-19 00:37:21.000000000","message":"This seems light.\n\nAt a minimum another critical role is managing the core reviewer ACLs and project \"associated\" repositories lists.","commit_id":"c942b0d7b19b10648ed02752363d36f2bd335e1c"},{"author":{"_account_id":16708,"name":"Kendall Nelson","display_name":"Kendall (diablo_rojo)","email":"kennelson11@gmail.com","username":"kjnelson"},"change_message_id":"01d08298b0b598c0ba8b159fd2b991516ffe94ae","unresolved":false,"context_lines":[{"line_number":223,"context_line":"- Release liaison: list of people which are allowed to sign off on a release"},{"line_number":224,"context_line":"  request for a deliverable owned by the project team."},{"line_number":225,"context_line":""},{"line_number":226,"context_line":"- Event liaison: contact point for organizing team gathering events."},{"line_number":227,"context_line":""},{"line_number":228,"context_line":"- Meeting chair: person(s) responsible for setting the agenda for team"},{"line_number":229,"context_line":"  meetings, and driving the meeting itself."}],"source_content_type":"text/x-rst","patch_set":4,"id":"1fa4df85_c590c351","line":226,"range":{"start_line":226,"start_character":67,"end_line":226,"end_character":68},"updated":"2020-03-14 00:20:27.000000000","message":"I feel like this should be a single person and not a max of three like the other roles. The amount of effort/work for this role isn\u0027t as much as the others and so I don\u0027t think it requires more than one person. Also, from my persepetive, sending out the PTG attendance survey, for example, to multiple people representing a single group (I have to do this now for some SIGS) sometimes illicits multiple responses and causes confusion.","commit_id":"c942b0d7b19b10648ed02752363d36f2bd335e1c"},{"author":{"_account_id":11628,"name":"Michael Johnson","email":"johnsomor@gmail.com","username":"johnsom"},"change_message_id":"e936668dfbbe26628c8c2953cbc81de2c2018f87","unresolved":false,"context_lines":[{"line_number":227,"context_line":""},{"line_number":228,"context_line":"- Meeting chair: person(s) responsible for setting the agenda for team"},{"line_number":229,"context_line":"  meetings, and driving the meeting itself."},{"line_number":230,"context_line":""},{"line_number":231,"context_line":".. _charter-amendment-section:"},{"line_number":232,"context_line":""},{"line_number":233,"context_line":"Amendment"}],"source_content_type":"text/x-rst","patch_set":4,"id":"1fa4df85_40548121","line":230,"updated":"2020-03-19 00:37:21.000000000","message":"Any guidance on how to reach the team lead(s)?\nPreviously we could look at the governance page and/or use the [PTL] subject tag on the discuss list. What happens when there is no PTL?","commit_id":"c942b0d7b19b10648ed02752363d36f2bd335e1c"}],"reference/projects.yaml":[{"author":{"_account_id":2,"name":"Monty Taylor","email":"mordred@inaugust.com","username":"mordred"},"change_message_id":"56dce61d4c63e0cbc9ba78a256bea959816133ef","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"1fa4df85_880c3c3c","updated":"2020-03-12 14:52:55.000000000","message":"I don\u0027t think you should remove all of the PTLs from here - or any of them - until such a time as they are not the elected PTL.","commit_id":"a35ed5ad6c9f3e051600100b996081f444350e46"}],"resolutions/20200311-dissolving-ptl-role.rst":[{"author":{"_account_id":13995,"name":"Nate Johnston","email":"nate.johnston@redhat.com","username":"natejohnston"},"change_message_id":"bb0ac34f8201c8a623ad656864034b6f2e3c453d","unresolved":false,"context_lines":[{"line_number":1,"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"},{"line_number":2,"context_line":" 2020-03-11 Dissolving PTL role"},{"line_number":3,"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"},{"line_number":4,"context_line":""},{"line_number":5,"context_line":"The role of a project team lead has been around inside the OpenStack project"}],"source_content_type":"text/x-rst","patch_set":4,"id":"1fa4df85_c72b022e","line":2,"range":{"start_line":2,"start_character":0,"end_line":2,"end_character":31},"updated":"2020-03-12 16:33:23.000000000","message":"Does this need to note previous governance actions that are superceded or nullified by this resolution, like https://governance.openstack.org/tc/resolutions/20141128-elections-process-for-leaderless-programs.html","commit_id":"c942b0d7b19b10648ed02752363d36f2bd335e1c"},{"author":{"_account_id":11628,"name":"Michael Johnson","email":"johnsomor@gmail.com","username":"johnsom"},"change_message_id":"e936668dfbbe26628c8c2953cbc81de2c2018f87","unresolved":false,"context_lines":[{"line_number":1,"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"},{"line_number":2,"context_line":" 2020-03-11 Dissolving PTL role"},{"line_number":3,"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"},{"line_number":4,"context_line":""},{"line_number":5,"context_line":"The role of a project team lead has been around inside the OpenStack project"}],"source_content_type":"text/x-rst","patch_set":4,"id":"1fa4df85_20c5c53c","line":2,"range":{"start_line":2,"start_character":12,"end_line":2,"end_character":31},"updated":"2020-03-19 00:37:21.000000000","message":"This document does not address what problem it is trying to solve clearly.\n\nIs it a lack of clarity in our documentation of the PTL role?\nIs it PTL burn out?\nIs it projects that are dying due to lack of interest, thus have no PTL nominations?\nIs it a step towards disbanding the governance of the community?\nIs it concern that some project PTLs are not living up to the \"ideal\" PTL?\nIs it siloing of projects that the PTL role has become a dictatorship?\nIs it panic due to decreasing community involvement?\n\nI think all of these have alternatives to simply dissolving the PTL role.\n\nOthers?","commit_id":"c942b0d7b19b10648ed02752363d36f2bd335e1c"},{"author":{"_account_id":5263,"name":"Jeremy Stanley","display_name":"fungi","email":"fungi@yuggoth.org","username":"fungi","status":"missing, presumed fed"},"change_message_id":"c4828753a5e3fe7d0d76e5f3b3cf85798d0676c0","unresolved":false,"context_lines":[{"line_number":13,"context_line":"However, the role has become overloaded with the PTL becoming an individual"},{"line_number":14,"context_line":"who represents the entire project and carrying much more responsibilities from"},{"line_number":15,"context_line":"ensuring releases happen, unblocking gates, organizing PTGs, preparing talks"},{"line_number":16,"context_line":"for project updates, and onboarding and much more."},{"line_number":17,"context_line":""},{"line_number":18,"context_line":"With OpenStack becoming more mature than before and the velocity of changes"},{"line_number":19,"context_line":"and the number of individuals involved both reduced, the projects no longer"}],"source_content_type":"text/x-rst","patch_set":4,"id":"1fa4df85_edb61ddd","line":16,"updated":"2020-03-12 18:00:42.000000000","message":"Put another way, I think the real point of this change is to let projects die when there\u0027s no longer anybody who wants to do these things.","commit_id":"c942b0d7b19b10648ed02752363d36f2bd335e1c"},{"author":{"_account_id":8482,"name":"Colleen Murphy","email":"colleen@gazlene.net","username":"krinkle"},"change_message_id":"e1919b8fad9d7863c01347c24dbc6d2f49f88480","unresolved":false,"context_lines":[{"line_number":10,"context_line":"resolving technical disputes within the team, and becoming a tie-breaker if"},{"line_number":11,"context_line":"the group is unable to come to a consensus."},{"line_number":12,"context_line":""},{"line_number":13,"context_line":"However, the role has become overloaded with the PTL becoming an individual"},{"line_number":14,"context_line":"who represents the entire project and carrying much more responsibilities from"},{"line_number":15,"context_line":"ensuring releases happen, unblocking gates, organizing PTGs, preparing talks"},{"line_number":16,"context_line":"for project updates, and onboarding and much more."},{"line_number":17,"context_line":""},{"line_number":18,"context_line":"With OpenStack becoming more mature than before and the velocity of changes"},{"line_number":19,"context_line":"and the number of individuals involved both reduced, the projects no longer"}],"source_content_type":"text/x-rst","patch_set":4,"id":"1fa4df85_a3603b37","line":16,"range":{"start_line":13,"start_character":49,"end_line":16,"end_character":50},"updated":"2020-03-12 16:05:43.000000000","message":"This resolution does not address who will assume responsibility for these things when there is no PTL to do so. This *is* the PTL\u0027s job, no matter how much you want to try to say it\u0027s \"just a point of contact\" or a \"tiebreaker\". If the PTL is abolished, no one will pick up this work and projects will die.","commit_id":"c942b0d7b19b10648ed02752363d36f2bd335e1c"},{"author":{"_account_id":11628,"name":"Michael Johnson","email":"johnsomor@gmail.com","username":"johnsom"},"change_message_id":"e936668dfbbe26628c8c2953cbc81de2c2018f87","unresolved":false,"context_lines":[{"line_number":11,"context_line":"the group is unable to come to a consensus."},{"line_number":12,"context_line":""},{"line_number":13,"context_line":"However, the role has become overloaded with the PTL becoming an individual"},{"line_number":14,"context_line":"who represents the entire project and carrying much more responsibilities from"},{"line_number":15,"context_line":"ensuring releases happen, unblocking gates, organizing PTGs, preparing talks"},{"line_number":16,"context_line":"for project updates, and onboarding and much more."},{"line_number":17,"context_line":""},{"line_number":18,"context_line":"With OpenStack becoming more mature than before and the velocity of changes"},{"line_number":19,"context_line":"and the number of individuals involved both reduced, the projects no longer"}],"source_content_type":"text/x-rst","patch_set":4,"id":"1fa4df85_80459917","line":16,"range":{"start_line":14,"start_character":38,"end_line":16,"end_character":50},"updated":"2020-03-19 00:37:21.000000000","message":"While this is true in some cases, it is not true in all of the project teams. We also already have a system of liaisons (https://wiki.openstack.org/wiki/CrossProjectLiaisons), \"Lieutenants\" (https://docs.openstack.org/neutron/pike/contributor/policies/neutron-teams.html#core-review-hierarchy), etc.\nThese items can be delegated by the PTL as many teams, such as Octavia, have.","commit_id":"c942b0d7b19b10648ed02752363d36f2bd335e1c"},{"author":{"_account_id":1004,"name":"Mohammed Naser","email":"mnaser@vexxhost.com","username":"mnaser"},"change_message_id":"d08322cde707b20ada44e8c318e3e9d9ebcbfe30","unresolved":false,"context_lines":[{"line_number":10,"context_line":"resolving technical disputes within the team, and becoming a tie-breaker if"},{"line_number":11,"context_line":"the group is unable to come to a consensus."},{"line_number":12,"context_line":""},{"line_number":13,"context_line":"However, the role has become overloaded with the PTL becoming an individual"},{"line_number":14,"context_line":"who represents the entire project and carrying much more responsibilities from"},{"line_number":15,"context_line":"ensuring releases happen, unblocking gates, organizing PTGs, preparing talks"},{"line_number":16,"context_line":"for project updates, and onboarding and much more."},{"line_number":17,"context_line":""},{"line_number":18,"context_line":"With OpenStack becoming more mature than before and the velocity of changes"},{"line_number":19,"context_line":"and the number of individuals involved both reduced, the projects no longer"}],"source_content_type":"text/x-rst","patch_set":4,"id":"1fa4df85_0764bab8","line":16,"range":{"start_line":13,"start_character":49,"end_line":16,"end_character":50},"in_reply_to":"1fa4df85_a3603b37","updated":"2020-03-12 16:31:38.000000000","message":"all of these are things which PTLs are not mandated to do, and we\u0027re burning out people by having that huge workload on them.\n\nthe release liaison will make sure the release still happens, *any* contributor can unblock the gate, *any* contributor can organize PTG, *any* contributor can do project updates and on-boarding.  this doesn\u0027t have to be the ptl.\n\nthe hope is that teams can self-organize because most cores work together tightly enough to discuss and split these responsibilities between them\n\nif they can\u0027t find a way to do that, I\u0027m afraid that\u0027s a dysfunctional team unfortunately","commit_id":"c942b0d7b19b10648ed02752363d36f2bd335e1c"},{"author":{"_account_id":9708,"name":"Balazs Gibizer","display_name":"gibi","email":"gibizer@gmail.com","username":"gibi"},"change_message_id":"8514bacc69f0699404a0143657b13afeed4d661b","unresolved":false,"context_lines":[{"line_number":13,"context_line":"However, the role has become overloaded with the PTL becoming an individual"},{"line_number":14,"context_line":"who represents the entire project and carrying much more responsibilities from"},{"line_number":15,"context_line":"ensuring releases happen, unblocking gates, organizing PTGs, preparing talks"},{"line_number":16,"context_line":"for project updates, and onboarding and much more."},{"line_number":17,"context_line":""},{"line_number":18,"context_line":"With OpenStack becoming more mature than before and the velocity of changes"},{"line_number":19,"context_line":"and the number of individuals involved both reduced, the projects no longer"}],"source_content_type":"text/x-rst","patch_set":4,"id":"1fa4df85_091b6473","line":16,"in_reply_to":"1fa4df85_edb61ddd","updated":"2020-03-13 08:45:43.000000000","message":"There is difference between \"doing the tasks\" or \"making sure that the task is done by somebody\". I feel that when we say \"anybody can organize PTG\" is the \"doing the task\" part. But who will make sure that the person exists and knows that he has to do the organization? Is it the TC?","commit_id":"c942b0d7b19b10648ed02752363d36f2bd335e1c"},{"author":{"_account_id":11628,"name":"Michael Johnson","email":"johnsomor@gmail.com","username":"johnsom"},"change_message_id":"e936668dfbbe26628c8c2953cbc81de2c2018f87","unresolved":false,"context_lines":[{"line_number":15,"context_line":"ensuring releases happen, unblocking gates, organizing PTGs, preparing talks"},{"line_number":16,"context_line":"for project updates, and onboarding and much more."},{"line_number":17,"context_line":""},{"line_number":18,"context_line":"With OpenStack becoming more mature than before and the velocity of changes"},{"line_number":19,"context_line":"and the number of individuals involved both reduced, the projects no longer"},{"line_number":20,"context_line":"need to have a specific individual to run the day-to-day operations of the"},{"line_number":21,"context_line":"project.  OpenStack projects have successfully managed to continue to work"},{"line_number":22,"context_line":"together following our four opens without needing much of a tie-breaker."}],"source_content_type":"text/x-rst","patch_set":4,"id":"1fa4df85_4099e176","line":19,"range":{"start_line":18,"start_character":56,"end_line":19,"end_character":51},"updated":"2020-03-19 00:37:21.000000000","message":"I don\u0027t think this can be a blanket statement. Some teams have flat or even growing involvement and a relatively high velocity(accounting for team size).","commit_id":"c942b0d7b19b10648ed02752363d36f2bd335e1c"},{"author":{"_account_id":11628,"name":"Michael Johnson","email":"johnsomor@gmail.com","username":"johnsom"},"change_message_id":"e936668dfbbe26628c8c2953cbc81de2c2018f87","unresolved":false,"context_lines":[{"line_number":16,"context_line":"for project updates, and onboarding and much more."},{"line_number":17,"context_line":""},{"line_number":18,"context_line":"With OpenStack becoming more mature than before and the velocity of changes"},{"line_number":19,"context_line":"and the number of individuals involved both reduced, the projects no longer"},{"line_number":20,"context_line":"need to have a specific individual to run the day-to-day operations of the"},{"line_number":21,"context_line":"project.  OpenStack projects have successfully managed to continue to work"},{"line_number":22,"context_line":"together following our four opens without needing much of a tie-breaker."},{"line_number":23,"context_line":""},{"line_number":24,"context_line":"It makes sense that the OpenStack projects no longer need to maintain a single"}],"source_content_type":"text/x-rst","patch_set":4,"id":"1fa4df85_a00e95e2","line":21,"range":{"start_line":19,"start_character":57,"end_line":21,"end_character":7},"updated":"2020-03-19 00:37:21.000000000","message":"I disagree with this statement. I think we are confusing \"need\" with \"are able\". Personally I don\u0027t think the need has decreased. There are constant outside impacts to teams (cross project collaboration, community goals, dependency breakage, etc.) that having an individual take point is beneficial to the community.","commit_id":"c942b0d7b19b10648ed02752363d36f2bd335e1c"},{"author":{"_account_id":11628,"name":"Michael Johnson","email":"johnsomor@gmail.com","username":"johnsom"},"change_message_id":"e936668dfbbe26628c8c2953cbc81de2c2018f87","unresolved":false,"context_lines":[{"line_number":19,"context_line":"and the number of individuals involved both reduced, the projects no longer"},{"line_number":20,"context_line":"need to have a specific individual to run the day-to-day operations of the"},{"line_number":21,"context_line":"project.  OpenStack projects have successfully managed to continue to work"},{"line_number":22,"context_line":"together following our four opens without needing much of a tie-breaker."},{"line_number":23,"context_line":""},{"line_number":24,"context_line":"It makes sense that the OpenStack projects no longer need to maintain a single"},{"line_number":25,"context_line":"individual who becomes a representative of the entire project at this point."}],"source_content_type":"text/x-rst","patch_set":4,"id":"1fa4df85_2002a5b5","line":22,"range":{"start_line":22,"start_character":42,"end_line":22,"end_character":71},"updated":"2020-03-19 00:37:21.000000000","message":"Maybe not as formal or \"public\" as in the past. lol","commit_id":"c942b0d7b19b10648ed02752363d36f2bd335e1c"},{"author":{"_account_id":11628,"name":"Michael Johnson","email":"johnsomor@gmail.com","username":"johnsom"},"change_message_id":"e936668dfbbe26628c8c2953cbc81de2c2018f87","unresolved":false,"context_lines":[{"line_number":21,"context_line":"project.  OpenStack projects have successfully managed to continue to work"},{"line_number":22,"context_line":"together following our four opens without needing much of a tie-breaker."},{"line_number":23,"context_line":""},{"line_number":24,"context_line":"It makes sense that the OpenStack projects no longer need to maintain a single"},{"line_number":25,"context_line":"individual who becomes a representative of the entire project at this point."},{"line_number":26,"context_line":"The projects should have their frameworks to decide how they want to continue"},{"line_number":27,"context_line":"to run the project amongst the contributors and core members."},{"line_number":28,"context_line":""}],"source_content_type":"text/x-rst","patch_set":4,"id":"1fa4df85_4016c1f3","line":25,"range":{"start_line":24,"start_character":0,"end_line":25,"end_character":76},"updated":"2020-03-19 00:37:21.000000000","message":"I disagree. I think there is value in a point of contact and coordination. This includes teams that have already put \"Lieutenants\" structures in place.\nTeams without a leader/point person tend to devolve with the following issues:\nSomeone will assume that role, but not get the recognition they deserve for the efforts, leading to burn out.\nThe team members will fall into \"someone else will take care of that\" mode.","commit_id":"c942b0d7b19b10648ed02752363d36f2bd335e1c"},{"author":{"_account_id":13995,"name":"Nate Johnston","email":"nate.johnston@redhat.com","username":"natejohnston"},"change_message_id":"16b18bb1f4cf0f49b1b6ec0973e2eebeb1aa9ffe","unresolved":false,"context_lines":[{"line_number":21,"context_line":"project.  OpenStack projects have successfully managed to continue to work"},{"line_number":22,"context_line":"together following our four opens without needing much of a tie-breaker."},{"line_number":23,"context_line":""},{"line_number":24,"context_line":"It makes sense that the OpenStack projects no longer need to maintain a single"},{"line_number":25,"context_line":"individual who becomes a representative of the entire project at this point."},{"line_number":26,"context_line":"The projects should have their frameworks to decide how they want to continue"},{"line_number":27,"context_line":"to run the project amongst the contributors and core members."},{"line_number":28,"context_line":""},{"line_number":29,"context_line":"Teams should maintain a few (ideally) different individuals who act as"},{"line_number":30,"context_line":"liaisons to help ensure that specific objectives of OpenStack as a whole can"},{"line_number":31,"context_line":"continue; those roles are:"},{"line_number":32,"context_line":""},{"line_number":33,"context_line":"* Release liaison: works with Release management team to ensure that OpenStack"},{"line_number":34,"context_line":"  coordinated release happens successfully"}],"source_content_type":"text/x-rst","patch_set":4,"id":"1fa4df85_28b0a88b","line":31,"range":{"start_line":24,"start_character":0,"end_line":31,"end_character":26},"updated":"2020-03-12 15:29:19.000000000","message":"In the second paragraph here the transition is made from \"teams can choose to govern themselves differently\" to \"we\u0027re assuming all teams will choose to govern themselves using this new model\".  I think that it would be better to lay the proposal out this way:\n\n1. We want to let projects self-organize if they with because $REASONS\n\n2. If a project wants to organize a different way then they should propose their self-governance plan to the governance repo and a \"ptl-less\" flag will be added to the project.  The TC will review and approve based on meeting the minimum team contact info criteria only.\n\n3. Any teams that don\u0027t do this will continue to elect PTLs as has traditionally been done.","commit_id":"c942b0d7b19b10648ed02752363d36f2bd335e1c"},{"author":{"_account_id":11628,"name":"Michael Johnson","email":"johnsomor@gmail.com","username":"johnsom"},"change_message_id":"e936668dfbbe26628c8c2953cbc81de2c2018f87","unresolved":false,"context_lines":[{"line_number":26,"context_line":"The projects should have their frameworks to decide how they want to continue"},{"line_number":27,"context_line":"to run the project amongst the contributors and core members."},{"line_number":28,"context_line":""},{"line_number":29,"context_line":"Teams should maintain a few (ideally) different individuals who act as"},{"line_number":30,"context_line":"liaisons to help ensure that specific objectives of OpenStack as a whole can"},{"line_number":31,"context_line":"continue; those roles are:"},{"line_number":32,"context_line":""},{"line_number":33,"context_line":"* Release liaison: works with Release management team to ensure that OpenStack"},{"line_number":34,"context_line":"  coordinated release happens successfully"}],"source_content_type":"text/x-rst","patch_set":4,"id":"1fa4df85_00d68928","line":31,"range":{"start_line":29,"start_character":0,"end_line":31,"end_character":26},"updated":"2020-03-19 00:37:21.000000000","message":"This already occurs under the current PTL structures, so I don\u0027t understand how this is a change really.","commit_id":"c942b0d7b19b10648ed02752363d36f2bd335e1c"},{"author":{"_account_id":1004,"name":"Mohammed Naser","email":"mnaser@vexxhost.com","username":"mnaser"},"change_message_id":"d08322cde707b20ada44e8c318e3e9d9ebcbfe30","unresolved":false,"context_lines":[{"line_number":21,"context_line":"project.  OpenStack projects have successfully managed to continue to work"},{"line_number":22,"context_line":"together following our four opens without needing much of a tie-breaker."},{"line_number":23,"context_line":""},{"line_number":24,"context_line":"It makes sense that the OpenStack projects no longer need to maintain a single"},{"line_number":25,"context_line":"individual who becomes a representative of the entire project at this point."},{"line_number":26,"context_line":"The projects should have their frameworks to decide how they want to continue"},{"line_number":27,"context_line":"to run the project amongst the contributors and core members."},{"line_number":28,"context_line":""},{"line_number":29,"context_line":"Teams should maintain a few (ideally) different individuals who act as"},{"line_number":30,"context_line":"liaisons to help ensure that specific objectives of OpenStack as a whole can"},{"line_number":31,"context_line":"continue; those roles are:"},{"line_number":32,"context_line":""},{"line_number":33,"context_line":"* Release liaison: works with Release management team to ensure that OpenStack"},{"line_number":34,"context_line":"  coordinated release happens successfully"}],"source_content_type":"text/x-rst","patch_set":4,"id":"1fa4df85_07091adc","line":31,"range":{"start_line":24,"start_character":0,"end_line":31,"end_character":26},"in_reply_to":"1fa4df85_23c44b92","updated":"2020-03-12 16:31:38.000000000","message":"yes, the \"liaisons\" is still something that\u0027s being figured out and ideally we should minimize them as much as we can.","commit_id":"c942b0d7b19b10648ed02752363d36f2bd335e1c"},{"author":{"_account_id":13995,"name":"Nate Johnston","email":"nate.johnston@redhat.com","username":"natejohnston"},"change_message_id":"b4ac78c79c0e2c91db8555b28be68f7241c7119e","unresolved":false,"context_lines":[{"line_number":21,"context_line":"project.  OpenStack projects have successfully managed to continue to work"},{"line_number":22,"context_line":"together following our four opens without needing much of a tie-breaker."},{"line_number":23,"context_line":""},{"line_number":24,"context_line":"It makes sense that the OpenStack projects no longer need to maintain a single"},{"line_number":25,"context_line":"individual who becomes a representative of the entire project at this point."},{"line_number":26,"context_line":"The projects should have their frameworks to decide how they want to continue"},{"line_number":27,"context_line":"to run the project amongst the contributors and core members."},{"line_number":28,"context_line":""},{"line_number":29,"context_line":"Teams should maintain a few (ideally) different individuals who act as"},{"line_number":30,"context_line":"liaisons to help ensure that specific objectives of OpenStack as a whole can"},{"line_number":31,"context_line":"continue; those roles are:"},{"line_number":32,"context_line":""},{"line_number":33,"context_line":"* Release liaison: works with Release management team to ensure that OpenStack"},{"line_number":34,"context_line":"  coordinated release happens successfully"}],"source_content_type":"text/x-rst","patch_set":4,"id":"1fa4df85_c866b42a","line":31,"range":{"start_line":24,"start_character":0,"end_line":31,"end_character":26},"in_reply_to":"1fa4df85_28b0a88b","updated":"2020-03-12 15:30:29.000000000","message":"*self-organize if they wish","commit_id":"c942b0d7b19b10648ed02752363d36f2bd335e1c"},{"author":{"_account_id":28522,"name":"Hervé Beraud","email":"herveberaud.pro@gmail.com","username":"hberaud"},"change_message_id":"86ecf21ff8c7dc478b25e1f6fba1744458243c64","unresolved":false,"context_lines":[{"line_number":21,"context_line":"project.  OpenStack projects have successfully managed to continue to work"},{"line_number":22,"context_line":"together following our four opens without needing much of a tie-breaker."},{"line_number":23,"context_line":""},{"line_number":24,"context_line":"It makes sense that the OpenStack projects no longer need to maintain a single"},{"line_number":25,"context_line":"individual who becomes a representative of the entire project at this point."},{"line_number":26,"context_line":"The projects should have their frameworks to decide how they want to continue"},{"line_number":27,"context_line":"to run the project amongst the contributors and core members."},{"line_number":28,"context_line":""},{"line_number":29,"context_line":"Teams should maintain a few (ideally) different individuals who act as"},{"line_number":30,"context_line":"liaisons to help ensure that specific objectives of OpenStack as a whole can"},{"line_number":31,"context_line":"continue; those roles are:"},{"line_number":32,"context_line":""},{"line_number":33,"context_line":"* Release liaison: works with Release management team to ensure that OpenStack"},{"line_number":34,"context_line":"  coordinated release happens successfully"}],"source_content_type":"text/x-rst","patch_set":4,"id":"1fa4df85_23c44b92","line":31,"range":{"start_line":24,"start_character":0,"end_line":31,"end_character":26},"in_reply_to":"1fa4df85_28b0a88b","updated":"2020-03-12 15:42:51.000000000","message":"\u003e In the second paragraph here the transition is made from \"teams can\n \u003e choose to govern themselves differently\" to \"we\u0027re assuming all\n \u003e teams will choose to govern themselves using this new model\".  I\n \u003e think that it would be better to lay the proposal out this way:\n \u003e \n \u003e 1. We want to let projects self-organize if they with because\n \u003e $REASONS\n \u003e \n \u003e 2. If a project wants to organize a different way then they should\n \u003e propose their self-governance plan to the governance repo and a\n \u003e \"ptl-less\" flag will be added to the project.  The TC will review\n \u003e and approve based on meeting the minimum team contact info criteria\n \u003e only.\n\nHowever I think some part are unavoidable like the \"release liaison\" which is something mandatory in all the cases... but I think you speak about organization in a general manner in the team.\n\n \u003e \n \u003e 3. Any teams that don\u0027t do this will continue to elect PTLs as has\n \u003e traditionally been done.","commit_id":"c942b0d7b19b10648ed02752363d36f2bd335e1c"},{"author":{"_account_id":1004,"name":"Mohammed Naser","email":"mnaser@vexxhost.com","username":"mnaser"},"change_message_id":"d08322cde707b20ada44e8c318e3e9d9ebcbfe30","unresolved":false,"context_lines":[{"line_number":21,"context_line":"project.  OpenStack projects have successfully managed to continue to work"},{"line_number":22,"context_line":"together following our four opens without needing much of a tie-breaker."},{"line_number":23,"context_line":""},{"line_number":24,"context_line":"It makes sense that the OpenStack projects no longer need to maintain a single"},{"line_number":25,"context_line":"individual who becomes a representative of the entire project at this point."},{"line_number":26,"context_line":"The projects should have their frameworks to decide how they want to continue"},{"line_number":27,"context_line":"to run the project amongst the contributors and core members."},{"line_number":28,"context_line":""},{"line_number":29,"context_line":"Teams should maintain a few (ideally) different individuals who act as"},{"line_number":30,"context_line":"liaisons to help ensure that specific objectives of OpenStack as a whole can"},{"line_number":31,"context_line":"continue; those roles are:"},{"line_number":32,"context_line":""},{"line_number":33,"context_line":"* Release liaison: works with Release management team to ensure that OpenStack"},{"line_number":34,"context_line":"  coordinated release happens successfully"}],"source_content_type":"text/x-rst","patch_set":4,"id":"1fa4df85_876f4a91","line":31,"range":{"start_line":24,"start_character":0,"end_line":31,"end_character":26},"in_reply_to":"1fa4df85_28b0a88b","updated":"2020-03-12 16:31:38.000000000","message":"I don\u0027t think we should have ptl and ptl-less, because pressure will be on project that are ptl-less to have a ptl, because they\u0027re going to \"seem\" less adequate or \"less\" performing.  it\u0027s a perception thing, we\u0027re humans.","commit_id":"c942b0d7b19b10648ed02752363d36f2bd335e1c"},{"author":{"_account_id":13995,"name":"Nate Johnston","email":"nate.johnston@redhat.com","username":"natejohnston"},"change_message_id":"ae4d0b817fb2fea8f05313b5665cea0b01b9fe60","unresolved":false,"context_lines":[{"line_number":21,"context_line":"project.  OpenStack projects have successfully managed to continue to work"},{"line_number":22,"context_line":"together following our four opens without needing much of a tie-breaker."},{"line_number":23,"context_line":""},{"line_number":24,"context_line":"It makes sense that the OpenStack projects no longer need to maintain a single"},{"line_number":25,"context_line":"individual who becomes a representative of the entire project at this point."},{"line_number":26,"context_line":"The projects should have their frameworks to decide how they want to continue"},{"line_number":27,"context_line":"to run the project amongst the contributors and core members."},{"line_number":28,"context_line":""},{"line_number":29,"context_line":"Teams should maintain a few (ideally) different individuals who act as"},{"line_number":30,"context_line":"liaisons to help ensure that specific objectives of OpenStack as a whole can"},{"line_number":31,"context_line":"continue; those roles are:"},{"line_number":32,"context_line":""},{"line_number":33,"context_line":"* Release liaison: works with Release management team to ensure that OpenStack"},{"line_number":34,"context_line":"  coordinated release happens successfully"}],"source_content_type":"text/x-rst","patch_set":4,"id":"1fa4df85_a8181884","line":31,"range":{"start_line":24,"start_character":0,"end_line":31,"end_character":26},"in_reply_to":"1fa4df85_28b0a88b","updated":"2020-03-12 15:34:36.000000000","message":"TC would also condition approval based on compliance with the Four Opens and the other principles of OpenStack.  Since a team is self-organizing they could choose representation based on elections, a lottery system, a rotation schedule, or all cores who work for $VENDOR.  The TC would reject that last one as not in keeping with the diversity principle of OpenStack.","commit_id":"c942b0d7b19b10648ed02752363d36f2bd335e1c"},{"author":{"_account_id":16708,"name":"Kendall Nelson","display_name":"Kendall (diablo_rojo)","email":"kennelson11@gmail.com","username":"kjnelson"},"change_message_id":"01d08298b0b598c0ba8b159fd2b991516ffe94ae","unresolved":false,"context_lines":[{"line_number":21,"context_line":"project.  OpenStack projects have successfully managed to continue to work"},{"line_number":22,"context_line":"together following our four opens without needing much of a tie-breaker."},{"line_number":23,"context_line":""},{"line_number":24,"context_line":"It makes sense that the OpenStack projects no longer need to maintain a single"},{"line_number":25,"context_line":"individual who becomes a representative of the entire project at this point."},{"line_number":26,"context_line":"The projects should have their frameworks to decide how they want to continue"},{"line_number":27,"context_line":"to run the project amongst the contributors and core members."},{"line_number":28,"context_line":""},{"line_number":29,"context_line":"Teams should maintain a few (ideally) different individuals who act as"},{"line_number":30,"context_line":"liaisons to help ensure that specific objectives of OpenStack as a whole can"},{"line_number":31,"context_line":"continue; those roles are:"},{"line_number":32,"context_line":""},{"line_number":33,"context_line":"* Release liaison: works with Release management team to ensure that OpenStack"},{"line_number":34,"context_line":"  coordinated release happens successfully"}],"source_content_type":"text/x-rst","patch_set":4,"id":"1fa4df85_85a88b77","line":31,"range":{"start_line":24,"start_character":0,"end_line":31,"end_character":26},"in_reply_to":"1fa4df85_876f4a91","updated":"2020-03-14 00:20:27.000000000","message":"I also think having more than one option is going to get confusing for anyone new to the community trying to work on more than one project..","commit_id":"c942b0d7b19b10648ed02752363d36f2bd335e1c"},{"author":{"_account_id":1004,"name":"Mohammed Naser","email":"mnaser@vexxhost.com","username":"mnaser"},"change_message_id":"d08322cde707b20ada44e8c318e3e9d9ebcbfe30","unresolved":false,"context_lines":[{"line_number":21,"context_line":"project.  OpenStack projects have successfully managed to continue to work"},{"line_number":22,"context_line":"together following our four opens without needing much of a tie-breaker."},{"line_number":23,"context_line":""},{"line_number":24,"context_line":"It makes sense that the OpenStack projects no longer need to maintain a single"},{"line_number":25,"context_line":"individual who becomes a representative of the entire project at this point."},{"line_number":26,"context_line":"The projects should have their frameworks to decide how they want to continue"},{"line_number":27,"context_line":"to run the project amongst the contributors and core members."},{"line_number":28,"context_line":""},{"line_number":29,"context_line":"Teams should maintain a few (ideally) different individuals who act as"},{"line_number":30,"context_line":"liaisons to help ensure that specific objectives of OpenStack as a whole can"},{"line_number":31,"context_line":"continue; those roles are:"},{"line_number":32,"context_line":""},{"line_number":33,"context_line":"* Release liaison: works with Release management team to ensure that OpenStack"},{"line_number":34,"context_line":"  coordinated release happens successfully"}],"source_content_type":"text/x-rst","patch_set":4,"id":"1fa4df85_276c569b","line":31,"range":{"start_line":24,"start_character":0,"end_line":31,"end_character":26},"in_reply_to":"1fa4df85_a8181884","updated":"2020-03-12 16:31:38.000000000","message":"absolutely.  that\u0027s why I had the part at the end to make sure that if we see things ain\u0027t right, we can come in and get involved.","commit_id":"c942b0d7b19b10648ed02752363d36f2bd335e1c"},{"author":{"_account_id":11628,"name":"Michael Johnson","email":"johnsomor@gmail.com","username":"johnsom"},"change_message_id":"e936668dfbbe26628c8c2953cbc81de2c2018f87","unresolved":false,"context_lines":[{"line_number":36,"context_line":"  is set up and organize running the PTG in a conductive manner"},{"line_number":37,"context_line":"* Meeting chair: Run meetings and manage the agenda for the project"},{"line_number":38,"context_line":""},{"line_number":39,"context_line":"Those roles will not renew for specific periods, and contributors and core"},{"line_number":40,"context_line":"members of the projects will manage that list.  It\u0027s advised that these roles"},{"line_number":41,"context_line":"are rotated every release, but will not be enforced."},{"line_number":42,"context_line":""}],"source_content_type":"text/x-rst","patch_set":4,"id":"1fa4df85_60941d45","line":39,"range":{"start_line":39,"start_character":0,"end_line":39,"end_character":47},"updated":"2020-03-19 00:37:21.000000000","message":"This is another red flag for me.\nWith the current election system, there is a healthy opportunity for a change in direction for teams.\nStagnant leadership for projects creates silos and limits the ability for new community members to grow their role.","commit_id":"c942b0d7b19b10648ed02752363d36f2bd335e1c"},{"author":{"_account_id":11628,"name":"Michael Johnson","email":"johnsomor@gmail.com","username":"johnsom"},"change_message_id":"e936668dfbbe26628c8c2953cbc81de2c2018f87","unresolved":false,"context_lines":[{"line_number":36,"context_line":"  is set up and organize running the PTG in a conductive manner"},{"line_number":37,"context_line":"* Meeting chair: Run meetings and manage the agenda for the project"},{"line_number":38,"context_line":""},{"line_number":39,"context_line":"Those roles will not renew for specific periods, and contributors and core"},{"line_number":40,"context_line":"members of the projects will manage that list.  It\u0027s advised that these roles"},{"line_number":41,"context_line":"are rotated every release, but will not be enforced."},{"line_number":42,"context_line":""},{"line_number":43,"context_line":"If any team issues occur where the teams are not able to consolidate and come"}],"source_content_type":"text/x-rst","patch_set":4,"id":"1fa4df85_e0a00da8","line":40,"range":{"start_line":39,"start_character":49,"end_line":40,"end_character":46},"updated":"2020-03-19 00:37:21.000000000","message":"This is a concern. This is one of the primary roles of a PTL. The person responsible for approving changes to sensitive roles, structure, etc.\nWhen I was PTL in the past there were multiple occurrences where people outside the project team attempted to \"propose\" changes to the project structure, etc. that was caught by someone checking with the PTL before approving.\nMost of it was misunderstanding the community process, some was not.\nThis is a value to having an elected lead that can make the tough calls and be the point of contact for the team.","commit_id":"c942b0d7b19b10648ed02752363d36f2bd335e1c"},{"author":{"_account_id":9708,"name":"Balazs Gibizer","display_name":"gibi","email":"gibizer@gmail.com","username":"gibi"},"change_message_id":"8514bacc69f0699404a0143657b13afeed4d661b","unresolved":false,"context_lines":[{"line_number":36,"context_line":"  is set up and organize running the PTG in a conductive manner"},{"line_number":37,"context_line":"* Meeting chair: Run meetings and manage the agenda for the project"},{"line_number":38,"context_line":""},{"line_number":39,"context_line":"Those roles will not renew for specific periods, and contributors and core"},{"line_number":40,"context_line":"members of the projects will manage that list.  It\u0027s advised that these roles"},{"line_number":41,"context_line":"are rotated every release, but will not be enforced."},{"line_number":42,"context_line":""},{"line_number":43,"context_line":"If any team issues occur where the teams are not able to consolidate and come"}],"source_content_type":"text/x-rst","patch_set":4,"id":"1fa4df85_0934c4dd","line":40,"range":{"start_line":39,"start_character":48,"end_line":40,"end_character":46},"updated":"2020-03-13 08:45:43.000000000","message":"will they? who the TC will ping if such list is not up to date?","commit_id":"c942b0d7b19b10648ed02752363d36f2bd335e1c"}]}