)]}'
{"resolutions/20190711-mandatory-repository-retirement.rst":[{"author":{"_account_id":5263,"name":"Jeremy Stanley","display_name":"fungi","email":"fungi@yuggoth.org","username":"fungi","status":"missing, presumed fed"},"change_message_id":"82d2fd28f5d3c91d1a8a40009233d53fbc4fe8f4","unresolved":false,"context_lines":[{"line_number":6,"context_line":"Projects \u003c20190322-namespace-unofficial-projects\u003e`, only current or"},{"line_number":7,"context_line":"former official OpenStack deliverable repositories (or those managed"},{"line_number":8,"context_line":"by SIGs, working groups and other officially recognized bodies)"},{"line_number":9,"context_line":"remain within the ``openstack`` Git namespace prefix on OpenDev."},{"line_number":10,"context_line":"Formerly official software which left OpenStack governance with the"},{"line_number":11,"context_line":"intent of continuing development outside it was in many cases"},{"line_number":12,"context_line":"subsequently abandoned in place by its authors, creating an"}],"source_content_type":"text/x-rst","patch_set":2,"id":"7faddb67_4e06c71e","line":9,"updated":"2019-07-15 13:17:14.000000000","message":"There are likely plenty of projects on PyPI with \"openstack\" in their distnames which aren\u0027t and never were official OpenStack deliverables. Short of threatening legal action to exercise trademark rights I don\u0027t expect we have much control over it, and I prefer to just accept that and not tell projects they need to change names when they give up OpenStack governance. The OpenStack TC doesn\u0027t have jurisdiction over what\u0027s published to PyPI, but it has been granted jurisdiction over what repositories appear in the \"openstack\" Git namespace on OpenDev.","commit_id":"d9a9bf03126b990cba4c7bcdbda162c94f596197"},{"author":{"_account_id":24162,"name":"Sorin Sbârnea","display_name":"zbr","email":"ssbarnea@redhat.com","username":"ssbarnea","status":"do not feed the troll 🥕"},"change_message_id":"8fc50c2b1f27e8e466b4e08880b69804e0718d17","unresolved":false,"context_lines":[{"line_number":6,"context_line":"Projects \u003c20190322-namespace-unofficial-projects\u003e`, only current or"},{"line_number":7,"context_line":"former official OpenStack deliverable repositories (or those managed"},{"line_number":8,"context_line":"by SIGs, working groups and other officially recognized bodies)"},{"line_number":9,"context_line":"remain within the ``openstack`` Git namespace prefix on OpenDev."},{"line_number":10,"context_line":"Formerly official software which left OpenStack governance with the"},{"line_number":11,"context_line":"intent of continuing development outside it was in many cases"},{"line_number":12,"context_line":"subsequently abandoned in place by its authors, creating an"}],"source_content_type":"text/x-rst","patch_set":2,"id":"7faddb67_e3154ce6","line":9,"range":{"start_line":9,"start_character":31,"end_line":9,"end_character":64},"updated":"2019-07-15 12:29:53.000000000","message":"While I think that this policy is needed it should also address the aspect of PYPI publication.\n\nI think we need to mention what should happen with ownership of PYPI packages because we do not want to force people to change packages names when they fork a project in order to maintain it.\n\nIf the PYPI project has openstack in its name, I see no problem on locking it. But, if the project does not have openstack in its name, we should allow future maintainers to take ownership of the package, so they can release new versions. I guess they will agree not to remove the repository (they cannot replace or delete releases by PYPI design)","commit_id":"d9a9bf03126b990cba4c7bcdbda162c94f596197"},{"author":{"_account_id":4146,"name":"Clark Boylan","email":"cboylan@sapwetik.org","username":"cboylan"},"change_message_id":"43e3d5c7303f2c6c2d526168ec97251c91ee41bc","unresolved":false,"context_lines":[{"line_number":6,"context_line":"Projects \u003c20190322-namespace-unofficial-projects\u003e`, only current or"},{"line_number":7,"context_line":"former official OpenStack deliverable repositories (or those managed"},{"line_number":8,"context_line":"by SIGs, working groups and other officially recognized bodies)"},{"line_number":9,"context_line":"remain within the ``openstack`` Git namespace prefix on OpenDev."},{"line_number":10,"context_line":"Formerly official software which left OpenStack governance with the"},{"line_number":11,"context_line":"intent of continuing development outside it was in many cases"},{"line_number":12,"context_line":"subsequently abandoned in place by its authors, creating an"}],"source_content_type":"text/x-rst","patch_set":2,"id":"7faddb67_70327912","line":9,"in_reply_to":"7faddb67_4e06c71e","updated":"2019-07-15 22:08:04.000000000","message":"It probably is worth considering that if the intent is to reduce end user confusion that a project going from TC governance to non TC governance while publishing to the same name on eg PyPI doesn\u0027t signal that transition at all. Its a similar problem to the one with code hosting just on another platform.\n\nWhile I agree that for simplicity (because updating all the code to use different names is a pain no one should endure) keeping the old name as is and moving forward is the best choice here we may want to consider what signalling of change we can expose on platforms like PyPI.","commit_id":"d9a9bf03126b990cba4c7bcdbda162c94f596197"},{"author":{"_account_id":4257,"name":"Zane Bitter","email":"zbitter@redhat.com","username":"zaneb"},"change_message_id":"d881794263ea42a80ee3b0abaf034d214ff61386","unresolved":false,"context_lines":[{"line_number":7,"context_line":"former official OpenStack deliverable repositories (or those managed"},{"line_number":8,"context_line":"by SIGs, working groups and other officially recognized bodies)"},{"line_number":9,"context_line":"remain within the ``openstack`` Git namespace prefix on OpenDev."},{"line_number":10,"context_line":"Formerly official software which left OpenStack governance with the"},{"line_number":11,"context_line":"intent of continuing development outside it was in many cases"},{"line_number":12,"context_line":"subsequently abandoned in place by its authors, creating an"},{"line_number":13,"context_line":"attractive nuisance and unwitting surprise for source consumers who"}],"source_content_type":"text/x-rst","patch_set":2,"id":"7faddb67_74f57bec","line":10,"range":{"start_line":10,"start_character":0,"end_line":10,"end_character":17},"updated":"2019-07-16 20:00:15.000000000","message":"I can\u0027t decide whether this is supposed to be read with a comma or a hyphen between \u0027formerly\u0027 and \u0027official\u0027. Could you eliminate the ambiguity by adding one of them?","commit_id":"d9a9bf03126b990cba4c7bcdbda162c94f596197"},{"author":{"_account_id":10607,"name":"Alexandra Settle","email":"a.settle@outlook.com","username":"asettle"},"change_message_id":"ae1f0bf1db3049b91f40865c55d9c5a50d84fdf3","unresolved":false,"context_lines":[{"line_number":7,"context_line":"former official OpenStack deliverable repositories (or those managed"},{"line_number":8,"context_line":"by SIGs, working groups and other officially recognized bodies)"},{"line_number":9,"context_line":"remain within the ``openstack`` Git namespace prefix on OpenDev."},{"line_number":10,"context_line":"Formerly official software which left OpenStack governance with the"},{"line_number":11,"context_line":"intent of continuing development outside it was in many cases"},{"line_number":12,"context_line":"subsequently abandoned in place by its authors, creating an"},{"line_number":13,"context_line":"attractive nuisance and unwitting surprise for source consumers who"}],"source_content_type":"text/x-rst","patch_set":2,"id":"7faddb67_2e79c0c6","line":10,"range":{"start_line":10,"start_character":0,"end_line":10,"end_character":17},"in_reply_to":"7faddb67_74f57bec","updated":"2019-07-19 12:34:31.000000000","message":"Formerly official software, which left OpenStack governance with the itent of continuining outside it was in many cases\nsubsequently abandoned in place by its authors, creating an... * (the comma makes more sense, basically)","commit_id":"d9a9bf03126b990cba4c7bcdbda162c94f596197"},{"author":{"_account_id":4257,"name":"Zane Bitter","email":"zbitter@redhat.com","username":"zaneb"},"change_message_id":"d881794263ea42a80ee3b0abaf034d214ff61386","unresolved":false,"context_lines":[{"line_number":14,"context_line":"(in at least some cases) likely continued unaware that it was no"},{"line_number":15,"context_line":"longer supported by anyone at all."},{"line_number":16,"context_line":""},{"line_number":17,"context_line":"When OpenStack ceases development on a source code repository,"},{"line_number":18,"context_line":"OpenDev\u0027s recommended `retirement process"},{"line_number":19,"context_line":"\u003chttps://docs.openstack.org/infra/manual/drivers.html#retiring-a-project\u003e`_"},{"line_number":20,"context_line":"is followed to replace that repository\u0027s source code with a"},{"line_number":21,"context_line":"prominent ``README`` message indicating its new situation, abandons"},{"line_number":22,"context_line":"all open changes for it, and sets Gerrit to reject future change"},{"line_number":23,"context_line":"proposals for review. When projects choose to continue development"},{"line_number":24,"context_line":"for formerly official OpenStack deliverables outside OpenStack"},{"line_number":25,"context_line":"governance, no similar process exists to clarify to users that"},{"line_number":26,"context_line":"OpenStack is no longer responsible for these repositories. This"}],"source_content_type":"text/x-rst","patch_set":2,"id":"7faddb67_14c76798","line":23,"range":{"start_line":17,"start_character":0,"end_line":23,"end_character":21},"updated":"2019-07-16 20:00:15.000000000","message":"This sentence is hard to read because the verbs don\u0027t agree.","commit_id":"d9a9bf03126b990cba4c7bcdbda162c94f596197"},{"author":{"_account_id":10607,"name":"Alexandra Settle","email":"a.settle@outlook.com","username":"asettle"},"change_message_id":"ae1f0bf1db3049b91f40865c55d9c5a50d84fdf3","unresolved":false,"context_lines":[{"line_number":14,"context_line":"(in at least some cases) likely continued unaware that it was no"},{"line_number":15,"context_line":"longer supported by anyone at all."},{"line_number":16,"context_line":""},{"line_number":17,"context_line":"When OpenStack ceases development on a source code repository,"},{"line_number":18,"context_line":"OpenDev\u0027s recommended `retirement process"},{"line_number":19,"context_line":"\u003chttps://docs.openstack.org/infra/manual/drivers.html#retiring-a-project\u003e`_"},{"line_number":20,"context_line":"is followed to replace that repository\u0027s source code with a"},{"line_number":21,"context_line":"prominent ``README`` message indicating its new situation, abandons"},{"line_number":22,"context_line":"all open changes for it, and sets Gerrit to reject future change"},{"line_number":23,"context_line":"proposals for review. When projects choose to continue development"},{"line_number":24,"context_line":"for formerly official OpenStack deliverables outside OpenStack"},{"line_number":25,"context_line":"governance, no similar process exists to clarify to users that"},{"line_number":26,"context_line":"OpenStack is no longer responsible for these repositories. This"}],"source_content_type":"text/x-rst","patch_set":2,"id":"7faddb67_8e479477","line":23,"range":{"start_line":17,"start_character":0,"end_line":23,"end_character":21},"in_reply_to":"7faddb67_14c76798","updated":"2019-07-19 12:34:31.000000000","message":"Suggested rewrite:\n\nWhen development ceases on a source code repository, the `retirement process\n\u003chttps://docs.openstack.org/infra/manual/drivers.html#retiring-a-project\u003e`_ is followed. This process replaces the repository\u0027s source code with a message in a ``README``file indicating the source code\u0027s new situation, abandons all open changes for the project, and sets Gerrit to reject future change proposals for review.","commit_id":"d9a9bf03126b990cba4c7bcdbda162c94f596197"},{"author":{"_account_id":4257,"name":"Zane Bitter","email":"zbitter@redhat.com","username":"zaneb"},"change_message_id":"d881794263ea42a80ee3b0abaf034d214ff61386","unresolved":false,"context_lines":[{"line_number":21,"context_line":"prominent ``README`` message indicating its new situation, abandons"},{"line_number":22,"context_line":"all open changes for it, and sets Gerrit to reject future change"},{"line_number":23,"context_line":"proposals for review. When projects choose to continue development"},{"line_number":24,"context_line":"for formerly official OpenStack deliverables outside OpenStack"},{"line_number":25,"context_line":"governance, no similar process exists to clarify to users that"},{"line_number":26,"context_line":"OpenStack is no longer responsible for these repositories. This"},{"line_number":27,"context_line":"problem is further complicated by OpenDev\u0027s use of Gitea and its"}],"source_content_type":"text/x-rst","patch_set":2,"id":"7faddb67_b46693c0","line":24,"range":{"start_line":24,"start_character":4,"end_line":24,"end_character":21},"updated":"2019-07-16 20:00:15.000000000","message":"Consider also using \u0027formerly-official\u0027 here for consistency.","commit_id":"d9a9bf03126b990cba4c7bcdbda162c94f596197"},{"author":{"_account_id":10607,"name":"Alexandra Settle","email":"a.settle@outlook.com","username":"asettle"},"change_message_id":"ae1f0bf1db3049b91f40865c55d9c5a50d84fdf3","unresolved":false,"context_lines":[{"line_number":22,"context_line":"all open changes for it, and sets Gerrit to reject future change"},{"line_number":23,"context_line":"proposals for review. When projects choose to continue development"},{"line_number":24,"context_line":"for formerly official OpenStack deliverables outside OpenStack"},{"line_number":25,"context_line":"governance, no similar process exists to clarify to users that"},{"line_number":26,"context_line":"OpenStack is no longer responsible for these repositories. This"},{"line_number":27,"context_line":"problem is further complicated by OpenDev\u0027s use of Gitea and its"},{"line_number":28,"context_line":"automatic redirect feature, where simply renaming those projects to"}],"source_content_type":"text/x-rst","patch_set":2,"id":"7faddb67_0e53a43a","line":25,"range":{"start_line":25,"start_character":15,"end_line":25,"end_character":22},"updated":"2019-07-19 12:34:31.000000000","message":"corresponding?","commit_id":"d9a9bf03126b990cba4c7bcdbda162c94f596197"},{"author":{"_account_id":10607,"name":"Alexandra Settle","email":"a.settle@outlook.com","username":"asettle"},"change_message_id":"ae1f0bf1db3049b91f40865c55d9c5a50d84fdf3","unresolved":false,"context_lines":[{"line_number":24,"context_line":"for formerly official OpenStack deliverables outside OpenStack"},{"line_number":25,"context_line":"governance, no similar process exists to clarify to users that"},{"line_number":26,"context_line":"OpenStack is no longer responsible for these repositories. This"},{"line_number":27,"context_line":"problem is further complicated by OpenDev\u0027s use of Gitea and its"},{"line_number":28,"context_line":"automatic redirect feature, where simply renaming those projects to"},{"line_number":29,"context_line":"move them to a new Git prefix namespace leaves their old"},{"line_number":30,"context_line":"``openstack`` URLs working for browsers and Git client operations so"}],"source_content_type":"text/x-rst","patch_set":2,"id":"7faddb67_ce36ec03","line":27,"range":{"start_line":27,"start_character":51,"end_line":27,"end_character":57},"updated":"2019-07-19 12:34:31.000000000","message":"TIL","commit_id":"d9a9bf03126b990cba4c7bcdbda162c94f596197"},{"author":{"_account_id":10607,"name":"Alexandra Settle","email":"a.settle@outlook.com","username":"asettle"},"change_message_id":"ae1f0bf1db3049b91f40865c55d9c5a50d84fdf3","unresolved":false,"context_lines":[{"line_number":25,"context_line":"governance, no similar process exists to clarify to users that"},{"line_number":26,"context_line":"OpenStack is no longer responsible for these repositories. This"},{"line_number":27,"context_line":"problem is further complicated by OpenDev\u0027s use of Gitea and its"},{"line_number":28,"context_line":"automatic redirect feature, where simply renaming those projects to"},{"line_number":29,"context_line":"move them to a new Git prefix namespace leaves their old"},{"line_number":30,"context_line":"``openstack`` URLs working for browsers and Git client operations so"},{"line_number":31,"context_line":"many existing users may never notice the transition."}],"source_content_type":"text/x-rst","patch_set":2,"id":"7faddb67_2e2780cc","line":28,"range":{"start_line":28,"start_character":18,"end_line":28,"end_character":27},"updated":"2019-07-19 12:34:31.000000000","message":"feature. Renaming these projects to move them ... *","commit_id":"d9a9bf03126b990cba4c7bcdbda162c94f596197"},{"author":{"_account_id":11655,"name":"Julia Kreger","email":"juliaashleykreger@gmail.com","username":"jkreger","status":"Flying to the moon with a Jetpack!"},"change_message_id":"ed1f334687615db167c19c1cb5a7774d02247252","unresolved":false,"context_lines":[{"line_number":31,"context_line":"many existing users may never notice the transition."},{"line_number":32,"context_line":""},{"line_number":33,"context_line":"The solution to this problem is to follow the repository retirement"},{"line_number":34,"context_line":"process in ``openstack`` any time a deliverable repository is"},{"line_number":35,"context_line":"removed from current governance, regardless of whether its authors"},{"line_number":36,"context_line":"intend to continue development on it outside governance. OpenDev"},{"line_number":37,"context_line":"allows multiple repositories to have the same base names across"},{"line_number":38,"context_line":"different namespaces, so this does not mean a project has to change"}],"source_content_type":"text/x-rst","patch_set":2,"id":"7faddb67_251025a8","line":35,"range":{"start_line":34,"start_character":25,"end_line":35,"end_character":32},"updated":"2019-07-17 11:14:22.000000000","message":"This, and reading up to this part, makes me feel like I have to release every repo, even repos that are misc tooling for CI that have zero deliverable value, in order to keep it in the namespace, which further increases the overhead and further increases PTL burnout.\n\nAm I really interpreting this correctly?\n\nAre we really heading down the more process path with the concept that everything is a releasable publishable artifact?","commit_id":"d9a9bf03126b990cba4c7bcdbda162c94f596197"},{"author":{"_account_id":5263,"name":"Jeremy Stanley","display_name":"fungi","email":"fungi@yuggoth.org","username":"fungi","status":"missing, presumed fed"},"change_message_id":"aa6c07469ede5fb645e5632413c16fee39248bc4","unresolved":false,"context_lines":[{"line_number":32,"context_line":""},{"line_number":33,"context_line":"The solution to this problem is to follow the repository retirement"},{"line_number":34,"context_line":"process in ``openstack`` any time a deliverable repository is"},{"line_number":35,"context_line":"removed from current governance, regardless of whether its authors"},{"line_number":36,"context_line":"intend to continue development on it outside governance. OpenDev"},{"line_number":37,"context_line":"allows multiple repositories to have the same base names across"},{"line_number":38,"context_line":"different namespaces, so this does not mean a project has to change"}],"source_content_type":"text/x-rst","patch_set":2,"id":"7faddb67_e81f4405","line":35,"updated":"2019-07-17 12:04:08.000000000","message":"What in this text gives you the impression that any of these repositories need to have releases? This is entirely about retiring copies of repositories within the \"openstack\" Git namespace if they leave OpenStack governance (and expecting them to fork if they wish to continue development outside official OpenStack governance). It says nothing about whether or not they need to tag releases. We already follow this retirement process when development ceases on official deliverable repositories, and this would simply make it required to follow the same process for any which wish to continue development somewhere else (in a different Git namespace on OpenDev or outside OpenDev entirely).","commit_id":"d9a9bf03126b990cba4c7bcdbda162c94f596197"},{"author":{"_account_id":10607,"name":"Alexandra Settle","email":"a.settle@outlook.com","username":"asettle"},"change_message_id":"ae1f0bf1db3049b91f40865c55d9c5a50d84fdf3","unresolved":false,"context_lines":[{"line_number":32,"context_line":""},{"line_number":33,"context_line":"The solution to this problem is to follow the repository retirement"},{"line_number":34,"context_line":"process in ``openstack`` any time a deliverable repository is"},{"line_number":35,"context_line":"removed from current governance, regardless of whether its authors"},{"line_number":36,"context_line":"intend to continue development on it outside governance. OpenDev"},{"line_number":37,"context_line":"allows multiple repositories to have the same base names across"},{"line_number":38,"context_line":"different namespaces, so this does not mean a project has to change"}],"source_content_type":"text/x-rst","patch_set":2,"id":"7faddb67_4e0bdc28","line":35,"in_reply_to":"7faddb67_e81f4405","updated":"2019-07-19 12:34:31.000000000","message":"Perhaps a re-read after some edits have been made might help. I admittedly don\u0027t see what you see there, Julia. But your interpretation may be similar to others so we want to ensure that\u0027s not the case - as Jeremy says, this is only able retiring copies of repos.","commit_id":"d9a9bf03126b990cba4c7bcdbda162c94f596197"},{"author":{"_account_id":5263,"name":"Jeremy Stanley","display_name":"fungi","email":"fungi@yuggoth.org","username":"fungi","status":"missing, presumed fed"},"change_message_id":"5a0fe737a02bcae993b108d786dc6c28ac69bde2","unresolved":false,"context_lines":[{"line_number":33,"context_line":"The solution to this problem is to follow the repository retirement"},{"line_number":34,"context_line":"process in ``openstack`` any time a deliverable repository is"},{"line_number":35,"context_line":"removed from current governance, regardless of whether its authors"},{"line_number":36,"context_line":"intend to continue development on it outside governance. OpenDev"},{"line_number":37,"context_line":"allows multiple repositories to have the same base names across"},{"line_number":38,"context_line":"different namespaces, so this does not mean a project has to change"},{"line_number":39,"context_line":"its new name. It does however mean that the repository must be"}],"source_content_type":"text/x-rst","patch_set":2,"id":"7faddb67_6b7a8af1","line":36,"updated":"2019-07-15 23:09:32.000000000","message":"Further discussion in #openstack-infra has raised that there is currently a blind spot in this plan. There are still some repositories listed in governance for the Infrastructure team which are not in the \"openstack\" namespace (they\u0027ve already been renamed into the \"opendev\" namespace). Options are to either add a carveout in the policy in case they\u0027re not removed from governance by the end of the Train cycle, assume that they will be removed from governance before then, or just interpret the requirement to follow retirement in the \"openstack\" namespace as implicitly meaning it\u0027s not necessary for those repos which have already been renamed out of the namespace even if they\u0027re removed from governance after the deadline (as the retirement process can\u0027t logically be applied within the \"openstack\" namespace for them anyway).","commit_id":"d9a9bf03126b990cba4c7bcdbda162c94f596197"},{"author":{"_account_id":4146,"name":"Clark Boylan","email":"cboylan@sapwetik.org","username":"cboylan"},"change_message_id":"43e3d5c7303f2c6c2d526168ec97251c91ee41bc","unresolved":false,"context_lines":[{"line_number":33,"context_line":"The solution to this problem is to follow the repository retirement"},{"line_number":34,"context_line":"process in ``openstack`` any time a deliverable repository is"},{"line_number":35,"context_line":"removed from current governance, regardless of whether its authors"},{"line_number":36,"context_line":"intend to continue development on it outside governance. OpenDev"},{"line_number":37,"context_line":"allows multiple repositories to have the same base names across"},{"line_number":38,"context_line":"different namespaces, so this does not mean a project has to change"},{"line_number":39,"context_line":"its new name. It does however mean that the repository must be"},{"line_number":40,"context_line":"forked into the new namespace, leaving behind its Gerrit reviews and"},{"line_number":41,"context_line":"not having its repository redirected in Gitea (the ``README`` file"}],"source_content_type":"text/x-rst","patch_set":2,"id":"7faddb67_b0a8f11f","line":38,"range":{"start_line":36,"start_character":57,"end_line":38,"end_character":20},"updated":"2019-07-15 22:08:04.000000000","message":"While the hosting software is perfectly fine with this there may be corner cases in other tooling that doesn\u0027t handle this well. I expect we\u0027ll just roll forward and fix any instances of that but worth being aware that there may be unexpected speed bumps around this.","commit_id":"d9a9bf03126b990cba4c7bcdbda162c94f596197"},{"author":{"_account_id":10607,"name":"Alexandra Settle","email":"a.settle@outlook.com","username":"asettle"},"change_message_id":"ae1f0bf1db3049b91f40865c55d9c5a50d84fdf3","unresolved":false,"context_lines":[{"line_number":37,"context_line":"allows multiple repositories to have the same base names across"},{"line_number":38,"context_line":"different namespaces, so this does not mean a project has to change"},{"line_number":39,"context_line":"its new name. It does however mean that the repository must be"},{"line_number":40,"context_line":"forked into the new namespace, leaving behind its Gerrit reviews and"},{"line_number":41,"context_line":"not having its repository redirected in Gitea (the ``README`` file"},{"line_number":42,"context_line":"can certainly mention where to find continued development however)."},{"line_number":43,"context_line":"This forces existing consumers of the source code to take note of"},{"line_number":44,"context_line":"the change in governance, so they can be made aware OpenStack is no"},{"line_number":45,"context_line":"longer responsible for what is being developed there."}],"source_content_type":"text/x-rst","patch_set":2,"id":"7faddb67_b0518e38","line":42,"range":{"start_line":40,"start_character":31,"end_line":42,"end_character":66},"updated":"2019-07-19 12:34:31.000000000","message":"maybe just say \"new namespace, leaving historical context in Gerrit and no redirection.\" otherwise it\u0027s just a bit repetitive","commit_id":"d9a9bf03126b990cba4c7bcdbda162c94f596197"},{"author":{"_account_id":4146,"name":"Clark Boylan","email":"cboylan@sapwetik.org","username":"cboylan"},"change_message_id":"43e3d5c7303f2c6c2d526168ec97251c91ee41bc","unresolved":false,"context_lines":[{"line_number":40,"context_line":"forked into the new namespace, leaving behind its Gerrit reviews and"},{"line_number":41,"context_line":"not having its repository redirected in Gitea (the ``README`` file"},{"line_number":42,"context_line":"can certainly mention where to find continued development however)."},{"line_number":43,"context_line":"This forces existing consumers of the source code to take note of"},{"line_number":44,"context_line":"the change in governance, so they can be made aware OpenStack is no"},{"line_number":45,"context_line":"longer responsible for what is being developed there."},{"line_number":46,"context_line":""}],"source_content_type":"text/x-rst","patch_set":2,"id":"7faddb67_b02b1193","line":43,"updated":"2019-07-15 22:08:04.000000000","message":"Do we expect that most consumers of our software consume it from source directly or instead via something like PyPI or distro packages?","commit_id":"d9a9bf03126b990cba4c7bcdbda162c94f596197"},{"author":{"_account_id":5263,"name":"Jeremy Stanley","display_name":"fungi","email":"fungi@yuggoth.org","username":"fungi","status":"missing, presumed fed"},"change_message_id":"9a8cdc38148395bc05c79b49ac4d6e6ea0a46ddc","unresolved":false,"context_lines":[{"line_number":40,"context_line":"forked into the new namespace, leaving behind its Gerrit reviews and"},{"line_number":41,"context_line":"not having its repository redirected in Gitea (the ``README`` file"},{"line_number":42,"context_line":"can certainly mention where to find continued development however)."},{"line_number":43,"context_line":"This forces existing consumers of the source code to take note of"},{"line_number":44,"context_line":"the change in governance, so they can be made aware OpenStack is no"},{"line_number":45,"context_line":"longer responsible for what is being developed there."},{"line_number":46,"context_line":""}],"source_content_type":"text/x-rst","patch_set":2,"id":"7faddb67_abc64267","line":43,"updated":"2019-07-15 22:42:09.000000000","message":"The concern being addressed is with consumers of the source code, so distro package maintainers and folks continuously deploying directly from revision control. Also this at least provides a warning somewhere, in the cases of primary concern where repositories leave OpenStack and then get abandoned yet their confused users continue reaching out to the OpenStack community to ask questions or attempt to file bug reports.\n\nFor indirect consumers like users of packages on PyPI or in various distros, other clues will be present (such as previous documentation URLs going away). It\u0027s also the responsibility of distro package maintainers to handle these sorts of changes on behalf of their users, and they ought to notice the next time they go to update their packages that the source code is no longer available at the same place they previously accessed it.\n\nAlso, at least for many direct or indirect users, when they go hunting down the source code hosting location to figure out where to report bugs, they should hopefully find the message we\u0027ve left for them letting them know what\u0027s happened and/or where to go.","commit_id":"d9a9bf03126b990cba4c7bcdbda162c94f596197"},{"author":{"_account_id":10607,"name":"Alexandra Settle","email":"a.settle@outlook.com","username":"asettle"},"change_message_id":"ae1f0bf1db3049b91f40865c55d9c5a50d84fdf3","unresolved":false,"context_lines":[{"line_number":41,"context_line":"not having its repository redirected in Gitea (the ``README`` file"},{"line_number":42,"context_line":"can certainly mention where to find continued development however)."},{"line_number":43,"context_line":"This forces existing consumers of the source code to take note of"},{"line_number":44,"context_line":"the change in governance, so they can be made aware OpenStack is no"},{"line_number":45,"context_line":"longer responsible for what is being developed there."},{"line_number":46,"context_line":""},{"line_number":47,"context_line":"Because this is a significant change in policy, it cannot easily be"},{"line_number":48,"context_line":"retroactively applied to old repositories which are no longer under"}],"source_content_type":"text/x-rst","patch_set":2,"id":"7faddb67_50393aef","line":45,"range":{"start_line":44,"start_character":52,"end_line":45,"end_character":18},"updated":"2019-07-19 12:34:31.000000000","message":"\"OpenStack\" taking responsible seems deliberately vague?","commit_id":"d9a9bf03126b990cba4c7bcdbda162c94f596197"},{"author":{"_account_id":10607,"name":"Alexandra Settle","email":"a.settle@outlook.com","username":"asettle"},"change_message_id":"ae1f0bf1db3049b91f40865c55d9c5a50d84fdf3","unresolved":false,"context_lines":[{"line_number":42,"context_line":"can certainly mention where to find continued development however)."},{"line_number":43,"context_line":"This forces existing consumers of the source code to take note of"},{"line_number":44,"context_line":"the change in governance, so they can be made aware OpenStack is no"},{"line_number":45,"context_line":"longer responsible for what is being developed there."},{"line_number":46,"context_line":""},{"line_number":47,"context_line":"Because this is a significant change in policy, it cannot easily be"},{"line_number":48,"context_line":"retroactively applied to old repositories which are no longer under"}],"source_content_type":"text/x-rst","patch_set":2,"id":"7faddb67_30227eba","line":45,"range":{"start_line":45,"start_character":47,"end_line":45,"end_character":52},"updated":"2019-07-19 12:34:31.000000000","message":"remove","commit_id":"d9a9bf03126b990cba4c7bcdbda162c94f596197"},{"author":{"_account_id":5263,"name":"Jeremy Stanley","display_name":"fungi","email":"fungi@yuggoth.org","username":"fungi","status":"missing, presumed fed"},"change_message_id":"535d51e686aa665f38cf8fd2d0fbb3d726984cd8","unresolved":false,"context_lines":[{"line_number":53,"context_line":"will be subject to the new mandatory retirement policy. Removals"},{"line_number":54,"context_line":"prior to the end of the Train cycle can be renamed to new namespaces"},{"line_number":55,"context_line":"in OpenDev (with redirects) per our previous de facto process, if"},{"line_number":56,"context_line":"maintainers prefer."}],"source_content_type":"text/x-rst","patch_set":2,"id":"7faddb67_3e98361a","line":56,"updated":"2019-07-17 14:05:20.000000000","message":"Also, apologies that the timeframe is described in a somewhat circuitous fashion. Since we have no name for the \"U\" cycle yet, I\u0027m forced to make it relative to the \"Train\" cycle (otherwise I fear references to an as-of-yet unnamed cycle would be even less clear).","commit_id":"d9a9bf03126b990cba4c7bcdbda162c94f596197"},{"author":{"_account_id":5263,"name":"Jeremy Stanley","display_name":"fungi","email":"fungi@yuggoth.org","username":"fungi","status":"missing, presumed fed"},"change_message_id":"aa6c07469ede5fb645e5632413c16fee39248bc4","unresolved":false,"context_lines":[{"line_number":53,"context_line":"will be subject to the new mandatory retirement policy. Removals"},{"line_number":54,"context_line":"prior to the end of the Train cycle can be renamed to new namespaces"},{"line_number":55,"context_line":"in OpenDev (with redirects) per our previous de facto process, if"},{"line_number":56,"context_line":"maintainers prefer."}],"source_content_type":"text/x-rst","patch_set":2,"id":"7faddb67_881a5014","line":56,"updated":"2019-07-17 12:04:08.000000000","message":"It\u0027s meant to be a grace period for projects which are already intending to move out of OpenStack governance, so they can do so without forking if they request governance removal by the end of this cycle. This resolution itself would also not be the only notice, and in fact there\u0027s already an accompanying ML thread I sent to openstack-discuss tagged for PTLs (and others) to get their attention and feedback on the proposal. Suggestions for other means of bringing this to the attention of folks in charge of official teams in OpenStack are most welcome.","commit_id":"d9a9bf03126b990cba4c7bcdbda162c94f596197"},{"author":{"_account_id":11655,"name":"Julia Kreger","email":"juliaashleykreger@gmail.com","username":"jkreger","status":"Flying to the moon with a Jetpack!"},"change_message_id":"ed1f334687615db167c19c1cb5a7774d02247252","unresolved":false,"context_lines":[{"line_number":44,"context_line":"the change in governance, so they can be made aware OpenStack is no"},{"line_number":45,"context_line":"longer responsible for what is being developed there."},{"line_number":46,"context_line":""},{"line_number":47,"context_line":"Because this is a significant change in policy, it cannot easily be"},{"line_number":48,"context_line":"retroactively applied to old repositories which are no longer under"},{"line_number":49,"context_line":"OpenStack\u0027s governance (but the damage this would mitigate for them"},{"line_number":50,"context_line":"is probably already done anyway). To provide ample warning for any"},{"line_number":51,"context_line":"existing projects considering exiting OpenStack in the near future,"},{"line_number":52,"context_line":"only removals after the conclusion of the Train development cycle"},{"line_number":53,"context_line":"will be subject to the new mandatory retirement policy. Removals"},{"line_number":54,"context_line":"prior to the end of the Train cycle can be renamed to new namespaces"},{"line_number":55,"context_line":"in OpenDev (with redirects) per our previous de facto process, if"},{"line_number":56,"context_line":"maintainers prefer."}],"source_content_type":"text/x-rst","patch_set":2,"id":"7faddb67_c5583189","line":56,"range":{"start_line":47,"start_character":0,"end_line":56,"end_character":19},"updated":"2019-07-17 11:14:22.000000000","message":"This really ought to be reworded to be explicit.\n\nUnder this policy, X Y, and Z will happen. We recognize the pain and headache this creates, but this policy change is considered ample notice.\n\nPresently I start reading and think \"oh, less worry\" Then I parse a little more and grok that no, everyone this impacts is going to suffer.","commit_id":"d9a9bf03126b990cba4c7bcdbda162c94f596197"},{"author":{"_account_id":10607,"name":"Alexandra Settle","email":"a.settle@outlook.com","username":"asettle"},"change_message_id":"ae1f0bf1db3049b91f40865c55d9c5a50d84fdf3","unresolved":false,"context_lines":[{"line_number":53,"context_line":"will be subject to the new mandatory retirement policy. Removals"},{"line_number":54,"context_line":"prior to the end of the Train cycle can be renamed to new namespaces"},{"line_number":55,"context_line":"in OpenDev (with redirects) per our previous de facto process, if"},{"line_number":56,"context_line":"maintainers prefer."}],"source_content_type":"text/x-rst","patch_set":2,"id":"7faddb67_50129a63","line":56,"in_reply_to":"7faddb67_3e98361a","updated":"2019-07-19 12:34:31.000000000","message":"I agree with calling it out explicitly. Might be worthwhile having a separate heading for this. Something like \"summarised consequences\" or something. It\u0027ll be helpful to for people reading this to get to the point","commit_id":"d9a9bf03126b990cba4c7bcdbda162c94f596197"},{"author":{"_account_id":4257,"name":"Zane Bitter","email":"zbitter@redhat.com","username":"zaneb"},"change_message_id":"440b9e8b525c2924f0341370425b56add3f57653","unresolved":false,"context_lines":[{"line_number":41,"context_line":"or previously-official OpenStack deliverable repositories (or those"},{"line_number":42,"context_line":"managed by SIGs, working groups and other officially-recognized"},{"line_number":43,"context_line":"bodies) remain within the ``openstack`` Git namespace prefix on"},{"line_number":44,"context_line":"OpenDev. Formerly-official software, which left OpenStack governance"},{"line_number":45,"context_line":"with the intent of continuing development outside it, was in many"},{"line_number":46,"context_line":"cases subsequently abandoned in place by its authors. This created"},{"line_number":47,"context_line":"an attractive nuisance and unwitting surprise for source code"}],"source_content_type":"text/x-rst","patch_set":3,"id":"7faddb67_df12e309","line":44,"range":{"start_line":44,"start_character":35,"end_line":44,"end_character":42},"updated":"2019-07-23 21:25:44.000000000","message":"that","commit_id":"57ab6aef3900690e9ac48b974be1065962358097"},{"author":{"_account_id":11655,"name":"Julia Kreger","email":"juliaashleykreger@gmail.com","username":"jkreger","status":"Flying to the moon with a Jetpack!"},"change_message_id":"bb687ad0223a1dc402f10c7358bff101fed373ec","unresolved":false,"context_lines":[{"line_number":41,"context_line":"or previously-official OpenStack deliverable repositories (or those"},{"line_number":42,"context_line":"managed by SIGs, working groups and other officially-recognized"},{"line_number":43,"context_line":"bodies) remain within the ``openstack`` Git namespace prefix on"},{"line_number":44,"context_line":"OpenDev. Formerly-official software, which left OpenStack governance"},{"line_number":45,"context_line":"with the intent of continuing development outside it, was in many"},{"line_number":46,"context_line":"cases subsequently abandoned in place by its authors. This created"},{"line_number":47,"context_line":"an attractive nuisance and unwitting surprise for source code"}],"source_content_type":"text/x-rst","patch_set":3,"id":"7faddb67_b718871e","line":44,"range":{"start_line":44,"start_character":35,"end_line":44,"end_character":42},"in_reply_to":"7faddb67_df12e309","updated":"2019-08-07 18:47:38.000000000","message":"I think which is actually better, although likely flipping the sentence around might be better... or not.","commit_id":"57ab6aef3900690e9ac48b974be1065962358097"}]}