)]}'
{"/COMMIT_MSG":[{"author":{"_account_id":13995,"name":"Nate Johnston","email":"nate.johnston@redhat.com","username":"natejohnston"},"change_message_id":"627d5fd7e5d669014b26fb5641380a1621cbc32e","unresolved":false,"context_lines":[{"line_number":12,"context_line":"held by a single individual."},{"line_number":13,"context_line":""},{"line_number":14,"context_line":"Change-Id: I183f616e66d13066cd91e2659e1e90f5d2798d69"},{"line_number":15,"context_line":"Co-Authored-By: Jean-Phillipe Evrard \u003cjean-philippe@evrard.me\u003e"}],"source_content_type":"text/x-gerrit-commit-message","patch_set":6,"id":"9f560f44_26d64829","line":15,"range":{"start_line":15,"start_character":0,"end_line":15,"end_character":36},"updated":"2020-08-11 15:41:15.000000000","message":"Huge apologies for the misspelling!","commit_id":"73207e50a34e3eb0bd263e2abc12aa69f597279c"},{"author":{"_account_id":17068,"name":"Jean-Philippe Evrard","email":"openstack@a.spamming.party","username":"evrardjp"},"change_message_id":"e3a2c9dececcf4d76241676d9dd224b3cc2aa36c","unresolved":false,"context_lines":[{"line_number":12,"context_line":"held by a single individual."},{"line_number":13,"context_line":""},{"line_number":14,"context_line":"Change-Id: I183f616e66d13066cd91e2659e1e90f5d2798d69"},{"line_number":15,"context_line":"Co-Authored-By: Jean-Phillipe Evrard \u003cjean-philippe@evrard.me\u003e"}],"source_content_type":"text/x-gerrit-commit-message","patch_set":6,"id":"9f560f44_948655db","line":15,"range":{"start_line":15,"start_character":0,"end_line":15,"end_character":36},"in_reply_to":"9f560f44_26d64829","updated":"2020-08-12 06:09:02.000000000","message":"Don\u0027t you worry :)","commit_id":"73207e50a34e3eb0bd263e2abc12aa69f597279c"}],"resolutions/20200803-distributed-project-leadership.rst":[{"author":{"_account_id":9708,"name":"Balazs Gibizer","display_name":"gibi","email":"gibizer@gmail.com","username":"gibi"},"change_message_id":"6f392b7be27f4f1050e3a375522ac5f53bb9b101","unresolved":false,"context_lines":[{"line_number":29,"context_line":""},{"line_number":30,"context_line":"Release liaison: The `_release liaison` is responsible for creating releases"},{"line_number":31,"context_line":"for an OpenStack project.  In addition, release liaisons review requests for"},{"line_number":32,"context_line":"Feature Freeze Exception (FFE)."},{"line_number":33,"context_line":""},{"line_number":34,"context_line":"tact-sig liaison: Historically named the \"infra Liaison\".  It is responsible for"},{"line_number":35,"context_line":"the health of the CI jobs run in the OpenStack Zuul CI.  In the event that there"}],"source_content_type":"text/x-rst","patch_set":3,"id":"9f560f44_f22d6efe","line":32,"updated":"2020-08-06 07:47:02.000000000","message":"* It this the role also who writes the cycle highlights marketing material as well?\n\n* Is this the role also who keeps the blueprint status, milestone targets, and other launchpad related things up to date and tidy?","commit_id":"87937fe5a12c9b5c032b68679bc990f7bb3ab853"},{"author":{"_account_id":17068,"name":"Jean-Philippe Evrard","email":"openstack@a.spamming.party","username":"evrardjp"},"change_message_id":"ce7fd97ce5829f722f75569b3deb30f2bbdf3b18","unresolved":false,"context_lines":[{"line_number":29,"context_line":""},{"line_number":30,"context_line":"Release liaison: The `_release liaison` is responsible for creating releases"},{"line_number":31,"context_line":"for an OpenStack project.  In addition, release liaisons review requests for"},{"line_number":32,"context_line":"Feature Freeze Exception (FFE)."},{"line_number":33,"context_line":""},{"line_number":34,"context_line":"tact-sig liaison: Historically named the \"infra Liaison\".  It is responsible for"},{"line_number":35,"context_line":"the health of the CI jobs run in the OpenStack Zuul CI.  In the event that there"}],"source_content_type":"text/x-rst","patch_set":3,"id":"9f560f44_7ea62ead","line":32,"in_reply_to":"9f560f44_4c10f6a8","updated":"2020-08-07 13:05:17.000000000","message":"I would prefer if the release liaison to keep a focus on the release duties. While cycle highlights could be indeed in there (and we should probably clarify it), the blueprint status and others listed here is not part of release liaison role, IMO. It\u0027s just fundamental things we have to do to deliver (and therefore release) software. We don\u0027t want to remove PTL so that release liaison is at the end the same thing as the PTL :) Let\u0027s distribute more and trust the teams\u0027 self-organisation.","commit_id":"87937fe5a12c9b5c032b68679bc990f7bb3ab853"},{"author":{"_account_id":9708,"name":"Balazs Gibizer","display_name":"gibi","email":"gibizer@gmail.com","username":"gibi"},"change_message_id":"54ea5f8989134fd06b385a7caa0f35a25518f68b","unresolved":false,"context_lines":[{"line_number":29,"context_line":""},{"line_number":30,"context_line":"Release liaison: The `_release liaison` is responsible for creating releases"},{"line_number":31,"context_line":"for an OpenStack project.  In addition, release liaisons review requests for"},{"line_number":32,"context_line":"Feature Freeze Exception (FFE)."},{"line_number":33,"context_line":""},{"line_number":34,"context_line":"tact-sig liaison: Historically named the \"infra Liaison\".  It is responsible for"},{"line_number":35,"context_line":"the health of the CI jobs run in the OpenStack Zuul CI.  In the event that there"}],"source_content_type":"text/x-rst","patch_set":3,"id":"9f560f44_efb3aae7","line":32,"in_reply_to":"9f560f44_798be866","updated":"2020-08-07 15:20:21.000000000","message":"\u003e If it\u0027s paperwork that\u0027s not blocking work, I guess one could argue\n \u003e \"why do we do it in the first place?\". I think things can evolve,\n\nThe benefit of a clean paperwork is not visible immediately but at a later time. For example when we want to have a fact based discussion about our current and past review bandwidth to plan the amount of accepted work for the future. Realizing at that point that we don\u0027t have past data is hard to fix retroactively.\n\n \u003e and if some teams need the paperwork, let\u0027s keep it. If some don\u0027t,\n \u003e good, let\u0027s get rid of it! We are all in this together, I hope we\n \u003e can communicate changes that a project has decided to go through.\n \u003e :)\n\nI\u0027m totally supportive to let every project decide how they organize themselves. If it is a conscious decision that they don\u0027t do that much paperwork then so be it. What I want to avoid is that we simply forget to do it even though we expect to have the data available later.","commit_id":"87937fe5a12c9b5c032b68679bc990f7bb3ab853"},{"author":{"_account_id":9708,"name":"Balazs Gibizer","display_name":"gibi","email":"gibizer@gmail.com","username":"gibi"},"change_message_id":"e109f877166d912a182c365025708745f1a12bff","unresolved":false,"context_lines":[{"line_number":29,"context_line":""},{"line_number":30,"context_line":"Release liaison: The `_release liaison` is responsible for creating releases"},{"line_number":31,"context_line":"for an OpenStack project.  In addition, release liaisons review requests for"},{"line_number":32,"context_line":"Feature Freeze Exception (FFE)."},{"line_number":33,"context_line":""},{"line_number":34,"context_line":"tact-sig liaison: Historically named the \"infra Liaison\".  It is responsible for"},{"line_number":35,"context_line":"the health of the CI jobs run in the OpenStack Zuul CI.  In the event that there"}],"source_content_type":"text/x-rst","patch_set":3,"id":"9f560f44_bec3a6ec","line":32,"in_reply_to":"9f560f44_7ea62ead","updated":"2020-08-07 13:18:56.000000000","message":"So if I understand correctly there are functions that the current PTLs are doing but in a distributed setup we are simply leaving them to the project team as a whole to fulfill. \n\nHonestly I doubt that launchpad management will be taken up by the project team in a self-organized way as this is mostly paper-work and if it is not done it does not cause immediate blockage of the ongoing work.\n\nThanks for adding the RFE coordinator optional role. I think that makes sure that the launchpad related work is not forgotten.","commit_id":"87937fe5a12c9b5c032b68679bc990f7bb3ab853"},{"author":{"_account_id":17068,"name":"Jean-Philippe Evrard","email":"openstack@a.spamming.party","username":"evrardjp"},"change_message_id":"9e3802f64134b1afaf536cc528f52c27e43d9807","unresolved":false,"context_lines":[{"line_number":29,"context_line":""},{"line_number":30,"context_line":"Release liaison: The `_release liaison` is responsible for creating releases"},{"line_number":31,"context_line":"for an OpenStack project.  In addition, release liaisons review requests for"},{"line_number":32,"context_line":"Feature Freeze Exception (FFE)."},{"line_number":33,"context_line":""},{"line_number":34,"context_line":"tact-sig liaison: Historically named the \"infra Liaison\".  It is responsible for"},{"line_number":35,"context_line":"the health of the CI jobs run in the OpenStack Zuul CI.  In the event that there"}],"source_content_type":"text/x-rst","patch_set":3,"id":"9f560f44_798be866","line":32,"in_reply_to":"9f560f44_bec3a6ec","updated":"2020-08-07 13:33:56.000000000","message":"If it\u0027s paperwork that\u0027s not blocking work, I guess one could argue \"why do we do it in the first place?\". I think things can evolve, and if some teams need the paperwork, let\u0027s keep it. If some don\u0027t, good, let\u0027s get rid of it! We are all in this together, I hope we can communicate changes that a project has decided to go through. :)","commit_id":"87937fe5a12c9b5c032b68679bc990f7bb3ab853"},{"author":{"_account_id":17068,"name":"Jean-Philippe Evrard","email":"openstack@a.spamming.party","username":"evrardjp"},"change_message_id":"d14aede7ad8027d66746a430be22a0c81edfda8c","unresolved":false,"context_lines":[{"line_number":29,"context_line":""},{"line_number":30,"context_line":"Release liaison: The `_release liaison` is responsible for creating releases"},{"line_number":31,"context_line":"for an OpenStack project.  In addition, release liaisons review requests for"},{"line_number":32,"context_line":"Feature Freeze Exception (FFE)."},{"line_number":33,"context_line":""},{"line_number":34,"context_line":"tact-sig liaison: Historically named the \"infra Liaison\".  It is responsible for"},{"line_number":35,"context_line":"the health of the CI jobs run in the OpenStack Zuul CI.  In the event that there"}],"source_content_type":"text/x-rst","patch_set":3,"id":"9f560f44_1db7253c","line":32,"in_reply_to":"9f560f44_efb3aae7","updated":"2020-08-10 09:20:30.000000000","message":"we totally agree there :)","commit_id":"87937fe5a12c9b5c032b68679bc990f7bb3ab853"},{"author":{"_account_id":13995,"name":"Nate Johnston","email":"nate.johnston@redhat.com","username":"natejohnston"},"change_message_id":"c680597c53d3c71e4b8b99177069d9cdcaa5796a","unresolved":false,"context_lines":[{"line_number":29,"context_line":""},{"line_number":30,"context_line":"Release liaison: The `_release liaison` is responsible for creating releases"},{"line_number":31,"context_line":"for an OpenStack project.  In addition, release liaisons review requests for"},{"line_number":32,"context_line":"Feature Freeze Exception (FFE)."},{"line_number":33,"context_line":""},{"line_number":34,"context_line":"tact-sig liaison: Historically named the \"infra Liaison\".  It is responsible for"},{"line_number":35,"context_line":"the health of the CI jobs run in the OpenStack Zuul CI.  In the event that there"}],"source_content_type":"text/x-rst","patch_set":3,"id":"9f560f44_4c10f6a8","line":32,"in_reply_to":"9f560f44_f22d6efe","updated":"2020-08-06 18:20:58.000000000","message":"A team could choose to expand the release liaison role to include those responsibilities, or create additional roles.  This document is intended to assert the minimum set of roles the TC would require to consider the project a functional going concern, but is not an exhaustive list of possible roles.  This was intended to be handled by the statement \"Any other responsibilities of the PTL that are not addressed in this document are left to the project teams to determine\" but I also added more to the list of optional roles.","commit_id":"87937fe5a12c9b5c032b68679bc990f7bb3ab853"},{"author":{"_account_id":9708,"name":"Balazs Gibizer","display_name":"gibi","email":"gibizer@gmail.com","username":"gibi"},"change_message_id":"6f392b7be27f4f1050e3a375522ac5f53bb9b101","unresolved":false,"context_lines":[{"line_number":41,"context_line":"the impact of any security reported issues for the project, coordinate the"},{"line_number":42,"context_line":"development of patches, review proposed patches, and propose any eventual"},{"line_number":43,"context_line":"backport(s)."},{"line_number":44,"context_line":""},{"line_number":45,"context_line":"Additional optional roles are:"},{"line_number":46,"context_line":""},{"line_number":47,"context_line":"Events liaison: An Events liaison ensures that a project has space reserved at a"}],"source_content_type":"text/x-rst","patch_set":3,"id":"9f560f44_32b1a6e2","line":44,"updated":"2020-08-06 07:47:02.000000000","message":"The PTL also making sure that incoming bugs are regularly triaged by the team.","commit_id":"87937fe5a12c9b5c032b68679bc990f7bb3ab853"},{"author":{"_account_id":17068,"name":"Jean-Philippe Evrard","email":"openstack@a.spamming.party","username":"evrardjp"},"change_message_id":"ce7fd97ce5829f722f75569b3deb30f2bbdf3b18","unresolved":false,"context_lines":[{"line_number":41,"context_line":"the impact of any security reported issues for the project, coordinate the"},{"line_number":42,"context_line":"development of patches, review proposed patches, and propose any eventual"},{"line_number":43,"context_line":"backport(s)."},{"line_number":44,"context_line":""},{"line_number":45,"context_line":"Additional optional roles are:"},{"line_number":46,"context_line":""},{"line_number":47,"context_line":"Events liaison: An Events liaison ensures that a project has space reserved at a"}],"source_content_type":"text/x-rst","patch_set":3,"id":"9f560f44_3ef7968d","line":44,"in_reply_to":"9f560f44_0c68be1a","updated":"2020-08-07 13:05:17.000000000","message":"I think that was my point: Neutron is proving there is a role for that, and it\u0027s rotating regularily. I definitely hope for the teams to self-organise, so that the bugs are indeed handled, not piling up and hidden under the bed.\n\nI consider the optional roles to _not be listed_ as governance role, but as a guideline of what the teams should keep in mind and do.","commit_id":"87937fe5a12c9b5c032b68679bc990f7bb3ab853"},{"author":{"_account_id":13995,"name":"Nate Johnston","email":"nate.johnston@redhat.com","username":"natejohnston"},"change_message_id":"c680597c53d3c71e4b8b99177069d9cdcaa5796a","unresolved":false,"context_lines":[{"line_number":41,"context_line":"the impact of any security reported issues for the project, coordinate the"},{"line_number":42,"context_line":"development of patches, review proposed patches, and propose any eventual"},{"line_number":43,"context_line":"backport(s)."},{"line_number":44,"context_line":""},{"line_number":45,"context_line":"Additional optional roles are:"},{"line_number":46,"context_line":""},{"line_number":47,"context_line":"Events liaison: An Events liaison ensures that a project has space reserved at a"}],"source_content_type":"text/x-rst","patch_set":3,"id":"9f560f44_0c68be1a","line":44,"in_reply_to":"9f560f44_32b1a6e2","updated":"2020-08-06 18:20:58.000000000","message":"\u003e The PTL also making sure that incoming bugs are regularly triaged\n \u003e by the team.\n\nSometimes; the Neutron rotating bug deputy is a counterexample.  Added to the list of possible roles.","commit_id":"87937fe5a12c9b5c032b68679bc990f7bb3ab853"},{"author":{"_account_id":17068,"name":"Jean-Philippe Evrard","email":"openstack@a.spamming.party","username":"evrardjp"},"change_message_id":"f7cad8acebbc8e847edfa6a5d00858aefd864ed6","unresolved":false,"context_lines":[{"line_number":41,"context_line":"the impact of any security reported issues for the project, coordinate the"},{"line_number":42,"context_line":"development of patches, review proposed patches, and propose any eventual"},{"line_number":43,"context_line":"backport(s)."},{"line_number":44,"context_line":""},{"line_number":45,"context_line":"Additional optional roles are:"},{"line_number":46,"context_line":""},{"line_number":47,"context_line":"Events liaison: An Events liaison ensures that a project has space reserved at a"}],"source_content_type":"text/x-rst","patch_set":3,"id":"9f560f44_b5f2c098","line":44,"in_reply_to":"9f560f44_32b1a6e2","updated":"2020-08-06 08:57:23.000000000","message":"That\u0027s true, that\u0027s a regular duty, which could be listend in optional. (Though that\u0027s kinda mandatory for the software itself!)","commit_id":"87937fe5a12c9b5c032b68679bc990f7bb3ab853"},{"author":{"_account_id":9708,"name":"Balazs Gibizer","display_name":"gibi","email":"gibizer@gmail.com","username":"gibi"},"change_message_id":"6f392b7be27f4f1050e3a375522ac5f53bb9b101","unresolved":false,"context_lines":[{"line_number":49,"context_line":"needs. The events liaison puts out an agenda for any of the project meetings."},{"line_number":50,"context_line":"This is a temporary role, lasting only during the preparation time for the event"},{"line_number":51,"context_line":"and it\u0027s duration.  Due to the temporary aspect of this role, the liaison will"},{"line_number":52,"context_line":"not be recorded in governance, else it might quickly get outdated."},{"line_number":53,"context_line":""},{"line_number":54,"context_line":"In order for the OpenStack Events teams to know who to contact, every project"},{"line_number":55,"context_line":"adhering to the \"PTL-less\" model should opt in to an event. This means the"}],"source_content_type":"text/x-rst","patch_set":3,"id":"9f560f44_f291ee48","line":52,"updated":"2020-08-06 07:47:02.000000000","message":"Is it the Event liaison that makes sure the PTG discussions are origanized, facilitated, and results are documented? Or is it the regular Meeting Facilitator role?","commit_id":"87937fe5a12c9b5c032b68679bc990f7bb3ab853"},{"author":{"_account_id":13995,"name":"Nate Johnston","email":"nate.johnston@redhat.com","username":"natejohnston"},"change_message_id":"c680597c53d3c71e4b8b99177069d9cdcaa5796a","unresolved":false,"context_lines":[{"line_number":49,"context_line":"needs. The events liaison puts out an agenda for any of the project meetings."},{"line_number":50,"context_line":"This is a temporary role, lasting only during the preparation time for the event"},{"line_number":51,"context_line":"and it\u0027s duration.  Due to the temporary aspect of this role, the liaison will"},{"line_number":52,"context_line":"not be recorded in governance, else it might quickly get outdated."},{"line_number":53,"context_line":""},{"line_number":54,"context_line":"In order for the OpenStack Events teams to know who to contact, every project"},{"line_number":55,"context_line":"adhering to the \"PTL-less\" model should opt in to an event. This means the"}],"source_content_type":"text/x-rst","patch_set":3,"id":"9f560f44_6cd05aca","line":52,"in_reply_to":"9f560f44_95edfcb8","updated":"2020-08-06 18:20:58.000000000","message":"Clarified.","commit_id":"87937fe5a12c9b5c032b68679bc990f7bb3ab853"},{"author":{"_account_id":17068,"name":"Jean-Philippe Evrard","email":"openstack@a.spamming.party","username":"evrardjp"},"change_message_id":"f7cad8acebbc8e847edfa6a5d00858aefd864ed6","unresolved":false,"context_lines":[{"line_number":49,"context_line":"needs. The events liaison puts out an agenda for any of the project meetings."},{"line_number":50,"context_line":"This is a temporary role, lasting only during the preparation time for the event"},{"line_number":51,"context_line":"and it\u0027s duration.  Due to the temporary aspect of this role, the liaison will"},{"line_number":52,"context_line":"not be recorded in governance, else it might quickly get outdated."},{"line_number":53,"context_line":""},{"line_number":54,"context_line":"In order for the OpenStack Events teams to know who to contact, every project"},{"line_number":55,"context_line":"adhering to the \"PTL-less\" model should opt in to an event. This means the"}],"source_content_type":"text/x-rst","patch_set":3,"id":"9f560f44_95edfcb8","line":52,"in_reply_to":"9f560f44_f291ee48","updated":"2020-08-06 08:57:23.000000000","message":"That should indeed be clarified. IMO the Events liaison ensure the team has a space, and can indeed help on organising the PTG discussions, facilitate them, and document them.","commit_id":"87937fe5a12c9b5c032b68679bc990f7bb3ab853"},{"author":{"_account_id":11975,"name":"Slawek Kaplonski","email":"skaplons@redhat.com","username":"slaweq"},"change_message_id":"a279091eee606b52f8db204408991377abf03b2d","unresolved":false,"context_lines":[{"line_number":57,"context_line":"person for a certain event, and that person shall contact the OpenStack events"},{"line_number":58,"context_line":"team as a representative of project \"x\"."},{"line_number":59,"context_line":""},{"line_number":60,"context_line":"Project Update/Onboarding liaisons: The Project Update lLiaison is responsible"},{"line_number":61,"context_line":"for giving the project update showcasing project achievements for the cycle to"},{"line_number":62,"context_line":"the community. The \"Project Onboarding\" liaison is responsible for"},{"line_number":63,"context_line":"giving/facilitating onboarding sessions during events for its projects\u0027"}],"source_content_type":"text/x-rst","patch_set":3,"id":"9f560f44_b26c969c","line":60,"range":{"start_line":60,"start_character":55,"end_line":60,"end_character":56},"updated":"2020-08-06 07:19:25.000000000","message":"nitty nit: not needed","commit_id":"87937fe5a12c9b5c032b68679bc990f7bb3ab853"},{"author":{"_account_id":13995,"name":"Nate Johnston","email":"nate.johnston@redhat.com","username":"natejohnston"},"change_message_id":"c680597c53d3c71e4b8b99177069d9cdcaa5796a","unresolved":false,"context_lines":[{"line_number":57,"context_line":"person for a certain event, and that person shall contact the OpenStack events"},{"line_number":58,"context_line":"team as a representative of project \"x\"."},{"line_number":59,"context_line":""},{"line_number":60,"context_line":"Project Update/Onboarding liaisons: The Project Update lLiaison is responsible"},{"line_number":61,"context_line":"for giving the project update showcasing project achievements for the cycle to"},{"line_number":62,"context_line":"the community. The \"Project Onboarding\" liaison is responsible for"},{"line_number":63,"context_line":"giving/facilitating onboarding sessions during events for its projects\u0027"}],"source_content_type":"text/x-rst","patch_set":3,"id":"9f560f44_4cd3d6d5","line":60,"range":{"start_line":60,"start_character":55,"end_line":60,"end_character":56},"in_reply_to":"9f560f44_b26c969c","updated":"2020-08-06 18:20:58.000000000","message":"Done","commit_id":"87937fe5a12c9b5c032b68679bc990f7bb3ab853"},{"author":{"_account_id":11975,"name":"Slawek Kaplonski","email":"skaplons@redhat.com","username":"slaweq"},"change_message_id":"a279091eee606b52f8db204408991377abf03b2d","unresolved":false,"context_lines":[{"line_number":71,"context_line":"decisions, with polls or elections when consensus can not be reached."},{"line_number":72,"context_line":""},{"line_number":73,"context_line":"Any other responsibilities of the PTL that are not addressed in this document"},{"line_number":74,"context_line":"are left tot he project teams to determine."},{"line_number":75,"context_line":""},{"line_number":76,"context_line":"Points of Concern"},{"line_number":77,"context_line":"-----------------"}],"source_content_type":"text/x-rst","patch_set":3,"id":"9f560f44_d20aeacf","line":74,"range":{"start_line":74,"start_character":9,"end_line":74,"end_character":15},"updated":"2020-08-06 07:19:25.000000000","message":"another nitty nit :)","commit_id":"87937fe5a12c9b5c032b68679bc990f7bb3ab853"},{"author":{"_account_id":13995,"name":"Nate Johnston","email":"nate.johnston@redhat.com","username":"natejohnston"},"change_message_id":"c680597c53d3c71e4b8b99177069d9cdcaa5796a","unresolved":false,"context_lines":[{"line_number":71,"context_line":"decisions, with polls or elections when consensus can not be reached."},{"line_number":72,"context_line":""},{"line_number":73,"context_line":"Any other responsibilities of the PTL that are not addressed in this document"},{"line_number":74,"context_line":"are left tot he project teams to determine."},{"line_number":75,"context_line":""},{"line_number":76,"context_line":"Points of Concern"},{"line_number":77,"context_line":"-----------------"}],"source_content_type":"text/x-rst","patch_set":3,"id":"9f560f44_acdd52e1","line":74,"range":{"start_line":74,"start_character":9,"end_line":74,"end_character":15},"in_reply_to":"9f560f44_d20aeacf","updated":"2020-08-06 18:20:58.000000000","message":"Done","commit_id":"87937fe5a12c9b5c032b68679bc990f7bb3ab853"},{"author":{"_account_id":11975,"name":"Slawek Kaplonski","email":"skaplons@redhat.com","username":"slaweq"},"change_message_id":"a279091eee606b52f8db204408991377abf03b2d","unresolved":false,"context_lines":[{"line_number":81,"context_line":""},{"line_number":82,"context_line":"* Discoverability: It won\u0027t always be easy to know who to contact for a project."},{"line_number":83,"context_line":"* Distributed Consensus: With an increased number of people accountable for"},{"line_number":84,"context_line":"  aspects of the project, the potential for miscommunications increases.  "},{"line_number":85,"context_line":"* Inclusion: Since some of the liaisons will not be explicitly written in code -"},{"line_number":86,"context_line":"  like the events liaisons - the project team members will need to actively"},{"line_number":87,"context_line":"  contact the OpenStack events team. In other words, we\u0027ll also introduce an opt"}],"source_content_type":"text/x-rst","patch_set":3,"id":"9f560f44_7224be5e","line":84,"range":{"start_line":84,"start_character":72,"end_line":84,"end_character":74},"updated":"2020-08-06 07:19:25.000000000","message":"nitty nit: trailing spaces","commit_id":"87937fe5a12c9b5c032b68679bc990f7bb3ab853"},{"author":{"_account_id":13995,"name":"Nate Johnston","email":"nate.johnston@redhat.com","username":"natejohnston"},"change_message_id":"c680597c53d3c71e4b8b99177069d9cdcaa5796a","unresolved":false,"context_lines":[{"line_number":81,"context_line":""},{"line_number":82,"context_line":"* Discoverability: It won\u0027t always be easy to know who to contact for a project."},{"line_number":83,"context_line":"* Distributed Consensus: With an increased number of people accountable for"},{"line_number":84,"context_line":"  aspects of the project, the potential for miscommunications increases.  "},{"line_number":85,"context_line":"* Inclusion: Since some of the liaisons will not be explicitly written in code -"},{"line_number":86,"context_line":"  like the events liaisons - the project team members will need to actively"},{"line_number":87,"context_line":"  contact the OpenStack events team. In other words, we\u0027ll also introduce an opt"}],"source_content_type":"text/x-rst","patch_set":3,"id":"9f560f44_e7fc853f","line":84,"range":{"start_line":84,"start_character":72,"end_line":84,"end_character":74},"in_reply_to":"9f560f44_7224be5e","updated":"2020-08-06 18:20:58.000000000","message":"Done","commit_id":"87937fe5a12c9b5c032b68679bc990f7bb3ab853"},{"author":{"_account_id":11975,"name":"Slawek Kaplonski","email":"skaplons@redhat.com","username":"slaweq"},"change_message_id":"a279091eee606b52f8db204408991377abf03b2d","unresolved":false,"context_lines":[{"line_number":108,"context_line":""},{"line_number":109,"context_line":"A project may change their opt-in status only once a release cycle, to ensure"},{"line_number":110,"context_line":"that the elections officials have clarity on which projects need PTL elections."},{"line_number":111,"context_line":"All requests should be recieved by week R-5 of the release calendar."},{"line_number":112,"context_line":""},{"line_number":113,"context_line":".. _release liaison: https://opendev.org/openstack/releases/src/branch/master/data/release_liaisons.yaml"},{"line_number":114,"context_line":".. _TaCT SIG: https://governance.openstack.org/sigs/tact-sig.html "}],"source_content_type":"text/x-rst","patch_set":3,"id":"9f560f44_122aa22a","line":111,"updated":"2020-08-06 07:19:25.000000000","message":"what about the case when e.g. project will not request change to distributed ptl model but there will no be any candidate for ptl for next cycle? Will it be automatically switched to the distributed mode?","commit_id":"87937fe5a12c9b5c032b68679bc990f7bb3ab853"},{"author":{"_account_id":17068,"name":"Jean-Philippe Evrard","email":"openstack@a.spamming.party","username":"evrardjp"},"change_message_id":"f7cad8acebbc8e847edfa6a5d00858aefd864ed6","unresolved":false,"context_lines":[{"line_number":108,"context_line":""},{"line_number":109,"context_line":"A project may change their opt-in status only once a release cycle, to ensure"},{"line_number":110,"context_line":"that the elections officials have clarity on which projects need PTL elections."},{"line_number":111,"context_line":"All requests should be recieved by week R-5 of the release calendar."},{"line_number":112,"context_line":""},{"line_number":113,"context_line":".. _release liaison: https://opendev.org/openstack/releases/src/branch/master/data/release_liaisons.yaml"},{"line_number":114,"context_line":".. _TaCT SIG: https://governance.openstack.org/sigs/tact-sig.html "}],"source_content_type":"text/x-rst","patch_set":3,"id":"9f560f44_d5f5b458","line":111,"in_reply_to":"9f560f44_122aa22a","updated":"2020-08-06 08:57:23.000000000","message":"I thought this could be settled in a follow up commit, but I am fine if we determine that now.\n\nI am not sure it\u0027s the right idea to have an \"automatic\" migration. As some roles are pretty much mandatory, I would prefer the projects to _actively_ say thay want to migrate. At the opposite side of that coin, if the team is not interested by this migration and don\u0027t have a PTL, we should be phasing out the team and its deliverables instead.\n\nOfc, I can change my mind :)","commit_id":"87937fe5a12c9b5c032b68679bc990f7bb3ab853"},{"author":{"_account_id":17068,"name":"Jean-Philippe Evrard","email":"openstack@a.spamming.party","username":"evrardjp"},"change_message_id":"ce7fd97ce5829f722f75569b3deb30f2bbdf3b18","unresolved":false,"context_lines":[{"line_number":108,"context_line":""},{"line_number":109,"context_line":"A project may change their opt-in status only once a release cycle, to ensure"},{"line_number":110,"context_line":"that the elections officials have clarity on which projects need PTL elections."},{"line_number":111,"context_line":"All requests should be recieved by week R-5 of the release calendar."},{"line_number":112,"context_line":""},{"line_number":113,"context_line":".. _release liaison: https://opendev.org/openstack/releases/src/branch/master/data/release_liaisons.yaml"},{"line_number":114,"context_line":".. _TaCT SIG: https://governance.openstack.org/sigs/tact-sig.html "}],"source_content_type":"text/x-rst","patch_set":3,"id":"9f560f44_de2dbafe","line":111,"in_reply_to":"9f560f44_47a1f145","updated":"2020-08-07 13:05:17.000000000","message":"Thanks, I agree with that.","commit_id":"87937fe5a12c9b5c032b68679bc990f7bb3ab853"},{"author":{"_account_id":13995,"name":"Nate Johnston","email":"nate.johnston@redhat.com","username":"natejohnston"},"change_message_id":"c680597c53d3c71e4b8b99177069d9cdcaa5796a","unresolved":false,"context_lines":[{"line_number":108,"context_line":""},{"line_number":109,"context_line":"A project may change their opt-in status only once a release cycle, to ensure"},{"line_number":110,"context_line":"that the elections officials have clarity on which projects need PTL elections."},{"line_number":111,"context_line":"All requests should be recieved by week R-5 of the release calendar."},{"line_number":112,"context_line":""},{"line_number":113,"context_line":".. _release liaison: https://opendev.org/openstack/releases/src/branch/master/data/release_liaisons.yaml"},{"line_number":114,"context_line":".. _TaCT SIG: https://governance.openstack.org/sigs/tact-sig.html "}],"source_content_type":"text/x-rst","patch_set":3,"id":"9f560f44_47a1f145","line":111,"in_reply_to":"9f560f44_d5f5b458","updated":"2020-08-06 18:20:58.000000000","message":"If a project has a PTL and there is no candidate for PTL then the previous process holds: it goes to the TC to decide.  I think the TC would work with the project team to determine which of the options would work best: an appointed PTL, a change to the distributed leadership model, or deprecation.  I added a paragraph at the end to make that explicit.","commit_id":"87937fe5a12c9b5c032b68679bc990f7bb3ab853"},{"author":{"_account_id":7198,"name":"Jay Bryant","email":"jungleboyj@electronicjungle.net","username":"jsbryant"},"change_message_id":"603680ebcbe6e4d451d1ee86e4a90741abf559d6","unresolved":false,"context_lines":[{"line_number":4,"context_line":""},{"line_number":5,"context_line":"The governing structure for OpenStack projects has long been for a Project"},{"line_number":6,"context_line":"Technical Lead (PTL) to be elected to serve as a singular focus for that"},{"line_number":7,"context_line":"project.  While the PTL role varies significantly from project to project, the"},{"line_number":8,"context_line":"PTL has many responsibilities for managing the development and release process"},{"line_number":9,"context_line":"for a project as well as representing the project both internally and"},{"line_number":10,"context_line":"externally.  This resolution outlines a process for OpenStack projects to opt in"},{"line_number":11,"context_line":"to a \"distributed leadership\" model where there is no PTL. The responsibilities"}],"source_content_type":"text/x-rst","patch_set":4,"id":"9f560f44_dd066e20","line":8,"range":{"start_line":7,"start_character":75,"end_line":8,"end_character":29},"updated":"2020-08-07 16:52:23.000000000","message":"This is awkwardly worded.  Maybe say \u0027PTL\u0027s across all projects have responsibilities ... \u0027","commit_id":"f4171ef23bd04eb1476e28dffc8cedcd481b2463"},{"author":{"_account_id":7198,"name":"Jay Bryant","email":"jungleboyj@electronicjungle.net","username":"jsbryant"},"change_message_id":"603680ebcbe6e4d451d1ee86e4a90741abf559d6","unresolved":false,"context_lines":[{"line_number":31,"context_line":"for an OpenStack project.  In addition, release liaisons review requests for"},{"line_number":32,"context_line":"Feature Freeze Exception (FFE)."},{"line_number":33,"context_line":""},{"line_number":34,"context_line":"tact-sig liaison: Historically named the \"infra Liaison\".  It is responsible for"},{"line_number":35,"context_line":"the health of the CI jobs run in the OpenStack Zuul CI.  In the event that there"},{"line_number":36,"context_line":"is an issue with those jobs, this liaison will be a point of contact for the"},{"line_number":37,"context_line":"`_TaCT SIG`.  Also, a +1 from at least one tact-sig liaison will be required"}],"source_content_type":"text/x-rst","patch_set":4,"id":"9f560f44_6e65dbb4","line":34,"range":{"start_line":34,"start_character":59,"end_line":34,"end_character":61},"updated":"2020-08-07 16:52:23.000000000","message":"This person","commit_id":"f4171ef23bd04eb1476e28dffc8cedcd481b2463"},{"author":{"_account_id":7198,"name":"Jay Bryant","email":"jungleboyj@electronicjungle.net","username":"jsbryant"},"change_message_id":"603680ebcbe6e4d451d1ee86e4a90741abf559d6","unresolved":false,"context_lines":[{"line_number":55,"context_line":""},{"line_number":56,"context_line":"In order for the OpenStack Events teams to know who to contact, every project"},{"line_number":57,"context_line":"adhering to the \"PTL-less\" model should opt in to an event. This means the"},{"line_number":58,"context_line":"team members will need organise themselves, decide who will be the contact"},{"line_number":59,"context_line":"person for a certain event, and that person shall contact the OpenStack events"},{"line_number":60,"context_line":"team as a representative of project \"x\"."},{"line_number":61,"context_line":""}],"source_content_type":"text/x-rst","patch_set":4,"id":"9f560f44_8e302fa1","line":58,"range":{"start_line":58,"start_character":18,"end_line":58,"end_character":31},"updated":"2020-08-07 16:52:23.000000000","message":"need to organize","commit_id":"f4171ef23bd04eb1476e28dffc8cedcd481b2463"},{"author":{"_account_id":7198,"name":"Jay Bryant","email":"jungleboyj@electronicjungle.net","username":"jsbryant"},"change_message_id":"603680ebcbe6e4d451d1ee86e4a90741abf559d6","unresolved":false,"context_lines":[{"line_number":70,"context_line":""},{"line_number":71,"context_line":"Bug Deputy: Ensures all incoming bugs are triaged."},{"line_number":72,"context_line":""},{"line_number":73,"context_line":"RFE Coordinator: This role would involve making sure that blueprint status and"},{"line_number":74,"context_line":"milestone targets are up to date, that RFEs are triaged and discussed before"},{"line_number":75,"context_line":"acceptance, and that the tracking LaunchPad or Storyboard items for RFEs are"},{"line_number":76,"context_line":"properly managed."}],"source_content_type":"text/x-rst","patch_set":4,"id":"9f560f44_2e15a3e5","line":73,"range":{"start_line":73,"start_character":0,"end_line":73,"end_character":3},"updated":"2020-08-07 16:52:23.000000000","message":"Should specify what \u0027RFE\u0027 stands for for people who aren\u0027t familiar with it.","commit_id":"f4171ef23bd04eb1476e28dffc8cedcd481b2463"},{"author":{"_account_id":17068,"name":"Jean-Philippe Evrard","email":"openstack@a.spamming.party","username":"evrardjp"},"change_message_id":"ff02a0a8b4cd9c4b79808d05a8c85685c385d7e1","unresolved":false,"context_lines":[{"line_number":79,"context_line":"discretion of the project teams.  The TC advocates the use of consensus"},{"line_number":80,"context_line":"decisions, with polls or elections when consensus can not be reached."},{"line_number":81,"context_line":""},{"line_number":82,"context_line":"Any other responsibilities of the PTL that are not addressed in this document"},{"line_number":83,"context_line":"are left to the project teams to determine."},{"line_number":84,"context_line":""},{"line_number":85,"context_line":"Points of Concern"},{"line_number":86,"context_line":"-----------------"}],"source_content_type":"text/x-rst","patch_set":4,"id":"9f560f44_196f4cc5","line":83,"range":{"start_line":82,"start_character":0,"end_line":83,"end_character":43},"updated":"2020-08-07 13:29:30.000000000","message":"What do you think of using this text as an introduction for the \"optional roles\" (L45), and clarify that it\u0027s recommended for projects to have people assigned to \"the following roles\" (current L47-81)?\n\nI think it clarifies what\u0027s necessary from the TC perspective to consider a project as \"functional enough\", while it is clear that many of those roles are up to the teams\u0027 self-organisation.","commit_id":"f4171ef23bd04eb1476e28dffc8cedcd481b2463"},{"author":{"_account_id":13995,"name":"Nate Johnston","email":"nate.johnston@redhat.com","username":"natejohnston"},"change_message_id":"daae87b5abf8787fc93e9e2cc460b7f62204e6dd","unresolved":false,"context_lines":[{"line_number":79,"context_line":"discretion of the project teams.  The TC advocates the use of consensus"},{"line_number":80,"context_line":"decisions, with polls or elections when consensus can not be reached."},{"line_number":81,"context_line":""},{"line_number":82,"context_line":"Any other responsibilities of the PTL that are not addressed in this document"},{"line_number":83,"context_line":"are left to the project teams to determine."},{"line_number":84,"context_line":""},{"line_number":85,"context_line":"Points of Concern"},{"line_number":86,"context_line":"-----------------"}],"source_content_type":"text/x-rst","patch_set":4,"id":"9f560f44_d93954a4","line":83,"range":{"start_line":82,"start_character":0,"end_line":83,"end_character":43},"in_reply_to":"9f560f44_196f4cc5","updated":"2020-08-07 13:37:00.000000000","message":"I think that is a good idea","commit_id":"f4171ef23bd04eb1476e28dffc8cedcd481b2463"},{"author":{"_account_id":7198,"name":"Jay Bryant","email":"jungleboyj@electronicjungle.net","username":"jsbryant"},"change_message_id":"603680ebcbe6e4d451d1ee86e4a90741abf559d6","unresolved":false,"context_lines":[{"line_number":132,"context_line":"the distributed project leadership model."},{"line_number":133,"context_line":""},{"line_number":134,"context_line":".. _release liaison: https://opendev.org/openstack/releases/src/branch/master/data/release_liaisons.yaml"},{"line_number":135,"context_line":".. _TaCT SIG: https://governance.openstack.org/sigs/tact-sig.html "},{"line_number":136,"context_line":".. _project_config repository: https://opendev.org/openstack/project-config"}],"source_content_type":"text/x-rst","patch_set":4,"id":"9f560f44_2eeac3d6","line":135,"range":{"start_line":135,"start_character":65,"end_line":135,"end_character":66},"updated":"2020-08-07 16:52:23.000000000","message":"Trailing space.  :-)","commit_id":"f4171ef23bd04eb1476e28dffc8cedcd481b2463"},{"author":{"_account_id":8556,"name":"Ghanshyam Maan","display_name":"Ghanshyam Maan","email":"gmaan.os14@gmail.com","username":"ghanshyam"},"change_message_id":"cf16c76a4583830e90ea066ee04a8a2aa9541b72","unresolved":false,"context_lines":[{"line_number":24,"context_line":"The day to day responsibilities of the PTL have been broken down into the"},{"line_number":25,"context_line":"following roles. Not all roles are required for the minimal viable health of a"},{"line_number":26,"context_line":"project. All these roles can be distributed amongst one or more individuals."},{"line_number":27,"context_line":""},{"line_number":28,"context_line":"Required roles"},{"line_number":29,"context_line":"~~~~~~~~~~~~~~"},{"line_number":30,"context_line":""}],"source_content_type":"text/x-rst","patch_set":5,"id":"9f560f44_2af2a69a","line":27,"range":{"start_line":27,"start_character":0,"end_line":27,"end_character":0},"updated":"2020-08-08 22:03:20.000000000","message":"we should clearly mention how this is different and give benefits than the current way of \"PTL\u0027s duties delegation\"[1], otherwise, it is confusing for projects already have the duties delegation or planning to do.\n\n[1] https://docs.openstack.org/project-team-guide/ptl.html#how-to-successfully-delegate","commit_id":"da73395092a72f623638d87ea4684d2c12baa65d"},{"author":{"_account_id":13995,"name":"Nate Johnston","email":"nate.johnston@redhat.com","username":"natejohnston"},"change_message_id":"f433550f28a00d6e24e4390a8fb0ba9ab5bcb80a","unresolved":false,"context_lines":[{"line_number":24,"context_line":"The day to day responsibilities of the PTL have been broken down into the"},{"line_number":25,"context_line":"following roles. Not all roles are required for the minimal viable health of a"},{"line_number":26,"context_line":"project. All these roles can be distributed amongst one or more individuals."},{"line_number":27,"context_line":""},{"line_number":28,"context_line":"Required roles"},{"line_number":29,"context_line":"~~~~~~~~~~~~~~"},{"line_number":30,"context_line":""}],"source_content_type":"text/x-rst","patch_set":5,"id":"9f560f44_ec1441eb","line":27,"range":{"start_line":27,"start_character":0,"end_line":27,"end_character":0},"in_reply_to":"9f560f44_2af2a69a","updated":"2020-08-10 14:52:59.000000000","message":"I will add a section above this drawing a comparison between the \"PTL only\" model, a \"PTL + liaisons\" model, and a \"liaisons only\" model i.e. distributed leadership.","commit_id":"da73395092a72f623638d87ea4684d2c12baa65d"},{"author":{"_account_id":13252,"name":"Dr. Jens Harbott","display_name":"Jens Harbott (frickler)","email":"frickler@offenerstapel.de","username":"jrosenboom"},"change_message_id":"fb053252924f8e3cc66c7063e8d3aeb3777004b7","unresolved":false,"context_lines":[{"line_number":38,"context_line":"  the health of the CI jobs run in the OpenStack Zuul CI.  In the event that there"},{"line_number":39,"context_line":"  is an issue with those jobs, this liaison will be a point of contact for the"},{"line_number":40,"context_line":"  `TaCT SIG`_.  Also, a +1 from at least one tact-sig liaison will be required"},{"line_number":41,"context_line":"  for changes in the `project_config repository`_."},{"line_number":42,"context_line":"* Security liaison: the security liaison is the contact person to help assessing"},{"line_number":43,"context_line":"  the impact of any security reported issues for the project, coordinate the"},{"line_number":44,"context_line":"  development of patches, review proposed patches, and propose any eventual"}],"source_content_type":"text/x-rst","patch_set":5,"id":"9f560f44_4f061654","line":41,"updated":"2020-08-07 15:30:04.000000000","message":"Where will these liaisons be documented? Would be good to have a reference here from an project-config reviewer pov.","commit_id":"da73395092a72f623638d87ea4684d2c12baa65d"},{"author":{"_account_id":13995,"name":"Nate Johnston","email":"nate.johnston@redhat.com","username":"natejohnston"},"change_message_id":"f433550f28a00d6e24e4390a8fb0ba9ab5bcb80a","unresolved":false,"context_lines":[{"line_number":38,"context_line":"  the health of the CI jobs run in the OpenStack Zuul CI.  In the event that there"},{"line_number":39,"context_line":"  is an issue with those jobs, this liaison will be a point of contact for the"},{"line_number":40,"context_line":"  `TaCT SIG`_.  Also, a +1 from at least one tact-sig liaison will be required"},{"line_number":41,"context_line":"  for changes in the `project_config repository`_."},{"line_number":42,"context_line":"* Security liaison: the security liaison is the contact person to help assessing"},{"line_number":43,"context_line":"  the impact of any security reported issues for the project, coordinate the"},{"line_number":44,"context_line":"  development of patches, review proposed patches, and propose any eventual"}],"source_content_type":"text/x-rst","patch_set":5,"id":"9f560f44_2ca639c2","line":41,"in_reply_to":"9f560f44_1d01e5af","updated":"2020-08-10 14:52:59.000000000","message":"This begs the question - where should the liaisons be documented?  Do all required liaison assignments need to be in the same file, or can they be in areas related to their function like the release liaison list is now?\n\nI am genuinely not sure of the best answer.","commit_id":"da73395092a72f623638d87ea4684d2c12baa65d"},{"author":{"_account_id":17068,"name":"Jean-Philippe Evrard","email":"openstack@a.spamming.party","username":"evrardjp"},"change_message_id":"93e0c8388d4429d9678e27bab5a77947fa269ef5","unresolved":false,"context_lines":[{"line_number":38,"context_line":"  the health of the CI jobs run in the OpenStack Zuul CI.  In the event that there"},{"line_number":39,"context_line":"  is an issue with those jobs, this liaison will be a point of contact for the"},{"line_number":40,"context_line":"  `TaCT SIG`_.  Also, a +1 from at least one tact-sig liaison will be required"},{"line_number":41,"context_line":"  for changes in the `project_config repository`_."},{"line_number":42,"context_line":"* Security liaison: the security liaison is the contact person to help assessing"},{"line_number":43,"context_line":"  the impact of any security reported issues for the project, coordinate the"},{"line_number":44,"context_line":"  development of patches, review proposed patches, and propose any eventual"}],"source_content_type":"text/x-rst","patch_set":5,"id":"9f560f44_1d01e5af","line":41,"in_reply_to":"9f560f44_4f061654","updated":"2020-08-10 09:38:10.000000000","message":"We should indeed mention the projects.yaml impact somewhere.","commit_id":"da73395092a72f623638d87ea4684d2c12baa65d"},{"author":{"_account_id":8556,"name":"Ghanshyam Maan","display_name":"Ghanshyam Maan","email":"gmaan.os14@gmail.com","username":"ghanshyam"},"change_message_id":"cf16c76a4583830e90ea066ee04a8a2aa9541b72","unresolved":false,"context_lines":[{"line_number":43,"context_line":"  the impact of any security reported issues for the project, coordinate the"},{"line_number":44,"context_line":"  development of patches, review proposed patches, and propose any eventual"},{"line_number":45,"context_line":"  backport(s)."},{"line_number":46,"context_line":""},{"line_number":47,"context_line":"Additional recommended roles"},{"line_number":48,"context_line":"~~~~~~~~~~~~~~~~~~~~~~~~~~~~"},{"line_number":49,"context_line":""}],"source_content_type":"text/x-rst","patch_set":5,"id":"9f560f44_6a2dbefc","line":46,"range":{"start_line":46,"start_character":0,"end_line":46,"end_character":0},"updated":"2020-08-08 22:03:20.000000000","message":"we need TC liaison also in mandatory roles so that TC can have a single point of contact.","commit_id":"da73395092a72f623638d87ea4684d2c12baa65d"},{"author":{"_account_id":13995,"name":"Nate Johnston","email":"nate.johnston@redhat.com","username":"natejohnston"},"change_message_id":"f8abaff498e4530df38c66d768f56f8bdda4b84f","unresolved":false,"context_lines":[{"line_number":43,"context_line":"  the impact of any security reported issues for the project, coordinate the"},{"line_number":44,"context_line":"  development of patches, review proposed patches, and propose any eventual"},{"line_number":45,"context_line":"  backport(s)."},{"line_number":46,"context_line":""},{"line_number":47,"context_line":"Additional recommended roles"},{"line_number":48,"context_line":"~~~~~~~~~~~~~~~~~~~~~~~~~~~~"},{"line_number":49,"context_line":""}],"source_content_type":"text/x-rst","patch_set":5,"id":"9f560f44_c0cbef47","line":46,"range":{"start_line":46,"start_character":0,"end_line":46,"end_character":0},"in_reply_to":"9f560f44_2692c84c","updated":"2020-08-11 20:03:15.000000000","message":"I would prefer that instead of contacting a single person we contact all of the people listed as mandatory liaisons.  I hold this position for two complementary reasons:\n\n1. Since the mandatory liaisons are performing essential functions their roles are most likely to be kept fresh.  Someone whose role has no real import under normal conditions and just provides an occasional ack is more likely to be an entry that gets stale or that gets an ack even when the contributor has drifted away from the project.\n\n2. A lack of response when contacting the required liaisons gets directly to the point of whether the project is healthy or not, or if a required liaison is missing.  Instead of creating an intermediary to delegate this check, it is simpler to measure the thing we want to measure directly.  \n\nI think that treating the group of liaisons as a collective point of contact gets to the heart of what distributing the leadership means, and is must more likely to be a successful model.  I think that if we try this and it does not work then we can assess the viability of TC liaison but I\u0027d prefer for that to be an iteration we come to if we find issues without one.","commit_id":"da73395092a72f623638d87ea4684d2c12baa65d"},{"author":{"_account_id":8556,"name":"Ghanshyam Maan","display_name":"Ghanshyam Maan","email":"gmaan.os14@gmail.com","username":"ghanshyam"},"change_message_id":"747b4912ef965fddfbc24f06a88a0717a2dc16c3","unresolved":false,"context_lines":[{"line_number":43,"context_line":"  the impact of any security reported issues for the project, coordinate the"},{"line_number":44,"context_line":"  development of patches, review proposed patches, and propose any eventual"},{"line_number":45,"context_line":"  backport(s)."},{"line_number":46,"context_line":""},{"line_number":47,"context_line":"Additional recommended roles"},{"line_number":48,"context_line":"~~~~~~~~~~~~~~~~~~~~~~~~~~~~"},{"line_number":49,"context_line":""}],"source_content_type":"text/x-rst","patch_set":5,"id":"9f560f44_2692c84c","line":46,"range":{"start_line":46,"start_character":0,"end_line":46,"end_character":0},"in_reply_to":"9f560f44_4c01ed04","updated":"2020-08-11 16:10:16.000000000","message":"well, it will not be a global contact person but instead, contact person for TC only. TC definitely need a single point of contact to:\n- check if there is any mandatory liaison missing\n- team conflict if any\n- in case the project is not/less active\n\nI mean there can be many situations when TC need some single point of contact for them to address various non-technical things. Key thing is we need to be very careful not to advertise that liaison as \"PTL kind of\" as you mentioned. We can document it as \u0027TC Liaison\u0027 and a contact person for TC when needed in various situations mentioned above(or we can add or redefine those in much generic way).","commit_id":"da73395092a72f623638d87ea4684d2c12baa65d"},{"author":{"_account_id":17068,"name":"Jean-Philippe Evrard","email":"openstack@a.spamming.party","username":"evrardjp"},"change_message_id":"93e0c8388d4429d9678e27bab5a77947fa269ef5","unresolved":false,"context_lines":[{"line_number":43,"context_line":"  the impact of any security reported issues for the project, coordinate the"},{"line_number":44,"context_line":"  development of patches, review proposed patches, and propose any eventual"},{"line_number":45,"context_line":"  backport(s)."},{"line_number":46,"context_line":""},{"line_number":47,"context_line":"Additional recommended roles"},{"line_number":48,"context_line":"~~~~~~~~~~~~~~~~~~~~~~~~~~~~"},{"line_number":49,"context_line":""}],"source_content_type":"text/x-rst","patch_set":5,"id":"9f560f44_bdf559cd","line":46,"range":{"start_line":46,"start_character":0,"end_line":46,"end_character":0},"in_reply_to":"9f560f44_6a2dbefc","updated":"2020-08-10 09:38:10.000000000","message":"I think I can agree on that. Due its lightweight aspect, one could expect that this liaison would also handle the team\u0027s meetings (should the team have meetings).","commit_id":"da73395092a72f623638d87ea4684d2c12baa65d"},{"author":{"_account_id":13995,"name":"Nate Johnston","email":"nate.johnston@redhat.com","username":"natejohnston"},"change_message_id":"f433550f28a00d6e24e4390a8fb0ba9ab5bcb80a","unresolved":false,"context_lines":[{"line_number":43,"context_line":"  the impact of any security reported issues for the project, coordinate the"},{"line_number":44,"context_line":"  development of patches, review proposed patches, and propose any eventual"},{"line_number":45,"context_line":"  backport(s)."},{"line_number":46,"context_line":""},{"line_number":47,"context_line":"Additional recommended roles"},{"line_number":48,"context_line":"~~~~~~~~~~~~~~~~~~~~~~~~~~~~"},{"line_number":49,"context_line":""}],"source_content_type":"text/x-rst","patch_set":5,"id":"9f560f44_4c01ed04","line":46,"range":{"start_line":46,"start_character":0,"end_line":46,"end_character":0},"in_reply_to":"9f560f44_bdf559cd","updated":"2020-08-10 14:52:59.000000000","message":"Can you explain what kinds of issues the TC needs a single point of contact for?  We also have the option of addressing the project team as a whole at their meeting time (if they have one) or on openstack-discuss.  \n\nIf the problem with the PTL position is that it is the proverbial \"single wringable neck\", then before we reintroduce the single wringable neck back into the scheme we need to have strictly scoped why it\u0027s needed and what the alternatives are.","commit_id":"da73395092a72f623638d87ea4684d2c12baa65d"},{"author":{"_account_id":8556,"name":"Ghanshyam Maan","display_name":"Ghanshyam Maan","email":"gmaan.os14@gmail.com","username":"ghanshyam"},"change_message_id":"ede85cff8b8366e3591187de71fc3812d71a44d3","unresolved":false,"context_lines":[{"line_number":43,"context_line":"  the impact of any security reported issues for the project, coordinate the"},{"line_number":44,"context_line":"  development of patches, review proposed patches, and propose any eventual"},{"line_number":45,"context_line":"  backport(s)."},{"line_number":46,"context_line":""},{"line_number":47,"context_line":"Additional recommended roles"},{"line_number":48,"context_line":"~~~~~~~~~~~~~~~~~~~~~~~~~~~~"},{"line_number":49,"context_line":""}],"source_content_type":"text/x-rst","patch_set":5,"id":"9f560f44_a3aeb895","line":46,"range":{"start_line":46,"start_character":0,"end_line":46,"end_character":0},"in_reply_to":"9f560f44_c0cbef47","updated":"2020-08-12 17:43:09.000000000","message":"that should work in usual situation but my concern over \u0027contact all of the mandatory liaison\u0027 is those member can treat that as \"I do not need to reply so someone else will do\". That is why we had PTL as contact person for TC instead of contacting all Core members.\n\nHaving a single person responsible solves that problem otherwise it is the same as \u0027contact all core members\u0027 in PTL model. I am ok to assign the TC single contact person resp to one of the current proposal liaison but with some renaming of name of the liaison though my preference will be a separate liaison in list and that can be served by existing liaison.","commit_id":"da73395092a72f623638d87ea4684d2c12baa65d"},{"author":{"_account_id":8556,"name":"Ghanshyam Maan","display_name":"Ghanshyam Maan","email":"gmaan.os14@gmail.com","username":"ghanshyam"},"change_message_id":"cf16c76a4583830e90ea066ee04a8a2aa9541b72","unresolved":false,"context_lines":[{"line_number":61,"context_line":"  the liaison will not be recorded in governance, else it might quickly get"},{"line_number":62,"context_line":"  outdated."},{"line_number":63,"context_line":""},{"line_number":64,"context_line":"  In order for the OpenStack Events teams to know who to contact, every project"},{"line_number":65,"context_line":"  adhering to the \"PTL-less\" model should opt in to an event. This means the"},{"line_number":66,"context_line":"  team members will need organise themselves, decide who will be the contact"},{"line_number":67,"context_line":"  person for a certain event, and that person shall contact the OpenStack events"}],"source_content_type":"text/x-rst","patch_set":5,"id":"9f560f44_aa335661","line":64,"range":{"start_line":64,"start_character":19,"end_line":64,"end_character":64},"updated":"2020-08-08 22:03:20.000000000","message":"we need to have a place where event team can look for the contact point for PTL-less model projects.","commit_id":"da73395092a72f623638d87ea4684d2c12baa65d"},{"author":{"_account_id":17068,"name":"Jean-Philippe Evrard","email":"openstack@a.spamming.party","username":"evrardjp"},"change_message_id":"4f221864a9e07c9d6108e04a0403cade8a6c01d2","unresolved":false,"context_lines":[{"line_number":61,"context_line":"  the liaison will not be recorded in governance, else it might quickly get"},{"line_number":62,"context_line":"  outdated."},{"line_number":63,"context_line":""},{"line_number":64,"context_line":"  In order for the OpenStack Events teams to know who to contact, every project"},{"line_number":65,"context_line":"  adhering to the \"PTL-less\" model should opt in to an event. This means the"},{"line_number":66,"context_line":"  team members will need organise themselves, decide who will be the contact"},{"line_number":67,"context_line":"  person for a certain event, and that person shall contact the OpenStack events"}],"source_content_type":"text/x-rst","patch_set":5,"id":"9f560f44_9a6e8994","line":64,"range":{"start_line":64,"start_character":19,"end_line":64,"end_character":64},"in_reply_to":"9f560f44_6c2311a8","updated":"2020-08-11 10:34:34.000000000","message":"this is indeed what I meant.","commit_id":"da73395092a72f623638d87ea4684d2c12baa65d"},{"author":{"_account_id":8556,"name":"Ghanshyam Maan","display_name":"Ghanshyam Maan","email":"gmaan.os14@gmail.com","username":"ghanshyam"},"change_message_id":"747b4912ef965fddfbc24f06a88a0717a2dc16c3","unresolved":false,"context_lines":[{"line_number":61,"context_line":"  the liaison will not be recorded in governance, else it might quickly get"},{"line_number":62,"context_line":"  outdated."},{"line_number":63,"context_line":""},{"line_number":64,"context_line":"  In order for the OpenStack Events teams to know who to contact, every project"},{"line_number":65,"context_line":"  adhering to the \"PTL-less\" model should opt in to an event. This means the"},{"line_number":66,"context_line":"  team members will need organise themselves, decide who will be the contact"},{"line_number":67,"context_line":"  person for a certain event, and that person shall contact the OpenStack events"}],"source_content_type":"text/x-rst","patch_set":5,"id":"9f560f44_c6c94c5b","line":64,"range":{"start_line":64,"start_character":19,"end_line":64,"end_character":64},"in_reply_to":"9f560f44_9a6e8994","updated":"2020-08-11 16:10:16.000000000","message":"ok, that make sense and more easy to maintain *optional* duties in _optional_ way. +1","commit_id":"da73395092a72f623638d87ea4684d2c12baa65d"},{"author":{"_account_id":17068,"name":"Jean-Philippe Evrard","email":"openstack@a.spamming.party","username":"evrardjp"},"change_message_id":"93e0c8388d4429d9678e27bab5a77947fa269ef5","unresolved":false,"context_lines":[{"line_number":61,"context_line":"  the liaison will not be recorded in governance, else it might quickly get"},{"line_number":62,"context_line":"  outdated."},{"line_number":63,"context_line":""},{"line_number":64,"context_line":"  In order for the OpenStack Events teams to know who to contact, every project"},{"line_number":65,"context_line":"  adhering to the \"PTL-less\" model should opt in to an event. This means the"},{"line_number":66,"context_line":"  team members will need organise themselves, decide who will be the contact"},{"line_number":67,"context_line":"  person for a certain event, and that person shall contact the OpenStack events"}],"source_content_type":"text/x-rst","patch_set":5,"id":"9f560f44_fddfd162","line":64,"range":{"start_line":64,"start_character":19,"end_line":64,"end_character":64},"in_reply_to":"9f560f44_aa335661","updated":"2020-08-10 09:38:10.000000000","message":"I thought we agreed during the meeting that if we set up an _opt in_ instead, it means that there is no need for us to setup a place to look liaisons up. The list is handled, at each event, by the events team. Of course, it\u0027s a big change compared to the current state. But it helps the life of the individuals in the events team to be an opt in, instead of an outdated wiki, IMO.\n\nSadly it won\u0027t help projects who decide to follow this model and then forget about events and don\u0027t read ML. But if they don\u0027t read ML, I am pretty sure they are already loosing something...","commit_id":"da73395092a72f623638d87ea4684d2c12baa65d"},{"author":{"_account_id":13995,"name":"Nate Johnston","email":"nate.johnston@redhat.com","username":"natejohnston"},"change_message_id":"f433550f28a00d6e24e4390a8fb0ba9ab5bcb80a","unresolved":false,"context_lines":[{"line_number":61,"context_line":"  the liaison will not be recorded in governance, else it might quickly get"},{"line_number":62,"context_line":"  outdated."},{"line_number":63,"context_line":""},{"line_number":64,"context_line":"  In order for the OpenStack Events teams to know who to contact, every project"},{"line_number":65,"context_line":"  adhering to the \"PTL-less\" model should opt in to an event. This means the"},{"line_number":66,"context_line":"  team members will need organise themselves, decide who will be the contact"},{"line_number":67,"context_line":"  person for a certain event, and that person shall contact the OpenStack events"}],"source_content_type":"text/x-rst","patch_set":5,"id":"9f560f44_6c2311a8","line":64,"range":{"start_line":64,"start_character":19,"end_line":64,"end_character":64},"in_reply_to":"9f560f44_fddfd162","updated":"2020-08-10 14:52:59.000000000","message":"The idea we discussed was that the events team would send an email to openstack-discuss titled \"[congress][tripleo] Events liaisons needed by MM/DD\" (with the actual projects in PTL-less mode listed) and those that wanted events representation would respond, and those that did not respond would not have events representation.","commit_id":"da73395092a72f623638d87ea4684d2c12baa65d"},{"author":{"_account_id":8556,"name":"Ghanshyam Maan","display_name":"Ghanshyam Maan","email":"gmaan.os14@gmail.com","username":"ghanshyam"},"change_message_id":"cf16c76a4583830e90ea066ee04a8a2aa9541b72","unresolved":false,"context_lines":[{"line_number":67,"context_line":"  person for a certain event, and that person shall contact the OpenStack events"},{"line_number":68,"context_line":"  team as a representative of project \"x\"."},{"line_number":69,"context_line":""},{"line_number":70,"context_line":"* Project Update/Onboarding liaisons: The Project Update Liaison is responsible"},{"line_number":71,"context_line":"  for giving the project update showcasing project achievements for the cycle to"},{"line_number":72,"context_line":"  the community. The \"Project Onboarding\" liaison is responsible for"},{"line_number":73,"context_line":"  giving/facilitating onboarding sessions during events for its projects\u0027"}],"source_content_type":"text/x-rst","patch_set":5,"id":"9f560f44_2a7586fa","line":70,"range":{"start_line":70,"start_character":2,"end_line":70,"end_character":37},"updated":"2020-08-08 22:03:20.000000000","message":"by seeing how many liaison we end up asking project, can we merge the \u0027Events liaison\u0027 and \u0027Project Update/Onboarding liaisons\u0027 into a single. We can document that \u0027Events liaison need to choose the member who can do Project Update/Onboarding if needed.","commit_id":"da73395092a72f623638d87ea4684d2c12baa65d"},{"author":{"_account_id":17068,"name":"Jean-Philippe Evrard","email":"openstack@a.spamming.party","username":"evrardjp"},"change_message_id":"93e0c8388d4429d9678e27bab5a77947fa269ef5","unresolved":false,"context_lines":[{"line_number":67,"context_line":"  person for a certain event, and that person shall contact the OpenStack events"},{"line_number":68,"context_line":"  team as a representative of project \"x\"."},{"line_number":69,"context_line":""},{"line_number":70,"context_line":"* Project Update/Onboarding liaisons: The Project Update Liaison is responsible"},{"line_number":71,"context_line":"  for giving the project update showcasing project achievements for the cycle to"},{"line_number":72,"context_line":"  the community. The \"Project Onboarding\" liaison is responsible for"},{"line_number":73,"context_line":"  giving/facilitating onboarding sessions during events for its projects\u0027"}],"source_content_type":"text/x-rst","patch_set":5,"id":"9f560f44_5dd4fd47","line":70,"range":{"start_line":70,"start_character":2,"end_line":70,"end_character":37},"in_reply_to":"9f560f44_2a7586fa","updated":"2020-08-10 09:38:10.000000000","message":"The point is that we don\u0027t ask those optional liaisons.\nI should clarify the wording even further to say, \"hey this is something you should pay attention\".","commit_id":"da73395092a72f623638d87ea4684d2c12baa65d"},{"author":{"_account_id":13995,"name":"Nate Johnston","email":"nate.johnston@redhat.com","username":"natejohnston"},"change_message_id":"f433550f28a00d6e24e4390a8fb0ba9ab5bcb80a","unresolved":false,"context_lines":[{"line_number":67,"context_line":"  person for a certain event, and that person shall contact the OpenStack events"},{"line_number":68,"context_line":"  team as a representative of project \"x\"."},{"line_number":69,"context_line":""},{"line_number":70,"context_line":"* Project Update/Onboarding liaisons: The Project Update Liaison is responsible"},{"line_number":71,"context_line":"  for giving the project update showcasing project achievements for the cycle to"},{"line_number":72,"context_line":"  the community. The \"Project Onboarding\" liaison is responsible for"},{"line_number":73,"context_line":"  giving/facilitating onboarding sessions during events for its projects\u0027"}],"source_content_type":"text/x-rst","patch_set":5,"id":"9f560f44_8c55c5fc","line":70,"range":{"start_line":70,"start_character":2,"end_line":70,"end_character":37},"in_reply_to":"9f560f44_5dd4fd47","updated":"2020-08-10 14:52:59.000000000","message":"Nothing prevents two roles from being held by the same person.  But a person might be good at setting agendas and doing logistics but not be happy at the prospect of public speaking.  Let\u0027s let projects combine these if they wish.  And since these are optional, it is not the end of the world if they are not filled.","commit_id":"da73395092a72f623638d87ea4684d2c12baa65d"},{"author":{"_account_id":8556,"name":"Ghanshyam Maan","display_name":"Ghanshyam Maan","email":"gmaan.os14@gmail.com","username":"ghanshyam"},"change_message_id":"747b4912ef965fddfbc24f06a88a0717a2dc16c3","unresolved":false,"context_lines":[{"line_number":67,"context_line":"  person for a certain event, and that person shall contact the OpenStack events"},{"line_number":68,"context_line":"  team as a representative of project \"x\"."},{"line_number":69,"context_line":""},{"line_number":70,"context_line":"* Project Update/Onboarding liaisons: The Project Update Liaison is responsible"},{"line_number":71,"context_line":"  for giving the project update showcasing project achievements for the cycle to"},{"line_number":72,"context_line":"  the community. The \"Project Onboarding\" liaison is responsible for"},{"line_number":73,"context_line":"  giving/facilitating onboarding sessions during events for its projects\u0027"}],"source_content_type":"text/x-rst","patch_set":5,"id":"9f560f44_e6d570e7","line":70,"range":{"start_line":70,"start_character":2,"end_line":70,"end_character":37},"in_reply_to":"9f560f44_7a58d5f9","updated":"2020-08-11 16:10:16.000000000","message":"ok, I think its good point in case event liaison not comfortable with public speaking then it will be difficult to get volunteers if we combine both. All good here. thanks.","commit_id":"da73395092a72f623638d87ea4684d2c12baa65d"},{"author":{"_account_id":17068,"name":"Jean-Philippe Evrard","email":"openstack@a.spamming.party","username":"evrardjp"},"change_message_id":"4f221864a9e07c9d6108e04a0403cade8a6c01d2","unresolved":false,"context_lines":[{"line_number":67,"context_line":"  person for a certain event, and that person shall contact the OpenStack events"},{"line_number":68,"context_line":"  team as a representative of project \"x\"."},{"line_number":69,"context_line":""},{"line_number":70,"context_line":"* Project Update/Onboarding liaisons: The Project Update Liaison is responsible"},{"line_number":71,"context_line":"  for giving the project update showcasing project achievements for the cycle to"},{"line_number":72,"context_line":"  the community. The \"Project Onboarding\" liaison is responsible for"},{"line_number":73,"context_line":"  giving/facilitating onboarding sessions during events for its projects\u0027"}],"source_content_type":"text/x-rst","patch_set":5,"id":"9f560f44_7a58d5f9","line":70,"range":{"start_line":70,"start_character":2,"end_line":70,"end_character":37},"in_reply_to":"9f560f44_8c55c5fc","updated":"2020-08-11 10:34:34.000000000","message":"totally agreed, and clarifies what I meant.","commit_id":"da73395092a72f623638d87ea4684d2c12baa65d"},{"author":{"_account_id":8556,"name":"Ghanshyam Maan","display_name":"Ghanshyam Maan","email":"gmaan.os14@gmail.com","username":"ghanshyam"},"change_message_id":"cf16c76a4583830e90ea066ee04a8a2aa9541b72","unresolved":false,"context_lines":[{"line_number":71,"context_line":"  for giving the project update showcasing project achievements for the cycle to"},{"line_number":72,"context_line":"  the community. The \"Project Onboarding\" liaison is responsible for"},{"line_number":73,"context_line":"  giving/facilitating onboarding sessions during events for its projects\u0027"},{"line_number":74,"context_line":"  community.  Similarly to the events liaison, those two roles are opt ins."},{"line_number":75,"context_line":""},{"line_number":76,"context_line":"* Meeting Facilitator: The Meeting Facilitator chairs the project\u0027s regular"},{"line_number":77,"context_line":"  periodic meetings and maintains their agenda."}],"source_content_type":"text/x-rst","patch_set":5,"id":"9f560f44_2a4746be","line":74,"range":{"start_line":74,"start_character":14,"end_line":74,"end_character":74},"updated":"2020-08-08 22:03:20.000000000","message":"ditto, we need to provide the wiki page or somewhere they can add this liaison.","commit_id":"da73395092a72f623638d87ea4684d2c12baa65d"},{"author":{"_account_id":17068,"name":"Jean-Philippe Evrard","email":"openstack@a.spamming.party","username":"evrardjp"},"change_message_id":"93e0c8388d4429d9678e27bab5a77947fa269ef5","unresolved":false,"context_lines":[{"line_number":71,"context_line":"  for giving the project update showcasing project achievements for the cycle to"},{"line_number":72,"context_line":"  the community. The \"Project Onboarding\" liaison is responsible for"},{"line_number":73,"context_line":"  giving/facilitating onboarding sessions during events for its projects\u0027"},{"line_number":74,"context_line":"  community.  Similarly to the events liaison, those two roles are opt ins."},{"line_number":75,"context_line":""},{"line_number":76,"context_line":"* Meeting Facilitator: The Meeting Facilitator chairs the project\u0027s regular"},{"line_number":77,"context_line":"  periodic meetings and maintains their agenda."}],"source_content_type":"text/x-rst","patch_set":5,"id":"9f560f44_9dca159e","line":74,"range":{"start_line":74,"start_character":14,"end_line":74,"end_character":74},"in_reply_to":"9f560f44_2a4746be","updated":"2020-08-10 09:38:10.000000000","message":"the wiki will be outdated, as it is today. I am not sure we want to continue that path.","commit_id":"da73395092a72f623638d87ea4684d2c12baa65d"},{"author":{"_account_id":13995,"name":"Nate Johnston","email":"nate.johnston@redhat.com","username":"natejohnston"},"change_message_id":"f433550f28a00d6e24e4390a8fb0ba9ab5bcb80a","unresolved":false,"context_lines":[{"line_number":71,"context_line":"  for giving the project update showcasing project achievements for the cycle to"},{"line_number":72,"context_line":"  the community. The \"Project Onboarding\" liaison is responsible for"},{"line_number":73,"context_line":"  giving/facilitating onboarding sessions during events for its projects\u0027"},{"line_number":74,"context_line":"  community.  Similarly to the events liaison, those two roles are opt ins."},{"line_number":75,"context_line":""},{"line_number":76,"context_line":"* Meeting Facilitator: The Meeting Facilitator chairs the project\u0027s regular"},{"line_number":77,"context_line":"  periodic meetings and maintains their agenda."}],"source_content_type":"text/x-rst","patch_set":5,"id":"9f560f44_ac66c9eb","line":74,"range":{"start_line":74,"start_character":14,"end_line":74,"end_character":74},"in_reply_to":"9f560f44_9dca159e","updated":"2020-08-10 14:52:59.000000000","message":"This cycle, the Foundation team sent a message saying \"Who wants to give updates?\" and, for example, Slawek provided the Neutron update.  That\u0027s really all this role has to be.  I\u0027m honestly on the fence on whether it needs to be delineated at all.","commit_id":"da73395092a72f623638d87ea4684d2c12baa65d"},{"author":{"_account_id":8556,"name":"Ghanshyam Maan","display_name":"Ghanshyam Maan","email":"gmaan.os14@gmail.com","username":"ghanshyam"},"change_message_id":"747b4912ef965fddfbc24f06a88a0717a2dc16c3","unresolved":false,"context_lines":[{"line_number":71,"context_line":"  for giving the project update showcasing project achievements for the cycle to"},{"line_number":72,"context_line":"  the community. The \"Project Onboarding\" liaison is responsible for"},{"line_number":73,"context_line":"  giving/facilitating onboarding sessions during events for its projects\u0027"},{"line_number":74,"context_line":"  community.  Similarly to the events liaison, those two roles are opt ins."},{"line_number":75,"context_line":""},{"line_number":76,"context_line":"* Meeting Facilitator: The Meeting Facilitator chairs the project\u0027s regular"},{"line_number":77,"context_line":"  periodic meetings and maintains their agenda."}],"source_content_type":"text/x-rst","patch_set":5,"id":"9f560f44_66032075","line":74,"range":{"start_line":74,"start_character":14,"end_line":74,"end_character":74},"in_reply_to":"9f560f44_ac66c9eb","updated":"2020-08-11 16:10:16.000000000","message":"+1, agree on these to be at runtime things than maintaining it at some permanent place.","commit_id":"da73395092a72f623638d87ea4684d2c12baa65d"},{"author":{"_account_id":8556,"name":"Ghanshyam Maan","display_name":"Ghanshyam Maan","email":"gmaan.os14@gmail.com","username":"ghanshyam"},"change_message_id":"cf16c76a4583830e90ea066ee04a8a2aa9541b72","unresolved":false,"context_lines":[{"line_number":73,"context_line":"  giving/facilitating onboarding sessions during events for its projects\u0027"},{"line_number":74,"context_line":"  community.  Similarly to the events liaison, those two roles are opt ins."},{"line_number":75,"context_line":""},{"line_number":76,"context_line":"* Meeting Facilitator: The Meeting Facilitator chairs the project\u0027s regular"},{"line_number":77,"context_line":"  periodic meetings and maintains their agenda."},{"line_number":78,"context_line":""},{"line_number":79,"context_line":"* Bug Deputy: Ensures all incoming bugs are triaged."},{"line_number":80,"context_line":""}],"source_content_type":"text/x-rst","patch_set":5,"id":"9f560f44_0a4242ab","line":77,"range":{"start_line":76,"start_character":0,"end_line":77,"end_character":47},"updated":"2020-08-08 22:03:20.000000000","message":"I think this should go to mandatory duties. Regular periodic meetings are good to check the progress of cycle\nMy idea is to club this into \u0027TC liaison\u0027 which i commented above.","commit_id":"da73395092a72f623638d87ea4684d2c12baa65d"},{"author":{"_account_id":17068,"name":"Jean-Philippe Evrard","email":"openstack@a.spamming.party","username":"evrardjp"},"change_message_id":"93e0c8388d4429d9678e27bab5a77947fa269ef5","unresolved":false,"context_lines":[{"line_number":73,"context_line":"  giving/facilitating onboarding sessions during events for its projects\u0027"},{"line_number":74,"context_line":"  community.  Similarly to the events liaison, those two roles are opt ins."},{"line_number":75,"context_line":""},{"line_number":76,"context_line":"* Meeting Facilitator: The Meeting Facilitator chairs the project\u0027s regular"},{"line_number":77,"context_line":"  periodic meetings and maintains their agenda."},{"line_number":78,"context_line":""},{"line_number":79,"context_line":"* Bug Deputy: Ensures all incoming bugs are triaged."},{"line_number":80,"context_line":""}],"source_content_type":"text/x-rst","patch_set":5,"id":"9f560f44_7d42a110","line":77,"range":{"start_line":76,"start_character":0,"end_line":77,"end_character":47},"in_reply_to":"9f560f44_0a4242ab","updated":"2020-08-10 09:38:10.000000000","message":"I believe synchronous meetings are not necessary for some projects.\n\nI don\u0027t want us to say \"here is the lightweight formula to PTL, you just need to do \u003cinsert a thousand things to do here\u003e\". We\u0027ll miss the point, and people will just say that this change didn\u0027t really change the current state of what\u0027s expected in the projects.","commit_id":"da73395092a72f623638d87ea4684d2c12baa65d"},{"author":{"_account_id":17068,"name":"Jean-Philippe Evrard","email":"openstack@a.spamming.party","username":"evrardjp"},"change_message_id":"4f221864a9e07c9d6108e04a0403cade8a6c01d2","unresolved":false,"context_lines":[{"line_number":73,"context_line":"  giving/facilitating onboarding sessions during events for its projects\u0027"},{"line_number":74,"context_line":"  community.  Similarly to the events liaison, those two roles are opt ins."},{"line_number":75,"context_line":""},{"line_number":76,"context_line":"* Meeting Facilitator: The Meeting Facilitator chairs the project\u0027s regular"},{"line_number":77,"context_line":"  periodic meetings and maintains their agenda."},{"line_number":78,"context_line":""},{"line_number":79,"context_line":"* Bug Deputy: Ensures all incoming bugs are triaged."},{"line_number":80,"context_line":""}],"source_content_type":"text/x-rst","patch_set":5,"id":"9f560f44_fa6b4582","line":77,"range":{"start_line":76,"start_character":0,"end_line":77,"end_character":47},"in_reply_to":"9f560f44_2c0bd98d","updated":"2020-08-11 10:34:34.000000000","message":"+1","commit_id":"da73395092a72f623638d87ea4684d2c12baa65d"},{"author":{"_account_id":13995,"name":"Nate Johnston","email":"nate.johnston@redhat.com","username":"natejohnston"},"change_message_id":"f433550f28a00d6e24e4390a8fb0ba9ab5bcb80a","unresolved":false,"context_lines":[{"line_number":73,"context_line":"  giving/facilitating onboarding sessions during events for its projects\u0027"},{"line_number":74,"context_line":"  community.  Similarly to the events liaison, those two roles are opt ins."},{"line_number":75,"context_line":""},{"line_number":76,"context_line":"* Meeting Facilitator: The Meeting Facilitator chairs the project\u0027s regular"},{"line_number":77,"context_line":"  periodic meetings and maintains their agenda."},{"line_number":78,"context_line":""},{"line_number":79,"context_line":"* Bug Deputy: Ensures all incoming bugs are triaged."},{"line_number":80,"context_line":""}],"source_content_type":"text/x-rst","patch_set":5,"id":"9f560f44_2c0bd98d","line":77,"range":{"start_line":76,"start_character":0,"end_line":77,"end_character":47},"in_reply_to":"9f560f44_7d42a110","updated":"2020-08-10 14:52:59.000000000","message":"The point of this proposal is to say \"this is the minimum the TC needs, you can figure the rest out yourself if you got his road\", not to dictate how projects do their business.  While most projects find utility in a weekly meeting, that is not something the TC has to have otherwise the project gets deprecated.  Teams that meet weekly that opt for distributed leadership will be aware they have to figure this out, it shouldn\u0027t be any kind of a surprise.\n\nI just don\u0027t want to wander into an overly proscriptive mode that assumes all projects work the same.","commit_id":"da73395092a72f623638d87ea4684d2c12baa65d"},{"author":{"_account_id":8556,"name":"Ghanshyam Maan","display_name":"Ghanshyam Maan","email":"gmaan.os14@gmail.com","username":"ghanshyam"},"change_message_id":"747b4912ef965fddfbc24f06a88a0717a2dc16c3","unresolved":false,"context_lines":[{"line_number":73,"context_line":"  giving/facilitating onboarding sessions during events for its projects\u0027"},{"line_number":74,"context_line":"  community.  Similarly to the events liaison, those two roles are opt ins."},{"line_number":75,"context_line":""},{"line_number":76,"context_line":"* Meeting Facilitator: The Meeting Facilitator chairs the project\u0027s regular"},{"line_number":77,"context_line":"  periodic meetings and maintains their agenda."},{"line_number":78,"context_line":""},{"line_number":79,"context_line":"* Bug Deputy: Ensures all incoming bugs are triaged."},{"line_number":80,"context_line":""}],"source_content_type":"text/x-rst","patch_set":5,"id":"9f560f44_e61c50c3","line":77,"range":{"start_line":76,"start_character":0,"end_line":77,"end_character":47},"in_reply_to":"9f560f44_fa6b4582","updated":"2020-08-11 16:10:16.000000000","message":"yeah, with leaving project handling things to project team make sense and if no meeting then also project still have other public interfaces (irc, ML etc) to discuss the periodic things.\n\nagree with you.","commit_id":"da73395092a72f623638d87ea4684d2c12baa65d"},{"author":{"_account_id":8556,"name":"Ghanshyam Maan","display_name":"Ghanshyam Maan","email":"gmaan.os14@gmail.com","username":"ghanshyam"},"change_message_id":"cf16c76a4583830e90ea066ee04a8a2aa9541b72","unresolved":false,"context_lines":[{"line_number":76,"context_line":"* Meeting Facilitator: The Meeting Facilitator chairs the project\u0027s regular"},{"line_number":77,"context_line":"  periodic meetings and maintains their agenda."},{"line_number":78,"context_line":""},{"line_number":79,"context_line":"* Bug Deputy: Ensures all incoming bugs are triaged."},{"line_number":80,"context_line":""},{"line_number":81,"context_line":"* RFE Coordinator: This role would involve making sure that blueprint status and"},{"line_number":82,"context_line":"  milestone targets are up to date, that RFEs are triaged and discussed before"},{"line_number":83,"context_line":"  acceptance, and that the tracking LaunchPad or Storyboard items for RFEs are"},{"line_number":84,"context_line":"  properly managed."},{"line_number":85,"context_line":""},{"line_number":86,"context_line":"The process by which each project team chooses these liaisons is left to the discretion of the"},{"line_number":87,"context_line":"project teams, as long as it is public, open, and respectful of the current TC guidelines."}],"source_content_type":"text/x-rst","patch_set":5,"id":"9f560f44_6a165eaa","line":84,"range":{"start_line":79,"start_character":0,"end_line":84,"end_character":19},"updated":"2020-08-08 22:03:20.000000000","message":"can we merge these two into one. both are for coordinating the incoming request either by bugs or RFE and it will be helpful to have it into single role where RFE are handled with bug itself like keystone if I am not wrong.","commit_id":"da73395092a72f623638d87ea4684d2c12baa65d"},{"author":{"_account_id":8556,"name":"Ghanshyam Maan","display_name":"Ghanshyam Maan","email":"gmaan.os14@gmail.com","username":"ghanshyam"},"change_message_id":"747b4912ef965fddfbc24f06a88a0717a2dc16c3","unresolved":false,"context_lines":[{"line_number":76,"context_line":"* Meeting Facilitator: The Meeting Facilitator chairs the project\u0027s regular"},{"line_number":77,"context_line":"  periodic meetings and maintains their agenda."},{"line_number":78,"context_line":""},{"line_number":79,"context_line":"* Bug Deputy: Ensures all incoming bugs are triaged."},{"line_number":80,"context_line":""},{"line_number":81,"context_line":"* RFE Coordinator: This role would involve making sure that blueprint status and"},{"line_number":82,"context_line":"  milestone targets are up to date, that RFEs are triaged and discussed before"},{"line_number":83,"context_line":"  acceptance, and that the tracking LaunchPad or Storyboard items for RFEs are"},{"line_number":84,"context_line":"  properly managed."},{"line_number":85,"context_line":""},{"line_number":86,"context_line":"The process by which each project team chooses these liaisons is left to the discretion of the"},{"line_number":87,"context_line":"project teams, as long as it is public, open, and respectful of the current TC guidelines."}],"source_content_type":"text/x-rst","patch_set":5,"id":"9f560f44_e671f00e","line":84,"range":{"start_line":79,"start_character":0,"end_line":84,"end_character":19},"in_reply_to":"9f560f44_311fb26c","updated":"2020-08-11 16:10:16.000000000","message":"ok, as these are optional and how the project wants to handle itis all good.","commit_id":"da73395092a72f623638d87ea4684d2c12baa65d"},{"author":{"_account_id":13995,"name":"Nate Johnston","email":"nate.johnston@redhat.com","username":"natejohnston"},"change_message_id":"f433550f28a00d6e24e4390a8fb0ba9ab5bcb80a","unresolved":false,"context_lines":[{"line_number":76,"context_line":"* Meeting Facilitator: The Meeting Facilitator chairs the project\u0027s regular"},{"line_number":77,"context_line":"  periodic meetings and maintains their agenda."},{"line_number":78,"context_line":""},{"line_number":79,"context_line":"* Bug Deputy: Ensures all incoming bugs are triaged."},{"line_number":80,"context_line":""},{"line_number":81,"context_line":"* RFE Coordinator: This role would involve making sure that blueprint status and"},{"line_number":82,"context_line":"  milestone targets are up to date, that RFEs are triaged and discussed before"},{"line_number":83,"context_line":"  acceptance, and that the tracking LaunchPad or Storyboard items for RFEs are"},{"line_number":84,"context_line":"  properly managed."},{"line_number":85,"context_line":""},{"line_number":86,"context_line":"The process by which each project team chooses these liaisons is left to the discretion of the"},{"line_number":87,"context_line":"project teams, as long as it is public, open, and respectful of the current TC guidelines."}],"source_content_type":"text/x-rst","patch_set":5,"id":"9f560f44_311fb26c","line":84,"range":{"start_line":79,"start_character":0,"end_line":84,"end_character":19},"in_reply_to":"9f560f44_6a165eaa","updated":"2020-08-10 14:52:59.000000000","message":"A project could choose to have the same person in both roles.  But I don\u0027t think that should be required.  For example, neutron rotates the bug deputy weekly.  But perhaps Neutron might want to have a different RFE coordinator per release cycle.  The Bug deputy triages that items are RFEs and then passes them to the RFE coordinator - other than frequently browsing LaunchPad their duties don\u0027t have any other real overlap.","commit_id":"da73395092a72f623638d87ea4684d2c12baa65d"},{"author":{"_account_id":13252,"name":"Dr. Jens Harbott","display_name":"Jens Harbott (frickler)","email":"frickler@offenerstapel.de","username":"jrosenboom"},"change_message_id":"fb053252924f8e3cc66c7063e8d3aeb3777004b7","unresolved":false,"context_lines":[{"line_number":86,"context_line":"The process by which each project team chooses these liaisons is left to the discretion of the"},{"line_number":87,"context_line":"project teams, as long as it is public, open, and respectful of the current TC guidelines."},{"line_number":88,"context_line":"The TC advocates the use of consensus decisions, with polls or elections when consensus"},{"line_number":89,"context_line":"can not be reached."},{"line_number":90,"context_line":""},{"line_number":91,"context_line":"Points of Concern"},{"line_number":92,"context_line":"-----------------"}],"source_content_type":"text/x-rst","patch_set":5,"id":"9f560f44_ef0f2a85","line":89,"updated":"2020-08-07 15:30:04.000000000","message":"Not sure whether it would also make sense to explicitly clarify that the period for which these assignments can be made is unspecified, no longer tied to a development cycle as for elected PTLs. (At least that is how I am reading this.)","commit_id":"da73395092a72f623638d87ea4684d2c12baa65d"},{"author":{"_account_id":17068,"name":"Jean-Philippe Evrard","email":"openstack@a.spamming.party","username":"evrardjp"},"change_message_id":"93e0c8388d4429d9678e27bab5a77947fa269ef5","unresolved":false,"context_lines":[{"line_number":86,"context_line":"The process by which each project team chooses these liaisons is left to the discretion of the"},{"line_number":87,"context_line":"project teams, as long as it is public, open, and respectful of the current TC guidelines."},{"line_number":88,"context_line":"The TC advocates the use of consensus decisions, with polls or elections when consensus"},{"line_number":89,"context_line":"can not be reached."},{"line_number":90,"context_line":""},{"line_number":91,"context_line":"Points of Concern"},{"line_number":92,"context_line":"-----------------"}],"source_content_type":"text/x-rst","patch_set":5,"id":"9f560f44_bd1ef908","line":89,"in_reply_to":"9f560f44_4a19dad4","updated":"2020-08-10 09:38:10.000000000","message":"I like the idea of having an ACK of the projects\u0027s liaisons indeed, at every cycle, to see if things can continue. We should indeed mention it here.","commit_id":"da73395092a72f623638d87ea4684d2c12baa65d"},{"author":{"_account_id":13995,"name":"Nate Johnston","email":"nate.johnston@redhat.com","username":"natejohnston"},"change_message_id":"f433550f28a00d6e24e4390a8fb0ba9ab5bcb80a","unresolved":false,"context_lines":[{"line_number":86,"context_line":"The process by which each project team chooses these liaisons is left to the discretion of the"},{"line_number":87,"context_line":"project teams, as long as it is public, open, and respectful of the current TC guidelines."},{"line_number":88,"context_line":"The TC advocates the use of consensus decisions, with polls or elections when consensus"},{"line_number":89,"context_line":"can not be reached."},{"line_number":90,"context_line":""},{"line_number":91,"context_line":"Points of Concern"},{"line_number":92,"context_line":"-----------------"}],"source_content_type":"text/x-rst","patch_set":5,"id":"9f560f44_ec8a8161","line":89,"in_reply_to":"9f560f44_bd1ef908","updated":"2020-08-10 14:52:59.000000000","message":"+1 for an ack, as well as clarifying that the duration of assignments is undefined but that the ack is required every election time","commit_id":"da73395092a72f623638d87ea4684d2c12baa65d"},{"author":{"_account_id":8556,"name":"Ghanshyam Maan","display_name":"Ghanshyam Maan","email":"gmaan.os14@gmail.com","username":"ghanshyam"},"change_message_id":"cf16c76a4583830e90ea066ee04a8a2aa9541b72","unresolved":false,"context_lines":[{"line_number":86,"context_line":"The process by which each project team chooses these liaisons is left to the discretion of the"},{"line_number":87,"context_line":"project teams, as long as it is public, open, and respectful of the current TC guidelines."},{"line_number":88,"context_line":"The TC advocates the use of consensus decisions, with polls or elections when consensus"},{"line_number":89,"context_line":"can not be reached."},{"line_number":90,"context_line":""},{"line_number":91,"context_line":"Points of Concern"},{"line_number":92,"context_line":"-----------------"}],"source_content_type":"text/x-rst","patch_set":5,"id":"9f560f44_4a19dad4","line":89,"in_reply_to":"9f560f44_ef0f2a85","updated":"2020-08-08 22:03:20.000000000","message":"this is very important point and I will say it must match with the elected PTL model so that at the same time TC can check how many projects are PTL/liaison-less","commit_id":"da73395092a72f623638d87ea4684d2c12baa65d"},{"author":{"_account_id":13252,"name":"Dr. Jens Harbott","display_name":"Jens Harbott (frickler)","email":"frickler@offenerstapel.de","username":"jrosenboom"},"change_message_id":"fb053252924f8e3cc66c7063e8d3aeb3777004b7","unresolved":false,"context_lines":[{"line_number":94,"context_line":"There are a few places where the projects that choose the distributed leadership"},{"line_number":95,"context_line":"model will need to innovate and solve problems:"},{"line_number":96,"context_line":""},{"line_number":97,"context_line":"* Discoverability: It won\u0027t always be easy to know who to contact for a project."},{"line_number":98,"context_line":"* Distributed Consensus: With an increased number of people accountable for"},{"line_number":99,"context_line":"  aspects of the project, the potential for miscommunications increases."},{"line_number":100,"context_line":"* Inclusion: Since some of the liaisons will not be explicitly written in code -"}],"source_content_type":"text/x-rst","patch_set":5,"id":"9f560f44_4f2a96da","line":97,"range":{"start_line":97,"start_character":51,"end_line":97,"end_character":54},"updated":"2020-08-07 15:30:04.000000000","message":"Nit: whom?","commit_id":"da73395092a72f623638d87ea4684d2c12baa65d"},{"author":{"_account_id":13995,"name":"Nate Johnston","email":"nate.johnston@redhat.com","username":"natejohnston"},"change_message_id":"f433550f28a00d6e24e4390a8fb0ba9ab5bcb80a","unresolved":false,"context_lines":[{"line_number":94,"context_line":"There are a few places where the projects that choose the distributed leadership"},{"line_number":95,"context_line":"model will need to innovate and solve problems:"},{"line_number":96,"context_line":""},{"line_number":97,"context_line":"* Discoverability: It won\u0027t always be easy to know who to contact for a project."},{"line_number":98,"context_line":"* Distributed Consensus: With an increased number of people accountable for"},{"line_number":99,"context_line":"  aspects of the project, the potential for miscommunications increases."},{"line_number":100,"context_line":"* Inclusion: Since some of the liaisons will not be explicitly written in code -"}],"source_content_type":"text/x-rst","patch_set":5,"id":"9f560f44_4c644d4a","line":97,"range":{"start_line":97,"start_character":51,"end_line":97,"end_character":54},"in_reply_to":"9f560f44_4f2a96da","updated":"2020-08-10 14:52:59.000000000","message":"+1 will fix in next respin","commit_id":"da73395092a72f623638d87ea4684d2c12baa65d"},{"author":{"_account_id":13252,"name":"Dr. Jens Harbott","display_name":"Jens Harbott (frickler)","email":"frickler@offenerstapel.de","username":"jrosenboom"},"change_message_id":"fb053252924f8e3cc66c7063e8d3aeb3777004b7","unresolved":false,"context_lines":[{"line_number":103,"context_line":"  in mechanism for teams attending the OpenStack events, which is different than"},{"line_number":104,"context_line":"  the usual opt out."},{"line_number":105,"context_line":"* Minimum Viable: This document is intended to assert the minimum set of roles"},{"line_number":106,"context_line":"  the TC would require to consider the project a functional going concern, but"},{"line_number":107,"context_line":"  is not an exhaustive list of possible roles.  For example, a project might"},{"line_number":108,"context_line":"  assign someone at the end of each cycle to write the cycle highlights.  These"},{"line_number":109,"context_line":"  responsibilities could also be collectively handled by the project team, as"}],"source_content_type":"text/x-rst","patch_set":5,"id":"9f560f44_cf64e64c","line":106,"range":{"start_line":106,"start_character":49,"end_line":106,"end_character":73},"updated":"2020-08-07 15:30:04.000000000","message":"This set of words doesn\u0027t make much sense to me, can you rephrase it somehow to make it better understandable for non-native speakers?","commit_id":"da73395092a72f623638d87ea4684d2c12baa65d"},{"author":{"_account_id":17068,"name":"Jean-Philippe Evrard","email":"openstack@a.spamming.party","username":"evrardjp"},"change_message_id":"93e0c8388d4429d9678e27bab5a77947fa269ef5","unresolved":false,"context_lines":[{"line_number":103,"context_line":"  in mechanism for teams attending the OpenStack events, which is different than"},{"line_number":104,"context_line":"  the usual opt out."},{"line_number":105,"context_line":"* Minimum Viable: This document is intended to assert the minimum set of roles"},{"line_number":106,"context_line":"  the TC would require to consider the project a functional going concern, but"},{"line_number":107,"context_line":"  is not an exhaustive list of possible roles.  For example, a project might"},{"line_number":108,"context_line":"  assign someone at the end of each cycle to write the cycle highlights.  These"},{"line_number":109,"context_line":"  responsibilities could also be collectively handled by the project team, as"}],"source_content_type":"text/x-rst","patch_set":5,"id":"9f560f44_fd14f1ea","line":106,"range":{"start_line":106,"start_character":49,"end_line":106,"end_character":73},"in_reply_to":"9f560f44_cf64e64c","updated":"2020-08-10 09:38:10.000000000","message":"sure.","commit_id":"da73395092a72f623638d87ea4684d2c12baa65d"},{"author":{"_account_id":13995,"name":"Nate Johnston","email":"nate.johnston@redhat.com","username":"natejohnston"},"change_message_id":"f433550f28a00d6e24e4390a8fb0ba9ab5bcb80a","unresolved":false,"context_lines":[{"line_number":103,"context_line":"  in mechanism for teams attending the OpenStack events, which is different than"},{"line_number":104,"context_line":"  the usual opt out."},{"line_number":105,"context_line":"* Minimum Viable: This document is intended to assert the minimum set of roles"},{"line_number":106,"context_line":"  the TC would require to consider the project a functional going concern, but"},{"line_number":107,"context_line":"  is not an exhaustive list of possible roles.  For example, a project might"},{"line_number":108,"context_line":"  assign someone at the end of each cycle to write the cycle highlights.  These"},{"line_number":109,"context_line":"  responsibilities could also be collectively handled by the project team, as"}],"source_content_type":"text/x-rst","patch_set":5,"id":"9f560f44_4cd44d48","line":106,"range":{"start_line":106,"start_character":49,"end_line":106,"end_character":73},"in_reply_to":"9f560f44_fd14f1ea","updated":"2020-08-10 14:52:59.000000000","message":"Sure.  Perhaps \"to consider the project team to be active and functioning\"?","commit_id":"da73395092a72f623638d87ea4684d2c12baa65d"},{"author":{"_account_id":8556,"name":"Ghanshyam Maan","display_name":"Ghanshyam Maan","email":"gmaan.os14@gmail.com","username":"ghanshyam"},"change_message_id":"cf16c76a4583830e90ea066ee04a8a2aa9541b72","unresolved":false,"context_lines":[{"line_number":116,"context_line":"Projects that would like to opt in to a distributed leadership role should make"},{"line_number":117,"context_line":"sure this change has a relative degree of consensus within the project.  To make"},{"line_number":118,"context_line":"the request, a change should be pushed to projects.yaml in the"},{"line_number":119,"context_line":"openstack/governance repository to add the line \"type: distributed\" to the \"ptl\""},{"line_number":120,"context_line":"section of the project\u0027s definition.  This change should have at least a +1 from"},{"line_number":121,"context_line":"the current PTL as well as at least one of the people currently serving as"},{"line_number":122,"context_line":"`release liaison`_ for the project."}],"source_content_type":"text/x-rst","patch_set":5,"id":"9f560f44_0a1b62c9","line":119,"range":{"start_line":119,"start_character":35,"end_line":119,"end_character":67},"updated":"2020-08-08 22:03:20.000000000","message":"and mandatory roles liaison? are we going to list them in project.yaml or somewhere else? we need to have the mandatory roles liaison list ready by the project while they moving to this model to avoid the situation that project opted to this model but do not have all the required liaison.","commit_id":"da73395092a72f623638d87ea4684d2c12baa65d"},{"author":{"_account_id":17068,"name":"Jean-Philippe Evrard","email":"openstack@a.spamming.party","username":"evrardjp"},"change_message_id":"93e0c8388d4429d9678e27bab5a77947fa269ef5","unresolved":false,"context_lines":[{"line_number":116,"context_line":"Projects that would like to opt in to a distributed leadership role should make"},{"line_number":117,"context_line":"sure this change has a relative degree of consensus within the project.  To make"},{"line_number":118,"context_line":"the request, a change should be pushed to projects.yaml in the"},{"line_number":119,"context_line":"openstack/governance repository to add the line \"type: distributed\" to the \"ptl\""},{"line_number":120,"context_line":"section of the project\u0027s definition.  This change should have at least a +1 from"},{"line_number":121,"context_line":"the current PTL as well as at least one of the people currently serving as"},{"line_number":122,"context_line":"`release liaison`_ for the project."}],"source_content_type":"text/x-rst","patch_set":5,"id":"9f560f44_dde80de3","line":119,"range":{"start_line":119,"start_character":35,"end_line":119,"end_character":67},"in_reply_to":"9f560f44_0a1b62c9","updated":"2020-08-10 09:38:10.000000000","message":"correct, on top of adapting the tooling to validate the schema, we should mention it here.","commit_id":"da73395092a72f623638d87ea4684d2c12baa65d"},{"author":{"_account_id":13995,"name":"Nate Johnston","email":"nate.johnston@redhat.com","username":"natejohnston"},"change_message_id":"f433550f28a00d6e24e4390a8fb0ba9ab5bcb80a","unresolved":false,"context_lines":[{"line_number":116,"context_line":"Projects that would like to opt in to a distributed leadership role should make"},{"line_number":117,"context_line":"sure this change has a relative degree of consensus within the project.  To make"},{"line_number":118,"context_line":"the request, a change should be pushed to projects.yaml in the"},{"line_number":119,"context_line":"openstack/governance repository to add the line \"type: distributed\" to the \"ptl\""},{"line_number":120,"context_line":"section of the project\u0027s definition.  This change should have at least a +1 from"},{"line_number":121,"context_line":"the current PTL as well as at least one of the people currently serving as"},{"line_number":122,"context_line":"`release liaison`_ for the project."}],"source_content_type":"text/x-rst","patch_set":5,"id":"9f560f44_2c6599b5","line":119,"range":{"start_line":119,"start_character":35,"end_line":119,"end_character":67},"in_reply_to":"9f560f44_dde80de3","updated":"2020-08-10 14:52:59.000000000","message":"So the release liaisons are already documented here [1] and I did not want to force the release team to change a process that works for them.  But I am open to ideas on what the best way is to document the required liaisons.\n\n[1] https://opendev.org/openstack/releases/src/branch/master/data/release_liaisons.yaml","commit_id":"da73395092a72f623638d87ea4684d2c12baa65d"},{"author":{"_account_id":8556,"name":"Ghanshyam Maan","display_name":"Ghanshyam Maan","email":"gmaan.os14@gmail.com","username":"ghanshyam"},"change_message_id":"cf16c76a4583830e90ea066ee04a8a2aa9541b72","unresolved":false,"context_lines":[{"line_number":117,"context_line":"sure this change has a relative degree of consensus within the project.  To make"},{"line_number":118,"context_line":"the request, a change should be pushed to projects.yaml in the"},{"line_number":119,"context_line":"openstack/governance repository to add the line \"type: distributed\" to the \"ptl\""},{"line_number":120,"context_line":"section of the project\u0027s definition.  This change should have at least a +1 from"},{"line_number":121,"context_line":"the current PTL as well as at least one of the people currently serving as"},{"line_number":122,"context_line":"`release liaison`_ for the project."},{"line_number":123,"context_line":""},{"line_number":124,"context_line":"Projects will remain with the PTL model unless they notify the TC that they wish"},{"line_number":125,"context_line":"to opt in to the distributed leadership model.  Once a project has moved to the"}],"source_content_type":"text/x-rst","patch_set":5,"id":"9f560f44_ca24ca0f","line":122,"range":{"start_line":120,"start_character":38,"end_line":122,"end_character":35},"updated":"2020-08-08 22:03:20.000000000","message":"How about making the criteria like: \n- current PTL +1\n- choose the mandatory roles liaison and their +1","commit_id":"da73395092a72f623638d87ea4684d2c12baa65d"},{"author":{"_account_id":13995,"name":"Nate Johnston","email":"nate.johnston@redhat.com","username":"natejohnston"},"change_message_id":"f433550f28a00d6e24e4390a8fb0ba9ab5bcb80a","unresolved":false,"context_lines":[{"line_number":117,"context_line":"sure this change has a relative degree of consensus within the project.  To make"},{"line_number":118,"context_line":"the request, a change should be pushed to projects.yaml in the"},{"line_number":119,"context_line":"openstack/governance repository to add the line \"type: distributed\" to the \"ptl\""},{"line_number":120,"context_line":"section of the project\u0027s definition.  This change should have at least a +1 from"},{"line_number":121,"context_line":"the current PTL as well as at least one of the people currently serving as"},{"line_number":122,"context_line":"`release liaison`_ for the project."},{"line_number":123,"context_line":""},{"line_number":124,"context_line":"Projects will remain with the PTL model unless they notify the TC that they wish"},{"line_number":125,"context_line":"to opt in to the distributed leadership model.  Once a project has moved to the"}],"source_content_type":"text/x-rst","patch_set":5,"id":"9f560f44_2c67594f","line":122,"range":{"start_line":120,"start_character":38,"end_line":122,"end_character":35},"in_reply_to":"9f560f44_1def25e9","updated":"2020-08-10 14:52:59.000000000","message":"+1","commit_id":"da73395092a72f623638d87ea4684d2c12baa65d"},{"author":{"_account_id":17068,"name":"Jean-Philippe Evrard","email":"openstack@a.spamming.party","username":"evrardjp"},"change_message_id":"93e0c8388d4429d9678e27bab5a77947fa269ef5","unresolved":false,"context_lines":[{"line_number":117,"context_line":"sure this change has a relative degree of consensus within the project.  To make"},{"line_number":118,"context_line":"the request, a change should be pushed to projects.yaml in the"},{"line_number":119,"context_line":"openstack/governance repository to add the line \"type: distributed\" to the \"ptl\""},{"line_number":120,"context_line":"section of the project\u0027s definition.  This change should have at least a +1 from"},{"line_number":121,"context_line":"the current PTL as well as at least one of the people currently serving as"},{"line_number":122,"context_line":"`release liaison`_ for the project."},{"line_number":123,"context_line":""},{"line_number":124,"context_line":"Projects will remain with the PTL model unless they notify the TC that they wish"},{"line_number":125,"context_line":"to opt in to the distributed leadership model.  Once a project has moved to the"}],"source_content_type":"text/x-rst","patch_set":5,"id":"9f560f44_1def25e9","line":122,"range":{"start_line":120,"start_character":38,"end_line":122,"end_character":35},"in_reply_to":"9f560f44_ca24ca0f","updated":"2020-08-10 09:38:10.000000000","message":"LGTM.","commit_id":"da73395092a72f623638d87ea4684d2c12baa65d"},{"author":{"_account_id":8556,"name":"Ghanshyam Maan","display_name":"Ghanshyam Maan","email":"gmaan.os14@gmail.com","username":"ghanshyam"},"change_message_id":"cf16c76a4583830e90ea066ee04a8a2aa9541b72","unresolved":false,"context_lines":[{"line_number":125,"context_line":"to opt in to the distributed leadership model.  Once a project has moved to the"},{"line_number":126,"context_line":"distributed leadership model, they can revert to the PTL model by creating a"},{"line_number":127,"context_line":"change to projects.yaml to remove the \"type: distributed\" line in the project\u0027s"},{"line_number":128,"context_line":"\"ptl\" stanza.  This change should have at least a +1 from at least one of the"},{"line_number":129,"context_line":"people currently serving as `release liaison`_ for the project."},{"line_number":130,"context_line":""},{"line_number":131,"context_line":"A project may change their opt-in status only once a release cycle, to ensure"},{"line_number":132,"context_line":"that the elections officials have clarity on which projects need PTL elections."}],"source_content_type":"text/x-rst","patch_set":5,"id":"9f560f44_6a7bfef3","line":129,"range":{"start_line":128,"start_character":15,"end_line":129,"end_character":63},"updated":"2020-08-08 22:03:20.000000000","message":"the reverting should be \n- +1 from all the current mandatory liaisons\n- choose the PTL \u003cif this is in between of cycle then it can be anyone from project who want to take resp and if it is at the end of cycle then it has to be during the time of PTL election. PTL election can go with go-ahead from TC by seeing the application from project to revert to PTL model\u003e","commit_id":"da73395092a72f623638d87ea4684d2c12baa65d"},{"author":{"_account_id":17068,"name":"Jean-Philippe Evrard","email":"openstack@a.spamming.party","username":"evrardjp"},"change_message_id":"93e0c8388d4429d9678e27bab5a77947fa269ef5","unresolved":false,"context_lines":[{"line_number":125,"context_line":"to opt in to the distributed leadership model.  Once a project has moved to the"},{"line_number":126,"context_line":"distributed leadership model, they can revert to the PTL model by creating a"},{"line_number":127,"context_line":"change to projects.yaml to remove the \"type: distributed\" line in the project\u0027s"},{"line_number":128,"context_line":"\"ptl\" stanza.  This change should have at least a +1 from at least one of the"},{"line_number":129,"context_line":"people currently serving as `release liaison`_ for the project."},{"line_number":130,"context_line":""},{"line_number":131,"context_line":"A project may change their opt-in status only once a release cycle, to ensure"},{"line_number":132,"context_line":"that the elections officials have clarity on which projects need PTL elections."}],"source_content_type":"text/x-rst","patch_set":5,"id":"9f560f44_7db741f6","line":129,"range":{"start_line":128,"start_character":15,"end_line":129,"end_character":63},"in_reply_to":"9f560f44_6a7bfef3","updated":"2020-08-10 09:38:10.000000000","message":"agreed","commit_id":"da73395092a72f623638d87ea4684d2c12baa65d"},{"author":{"_account_id":13995,"name":"Nate Johnston","email":"nate.johnston@redhat.com","username":"natejohnston"},"change_message_id":"f433550f28a00d6e24e4390a8fb0ba9ab5bcb80a","unresolved":false,"context_lines":[{"line_number":125,"context_line":"to opt in to the distributed leadership model.  Once a project has moved to the"},{"line_number":126,"context_line":"distributed leadership model, they can revert to the PTL model by creating a"},{"line_number":127,"context_line":"change to projects.yaml to remove the \"type: distributed\" line in the project\u0027s"},{"line_number":128,"context_line":"\"ptl\" stanza.  This change should have at least a +1 from at least one of the"},{"line_number":129,"context_line":"people currently serving as `release liaison`_ for the project."},{"line_number":130,"context_line":""},{"line_number":131,"context_line":"A project may change their opt-in status only once a release cycle, to ensure"},{"line_number":132,"context_line":"that the elections officials have clarity on which projects need PTL elections."}],"source_content_type":"text/x-rst","patch_set":5,"id":"9f560f44_acf529cd","line":129,"range":{"start_line":128,"start_character":15,"end_line":129,"end_character":63},"in_reply_to":"9f560f44_7db741f6","updated":"2020-08-10 14:52:59.000000000","message":"Yes I assumed the process would be:\n\n1) +1 from all mandatory liaisons\n2) election process","commit_id":"da73395092a72f623638d87ea4684d2c12baa65d"},{"author":{"_account_id":13252,"name":"Dr. Jens Harbott","display_name":"Jens Harbott (frickler)","email":"frickler@offenerstapel.de","username":"jrosenboom"},"change_message_id":"fb053252924f8e3cc66c7063e8d3aeb3777004b7","unresolved":false,"context_lines":[{"line_number":132,"context_line":"that the elections officials have clarity on which projects need PTL elections."},{"line_number":133,"context_line":"All requests should be received by week R-5 of the release calendar."},{"line_number":134,"context_line":""},{"line_number":135,"context_line":"This document does not change the procedure when a project has no candidate for"},{"line_number":136,"context_line":"PTL: the TC must then make an appointment.  One of the possible options that the"},{"line_number":137,"context_line":"TC may consider, in consultation with the project team, to change the team to"},{"line_number":138,"context_line":"the distributed project leadership model."}],"source_content_type":"text/x-rst","patch_set":5,"id":"9f560f44_8fe30ea4","line":135,"updated":"2020-08-07 15:30:04.000000000","message":"Actually I\u0027d say it does change the procedure, the TC still has to make a decision, but a new option for that decision is created.","commit_id":"da73395092a72f623638d87ea4684d2c12baa65d"},{"author":{"_account_id":17068,"name":"Jean-Philippe Evrard","email":"openstack@a.spamming.party","username":"evrardjp"},"change_message_id":"93e0c8388d4429d9678e27bab5a77947fa269ef5","unresolved":false,"context_lines":[{"line_number":132,"context_line":"that the elections officials have clarity on which projects need PTL elections."},{"line_number":133,"context_line":"All requests should be received by week R-5 of the release calendar."},{"line_number":134,"context_line":""},{"line_number":135,"context_line":"This document does not change the procedure when a project has no candidate for"},{"line_number":136,"context_line":"PTL: the TC must then make an appointment.  One of the possible options that the"},{"line_number":137,"context_line":"TC may consider, in consultation with the project team, to change the team to"},{"line_number":138,"context_line":"the distributed project leadership model."}],"source_content_type":"text/x-rst","patch_set":5,"id":"9f560f44_ddd12d25","line":135,"in_reply_to":"9f560f44_8fe30ea4","updated":"2020-08-10 09:38:10.000000000","message":"I guess we can reword this :)","commit_id":"da73395092a72f623638d87ea4684d2c12baa65d"},{"author":{"_account_id":13995,"name":"Nate Johnston","email":"nate.johnston@redhat.com","username":"natejohnston"},"change_message_id":"f433550f28a00d6e24e4390a8fb0ba9ab5bcb80a","unresolved":false,"context_lines":[{"line_number":132,"context_line":"that the elections officials have clarity on which projects need PTL elections."},{"line_number":133,"context_line":"All requests should be received by week R-5 of the release calendar."},{"line_number":134,"context_line":""},{"line_number":135,"context_line":"This document does not change the procedure when a project has no candidate for"},{"line_number":136,"context_line":"PTL: the TC must then make an appointment.  One of the possible options that the"},{"line_number":137,"context_line":"TC may consider, in consultation with the project team, to change the team to"},{"line_number":138,"context_line":"the distributed project leadership model."}],"source_content_type":"text/x-rst","patch_set":5,"id":"9f560f44_6ccdd1b5","line":135,"in_reply_to":"9f560f44_ddd12d25","updated":"2020-08-10 14:52:59.000000000","message":"+1","commit_id":"da73395092a72f623638d87ea4684d2c12baa65d"},{"author":{"_account_id":13995,"name":"Nate Johnston","email":"nate.johnston@redhat.com","username":"natejohnston"},"change_message_id":"627d5fd7e5d669014b26fb5641380a1621cbc32e","unresolved":false,"context_lines":[{"line_number":109,"context_line":""},{"line_number":110,"context_line":"While the PTL is assigned to a single cycle, the duration of the assignment"},{"line_number":111,"context_line":"for a project liaison is unlimited in time. To avoid outdated information,"},{"line_number":112,"context_line":"a TC member dedicated to follow a project with distributed leadership"},{"line_number":113,"context_line":"will query, at regular intervals (once per cycle), if the liaisons for the"},{"line_number":114,"context_line":"project are still valid. It is expected to have the liaisons answer on the"},{"line_number":115,"context_line":"mailing list thread to extend/validate their liaison status."}],"source_content_type":"text/x-rst","patch_set":6,"id":"9f560f44_662b2030","line":112,"range":{"start_line":112,"start_character":0,"end_line":112,"end_character":11},"updated":"2020-08-11 15:41:15.000000000","message":"Would this be one or both of the TC liaisons to the project, or a new position?","commit_id":"73207e50a34e3eb0bd263e2abc12aa69f597279c"},{"author":{"_account_id":17068,"name":"Jean-Philippe Evrard","email":"openstack@a.spamming.party","username":"evrardjp"},"change_message_id":"8ffd6df0338534941668cd4c9f21a48b6c051792","unresolved":false,"context_lines":[{"line_number":109,"context_line":""},{"line_number":110,"context_line":"While the PTL is assigned to a single cycle, the duration of the assignment"},{"line_number":111,"context_line":"for a project liaison is unlimited in time. To avoid outdated information,"},{"line_number":112,"context_line":"a TC member dedicated to follow a project with distributed leadership"},{"line_number":113,"context_line":"will query, at regular intervals (once per cycle), if the liaisons for the"},{"line_number":114,"context_line":"project are still valid. It is expected to have the liaisons answer on the"},{"line_number":115,"context_line":"mailing list thread to extend/validate their liaison status."}],"source_content_type":"text/x-rst","patch_set":6,"id":"9f560f44_b45a7980","line":112,"range":{"start_line":112,"start_character":0,"end_line":112,"end_character":11},"in_reply_to":"9f560f44_662b2030","updated":"2020-08-13 06:55:17.000000000","message":"I consider one amongst the two, TC members can organise themselves :)","commit_id":"73207e50a34e3eb0bd263e2abc12aa69f597279c"},{"author":{"_account_id":13995,"name":"Nate Johnston","email":"nate.johnston@redhat.com","username":"natejohnston"},"change_message_id":"627d5fd7e5d669014b26fb5641380a1621cbc32e","unresolved":false,"context_lines":[{"line_number":120,"context_line":"There are a few places where the projects that choose the distributed leadership"},{"line_number":121,"context_line":"model will need to innovate and solve problems:"},{"line_number":122,"context_line":""},{"line_number":123,"context_line":"* Discoverability: It will make harder to know whom to contact for a project."},{"line_number":124,"context_line":"* Distributed Consensus: With an increased number of people accountable for"},{"line_number":125,"context_line":"  aspects of the project, the potential for miscommunications increases."},{"line_number":126,"context_line":"* Inclusion: Since some of the liaisons will not be explicitly written in code -"}],"source_content_type":"text/x-rst","patch_set":6,"id":"9f560f44_a6f378e7","line":123,"range":{"start_line":123,"start_character":19,"end_line":123,"end_character":38},"updated":"2020-08-11 15:41:15.000000000","message":"nit: \"It will make it harder\" or easier to read \"It will be more difficult\"","commit_id":"73207e50a34e3eb0bd263e2abc12aa69f597279c"},{"author":{"_account_id":8556,"name":"Ghanshyam Maan","display_name":"Ghanshyam Maan","email":"gmaan.os14@gmail.com","username":"ghanshyam"},"change_message_id":"747b4912ef965fddfbc24f06a88a0717a2dc16c3","unresolved":false,"context_lines":[{"line_number":109,"context_line":""},{"line_number":110,"context_line":"While the PTL is assigned to a single cycle, the duration of the assignment"},{"line_number":111,"context_line":"for a project liaison is unlimited in time. To avoid outdated information,"},{"line_number":112,"context_line":"a TC member dedicated to follow a project with distributed leadership"},{"line_number":113,"context_line":"will query, at regular intervals (once per cycle), if the liaisons for the"},{"line_number":114,"context_line":"project are still valid. It is expected to have the liaisons answer on the"},{"line_number":115,"context_line":"mailing list thread to extend/validate their liaison status."},{"line_number":116,"context_line":""}],"source_content_type":"text/x-rst","patch_set":7,"id":"9f560f44_665fa072","line":113,"range":{"start_line":112,"start_character":2,"end_line":113,"end_character":32},"updated":"2020-08-11 16:10:16.000000000","message":"+1.","commit_id":"ac33be1ca40369c5c37f9a2db966ac13298ab6dd"},{"author":{"_account_id":13995,"name":"Nate Johnston","email":"nate.johnston@redhat.com","username":"natejohnston"},"change_message_id":"6cebe4bb686ee9011b419b0387fe0e983d780aec","unresolved":false,"context_lines":[{"line_number":150,"context_line":"the TC when it will receive at least a +1 from the current PTL, and the future"},{"line_number":151,"context_line":"liaisons."},{"line_number":152,"context_line":""},{"line_number":153,"context_line":"Technical notes:"},{"line_number":154,"context_line":"* A follow-up patch on this resolution will change"},{"line_number":155,"context_line":"  the \"liaisons\" field to adapt its current structure, to add the new mandatory"},{"line_number":156,"context_line":"  roles, next to the already present list of TC members liaising for the"}],"source_content_type":"text/x-rst","patch_set":7,"id":"9f560f44_004b27b0","line":153,"range":{"start_line":153,"start_character":0,"end_line":153,"end_character":16},"updated":"2020-08-11 20:14:57.000000000","message":"Respun to add a carriage return after this line so the list would render.","commit_id":"ac33be1ca40369c5c37f9a2db966ac13298ab6dd"},{"author":{"_account_id":8556,"name":"Ghanshyam Maan","display_name":"Ghanshyam Maan","email":"gmaan.os14@gmail.com","username":"ghanshyam"},"change_message_id":"747b4912ef965fddfbc24f06a88a0717a2dc16c3","unresolved":false,"context_lines":[{"line_number":155,"context_line":"  the \"liaisons\" field to adapt its current structure, to add the new mandatory"},{"line_number":156,"context_line":"  roles, next to the already present list of TC members liaising for the"},{"line_number":157,"context_line":"  project."},{"line_number":158,"context_line":"* The releases liaison will continue to be listed in the `releases` repository,"},{"line_number":159,"context_line":"  to not impact the current delivery of the releases."},{"line_number":160,"context_line":""},{"line_number":161,"context_line":"Once a project has moved to the distributed leadership model, they can revert to"},{"line_number":162,"context_line":"the PTL model by creating a change to `projects.yaml` to remove the"}],"source_content_type":"text/x-rst","patch_set":7,"id":"9f560f44_26f3e875","line":159,"range":{"start_line":158,"start_character":0,"end_line":159,"end_character":53},"updated":"2020-08-11 16:10:16.000000000","message":"those are not complete release liaison list, instead of it is liaison other than PTL. so with this model, we need to have all projects have a liaison.\n\nI think the current list can be valid for release team in PTL model and the other needs to be in TC side. Because in TC we should have mandatory liaison things for non-PTL model in project.yaml to see if anything missing And any removal is known by TC.","commit_id":"ac33be1ca40369c5c37f9a2db966ac13298ab6dd"},{"author":{"_account_id":8556,"name":"Ghanshyam Maan","display_name":"Ghanshyam Maan","email":"gmaan.os14@gmail.com","username":"ghanshyam"},"change_message_id":"ede85cff8b8366e3591187de71fc3812d71a44d3","unresolved":false,"context_lines":[{"line_number":155,"context_line":"  the \"liaisons\" field to adapt its current structure, to add the new mandatory"},{"line_number":156,"context_line":"  roles, next to the already present list of TC members liaising for the"},{"line_number":157,"context_line":"  project."},{"line_number":158,"context_line":"* The releases liaison will continue to be listed in the `releases` repository,"},{"line_number":159,"context_line":"  to not impact the current delivery of the releases."},{"line_number":160,"context_line":""},{"line_number":161,"context_line":"Once a project has moved to the distributed leadership model, they can revert to"},{"line_number":162,"context_line":"the PTL model by creating a change to `projects.yaml` to remove the"}],"source_content_type":"text/x-rst","patch_set":7,"id":"9f560f44_63d6602a","line":159,"range":{"start_line":158,"start_character":0,"end_line":159,"end_character":53},"in_reply_to":"9f560f44_204e2bc1","updated":"2020-08-12 17:43:09.000000000","message":"+1, that is good idea.","commit_id":"ac33be1ca40369c5c37f9a2db966ac13298ab6dd"},{"author":{"_account_id":13995,"name":"Nate Johnston","email":"nate.johnston@redhat.com","username":"natejohnston"},"change_message_id":"6cebe4bb686ee9011b419b0387fe0e983d780aec","unresolved":false,"context_lines":[{"line_number":155,"context_line":"  the \"liaisons\" field to adapt its current structure, to add the new mandatory"},{"line_number":156,"context_line":"  roles, next to the already present list of TC members liaising for the"},{"line_number":157,"context_line":"  project."},{"line_number":158,"context_line":"* The releases liaison will continue to be listed in the `releases` repository,"},{"line_number":159,"context_line":"  to not impact the current delivery of the releases."},{"line_number":160,"context_line":""},{"line_number":161,"context_line":"Once a project has moved to the distributed leadership model, they can revert to"},{"line_number":162,"context_line":"the PTL model by creating a change to `projects.yaml` to remove the"}],"source_content_type":"text/x-rst","patch_set":7,"id":"9f560f44_204e2bc1","line":159,"range":{"start_line":158,"start_character":0,"end_line":159,"end_character":53},"in_reply_to":"9f560f44_26f3e875","updated":"2020-08-11 20:14:57.000000000","message":"I\u0027m Ok with that - perhaps we can decide which one would change first and then add a job for the other one that checks if the contents match the first.  For example, if the project_config liaison list is authoritative then adda job on the releases repo that checks to make sure that if there is one listed in project_config that it is the same in releases.  What do you think?","commit_id":"ac33be1ca40369c5c37f9a2db966ac13298ab6dd"},{"author":{"_account_id":17068,"name":"Jean-Philippe Evrard","email":"openstack@a.spamming.party","username":"evrardjp"},"change_message_id":"8ffd6df0338534941668cd4c9f21a48b6c051792","unresolved":false,"context_lines":[{"line_number":155,"context_line":"  the \"liaisons\" field to adapt its current structure, to add the new mandatory"},{"line_number":156,"context_line":"  roles, next to the already present list of TC members liaising for the"},{"line_number":157,"context_line":"  project."},{"line_number":158,"context_line":"* The releases liaison will continue to be listed in the `releases` repository,"},{"line_number":159,"context_line":"  to not impact the current delivery of the releases."},{"line_number":160,"context_line":""},{"line_number":161,"context_line":"Once a project has moved to the distributed leadership model, they can revert to"},{"line_number":162,"context_line":"the PTL model by creating a change to `projects.yaml` to remove the"}],"source_content_type":"text/x-rst","patch_set":7,"id":"9f560f44_419a2f6e","line":159,"range":{"start_line":158,"start_character":0,"end_line":159,"end_character":53},"in_reply_to":"9f560f44_63d6602a","updated":"2020-08-13 06:55:17.000000000","message":"I would suggest that we help releases on its tooling to leverage governance data, and that governance can expose this feature, so that releases can use it.\n\nI suggest that we don\u0027t start implementing double lists which can get oudated very quick, and is not very \"user friendly\".\n\nLet\u0027s just sync with releases, and see what can be done, and when. I guess early in the release cycle is best.","commit_id":"ac33be1ca40369c5c37f9a2db966ac13298ab6dd"},{"author":{"_account_id":308,"name":"Thierry Carrez","email":"thierry@openstack.org","username":"ttx"},"change_message_id":"e1096c8c73c404a2e98d78daa69b3d9dbf870719","unresolved":false,"context_lines":[{"line_number":2,"context_line":"2020-08-03 Distributed Project Leadership"},{"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\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":4,"context_line":""},{"line_number":5,"context_line":"The governing structure for OpenStack projects has long been for a Project"},{"line_number":6,"context_line":"Technical Lead (PTL) to be elected to serve as a singular focus for that"},{"line_number":7,"context_line":"project.  While the PTL role varies significantly from project to project, the"},{"line_number":8,"context_line":"PTL has many responsibilities for managing the development and release process"}],"source_content_type":"text/x-rst","patch_set":9,"id":"9f560f44_a58245ff","line":5,"range":{"start_line":5,"start_character":38,"end_line":5,"end_character":46},"updated":"2020-08-12 10:53:31.000000000","message":"project teams","commit_id":"3e9b4b23727cba52abf73c282a3027f230a293d4"},{"author":{"_account_id":13995,"name":"Nate Johnston","email":"nate.johnston@redhat.com","username":"natejohnston"},"change_message_id":"78c9272ada2b798cde4d2267aedfa677eee60573","unresolved":false,"context_lines":[{"line_number":2,"context_line":"2020-08-03 Distributed Project Leadership"},{"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\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":4,"context_line":""},{"line_number":5,"context_line":"The governing structure for OpenStack projects has long been for a Project"},{"line_number":6,"context_line":"Technical Lead (PTL) to be elected to serve as a singular focus for that"},{"line_number":7,"context_line":"project.  While the PTL role varies significantly from project to project, the"},{"line_number":8,"context_line":"PTL has many responsibilities for managing the development and release process"}],"source_content_type":"text/x-rst","patch_set":9,"id":"9f560f44_581d0772","line":5,"range":{"start_line":5,"start_character":38,"end_line":5,"end_character":46},"in_reply_to":"9f560f44_a58245ff","updated":"2020-08-12 17:25:02.000000000","message":"Done","commit_id":"3e9b4b23727cba52abf73c282a3027f230a293d4"},{"author":{"_account_id":308,"name":"Thierry Carrez","email":"thierry@openstack.org","username":"ttx"},"change_message_id":"e1096c8c73c404a2e98d78daa69b3d9dbf870719","unresolved":false,"context_lines":[{"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\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":4,"context_line":""},{"line_number":5,"context_line":"The governing structure for OpenStack projects has long been for a Project"},{"line_number":6,"context_line":"Technical Lead (PTL) to be elected to serve as a singular focus for that"},{"line_number":7,"context_line":"project.  While the PTL role varies significantly from project to project, the"},{"line_number":8,"context_line":"PTL has many responsibilities for managing the development and release process"},{"line_number":9,"context_line":"for a project as well as representing the project both internally and"}],"source_content_type":"text/x-rst","patch_set":9,"id":"9f560f44_65882d22","line":6,"range":{"start_line":6,"start_character":0,"end_line":6,"end_character":9},"updated":"2020-08-12 10:53:31.000000000","message":"Team","commit_id":"3e9b4b23727cba52abf73c282a3027f230a293d4"},{"author":{"_account_id":13995,"name":"Nate Johnston","email":"nate.johnston@redhat.com","username":"natejohnston"},"change_message_id":"78c9272ada2b798cde4d2267aedfa677eee60573","unresolved":false,"context_lines":[{"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\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":4,"context_line":""},{"line_number":5,"context_line":"The governing structure for OpenStack projects has long been for a Project"},{"line_number":6,"context_line":"Technical Lead (PTL) to be elected to serve as a singular focus for that"},{"line_number":7,"context_line":"project.  While the PTL role varies significantly from project to project, the"},{"line_number":8,"context_line":"PTL has many responsibilities for managing the development and release process"},{"line_number":9,"context_line":"for a project as well as representing the project both internally and"}],"source_content_type":"text/x-rst","patch_set":9,"id":"9f560f44_b8126361","line":6,"range":{"start_line":6,"start_character":0,"end_line":6,"end_character":9},"in_reply_to":"9f560f44_65882d22","updated":"2020-08-12 17:25:02.000000000","message":"Done","commit_id":"3e9b4b23727cba52abf73c282a3027f230a293d4"},{"author":{"_account_id":308,"name":"Thierry Carrez","email":"thierry@openstack.org","username":"ttx"},"change_message_id":"e1096c8c73c404a2e98d78daa69b3d9dbf870719","unresolved":false,"context_lines":[{"line_number":37,"context_line":"Required roles"},{"line_number":38,"context_line":"~~~~~~~~~~~~~~"},{"line_number":39,"context_line":""},{"line_number":40,"context_line":"The projects are expected to have at least the following required liaison roles:"},{"line_number":41,"context_line":""},{"line_number":42,"context_line":"* Release liaison: The `release liaison`_ is responsible for creating releases"},{"line_number":43,"context_line":"  for an OpenStack project.  In addition, release liaisons review requests for"}],"source_content_type":"text/x-rst","patch_set":9,"id":"9f560f44_e57b9d26","line":40,"range":{"start_line":40,"start_character":0,"end_line":40,"end_character":12},"updated":"2020-08-12 10:53:31.000000000","message":"Project teams","commit_id":"3e9b4b23727cba52abf73c282a3027f230a293d4"},{"author":{"_account_id":13995,"name":"Nate Johnston","email":"nate.johnston@redhat.com","username":"natejohnston"},"change_message_id":"78c9272ada2b798cde4d2267aedfa677eee60573","unresolved":false,"context_lines":[{"line_number":37,"context_line":"Required roles"},{"line_number":38,"context_line":"~~~~~~~~~~~~~~"},{"line_number":39,"context_line":""},{"line_number":40,"context_line":"The projects are expected to have at least the following required liaison roles:"},{"line_number":41,"context_line":""},{"line_number":42,"context_line":"* Release liaison: The `release liaison`_ is responsible for creating releases"},{"line_number":43,"context_line":"  for an OpenStack project.  In addition, release liaisons review requests for"}],"source_content_type":"text/x-rst","patch_set":9,"id":"9f560f44_d808f72e","line":40,"range":{"start_line":40,"start_character":0,"end_line":40,"end_character":12},"in_reply_to":"9f560f44_e57b9d26","updated":"2020-08-12 17:25:02.000000000","message":"Done","commit_id":"3e9b4b23727cba52abf73c282a3027f230a293d4"},{"author":{"_account_id":308,"name":"Thierry Carrez","email":"thierry@openstack.org","username":"ttx"},"change_message_id":"e1096c8c73c404a2e98d78daa69b3d9dbf870719","unresolved":false,"context_lines":[{"line_number":39,"context_line":""},{"line_number":40,"context_line":"The projects are expected to have at least the following required liaison roles:"},{"line_number":41,"context_line":""},{"line_number":42,"context_line":"* Release liaison: The `release liaison`_ is responsible for creating releases"},{"line_number":43,"context_line":"  for an OpenStack project.  In addition, release liaisons review requests for"},{"line_number":44,"context_line":"  Feature Freeze Exception (FFE)."},{"line_number":45,"context_line":""},{"line_number":46,"context_line":"* tact-sig liaison: Historically named the \"infra Liaison\".  It is responsible for"}],"source_content_type":"text/x-rst","patch_set":9,"id":"9f560f44_25763540","line":43,"range":{"start_line":42,"start_character":46,"end_line":43,"end_character":26},"updated":"2020-08-12 10:53:31.000000000","message":"I\u0027d say \"responsible for requesting releases for deliverables produced by the project team\".","commit_id":"3e9b4b23727cba52abf73c282a3027f230a293d4"},{"author":{"_account_id":13995,"name":"Nate Johnston","email":"nate.johnston@redhat.com","username":"natejohnston"},"change_message_id":"78c9272ada2b798cde4d2267aedfa677eee60573","unresolved":false,"context_lines":[{"line_number":39,"context_line":""},{"line_number":40,"context_line":"The projects are expected to have at least the following required liaison roles:"},{"line_number":41,"context_line":""},{"line_number":42,"context_line":"* Release liaison: The `release liaison`_ is responsible for creating releases"},{"line_number":43,"context_line":"  for an OpenStack project.  In addition, release liaisons review requests for"},{"line_number":44,"context_line":"  Feature Freeze Exception (FFE)."},{"line_number":45,"context_line":""},{"line_number":46,"context_line":"* tact-sig liaison: Historically named the \"infra Liaison\".  It is responsible for"}],"source_content_type":"text/x-rst","patch_set":9,"id":"9f560f44_c355acfc","line":43,"range":{"start_line":42,"start_character":46,"end_line":43,"end_character":26},"in_reply_to":"9f560f44_25763540","updated":"2020-08-12 17:25:02.000000000","message":"Done","commit_id":"3e9b4b23727cba52abf73c282a3027f230a293d4"},{"author":{"_account_id":308,"name":"Thierry Carrez","email":"thierry@openstack.org","username":"ttx"},"change_message_id":"e1096c8c73c404a2e98d78daa69b3d9dbf870719","unresolved":false,"context_lines":[{"line_number":40,"context_line":"The projects are expected to have at least the following required liaison roles:"},{"line_number":41,"context_line":""},{"line_number":42,"context_line":"* Release liaison: The `release liaison`_ is responsible for creating releases"},{"line_number":43,"context_line":"  for an OpenStack project.  In addition, release liaisons review requests for"},{"line_number":44,"context_line":"  Feature Freeze Exception (FFE)."},{"line_number":45,"context_line":""},{"line_number":46,"context_line":"* tact-sig liaison: Historically named the \"infra Liaison\".  It is responsible for"},{"line_number":47,"context_line":"  the health of the CI jobs run in the OpenStack Zuul CI.  In the event that there"}],"source_content_type":"text/x-rst","patch_set":9,"id":"9f560f44_05a85175","line":44,"range":{"start_line":43,"start_character":42,"end_line":44,"end_character":33},"updated":"2020-08-12 10:53:31.000000000","message":"I\u0027m not sure that\u0027s required. Some teams don\u0027t really use FFEs, and if they do, they can be delegated to the group. Maybe say \"release liaisons generally review...\" ?","commit_id":"3e9b4b23727cba52abf73c282a3027f230a293d4"},{"author":{"_account_id":13995,"name":"Nate Johnston","email":"nate.johnston@redhat.com","username":"natejohnston"},"change_message_id":"78c9272ada2b798cde4d2267aedfa677eee60573","unresolved":false,"context_lines":[{"line_number":40,"context_line":"The projects are expected to have at least the following required liaison roles:"},{"line_number":41,"context_line":""},{"line_number":42,"context_line":"* Release liaison: The `release liaison`_ is responsible for creating releases"},{"line_number":43,"context_line":"  for an OpenStack project.  In addition, release liaisons review requests for"},{"line_number":44,"context_line":"  Feature Freeze Exception (FFE)."},{"line_number":45,"context_line":""},{"line_number":46,"context_line":"* tact-sig liaison: Historically named the \"infra Liaison\".  It is responsible for"},{"line_number":47,"context_line":"  the health of the CI jobs run in the OpenStack Zuul CI.  In the event that there"}],"source_content_type":"text/x-rst","patch_set":9,"id":"9f560f44_a35a3827","line":44,"range":{"start_line":43,"start_character":42,"end_line":44,"end_character":33},"in_reply_to":"9f560f44_05a85175","updated":"2020-08-12 17:25:02.000000000","message":"Done","commit_id":"3e9b4b23727cba52abf73c282a3027f230a293d4"},{"author":{"_account_id":308,"name":"Thierry Carrez","email":"thierry@openstack.org","username":"ttx"},"change_message_id":"e1096c8c73c404a2e98d78daa69b3d9dbf870719","unresolved":false,"context_lines":[{"line_number":50,"context_line":"  for changes in the `project_config repository`_."},{"line_number":51,"context_line":""},{"line_number":52,"context_line":"* Security liaison: the security liaison is the contact person to help assessing"},{"line_number":53,"context_line":"  the impact of any security reported issues for the project, coordinate the"},{"line_number":54,"context_line":"  development of patches, review proposed patches, and propose any eventual"},{"line_number":55,"context_line":"  backport(s)."},{"line_number":56,"context_line":""}],"source_content_type":"text/x-rst","patch_set":9,"id":"9f560f44_45bb69c3","line":53,"range":{"start_line":53,"start_character":45,"end_line":53,"end_character":60},"updated":"2020-08-12 10:53:31.000000000","message":"in the project team deliverables","commit_id":"3e9b4b23727cba52abf73c282a3027f230a293d4"},{"author":{"_account_id":13995,"name":"Nate Johnston","email":"nate.johnston@redhat.com","username":"natejohnston"},"change_message_id":"78c9272ada2b798cde4d2267aedfa677eee60573","unresolved":false,"context_lines":[{"line_number":50,"context_line":"  for changes in the `project_config repository`_."},{"line_number":51,"context_line":""},{"line_number":52,"context_line":"* Security liaison: the security liaison is the contact person to help assessing"},{"line_number":53,"context_line":"  the impact of any security reported issues for the project, coordinate the"},{"line_number":54,"context_line":"  development of patches, review proposed patches, and propose any eventual"},{"line_number":55,"context_line":"  backport(s)."},{"line_number":56,"context_line":""}],"source_content_type":"text/x-rst","patch_set":9,"id":"9f560f44_e33b90c5","line":53,"range":{"start_line":53,"start_character":45,"end_line":53,"end_character":60},"in_reply_to":"9f560f44_45bb69c3","updated":"2020-08-12 17:25:02.000000000","message":"Done","commit_id":"3e9b4b23727cba52abf73c282a3027f230a293d4"},{"author":{"_account_id":308,"name":"Thierry Carrez","email":"thierry@openstack.org","username":"ttx"},"change_message_id":"e1096c8c73c404a2e98d78daa69b3d9dbf870719","unresolved":false,"context_lines":[{"line_number":59,"context_line":""},{"line_number":60,"context_line":"Any other responsibilities of the PTL that are not addressed above are optional,"},{"line_number":61,"context_line":"and are left to the project teams to determine."},{"line_number":62,"context_line":"The TC recommends projects opting in for distributed project leadership to assign"},{"line_number":63,"context_line":"people into the following optional roles, to each project\u0027s discretion:"},{"line_number":64,"context_line":""},{"line_number":65,"context_line":"* Events liaison: An Events liaison ensures that a project has space reserved at"}],"source_content_type":"text/x-rst","patch_set":9,"id":"9f560f44_85b581d0","line":62,"range":{"start_line":62,"start_character":18,"end_line":62,"end_character":26},"updated":"2020-08-12 10:53:31.000000000","message":"project teams","commit_id":"3e9b4b23727cba52abf73c282a3027f230a293d4"},{"author":{"_account_id":13995,"name":"Nate Johnston","email":"nate.johnston@redhat.com","username":"natejohnston"},"change_message_id":"78c9272ada2b798cde4d2267aedfa677eee60573","unresolved":false,"context_lines":[{"line_number":59,"context_line":""},{"line_number":60,"context_line":"Any other responsibilities of the PTL that are not addressed above are optional,"},{"line_number":61,"context_line":"and are left to the project teams to determine."},{"line_number":62,"context_line":"The TC recommends projects opting in for distributed project leadership to assign"},{"line_number":63,"context_line":"people into the following optional roles, to each project\u0027s discretion:"},{"line_number":64,"context_line":""},{"line_number":65,"context_line":"* Events liaison: An Events liaison ensures that a project has space reserved at"}],"source_content_type":"text/x-rst","patch_set":9,"id":"9f560f44_43499c5e","line":62,"range":{"start_line":62,"start_character":18,"end_line":62,"end_character":26},"in_reply_to":"9f560f44_85b581d0","updated":"2020-08-12 17:25:02.000000000","message":"Done","commit_id":"3e9b4b23727cba52abf73c282a3027f230a293d4"},{"author":{"_account_id":308,"name":"Thierry Carrez","email":"thierry@openstack.org","username":"ttx"},"change_message_id":"e1096c8c73c404a2e98d78daa69b3d9dbf870719","unresolved":false,"context_lines":[{"line_number":60,"context_line":"Any other responsibilities of the PTL that are not addressed above are optional,"},{"line_number":61,"context_line":"and are left to the project teams to determine."},{"line_number":62,"context_line":"The TC recommends projects opting in for distributed project leadership to assign"},{"line_number":63,"context_line":"people into the following optional roles, to each project\u0027s discretion:"},{"line_number":64,"context_line":""},{"line_number":65,"context_line":"* Events liaison: An Events liaison ensures that a project has space reserved at"},{"line_number":66,"context_line":"  a PTG or Summit for the project that will be sufficient for the project\u0027s"}],"source_content_type":"text/x-rst","patch_set":9,"id":"9f560f44_c5c6594a","line":63,"range":{"start_line":63,"start_character":50,"end_line":63,"end_character":57},"updated":"2020-08-12 10:53:31.000000000","message":"team","commit_id":"3e9b4b23727cba52abf73c282a3027f230a293d4"},{"author":{"_account_id":13995,"name":"Nate Johnston","email":"nate.johnston@redhat.com","username":"natejohnston"},"change_message_id":"78c9272ada2b798cde4d2267aedfa677eee60573","unresolved":false,"context_lines":[{"line_number":60,"context_line":"Any other responsibilities of the PTL that are not addressed above are optional,"},{"line_number":61,"context_line":"and are left to the project teams to determine."},{"line_number":62,"context_line":"The TC recommends projects opting in for distributed project leadership to assign"},{"line_number":63,"context_line":"people into the following optional roles, to each project\u0027s discretion:"},{"line_number":64,"context_line":""},{"line_number":65,"context_line":"* Events liaison: An Events liaison ensures that a project has space reserved at"},{"line_number":66,"context_line":"  a PTG or Summit for the project that will be sufficient for the project\u0027s"}],"source_content_type":"text/x-rst","patch_set":9,"id":"9f560f44_8374549e","line":63,"range":{"start_line":63,"start_character":50,"end_line":63,"end_character":57},"in_reply_to":"9f560f44_c5c6594a","updated":"2020-08-12 17:25:02.000000000","message":"changed to \"project team\u0027s\" for consistency","commit_id":"3e9b4b23727cba52abf73c282a3027f230a293d4"},{"author":{"_account_id":308,"name":"Thierry Carrez","email":"thierry@openstack.org","username":"ttx"},"change_message_id":"e1096c8c73c404a2e98d78daa69b3d9dbf870719","unresolved":false,"context_lines":[{"line_number":62,"context_line":"The TC recommends projects opting in for distributed project leadership to assign"},{"line_number":63,"context_line":"people into the following optional roles, to each project\u0027s discretion:"},{"line_number":64,"context_line":""},{"line_number":65,"context_line":"* Events liaison: An Events liaison ensures that a project has space reserved at"},{"line_number":66,"context_line":"  a PTG or Summit for the project that will be sufficient for the project\u0027s"},{"line_number":67,"context_line":"  meeting needs. The events liaison puts out an agenda for any of the project"},{"line_number":68,"context_line":"  meetings, makes sure those meetings are organized and facilitated, and that"}],"source_content_type":"text/x-rst","patch_set":9,"id":"9f560f44_25c47540","line":65,"range":{"start_line":65,"start_character":51,"end_line":65,"end_character":58},"updated":"2020-08-12 10:53:31.000000000","message":"team","commit_id":"3e9b4b23727cba52abf73c282a3027f230a293d4"},{"author":{"_account_id":13995,"name":"Nate Johnston","email":"nate.johnston@redhat.com","username":"natejohnston"},"change_message_id":"78c9272ada2b798cde4d2267aedfa677eee60573","unresolved":false,"context_lines":[{"line_number":62,"context_line":"The TC recommends projects opting in for distributed project leadership to assign"},{"line_number":63,"context_line":"people into the following optional roles, to each project\u0027s discretion:"},{"line_number":64,"context_line":""},{"line_number":65,"context_line":"* Events liaison: An Events liaison ensures that a project has space reserved at"},{"line_number":66,"context_line":"  a PTG or Summit for the project that will be sufficient for the project\u0027s"},{"line_number":67,"context_line":"  meeting needs. The events liaison puts out an agenda for any of the project"},{"line_number":68,"context_line":"  meetings, makes sure those meetings are organized and facilitated, and that"}],"source_content_type":"text/x-rst","patch_set":9,"id":"9f560f44_43623cda","line":65,"range":{"start_line":65,"start_character":51,"end_line":65,"end_character":58},"in_reply_to":"9f560f44_25c47540","updated":"2020-08-12 17:25:02.000000000","message":"Done","commit_id":"3e9b4b23727cba52abf73c282a3027f230a293d4"},{"author":{"_account_id":308,"name":"Thierry Carrez","email":"thierry@openstack.org","username":"ttx"},"change_message_id":"e1096c8c73c404a2e98d78daa69b3d9dbf870719","unresolved":false,"context_lines":[{"line_number":63,"context_line":"people into the following optional roles, to each project\u0027s discretion:"},{"line_number":64,"context_line":""},{"line_number":65,"context_line":"* Events liaison: An Events liaison ensures that a project has space reserved at"},{"line_number":66,"context_line":"  a PTG or Summit for the project that will be sufficient for the project\u0027s"},{"line_number":67,"context_line":"  meeting needs. The events liaison puts out an agenda for any of the project"},{"line_number":68,"context_line":"  meetings, makes sure those meetings are organized and facilitated, and that"},{"line_number":69,"context_line":"  the results are documented.  This is a temporary role, lasting only during the"}],"source_content_type":"text/x-rst","patch_set":9,"id":"9f560f44_45e089cd","line":66,"range":{"start_line":66,"start_character":18,"end_line":66,"end_character":33},"updated":"2020-08-12 10:53:31.000000000","message":"probably redundant","commit_id":"3e9b4b23727cba52abf73c282a3027f230a293d4"},{"author":{"_account_id":308,"name":"Thierry Carrez","email":"thierry@openstack.org","username":"ttx"},"change_message_id":"e1096c8c73c404a2e98d78daa69b3d9dbf870719","unresolved":false,"context_lines":[{"line_number":63,"context_line":"people into the following optional roles, to each project\u0027s discretion:"},{"line_number":64,"context_line":""},{"line_number":65,"context_line":"* Events liaison: An Events liaison ensures that a project has space reserved at"},{"line_number":66,"context_line":"  a PTG or Summit for the project that will be sufficient for the project\u0027s"},{"line_number":67,"context_line":"  meeting needs. The events liaison puts out an agenda for any of the project"},{"line_number":68,"context_line":"  meetings, makes sure those meetings are organized and facilitated, and that"},{"line_number":69,"context_line":"  the results are documented.  This is a temporary role, lasting only during the"}],"source_content_type":"text/x-rst","patch_set":9,"id":"9f560f44_e5cefd59","line":66,"range":{"start_line":66,"start_character":66,"end_line":66,"end_character":73},"updated":"2020-08-12 10:53:31.000000000","message":"team","commit_id":"3e9b4b23727cba52abf73c282a3027f230a293d4"},{"author":{"_account_id":13995,"name":"Nate Johnston","email":"nate.johnston@redhat.com","username":"natejohnston"},"change_message_id":"78c9272ada2b798cde4d2267aedfa677eee60573","unresolved":false,"context_lines":[{"line_number":63,"context_line":"people into the following optional roles, to each project\u0027s discretion:"},{"line_number":64,"context_line":""},{"line_number":65,"context_line":"* Events liaison: An Events liaison ensures that a project has space reserved at"},{"line_number":66,"context_line":"  a PTG or Summit for the project that will be sufficient for the project\u0027s"},{"line_number":67,"context_line":"  meeting needs. The events liaison puts out an agenda for any of the project"},{"line_number":68,"context_line":"  meetings, makes sure those meetings are organized and facilitated, and that"},{"line_number":69,"context_line":"  the results are documented.  This is a temporary role, lasting only during the"}],"source_content_type":"text/x-rst","patch_set":9,"id":"9f560f44_235f480f","line":66,"range":{"start_line":66,"start_character":66,"end_line":66,"end_character":73},"in_reply_to":"9f560f44_e5cefd59","updated":"2020-08-12 17:25:02.000000000","message":"Done","commit_id":"3e9b4b23727cba52abf73c282a3027f230a293d4"},{"author":{"_account_id":308,"name":"Thierry Carrez","email":"thierry@openstack.org","username":"ttx"},"change_message_id":"e1096c8c73c404a2e98d78daa69b3d9dbf870719","unresolved":false,"context_lines":[{"line_number":73,"context_line":""},{"line_number":74,"context_line":"  At the beginning of the organisation of an event, the OpenStack Events teams"},{"line_number":75,"context_line":"  will query on our openstack-discuss ML for participants ready to liaise for"},{"line_number":76,"context_line":"  the event, for each the projects with distributed leadership."},{"line_number":77,"context_line":"  The projects interested by a representation in the event can then opt-in to"},{"line_number":78,"context_line":"  the event by assigning a liaison. The projects are free to decide how and"},{"line_number":79,"context_line":"  who will be assigned as the event liaison.  The projects not answering on"}],"source_content_type":"text/x-rst","patch_set":9,"id":"9f560f44_c5cbf947","line":76,"range":{"start_line":76,"start_character":26,"end_line":76,"end_character":34},"updated":"2020-08-12 10:53:31.000000000","message":"teams","commit_id":"3e9b4b23727cba52abf73c282a3027f230a293d4"},{"author":{"_account_id":13995,"name":"Nate Johnston","email":"nate.johnston@redhat.com","username":"natejohnston"},"change_message_id":"78c9272ada2b798cde4d2267aedfa677eee60573","unresolved":false,"context_lines":[{"line_number":73,"context_line":""},{"line_number":74,"context_line":"  At the beginning of the organisation of an event, the OpenStack Events teams"},{"line_number":75,"context_line":"  will query on our openstack-discuss ML for participants ready to liaise for"},{"line_number":76,"context_line":"  the event, for each the projects with distributed leadership."},{"line_number":77,"context_line":"  The projects interested by a representation in the event can then opt-in to"},{"line_number":78,"context_line":"  the event by assigning a liaison. The projects are free to decide how and"},{"line_number":79,"context_line":"  who will be assigned as the event liaison.  The projects not answering on"}],"source_content_type":"text/x-rst","patch_set":9,"id":"9f560f44_63878063","line":76,"range":{"start_line":76,"start_character":26,"end_line":76,"end_character":34},"in_reply_to":"9f560f44_c5cbf947","updated":"2020-08-12 17:25:02.000000000","message":"Done","commit_id":"3e9b4b23727cba52abf73c282a3027f230a293d4"},{"author":{"_account_id":308,"name":"Thierry Carrez","email":"thierry@openstack.org","username":"ttx"},"change_message_id":"e1096c8c73c404a2e98d78daa69b3d9dbf870719","unresolved":false,"context_lines":[{"line_number":74,"context_line":"  At the beginning of the organisation of an event, the OpenStack Events teams"},{"line_number":75,"context_line":"  will query on our openstack-discuss ML for participants ready to liaise for"},{"line_number":76,"context_line":"  the event, for each the projects with distributed leadership."},{"line_number":77,"context_line":"  The projects interested by a representation in the event can then opt-in to"},{"line_number":78,"context_line":"  the event by assigning a liaison. The projects are free to decide how and"},{"line_number":79,"context_line":"  who will be assigned as the event liaison.  The projects not answering on"},{"line_number":80,"context_line":"  the ML or not assigning a liaison on time will not have representation in"}],"source_content_type":"text/x-rst","patch_set":9,"id":"9f560f44_25d91522","line":77,"range":{"start_line":77,"start_character":6,"end_line":77,"end_character":14},"updated":"2020-08-12 10:53:31.000000000","message":"project teams","commit_id":"3e9b4b23727cba52abf73c282a3027f230a293d4"},{"author":{"_account_id":13995,"name":"Nate Johnston","email":"nate.johnston@redhat.com","username":"natejohnston"},"change_message_id":"78c9272ada2b798cde4d2267aedfa677eee60573","unresolved":false,"context_lines":[{"line_number":74,"context_line":"  At the beginning of the organisation of an event, the OpenStack Events teams"},{"line_number":75,"context_line":"  will query on our openstack-discuss ML for participants ready to liaise for"},{"line_number":76,"context_line":"  the event, for each the projects with distributed leadership."},{"line_number":77,"context_line":"  The projects interested by a representation in the event can then opt-in to"},{"line_number":78,"context_line":"  the event by assigning a liaison. The projects are free to decide how and"},{"line_number":79,"context_line":"  who will be assigned as the event liaison.  The projects not answering on"},{"line_number":80,"context_line":"  the ML or not assigning a liaison on time will not have representation in"}],"source_content_type":"text/x-rst","patch_set":9,"id":"9f560f44_c37c8c74","line":77,"range":{"start_line":77,"start_character":6,"end_line":77,"end_character":14},"in_reply_to":"9f560f44_25d91522","updated":"2020-08-12 17:25:02.000000000","message":"Done","commit_id":"3e9b4b23727cba52abf73c282a3027f230a293d4"},{"author":{"_account_id":308,"name":"Thierry Carrez","email":"thierry@openstack.org","username":"ttx"},"change_message_id":"e1096c8c73c404a2e98d78daa69b3d9dbf870719","unresolved":false,"context_lines":[{"line_number":75,"context_line":"  will query on our openstack-discuss ML for participants ready to liaise for"},{"line_number":76,"context_line":"  the event, for each the projects with distributed leadership."},{"line_number":77,"context_line":"  The projects interested by a representation in the event can then opt-in to"},{"line_number":78,"context_line":"  the event by assigning a liaison. The projects are free to decide how and"},{"line_number":79,"context_line":"  who will be assigned as the event liaison.  The projects not answering on"},{"line_number":80,"context_line":"  the ML or not assigning a liaison on time will not have representation in"},{"line_number":81,"context_line":"  the event."}],"source_content_type":"text/x-rst","patch_set":9,"id":"9f560f44_05d691f2","line":78,"range":{"start_line":78,"start_character":36,"end_line":78,"end_character":48},"updated":"2020-08-12 10:53:31.000000000","message":"Teams","commit_id":"3e9b4b23727cba52abf73c282a3027f230a293d4"},{"author":{"_account_id":13995,"name":"Nate Johnston","email":"nate.johnston@redhat.com","username":"natejohnston"},"change_message_id":"78c9272ada2b798cde4d2267aedfa677eee60573","unresolved":false,"context_lines":[{"line_number":75,"context_line":"  will query on our openstack-discuss ML for participants ready to liaise for"},{"line_number":76,"context_line":"  the event, for each the projects with distributed leadership."},{"line_number":77,"context_line":"  The projects interested by a representation in the event can then opt-in to"},{"line_number":78,"context_line":"  the event by assigning a liaison. The projects are free to decide how and"},{"line_number":79,"context_line":"  who will be assigned as the event liaison.  The projects not answering on"},{"line_number":80,"context_line":"  the ML or not assigning a liaison on time will not have representation in"},{"line_number":81,"context_line":"  the event."}],"source_content_type":"text/x-rst","patch_set":9,"id":"9f560f44_03968495","line":78,"range":{"start_line":78,"start_character":36,"end_line":78,"end_character":48},"in_reply_to":"9f560f44_05d691f2","updated":"2020-08-12 17:25:02.000000000","message":"Done","commit_id":"3e9b4b23727cba52abf73c282a3027f230a293d4"},{"author":{"_account_id":308,"name":"Thierry Carrez","email":"thierry@openstack.org","username":"ttx"},"change_message_id":"e1096c8c73c404a2e98d78daa69b3d9dbf870719","unresolved":false,"context_lines":[{"line_number":76,"context_line":"  the event, for each the projects with distributed leadership."},{"line_number":77,"context_line":"  The projects interested by a representation in the event can then opt-in to"},{"line_number":78,"context_line":"  the event by assigning a liaison. The projects are free to decide how and"},{"line_number":79,"context_line":"  who will be assigned as the event liaison.  The projects not answering on"},{"line_number":80,"context_line":"  the ML or not assigning a liaison on time will not have representation in"},{"line_number":81,"context_line":"  the event."},{"line_number":82,"context_line":""}],"source_content_type":"text/x-rst","patch_set":9,"id":"9f560f44_a5fec568","line":79,"range":{"start_line":79,"start_character":46,"end_line":79,"end_character":58},"updated":"2020-08-12 10:53:31.000000000","message":"Project teams","commit_id":"3e9b4b23727cba52abf73c282a3027f230a293d4"},{"author":{"_account_id":13995,"name":"Nate Johnston","email":"nate.johnston@redhat.com","username":"natejohnston"},"change_message_id":"78c9272ada2b798cde4d2267aedfa677eee60573","unresolved":false,"context_lines":[{"line_number":76,"context_line":"  the event, for each the projects with distributed leadership."},{"line_number":77,"context_line":"  The projects interested by a representation in the event can then opt-in to"},{"line_number":78,"context_line":"  the event by assigning a liaison. The projects are free to decide how and"},{"line_number":79,"context_line":"  who will be assigned as the event liaison.  The projects not answering on"},{"line_number":80,"context_line":"  the ML or not assigning a liaison on time will not have representation in"},{"line_number":81,"context_line":"  the event."},{"line_number":82,"context_line":""}],"source_content_type":"text/x-rst","patch_set":9,"id":"9f560f44_e392709f","line":79,"range":{"start_line":79,"start_character":46,"end_line":79,"end_character":58},"in_reply_to":"9f560f44_a5fec568","updated":"2020-08-12 17:25:02.000000000","message":"Done","commit_id":"3e9b4b23727cba52abf73c282a3027f230a293d4"},{"author":{"_account_id":308,"name":"Thierry Carrez","email":"thierry@openstack.org","username":"ttx"},"change_message_id":"e1096c8c73c404a2e98d78daa69b3d9dbf870719","unresolved":false,"context_lines":[{"line_number":86,"context_line":"  giving/facilitating onboarding sessions during events for its projects\u0027"},{"line_number":87,"context_line":"  community.  Similarly to the events liaison, those two roles are opt ins."},{"line_number":88,"context_line":""},{"line_number":89,"context_line":"* Meeting Facilitator: The Meeting Facilitator chairs the project\u0027s regular"},{"line_number":90,"context_line":"  periodic meetings and maintains their agenda."},{"line_number":91,"context_line":""},{"line_number":92,"context_line":"* Bug Deputy: Ensures all incoming bugs are triaged."}],"source_content_type":"text/x-rst","patch_set":9,"id":"9f560f44_e5f71d8c","line":89,"range":{"start_line":89,"start_character":58,"end_line":89,"end_character":65},"updated":"2020-08-12 10:53:31.000000000","message":"team","commit_id":"3e9b4b23727cba52abf73c282a3027f230a293d4"},{"author":{"_account_id":13995,"name":"Nate Johnston","email":"nate.johnston@redhat.com","username":"natejohnston"},"change_message_id":"78c9272ada2b798cde4d2267aedfa677eee60573","unresolved":false,"context_lines":[{"line_number":86,"context_line":"  giving/facilitating onboarding sessions during events for its projects\u0027"},{"line_number":87,"context_line":"  community.  Similarly to the events liaison, those two roles are opt ins."},{"line_number":88,"context_line":""},{"line_number":89,"context_line":"* Meeting Facilitator: The Meeting Facilitator chairs the project\u0027s regular"},{"line_number":90,"context_line":"  periodic meetings and maintains their agenda."},{"line_number":91,"context_line":""},{"line_number":92,"context_line":"* Bug Deputy: Ensures all incoming bugs are triaged."}],"source_content_type":"text/x-rst","patch_set":9,"id":"9f560f44_63eca029","line":89,"range":{"start_line":89,"start_character":58,"end_line":89,"end_character":65},"in_reply_to":"9f560f44_e5f71d8c","updated":"2020-08-12 17:25:02.000000000","message":"Done","commit_id":"3e9b4b23727cba52abf73c282a3027f230a293d4"},{"author":{"_account_id":308,"name":"Thierry Carrez","email":"thierry@openstack.org","username":"ttx"},"change_message_id":"e1096c8c73c404a2e98d78daa69b3d9dbf870719","unresolved":false,"context_lines":[{"line_number":117,"context_line":"Points of Concern"},{"line_number":118,"context_line":"-----------------"},{"line_number":119,"context_line":""},{"line_number":120,"context_line":"There are a few places where the projects that choose the distributed leadership"},{"line_number":121,"context_line":"model will need to innovate and solve problems:"},{"line_number":122,"context_line":""},{"line_number":123,"context_line":"* Discoverability: It will be more difficult to know whom to contact for a project."}],"source_content_type":"text/x-rst","patch_set":9,"id":"9f560f44_e53c3d32","line":120,"range":{"start_line":120,"start_character":33,"end_line":120,"end_character":41},"updated":"2020-08-12 10:53:31.000000000","message":"project teams","commit_id":"3e9b4b23727cba52abf73c282a3027f230a293d4"},{"author":{"_account_id":13995,"name":"Nate Johnston","email":"nate.johnston@redhat.com","username":"natejohnston"},"change_message_id":"78c9272ada2b798cde4d2267aedfa677eee60573","unresolved":false,"context_lines":[{"line_number":117,"context_line":"Points of Concern"},{"line_number":118,"context_line":"-----------------"},{"line_number":119,"context_line":""},{"line_number":120,"context_line":"There are a few places where the projects that choose the distributed leadership"},{"line_number":121,"context_line":"model will need to innovate and solve problems:"},{"line_number":122,"context_line":""},{"line_number":123,"context_line":"* Discoverability: It will be more difficult to know whom to contact for a project."}],"source_content_type":"text/x-rst","patch_set":9,"id":"9f560f44_03db247d","line":120,"range":{"start_line":120,"start_character":33,"end_line":120,"end_character":41},"in_reply_to":"9f560f44_e53c3d32","updated":"2020-08-12 17:25:02.000000000","message":"Done","commit_id":"3e9b4b23727cba52abf73c282a3027f230a293d4"},{"author":{"_account_id":308,"name":"Thierry Carrez","email":"thierry@openstack.org","username":"ttx"},"change_message_id":"e1096c8c73c404a2e98d78daa69b3d9dbf870719","unresolved":false,"context_lines":[{"line_number":131,"context_line":"* Minimum Viable: This document is intended to assert the minimum set of roles"},{"line_number":132,"context_line":"  the TC would require to consider the project team to be active and"},{"line_number":133,"context_line":"  functioning.  It is not an exhaustive list of possible roles.  For example,"},{"line_number":134,"context_line":"  a project might assign someone at the end of each cycle to write the cycle"},{"line_number":135,"context_line":"  highlights.  These responsibilities could also be collectively handled by the"},{"line_number":136,"context_line":"  project team, as needed or rotated at intervals.  Teams have the freedom to"},{"line_number":137,"context_line":"  choose what works best for them."}],"source_content_type":"text/x-rst","patch_set":9,"id":"9f560f44_c5393940","line":134,"range":{"start_line":134,"start_character":4,"end_line":134,"end_character":11},"updated":"2020-08-12 10:53:31.000000000","message":"team","commit_id":"3e9b4b23727cba52abf73c282a3027f230a293d4"},{"author":{"_account_id":13995,"name":"Nate Johnston","email":"nate.johnston@redhat.com","username":"natejohnston"},"change_message_id":"78c9272ada2b798cde4d2267aedfa677eee60573","unresolved":false,"context_lines":[{"line_number":131,"context_line":"* Minimum Viable: This document is intended to assert the minimum set of roles"},{"line_number":132,"context_line":"  the TC would require to consider the project team to be active and"},{"line_number":133,"context_line":"  functioning.  It is not an exhaustive list of possible roles.  For example,"},{"line_number":134,"context_line":"  a project might assign someone at the end of each cycle to write the cycle"},{"line_number":135,"context_line":"  highlights.  These responsibilities could also be collectively handled by the"},{"line_number":136,"context_line":"  project team, as needed or rotated at intervals.  Teams have the freedom to"},{"line_number":137,"context_line":"  choose what works best for them."}],"source_content_type":"text/x-rst","patch_set":9,"id":"9f560f44_23e2a830","line":134,"range":{"start_line":134,"start_character":4,"end_line":134,"end_character":11},"in_reply_to":"9f560f44_c5393940","updated":"2020-08-12 17:25:02.000000000","message":"Done","commit_id":"3e9b4b23727cba52abf73c282a3027f230a293d4"},{"author":{"_account_id":308,"name":"Thierry Carrez","email":"thierry@openstack.org","username":"ttx"},"change_message_id":"e1096c8c73c404a2e98d78daa69b3d9dbf870719","unresolved":false,"context_lines":[{"line_number":139,"context_line":"Process for Opting In to Distributed Leadership"},{"line_number":140,"context_line":"-----------------------------------------------"},{"line_number":141,"context_line":""},{"line_number":142,"context_line":"Projects that would like to opt in to a distributed leadership role should make"},{"line_number":143,"context_line":"sure this change has a relative degree of consensus within the project.  To make"},{"line_number":144,"context_line":"the request, a change should be pushed to `projects.yaml` in the"},{"line_number":145,"context_line":"`openstack/governance` repository to add the line \"leadership_type: distributed\""}],"source_content_type":"text/x-rst","patch_set":9,"id":"9f560f44_6512edb6","line":142,"range":{"start_line":142,"start_character":0,"end_line":142,"end_character":8},"updated":"2020-08-12 10:53:31.000000000","message":"Project teams","commit_id":"3e9b4b23727cba52abf73c282a3027f230a293d4"},{"author":{"_account_id":13995,"name":"Nate Johnston","email":"nate.johnston@redhat.com","username":"natejohnston"},"change_message_id":"ab3d4fcad126bae52deefb9d2f92069743db9e2d","unresolved":false,"context_lines":[{"line_number":139,"context_line":"Process for Opting In to Distributed Leadership"},{"line_number":140,"context_line":"-----------------------------------------------"},{"line_number":141,"context_line":""},{"line_number":142,"context_line":"Projects that would like to opt in to a distributed leadership role should make"},{"line_number":143,"context_line":"sure this change has a relative degree of consensus within the project.  To make"},{"line_number":144,"context_line":"the request, a change should be pushed to `projects.yaml` in the"},{"line_number":145,"context_line":"`openstack/governance` repository to add the line \"leadership_type: distributed\""}],"source_content_type":"text/x-rst","patch_set":9,"id":"9f560f44_43bebcff","line":142,"range":{"start_line":142,"start_character":0,"end_line":142,"end_character":8},"in_reply_to":"9f560f44_6512edb6","updated":"2020-08-12 17:28:03.000000000","message":"Done","commit_id":"3e9b4b23727cba52abf73c282a3027f230a293d4"},{"author":{"_account_id":308,"name":"Thierry Carrez","email":"thierry@openstack.org","username":"ttx"},"change_message_id":"e1096c8c73c404a2e98d78daa69b3d9dbf870719","unresolved":false,"context_lines":[{"line_number":140,"context_line":"-----------------------------------------------"},{"line_number":141,"context_line":""},{"line_number":142,"context_line":"Projects that would like to opt in to a distributed leadership role should make"},{"line_number":143,"context_line":"sure this change has a relative degree of consensus within the project.  To make"},{"line_number":144,"context_line":"the request, a change should be pushed to `projects.yaml` in the"},{"line_number":145,"context_line":"`openstack/governance` repository to add the line \"leadership_type: distributed\""},{"line_number":146,"context_line":"to the project\u0027s definition.  The minimum required liaisons will also need to be"}],"source_content_type":"text/x-rst","patch_set":9,"id":"9f560f44_851101b0","line":143,"range":{"start_line":143,"start_character":63,"end_line":143,"end_character":70},"updated":"2020-08-12 10:53:31.000000000","message":"team","commit_id":"3e9b4b23727cba52abf73c282a3027f230a293d4"},{"author":{"_account_id":13995,"name":"Nate Johnston","email":"nate.johnston@redhat.com","username":"natejohnston"},"change_message_id":"ab3d4fcad126bae52deefb9d2f92069743db9e2d","unresolved":false,"context_lines":[{"line_number":140,"context_line":"-----------------------------------------------"},{"line_number":141,"context_line":""},{"line_number":142,"context_line":"Projects that would like to opt in to a distributed leadership role should make"},{"line_number":143,"context_line":"sure this change has a relative degree of consensus within the project.  To make"},{"line_number":144,"context_line":"the request, a change should be pushed to `projects.yaml` in the"},{"line_number":145,"context_line":"`openstack/governance` repository to add the line \"leadership_type: distributed\""},{"line_number":146,"context_line":"to the project\u0027s definition.  The minimum required liaisons will also need to be"}],"source_content_type":"text/x-rst","patch_set":9,"id":"9f560f44_e3c0b07f","line":143,"range":{"start_line":143,"start_character":63,"end_line":143,"end_character":70},"in_reply_to":"9f560f44_851101b0","updated":"2020-08-12 17:28:03.000000000","message":"Done","commit_id":"3e9b4b23727cba52abf73c282a3027f230a293d4"},{"author":{"_account_id":308,"name":"Thierry Carrez","email":"thierry@openstack.org","username":"ttx"},"change_message_id":"e1096c8c73c404a2e98d78daa69b3d9dbf870719","unresolved":false,"context_lines":[{"line_number":158,"context_line":"* The releases liaison will continue to be listed in the `releases` repository,"},{"line_number":159,"context_line":"  to not impact the current delivery of the releases."},{"line_number":160,"context_line":""},{"line_number":161,"context_line":"Once a project has moved to the distributed leadership model, they can revert to"},{"line_number":162,"context_line":"the PTL model by creating a change to `projects.yaml` to remove the"},{"line_number":163,"context_line":"\"leadership_type: distributed\" line in the project\u0027s configuration."},{"line_number":164,"context_line":"This change should have at least a +1 from all the people currently serving as"}],"source_content_type":"text/x-rst","patch_set":9,"id":"9f560f44_2520f5f7","line":161,"range":{"start_line":161,"start_character":7,"end_line":161,"end_character":14},"updated":"2020-08-12 10:53:31.000000000","message":"project team","commit_id":"3e9b4b23727cba52abf73c282a3027f230a293d4"},{"author":{"_account_id":13995,"name":"Nate Johnston","email":"nate.johnston@redhat.com","username":"natejohnston"},"change_message_id":"ab3d4fcad126bae52deefb9d2f92069743db9e2d","unresolved":false,"context_lines":[{"line_number":158,"context_line":"* The releases liaison will continue to be listed in the `releases` repository,"},{"line_number":159,"context_line":"  to not impact the current delivery of the releases."},{"line_number":160,"context_line":""},{"line_number":161,"context_line":"Once a project has moved to the distributed leadership model, they can revert to"},{"line_number":162,"context_line":"the PTL model by creating a change to `projects.yaml` to remove the"},{"line_number":163,"context_line":"\"leadership_type: distributed\" line in the project\u0027s configuration."},{"line_number":164,"context_line":"This change should have at least a +1 from all the people currently serving as"}],"source_content_type":"text/x-rst","patch_set":9,"id":"9f560f44_833574ab","line":161,"range":{"start_line":161,"start_character":7,"end_line":161,"end_character":14},"in_reply_to":"9f560f44_2520f5f7","updated":"2020-08-12 17:28:03.000000000","message":"Done","commit_id":"3e9b4b23727cba52abf73c282a3027f230a293d4"},{"author":{"_account_id":308,"name":"Thierry Carrez","email":"thierry@openstack.org","username":"ttx"},"change_message_id":"e1096c8c73c404a2e98d78daa69b3d9dbf870719","unresolved":false,"context_lines":[{"line_number":166,"context_line":"be in the `governance` repo.  It must also get a +1 from the future PTL,"},{"line_number":167,"context_line":"listed in the same change."},{"line_number":168,"context_line":""},{"line_number":169,"context_line":"A project may change their opt-in status only once a release cycle, to ensure"},{"line_number":170,"context_line":"that the elections officials have clarity on which projects need PTL elections."},{"line_number":171,"context_line":"All requests should be received by week R-5 of the release calendar."},{"line_number":172,"context_line":""}],"source_content_type":"text/x-rst","patch_set":9,"id":"9f560f44_051df1bc","line":169,"range":{"start_line":169,"start_character":2,"end_line":169,"end_character":9},"updated":"2020-08-12 10:53:31.000000000","message":"project team","commit_id":"3e9b4b23727cba52abf73c282a3027f230a293d4"},{"author":{"_account_id":13995,"name":"Nate Johnston","email":"nate.johnston@redhat.com","username":"natejohnston"},"change_message_id":"ab3d4fcad126bae52deefb9d2f92069743db9e2d","unresolved":false,"context_lines":[{"line_number":166,"context_line":"be in the `governance` repo.  It must also get a +1 from the future PTL,"},{"line_number":167,"context_line":"listed in the same change."},{"line_number":168,"context_line":""},{"line_number":169,"context_line":"A project may change their opt-in status only once a release cycle, to ensure"},{"line_number":170,"context_line":"that the elections officials have clarity on which projects need PTL elections."},{"line_number":171,"context_line":"All requests should be received by week R-5 of the release calendar."},{"line_number":172,"context_line":""}],"source_content_type":"text/x-rst","patch_set":9,"id":"9f560f44_43535ce3","line":169,"range":{"start_line":169,"start_character":2,"end_line":169,"end_character":9},"in_reply_to":"9f560f44_051df1bc","updated":"2020-08-12 17:28:03.000000000","message":"Done","commit_id":"3e9b4b23727cba52abf73c282a3027f230a293d4"},{"author":{"_account_id":308,"name":"Thierry Carrez","email":"thierry@openstack.org","username":"ttx"},"change_message_id":"e1096c8c73c404a2e98d78daa69b3d9dbf870719","unresolved":false,"context_lines":[{"line_number":167,"context_line":"listed in the same change."},{"line_number":168,"context_line":""},{"line_number":169,"context_line":"A project may change their opt-in status only once a release cycle, to ensure"},{"line_number":170,"context_line":"that the elections officials have clarity on which projects need PTL elections."},{"line_number":171,"context_line":"All requests should be received by week R-5 of the release calendar."},{"line_number":172,"context_line":""},{"line_number":173,"context_line":"The distributed leadership model is only requested explicitly."}],"source_content_type":"text/x-rst","patch_set":9,"id":"9f560f44_457c09eb","line":170,"range":{"start_line":170,"start_character":51,"end_line":170,"end_character":59},"updated":"2020-08-12 10:53:31.000000000","message":"teams","commit_id":"3e9b4b23727cba52abf73c282a3027f230a293d4"},{"author":{"_account_id":13995,"name":"Nate Johnston","email":"nate.johnston@redhat.com","username":"natejohnston"},"change_message_id":"ab3d4fcad126bae52deefb9d2f92069743db9e2d","unresolved":false,"context_lines":[{"line_number":167,"context_line":"listed in the same change."},{"line_number":168,"context_line":""},{"line_number":169,"context_line":"A project may change their opt-in status only once a release cycle, to ensure"},{"line_number":170,"context_line":"that the elections officials have clarity on which projects need PTL elections."},{"line_number":171,"context_line":"All requests should be received by week R-5 of the release calendar."},{"line_number":172,"context_line":""},{"line_number":173,"context_line":"The distributed leadership model is only requested explicitly."}],"source_content_type":"text/x-rst","patch_set":9,"id":"9f560f44_c33f6c85","line":170,"range":{"start_line":170,"start_character":51,"end_line":170,"end_character":59},"in_reply_to":"9f560f44_457c09eb","updated":"2020-08-12 17:28:03.000000000","message":"Done","commit_id":"3e9b4b23727cba52abf73c282a3027f230a293d4"},{"author":{"_account_id":308,"name":"Thierry Carrez","email":"thierry@openstack.org","username":"ttx"},"change_message_id":"e1096c8c73c404a2e98d78daa69b3d9dbf870719","unresolved":false,"context_lines":[{"line_number":171,"context_line":"All requests should be received by week R-5 of the release calendar."},{"line_number":172,"context_line":""},{"line_number":173,"context_line":"The distributed leadership model is only requested explicitly."},{"line_number":174,"context_line":"If a project has no candidate for PTL, the TC will still evaluate the future"},{"line_number":175,"context_line":"of the project, with now an extra option (on top of stopping the project or"},{"line_number":176,"context_line":"appointing a PTL): convert the project to a distributed leadership with the"},{"line_number":177,"context_line":"help of the project team members."}],"source_content_type":"text/x-rst","patch_set":9,"id":"9f560f44_a581a5c6","line":174,"range":{"start_line":174,"start_character":5,"end_line":174,"end_character":12},"updated":"2020-08-12 10:53:31.000000000","message":"project team","commit_id":"3e9b4b23727cba52abf73c282a3027f230a293d4"},{"author":{"_account_id":13995,"name":"Nate Johnston","email":"nate.johnston@redhat.com","username":"natejohnston"},"change_message_id":"ab3d4fcad126bae52deefb9d2f92069743db9e2d","unresolved":false,"context_lines":[{"line_number":171,"context_line":"All requests should be received by week R-5 of the release calendar."},{"line_number":172,"context_line":""},{"line_number":173,"context_line":"The distributed leadership model is only requested explicitly."},{"line_number":174,"context_line":"If a project has no candidate for PTL, the TC will still evaluate the future"},{"line_number":175,"context_line":"of the project, with now an extra option (on top of stopping the project or"},{"line_number":176,"context_line":"appointing a PTL): convert the project to a distributed leadership with the"},{"line_number":177,"context_line":"help of the project team members."}],"source_content_type":"text/x-rst","patch_set":9,"id":"9f560f44_633ae098","line":174,"range":{"start_line":174,"start_character":5,"end_line":174,"end_character":12},"in_reply_to":"9f560f44_a581a5c6","updated":"2020-08-12 17:28:03.000000000","message":"Done","commit_id":"3e9b4b23727cba52abf73c282a3027f230a293d4"},{"author":{"_account_id":16643,"name":"Goutham Pacha Ravi","email":"gouthampravi@gmail.com","username":"gouthamr"},"change_message_id":"94e6a6da7e8ab5ff9d744831a2954a4504e5a8dc","unresolved":false,"context_lines":[{"line_number":60,"context_line":"Additional recommended roles"},{"line_number":61,"context_line":"~~~~~~~~~~~~~~~~~~~~~~~~~~~~"},{"line_number":62,"context_line":""},{"line_number":63,"context_line":"Any other responsibilities of the PTL that are not addressed above are optional,"},{"line_number":64,"context_line":"and are left to the project teams to determine.  The TC recommends project teams"},{"line_number":65,"context_line":"opting in for distributed project leadership to assign people into the following"},{"line_number":66,"context_line":"optional roles, to each project team\u0027s discretion:"},{"line_number":67,"context_line":""}],"source_content_type":"text/x-rst","patch_set":12,"id":"9f560f44_112e92a4","line":64,"range":{"start_line":63,"start_character":0,"end_line":64,"end_character":47},"updated":"2020-08-17 23:26:54.000000000","message":"If a project does not have a liaison for something in this list, how does someone that\u0027s trying to work with the project coordinate? \n\nDoes it make sense to assign fallbacks to the above required roles for each of the roles below? Or make it a collective responsibility for those picking up the above required roles?","commit_id":"08763131e43d866c40c9c3a7e9a0b6f58693a7f0"},{"author":{"_account_id":308,"name":"Thierry Carrez","email":"thierry@openstack.org","username":"ttx"},"change_message_id":"557b359123ea7162d45a5f2793c65f76780b87ff","unresolved":false,"context_lines":[{"line_number":60,"context_line":"Additional recommended roles"},{"line_number":61,"context_line":"~~~~~~~~~~~~~~~~~~~~~~~~~~~~"},{"line_number":62,"context_line":""},{"line_number":63,"context_line":"Any other responsibilities of the PTL that are not addressed above are optional,"},{"line_number":64,"context_line":"and are left to the project teams to determine.  The TC recommends project teams"},{"line_number":65,"context_line":"opting in for distributed project leadership to assign people into the following"},{"line_number":66,"context_line":"optional roles, to each project team\u0027s discretion:"},{"line_number":67,"context_line":""}],"source_content_type":"text/x-rst","patch_set":12,"id":"9f560f44_a60cc639","line":64,"range":{"start_line":63,"start_character":0,"end_line":64,"end_character":47},"in_reply_to":"9f560f44_112e92a4","updated":"2020-08-18 09:31:26.000000000","message":"I\u0027d say it\u0027s a collective responsibility to take on the additional roles.\n\nThe \"required\" roles are the bare minimum we need for basic accountability in project teams (producing \"openstack\"). The other roles are certainly good to have, but \"openstack\" can survive if they are not filled.","commit_id":"08763131e43d866c40c9c3a7e9a0b6f58693a7f0"},{"author":{"_account_id":17068,"name":"Jean-Philippe Evrard","email":"openstack@a.spamming.party","username":"evrardjp"},"change_message_id":"0bf62e14f6056e631611e4bb7ffee5be66d63608","unresolved":false,"context_lines":[{"line_number":60,"context_line":"Additional recommended roles"},{"line_number":61,"context_line":"~~~~~~~~~~~~~~~~~~~~~~~~~~~~"},{"line_number":62,"context_line":""},{"line_number":63,"context_line":"Any other responsibilities of the PTL that are not addressed above are optional,"},{"line_number":64,"context_line":"and are left to the project teams to determine.  The TC recommends project teams"},{"line_number":65,"context_line":"opting in for distributed project leadership to assign people into the following"},{"line_number":66,"context_line":"optional roles, to each project team\u0027s discretion:"},{"line_number":67,"context_line":""}],"source_content_type":"text/x-rst","patch_set":12,"id":"9f560f44_061bf21a","line":64,"range":{"start_line":63,"start_character":0,"end_line":64,"end_character":47},"in_reply_to":"9f560f44_a60cc639","updated":"2020-08-18 09:59:29.000000000","message":"+1","commit_id":"08763131e43d866c40c9c3a7e9a0b6f58693a7f0"},{"author":{"_account_id":11975,"name":"Slawek Kaplonski","email":"skaplons@redhat.com","username":"slaweq"},"change_message_id":"232cec2f6ed18ec298e00ad703d8720eab559d46","unresolved":false,"context_lines":[{"line_number":97,"context_line":"* RFE Coordinator: This role would involve making sure that blueprint status and"},{"line_number":98,"context_line":"  milestone targets are up to date, that RFEs are triaged and discussed before"},{"line_number":99,"context_line":"  acceptance, and that the tracking LaunchPad or Storyboard items for RFEs are"},{"line_number":100,"context_line":"  properly managed."},{"line_number":101,"context_line":""},{"line_number":102,"context_line":"Liaison selection"},{"line_number":103,"context_line":"~~~~~~~~~~~~~~~~~"}],"source_content_type":"text/x-rst","patch_set":12,"id":"9f560f44_933498e0","line":100,"updated":"2020-08-13 10:31:14.000000000","message":"one minor thing. I\u0027m writing it now as I just got such email from Kendall :)\nSo she emailed me about Neutron question in the user survey. Who should be contact point in such things like user survey in this distributed model?","commit_id":"08763131e43d866c40c9c3a7e9a0b6f58693a7f0"},{"author":{"_account_id":13995,"name":"Nate Johnston","email":"nate.johnston@redhat.com","username":"natejohnston"},"change_message_id":"677781db95ea49fe67b0eb36008499ffdbd6b7d1","unresolved":false,"context_lines":[{"line_number":97,"context_line":"* RFE Coordinator: This role would involve making sure that blueprint status and"},{"line_number":98,"context_line":"  milestone targets are up to date, that RFEs are triaged and discussed before"},{"line_number":99,"context_line":"  acceptance, and that the tracking LaunchPad or Storyboard items for RFEs are"},{"line_number":100,"context_line":"  properly managed."},{"line_number":101,"context_line":""},{"line_number":102,"context_line":"Liaison selection"},{"line_number":103,"context_line":"~~~~~~~~~~~~~~~~~"}],"source_content_type":"text/x-rst","patch_set":12,"id":"9f560f44_3f3f46b6","line":100,"in_reply_to":"9f560f44_022670b8","updated":"2020-08-13 18:08:19.000000000","message":"\u003e this is good point. My opinion is if we have TC liaison   \n \u003e(not is current proposal but that is what I think we \n \u003e should have) then we delegate such duties to that liaison.\n\nIn a nutshell this is my issue with the TC liaison: the position becomes a catch-all for anything not otherwise listed, which effectively makes it a \"PTL-lite\" IMHO.  I think that if there are things needed from the project team that are not handled by a particular liaison, then the first impulse needs to be to go to the project team in general, either by email or adding an item to their weekly IRC meeting.  Perhaps this is overly idealistic of me.\n\nIn addition, perhaps this document should also have a paragraph saying explitly \"An attribute of the PTL system is that there is always a single party that can be counted on to be held responsible to respond to any inquiry.  Moving to a distributed leadership model adds responsibilities not just to the designated liaisons but also every member of the product team to ensure that coordination is socialized, inquiries are answered, and obligations are met, even ones not foreseen by this document.\"","commit_id":"08763131e43d866c40c9c3a7e9a0b6f58693a7f0"},{"author":{"_account_id":17068,"name":"Jean-Philippe Evrard","email":"openstack@a.spamming.party","username":"evrardjp"},"change_message_id":"af4d855c8ccabe5acba4bbbaf0f569f435444308","unresolved":false,"context_lines":[{"line_number":97,"context_line":"* RFE Coordinator: This role would involve making sure that blueprint status and"},{"line_number":98,"context_line":"  milestone targets are up to date, that RFEs are triaged and discussed before"},{"line_number":99,"context_line":"  acceptance, and that the tracking LaunchPad or Storyboard items for RFEs are"},{"line_number":100,"context_line":"  properly managed."},{"line_number":101,"context_line":""},{"line_number":102,"context_line":"Liaison selection"},{"line_number":103,"context_line":"~~~~~~~~~~~~~~~~~"}],"source_content_type":"text/x-rst","patch_set":12,"id":"9f560f44_a2fce43e","line":100,"in_reply_to":"9f560f44_022670b8","updated":"2020-08-13 14:48:00.000000000","message":"I would say that we ping the team, like for the events, and the team decides. Happy to hear your opinions.\n\nI am not sure we need to list _all_ the duties though : )","commit_id":"08763131e43d866c40c9c3a7e9a0b6f58693a7f0"},{"author":{"_account_id":17068,"name":"Jean-Philippe Evrard","email":"openstack@a.spamming.party","username":"evrardjp"},"change_message_id":"0bf62e14f6056e631611e4bb7ffee5be66d63608","unresolved":false,"context_lines":[{"line_number":97,"context_line":"* RFE Coordinator: This role would involve making sure that blueprint status and"},{"line_number":98,"context_line":"  milestone targets are up to date, that RFEs are triaged and discussed before"},{"line_number":99,"context_line":"  acceptance, and that the tracking LaunchPad or Storyboard items for RFEs are"},{"line_number":100,"context_line":"  properly managed."},{"line_number":101,"context_line":""},{"line_number":102,"context_line":"Liaison selection"},{"line_number":103,"context_line":"~~~~~~~~~~~~~~~~~"}],"source_content_type":"text/x-rst","patch_set":12,"id":"9f560f44_662aae2c","line":100,"in_reply_to":"9f560f44_2b2703b9","updated":"2020-08-18 09:59:29.000000000","message":"Thanks :)","commit_id":"08763131e43d866c40c9c3a7e9a0b6f58693a7f0"},{"author":{"_account_id":17068,"name":"Jean-Philippe Evrard","email":"openstack@a.spamming.party","username":"evrardjp"},"change_message_id":"73ee05ec60f3afaafcc3c8b08328ae4326c9aedb","unresolved":false,"context_lines":[{"line_number":97,"context_line":"* RFE Coordinator: This role would involve making sure that blueprint status and"},{"line_number":98,"context_line":"  milestone targets are up to date, that RFEs are triaged and discussed before"},{"line_number":99,"context_line":"  acceptance, and that the tracking LaunchPad or Storyboard items for RFEs are"},{"line_number":100,"context_line":"  properly managed."},{"line_number":101,"context_line":""},{"line_number":102,"context_line":"Liaison selection"},{"line_number":103,"context_line":"~~~~~~~~~~~~~~~~~"}],"source_content_type":"text/x-rst","patch_set":12,"id":"9f560f44_c54bd8ad","line":100,"in_reply_to":"9f560f44_3f3f46b6","updated":"2020-08-14 06:48:18.000000000","message":"That\u0027s what I meant with the \"Any other responsibilities of the PTL that are not addressed above are optional,\nand are left to the project teams to determine.\"\n\nBut if it helps on clarity, let\u0027s reword on L63.","commit_id":"08763131e43d866c40c9c3a7e9a0b6f58693a7f0"},{"author":{"_account_id":8556,"name":"Ghanshyam Maan","display_name":"Ghanshyam Maan","email":"gmaan.os14@gmail.com","username":"ghanshyam"},"change_message_id":"dac7944eae50aa234f963dda013ef2fac3a664a7","unresolved":false,"context_lines":[{"line_number":97,"context_line":"* RFE Coordinator: This role would involve making sure that blueprint status and"},{"line_number":98,"context_line":"  milestone targets are up to date, that RFEs are triaged and discussed before"},{"line_number":99,"context_line":"  acceptance, and that the tracking LaunchPad or Storyboard items for RFEs are"},{"line_number":100,"context_line":"  properly managed."},{"line_number":101,"context_line":""},{"line_number":102,"context_line":"Liaison selection"},{"line_number":103,"context_line":"~~~~~~~~~~~~~~~~~"}],"source_content_type":"text/x-rst","patch_set":12,"id":"9f560f44_022670b8","line":100,"in_reply_to":"9f560f44_933498e0","updated":"2020-08-13 14:08:13.000000000","message":"this is good point. My opinion is if we have TC liaison (not is current proposal but that is what I think we should have) then we delegate such duties to that liaison.","commit_id":"08763131e43d866c40c9c3a7e9a0b6f58693a7f0"},{"author":{"_account_id":11975,"name":"Slawek Kaplonski","email":"skaplons@redhat.com","username":"slaweq"},"change_message_id":"ef2e6f701a633ac2b256ccdcd26eb0df6c1c07a4","unresolved":false,"context_lines":[{"line_number":97,"context_line":"* RFE Coordinator: This role would involve making sure that blueprint status and"},{"line_number":98,"context_line":"  milestone targets are up to date, that RFEs are triaged and discussed before"},{"line_number":99,"context_line":"  acceptance, and that the tracking LaunchPad or Storyboard items for RFEs are"},{"line_number":100,"context_line":"  properly managed."},{"line_number":101,"context_line":""},{"line_number":102,"context_line":"Liaison selection"},{"line_number":103,"context_line":"~~~~~~~~~~~~~~~~~"}],"source_content_type":"text/x-rst","patch_set":12,"id":"9f560f44_2b2703b9","line":100,"in_reply_to":"9f560f44_c54bd8ad","updated":"2020-08-14 09:13:26.000000000","message":"I\u0027m totally fine with that :)\nI just wanted to ensure that things like that aren\u0027t forgotten and that\u0027s all.","commit_id":"08763131e43d866c40c9c3a7e9a0b6f58693a7f0"},{"author":{"_account_id":16643,"name":"Goutham Pacha Ravi","email":"gouthampravi@gmail.com","username":"gouthamr"},"change_message_id":"94e6a6da7e8ab5ff9d744831a2954a4504e5a8dc","unresolved":false,"context_lines":[{"line_number":98,"context_line":"  milestone targets are up to date, that RFEs are triaged and discussed before"},{"line_number":99,"context_line":"  acceptance, and that the tracking LaunchPad or Storyboard items for RFEs are"},{"line_number":100,"context_line":"  properly managed."},{"line_number":101,"context_line":""},{"line_number":102,"context_line":"Liaison selection"},{"line_number":103,"context_line":"~~~~~~~~~~~~~~~~~"},{"line_number":104,"context_line":""}],"source_content_type":"text/x-rst","patch_set":12,"id":"9f560f44_740b7c23","line":101,"range":{"start_line":101,"start_character":0,"end_line":101,"end_character":0},"updated":"2020-08-17 23:26:54.000000000","message":"How does this document alter current \"Cross Project Liaisons\" effort? Missing someone who can do:\n- Vetting of cross project documentation (docs liaison would handle this)\n- Submit cycle highlights","commit_id":"08763131e43d866c40c9c3a7e9a0b6f58693a7f0"},{"author":{"_account_id":308,"name":"Thierry Carrez","email":"thierry@openstack.org","username":"ttx"},"change_message_id":"557b359123ea7162d45a5f2793c65f76780b87ff","unresolved":false,"context_lines":[{"line_number":98,"context_line":"  milestone targets are up to date, that RFEs are triaged and discussed before"},{"line_number":99,"context_line":"  acceptance, and that the tracking LaunchPad or Storyboard items for RFEs are"},{"line_number":100,"context_line":"  properly managed."},{"line_number":101,"context_line":""},{"line_number":102,"context_line":"Liaison selection"},{"line_number":103,"context_line":"~~~~~~~~~~~~~~~~~"},{"line_number":104,"context_line":""}],"source_content_type":"text/x-rst","patch_set":12,"id":"9f560f44_c63a9acb","line":101,"range":{"start_line":101,"start_character":0,"end_line":101,"end_character":0},"in_reply_to":"9f560f44_740b7c23","updated":"2020-08-18 09:31:26.000000000","message":"Re: cycle-highlights, I\u0027d say that\u0027s part of the release liaison role.","commit_id":"08763131e43d866c40c9c3a7e9a0b6f58693a7f0"},{"author":{"_account_id":17068,"name":"Jean-Philippe Evrard","email":"openstack@a.spamming.party","username":"evrardjp"},"change_message_id":"0bf62e14f6056e631611e4bb7ffee5be66d63608","unresolved":false,"context_lines":[{"line_number":98,"context_line":"  milestone targets are up to date, that RFEs are triaged and discussed before"},{"line_number":99,"context_line":"  acceptance, and that the tracking LaunchPad or Storyboard items for RFEs are"},{"line_number":100,"context_line":"  properly managed."},{"line_number":101,"context_line":""},{"line_number":102,"context_line":"Liaison selection"},{"line_number":103,"context_line":"~~~~~~~~~~~~~~~~~"},{"line_number":104,"context_line":""}],"source_content_type":"text/x-rst","patch_set":12,"id":"9f560f44_e6151ee7","line":101,"range":{"start_line":101,"start_character":0,"end_line":101,"end_character":0},"in_reply_to":"9f560f44_c63a9acb","updated":"2020-08-18 09:59:29.000000000","message":"I agree there.\n\nFor cross project liaisons, would it be ok on a case by case basis? Or do you feel the need that all the teams must be ready to have someone ready for that? IMO, the documentation is now the responsibility of everyone. When the release liaison votes for a release, it _ensures_ the software is properly documented.","commit_id":"08763131e43d866c40c9c3a7e9a0b6f58693a7f0"},{"author":{"_account_id":11975,"name":"Slawek Kaplonski","email":"skaplons@redhat.com","username":"slaweq"},"change_message_id":"232cec2f6ed18ec298e00ad703d8720eab559d46","unresolved":false,"context_lines":[{"line_number":123,"context_line":"There are a few places where the project teams that choose the distributed"},{"line_number":124,"context_line":"leadership model will need to innovate and solve problems:"},{"line_number":125,"context_line":""},{"line_number":126,"context_line":"* Discoverability: It will make harder to know whom to contact for a project team."},{"line_number":127,"context_line":"* Distributed Consensus: With an increased number of people accountable for"},{"line_number":128,"context_line":"  aspects of the project team, the potential for miscommunications increases."},{"line_number":129,"context_line":"* Unclear responsibilities: As a project team moves to the distributed leadership"}],"source_content_type":"text/x-rst","patch_set":12,"id":"9f560f44_13f24807","line":126,"updated":"2020-08-13 10:31:14.000000000","message":"maybe one additional liaison could be defined, something like \"Spokesmann\" :)","commit_id":"08763131e43d866c40c9c3a7e9a0b6f58693a7f0"},{"author":{"_account_id":17068,"name":"Jean-Philippe Evrard","email":"openstack@a.spamming.party","username":"evrardjp"},"change_message_id":"73ee05ec60f3afaafcc3c8b08328ae4326c9aedb","unresolved":false,"context_lines":[{"line_number":123,"context_line":"There are a few places where the project teams that choose the distributed"},{"line_number":124,"context_line":"leadership model will need to innovate and solve problems:"},{"line_number":125,"context_line":""},{"line_number":126,"context_line":"* Discoverability: It will make harder to know whom to contact for a project team."},{"line_number":127,"context_line":"* Distributed Consensus: With an increased number of people accountable for"},{"line_number":128,"context_line":"  aspects of the project team, the potential for miscommunications increases."},{"line_number":129,"context_line":"* Unclear responsibilities: As a project team moves to the distributed leadership"}],"source_content_type":"text/x-rst","patch_set":12,"id":"9f560f44_85d600c3","line":126,"in_reply_to":"9f560f44_13f24807","updated":"2020-08-14 06:48:18.000000000","message":"Or spokeswoman, or ... : )\n\nBut tbh,  I prefer if we didn\u0027t have that, as it will look like a PTL-lite solution :p\n\nI was really hoping we could do more things distributed.","commit_id":"08763131e43d866c40c9c3a7e9a0b6f58693a7f0"},{"author":{"_account_id":8449,"name":"Marios Andreou","email":"marios.andreou@gmail.com","username":"marios"},"change_message_id":"860380327e86002dab286b810fd4afed2d29c2a1","unresolved":false,"context_lines":[{"line_number":123,"context_line":"There are a few places where the project teams that choose the distributed"},{"line_number":124,"context_line":"leadership model will need to innovate and solve problems:"},{"line_number":125,"context_line":""},{"line_number":126,"context_line":"* Discoverability: It will make harder to know whom to contact for a project team."},{"line_number":127,"context_line":"* Distributed Consensus: With an increased number of people accountable for"},{"line_number":128,"context_line":"  aspects of the project team, the potential for miscommunications increases."},{"line_number":129,"context_line":"* Unclear responsibilities: As a project team moves to the distributed leadership"}],"source_content_type":"text/x-rst","patch_set":12,"id":"9f560f44_52c32358","line":126,"in_reply_to":"9f560f44_85d600c3","updated":"2020-09-15 07:17:30.000000000","message":"I think that is addressed by line 27 above \"The PTL remains the single point of contact and responsibility for\nall the duties.\" i.e. we still have a person assigned as PTL in order to be accountable for and coordinate the liaisons. \n\nEach project should have the PTL membership (ie. PTL + liaisons) documented in an obvious place but otherwise the PTL can always act as a first point of contact when you don\u0027t know who to ping specifically.","commit_id":"08763131e43d866c40c9c3a7e9a0b6f58693a7f0"}]}