| frickler | fungi: thx for the update, some more things I note there: the last sentence still mentions OpenStackID, should be OpenInfraID? also the affiliation section on the profile page says "paid to work on OpenStack", that likely also should be generalized? | 09:36 |
|---|---|---|
| opendevreview | Merged openstack/election master: kolla: Add Michal Nasiadka PTL candidacy https://review.opendev.org/c/openstack/election/+/974902 | 13:28 |
| opendevreview | Merged openstack/election master: TC: Add Michal Nasiadka candidacy https://review.opendev.org/c/openstack/election/+/974904 | 13:30 |
| opendevreview | Merged openstack/election master: adding sean mooney's ptl candidacy for cyborg https://review.opendev.org/c/openstack/election/+/975690 | 13:30 |
| opendevreview | Merged openstack/election master: magnum: Add Michal Nasiadka candidacy https://review.opendev.org/c/openstack/election/+/975424 | 13:30 |
| opendevreview | Merged openstack/election master: Add Ivan Anfimov candidacy for Horizon PTL https://review.opendev.org/c/openstack/election/+/975621 | 13:30 |
| opendevreview | Merged openstack/election master: Adding Juan Larriba candidacy for Telemetry https://review.opendev.org/c/openstack/election/+/975810 | 13:30 |
| opendevreview | Merged openstack/election master: Add Hao Wang candidacy for Zaqar 2026.2 PTL https://review.opendev.org/c/openstack/election/+/975701 | 13:31 |
| fungi | frickler: great points, i'll pass those along | 14:12 |
| fungi | JayF: out of curiosity, do all ironic devs get to vote for the metal3 project leadership too? since ironic is integral to their project it would only make sense | 15:00 |
| JayF | I think that's actually not a good comparison; Metal3 decisions don't directly impact Ironic | 15:33 |
| JayF | whereas they are completely reliant on us for implementation of features | 15:33 |
| JayF | (for purposes of this discussion I'm convieniently ignoring that 99.9999% of the time the contributor on both sides is the same person) | 15:33 |
| fungi | ah, right, so it would be more that metal3 contributors should get to vote for openstack leadership and not the other way around | 15:55 |
| fungi | i guess the anaolgy i'm looking for is whether nova developers should get to vote for libvirt leaders then | 15:55 |
| fungi | since libvirt decisions potentially impact nova work | 15:56 |
| JayF | I think ... should is a strong word | 16:01 |
| JayF | My proposed idea is more along the lines of inviting people into the tent | 16:01 |
| JayF | I don't think we have any ethical/moral responsibility to do so; it's just nice to do. | 16:02 |
| fungi | got it | 16:09 |
| clarkb | fwiw I think that the existing invitation of contributing -> having a vote seems reasonable. That said I agree that we probably don't capture all of the contributors doing things like translations very well. It isn't like external groups can't provide feedback through issues, the mailing list, specs and so on. | 16:11 |
| clarkb | and some of those activities can lead to formal recognition that enables voting | 16:12 |
| -opendevstatus- NOTICE: Gerrit on review.opendev.org will experience a short outage while we upgrade it to 3.11.8 | 17:50 | |
| JayF | it's a really, really good point that if we orient "AC" correctly, we'll catch the crossovers already engaging in the community | 17:56 |
| JayF | that's a nice perspective | 17:56 |
| gmaan | on same line, all operators/end users comes into my mind which are impacted by leadership decision directly or indirectly or maybe openinfra membership companies? | 18:02 |
| fungi | that was the argument for renaming atc to ac after the tc absorbed the uc, so ac was in theory supposed to be the union of atc and auc folks | 18:04 |
| fungi | but in practice, none of the traditionally auc constituents got folded into any automated ac identification process, on the expectation that formerly auc voters would get added via the extra ac mechanism | 18:05 |
| gmaan | exactly. its it still technical election and TC is a leadership who does not only control governance part but take technical decision also. I feel including adjacent/dependent OSS/lib in election seems little out of scope for voting. yes, anyone contributing via ML, feedback etc are valid one | 18:07 |
| gmaan | that is what TC charter covers https://governance.openstack.org/tc/reference/charter.html#voters-for-tc-seats-ac | 18:07 |
| gmaan | one good example is 'Bug triaging not tracked in Gerrit' | 18:08 |
| gmaan | I think it projects side we are getting less proposal for exytra-acs for people doing all these less visible contribution. If they propose then TC charter covers it to include them as extra-acs | 18:09 |
| gouthamr | need to remind PTLs/DPLs unfortunately - this became something of tribal knowledge unfortunately | 18:33 |
| gouthamr | also, i don't like that we're maintaining the ACs in projects.yaml .. maybe if it were closer to their code base, it'd make sense - it'd be hard to pull the data from all over the place, but, the TC needing to approve ACs seems a bit bureaucratic | 18:35 |
| fungi | changing that will definitely need a charter revision though | 18:37 |
| gouthamr | yes | 18:37 |
| fungi | (aside from new tracking automation/workflows obviously) | 18:37 |
| gouthamr | okay this brainstorming is helping me, keep it coming.. i want to revive/strengthen formal recognition within our community for invisible/unsung work... time and again we've shown intention to do that, but, we are extremely busy and have processes that we keep up with that kinda relegates this to an afterthought.. being able to vote in elections is just one part of it | 18:40 |
| gouthamr | sean-k-mooney: fungi: https://answers.launchpad.net/launchpad/+question/823538 was actioned by LP admins | 18:56 |
| gouthamr | you may have already seen notifications | 18:56 |
| * gouthamr probably slowed this down with the typo in the team name | 18:56 | |
| gouthamr | https://launchpad.net/~cyborg-team is owned by openstack-admins for correctness as we discussed | 18:57 |
| fungi | thanks! | 18:58 |
| sean-k-mooney | gouthamr: yep i was looking at the emails thansk for taking care of that and yes cyborg-team is teh name of the team that is set as teh drivers and mainainer of the lauchpad project rather then "cybrog-drivers" as the team name | 19:10 |
| sean-k-mooney | so they updated the correct one. | 19:10 |
| gouthamr | ack, good stuff | 19:10 |
| sean-k-mooney | one thing we need to confirm is that openstack-administors shoudl have the amdinistrato status https://launchpad.net/~cyborg-team/+members | 19:11 |
| sean-k-mooney | or at least that as an owner it can grant that when needed | 19:11 |
| gouthamr | yeah, that's how it works with the other teams, openstack-admin doesn't need to be in the team, just owning it allows it to add/boot anyone and manage things | 19:13 |
| fungi | correct | 19:33 |
| fungi | technically speaking, if e.g. the nova ptl asks me to make changes to the nova project on lp, i use the openstack-admins ownership of the drivers team to add myself to the drivers team temporarily, which then gives me access to make changes to things the drivers team owns | 19:35 |
| fungi | owning a team doesn't automatically and transitively grant control over things the team owns | 19:35 |
| gouthamr | ah, i didn't know that part about the sausage | 19:36 |
| fungi | it's more of an implementation detail. from a practical standpoint it's mostly irrelevant | 19:37 |
| spotz[m] | Ok I think I have caught up on this channel at least at a high level:) | 21:56 |
| fungi | that makes one of us | 21:56 |
| spotz[m] | I said high level:) | 21:57 |
| *** gmaan is now known as gmaan_afk | 22:46 | |
Generated by irclog2html.py 4.0.0 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!