frickler | gmann: that was easy, seems with the retired.acl in place, I just needed my TC powers, no special superpowers. total number of config errors dropped from 342 to 329, but there were 37 for tripleo-ci, so a net 24 new errors | 05:02 |
---|---|---|
frickler | so most of the new errors are for unmaintained branches or for inactive projects (or both). putting up patches now for what remains. cc elodilles_pto | 05:23 |
frickler | that all, some may still need cherry-picks. all in all not nearly as bad as I had expected https://review.opendev.org/q/topic:%22drop-tripleo%22+OR+topic:%22remove-tripleo%22+status:open | 05:36 |
frickler | so I guess next up I can run some stable EOM branch cleanup | 05:45 |
tkajinam | frickler, I wonder if you can force-merge https://review.opendev.org/c/openstack/barbican/+/877812 . alternatively I can make all broken jobs non-voting so that we can merge it | 06:34 |
tkajinam | there was an attempt to fix stable/zed gate but it has been blocked by multiple problems there. Idk if the gate can be fully restored before we move zed to unmaintained | 06:34 |
frickler | tkajinam: yes, I plan to do that for those patches that have unrelated CI failures | 06:37 |
tkajinam | ok | 06:37 |
tkajinam | I updated it to make srbac job non-voting but reverted it after I noticed that functional jobs are also broken... so the latest version only do tripleo job removal | 06:38 |
*** elodilles_pto is now known as elodilles | 07:17 | |
frickler | and done, 200+ branches deleted https://paste.opendev.org/show/brz3YtgscgJU8Eptqsyr/ | 08:04 |
*** haleyb_ is now known as haleyb | 15:27 | |
*** ykarel is now known as ykarel|away | 16:30 | |
opendevreview | Vladimir Kozhukalov proposed openstack/project-config master: Add openstack-helm-plugin git repository https://review.opendev.org/c/openstack/project-config/+/916007 | 17:07 |
gmann | frickler: thanks. I think fixing on master/supported branch is ok and those can easily backported to unmaintained branches by their maintainers. | 17:09 |
opendevreview | Vladimir Kozhukalov proposed openstack/project-config master: Add openstack-helm-plugin git repository https://review.opendev.org/c/openstack/project-config/+/916007 | 17:22 |
JayF | Do we still retire openstack/ repos for projects migrating out of OpenStack governance? Or do they keep their namespace? | 17:23 |
clarkb | my understanding of the current process is that openstack/foo gets retired in place then if someone else wants to resurrect it they may do so with a fork at bar/foo | 17:25 |
clarkb | they can simply revert the retirement commit and continue development from there | 17:25 |
fungi | JayF: the current policy is still as described in https://governance.openstack.org/tc/resolutions/20190711-mandatory-repository-retirement.html (with rationale included) | 17:26 |
JayF | Do we know if there are any of those "carryover" ones left? | 17:27 |
JayF | That are in openstack/ but not under openstack governance? | 17:27 |
JayF | context is I'm reviewing https://review.opendev.org/c/openstack/governance/+/915021/2/reference/charter.rst#223 | 17:27 |
gmann | I do not think we did cleanup of those that time we wrote resolution | 17:27 |
JayF | and it's basically "AC is anyone with commits in openstack/" | 17:27 |
JayF | and I'm concerned there are some stragglers | 17:27 |
gmann | If there are any, those might be a bug and moving them from openstack/ is solution | 17:28 |
clarkb | you shouldn't need to move anything out of openstack fi you retire it | 17:28 |
fungi | JayF: the main one to consider, which i mentioned to spotz when she was drafting it, is openstack/project-config (ostensibly vouched for by the openstack tact sig for now) | 17:28 |
clarkb | since no contributions will occur on retired repos | 17:28 |
gmann | basically anything in openstack/ namespace has to be official project/deliverables in OpenStack | 17:28 |
JayF | gmann: > Because this is a significant change in policy, it cannot easily be retroactively applied to old repositories which are no longer under OpenStack’s governance (but the damage this would mitigate for them is probably already done anyway). | 17:29 |
JayF | gmann: from the linked resolution from 2019 above | 17:29 |
JayF | That indicates to me there are valid reasons for a non-openstack-project repo to be in openstack/ and we don't really expect to proactively move them out | 17:29 |
fungi | JayF: anything that wasn't officially governed by an openstack project team, the openstack tc, or an openstack sig was removed from the openstack namespace prior to that resolution passintg | 17:29 |
JayF | OK, cool, thank you all for the context | 17:30 |
gmann | JayF: yes, we did all the migration that time. but if anything left or added in OpenStack/ namspace before governance change merge that can happen | 17:30 |
fungi | JayF: https://governance.openstack.org/tc/resolutions/20190322-namespace-unofficial-projects.html | 17:30 |
gmann | that was a lot of work that time and I do not think anything left. and resolution ^^ is policy to continue the same | 17:31 |
JayF | perfect, thanks \o/ | 17:31 |
gmann | JayF: in AC thing, if we want to be more careful then mentioning it "as a official governed repo by OpenStack governance" can be clear | 17:31 |
fungi | JayF: the other resolution related to that which was passed in the same proximate timeframe was https://governance.openstack.org/tc/resolutions/20200228-openstack-infra-split-to-opendev.html | 17:33 |
opendevreview | Vladimir Kozhukalov proposed openstack/project-config master: Add openstack-helm-plugin git repository https://review.opendev.org/c/openstack/project-config/+/916007 | 17:37 |
Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!