Thursday, 2026-02-05

gouthamryeah we’d need to discuss with the community, if it makes sense we could make our ACs our electorate.. and not worry about the foundation membership level00:17
gouthamrthat’d also be a TC charter change00:17
fricklerI'm also pretty sure a lot of people missed to vote this time because of the mess with the broken ballot generation (like I did). I wonder whether it would be worth be make an exception and not count this year's board election towards the activity measure07:46
opendevreviewMerged openstack/election master: Add nomination directories for Oslo and Requirements  https://review.opendev.org/c/openstack/election/+/97571813:47
fungiclarkb: gouthamr: my understanding it that, since the openstack project (via their elected representatives on the tc) held a privileged position in the original openstack foundation bylaws, in particular the ability to propose and veto bylaws changes, it was prudent to have the people electing those representatives registered and subject to a legal agreement14:27
fungii can ask jbryce whether he remembers more specifically the reason active technical contributors (as the bylaws called them) were designated as a strict subset of the foundation individual members14:29
fungiat this point, probably the only benefit to requiring the voting constituency for the tc to be foundation members is that there's some oversight and legal recourse (in theory) in the event anyone tries to compromise the election process14:31
fungibut as i'm not a lawyer, i really don't know14:31
fungii do know we've discussed the possibility to do away with that requirement in the past, but the tc never reached consensus to change it so the status quo has persisted as tradition14:32
fungifrickler: in the past, there's also been outreach before downgrading memberships, which gave the opportunity to avoid being downgraded if you had missed elections but still intended to keep your membership14:48
fungivoting in an election is merely a proxy for determining interest, if someone has voted in a recent election we can automatically assume they don't want their membership downgraded. if they haven't voted in a while, then they get asked and downgraded if they don't perform the indicated action to refresh their member activity14:50
frickleroh, if there's a feedback process instead of an automated action, that sounds like a fine solution, too15:03
fungii don't know for sure that's the process they'll use next time, but it's reasonable to assume it isn't changing15:05
opendevreviewJuan Larriba proposed openstack/election master: Adding Juan Larriba candidacy for Telemetry  https://review.opendev.org/c/openstack/election/+/97581015:22
opendevreviewIan Y. Choi proposed openstack/election master: Fix render election schedule to releases  https://review.opendev.org/c/openstack/election/+/97582117:00
fungifrickler: gouthamr: i confirmed with wes that the notifications to users slated for membership downgrade are expected to continue, and also he's working on shoring up the language on the join page/form18:45
fungithanks for the input!18:46
gouthamryep, and on the board ballot email too, please :) 18:46
gouthamrthere's a chance folks would visit the membership page rarely and forget after they've signed up18:46
gouthamrthanks fungi 18:47
fungii mentioned the board ballots/election notices too, i don't know if they keep a reusable template for that somewhere18:48
gouthamrack18:49
*** croeland1 is now known as croelandt20:05
opendevreviewVladimir Kozhukalov proposed openstack/election master: Add Vladimir Kozhukalov candidacy for Openstack-Helm 2026.2 PTL  https://review.opendev.org/c/openstack/election/+/97585820:42
fungigouthamr: wes has updated the wording at https://openinfra.org/join/individual now based on your feedback, thanks!21:51
gouthamrgreat, thank you for the quick action on this fungi 21:52
fungiall i did was pass the suggestion along, but you're welcome of course21:53
gouthamr:P helped me write the reminder i wanted to craft for the ML22:20
gouthamrhttps://lists.openstack.org/archives/list/openstack-discuss@lists.openstack.org/thread/4FJCB24CL3RPO73WKGNLXX3PE2BFYJAQ/22:20
fungiawesome23:12
JayFI think there would be interesting opportunities around inviting classes of folks generally as extra-ACs. If someone is a maintainer of gophercloud, for instance, I'd consider them a contributor to the openstack community.23:23
fungithat was traditionally done for translators23:25
gouthamrinteresting indeed. i was thinking of how we struggle to recognize "non-coders" of all sorts when i wrote that.. like translators ^, operators, folks running our SIGs, reporting bugs, engaging in design discussions but not committing anything - all important stakeholders.. 23:26
JayFI mean, I'm also thinking coders that are outside the community, but are strongly impacted by our technical decisions23:34
gouthamrtrue23:34
JayFGophercloud / openstack-exporter came to mind for me, mainly because I have a part-timer on my team who is mainly dedicated to those23:34
JayFbut also things like metal323:34
JayFand in practice; most of these folks already crossover as ACs, but I think it'd be a nice gesture to extend the grace overall23:35
JayFAdmittedly I'm probably more open to this as Ironic has some of the strongest ties to CNCF stuff (we have support at multiple layers for integrating with their ecosystem, including OCI image support and metal3)23:36
gouthamrtotally, it's the discretion of PTLs/DPLs (or really the project team) to nominate anyone.. 23:36
gouthamrJayF: if you have names, lead the way! :) 23:37
JayFI've already got an email out to the rest of the Ironic DPL about my specific employee, but he shouldn't be special just because I pay attention23:42

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