[all][election] Check your voting eligibility for the OpenStack PTL & TC elections
Hello Stackers, Election season is here, and we want to ensure every voice that helps build OpenStack is heard. I would like you to take a moment to verify your "Active Contributor" [1] and OpenInfra Foundation membership status so you don't miss your chance to vote. To receive a ballot for the OpenStack TC elections, you must be a contributor to OpenStack repositories _and_ hold the status of "OIF Individual Member." To receive a ballot for a PTL election, you must have contributed to any of a project team's repositories _and_ hold the status of "OIF Individual Member." Check your membership level: ======================== Log in to your profile at https://openinfra.org/a/profile. Even if you’ve been a member for years, the OpenInfra Foundation (OIF) has a policy that automatically downgrades memberships to "OIF Community Member" if you haven't voted in recent Governing Board elections [2]. Upon logging in, if you see that you are an "OIF Community Member," you can restore your "OIF Individual Member" status on that profile page. Get recognized as an "Active Contributor": ================================ While our policy traditionally focuses on contributors to OpenStack's git repositories, we know that impactful work happens far beyond just code and documentation. We definitely value the "intangible" work that keeps this community running. If you haven’t contributed code or documentation to a repository during the 2025.2–2026.1 timeframe (March 14, 2025 – February 18, 2026), you can still vote! Please reach out to the PTL or DPL liaison of the project team you’ve supported and request to be added as an "Extra AC" (Extra Active Contributor) today [3]. The deadline to do this is February 13, 2026. If you run into issues or have questions about your eligibility, the TC would be happy to help. Simply reply to this thread, or chime in on OFTC's #openstack-tc IRC channel. Thanks, Goutham Pacha Ravi (gouthamr) [1] "Active Contributor": https://governance.openstack.org/tc/reference/charter.html#voters-for-tc-sea... [2] OIF membership page: https://openinfra.org/join/individual/ [3] Extra AC deadline: https://releases.openstack.org/gazpacho/schedule.html#g-extra-acs
The OpenInfra login seems to be asking for a rather wild number of permissions: " Allow access to your profile info. Allow access to your email info. Allow access to your address info. Use Openid Connect Protocol Allow to emit refresh tokens (offline access without user presence). Read our own member profile and personal information Allow write my speaker profile data Read access to my speaker profile Allow to read organization data Allow to write organization data Get My Member Info Allow to write my member information Add events to your schedule Remove events from your schedule Create Shareable schedule Delete shareable schedule Allow access to write your Profile. Allow to nominate candidates Allows to write my candidate profile " Isn't that excessive? Best wishes - Nell On Thu, Feb 5, 2026 at 10:21 PM Goutham Pacha Ravi <gouthampravi@gmail.com> wrote:
Hello Stackers,
Election season is here, and we want to ensure every voice that helps build OpenStack is heard. I would like you to take a moment to verify your "Active Contributor" [1] and OpenInfra Foundation membership status so you don't miss your chance to vote.
To receive a ballot for the OpenStack TC elections, you must be a contributor to OpenStack repositories _and_ hold the status of "OIF Individual Member." To receive a ballot for a PTL election, you must have contributed to any of a project team's repositories _and_ hold the status of "OIF Individual Member."
Check your membership level: ========================
Log in to your profile at https://openinfra.org/a/profile.
Even if you’ve been a member for years, the OpenInfra Foundation (OIF) has a policy that automatically downgrades memberships to "OIF Community Member" if you haven't voted in recent Governing Board elections [2]. Upon logging in, if you see that you are an "OIF Community Member," you can restore your "OIF Individual Member" status on that profile page.
Get recognized as an "Active Contributor": ================================
While our policy traditionally focuses on contributors to OpenStack's git repositories, we know that impactful work happens far beyond just code and documentation. We definitely value the "intangible" work that keeps this community running.
If you haven’t contributed code or documentation to a repository during the 2025.2–2026.1 timeframe (March 14, 2025 – February 18, 2026), you can still vote! Please reach out to the PTL or DPL liaison of the project team you’ve supported and request to be added as an "Extra AC" (Extra Active Contributor) today [3]. The deadline to do this is February 13, 2026.
If you run into issues or have questions about your eligibility, the TC would be happy to help. Simply reply to this thread, or chime in on OFTC's #openstack-tc IRC channel.
Thanks, Goutham Pacha Ravi (gouthamr)
[1] "Active Contributor":
https://governance.openstack.org/tc/reference/charter.html#voters-for-tc-sea... [2] OIF membership page: https://openinfra.org/join/individual/ [3] Extra AC deadline: https://releases.openstack.org/gazpacho/schedule.html#g-extra-acs
On 2026-02-06 13:10:21 +0000 (+0000), Nell Jerram wrote:
The OpenInfra login seems to be asking for a rather wild number of permissions: [...]
I've brought this up in the past with the contracting firm that manages those systems, but in essence that's the OpenInfra Foundation web site asking for permission to read the information it stores for you in the OpenInfra Foundation authentication and identity system. There are apparently some technical challenges with silencing that, but I'll bring it up with them again and see if they have any new ideas to make that less scary. -- Jeremy Stanley
In my opinion it does need to be fixed urgently. It's bad practice to encourage anyone to click through this kind of rubbish. I must admit, I'm also not clear who is the SSO provider, and who is the consumer. All the orgs involved seem to have the same "openinfra" name. Best wishes - Nell On Fri, Feb 6, 2026 at 4:07 PM Jeremy Stanley <fungi@yuggoth.org> wrote:
On 2026-02-06 13:10:21 +0000 (+0000), Nell Jerram wrote:
The OpenInfra login seems to be asking for a rather wild number of permissions: [...]
I've brought this up in the past with the contracting firm that manages those systems, but in essence that's the OpenInfra Foundation web site asking for permission to read the information it stores for you in the OpenInfra Foundation authentication and identity system. There are apparently some technical challenges with silencing that, but I'll bring it up with them again and see if they have any new ideas to make that less scary. -- Jeremy Stanley
On 2026-02-06 19:32:31 +0000 (+0000), Nell Jerram wrote:
In my opinion it does need to be fixed urgently. It's bad practice to encourage anyone to click through this kind of rubbish. [...]
I'm told it's that way in order to ensure compliance with the GDPR, and that the designers decided always notifying and asking a user's permission before doing anything with their personal data was the best way to achieve that. There's always room for improvement, of course, and it could at a minimum benefit from some additional context, in particular some way to indicate that you're giving the OpenInfra Foundation permission to access data you've already given to the OpenInfra Foundation and to update that information when you ask it to apply changes. -- Jeremy Stanley
Hey Nell it's a good question and fair observation. The consent screen language could definitely be clearer. I do want to explain why those scopes exist, because the underlying architecture is actually sound. What you're looking at is the OpenInfra Foundation's OpenID Connect identity provider. It's not just the login for one thing — it's the single identity layer that powers everything in the OpenInfra ecosystem. That same login handles: Foundation membership and governance — which is what you're doing (elections, voting eligibility, candidate nominations) Event infrastructure — registration, schedules, speaker submissions via the CFP, shareable schedules for summits and PTGs Project and foundation websites — OpenStack, StarlingX, Kata Containers, the OpenInfra site itself Speaker and sponsor management — profile data, organization affiliations So when you see scopes like "nominate candidates" and "write candidate profile," those are the election and governance functions you'd expect. The schedule and speaker profile scopes are there because the same identity carries across into summit participation. The organization read/write handles your company affiliation for membership and voting eligibility purposes. The reason the consent screen feels excessive is that it's presenting the full capability set of the platform upfront — foundation governance, event ops, community participation — even though you may only be here to manage your membership and vote. Incremental consent (requesting scopes only when you actually use a feature) may seem like a better UX pattern up front, but as you navigated the site if you decided to do other things you'd have to incrementally grant consent which would be more complicated to code and potentially create friction in the end experience. At the end of the day, what you're seeing is transparency, not overreach. Most platforms access equivalent data without itemizing it. The auth flow itself is PKCE-based and standards-compliant per RFC 7636: https://datatracker.ietf.org/doc/html/rfc7636 And importantly — all of this is open source. The IDP, the API, and the foundation website are all available for full audit, and PRs are welcome if anyone feels inclined to suggest an improvement for the consent experience: IDP: https://github.com/OpenStackweb/openstackid Summit API: https://github.com/OpenStackweb/summit-api Foundation Website: https://github.com/OpenStackweb/osf-website Thanks for paying attention and bringing this up :). I hope this was a helpful explanation.
participants (5)
-
Goutham Pacha Ravi
-
Jay Faulkner
-
Jeremy Stanley
-
jpmaxman＠tipit.net
-
Nell Jerram