| opendevreview | Sylvain Bauza proposed openstack/governance master: Add agentic-workflows to TaCT SIG https://review.opendev.org/c/openstack/governance/+/984958 | 15:19 |
|---|---|---|
| bauzas | fungi: thanks for offering the TaCT SIG to host the agentic-workflows repo :) | 15:52 |
| fungi | it seemed like a fine place to coordinate that effort | 15:53 |
| bauzas | one chicken-and-egg concern I have : should the governance patch depend on the project-config (and if so we could start having an initial git repo before the TC chime in) or do we want to hold on the TC approval before we start pushing into that repo ? | 16:22 |
| mnasiadka | In my mind maybe the governance patch should be first, but I think we lack guidance on that in any documentation - so given the TaCT SIG chair agrees, we should be fine. | 16:24 |
| sean-k-mooney | mnasiadka: i think if you follow https://docs.opendev.org/opendev/infra-manual/latest/creators.html#give-opendev-exclusive-permission-to-publish-releases top to bottom the governace change happens after the repo creation | 16:26 |
| sean-k-mooney | https://docs.opendev.org/opendev/infra-manual/latest/creators.html#adding-the-project-to-the-ci-system | 16:26 |
| sean-k-mooney | is what i ment to link | 16:26 |
| fungi | yes, that order | 16:27 |
| sean-k-mooney | although i think we usually wait for both patches to be up before merging | 16:27 |
| fungi | normally the repositories have to be created before we merge a governance change referring to them, but like to have confirmation from the stakeholders on both patches before any merge | 16:27 |
| fungi | the esoteric reason for this is that if you have project creation straddling an election, it can cause problems for the election officials trying to check for merged commits in a deliverable repository that doesn't exist yet | 16:28 |
| fungi | this used to happen semi-regularly | 16:29 |
| fungi | it only became a catch-22 policy situation in 2019 when "officialness" was required to add a repository to the openstack/ git namespace, at which point we started trying to get them proposed closer together timewise and having tentative stakeholder approval on the addition | 16:31 |
| mnasiadka | Well, I didn’t find it - but good to know (although both are related to each other - I assume we shouldn’t have a repo that is not tied to project or sig in the openstack namespace) | 16:31 |
| fungi | logically there's a circular dependency between the two, functionally we merge the project-config change before the governance change to avoid race conditions with processes which expect repos listed in governance to actually exist at any point in time | 16:32 |
| fungi | mnasiadka: it happened with the approval of this resolution... https://governance.openstack.org/tc/resolutions/20190322-namespace-unofficial-projects.html | 16:33 |
| sean-k-mooney | mnasiadka: that why we use the needed-by and depens-on in the commit as well | 16:36 |
| sean-k-mooney | we are ment to upload both then update update them to point at each other | 16:36 |
| sean-k-mooney | and when both are approved we merge them at about the same tiem | 16:36 |
| sean-k-mooney | but ya its a bit of overhead but it also does nto happen that often | 16:37 |
| bauzas | I'm already preparing the initial commit | 16:42 |
| fungi | the needed-by isn't strictly necessary, as one of the people reviewing those anyway i'm usually fine with just a simple review comment that says "the corresponding governance change can be found here..." | 16:42 |
| bauzas | so once we merge the project-config, I'll git init and push | 16:42 |
| bauzas | fungi: I added a comment to the project-config change for telling about the gov one | 16:43 |
| fungi | yep, that worked just fine, and is how i spotted it | 16:43 |
| fungi | no need to push yet another patchset just to add a needed-by trailer to the commit message, losing existing votes and and triggering check jobs all ovr again | 16:44 |
| bauzas | yup, will just wait for the merge | 16:49 |
Generated by irclog2html.py 4.1.0 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!