Tuesday, 2024-04-16

fricklergmann: 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 errors05:02
fricklerso 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
fricklerthat 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:open05:36
fricklerso I guess next up I can run some stable EOM branch cleanup05:45
tkajinamfrickler, 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 it06:34
tkajinamthere 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 unmaintained06:34
fricklertkajinam: yes, I plan to do that for those patches that have unrelated CI failures06:37
tkajinamok06:37
tkajinamI 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 removal06:38
*** elodilles_pto is now known as elodilles07:17
fricklerand done, 200+ branches deleted https://paste.opendev.org/show/brz3YtgscgJU8Eptqsyr/08:04
*** haleyb_ is now known as haleyb15:27
*** ykarel is now known as ykarel|away16:30
opendevreviewVladimir Kozhukalov proposed openstack/project-config master: Add openstack-helm-plugin git repository  https://review.opendev.org/c/openstack/project-config/+/91600717:07
gmannfrickler: thanks. I think fixing on master/supported branch is ok and those can easily backported to unmaintained branches by their maintainers.17:09
opendevreviewVladimir Kozhukalov proposed openstack/project-config master: Add openstack-helm-plugin git repository  https://review.opendev.org/c/openstack/project-config/+/91600717:22
JayFDo we still retire openstack/ repos for projects migrating out of OpenStack governance? Or do they keep their namespace?17:23
clarkbmy 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/foo17:25
clarkbthey can simply revert the retirement commit and continue development from there17:25
fungiJayF: the current policy is still as described in https://governance.openstack.org/tc/resolutions/20190711-mandatory-repository-retirement.html (with rationale included)17:26
JayFDo we know if there are any of those "carryover" ones left? 17:27
JayFThat are in openstack/ but not under openstack governance? 17:27
JayFcontext is I'm reviewing https://review.opendev.org/c/openstack/governance/+/915021/2/reference/charter.rst#22317:27
gmannI do not think we did cleanup of those that time we wrote resolution17:27
JayFand it's basically "AC is anyone with commits in openstack/" 17:27
JayFand I'm concerned there are some stragglers17:27
gmannIf there are any, those might be a bug and moving them from openstack/ is solution17:28
clarkbyou shouldn't need to move anything out of openstack fi you retire it17:28
fungiJayF: 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
clarkbsince no contributions will occur on retired repos17:28
gmannbasically anything in openstack/ namespace has to be official project/deliverables in OpenStack17:28
JayFgmann: > 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
JayFgmann: from the linked resolution from 2019 above17:29
JayFThat 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 out17:29
fungiJayF: 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 passintg17:29
JayFOK, cool, thank you all for the context17:30
gmannJayF: yes, we did all the migration that time. but if anything left or added in OpenStack/ namspace before governance change merge that can happen17:30
fungiJayF: https://governance.openstack.org/tc/resolutions/20190322-namespace-unofficial-projects.html17:30
gmannthat was a lot of work that time and I do not think anything left. and resolution ^^ is policy to continue the same17:31
JayFperfect, thanks \o/17:31
gmannJayF: in AC thing, if we want to be more careful then mentioning it "as a official governed repo by OpenStack governance" can be clear17:31
fungiJayF: 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.html17:33
opendevreviewVladimir Kozhukalov proposed openstack/project-config master: Add openstack-helm-plugin git repository  https://review.opendev.org/c/openstack/project-config/+/91600717:37

Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!