)]}'
{"/PATCHSET_LEVEL":[{"author":{"_account_id":5314,"name":"Brian Rosmaita","email":"rosmaita.fossdev@gmail.com","username":"brian-rosmaita"},"change_message_id":"2e9e408ca57c1b063a4fcd91bef9838e02599263","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"256dd866_06c17623","updated":"2024-03-05 17:33:39.000000000","message":"@Elod: reply inline","commit_id":"8f25583cabd1424b9520efe29556e9c2b18c4fd3"},{"author":{"_account_id":5314,"name":"Brian Rosmaita","email":"rosmaita.fossdev@gmail.com","username":"brian-rosmaita"},"change_message_id":"5e6937c72fa261b45fd11001cdc89f593cc81b21","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"55c4c230_2576f4bc","updated":"2024-03-01 17:38:06.000000000","message":"A few comments inline.  I agree with frickler\u0027s suggestion for a SIG if you\u0027re willing to take it on.","commit_id":"8f25583cabd1424b9520efe29556e9c2b18c4fd3"},{"author":{"_account_id":8556,"name":"Ghanshyam Maan","display_name":"Ghanshyam Maan","email":"gmaan.os14@gmail.com","username":"ghanshyam"},"change_message_id":"4dce1b0beba6d7e311daba976750b22529eb1a6b","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"6777df20_1ff3b3ef","updated":"2024-03-05 18:47:31.000000000","message":"I am ok on this version and project specific group thing can be done in separate change.","commit_id":"8f25583cabd1424b9520efe29556e9c2b18c4fd3"},{"author":{"_account_id":17685,"name":"Elod Illes","email":"elod.illes@est.tech","username":"elod.illes"},"change_message_id":"deb3fb159229c5d39d577c8996351c4991f2d13b","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"6362a5f1_d0d5394f","updated":"2024-03-01 17:11:22.000000000","message":"Well, this is a simple description of the main idea. Should we add here anything else? Do you want any special handling of how to get membership?\n\nnote:\n- who became a member of openstack-unmaintained-core group will have right to add additional members to the group, there won\u0027t be a smaller group who controls the membership, as far as i understand the group setup\n- people who are added to the group will have rights to every repository and every unmaintained branch\n\nDo I understand this well? Do we want to have a formal way of membership query vial e.g. a mail to ML with [unmaintained] tag or something?","commit_id":"8f25583cabd1424b9520efe29556e9c2b18c4fd3"},{"author":{"_account_id":8556,"name":"Ghanshyam Maan","display_name":"Ghanshyam Maan","email":"gmaan.os14@gmail.com","username":"ghanshyam"},"change_message_id":"a36b2971e1d9c93bc4a081487bb50680e86ea95f","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"bc028403_a2063826","updated":"2024-03-01 18:04:04.000000000","message":"thanks Elod for adding it. a few suggestion but my -1 is mainly to cover the \u0027how to be added in PROJECTNAME-unmaintained-core\u0027 also.","commit_id":"8f25583cabd1424b9520efe29556e9c2b18c4fd3"},{"author":{"_account_id":5314,"name":"Brian Rosmaita","email":"rosmaita.fossdev@gmail.com","username":"brian-rosmaita"},"change_message_id":"2e9e408ca57c1b063a4fcd91bef9838e02599263","unresolved":true,"context_lines":[],"source_content_type":"","patch_set":1,"id":"7e39dcf7_9a55f6e0","in_reply_to":"6362a5f1_d0d5394f","updated":"2024-03-05 17:33:39.000000000","message":"Just realized I never answered this.  You\u0027re correct, the way the openstack-unmaintained-core group is currently set up is the way you describe.  But the idea is that it will be a self-maintaining group; there\u0027s nothing in the TC resolution that dictates how it should function.  So it\u0027s up to the group itself to decide whether it wants to have a smaller group that controls membership, and also what the process for becoming a member is (but presumably it will involve a transparent process like nomination (self or other, up to you) on the mailing list, wait a week for comments, and then add to openstack-unmaintained-core (basically, the same process as becoming a member of a project core team).","commit_id":"8f25583cabd1424b9520efe29556e9c2b18c4fd3"}],"doc/source/stable-branches.rst":[{"author":{"_account_id":8556,"name":"Ghanshyam Maan","display_name":"Ghanshyam Maan","email":"gmaan.os14@gmail.com","username":"ghanshyam"},"change_message_id":"a36b2971e1d9c93bc4a081487bb50680e86ea95f","unresolved":true,"context_lines":[{"line_number":357,"context_line":"to merge appropriate changes into Unmaintained branches."},{"line_number":358,"context_line":""},{"line_number":359,"context_line":"Additionally, each project may have (but is not required to have) a Gerrit"},{"line_number":360,"context_line":"team called PROJECTNAME-unmaintained-core to handle all work on that"},{"line_number":361,"context_line":"project\u0027s Unmaintained branches.  This group is managed by the PTL or the"},{"line_number":362,"context_line":"Unmaintained branch liaison if there is one.  The group is created by"},{"line_number":363,"context_line":"proposing an appropriate set of permissions to the project\u0027s Gerrit ACLs"}],"source_content_type":"text/x-rst","patch_set":1,"id":"e6d5f356_54abaf95","line":360,"range":{"start_line":360,"start_character":12,"end_line":360,"end_character":41},"updated":"2024-03-01 18:04:04.000000000","message":"can we add a note about this group also the same way we did for global group?","commit_id":"8f25583cabd1424b9520efe29556e9c2b18c4fd3"},{"author":{"_account_id":8556,"name":"Ghanshyam Maan","display_name":"Ghanshyam Maan","email":"gmaan.os14@gmail.com","username":"ghanshyam"},"change_message_id":"a36b2971e1d9c93bc4a081487bb50680e86ea95f","unresolved":true,"context_lines":[{"line_number":366,"context_line":"for an example."},{"line_number":367,"context_line":""},{"line_number":368,"context_line":".. note::"},{"line_number":369,"context_line":"   To become a member of the ``openstack-unmaintained-core`` team, first"},{"line_number":370,"context_line":"   the stable policy has to be understood, as it still applies to"},{"line_number":371,"context_line":"   unmaintained branches as well. Then contact the group itself and"},{"line_number":372,"context_line":"   signal the interest of becoming a member of the group and the intention"}],"source_content_type":"text/x-rst","patch_set":1,"id":"cb431f6a_644d50c7","line":369,"range":{"start_line":369,"start_character":29,"end_line":369,"end_character":60},"updated":"2024-03-01 18:04:04.000000000","message":"with ref to my above comment, can we make it generic for both group because both group exist and we should tell them how to become member in either one. Something like below\n\nTo become a member of the ``openstack-unmaintained-core`` or ``PROJECTNAME-unmaintained-core`` team,...","commit_id":"8f25583cabd1424b9520efe29556e9c2b18c4fd3"},{"author":{"_account_id":8556,"name":"Ghanshyam Maan","display_name":"Ghanshyam Maan","email":"gmaan.os14@gmail.com","username":"ghanshyam"},"change_message_id":"4dce1b0beba6d7e311daba976750b22529eb1a6b","unresolved":true,"context_lines":[{"line_number":366,"context_line":"for an example."},{"line_number":367,"context_line":""},{"line_number":368,"context_line":".. note::"},{"line_number":369,"context_line":"   To become a member of the ``openstack-unmaintained-core`` team, first"},{"line_number":370,"context_line":"   the stable policy has to be understood, as it still applies to"},{"line_number":371,"context_line":"   unmaintained branches as well. Then contact the group itself and"},{"line_number":372,"context_line":"   signal the interest of becoming a member of the group and the intention"}],"source_content_type":"text/x-rst","patch_set":1,"id":"a98cb2bc_0c38a9a0","line":369,"range":{"start_line":369,"start_character":29,"end_line":369,"end_character":60},"in_reply_to":"262396d1_7208630c","updated":"2024-03-05 18:47:31.000000000","message":"As discussed in today TC meeting, I am ok to cover the project specific unmaintained group in separate change.","commit_id":"8f25583cabd1424b9520efe29556e9c2b18c4fd3"},{"author":{"_account_id":8556,"name":"Ghanshyam Maan","display_name":"Ghanshyam Maan","email":"gmaan.os14@gmail.com","username":"ghanshyam"},"change_message_id":"a02924c01fbed5c891aafc405d04aa5e47fac35f","unresolved":true,"context_lines":[{"line_number":366,"context_line":"for an example."},{"line_number":367,"context_line":""},{"line_number":368,"context_line":".. note::"},{"line_number":369,"context_line":"   To become a member of the ``openstack-unmaintained-core`` team, first"},{"line_number":370,"context_line":"   the stable policy has to be understood, as it still applies to"},{"line_number":371,"context_line":"   unmaintained branches as well. Then contact the group itself and"},{"line_number":372,"context_line":"   signal the interest of becoming a member of the group and the intention"}],"source_content_type":"text/x-rst","patch_set":1,"id":"262396d1_7208630c","line":369,"range":{"start_line":369,"start_character":29,"end_line":369,"end_character":60},"in_reply_to":"413e247c_a77bce75","updated":"2024-03-01 20:15:03.000000000","message":"As we know that PROJECTNAME-unmaintained-core is going to be separate from projct team, the core memship should be determine by the PROJECTNAME-unmaintained-core and not the project team maintaining the master and mainstained branches.\n\nI am ok if we want to separate the paragraph for that if there are any separate criteria/requirements of this than global maintain group but I think, requirement of both group is basically stays same:\n 1. understand the stable policy\n 2. contact PROJECTNAME-unmaintained-core to be part if it","commit_id":"8f25583cabd1424b9520efe29556e9c2b18c4fd3"},{"author":{"_account_id":5314,"name":"Brian Rosmaita","email":"rosmaita.fossdev@gmail.com","username":"brian-rosmaita"},"change_message_id":"5267adf9bc5edcfd6d9e83dd58fe265f560d3009","unresolved":true,"context_lines":[{"line_number":366,"context_line":"for an example."},{"line_number":367,"context_line":""},{"line_number":368,"context_line":".. note::"},{"line_number":369,"context_line":"   To become a member of the ``openstack-unmaintained-core`` team, first"},{"line_number":370,"context_line":"   the stable policy has to be understood, as it still applies to"},{"line_number":371,"context_line":"   unmaintained branches as well. Then contact the group itself and"},{"line_number":372,"context_line":"   signal the interest of becoming a member of the group and the intention"}],"source_content_type":"text/x-rst","patch_set":1,"id":"413e247c_a77bce75","line":369,"range":{"start_line":369,"start_character":29,"end_line":369,"end_character":60},"in_reply_to":"cb431f6a_644d50c7","updated":"2024-03-01 19:26:02.000000000","message":"I think we need to keep these separate.  The PROJECTNAME-unmaintained-core team membership is determined by PROJECTNAME, which may have different requirements from the global team.","commit_id":"8f25583cabd1424b9520efe29556e9c2b18c4fd3"},{"author":{"_account_id":13252,"name":"Dr. Jens Harbott","display_name":"Jens Harbott (frickler)","email":"frickler@offenerstapel.de","username":"jrosenboom"},"change_message_id":"d5ac5637023c1790d4e572aefb33ceb6e9cc0f1a","unresolved":true,"context_lines":[{"line_number":367,"context_line":""},{"line_number":368,"context_line":".. note::"},{"line_number":369,"context_line":"   To become a member of the ``openstack-unmaintained-core`` team, first"},{"line_number":370,"context_line":"   the stable policy has to be understood, as it still applies to"},{"line_number":371,"context_line":"   unmaintained branches as well. Then contact the group itself and"},{"line_number":372,"context_line":"   signal the interest of becoming a member of the group and the intention"},{"line_number":373,"context_line":"   to maintain a project (or multiple projects) and its CI, then the"}],"source_content_type":"text/x-rst","patch_set":1,"id":"3a92a846_38d7e17c","line":370,"range":{"start_line":370,"start_character":7,"end_line":370,"end_character":20},"updated":"2024-03-01 17:15:15.000000000","message":"would be nice to link to it","commit_id":"8f25583cabd1424b9520efe29556e9c2b18c4fd3"},{"author":{"_account_id":17685,"name":"Elod Illes","email":"elod.illes@est.tech","username":"elod.illes"},"change_message_id":"3a06e748662350134b2fff9278863e3335edc4c6","unresolved":true,"context_lines":[{"line_number":367,"context_line":""},{"line_number":368,"context_line":".. note::"},{"line_number":369,"context_line":"   To become a member of the ``openstack-unmaintained-core`` team, first"},{"line_number":370,"context_line":"   the stable policy has to be understood, as it still applies to"},{"line_number":371,"context_line":"   unmaintained branches as well. Then contact the group itself and"},{"line_number":372,"context_line":"   signal the interest of becoming a member of the group and the intention"},{"line_number":373,"context_line":"   to maintain a project (or multiple projects) and its CI, then the"}],"source_content_type":"text/x-rst","patch_set":1,"id":"6ee2c35d_cb8848f3","line":370,"range":{"start_line":370,"start_character":7,"end_line":370,"end_character":20},"in_reply_to":"3a92a846_38d7e17c","updated":"2024-03-01 17:21:14.000000000","message":"i can add: ``(*this page*)`` o:)","commit_id":"8f25583cabd1424b9520efe29556e9c2b18c4fd3"},{"author":{"_account_id":5314,"name":"Brian Rosmaita","email":"rosmaita.fossdev@gmail.com","username":"brian-rosmaita"},"change_message_id":"5e6937c72fa261b45fd11001cdc89f593cc81b21","unresolved":true,"context_lines":[{"line_number":367,"context_line":""},{"line_number":368,"context_line":".. note::"},{"line_number":369,"context_line":"   To become a member of the ``openstack-unmaintained-core`` team, first"},{"line_number":370,"context_line":"   the stable policy has to be understood, as it still applies to"},{"line_number":371,"context_line":"   unmaintained branches as well. Then contact the group itself and"},{"line_number":372,"context_line":"   signal the interest of becoming a member of the group and the intention"},{"line_number":373,"context_line":"   to maintain a project (or multiple projects) and its CI, then the"}],"source_content_type":"text/x-rst","patch_set":1,"id":"a3a70be4_72f0b8d1","line":370,"range":{"start_line":370,"start_character":7,"end_line":370,"end_character":20},"in_reply_to":"6ee2c35d_cb8848f3","updated":"2024-03-01 17:38:06.000000000","message":"maybe add in line 371:\n\nunmaintained branches as well.  That means you have read and understood this entire document, particularly the part about :ref:`Appropriate Fixes\u003cappropriate-fixes\u003e`.","commit_id":"8f25583cabd1424b9520efe29556e9c2b18c4fd3"},{"author":{"_account_id":13252,"name":"Dr. Jens Harbott","display_name":"Jens Harbott (frickler)","email":"frickler@offenerstapel.de","username":"jrosenboom"},"change_message_id":"2f441dba0c7d58c582081e98bf8a98392412c21d","unresolved":true,"context_lines":[{"line_number":367,"context_line":""},{"line_number":368,"context_line":".. note::"},{"line_number":369,"context_line":"   To become a member of the ``openstack-unmaintained-core`` team, first"},{"line_number":370,"context_line":"   the stable policy has to be understood, as it still applies to"},{"line_number":371,"context_line":"   unmaintained branches as well. Then contact the group itself and"},{"line_number":372,"context_line":"   signal the interest of becoming a member of the group and the intention"},{"line_number":373,"context_line":"   to maintain a project (or multiple projects) and its CI, then the"}],"source_content_type":"text/x-rst","patch_set":1,"id":"3eb999c7_3afe933e","line":370,"range":{"start_line":370,"start_character":7,"end_line":370,"end_character":20},"in_reply_to":"a3a70be4_72f0b8d1","updated":"2024-03-04 11:49:53.000000000","message":"oh, I wasn\u0027t aware that that section is in the same document here. but yes, I would agree with that addition. Maybe also add a note over there that it also applies to unmaintained branches?","commit_id":"8f25583cabd1424b9520efe29556e9c2b18c4fd3"},{"author":{"_account_id":13252,"name":"Dr. Jens Harbott","display_name":"Jens Harbott (frickler)","email":"frickler@offenerstapel.de","username":"jrosenboom"},"change_message_id":"d5ac5637023c1790d4e572aefb33ceb6e9cc0f1a","unresolved":true,"context_lines":[{"line_number":368,"context_line":".. note::"},{"line_number":369,"context_line":"   To become a member of the ``openstack-unmaintained-core`` team, first"},{"line_number":370,"context_line":"   the stable policy has to be understood, as it still applies to"},{"line_number":371,"context_line":"   unmaintained branches as well. Then contact the group itself and"},{"line_number":372,"context_line":"   signal the interest of becoming a member of the group and the intention"},{"line_number":373,"context_line":"   to maintain a project (or multiple projects) and its CI, then the"},{"line_number":374,"context_line":"   team will decide and grant membership."}],"source_content_type":"text/x-rst","patch_set":1,"id":"5ecb9797_c47ae4ee","line":371,"updated":"2024-03-01 17:15:15.000000000","message":"Does it make sense to define a preferred way of contacting them? Like who would a new contributor even find out whom to contact?\n\nIIUC currently the team is only defined by gerrit membership, do you think it would be useful to define it as a SIG? that would for example allow to have some contact and membership information listed on the governance pages","commit_id":"8f25583cabd1424b9520efe29556e9c2b18c4fd3"},{"author":{"_account_id":8556,"name":"Ghanshyam Maan","display_name":"Ghanshyam Maan","email":"gmaan.os14@gmail.com","username":"ghanshyam"},"change_message_id":"a36b2971e1d9c93bc4a081487bb50680e86ea95f","unresolved":true,"context_lines":[{"line_number":368,"context_line":".. note::"},{"line_number":369,"context_line":"   To become a member of the ``openstack-unmaintained-core`` team, first"},{"line_number":370,"context_line":"   the stable policy has to be understood, as it still applies to"},{"line_number":371,"context_line":"   unmaintained branches as well. Then contact the group itself and"},{"line_number":372,"context_line":"   signal the interest of becoming a member of the group and the intention"},{"line_number":373,"context_line":"   to maintain a project (or multiple projects) and its CI, then the"},{"line_number":374,"context_line":"   team will decide and grant membership."}],"source_content_type":"text/x-rst","patch_set":1,"id":"692a5b2e_7d37bac0","line":371,"in_reply_to":"3a76d643_dbe7d0a6","updated":"2024-03-01 18:04:04.000000000","message":"I am not much in favor of defining a SIG which is again moving things under the upstream maintenance. We should keep \u0027unmaintained\u0027 process/branch/team as explicit different than what project/SIG team care of. That is why we have this group as explicit than the existing stable-core group.\n\nI will say to link the gerrit group here to know whom to contact for it https://review.opendev.org/admin/groups/4d728691952c04b8b2ec828eabc96b98dc124d69,members","commit_id":"8f25583cabd1424b9520efe29556e9c2b18c4fd3"},{"author":{"_account_id":5314,"name":"Brian Rosmaita","email":"rosmaita.fossdev@gmail.com","username":"brian-rosmaita"},"change_message_id":"5e6937c72fa261b45fd11001cdc89f593cc81b21","unresolved":true,"context_lines":[{"line_number":368,"context_line":".. note::"},{"line_number":369,"context_line":"   To become a member of the ``openstack-unmaintained-core`` team, first"},{"line_number":370,"context_line":"   the stable policy has to be understood, as it still applies to"},{"line_number":371,"context_line":"   unmaintained branches as well. Then contact the group itself and"},{"line_number":372,"context_line":"   signal the interest of becoming a member of the group and the intention"},{"line_number":373,"context_line":"   to maintain a project (or multiple projects) and its CI, then the"},{"line_number":374,"context_line":"   team will decide and grant membership."}],"source_content_type":"text/x-rst","patch_set":1,"id":"3a76d643_dbe7d0a6","line":371,"in_reply_to":"59678cc4_08976e3e","updated":"2024-03-01 17:38:06.000000000","message":"The SIG idea sounds good to me.  You can keep it lightweight (e.g., only meet monthly until there\u0027s a reason to have higher frequency) and like frickler says, it will give you a landing place for some contact info.","commit_id":"8f25583cabd1424b9520efe29556e9c2b18c4fd3"},{"author":{"_account_id":17685,"name":"Elod Illes","email":"elod.illes@est.tech","username":"elod.illes"},"change_message_id":"3a06e748662350134b2fff9278863e3335edc4c6","unresolved":true,"context_lines":[{"line_number":368,"context_line":".. note::"},{"line_number":369,"context_line":"   To become a member of the ``openstack-unmaintained-core`` team, first"},{"line_number":370,"context_line":"   the stable policy has to be understood, as it still applies to"},{"line_number":371,"context_line":"   unmaintained branches as well. Then contact the group itself and"},{"line_number":372,"context_line":"   signal the interest of becoming a member of the group and the intention"},{"line_number":373,"context_line":"   to maintain a project (or multiple projects) and its CI, then the"},{"line_number":374,"context_line":"   team will decide and grant membership."}],"source_content_type":"text/x-rst","patch_set":1,"id":"59678cc4_08976e3e","line":371,"in_reply_to":"5ecb9797_c47ae4ee","updated":"2024-03-01 17:21:14.000000000","message":"sounds OK to me! if we agree on it then we can do that, yes.","commit_id":"8f25583cabd1424b9520efe29556e9c2b18c4fd3"},{"author":{"_account_id":8556,"name":"Ghanshyam Maan","display_name":"Ghanshyam Maan","email":"gmaan.os14@gmail.com","username":"ghanshyam"},"change_message_id":"a36b2971e1d9c93bc4a081487bb50680e86ea95f","unresolved":true,"context_lines":[{"line_number":370,"context_line":"   the stable policy has to be understood, as it still applies to"},{"line_number":371,"context_line":"   unmaintained branches as well. Then contact the group itself and"},{"line_number":372,"context_line":"   signal the interest of becoming a member of the group and the intention"},{"line_number":373,"context_line":"   to maintain a project (or multiple projects) and its CI, then the"},{"line_number":374,"context_line":"   team will decide and grant membership."},{"line_number":375,"context_line":""},{"line_number":376,"context_line":"Review guidelines"}],"source_content_type":"text/x-rst","patch_set":1,"id":"07c8854f_bda9b24d","line":373,"range":{"start_line":373,"start_character":48,"end_line":373,"end_character":59},"updated":"2024-03-01 18:04:04.000000000","message":"this was one of the confusion people had in discussion. What I understood from above paragraph as well this line that, member in global ``openstack-unmaintained-core`` or project specific ``PROJECTNAME-unmaintained-core`` group are responsible to maintain the CI (single or multiple projects) not just add/remove the members. Which is why encouraging \"member to be part of global group and if really needed then only create the project specific group\" make sense.\n\nso +1 on adding the CI maintenance responsibility explicitly here too.","commit_id":"8f25583cabd1424b9520efe29556e9c2b18c4fd3"},{"author":{"_account_id":5314,"name":"Brian Rosmaita","email":"rosmaita.fossdev@gmail.com","username":"brian-rosmaita"},"change_message_id":"5e6937c72fa261b45fd11001cdc89f593cc81b21","unresolved":true,"context_lines":[{"line_number":371,"context_line":"   unmaintained branches as well. Then contact the group itself and"},{"line_number":372,"context_line":"   signal the interest of becoming a member of the group and the intention"},{"line_number":373,"context_line":"   to maintain a project (or multiple projects) and its CI, then the"},{"line_number":374,"context_line":"   team will decide and grant membership."},{"line_number":375,"context_line":""},{"line_number":376,"context_line":"Review guidelines"},{"line_number":377,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"}],"source_content_type":"text/x-rst","patch_set":1,"id":"52985e82_0156832f","line":374,"updated":"2024-03-01 17:38:06.000000000","message":"One suggestion for when you rewrite this Note to mention the SIG ... do it as an ordered list, and then you can do what we do on the contributor page somewhere:\n\n1. read and understand ...\n2. go back and read #1\n3. contact the Unmaintenance SIG","commit_id":"8f25583cabd1424b9520efe29556e9c2b18c4fd3"}]}