)]}'
{"/PATCHSET_LEVEL":[{"author":{"_account_id":5263,"name":"Jeremy Stanley","display_name":"fungi","email":"fungi@yuggoth.org","username":"fungi","status":"missing, presumed fed"},"change_message_id":"cfdd4884ec33dbd0eae1671ff0e9fc862fedd68f","unresolved":true,"context_lines":[],"source_content_type":"","patch_set":2,"id":"647c5e96_6fd4e9eb","updated":"2026-09-10 17:12:18.000000000","message":"ai;dr (I lost patience about 100 lines into the new document.)\n\nI feel like this is duplicative both of the TC Charter and Project Teams Guide PTL chapter. The charter already grants PTLs complete control, so any attempts to then spell that out under the guise of governance only serves to potentially constrain their role. Documentation about actions the TC mandates are appropriate for governance, anything beyond that (like explaining what PTLs usually do and things they consider) are best maintained in a non-governance document.","commit_id":"234e9c33bc87325f3e7c1c351959891060aa3b41"},{"author":{"_account_id":15334,"name":"Stephen Finucane","display_name":"stephenfin","email":"stephenfin@redhat.com","username":"sfinucan"},"change_message_id":"51cacc7e48ebfb36bfc6035433d6687f46792777","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":2,"id":"381d4aea_52768cce","in_reply_to":"647c5e96_6fd4e9eb","updated":"2026-09-11 12:32:47.000000000","message":"As you\u0027ve seen, I\u0027ve dropped pretty much all of the duplicated content in favor of a pointer to the project-config","commit_id":"234e9c33bc87325f3e7c1c351959891060aa3b41"},{"author":{"_account_id":11604,"name":"sean mooney","email":"smooney@redhat.com","username":"sean-k-mooney"},"change_message_id":"82bee08cf64c6bb2d832a17982d9fb09575d0dd4","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":3,"id":"6e6d3eca_ad0688c6","updated":"2026-09-11 07:16:06.000000000","message":"by the way none of the comment i left in line shoudl prevent this form progressing\n\nbut i think we can imporve the doc if it is revised","commit_id":"bf0998cebe40383118e4aa21662684faa7a39740"},{"author":{"_account_id":11604,"name":"sean mooney","email":"smooney@redhat.com","username":"sean-k-mooney"},"change_message_id":"72a06babd5a3c127c6c5a732691af0fcd13dff85","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":5,"id":"5da8d792_8f078761","updated":"2026-09-11 16:39:43.000000000","message":"thanks looks good to me too","commit_id":"3b5400f14e151c15bcfa34237238b7d832df4b0b"}],"reference/distributed-project-leadership.rst":[{"author":{"_account_id":11604,"name":"sean mooney","email":"smooney@redhat.com","username":"sean-k-mooney"},"change_message_id":"80775ed4f5330b30f9f72d2a3a6216081d1f09bd","unresolved":true,"context_lines":[{"line_number":28,"context_line":"The project teams are expected to have at least the following required liaison"},{"line_number":29,"context_line":"roles:"},{"line_number":30,"context_line":""},{"line_number":31,"context_line":"* *Release liaison*: The :repo:`openstack/governance/src/branch/master/reference/projects.yaml`"},{"line_number":32,"context_line":"  is responsible for requesting releases for deliverables produced by the"},{"line_number":33,"context_line":"  project team.  In addition, release liaisons generally review requests for"},{"line_number":34,"context_line":"  Feature Freeze Exception (FFE)."}],"source_content_type":"text/x-rst","patch_set":3,"id":"0261ba05_f6330fdb","line":31,"range":{"start_line":31,"start_character":2,"end_line":31,"end_character":19},"updated":"2026-09-10 21:00:44.000000000","message":"femto-nit: i try to aovid `*` in favor of ` `` ` \npreferint the litral syntax over build as i fine the usage of `*` more confusing sepcicly when switching between rst and markdown lately.","commit_id":"bf0998cebe40383118e4aa21662684faa7a39740"},{"author":{"_account_id":15334,"name":"Stephen Finucane","display_name":"stephenfin","email":"stephenfin@redhat.com","username":"sfinucan"},"change_message_id":"7c5b88f746bf735b89cc18cca6d5ef9ecea84e49","unresolved":false,"context_lines":[{"line_number":28,"context_line":"The project teams are expected to have at least the following required liaison"},{"line_number":29,"context_line":"roles:"},{"line_number":30,"context_line":""},{"line_number":31,"context_line":"* *Release liaison*: The :repo:`openstack/governance/src/branch/master/reference/projects.yaml`"},{"line_number":32,"context_line":"  is responsible for requesting releases for deliverables produced by the"},{"line_number":33,"context_line":"  project team.  In addition, release liaisons generally review requests for"},{"line_number":34,"context_line":"  Feature Freeze Exception (FFE)."}],"source_content_type":"text/x-rst","patch_set":3,"id":"83e232f0_806c669f","line":31,"range":{"start_line":31,"start_character":2,"end_line":31,"end_character":19},"in_reply_to":"0261ba05_f6330fdb","updated":"2026-09-11 10:39:14.000000000","message":"They\u0027re different things. `*` is *emphasis* (a.k.a. *italics*; not confused with **strong emphasis**) for both [reStructuredText](https://www.sphinx-doc.org/en/master/usage/restructuredtext/basics.html#inline-markup) and [Markdown](https://spec.commonmark.org/0.31.2/#emphasis-and-strong-emphasis). ` `` ` is for `literals`, like `PythonSymbol` or `a-command --help`. This is intended to be emphasis and not literals since these aren\u0027t symbols.","commit_id":"bf0998cebe40383118e4aa21662684faa7a39740"},{"author":{"_account_id":11604,"name":"sean mooney","email":"smooney@redhat.com","username":"sean-k-mooney"},"change_message_id":"99242574cfb60c51f6ecf1ee40e81c73e69637b1","unresolved":false,"context_lines":[{"line_number":28,"context_line":"The project teams are expected to have at least the following required liaison"},{"line_number":29,"context_line":"roles:"},{"line_number":30,"context_line":""},{"line_number":31,"context_line":"* *Release liaison*: The :repo:`openstack/governance/src/branch/master/reference/projects.yaml`"},{"line_number":32,"context_line":"  is responsible for requesting releases for deliverables produced by the"},{"line_number":33,"context_line":"  project team.  In addition, release liaisons generally review requests for"},{"line_number":34,"context_line":"  Feature Freeze Exception (FFE)."}],"source_content_type":"text/x-rst","patch_set":3,"id":"45d0cd89_3aebe2b6","line":31,"range":{"start_line":31,"start_character":2,"end_line":31,"end_character":19},"in_reply_to":"83e232f0_806c669f","updated":"2026-09-11 10:48:08.000000000","message":"ok i really dont think this shoudl be italicieed tha tmakes it harder to read in my opion\nagain it sa styl enice but the fact that i cna never remvoerb if its bold or italice is one fo the reaosn i dislike using *\n\nagain you dont have to change this but i really dont like using italics for anythign in our docs but that is just a prefence\n\ni personally find it harder to read so i personally avoid using them i also alwasy interpete italics as soemthng that has less emphasis then normal text i.e. thing that you shoudl be able ot ignore not thing that are imporant","commit_id":"bf0998cebe40383118e4aa21662684faa7a39740"}],"reference/incubation-integration-requirements.rst":[{"author":{"_account_id":16643,"name":"Goutham Pacha Ravi","email":"gouthampravi@gmail.com","username":"gouthamr"},"change_message_id":"df9db2b70703c3a1c3dfde30f47fa812dc811fcd","unresolved":true,"context_lines":[],"source_content_type":"","patch_set":2,"id":"091d0ecb_7626cb21","updated":"2026-09-10 17:02:52.000000000","message":"This update is harmless, but,this is an outdated document and we must flag its retirement.","commit_id":"234e9c33bc87325f3e7c1c351959891060aa3b41"},{"author":{"_account_id":15334,"name":"Stephen Finucane","display_name":"stephenfin","email":"stephenfin@redhat.com","username":"sfinucan"},"change_message_id":"7c5b88f746bf735b89cc18cca6d5ef9ecea84e49","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":2,"id":"bb2aa819_7bf656f8","in_reply_to":"091d0ecb_7626cb21","updated":"2026-09-11 10:39:14.000000000","message":"Acknowledged","commit_id":"234e9c33bc87325f3e7c1c351959891060aa3b41"}],"reference/project-leadership.rst":[{"author":{"_account_id":5263,"name":"Jeremy Stanley","display_name":"fungi","email":"fungi@yuggoth.org","username":"fungi","status":"missing, presumed fed"},"change_message_id":"cfdd4884ec33dbd0eae1671ff0e9fc862fedd68f","unresolved":true,"context_lines":[{"line_number":23,"context_line":""},{"line_number":24,"context_line":"The :doc:`charter \u003ccharter\u003e` defines the PTL\u0027s core authority concisely:"},{"line_number":25,"context_line":""},{"line_number":26,"context_line":"    Project Team Leads (\"PTLs\") manage day-to-day operations, drive the team"},{"line_number":27,"context_line":"    goals and resolve technical disputes within their team. Each team should be"},{"line_number":28,"context_line":"    self-managing by the contributors, and all disputes should be resolved"},{"line_number":29,"context_line":"    through active debate and discussion by the community itself. However if a"},{"line_number":30,"context_line":"    given debate cannot be clearly resolved, the PTL can decide the outcome."},{"line_number":31,"context_line":""},{"line_number":32,"context_line":"Beyond that formal definition, the PTL serves as the primary external face of"},{"line_number":33,"context_line":"the project: the person other contributors, SIGs, and the TC go to first when"}],"source_content_type":"text/x-rst","patch_set":2,"id":"90ceb785_d0c5cf20","line":30,"range":{"start_line":26,"start_character":0,"end_line":30,"end_character":76},"updated":"2026-09-10 17:12:18.000000000","message":"It would be kind of annoying to need to edit this copy when the charter is reworded, but is more likely to get forgotten instead and then diverge in confusing ways.","commit_id":"234e9c33bc87325f3e7c1c351959891060aa3b41"},{"author":{"_account_id":16643,"name":"Goutham Pacha Ravi","email":"gouthampravi@gmail.com","username":"gouthamr"},"change_message_id":"df9db2b70703c3a1c3dfde30f47fa812dc811fcd","unresolved":true,"context_lines":[{"line_number":23,"context_line":""},{"line_number":24,"context_line":"The :doc:`charter \u003ccharter\u003e` defines the PTL\u0027s core authority concisely:"},{"line_number":25,"context_line":""},{"line_number":26,"context_line":"    Project Team Leads (\"PTLs\") manage day-to-day operations, drive the team"},{"line_number":27,"context_line":"    goals and resolve technical disputes within their team. Each team should be"},{"line_number":28,"context_line":"    self-managing by the contributors, and all disputes should be resolved"},{"line_number":29,"context_line":"    through active debate and discussion by the community itself. However if a"},{"line_number":30,"context_line":"    given debate cannot be clearly resolved, the PTL can decide the outcome."},{"line_number":31,"context_line":""},{"line_number":32,"context_line":"Beyond that formal definition, the PTL serves as the primary external face of"},{"line_number":33,"context_line":"the project: the person other contributors, SIGs, and the TC go to first when"}],"source_content_type":"text/x-rst","patch_set":2,"id":"86e8810c_cd871cb0","line":30,"range":{"start_line":26,"start_character":0,"end_line":30,"end_character":76},"updated":"2026-09-10 17:02:52.000000000","message":"please link instead of repeating in case this ever drifts.","commit_id":"234e9c33bc87325f3e7c1c351959891060aa3b41"},{"author":{"_account_id":15334,"name":"Stephen Finucane","display_name":"stephenfin","email":"stephenfin@redhat.com","username":"sfinucan"},"change_message_id":"15ca8acd711edea4be3456431bf2f179869570a2","unresolved":false,"context_lines":[{"line_number":23,"context_line":""},{"line_number":24,"context_line":"The :doc:`charter \u003ccharter\u003e` defines the PTL\u0027s core authority concisely:"},{"line_number":25,"context_line":""},{"line_number":26,"context_line":"    Project Team Leads (\"PTLs\") manage day-to-day operations, drive the team"},{"line_number":27,"context_line":"    goals and resolve technical disputes within their team. Each team should be"},{"line_number":28,"context_line":"    self-managing by the contributors, and all disputes should be resolved"},{"line_number":29,"context_line":"    through active debate and discussion by the community itself. However if a"},{"line_number":30,"context_line":"    given debate cannot be clearly resolved, the PTL can decide the outcome."},{"line_number":31,"context_line":""},{"line_number":32,"context_line":"Beyond that formal definition, the PTL serves as the primary external face of"},{"line_number":33,"context_line":"the project: the person other contributors, SIGs, and the TC go to first when"}],"source_content_type":"text/x-rst","patch_set":2,"id":"9cc62ba4_b43922a4","line":30,"range":{"start_line":26,"start_character":0,"end_line":30,"end_character":76},"in_reply_to":"86e8810c_cd871cb0","updated":"2026-09-10 18:13:13.000000000","message":"Good call. Done.","commit_id":"234e9c33bc87325f3e7c1c351959891060aa3b41"},{"author":{"_account_id":15334,"name":"Stephen Finucane","display_name":"stephenfin","email":"stephenfin@redhat.com","username":"sfinucan"},"change_message_id":"15ca8acd711edea4be3456431bf2f179869570a2","unresolved":false,"context_lines":[{"line_number":23,"context_line":""},{"line_number":24,"context_line":"The :doc:`charter \u003ccharter\u003e` defines the PTL\u0027s core authority concisely:"},{"line_number":25,"context_line":""},{"line_number":26,"context_line":"    Project Team Leads (\"PTLs\") manage day-to-day operations, drive the team"},{"line_number":27,"context_line":"    goals and resolve technical disputes within their team. Each team should be"},{"line_number":28,"context_line":"    self-managing by the contributors, and all disputes should be resolved"},{"line_number":29,"context_line":"    through active debate and discussion by the community itself. However if a"},{"line_number":30,"context_line":"    given debate cannot be clearly resolved, the PTL can decide the outcome."},{"line_number":31,"context_line":""},{"line_number":32,"context_line":"Beyond that formal definition, the PTL serves as the primary external face of"},{"line_number":33,"context_line":"the project: the person other contributors, SIGs, and the TC go to first when"}],"source_content_type":"text/x-rst","patch_set":2,"id":"acf08215_bb733005","line":30,"range":{"start_line":26,"start_character":0,"end_line":30,"end_character":76},"in_reply_to":"90ceb785_d0c5cf20","updated":"2026-09-10 18:13:13.000000000","message":"Done","commit_id":"234e9c33bc87325f3e7c1c351959891060aa3b41"},{"author":{"_account_id":16643,"name":"Goutham Pacha Ravi","email":"gouthampravi@gmail.com","username":"gouthamr"},"change_message_id":"df9db2b70703c3a1c3dfde30f47fa812dc811fcd","unresolved":true,"context_lines":[{"line_number":35,"context_line":"facilitation at least as much as it is one of decision-making authority."},{"line_number":36,"context_line":""},{"line_number":37,"context_line":"The scope of what the PTL actually does day-to-day varies significantly between"},{"line_number":38,"context_line":"project teams. Large, active teams may have the PTL focus primarily on"},{"line_number":39,"context_line":"coordination and delegation, while smaller teams may have the PTL more directly"},{"line_number":40,"context_line":"involved in every aspect of operations. PTLs are strongly encouraged to"},{"line_number":41,"context_line":"delegate responsibilities wherever they can, to avoid the role becoming a"}],"source_content_type":"text/x-rst","patch_set":2,"id":"d7c463d5_669c2c33","line":38,"range":{"start_line":38,"start_character":15,"end_line":38,"end_character":28},"updated":"2026-09-10 17:02:52.000000000","message":"Larger\n\n\nactivity doesn\u0027t have much to do with the need for delegation.","commit_id":"234e9c33bc87325f3e7c1c351959891060aa3b41"},{"author":{"_account_id":15334,"name":"Stephen Finucane","display_name":"stephenfin","email":"stephenfin@redhat.com","username":"sfinucan"},"change_message_id":"15ca8acd711edea4be3456431bf2f179869570a2","unresolved":false,"context_lines":[{"line_number":35,"context_line":"facilitation at least as much as it is one of decision-making authority."},{"line_number":36,"context_line":""},{"line_number":37,"context_line":"The scope of what the PTL actually does day-to-day varies significantly between"},{"line_number":38,"context_line":"project teams. Large, active teams may have the PTL focus primarily on"},{"line_number":39,"context_line":"coordination and delegation, while smaller teams may have the PTL more directly"},{"line_number":40,"context_line":"involved in every aspect of operations. PTLs are strongly encouraged to"},{"line_number":41,"context_line":"delegate responsibilities wherever they can, to avoid the role becoming a"}],"source_content_type":"text/x-rst","patch_set":2,"id":"1468479e_51991e5c","line":38,"range":{"start_line":38,"start_character":15,"end_line":38,"end_character":28},"in_reply_to":"d7c463d5_669c2c33","updated":"2026-09-10 18:13:13.000000000","message":"Done","commit_id":"234e9c33bc87325f3e7c1c351959891060aa3b41"},{"author":{"_account_id":5263,"name":"Jeremy Stanley","display_name":"fungi","email":"fungi@yuggoth.org","username":"fungi","status":"missing, presumed fed"},"change_message_id":"cfdd4884ec33dbd0eae1671ff0e9fc862fedd68f","unresolved":true,"context_lines":[{"line_number":46,"context_line":""},{"line_number":47,"context_line":"PTL seats are renewed every development cycle. A separate election is run for"},{"line_number":48,"context_line":"each project team. The full election rules are specified in the :doc:`charter"},{"line_number":49,"context_line":"\u003ccharter\u003e`. In summary:"},{"line_number":50,"context_line":""},{"line_number":51,"context_line":"* Any Active Project Contributor (APC) may stand as a candidate. An APC is an"},{"line_number":52,"context_line":"  Individual Member of the OpenStack Foundation who committed a change to or"}],"source_content_type":"text/x-rst","patch_set":2,"id":"2b1da620_aef6c16c","line":49,"range":{"start_line":49,"start_character":15,"end_line":49,"end_character":22},"updated":"2026-09-10 17:12:18.000000000","message":"This is an imprecise definition which could mislead some readers and result in confusion. It would be best to be clear it\u0027s an over-simplification and not merely a summary.","commit_id":"234e9c33bc87325f3e7c1c351959891060aa3b41"},{"author":{"_account_id":15334,"name":"Stephen Finucane","display_name":"stephenfin","email":"stephenfin@redhat.com","username":"sfinucan"},"change_message_id":"15ca8acd711edea4be3456431bf2f179869570a2","unresolved":false,"context_lines":[{"line_number":46,"context_line":""},{"line_number":47,"context_line":"PTL seats are renewed every development cycle. A separate election is run for"},{"line_number":48,"context_line":"each project team. The full election rules are specified in the :doc:`charter"},{"line_number":49,"context_line":"\u003ccharter\u003e`. In summary:"},{"line_number":50,"context_line":""},{"line_number":51,"context_line":"* Any Active Project Contributor (APC) may stand as a candidate. An APC is an"},{"line_number":52,"context_line":"  Individual Member of the OpenStack Foundation who committed a change to or"}],"source_content_type":"text/x-rst","patch_set":2,"id":"37c6203d_6f5a8ca2","line":49,"range":{"start_line":49,"start_character":15,"end_line":49,"end_character":22},"in_reply_to":"2b1da620_aef6c16c","updated":"2026-09-10 18:13:13.000000000","message":"I\u0027ve dropped this in favor of a link to the relevant charter section.","commit_id":"234e9c33bc87325f3e7c1c351959891060aa3b41"},{"author":{"_account_id":16643,"name":"Goutham Pacha Ravi","email":"gouthampravi@gmail.com","username":"gouthamr"},"change_message_id":"df9db2b70703c3a1c3dfde30f47fa812dc811fcd","unresolved":true,"context_lines":[{"line_number":74,"context_line":"Any exceptions to the PTL election schedule are recorded in"},{"line_number":75,"context_line":":doc:`election-exceptions`."},{"line_number":76,"context_line":""},{"line_number":77,"context_line":"Responsibilities"},{"line_number":78,"context_line":"----------------"},{"line_number":79,"context_line":""},{"line_number":80,"context_line":"Recurrent duties"},{"line_number":81,"context_line":"~~~~~~~~~~~~~~~~"}],"source_content_type":"text/x-rst","patch_set":2,"id":"168585b1_ff7aa1d4","line":78,"range":{"start_line":77,"start_character":0,"end_line":78,"end_character":16},"updated":"2026-09-10 17:02:52.000000000","message":"Was your intention to spell out the absolute minimum here?\n\nBecause of the dynamic nature of this, we incorporated this into the project-team-guide. If we did add the content below here, we\u0027ll have duplicated the content between the two places and any changes will have to be in two places instead of one. \n\nI would be in favor of \"legitimizing\" the guideline in the project-team-guide\" by linking that here. The TC is the primary maintainer of the project team guide as well.\n\nI see that some members of the TC feel that the \"governance\" repo should be where we define \"rules\" and the project-team-guide isn\u0027t. I think we should apply nuance to this. I think defining _every_ task below as a \"rule\" takes away the independence that the TC has given project teams. Project teams were encouraged through a past TC goal to spell out the PTL tasks: https://governance.openstack.org/tc/goals/completed/ussuri/project-ptl-and-contrib-docs.html\n\nThrough this, each project team at the time took the primary project-team-guide and implemented their specific tasks and wrote up a document that lives in the contributor guide for the project. My suspicion is that established practices may already drift from the rules we\u0027re trying to codify here.","commit_id":"234e9c33bc87325f3e7c1c351959891060aa3b41"},{"author":{"_account_id":15334,"name":"Stephen Finucane","display_name":"stephenfin","email":"stephenfin@redhat.com","username":"sfinucan"},"change_message_id":"15ca8acd711edea4be3456431bf2f179869570a2","unresolved":false,"context_lines":[{"line_number":74,"context_line":"Any exceptions to the PTL election schedule are recorded in"},{"line_number":75,"context_line":":doc:`election-exceptions`."},{"line_number":76,"context_line":""},{"line_number":77,"context_line":"Responsibilities"},{"line_number":78,"context_line":"----------------"},{"line_number":79,"context_line":""},{"line_number":80,"context_line":"Recurrent duties"},{"line_number":81,"context_line":"~~~~~~~~~~~~~~~~"}],"source_content_type":"text/x-rst","patch_set":2,"id":"c97bec67_d523380e","line":78,"range":{"start_line":77,"start_character":0,"end_line":78,"end_character":16},"in_reply_to":"168585b1_ff7aa1d4","updated":"2026-09-10 18:13:13.000000000","message":"I thought it acceptable to list the roles here because we had already spelled them out in the DPL guide. I\u0027ve simplified this section in PS3 and am happy to remove it in a future PS, but I think we should probably consider migrating some of the DPL content across also if we opt to do this.","commit_id":"234e9c33bc87325f3e7c1c351959891060aa3b41"},{"author":{"_account_id":5263,"name":"Jeremy Stanley","display_name":"fungi","email":"fungi@yuggoth.org","username":"fungi","status":"missing, presumed fed"},"change_message_id":"cfdd4884ec33dbd0eae1671ff0e9fc862fedd68f","unresolved":true,"context_lines":[{"line_number":80,"context_line":"Recurrent duties"},{"line_number":81,"context_line":"~~~~~~~~~~~~~~~~"},{"line_number":82,"context_line":""},{"line_number":83,"context_line":"The following are the standing responsibilities a PTL is expected to keep on"},{"line_number":84,"context_line":"top of throughout a cycle. Many of these can be delegated (see"},{"line_number":85,"context_line":"`Liaison roles`_ and `Core team management`_ below), but the PTL retains"},{"line_number":86,"context_line":"overall accountability."},{"line_number":87,"context_line":""}],"source_content_type":"text/x-rst","patch_set":2,"id":"83cfe18a_da7c746b","line":84,"range":{"start_line":83,"start_character":0,"end_line":84,"end_character":26},"updated":"2026-09-10 17:12:18.000000000","message":"Interfacing with the Testing and Collaboration Tools SIG is something that gets spelled out in the DPL document, so should probably be included here too.","commit_id":"234e9c33bc87325f3e7c1c351959891060aa3b41"},{"author":{"_account_id":15334,"name":"Stephen Finucane","display_name":"stephenfin","email":"stephenfin@redhat.com","username":"sfinucan"},"change_message_id":"15ca8acd711edea4be3456431bf2f179869570a2","unresolved":false,"context_lines":[{"line_number":80,"context_line":"Recurrent duties"},{"line_number":81,"context_line":"~~~~~~~~~~~~~~~~"},{"line_number":82,"context_line":""},{"line_number":83,"context_line":"The following are the standing responsibilities a PTL is expected to keep on"},{"line_number":84,"context_line":"top of throughout a cycle. Many of these can be delegated (see"},{"line_number":85,"context_line":"`Liaison roles`_ and `Core team management`_ below), but the PTL retains"},{"line_number":86,"context_line":"overall accountability."},{"line_number":87,"context_line":""}],"source_content_type":"text/x-rst","patch_set":2,"id":"4091cd84_0eff69b0","line":84,"range":{"start_line":83,"start_character":0,"end_line":84,"end_character":26},"in_reply_to":"83cfe18a_da7c746b","updated":"2026-09-10 18:13:13.000000000","message":"This was documented in a later section. I\u0027ve dropped all of this and bumped that section up.","commit_id":"234e9c33bc87325f3e7c1c351959891060aa3b41"},{"author":{"_account_id":5263,"name":"Jeremy Stanley","display_name":"fungi","email":"fungi@yuggoth.org","username":"fungi","status":"missing, presumed fed"},"change_message_id":"cfdd4884ec33dbd0eae1671ff0e9fc862fedd68f","unresolved":true,"context_lines":[{"line_number":85,"context_line":"`Liaison roles`_ and `Core team management`_ below), but the PTL retains"},{"line_number":86,"context_line":"overall accountability."},{"line_number":87,"context_line":""},{"line_number":88,"context_line":"* **Bug triage**: Ensure that incoming bug reports are reviewed and triaged"},{"line_number":89,"context_line":"  in a timely fashion, so that regressions are caught quickly and contributors"},{"line_number":90,"context_line":"  have a clear picture of the project\u0027s health."},{"line_number":91,"context_line":""}],"source_content_type":"text/x-rst","patch_set":2,"id":"a5224ff0_ce4f1503","line":88,"range":{"start_line":88,"start_character":4,"end_line":88,"end_character":14},"updated":"2026-09-10 17:12:18.000000000","message":"Maybe rework this specific to security bugs. We have liaison roles for a reason, and handling reports of suspected vulnerabilities is one of those. Keeping on top of normal bugs is also a good idea, but there are a lot of teams that are inundated from time to time and let it slip, so I\u0027m not sure normal bugs belong on the \"short list.\"","commit_id":"234e9c33bc87325f3e7c1c351959891060aa3b41"},{"author":{"_account_id":15334,"name":"Stephen Finucane","display_name":"stephenfin","email":"stephenfin@redhat.com","username":"sfinucan"},"change_message_id":"15ca8acd711edea4be3456431bf2f179869570a2","unresolved":false,"context_lines":[{"line_number":85,"context_line":"`Liaison roles`_ and `Core team management`_ below), but the PTL retains"},{"line_number":86,"context_line":"overall accountability."},{"line_number":87,"context_line":""},{"line_number":88,"context_line":"* **Bug triage**: Ensure that incoming bug reports are reviewed and triaged"},{"line_number":89,"context_line":"  in a timely fashion, so that regressions are caught quickly and contributors"},{"line_number":90,"context_line":"  have a clear picture of the project\u0027s health."},{"line_number":91,"context_line":""}],"source_content_type":"text/x-rst","patch_set":2,"id":"1d6e0e2b_12bc1700","line":88,"range":{"start_line":88,"start_character":4,"end_line":88,"end_character":14},"in_reply_to":"a5224ff0_ce4f1503","updated":"2026-09-10 18:13:13.000000000","message":"Done","commit_id":"234e9c33bc87325f3e7c1c351959891060aa3b41"},{"author":{"_account_id":5263,"name":"Jeremy Stanley","display_name":"fungi","email":"fungi@yuggoth.org","username":"fungi","status":"missing, presumed fed"},"change_message_id":"cfdd4884ec33dbd0eae1671ff0e9fc862fedd68f","unresolved":true,"context_lines":[{"line_number":89,"context_line":"  in a timely fashion, so that regressions are caught quickly and contributors"},{"line_number":90,"context_line":"  have a clear picture of the project\u0027s health."},{"line_number":91,"context_line":""},{"line_number":92,"context_line":"* **Core team stewardship**: Maintain the project\u0027s core reviewer group so that"},{"line_number":93,"context_line":"  the review queue stays healthy. This is discussed in more in `Core team"},{"line_number":94,"context_line":"  management`_ below."},{"line_number":95,"context_line":""}],"source_content_type":"text/x-rst","patch_set":2,"id":"8feb57d5_aa612c75","line":92,"range":{"start_line":92,"start_character":4,"end_line":92,"end_character":25},"updated":"2026-09-10 17:12:18.000000000","message":"I recommend putting this first in the list for visibility, as it seems to be the most overlooked.","commit_id":"234e9c33bc87325f3e7c1c351959891060aa3b41"},{"author":{"_account_id":15334,"name":"Stephen Finucane","display_name":"stephenfin","email":"stephenfin@redhat.com","username":"sfinucan"},"change_message_id":"15ca8acd711edea4be3456431bf2f179869570a2","unresolved":false,"context_lines":[{"line_number":89,"context_line":"  in a timely fashion, so that regressions are caught quickly and contributors"},{"line_number":90,"context_line":"  have a clear picture of the project\u0027s health."},{"line_number":91,"context_line":""},{"line_number":92,"context_line":"* **Core team stewardship**: Maintain the project\u0027s core reviewer group so that"},{"line_number":93,"context_line":"  the review queue stays healthy. This is discussed in more in `Core team"},{"line_number":94,"context_line":"  management`_ below."},{"line_number":95,"context_line":""}],"source_content_type":"text/x-rst","patch_set":2,"id":"b5c34eb5_bcb2d8fa","line":92,"range":{"start_line":92,"start_character":4,"end_line":92,"end_character":25},"in_reply_to":"8feb57d5_aa612c75","updated":"2026-09-10 18:13:13.000000000","message":"Done","commit_id":"234e9c33bc87325f3e7c1c351959891060aa3b41"},{"author":{"_account_id":16643,"name":"Goutham Pacha Ravi","email":"gouthampravi@gmail.com","username":"gouthamr"},"change_message_id":"df9db2b70703c3a1c3dfde30f47fa812dc811fcd","unresolved":true,"context_lines":[{"line_number":166,"context_line":""},{"line_number":167,"context_line":"* **Project update**: If the project has news to share at a Summit, submit a"},{"line_number":168,"context_line":"  project update session proposal. Speaker registration must be completed"},{"line_number":169,"context_line":"  before the deadline communicated by the OpenStack Foundation."},{"line_number":170,"context_line":""},{"line_number":171,"context_line":"Physical attendance is preferred but not mandatory. If the PTL cannot attend,"},{"line_number":172,"context_line":"they should designate someone to run team sessions and post summaries on their"}],"source_content_type":"text/x-rst","patch_set":2,"id":"fffff605_e9891d17","line":169,"range":{"start_line":169,"start_character":41,"end_line":169,"end_character":63},"updated":"2026-09-10 17:02:52.000000000","message":"OpenInfra Foundation.. \n\nbut an example of the things I think we shouldn\u0027t worry about codifying here, but take it to the project team guide.","commit_id":"234e9c33bc87325f3e7c1c351959891060aa3b41"},{"author":{"_account_id":15334,"name":"Stephen Finucane","display_name":"stephenfin","email":"stephenfin@redhat.com","username":"sfinucan"},"change_message_id":"15ca8acd711edea4be3456431bf2f179869570a2","unresolved":false,"context_lines":[{"line_number":166,"context_line":""},{"line_number":167,"context_line":"* **Project update**: If the project has news to share at a Summit, submit a"},{"line_number":168,"context_line":"  project update session proposal. Speaker registration must be completed"},{"line_number":169,"context_line":"  before the deadline communicated by the OpenStack Foundation."},{"line_number":170,"context_line":""},{"line_number":171,"context_line":"Physical attendance is preferred but not mandatory. If the PTL cannot attend,"},{"line_number":172,"context_line":"they should designate someone to run team sessions and post summaries on their"}],"source_content_type":"text/x-rst","patch_set":2,"id":"ccbda18e_a0ffcf4e","line":169,"range":{"start_line":169,"start_character":41,"end_line":169,"end_character":63},"in_reply_to":"fffff605_e9891d17","updated":"2026-09-10 18:13:13.000000000","message":"Done","commit_id":"234e9c33bc87325f3e7c1c351959891060aa3b41"},{"author":{"_account_id":16643,"name":"Goutham Pacha Ravi","email":"gouthampravi@gmail.com","username":"gouthamr"},"change_message_id":"df9db2b70703c3a1c3dfde30f47fa812dc811fcd","unresolved":true,"context_lines":[{"line_number":173,"context_line":"behalf."},{"line_number":174,"context_line":""},{"line_number":175,"context_line":".. _liaison-roles:"},{"line_number":176,"context_line":""},{"line_number":177,"context_line":"Liaison roles"},{"line_number":178,"context_line":"-------------"},{"line_number":179,"context_line":""},{"line_number":180,"context_line":"Certain responsibilities are significant and well-defined enough that the"},{"line_number":181,"context_line":"community names an individual as the point of contact for each of them. These"}],"source_content_type":"text/x-rst","patch_set":2,"id":"575b25f5_cdfd419d","line":178,"range":{"start_line":176,"start_character":0,"end_line":178,"end_character":13},"updated":"2026-09-10 17:02:52.000000000","message":"Thanks, this section is very useful; because the TC intentionally formalized this during the Hibiscus cycle. We need release acks and vulnerability management contacts, and will soon need TaCT contacts in the same way","commit_id":"234e9c33bc87325f3e7c1c351959891060aa3b41"},{"author":{"_account_id":15334,"name":"Stephen Finucane","display_name":"stephenfin","email":"stephenfin@redhat.com","username":"sfinucan"},"change_message_id":"15ca8acd711edea4be3456431bf2f179869570a2","unresolved":false,"context_lines":[{"line_number":173,"context_line":"behalf."},{"line_number":174,"context_line":""},{"line_number":175,"context_line":".. _liaison-roles:"},{"line_number":176,"context_line":""},{"line_number":177,"context_line":"Liaison roles"},{"line_number":178,"context_line":"-------------"},{"line_number":179,"context_line":""},{"line_number":180,"context_line":"Certain responsibilities are significant and well-defined enough that the"},{"line_number":181,"context_line":"community names an individual as the point of contact for each of them. These"}],"source_content_type":"text/x-rst","patch_set":2,"id":"eb5ba430_95a2f9ac","line":178,"range":{"start_line":176,"start_character":0,"end_line":178,"end_character":13},"in_reply_to":"575b25f5_cdfd419d","updated":"2026-09-10 18:13:13.000000000","message":"I\u0027ve prioritised this section above all others, in light of your/fungi\u0027s feedback.","commit_id":"234e9c33bc87325f3e7c1c351959891060aa3b41"},{"author":{"_account_id":16643,"name":"Goutham Pacha Ravi","email":"gouthampravi@gmail.com","username":"gouthamr"},"change_message_id":"df9db2b70703c3a1c3dfde30f47fa812dc811fcd","unresolved":true,"context_lines":[{"line_number":185,"context_line":"Under the PTL model, **the PTL holds all of these roles by default**. There is"},{"line_number":186,"context_line":"no requirement to appoint separate people, and most project teams do not. Where"},{"line_number":187,"context_line":"the PTL chooses to delegate a role to another contributor, that person\u0027s name"},{"line_number":188,"context_line":"is recorded in the appropriate place, but accountability for the role remains"},{"line_number":189,"context_line":"with the PTL."},{"line_number":190,"context_line":""},{"line_number":191,"context_line":"The :doc:`Distributed Project Leadership \u003cdistributed-project-leadership\u003e`"}],"source_content_type":"text/x-rst","patch_set":2,"id":"2dc6c579_55ac1180","line":188,"range":{"start_line":188,"start_character":19,"end_line":188,"end_character":36},"updated":"2026-09-10 17:02:52.000000000","message":"governance repository","commit_id":"234e9c33bc87325f3e7c1c351959891060aa3b41"},{"author":{"_account_id":15334,"name":"Stephen Finucane","display_name":"stephenfin","email":"stephenfin@redhat.com","username":"sfinucan"},"change_message_id":"15ca8acd711edea4be3456431bf2f179869570a2","unresolved":false,"context_lines":[{"line_number":185,"context_line":"Under the PTL model, **the PTL holds all of these roles by default**. There is"},{"line_number":186,"context_line":"no requirement to appoint separate people, and most project teams do not. Where"},{"line_number":187,"context_line":"the PTL chooses to delegate a role to another contributor, that person\u0027s name"},{"line_number":188,"context_line":"is recorded in the appropriate place, but accountability for the role remains"},{"line_number":189,"context_line":"with the PTL."},{"line_number":190,"context_line":""},{"line_number":191,"context_line":"The :doc:`Distributed Project Leadership \u003cdistributed-project-leadership\u003e`"}],"source_content_type":"text/x-rst","patch_set":2,"id":"1a852ddb_f79de362","line":188,"range":{"start_line":188,"start_character":19,"end_line":188,"end_character":36},"in_reply_to":"2dc6c579_55ac1180","updated":"2026-09-10 18:13:13.000000000","message":"Done","commit_id":"234e9c33bc87325f3e7c1c351959891060aa3b41"},{"author":{"_account_id":16643,"name":"Goutham Pacha Ravi","email":"gouthampravi@gmail.com","username":"gouthamr"},"change_message_id":"df9db2b70703c3a1c3dfde30f47fa812dc811fcd","unresolved":true,"context_lines":[{"line_number":224,"context_line":"core team to the existing core team. However, like the delegation of other"},{"line_number":225,"context_line":"responsibilities, accountability for this role ultimately remains with the PTL."},{"line_number":226,"context_line":""},{"line_number":227,"context_line":"When evaluating candidates for addition to the core team, consider:"},{"line_number":228,"context_line":""},{"line_number":229,"context_line":"* Are their review volumes and disagreement rates comparable to those of"},{"line_number":230,"context_line":"  existing core reviewers?"},{"line_number":231,"context_line":"* Do they follow up consistently on reviews they have started?"},{"line_number":232,"context_line":"* Is their review feedback constructive and accurate?"},{"line_number":233,"context_line":"* Do they participate in bug triage, specifications review, and team meetings?"},{"line_number":234,"context_line":"* Do they have a clear understanding of the project\u0027s direction and priorities?"},{"line_number":235,"context_line":""},{"line_number":236,"context_line":"When considering removing a core reviewer, consider:"},{"line_number":237,"context_line":""},{"line_number":238,"context_line":"* Has their review activity dropped significantly below the level of the rest"},{"line_number":239,"context_line":"  of the core team?"},{"line_number":240,"context_line":"* Have their job responsibilities changed such that they no longer have"},{"line_number":241,"context_line":"  capacity for the role?"},{"line_number":242,"context_line":"* Is their knowledge of the codebase still current enough to review"},{"line_number":243,"context_line":"  effectively?"},{"line_number":244,"context_line":""},{"line_number":245,"context_line":"When adding a new core reviewer, announce the addition to the mailing list, add"},{"line_number":246,"context_line":"them to the relevant Gerrit group, and (if applicable) add them to the project"}],"source_content_type":"text/x-rst","patch_set":2,"id":"ddb50577_69c55817","line":243,"range":{"start_line":227,"start_character":0,"end_line":243,"end_character":14},"updated":"2026-09-10 17:02:52.000000000","message":"Link to the project-team-guide instead perhaps","commit_id":"234e9c33bc87325f3e7c1c351959891060aa3b41"},{"author":{"_account_id":15334,"name":"Stephen Finucane","display_name":"stephenfin","email":"stephenfin@redhat.com","username":"sfinucan"},"change_message_id":"15ca8acd711edea4be3456431bf2f179869570a2","unresolved":false,"context_lines":[{"line_number":224,"context_line":"core team to the existing core team. However, like the delegation of other"},{"line_number":225,"context_line":"responsibilities, accountability for this role ultimately remains with the PTL."},{"line_number":226,"context_line":""},{"line_number":227,"context_line":"When evaluating candidates for addition to the core team, consider:"},{"line_number":228,"context_line":""},{"line_number":229,"context_line":"* Are their review volumes and disagreement rates comparable to those of"},{"line_number":230,"context_line":"  existing core reviewers?"},{"line_number":231,"context_line":"* Do they follow up consistently on reviews they have started?"},{"line_number":232,"context_line":"* Is their review feedback constructive and accurate?"},{"line_number":233,"context_line":"* Do they participate in bug triage, specifications review, and team meetings?"},{"line_number":234,"context_line":"* Do they have a clear understanding of the project\u0027s direction and priorities?"},{"line_number":235,"context_line":""},{"line_number":236,"context_line":"When considering removing a core reviewer, consider:"},{"line_number":237,"context_line":""},{"line_number":238,"context_line":"* Has their review activity dropped significantly below the level of the rest"},{"line_number":239,"context_line":"  of the core team?"},{"line_number":240,"context_line":"* Have their job responsibilities changed such that they no longer have"},{"line_number":241,"context_line":"  capacity for the role?"},{"line_number":242,"context_line":"* Is their knowledge of the codebase still current enough to review"},{"line_number":243,"context_line":"  effectively?"},{"line_number":244,"context_line":""},{"line_number":245,"context_line":"When adding a new core reviewer, announce the addition to the mailing list, add"},{"line_number":246,"context_line":"them to the relevant Gerrit group, and (if applicable) add them to the project"}],"source_content_type":"text/x-rst","patch_set":2,"id":"6c40e274_b3ec541b","line":243,"range":{"start_line":227,"start_character":0,"end_line":243,"end_character":14},"in_reply_to":"ddb50577_69c55817","updated":"2026-09-10 18:13:13.000000000","message":"Done","commit_id":"234e9c33bc87325f3e7c1c351959891060aa3b41"},{"author":{"_account_id":11604,"name":"sean mooney","email":"smooney@redhat.com","username":"sean-k-mooney"},"change_message_id":"80775ed4f5330b30f9f72d2a3a6216081d1f09bd","unresolved":true,"context_lines":[{"line_number":57,"context_line":"    The `Project Team Guide`_ provides a guide on how to maintain core"},{"line_number":58,"context_line":"    membership, including guidelines on when and how to add or remove cores."},{"line_number":59,"context_line":""},{"line_number":60,"context_line":"Liaisons"},{"line_number":61,"context_line":"~~~~~~~~"},{"line_number":62,"context_line":""},{"line_number":63,"context_line":"Projects are expected to maintain relationships between the project team and"}],"source_content_type":"text/x-rst","patch_set":3,"id":"68474743_07a1b88b","line":60,"range":{"start_line":60,"start_character":0,"end_line":60,"end_character":8},"updated":"2026-09-10 21:00:44.000000000","message":"jsut a stucal comment\n\nsince the liason roles are the saem across PTL and DPL should we have a sepreate page that defiens teh Liaisons and embed or link to it form both docs\n\nwe can still keep the DPL vs PTL raming around them but for the sepcifc leasios roles i think may be helpful to keep them in sync","commit_id":"bf0998cebe40383118e4aa21662684faa7a39740"},{"author":{"_account_id":15334,"name":"Stephen Finucane","display_name":"stephenfin","email":"stephenfin@redhat.com","username":"sfinucan"},"change_message_id":"7c5b88f746bf735b89cc18cca6d5ef9ecea84e49","unresolved":false,"context_lines":[{"line_number":57,"context_line":"    The `Project Team Guide`_ provides a guide on how to maintain core"},{"line_number":58,"context_line":"    membership, including guidelines on when and how to add or remove cores."},{"line_number":59,"context_line":""},{"line_number":60,"context_line":"Liaisons"},{"line_number":61,"context_line":"~~~~~~~~"},{"line_number":62,"context_line":""},{"line_number":63,"context_line":"Projects are expected to maintain relationships between the project team and"}],"source_content_type":"text/x-rst","patch_set":3,"id":"0670cfd8_530b7009","line":60,"range":{"start_line":60,"start_character":0,"end_line":60,"end_character":8},"in_reply_to":"68474743_07a1b88b","updated":"2026-09-11 10:39:14.000000000","message":"This is a good point: there\u0027s no need to repeat myself here. I\u0027ve dropped the list and instead pointed back to the DPL guide.","commit_id":"bf0998cebe40383118e4aa21662684faa7a39740"},{"author":{"_account_id":11604,"name":"sean mooney","email":"smooney@redhat.com","username":"sean-k-mooney"},"change_message_id":"80775ed4f5330b30f9f72d2a3a6216081d1f09bd","unresolved":true,"context_lines":[{"line_number":87,"context_line":"  for the OpenStack Vulnerability Management process. They help assess the"},{"line_number":88,"context_line":"  impact of reported security issues, coordinate patch development and review,"},{"line_number":89,"context_line":"  and manage backports."},{"line_number":90,"context_line":""},{"line_number":91,"context_line":"The :doc:`Distributed Project Leadership \u003cdistributed-project-leadership\u003e`"},{"line_number":92,"context_line":"model uses these same roles as the basis for dividing up the responsibilities"},{"line_number":93,"context_line":"that would otherwise rest with the PTL. Under the DPL model named liaisons are"}],"source_content_type":"text/x-rst","patch_set":3,"id":"a92a0051_474819fd","line":90,"updated":"2026-09-10 21:00:44.000000000","message":"tehre are other liason roles behyond the core 3\n\nthe project update/onborading role (the public face of the project)\nand the tempory event laison. both of those fall to the ptl by default as well\nbut can be delgated, we currently do not record the event liason in the governace repo directlybut we could add the abliyt to list the proejct onboridng/updates liason.\n\nthat is the person the TC woudl reach out to for things like the release highlight or project update livestream.","commit_id":"bf0998cebe40383118e4aa21662684faa7a39740"},{"author":{"_account_id":15334,"name":"Stephen Finucane","display_name":"stephenfin","email":"stephenfin@redhat.com","username":"sfinucan"},"change_message_id":"7c5b88f746bf735b89cc18cca6d5ef9ecea84e49","unresolved":false,"context_lines":[{"line_number":87,"context_line":"  for the OpenStack Vulnerability Management process. They help assess the"},{"line_number":88,"context_line":"  impact of reported security issues, coordinate patch development and review,"},{"line_number":89,"context_line":"  and manage backports."},{"line_number":90,"context_line":""},{"line_number":91,"context_line":"The :doc:`Distributed Project Leadership \u003cdistributed-project-leadership\u003e`"},{"line_number":92,"context_line":"model uses these same roles as the basis for dividing up the responsibilities"},{"line_number":93,"context_line":"that would otherwise rest with the PTL. Under the DPL model named liaisons are"}],"source_content_type":"text/x-rst","patch_set":3,"id":"9f1173bc_0ad27b55","line":90,"in_reply_to":"a92a0051_474819fd","updated":"2026-09-11 10:39:14.000000000","message":"I\u0027ve pointed at the optional roles.","commit_id":"bf0998cebe40383118e4aa21662684faa7a39740"},{"author":{"_account_id":11604,"name":"sean mooney","email":"smooney@redhat.com","username":"sean-k-mooney"},"change_message_id":"80775ed4f5330b30f9f72d2a3a6216081d1f09bd","unresolved":true,"context_lines":[{"line_number":96,"context_line":"Relationship with the TC"},{"line_number":97,"context_line":"------------------------"},{"line_number":98,"context_line":""},{"line_number":99,"context_line":"Although the TC has ultimate technical oversight over all official project"},{"line_number":100,"context_line":"teams, it generally does not involve itself in team-internal decisions. The PTL"},{"line_number":101,"context_line":"is trusted to manage the team\u0027s affairs within the OpenStack community norms"},{"line_number":102,"context_line":"and the TC\u0027s published guidelines."},{"line_number":103,"context_line":""},{"line_number":104,"context_line":"The TC does expect PTLs to:"},{"line_number":105,"context_line":""}],"source_content_type":"text/x-rst","patch_set":3,"id":"7e58ac92_ccb9c24c","line":102,"range":{"start_line":99,"start_character":0,"end_line":102,"end_character":34},"updated":"2026-09-10 21:00:44.000000000","message":"my only real commont on this is ultimatly all power and duties fo the ptl are delegated form the TC and the ptl serves at there behst folowing there election vai our standared processes. they may choose too and are encuraged to delegate future to apoint liasons but while the tc is not directly invoed in team internals i think its important to capture that this is a case of power and trust flowing downwords form the tc.","commit_id":"bf0998cebe40383118e4aa21662684faa7a39740"},{"author":{"_account_id":11604,"name":"sean mooney","email":"smooney@redhat.com","username":"sean-k-mooney"},"change_message_id":"99242574cfb60c51f6ecf1ee40e81c73e69637b1","unresolved":true,"context_lines":[{"line_number":96,"context_line":"Relationship with the TC"},{"line_number":97,"context_line":"------------------------"},{"line_number":98,"context_line":""},{"line_number":99,"context_line":"Although the TC has ultimate technical oversight over all official project"},{"line_number":100,"context_line":"teams, it generally does not involve itself in team-internal decisions. The PTL"},{"line_number":101,"context_line":"is trusted to manage the team\u0027s affairs within the OpenStack community norms"},{"line_number":102,"context_line":"and the TC\u0027s published guidelines."},{"line_number":103,"context_line":""},{"line_number":104,"context_line":"The TC does expect PTLs to:"},{"line_number":105,"context_line":""}],"source_content_type":"text/x-rst","patch_set":3,"id":"838f10e5_a7caafea","line":102,"range":{"start_line":99,"start_character":0,"end_line":102,"end_character":34},"in_reply_to":"166d967c_f817296d","updated":"2026-09-11 10:48:08.000000000","message":"```suggestion\nAlthough the TC has ultimate technical oversight over all official project\nteams, it generally does not involve itself in team-internal decisions.\nThe TC delages the responsibility and authority to conduct the day to day  running\nof the team and its accountability to the PTL. The PTL is trusted to manage the team\u0027s affairs within the OpenStack community norms and the TC\u0027s published guidelines and may further delegate there roles and responsibility to liaisons they appoint.\n```\n\nmaybe somethign like that","commit_id":"bf0998cebe40383118e4aa21662684faa7a39740"},{"author":{"_account_id":15334,"name":"Stephen Finucane","display_name":"stephenfin","email":"stephenfin@redhat.com","username":"sfinucan"},"change_message_id":"7c5b88f746bf735b89cc18cca6d5ef9ecea84e49","unresolved":true,"context_lines":[{"line_number":96,"context_line":"Relationship with the TC"},{"line_number":97,"context_line":"------------------------"},{"line_number":98,"context_line":""},{"line_number":99,"context_line":"Although the TC has ultimate technical oversight over all official project"},{"line_number":100,"context_line":"teams, it generally does not involve itself in team-internal decisions. The PTL"},{"line_number":101,"context_line":"is trusted to manage the team\u0027s affairs within the OpenStack community norms"},{"line_number":102,"context_line":"and the TC\u0027s published guidelines."},{"line_number":103,"context_line":""},{"line_number":104,"context_line":"The TC does expect PTLs to:"},{"line_number":105,"context_line":""}],"source_content_type":"text/x-rst","patch_set":3,"id":"166d967c_f817296d","line":102,"range":{"start_line":99,"start_character":0,"end_line":102,"end_character":34},"in_reply_to":"7e58ac92_ccb9c24c","updated":"2026-09-11 10:39:14.000000000","message":"I get your point but I\u0027m not sure how to capture this here. Feel free to add a `suggestion` comment if you think it\u0027s worth changing and have ideas for how to do so 🙏","commit_id":"bf0998cebe40383118e4aa21662684faa7a39740"},{"author":{"_account_id":15334,"name":"Stephen Finucane","display_name":"stephenfin","email":"stephenfin@redhat.com","username":"sfinucan"},"change_message_id":"c14fef4901a01e112d0839f36c2dde1bc9bf64b0","unresolved":false,"context_lines":[{"line_number":96,"context_line":"Relationship with the TC"},{"line_number":97,"context_line":"------------------------"},{"line_number":98,"context_line":""},{"line_number":99,"context_line":"Although the TC has ultimate technical oversight over all official project"},{"line_number":100,"context_line":"teams, it generally does not involve itself in team-internal decisions. The PTL"},{"line_number":101,"context_line":"is trusted to manage the team\u0027s affairs within the OpenStack community norms"},{"line_number":102,"context_line":"and the TC\u0027s published guidelines."},{"line_number":103,"context_line":""},{"line_number":104,"context_line":"The TC does expect PTLs to:"},{"line_number":105,"context_line":""}],"source_content_type":"text/x-rst","patch_set":3,"id":"08094132_f27e5770","line":102,"range":{"start_line":99,"start_character":0,"end_line":102,"end_character":34},"in_reply_to":"838f10e5_a7caafea","updated":"2026-09-11 15:26:56.000000000","message":"Done","commit_id":"bf0998cebe40383118e4aa21662684faa7a39740"}]}