| *** ralonsoh_ is now known as ralonsoh | 08:08 | |
| elodilles | hi infra team o/ kolla team needs some help for this patch: https://review.opendev.org/c/openstack/project-config/+/908321 | 13:45 |
|---|---|---|
| elodilles | if i understand correctly then the kayobe- and kolla-unmaintained-core can be created by the infra team, right? | 13:46 |
| elodilles | also, the team is OK to add openstack-unmaintained-core as member to these team | 13:46 |
| elodilles | (or if that is better, then the above patch can also contain the group with the +2/+W labels. i don't know which is better) | 13:47 |
| elodilles | mnasiadka: ^^^ | 13:48 |
| fungi | elodilles: the groups will be created automatically when those acl additions merge, they'll just be empty by default. we usually add the ptl for the project as the initial member and then let them set the group up however they like | 13:49 |
| mnasiadka | elodilles: that means let's merge that and I'll bug fungi to add me to that group (so I can add openstack-unmaintained-core) | 13:50 |
| fungi | also, to be clear, people interested in helping with unmaintained branches for at least one project are strongly encouraged to just join the central openstack-unmaintained-core group instead | 13:51 |
| fungi | which then doesn't require any acl changes and allows them to also help with unmaintained branches for other projects if they prefer | 13:51 |
| fungi | but if there is a reason these individuals can't join openstack-unmaintained-core, or that the project doesn't want to grant everyone in openstack-unmaintained-core control of their unmaintained/.* branches, acl changes such as those proposed are the primary workaround | 13:52 |
| mnasiadka | I think for the time being we'd like to maintain the unmaintained/yoga branch with the current kayobe/kolla core groups - I'm OK with openstack-unmaintained-core having core access to those projects if required/desired | 13:54 |
| mnasiadka | fungi: but if there's a streamlined process how to apply for openstack-unmaintained-core membership - and no one is going to be unhappy that I'm reviewing only kolla/kayobe - I'm fine with that ;) | 13:58 |
| fungi | elodilles: and more of a discussion for the #openstack-tc channel, but https://governance.openstack.org/tc/resolutions/20231114-amend-unmaintained-status.html says that projects aren't required to grant control of those branches to the central openstack-unmaintained-core group. says clearly in a couple of places: "this group may override the powers of the openstack-unmaintained-core | 13:58 |
| fungi | group" and "It is possible for individual project teams to override the OpenStack-wide group for that project’s Unmaintained branches." | 13:59 |
| fungi | oh, never mind, i see in a later review comment you backed off from that assertion | 14:00 |
| elodilles | fungi: hmmm. e.g. ironic team had concerns about adding openstack-unmaintained-core for their unmaintained branches but since only tonyb and me are there (we are stable-maint-core's anyway, so we understand the stable policy rules). if we add everyone to openstack-unmaintained-core then that opens up core reviewing options for *everyone*. | 14:01 |
| fungi | yes, that was the tc's goal with this, as i understood it. try to break down the silo walls that unfortunately hamstring openstack in too many places, and just have one big happy group where anyone can approve unmaintained/.* branch changes on any project they feel competent and comfortable to do so | 14:03 |
| elodilles | i accept that :) hope teams understand that too then ;) | 14:04 |
| fungi | but for projects which care strongly about their unmaintained branches and have trouble trusting outside their own teams, there's still the escape hatch of overriding the central inherited acl with project-specific teams | 14:04 |
| fungi | so the openstack-wide approach isn't forced on anyone, merely strongly encouraged | 14:05 |
| elodilles | in that case maybe ironic teams wants to reconsider the addition of openstack-unmaintained core to their unmaintained group i guess | 14:05 |
| elodilles | JayF: ^^^ | 14:05 |
| fungi | i have a feeling JayF was deeply involved in these discussions within the tc, so presumably has a firm grasp of the intent | 14:06 |
| fungi | but it can't hurt to double-check | 14:06 |
| elodilles | +1 | 14:07 |
| mnasiadka | Ok then, I'll consult again the Kolla community which one do we want, but surely we want to regain core access for regular branches cores | 14:09 |
| fungi | the way openstack-unmaintained-core is set up now, any member of that group can add anyone they want, and also the tc can add anyone they want (mostly as a failsafe in case all members of that group become inactive), but probably the people in openstack-unmaintained-core want to come up with some sort of (at least informal) policy like "must be a current/former member of a core team for | 14:11 |
| fungi | at least one project in openstack" or whatever | 14:11 |
| fungi | or maybe if you're a current or former core reviewer for at least one project with unmaintained branches, you can be added without need for discussion, but still leave open the possibility for people to join who aren't and haven't been project cores if they're sufficiently motivated and involved elsewhere | 14:13 |
| mnasiadka | Well, there are projects that follow stable policy rules, and projects that don't really - and deployment projects sort of are a bit different than regular Python based projects - so I'm thinking that process needs to be still communicated/defined/etc | 14:13 |
| fungi | the tc has (so far) left it up to that group to steer its own ship | 14:13 |
| fungi | but yes i agree that choosing some process and communicating it would be good to do very soon | 14:14 |
| mnasiadka | elodilles: can we merge that patch so we regain control over the branches we still use (but are unmaintained/*) in a shorter timeframe than weeks? ;-) | 14:14 |
| fungi | if the group only has two members, it won't be very effective at its intended purpose | 14:14 |
| elodilles | mnasiadka: yepp, that's completely OK to me | 14:17 |
| opendevreview | Merged openstack/project-config master: Implement kolla/kayobe-unmaintained-core groups https://review.opendev.org/c/openstack/project-config/+/908321 | 14:34 |
| elodilles | thx fungi o/ | 14:39 |
| mnasiadka | fungi: if you could add me to kolla-unmaintained-core and kayobe-unmaintained-core in some spare time - I would be grateful | 14:41 |
| mnasiadka | Ah, done, thanks :) | 14:42 |
| fungi | i was watching for the e-mail notification that the deploy completed | 14:43 |
| * fungi is event-driven | 14:43 | |
| *** jph3 is now known as jph | 15:06 | |
Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!