)]}'
{"/PATCHSET_LEVEL":[{"author":{"_account_id":15334,"name":"Stephen Finucane","display_name":"stephenfin","email":"stephenfin@redhat.com","username":"sfinucan"},"change_message_id":"e531301babac0724d8e0c4c65db4d0f21385194c","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":2,"id":"f4461010_c0b98bae","updated":"2026-05-21 12:47:49.000000000","message":"\u003e I\u0027d love to expand this for security and tact-sig as well. In practice many PTL model teams use the same liaison roles as DPL model teams, but we\u0027ve ended up tracking them in random places because governance wasn\u0027t set up for it.\n\u003e \n\u003e The main question I have is logistical in nature, about the refresh process. Will liaisons for PTL teams get a forced refresh once per cycle like they do for DPL?\n\nI believe this is a TC question, but I\u0027d be in favour of this. The same heartbeat arguments that apply to the DPL model also apply here.\n\n\u003e And a minor nit, the couple of places you update PTL IRC nicks is likely to cause churn at the next election if they haven\u0027t set them in their foundation profiles, since they\u0027ll get reset back to not-supplied at that point.\n\nOkay, I was wondering why they were present in `openstack/releases` but not here. I think that (them being reset) is fine and if anything might act as a forcing function to get said PTLs to update their foundation profiles.","commit_id":"9e86f0fa1328f96c36cd5f05fd9e974b4c5f9909"}],"openstack_governance/projects_schema.yaml":[{"author":{"_account_id":15334,"name":"Stephen Finucane","display_name":"stephenfin","email":"stephenfin@redhat.com","username":"sfinucan"},"change_message_id":"df22924e6479a121f4836562c8ea6aa32ffe0b01","unresolved":false,"context_lines":[{"line_number":30,"context_line":"    - deliverables"},{"line_number":31,"context_line":"    - url"},{"line_number":32,"context_line":"    - mission"},{"line_number":33,"context_line":"  if:"},{"line_number":34,"context_line":"    properties:"},{"line_number":35,"context_line":"      leadership_type:"},{"line_number":36,"context_line":"        const: \"distributed\""}],"source_content_type":"text/x-yaml","patch_set":1,"id":"ce273cf3_ff8b9ad8","line":33,"updated":"2026-05-19 15:44:33.000000000","message":"For anyone that hasn\u0027t seen this before https://json-schema.org/understanding-json-schema/reference/conditionals#ifthenelse","commit_id":"16805c73122fc61517f456b790ed0561f9a5d9e9"}],"reference/distributed-project-leadership.rst":[{"author":{"_account_id":17685,"name":"Elod Illes","email":"elod.illes@est.tech","username":"elod.illes"},"change_message_id":"3dc5fe37b41c016a0462d398db4f7eb93e1b5b89","unresolved":true,"context_lines":[{"line_number":45,"context_line":"* Release liaison: The :repo:`openstack/releases/src/branch/master/data/release_liaisons.yaml`"},{"line_number":46,"context_line":"  is responsible for requesting releases for deliverables produced by the"},{"line_number":47,"context_line":"  project team.  In addition, release liaisons generally review requests for"},{"line_number":48,"context_line":"  Feature Freeze Exception (FFE)."},{"line_number":49,"context_line":""},{"line_number":50,"context_line":"* tact-sig liaison: Historically named the \"infra Liaison\".  It is responsible for"},{"line_number":51,"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":1,"id":"d37278d7_e25bd858","line":48,"updated":"2026-05-19 15:58:14.000000000","message":"this ^^^ section needs to be rephrased as well.","commit_id":"16805c73122fc61517f456b790ed0561f9a5d9e9"},{"author":{"_account_id":17685,"name":"Elod Illes","email":"elod.illes@est.tech","username":"elod.illes"},"change_message_id":"3dc5fe37b41c016a0462d398db4f7eb93e1b5b89","unresolved":true,"context_lines":[{"line_number":192,"context_line":"should have at least a +1 from all the people currently serving as liaisons,"},{"line_number":193,"context_line":"including the :repo:`openstack/releases/src/branch/master/data/release_liaisons.yaml`"},{"line_number":194,"context_line":"for the project team, which might not be in the ``governance`` repo."},{"line_number":195,"context_line":"It must also get a +1 from the future PTL, listed in the same change."},{"line_number":196,"context_line":""},{"line_number":197,"context_line":".. note::"},{"line_number":198,"context_line":""}],"source_content_type":"text/x-rst","patch_set":1,"id":"6d5baff0_ca1f99b8","line":195,"updated":"2026-05-19 15:58:14.000000000","message":"^^^ ditto","commit_id":"16805c73122fc61517f456b790ed0561f9a5d9e9"}]}