Tuesday, 2023-03-28

fricklernot sure where to best ask this, but how is the openstack/openstack repo maintained? I was crosschecking the xstatic-font-awesome retirement and see it still being listed as submodule there08:53
fricklerunrelated: the list of runtimes at the bottom of https://governance.openstack.org/tc/reference/project-testing-interface.html could also use better sorting10:07
*** gthiemon1e is now known as gthiemonge12:24
gmannfrickler:   openstack/openstack should be updated on those repo additional/removal12:49
fricklergmann: "should be" ... done by someone or by some job which might be broken?12:50
gmannfrickler: it was job but I need to check that12:52
fungiyeah, i poked around briefly trying to find the update job, but didn't turn up where it's defined12:57
fricklerI found https://opendev.org/openstack/openstack/src/branch/master/generate-gitmodules.py but no reference to that in codesearch13:02
knikollao/13:05
gmannbut does it remove things? I can see tempest-lib also there which was retired a year ago13:06
knikollagouthamr: IIRC, we don't usually record PTG sessions. But there have been some cases.13:07
fungigmann: frickler: i doubt it removes retired projects since they're still openstack project governed repositories, even if they're not expected to merge new changes very often (they're not entirely read-only, the tc still has access to alter them if necessary)13:08
fricklerfungi: xstatic-font-awesome no longer is in https://opendev.org/openstack/governance/raw/reference/projects.yaml and if I read https://opendev.org/openstack/openstack/src/branch/master/generate-gitmodules.py#L54 correctly that should be a "git rm"13:15
* frickler now tries to run that script locally with only echoing those commands13:16
frickleror maybe in some hours, actually cloning that repo doesn't seem to be fast13:17
gmannI do not think it should keep retired one as they are no longer 'component of openstack ', 'not tested by zuul'13:17
gmannI was wrong that it does remove things also which i feel it should13:18
fungifrickler: gmann: a git log of the .gitmodules file indicates it was last updated manually with https://review.opendev.org/73601213:19
fungithat could be why we're not finding any automation... there isn't any?13:19
frickleroh, yes, if that has been a manual ajaeger-task before, that would explain it13:20
fungimaybe hberaud remembers reviewing those up to a few years ago13:20
fricklerrunning manually lists roughly 50 additions and 20 removals pending13:21
gmannah, right13:21
fungiwe could probably create a proposal job triggered from merges to governance that alter relevant files (maybe just projects.yaml)13:21
fricklerhmm, I tried to create an update manually, but even "git review -s" fails with "Description: fatal: Upload denied for project 'openstack/openstack'"13:56
fungii think there's an acl limiting who can propose changes13:58
gmannyeah https://github.com/openstack/project-config/blob/master/gerrit/acls/openstack/openstack.config13:58
fricklerbut why does that even block -s?13:59
gmannwe can add TC group too as it is repo under TC to maintain?13:59
fricklerfrom the acl that could be a release team task, guess I'll ask over there first14:01
fungifrickler: git review -s performs a test push to confirm you have sufficient rights to propose changes14:04
fungiso i guess it's working as intended, since it errored for that reason14:04
frickleroh, I wasn't aware of that. but likely makes sense to fail early, rather than after having done all the work to prepare a patch14:06
fungithe most common place new users run into it is when they haven't agreed to the openinfra icla and try to push changes for a cla-enforced project14:11
fungiso it helps that the first recommended step in starting to work on a change in a new repo is git review -s, since it catches that straight away14:16
clarkbdo we know if anyone is getting value out of that repo?14:22
clarkbthe original idea behind it was to have a linear historical record of changes landing across openstack projects14:22
clarkbin particular this was envisioned as being useful for continuous deployment systems needing to bisect issues.14:23
knikollainteresting, i didn't know it existed14:26
fungiclarkb: apparently the cncf "landscape" gets value out of the github replica of it, since cncf/lf assumes open source projects are all monorepos and exist on github14:32
fungiso to have openstack be included in the landscape it had to be added as a single git repository there14:33
PagliaccisCloud#kata now discussing runtime-rs14:34
PagliaccisCloudYikes wrong channel - sorry!14:34
fungiPagliaccisCloud: you want #openinfra-events14:34
clarkbfungi: interesting. I'm pretty sure openstack isn't unique in having more than one repo. I wonder what others do about that14:35
fungiin some cases they just pick one repository, in some cases they're listed as distinct projects14:37
opendevreviewVishal Manchanda proposed openstack/governance master: Add xstatic-angular-fileupload as Horizon team deliverables  https://review.opendev.org/c/openstack/governance/+/87384517:25
opendevreviewJames Slagle proposed openstack/governance master: TripleO: switch to distributed project leadership  https://review.opendev.org/c/openstack/governance/+/87879921:41

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