| opendevreview | OpenStack Proposal Bot proposed openstack/contributor-guide master: Imported Translations from Zanata https://review.opendev.org/c/openstack/contributor-guide/+/954398 | 03:00 |
|---|---|---|
| opendevreview | Merged openstack/election master: Update TC liaison for the 2026.1 election https://review.opendev.org/c/openstack/election/+/954302 | 03:16 |
| opendevreview | OpenStack Proposal Bot proposed openstack/openstack-manuals master: Imported Translations from Zanata https://review.opendev.org/c/openstack/openstack-manuals/+/947180 | 03:48 |
| opendevreview | Dmitriy Rabotyagov proposed openstack/training-guides master: Bump minimum tox version to 4.0 https://review.opendev.org/c/openstack/training-guides/+/954432 | 07:25 |
| frickler | tc-members: forgot to mention yesterday, stephenfin proposed to move the service-types-authority repo to SDK deliverables https://review.opendev.org/c/openstack/governance/+/953548 which I don't think is a good idea, but feedback from others would be interesting | 07:51 |
| frickler | regarding the membership issue, I think doing multiple status notices that get sent to all openstacky IRC channels would be appropriate. like one at 15 UTC and one at 07 UTC to try and reach a maximum of people while they are online. and repeat in a week before the deadline ends | 08:09 |
| frickler | fungi: another question around OIF membership: when will https://openinfra.org/a/community/members be switched? currently it still seems to show the old membership? | 09:48 |
| frickler | also, will all "date joined" data be reset? | 09:48 |
| spotz[m] | frickler: While I did suggest it, and do think we should do it, I fair even staggering the times we won't reach everyone due to not everyone being on IRC or Matrix | 12:16 |
| spotz[m] | s/fair/fear/ | 12:16 |
| fungi | frickler: can you elaborate on what you're seeing at https://openinfra.org/a/community/members vs what you expect to see? are you asking when any un-renewed individual memberships will be downgraded to non-member status? | 12:41 |
| fungi | just making sure i frame the question accurately to the folks driving that | 12:41 |
| frickler | fungi: maybe I'm a bit confused about "becoming a new member" vs. "renewing membership". if I'm currently a member and renew my membership not now but say in 3 months, will that still be the same membership that I've had for almost 10 years? if not, when will current memberships be terminated and when will that be reflected in the database? | 13:01 |
| frickler | if the membership continues regardless, then why will voting in 180 days be affected, if my effictive membership hasn't changed for 10 vears? | 13:01 |
| frickler | related question: is there a way to see whether some other member has renewed their membership or not? or is that information not meant to be public? | 13:03 |
| fungi | frickler: my understanding is that it's all the same database, but explicitly renewing makes you a project individual member for the openinfra directed fund at lf effectively replacing your individual membership with the openinfra foundation that's being dissolved. from an implementation standpoint i expect they're just going to downgrade everyone who doesn't renew to non-member | 13:03 |
| fungi | status. i'll pass along your questions though | 13:04 |
| fungi | but to be clear, you've been a member for 10 years in an organization that legally no longer exists | 13:04 |
| fungi | so technically you're becomming a member in a new organization when using that renew option | 13:05 |
| fungi | i think they're just using the renew timestamps to work out who's got a valid membership going forward so they know which ones to downgrade to non-members in the database | 13:06 |
| frickler | so then the term "renew" is wrong and one should talk about new memberships. and also should start a new database and not continue the existing one | 13:06 |
| fungi | i think the database backend is an implementation detail, as long as they can work out which memberships are current and which aren't | 13:06 |
| fungi | probably they didn't have the time nor budget to stand up an entire separate system for this | 13:07 |
| fungi | anyway, i'll try to get answers to those questions | 13:07 |
| frickler | the thing is, if the membership database still says "member since 2015", then the "OIF Individual Members are eligible to vote in an OIF Individual Member Election only if the date of such vote falls at least 180 days after the effective date that such an individual became an OIF Individual Member according to the OIF Individual Member Registry." condition will still hold, regardless of when the | 13:08 |
| frickler | renewal took place | 13:09 |
| fungi | yes, i expect those will be reset but don't know when | 13:09 |
| gmaan | frickler: re: service-types-authority I think you have valid concern. I will comment in gerrit. | 15:19 |
| gmaan | replied, one way to solve is to add sdk team or interested members in the service-types-authority core list so that it would not rely on TC only. | 15:47 |
| gmaan | though current group is also needs to be cleaned up https://review.opendev.org/admin/groups/9bfde554b17369715f86befdfac57905018f720b,members | 15:47 |
| frickler | gmaan: I would rather add interested contributors than the whole team, that might be a good compromise indeed. +1 to cleanup, same likely goes for https://review.opendev.org/admin/groups/bab0688e5c0371ef63cf6e002806e97a0fb879bb,members (api-sig-core) | 16:46 |
| fungi | frickler: so i'm being told the plan is to not change the member-since datestamp since users are interested in expressing how long they've been involved across the organizational shift. and the choice of the term "renew" was a shorthand to indicate that the process in joining the new org was simplified to not require additional member information but rather consenting to port | 16:47 |
| fungi | the existing information to the new organization. i understand these were not technically correct, but basically compromises to satisfy the legal requirements for upcoming governance board elections balanced against common user expectations | 16:47 |
| fungi | from an implementation perspective, there is a new flag in the database to indicate whether the individual is a member of the new org, and i'll get an election tooling patch up shortly to handle that transition | 16:48 |
| fungi | wes wilson is working on some updated wording for the renewal that will hopefully help clarify | 16:51 |
| gmaan | frickler: ++ yeah, interested contributors are good explicit way | 16:51 |
| frickler | so the 180d frame is not relevant for TC+PTL elections, or is it? but people need to renew/transfer their membership for a valid candidacy? | 16:52 |
| fungi | correct | 16:52 |
| fungi | the 180d timeframe is specifically about openinfra governing board elections because their charter requires membership for that long in order to be eligible to vote | 16:52 |
| fungi | the tc charter determins who's eligible to vote and run in openstack technical elections, and does not impose that limitation | 16:53 |
| fungi | the revised wording for the web form looks like it's going to refer to it as "reestablishing" membership and the button text will be "confirm" rather than renew | 16:54 |
| fungi | at least that's the mockup i just looked over, so will probably take effect later today | 16:55 |
| opendevreview | Stephen Finucane proposed openstack/governance master: Deprecate shade, os-client-config https://review.opendev.org/c/openstack/governance/+/953549 | 17:04 |
| fungi | frickler: and it's been updated now | 17:37 |
| frickler | fungi: thx, I think that's a better wording. nit: the link from the profile page still says "Renew Your Membership" | 17:42 |
| fungi | thanks for pointing that out! i'll pass it along | 17:52 |
| fungi | sounds like he's working on adjusting that link as well now too | 17:54 |
| *** vhari_ is now known as vhari | 19:03 | |
Generated by irclog2html.py 4.0.0 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!