| tonyb | gmann: Yeah. It's still a very high number and more worrying is the TC count. 1 candidate for 5 seats :/ | 00:04 |
|---|---|---|
| opendevreview | Merged openstack/election master: Adding noonedeadpunk candidacy for OpenStack-Ansible PTL https://review.opendev.org/c/openstack/election/+/873642 | 00:04 |
| opendevreview | Merged openstack/election master: Add Pierre Riteau's candidacy for Blazar PTL (Bobcat) https://review.opendev.org/c/openstack/election/+/873641 | 00:12 |
| opendevreview | Merged openstack/election master: Add Carlos da Silva candidacy for Manila PTL https://review.opendev.org/c/openstack/election/+/873640 | 00:12 |
| opendevreview | Merged openstack/election master: Adding Michael Johnson candidacy for Designate https://review.opendev.org/c/openstack/election/+/873631 | 00:12 |
| gmann | tonyb: indeed, TC is more worry. let's see | 02:14 |
| gmann | pinged current PTLs of projects need nomination, let's see by tomorrow if number goes low | 02:41 |
| gmann | sent reminder on PTL email who are not on IRC | 02:45 |
| opendevreview | Wu Wenxiang proposed openstack/election master: Adding wu.wenxiang candidacy for skyline https://review.opendev.org/c/openstack/election/+/873665 | 03:11 |
| opendevreview | Takashi Kajinami proposed openstack/election master: Adding Takashi Kajinami candidacy for Puppet OpenStack PTL https://review.opendev.org/c/openstack/election/+/873666 | 03:57 |
| gmann | more nominations are started now | 03:57 |
| opendevreview | Takashi Kajinami proposed openstack/election master: Adding Takashi Kajinami candidacy for Heat PTL https://review.opendev.org/c/openstack/election/+/873669 | 04:10 |
| opendevreview | Brian Rosmaita proposed openstack/election master: Adding Brian Rosmaita candidacy for TC https://review.opendev.org/c/openstack/election/+/873670 | 04:11 |
| opendevreview | Merged openstack/election master: Adding wu.wenxiang candidacy for skyline https://review.opendev.org/c/openstack/election/+/873665 | 04:23 |
| opendevreview | Merged openstack/election master: Adding Brian Rosmaita candidacy for TC https://review.opendev.org/c/openstack/election/+/873670 | 04:28 |
| opendevreview | Merged openstack/election master: Adding Takashi Kajinami candidacy for Puppet OpenStack PTL https://review.opendev.org/c/openstack/election/+/873666 | 04:35 |
| opendevreview | Merged openstack/election master: Adding Takashi Kajinami candidacy for Heat PTL https://review.opendev.org/c/openstack/election/+/873669 | 04:35 |
| opendevreview | Andrey Pavlov proposed openstack/election master: Add Andrey Pavlov candidacy for Ec2 API https://review.opendev.org/c/openstack/election/+/873676 | 06:00 |
| opendevreview | Gregory Thiemonge proposed openstack/election master: Adding Gregory Thiemonge candidacy for Octavia PTL https://review.opendev.org/c/openstack/election/+/873678 | 06:47 |
| opendevreview | Matthias Runge proposed openstack/election master: Add Matthias Runge candidacy for Telemetry PTL https://review.opendev.org/c/openstack/election/+/873679 | 07:13 |
| opendevreview | Wenping Song proposed openstack/election master: Add Wenping Song candidacy for Cyborg PTL https://review.opendev.org/c/openstack/election/+/873682 | 07:53 |
| opendevreview | suzhengwei proposed openstack/election master: Add suzhengwei candidacy for Masakari PTL https://review.opendev.org/c/openstack/election/+/873683 | 08:05 |
| opendevreview | inspurericzhang proposed openstack/election master: Adding Eric Zhang candidacy for Venus https://review.opendev.org/c/openstack/election/+/873687 | 08:58 |
| *** gibi_ is now known as gibi | 09:00 | |
| opendevreview | wu.chunyang proposed openstack/election master: Add wu.chunyang candidacy for Trove PTL https://review.opendev.org/c/openstack/election/+/873688 | 09:06 |
| opendevreview | Jake Yip proposed openstack/election master: Add Jake Yip's candidacy for Magnum PTL https://review.opendev.org/c/openstack/election/+/873700 | 11:24 |
| opendevreview | Roman Dobosz proposed openstack/election master: Adding Roman Dobosz candidacy for Kuryr PTL https://review.opendev.org/c/openstack/election/+/873701 | 11:27 |
| opendevreview | Roman Dobosz proposed openstack/election master: Adding Roman Dobosz candidacy for Kuryr PTL https://review.opendev.org/c/openstack/election/+/873701 | 11:30 |
| opendevreview | Merged openstack/election master: Add Andrey Pavlov candidacy for Ec2 API https://review.opendev.org/c/openstack/election/+/873676 | 11:54 |
| opendevreview | Merged openstack/election master: Adding Gregory Thiemonge candidacy for Octavia PTL https://review.opendev.org/c/openstack/election/+/873678 | 12:05 |
| opendevreview | Merged openstack/election master: Add Matthias Runge candidacy for Telemetry PTL https://review.opendev.org/c/openstack/election/+/873679 | 12:05 |
| opendevreview | Merged openstack/election master: Add Wenping Song candidacy for Cyborg PTL https://review.opendev.org/c/openstack/election/+/873682 | 12:05 |
| opendevreview | Merged openstack/election master: Add wu.chunyang candidacy for Trove PTL https://review.opendev.org/c/openstack/election/+/873688 | 12:11 |
| opendevreview | Merged openstack/election master: Add suzhengwei candidacy for Masakari PTL https://review.opendev.org/c/openstack/election/+/873683 | 12:16 |
| opendevreview | Merged openstack/election master: Adding Eric Zhang candidacy for Venus https://review.opendev.org/c/openstack/election/+/873687 | 12:16 |
| opendevreview | Merged openstack/election master: Add Jake Yip's candidacy for Magnum PTL https://review.opendev.org/c/openstack/election/+/873700 | 12:16 |
| opendevreview | Merged openstack/election master: Adding Roman Dobosz candidacy for Kuryr PTL https://review.opendev.org/c/openstack/election/+/873701 | 12:30 |
| *** dasm|off is now known as dasm | 13:10 | |
| opendevreview | Kristi Nikolla proposed openstack/election master: Add Kristi Nikolla for TC in Bobcat https://review.opendev.org/c/openstack/election/+/873714 | 14:29 |
| opendevreview | Lance Albertson proposed openstack/election master: Add Lance Albertson candidancy for Openstack Chef PTL https://review.opendev.org/c/openstack/election/+/873719 | 15:06 |
| opendevreview | Martin Kopec proposed openstack/election master: Add Martin Kopec candidacy for QA Bobcat PTL https://review.opendev.org/c/openstack/election/+/873736 | 17:31 |
| gmann | election updates: from 31 yesterday we are down to 14 (3 nomination in-review) projects without nomination and 2 TC seats | 18:19 |
| gmann | ping worked fine. I will send another reminder to the remaining projects by today EOD. | 18:26 |
| gmann | Hopefully there will be notification email from election official too today | 18:27 |
| fungi | we also need to be careful that we not only have enough tc candidates to fill the open seats but to do so without ending up with a majority of the tc affiliated with the same organization | 18:34 |
| gmann | yeah diversity is one of critical known issue and worst part is that we do not have perfect solution for that. I keep raising and saying that it might be in alert situation soon. | 18:39 |
| fungi | ideally people who are employed by the same company who are considering running for seats on the tc would coordinate among themselves in order to avoid having too many at once | 18:43 |
| dansmith | fungi: there's really no such coordination of that in my company, FWIW | 18:43 |
| dansmith | fungi: do you not see a path out of that requirement at some point? | 18:44 |
| clarkb | It would require a bylaws update? I could be wrong about that though | 18:44 |
| dansmith | because I'm concerned about how we proceed if we've got enough people willing but not enough for the diversity requirement | 18:44 |
| gmann | yes, bylaw update needed | 18:44 |
| dansmith | yeah, I know, but .. might be good to get ahead of that if we see a future where that's going to be required | 18:45 |
| dansmith | and if not, I guess figure out what to do | 18:45 |
| gmann | worst will be we do not fill all seats and still goes more than half of TC from same companies | 18:45 |
| fungi | we could declare openstack a project of that company instead of an independent community | 18:45 |
| dansmith | reducing the TC seats doesn't really fix it I think | 18:45 |
| gmann | in that case it is like "no one is interested in TC but you also cannot contribute as you are from same company" | 18:46 |
| gmann | dansmith: that is one option is we do not see more people interested | 18:46 |
| gmann | but yes diversity requirement still needs to be revised | 18:46 |
| dansmith | gmann: but reducing the seats doesn't change the makeup really does it? | 18:46 |
| fungi | once the majority of the primary governing body for openstack works at the same company, it's no longer possible for affiliates of all other organizations to outvote them | 18:46 |
| gmann | yeah | 18:46 |
| dansmith | if we reduce seats but the majority are still from one company... | 18:46 |
| gmann | yes, diversity requirement has to change if we are not able to get more companies contributing | 18:47 |
| dansmith | well, what I'm saying is, if we hit that problem in one election, but it takes 6mo to do the bylaw change, we might be in a pickle we can't solve immediately | 18:47 |
| dansmith | maybe "the tc has to be disbanded this cycle unless some other people step up" will be the carrot we need, I dunno | 18:48 |
| gmann | dansmith: yeah, board has some option for that. I think some exception too but need to check | 18:48 |
| dansmith | oh okay | 18:48 |
| fungi | also worth noting, the percentage of leadership with a common affiliation is significantly higher than for the contributor electorate as a whole. i ran some statistics, and among contributors who were active in 2022 and reported an affiliation, only something like 28% reported their affiliation with the same organization (or with a subsidiary/division thereof) | 18:49 |
| gmann | "(c) In the event of a Technical Committee election that would result in half or more of the members of the Technical Committee being Affiliated, the Board of Directors may defer the effective date of office of the newly elected Technical Committee members who are Affiliated for a period not to exceed thirty (30) days after a resolution by the Board of Directors approving such deferral." | 18:49 |
| dansmith | fungi: ah well that's good | 18:49 |
| gmann | but bylaw does not talk or considered the situation of less candidates than TC seats and still not diverse | 18:50 |
| fungi | gmann: the bylaws basically go on to say that the board is stopping the tc from electing anyone until they can figure out how to not exceed the majority limitation | 18:50 |
| gmann | but yes, that is something to be dicussed i board | 18:50 |
| dansmith | gmann: yeah, that seems relevant, but deferring doesn't do anything to help it seems | 18:50 |
| gmann | dansmith: yes, differing will stop the things to merge as per TC charter and required motion vote etc | 18:51 |
| fungi | the bylaws don't explicitly say "the board can decide it's okay to have a majority with the same affiliation under special circumstances" since that would require the bylaws to be changed | 18:51 |
| dansmith | ack | 18:51 |
| dansmith | well, this is why it seems like it might be prudent to get ducks in a row before that situation happens, either decide what happens to keep the diversity, remove the requirement, or figure out what the plan is | 18:52 |
| gmann | bylaws change require time but it seems not known/documented solution for this situation "less TC candidates for open seat and not diverse " | 18:52 |
| dansmith | if no ducks are aligned thusly, then after the election we have a scramble | 18:52 |
| fungi | basically how that will play out is either 1. the board helps shake down people on the streets until it can pressgang them into service, or 2. the board starts revising the bylaws | 18:52 |
| dansmith | fungi: yeah | 18:53 |
| dansmith | sucks for the people that got elected and told no, though :/ | 18:53 |
| gmann | I think bylaw has to be revised in advance or at least handle the situation of less interested people | 18:53 |
| gmann | I mentioned that in last election also we should have something ready in advance before it occur | 18:54 |
| fungi | if that's really the only option, then yes the tc should start talking to the board of directors about allowing openstack to become primarily governed by a single company | 18:54 |
| gmann | dansmith: yeah. I hate that situation. and even when "no other people want to be in TC but you cannot be as you are from company who is helping OpenStack a lot" | 18:55 |
| dansmith | yeah | 18:55 |
| gmann | I will bring this to Board this time | 18:55 |
| dansmith | fungi: to be clear, I 100% prefer the diversity requirement (and the diversity that it brings), I just don't want us to get caught with a thing that has to be resolved | 18:56 |
| dansmith | and I really think it sucks to let people run, be elected and tell them (or others on the tc) that they can't serve | 18:56 |
| dansmith | especially since there's no cabal of tc members and candidates (at my company) preparing for that possibility | 18:56 |
| gmann | this topic will at least make more attention to the less diversity issue which we have been raising in Board for long | 18:57 |
| fungi | well, technically they wouldn't be "elected" under the current bylaws, because the board would suspend confirmation of the results until the majority situation is worked out | 18:58 |
| dansmith | well, you know what I mean | 18:58 |
| dansmith | (I hope) | 18:59 |
| dansmith | "voted for" | 18:59 |
| fungi | yep, i get it | 18:59 |
| fungi | we've had that happen multiple times for the foundation's board of directors though | 18:59 |
| fungi | if two people affiliated with a platinum member org (who is guaranteed a seat) rank in the individual member election, only the higher of the two is elected | 19:00 |
| dansmith | but after a call pleading for people to run? | 19:01 |
| dansmith | it's one thing if you've got 20 candidates for 10 spots and there's a diversity requirement that means one will not get it, but it's another to say "we have nobody to fill these seats...except all those people over there with the wrong color hat" :) | 19:01 |
| fungi | blue | 19:02 |
| dansmith | anyway, I know I can't be perceived to be impartial on this topic so I should shut up, but.. I just hope we (the community) can get ahead of it for the sake of the individuals | 19:02 |
| knikolla[m] | :/ | 19:03 |
| gmann | agree | 19:04 |
| knikolla[m] | once you weaken those protections, it's almost impossible to bring them back. | 19:05 |
| dansmith | knikolla[m]: I dunno, nova introduced one because lack-of-diversity was becoming a problem, so it's certainly possible | 19:07 |
| dansmith | but I agree that removing it is not a good look regardless | 19:07 |
| gmann | but if we are not getting more diversity and community/board/foundation are not able to attract more company now then it is less possible to have more companies stepping up in future | 19:08 |
| gmann | main motive is to bring more attention from board and if more companies can start thinking on this | 19:08 |
| knikolla[m] | but an action like this makes it even less possible due to the perception that it will validate. I agree that it is not a good look, and that it might be the only path forward, but I want to implement new safeguards if these ones are removed. | 19:09 |
| knikolla[m] | In the case of Nova, the safeguarding mechanism is the TC. In the case of the TC, it's the foundation. | 19:10 |
| dansmith | maybe the foundation can just force fungi to run ;P | 19:11 |
| gmann | that is true. we had safeguard of though un-written or two different company (than author) +2 to merge any code | 19:11 |
| gmann | governance is important part but if we can trust company/people for merging the code/features not to be vendor lockin then at some point we should trust for governance also | 19:12 |
| diablo_rojo_phone | I think rather than lifting or weakening the diversity requirement, maybe we look at shrinking the size of the TC to 7. | 19:13 |
| gmann | and if it happen we are not stopping more companies to come in community and chaneg bylaw alslo | 19:13 |
| gmann | also | 19:13 |
| gmann | size reduction is unrelated to diversity even it make it more worst | 19:13 |
| knikolla[m] | That's not really true though. Merging code has strict guidelines about preserving backwards compatibility, passing CI, can be reverted with another 2 +2s. | 19:13 |
| dansmith | diablo_rojo_phone: does that solve it? | 19:13 |
| dansmith | depends on who is left, but it could be worse | 19:13 |
| knikolla[m] | Governance changes are much more impactful and it's impossible to revert without a majority, which would not be possible anymore. | 19:14 |
| gmann | knikolla[m]: and why +2 members cannot change CI? | 19:14 |
| fungi | dansmith: i didn't want to say it out loud, but yes if we end up being short enough to fill seats in compliance with the bylaws and current tc charter, then i'll nominate myself at the last minute | 19:14 |
| fungi | assuming one will be enough | 19:14 |
| knikolla[m] | gmann: I imagine at some point the TC would intervene. | 19:14 |
| dansmith | fungi: excellent, problem solved IMHO :D | 19:14 |
| gmann | knikolla[m]: sure but its trust which is making community success more than anything | 19:15 |
| gmann | I am not denying laws should not be there but based on situation | 19:15 |
| diablo_rojo_phone | I'm not saying it would solve the problem but that it's an alternative approach. | 19:15 |
| diablo_rojo_phone | With a smaller number it's less seats to fill overall. | 19:16 |
| diablo_rojo_phone | A single company having the majority may still be an issue but the scale is smaller so it might be easier to handle finding people to fill seats. | 19:18 |
| knikolla[m] | gmann: I completely agree. And usually trust isn't broken by one single action, or even knowingly. The influence of an employer, in particular when your job and health insurance depends on it, isn't even about trust anymore. | 19:18 |
| rosmaita | not completely off-topic, but I was just looking at members.yaml and the 'date' field for each member is kind of weird | 19:29 |
| rosmaita | mine is 'February 2022' which is when I was elected, but Dan's is 'September 2023', which is when his term expires. | 19:29 |
| rosmaita | What's supposed to be in there? | 19:29 |
| fungi | dan was elected in the future | 19:30 |
| fungi | but no, these days it's supposed to be the date each person was elected | 19:30 |
| gmann | rosmaita: that is correct, it is date of elected date | 19:30 |
| fungi | it used to be when their term was expected to expire, but the flexible term duration we switched to not long ago changed it | 19:30 |
| fungi | because we could no longer pinpoint exactly when their term should end | 19:31 |
| fungi | only an approximate range of dates | 19:31 |
| rosmaita | ok, so there shouldn't be any 2023 dates in there yet, since the first 2023 election has not happened yet | 19:31 |
| gmann | rosmaita: we can calculate the end term with "elected for a term that expires at the conclusion of the second scheduled election after the start of their term or after 14 months, " | 19:31 |
| dansmith | rosmaita: my corporate overloard has already paid off for my continued reelection through the end of the year, obviously ;P | 19:31 |
| gmann | end date cannot be known in advance as election dates are not so start date are written | 19:32 |
| gmann | it is written as "Elected On" | 19:33 |
| rosmaita | i was looking at this: https://opendev.org/openstack/governance/src/branch/master/reference/members.yaml | 19:34 |
| rosmaita | so all those 'September 2023' should be 'September 2022' | 19:34 |
| gmann | rosmaita: ohk, on site it is "Elected On" but yes we can change here too for clarification | 19:34 |
| fungi | it's likely that the election tools which generate the patch to add those did not get updated for the change to elected-on | 19:35 |
| gmann | rosmaita: name of field can be corrected from 'date' to 'start date' | 19:35 |
| rosmaita | i couldn't find it on the website, so went to the source code | 19:35 |
| gmann | or 'elected on' | 19:35 |
| gmann | here https://governance.openstack.org/tc/#current-members | 19:36 |
| rosmaita | OK, but gmann, you were not elected on September 2023! | 19:36 |
| gmann | oh wait | 19:37 |
| gmann | rosmaita: yeah sept 2023 are wrong, not sure how it got wrong | 19:39 |
| gmann | but we should fix those | 19:39 |
| rosmaita | i wonder if we should include an "Affiliation" field, because just looking at the email addresses, it looks like only 1 red hatter is on the TC | 19:39 |
| rosmaita | people might not realize how dire the affiliation situation is | 19:40 |
| knikolla[m] | good point | 19:41 |
| gmann | rosmaita: +1, good point | 19:41 |
| fungi | the election tooling has facilities to query affiliation. we could put it in the data file and just not expose it on the web site. there's a balance to strike between making sure we don't end up with a majority and making it look like tc members are appointed representatives of their employers | 19:41 |
| gmann | rosmaita: can you propose those or i can do if you want | 19:41 |
| rosmaita | gmann: for the date? sure, i will do it | 19:42 |
| gmann | +1 | 19:42 |
| fungi | obviously tc members are supposed to represent the electorate not their employers, the majority affiliation limit exists to try to prevent things from going off the rails if they effectively did end up acting in the interests of their employer instead of the electorate. but as soon as we start publishing their names and employer names side by side, it looks like we expect them to act as | 19:42 |
| fungi | employer representatives | 19:42 |
| dansmith | yeah I mean | 19:43 |
| gmann | I can add affiliation things | 19:43 |
| rosmaita | fungi: good point | 19:43 |
| dansmith | I want to be clear that I don't just do what my employer tells me to (nor do they tell me what to do) | 19:43 |
| rosmaita | dansmith: i don't think anyone would accuse you of doing whatever someone told you! | 19:44 |
| dansmith | I'm definitely on the TC as me, not as a redhatter | 19:44 |
| gmann | this is info not the direction change of any member to serve as company right? | 19:44 |
| dansmith | rosmaita: I take that as a compliment :) | 19:44 |
| rosmaita | :D | 19:44 |
| rosmaita | gmann: yes, but i think fungi has a good point ... it could be misinterpreted, so let's not do it (provide the employer info) | 19:44 |
| dansmith | ++ | 19:45 |
| fungi | obviously tc members are supposed to represent the electorate not their employers, the majority affiliation limit exists to try to prevent things from going off the rails if they effectively did end up acting in the interests of their employer instead of the electorate. but as soon as we start publishing their names and employer names side by side, it looks like we expect them to act as | 19:45 |
| fungi | employer representatives. but we already struggle with the broader public perception that openstack is a commercially-controlled product and not community developed, so just want to be careful making it look even more like that | 19:45 |
| gmann | humm | 19:45 |
| fungi | i didn't mean to repeat my prior comment, silly input buffer | 19:45 |
| gmann | foundation profile has affiliation right? | 19:45 |
| dansmith | it's a bit different for foundation | 19:45 |
| fungi | yes, that's where the election officials query it from | 19:45 |
| dansmith | maybe a table under the members with count-from-employer ? | 19:46 |
| fungi | (specifically from an api that the foundation profile also uses) | 19:46 |
| knikolla[m] | https://www.openstack.org/community/tech-committee | 19:46 |
| knikolla[m] | you can already see the affiliation here ^ | 19:46 |
| gmann | yeah that also so should we remove from there too? | 19:46 |
| dansmith | nice you can also see that I have no bio | 19:46 |
| fungi | oof, that wasn't supposed to be like that. i think they ended up reusing the board of directors rendering routine to also show the tc | 19:46 |
| fungi | i'll bring that up with the webdev folks who run that site | 19:47 |
| gmann | being consistent on all place is good but considering company info in TC page will be mislead is confusing to me | 19:47 |
| knikolla[m] | i'm also entirely unsure where to go to update the bio there. | 19:48 |
| gmann | honestly saying, I do not mind adding it in TC page also as that is just info and why to hide that | 19:48 |
| fungi | yes, i don't think the foundation's tc page is supposed to be showing affiliations. the board members page shows that because of platinum board seats representing their employers | 19:48 |
| gmann | board page show for individual board also | 19:48 |
| gmann | anyways let's fix the date for now | 19:49 |
| rosmaita | knikolla[m]: click on the openstack logo under your name | 19:50 |
| rosmaita | then you have to log in, and then find your profile page again | 19:50 |
| rosmaita | and there will be an edit button | 19:50 |
| gmann | this is edit page which gets redirected from openstack one https://id.openinfra.dev/accounts/user/profile | 19:51 |
| knikolla[m] | rosmaita: thank you! really helpful! | 19:52 |
| fungi | also https://www.openstack.org/profile/ should give you the ability to edit the same info | 19:53 |
| fungi | i think data gets replicated between the two at this point | 19:53 |
| gmann | no that point the edit to https://id.openinfra.dev/accounts/user/profile | 19:53 |
| fungi | ahh, yes they did update that | 19:54 |
| fungi | okay so the old url is read-only now | 19:54 |
| fungi | and replicated from id.openinfra.dev | 19:54 |
| knikolla[m] | I don't know what I did wrong the last time, as it took me to the OpenStack ID profile edit, rather than the foundation profile edit. | 19:54 |
| knikolla[m] | which seem to be different. | 19:54 |
| fungi | for a while the replication was going in the other direction | 19:54 |
| knikolla[m] | noted | 19:55 |
| fungi | oh, actually it's more confusing with that | 19:56 |
| opendevreview | Brian Rosmaita proposed openstack/governance master: Correct 'date' field https://review.opendev.org/c/openstack/governance/+/873749 | 19:56 |
| gmann | not sure if speaker details are also syncup from single place or it is different https://www.openstack.org/profile/speaker | 19:56 |
| fungi | on id.openinfra.dev you can update your name, contact info and bio and well as some other settings. to update your affiliation you still have to do it on www.openstack.org | 19:57 |
| fungi | the buttons for add/edit/delete affiliations with date ranges | 19:57 |
| fungi | not sure if they're working on porting that to the new interface | 19:58 |
| gmann | right | 19:59 |
| gmann | also speaker bio porting to same place as bio/other info can be good | 20:00 |
| gmann | everything in single place is helpful | 20:00 |
| fungi | right, i'm trying to find out now if there's work in progress to move the rest of that to the new id system | 20:00 |
| fungi | okay, also there's a newer interface at https://openinfra.dev/a/profile for the foundation profile (rather than id) fields, you can find the affiliation stuff at the bottom of that page | 20:10 |
| fungi | though i'm talking to them about that still being confusing to have split into two places | 20:10 |
| rosmaita | fungi: my plan to run ChatGPT for the TC so you wouldn't have to has run up against the bylaws provision that "Individual Members must be natural persons" | 21:00 |
| rosmaita | it actually wrote a nice nomination letter: https://etherpad.opendev.org/p/chatGPT-for-TC | 21:00 |
| fungi | awesome! i for one welcome our new artificially unintelligent overlords | 21:13 |
| opendevreview | Merged openstack/election master: Add Kristi Nikolla for TC in Bobcat https://review.opendev.org/c/openstack/election/+/873714 | 21:59 |
| opendevreview | Merged openstack/election master: Add Lance Albertson candidancy for Openstack Chef PTL https://review.opendev.org/c/openstack/election/+/873719 | 21:59 |
| opendevreview | Merged openstack/election master: Add Martin Kopec candidacy for QA Bobcat PTL https://review.opendev.org/c/openstack/election/+/873736 | 22:02 |
| opendevreview | Slawek Kaplonski proposed openstack/election master: Add Slawek Kaplonski for TC in Bobcat https://review.opendev.org/c/openstack/election/+/873756 | 22:35 |
| zaneb | rosmaita: that first one is disturbingly realistic | 23:44 |
Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!