| opendevreview | Merged openstack/governance master: Classify gov changes by hashtag, not topic https://review.opendev.org/c/openstack/governance/+/981832 | 02:16 |
|---|---|---|
| opendevreview | Merged openstack/governance master: Revert "Revive os_monasca" https://review.opendev.org/c/openstack/governance/+/974775 | 03:08 |
| opendevreview | Merged openstack/openstack-manuals master: Update sitemap https://review.opendev.org/c/openstack/openstack-manuals/+/984150 | 06:32 |
| sean-k-mooney | gouthamr: clarkb fungi i just sent https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack.org/thread/6M43NTTOI3ZUQBIEJIJZTKJVCZZE5WLC/ to kind fo kick start that converation on if we should have some minimal scfolidng in repos to make a space for agentic devleopement without forceing it or actully really commiting any of the content to the repo outside of a | 11:02 |
| sean-k-mooney | very minimal tool independent baseline | 11:02 |
| sean-k-mooney | gouthamr: i think you said you wanted ot ahve a topic on somethign similar in the ptg so i tried to have somethign concret that coudl be discussed but its just an idea for feedback at this point | 11:03 |
| opendevreview | cid proposed openstack/governance master: [EOL]: Retire VirtualPDU https://review.opendev.org/c/openstack/governance/+/984545 | 11:36 |
| clarkb | sean-k-mooney: your email seemed well thought out. The only thought I've got is probably bikeshedding, but when we first introduced bindep it read its info from other-requirements.txt. It was decided that was too generic and that bindep.txt should be preferred to avoid confusion or collisions. I worry that ai/ is maybe too generic and may collide with tools if not today but | 15:16 |
| clarkb | eventually | 15:17 |
| clarkb | but also that is easy to change later if necessary. So Its not worth making a big deal or even a response on the mailing list. Just a note to think about potential naming collisions that could happen as these things get formalized | 15:17 |
| cid | stackers, \o/ | 15:28 |
| fungi | welcome back cid | 15:28 |
| cid | When someone get's a free cycle, https://review.opendev.org/c/openstack/governance/+/984545 | 15:28 |
| cid | thank you fungi. Always been around by the way :D. | 15:28 |
| cid | so, ironic is retiring virtualpdu and this is the first steps. | 15:28 |
| sean-k-mooney | clarkb: ya im ok with a difent name | 15:30 |
| sean-k-mooney | that is just what i have in my personla repos | 15:30 |
| sean-k-mooney | so we could call that scratch or workspace or anything else | 15:30 |
| sean-k-mooney | clarkb: neutron (rodolfo) was thinkign of llm https://review.opendev.org/c/openstack/neutron/+/982466 | 15:31 |
| fungi | cid: please have dtansur +1 the project-config change for confirmation, or point to where the team recorded some consensus on retiring it | 15:32 |
| fungi | (dtansur because he's the tact sig liaison for ironic) | 15:32 |
| clarkb | sean-k-mooney: ya and I think wrost case you just chagne it later if some tool important enough shows up that collides | 15:33 |
| cid | alright, tks fungi. I will ping dtantsur | 15:35 |
| gouthamr | sean-k-mooney: ty for putting that together and proposing the topic! let me think through this, it feels like we can break up the AI topics into separate sessions (even if they're back-to-back).. some of this is pure governance stuff, and others like the one you proposed are governance+technical proposals | 16:13 |
| gouthamr | tc-members: a gentle reminder that the weekly IRC meeting will be hosted here in ~45 minutes. The agenda is here: https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee#Agenda | 16:14 |
| sean-k-mooney | gouthamr: we can also jsut do this async on the list as long as we get a temperture reading on comunity apitite for this adn some general direction at the tc/board level | 16:25 |
| sean-k-mooney | PTG are great fo high bandiwth converation but a lot of these topic can evovle naturaly in the proejct over time | 16:26 |
| spotz[m] | WIll be right back taking a dog out | 16:57 |
| cardoe | early o/ cause I'm gonna go grab my lunch and back in 3 minutes | 16:59 |
| gouthamr | ack and ack | 17:00 |
| gouthamr | #startmeeting tc | 17:00 |
| opendevmeet | Meeting started Tue Apr 14 17:00:50 2026 UTC and is due to finish in 60 minutes. The chair is gouthamr. Information about MeetBot at http://wiki.debian.org/MeetBot. | 17:00 |
| opendevmeet | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 17:00 |
| opendevmeet | The meeting name has been set to 'tc' | 17:00 |
| gouthamr | Welcome to the weekly meeting of the OpenStack Technical Committee. A reminder that this meeting is held under the OpenInfra Code of Conduct available at https://openinfra.dev/legal/code-of-conduct. | 17:01 |
| gouthamr | Today's meeting agenda can be found at https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee | 17:01 |
| gouthamr | #topic Roll Call | 17:01 |
| noonedeadpunk | o/ | 17:01 |
| dansmith | o/ | 17:01 |
| bauzas | o/ | 17:02 |
| gouthamr | courtesy-ping: frickler, mnasiadka | 17:02 |
| mnasiadka | o/ | 17:02 |
| gouthamr | no noted absence today.. let's get started | 17:04 |
| gouthamr | #topic Last week's AIs | 17:04 |
| gouthamr | noonedeadpunk took one to send out ML notifications regarding the retirement and deprecation of venus and vitrage projects | 17:05 |
| gouthamr | #link https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack.org/thread/PGT5EUDSNEILHHA2GY6DOQ7FRFIXHTC7/ (Venus retirement) | 17:06 |
| gouthamr | did we need one for vitrage, noonedeadpunk ? | 17:06 |
| noonedeadpunk | Yes, we do | 17:06 |
| noonedeadpunk | I just still didn't get to content removal | 17:06 |
| noonedeadpunk | and wanted to send one when it's done | 17:06 |
| noonedeadpunk | and then waiting a bit for venus reaction | 17:07 |
| gouthamr | ack on the venus direction; but with vitrage, just clarifying if the content removal will be WIP until we get ML reactions? | 17:07 |
| noonedeadpunk | as quite some xstatic under vitrage governance are used for venus | 17:07 |
| spotz[m] | o/ | 17:08 |
| gouthamr | noonedeadpunk: will the content removal be WIP until you hear back from the ML, i am guessing the answer is "yes, sure" | 17:09 |
| noonedeadpunk | yes, sure :) | 17:09 |
| gouthamr | :P thanks, let's move to the next one | 17:10 |
| gouthamr | we finally closed out on the os-monasca changes | 17:10 |
| gouthamr | requestsexceptions' retirement is still stuck due to dependencies | 17:10 |
| gouthamr | the proposal to use hashtags instead of topics to implement our review house rules has merged | 17:11 |
| gouthamr | #link https://review.opendev.org/c/openstack/governance/+/981832 | 17:11 |
| gouthamr | please see the specific hashtags we'll use on this link: | 17:12 |
| gouthamr | #link https://governance.openstack.org/tc/reference/house-rules.html | 17:12 |
| gouthamr | noonedeadpunk and cardoe took on an AI about drafting a MariaDB collation related cross-project goal | 17:12 |
| gouthamr | you were hoping to do this before PTG however.. it'd be nice if you'd like project maintainers to vet it on Monday, but we can discuss this further on Friday if you'd need some dedicated time | 17:13 |
| cardoe | yeah we've not made progress | 17:14 |
| cardoe | I've been testing out some configurations | 17:14 |
| cardoe | I'll follow up with noonedeadpunk this week | 17:15 |
| gouthamr | thank you | 17:15 |
| noonedeadpunk | I'm jsut burried with internal stuff /o\ | 17:15 |
| gouthamr | ack :| | 17:16 |
| gouthamr | we had two call outs to the community regarding PTG scheduling last week: | 17:16 |
| gouthamr | #link https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack.org/message/OHGVAYGT2MJGMN7KCRUAZVQPT6R5GHGT/ (Please schedule cross-project sessions earlier in the week) | 17:16 |
| gouthamr | #link https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack.org/message/TRKVDTCLVQOMX2HOSXQ2MXSIZWSP5PWD/ (TC/Operators Hour on Monday April 20 2026 1700 UTC) | 17:16 |
| gouthamr | i'll bump the operators' one with a ICS file because i had a couple of emails asking for a calendar invite | 17:18 |
| gouthamr | i'll also be sending a reminder to PTLs/DPLs regarding the TC forum we'll have with them on Apr 20th at 1600 UTC | 17:18 |
| gouthamr | mharley[m] was here last week taking AIs regarding the PQC proposals he was championing | 17:19 |
| gouthamr | we told him that he can also play the role of being the tc liaison, he worked with fungi to get a dedicated track for the PQC pop up team | 17:19 |
| gouthamr | that's all the AIs i see, was anyone working on anything else? | 17:20 |
| gouthamr | #topic PTG | 17:22 |
| gouthamr | we'll be dropping our IRC meeting next week because of the PTG | 17:22 |
| gouthamr | there'll be no TC sessions on tuesday, but, i'm sure you're all going to be too busy in other sessions to warrant this distraction | 17:23 |
| gouthamr | any objections to this? | 17:23 |
| bauzas | - | 17:23 |
| cardoe | works for me | 17:23 |
| gouthamr | ty | 17:23 |
| gouthamr | #link https://etherpad.opendev.org/p/apr2026-ptg-os-tc (TC PTG Etherpad) | 17:24 |
| gouthamr | ^ final call for topics.. will be slotting these items into the schedule.. | 17:24 |
| gouthamr | small cross project call outs are encouraged for the leaders' forum | 17:24 |
| gouthamr | so please do add any, including prospective goals | 17:25 |
| gouthamr | i'll chat here about the final schedule later in the week.. | 17:26 |
| gouthamr | any comments/concerns to share? | 17:26 |
| gouthamr | okay, lets move to the next topic | 17:28 |
| gouthamr | #topic Launchpad tracker (mal)practices (gouthamr) | 17:28 |
| cardoe | uh oh | 17:30 |
| gouthamr | you're aware that we've been slowly helping teams recover their launchpad teams from inactive individual users over the past couple of releases.. | 17:30 |
| gouthamr | the most recent one was the mistral | 17:30 |
| gouthamr | #link https://answers.launchpad.net/launchpad/+question/824018 | 17:30 |
| gouthamr | launchpad admins are being super responsive about this, which is a good thing... but, being reactive about this sucks, especially when we're being inundated with security bugs of late, and we don't know if the process itself is secure | 17:31 |
| gouthamr | ideally, every bug tracker on launchpad is managed by a team of project maintainers, not an individual.. and this team should be owned/administered by https://launchpad.net/~openstack-admins | 17:32 |
| gouthamr | this allows us to control the group when things start falling apart within projects.. | 17:33 |
| gouthamr | but, beyond the memberships themselves, administrators have a lot of control in launchpad regarding bugs and blueprints.. for one, the "bug sharing" settings are insecure by default and will need to be properly set | 17:34 |
| gouthamr | OpenStack's VMT has a process to vet private security bugs and pull in people selectively to maintain any necessary embargoes for bugs.. | 17:35 |
| gouthamr | #link https://security.openstack.org/vmt-process.html | 17:35 |
| gouthamr | this process falls apart if the bug tracker has been misconfigured | 17:35 |
| fungi | #klink https://security.openstack.org/repos-overseen.html#requirements VMT Repositories Overseen (Requirements) | 17:36 |
| fungi | #4 in particular states "The defect tracker for each overseen repository must be configured to initially only provide access for the VMT for privately-submitted reports." | 17:37 |
| fungi | er, i flubbed the link tag, sorry | 17:37 |
| fungi | #link https://security.openstack.org/repos-overseen.html#requirements VMT Repositories Overseen (Requirements) | 17:37 |
| gouthamr | ty.. | 17:37 |
| gouthamr | #link https://gist.github.com/gouthampacha/2e31f5127a907e6c59d357cf98dc35e2 | 17:38 |
| mharley[m] | Hello, folks. Was I summoned? 😊 | 17:38 |
| spotz[m] | hehe | 17:39 |
| mharley[m] | gouthamr:, how may I help? | 17:39 |
| gouthamr | mharley[m]: yes and no, please read scrollback.. we're onto a different topic now | 17:39 |
| mharley[m] | Sure thing. | 17:39 |
| gouthamr | an AI script went through the release repo to find all the deliverables using launchpad, scanned their launchpad trackers and identified the gaps.. | 17:40 |
| sean-k-mooney | so lookign at that ill just note that openstack-cyborg is not just cyborg becuase that is a diffent project on lauchpad | 17:41 |
| sean-k-mooney | context being https://gist.github.com/gouthampacha/2e31f5127a907e6c59d357cf98dc35e2#file-lp-drivers-audit-2026-04-txt-L106 | 17:41 |
| gouthamr | ah, ty sean-k-mooney | 17:41 |
| gouthamr | makes sense, that part is not actionable, but good to know why it was that way | 17:42 |
| sean-k-mooney | we coudl rename the driver team proably to follow the convention however | 17:42 |
| fungi | openstack/project-config:gerrit/projects.yaml includes the remapping for repository-to-lp name differences or grouping | 17:42 |
| mnasiadka | gouthamr: I’ll raise LP question to sort out the Magnum project teams | 17:42 |
| gouthamr | mnasiadka: no, let's do a bulk request for all the 12 teams | 17:43 |
| gouthamr | ? | 17:43 |
| mnasiadka | Sure, bulk request is fine, I still need that access - not only for security bugs :) | 17:43 |
| mnasiadka | Sooner the better | 17:43 |
| gouthamr | ouch, yes.. let's fix that up | 17:43 |
| gouthamr | #action we'll file a bulk request to transfer the 12 project specific launchpad teams under ~openstack-admins | 17:44 |
| gouthamr | once we do this though, we'll need to flag that PTLs/bug supervisors must fix the projects' security settings | 17:45 |
| gouthamr | if you're reading this, you probably already know what to do.. but, probably a project team guide page can be dedicated to how to set things up on launchpad | 17:46 |
| mnasiadka | Well, in some cases first openstack-admins will need to add PTLs to drivers team (e.g. I have no membership in magnum-ui-drivers) | 17:46 |
| gouthamr | yes, these requests can be made here or on #openstack-infra once the transfer is complete | 17:47 |
| gouthamr | fungi or clarkb have helped add people in the past, and you can then take over and make the rest of the changes | 17:47 |
| gouthamr | i'll do some of this work over this week and bring some "actions to take" material to the TC/Community Leaders' forum session next week | 17:48 |
| fungi | frickler may also help with that (if he has time) | 17:49 |
| fungi | gmaan is in that lp team too | 17:49 |
| gouthamr | that's all i had for $topic.. i appreciate the feedback because this is quite a serious flaw for us for project maintenance and our security process | 17:49 |
| gouthamr | the security-sig / VMT will also be at the forum session and i'll volunteer fungi/JayF to fill us in on the recent upward trend in security bugs that are keeping us awake at night | 17:50 |
| gmaan | ++, i can help whenever needed | 17:50 |
| spotz[m] | I have one thing when we’re all done | 17:51 |
| gouthamr | ack, ty gmaan fungi | 17:51 |
| gouthamr | ack spotz[m], anything else for $topic? | 17:51 |
| spotz[m] | Not this one more new topic | 17:51 |
| gouthamr | #topic A check on gate health | 17:51 |
| fungi | s/forum/ptg/ i assume? | 17:51 |
| gouthamr | fungi: yes, sorry, names | 17:52 |
| fungi | np, just making sure i hadn't missed something | 17:52 |
| gouthamr | well on this topic, #openstack-infra has been busy.. gerrit was upgraded, anubis deployed on several servers.. | 17:53 |
| gouthamr | any concerns to note this week? or bring into next week's discussions? | 17:53 |
| fungi | in the last hour-ish we finally recombined docs.openstack.org requests back onto the same server that hosts the other static sites | 17:53 |
| fungi | now that we have a handle on tuning, it's no longer necessary to offload it to a separate server | 17:54 |
| clarkb | Resolute releases in like 8 days and we've got some work in progress to try and have nodes up and running but that isn't done yet | 17:54 |
| clarkb | bionic is effectively gone at this point | 17:55 |
| fungi | yeah, sadly other distractions and fires have sapped a lot of our available time to get usual things done | 17:55 |
| clarkb | (there may still be some zuul configs that need cleanup but no bionic things should be functioning) | 17:55 |
| gouthamr | neat, having these test nodes would be really nice to roll out py314 jobs onto.. and then find some volunteers to drive devstack-based tempest and other kinda testing onto | 17:56 |
| gouthamr | fungi: clarkb: ack, thank you.. | 17:56 |
| gouthamr | we have a few more minutes.. let me switch topics so we can seed any async discussions or add items to the minutes | 17:57 |
| gouthamr | #topic Open Discussion | 17:57 |
| spotz[m] | My turn?:) | 17:58 |
| gouthamr | yes, go for it, spotz[m] | 17:58 |
| spotz[m] | Ildiko mentioned earlier today that in the contributor and user surveys, I believe, a new question asking about AI usage. It would be very helpful if folks could participate in these surveys and answer the question(s). I haven't done it yet myself so not sure the exact wording or number of questions | 17:59 |
| gouthamr | #link https://openinfrafoundation.formstack.com/forms/openstack_maintainer_experience_survey (Maintainer Survey) | 18:01 |
| gouthamr | #link https://openinfrafoundation.formstack.com/forms/openstack_contributor_experience_survey (Contributor Survey) | 18:01 |
| gouthamr | the PTG is a good time to plug the maintainer one | 18:01 |
| gouthamr | the questions you're asking about: | 18:02 |
| gouthamr | Maintainers' survey: | 18:02 |
| gouthamr | 1) What AI tools are you using to enhance the efficiency of the code review process? | 18:02 |
| gouthamr | 2) How is AI affecting your work in the community as a maintainer, for instance your review workflow and efficiency? | 18:02 |
| gouthamr | 3) What AI tools are you using when preparing your contribution? | 18:02 |
| gouthamr | 4) How is AI affecting your contribution workflow and efficiency? | 18:02 |
| gouthamr | Contributor Survey: | 18:02 |
| gouthamr | 1) What AI tools are you using when preparing your contribution? | 18:02 |
| gouthamr | 2) How is AI affecting your contribution workflow and efficiency? | 18:02 |
| spotz[m] | Thanks for grabbing that out:) | 18:03 |
| * gouthamr will amplify this on the ML in my early TC recap for this week | 18:03 | |
| gouthamr | anything else to note for today? | 18:03 |
| sean-k-mooney | ha that version fo the survy offically opened for input | 18:04 |
| gouthamr | if not, please keep the chatter going here.. no IRC meeting next week.. will be nice to catch up in sync again! hope you have a productive PTG! | 18:04 |
| gouthamr | thank you all for participating | 18:05 |
| sean-k-mooney | i may have missed a mail saying there was a new one but i agree anouching it at the ptg woudl be good | 18:05 |
| gouthamr | ++ | 18:05 |
| gouthamr | #endmeeting | 18:05 |
| opendevmeet | Meeting ended Tue Apr 14 18:05:21 2026 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 18:05 |
| opendevmeet | Minutes: https://meetings.opendev.org/meetings/tc/2026/tc.2026-04-14-17.00.html | 18:05 |
| opendevmeet | Minutes (text): https://meetings.opendev.org/meetings/tc/2026/tc.2026-04-14-17.00.txt | 18:05 |
| opendevmeet | Log: https://meetings.opendev.org/meetings/tc/2026/tc.2026-04-14-17.00.log.html | 18:05 |
| bauzas | I hoepe we'll have a TC time for that | 18:05 |
| fungi | sean-k-mooney: there was a targeted announcement to the contributor/maintainer addresses from gerrit | 18:05 |
| bauzas | I already provided some comments in the TC etherpad about those | 18:05 |
| fungi | i'll be sending a followup announcement to the ml soon | 18:05 |
| sean-k-mooney | ack im not sure if that just missed or got eaten by one of my mail filters or if i just dint recive or see it | 18:07 |
| sean-k-mooney | but cool either way | 18:07 |
| fungi | it may have been integrated into the contributor badge message, i'm not sure, so could have been easy to overlook | 18:08 |
| sean-k-mooney | just lookign for the url in allmail, the lsat time i see https://openinfrafoundation.formstack.com/forms/openstack_maintainer_experience_survey was the results from last cycle. | 18:13 |
| frickler | sorry, my traveling today took much longer than planned. reading backlog now | 18:13 |
| sean-k-mooney | fungi: anyway not impoant enough to spend more time on | 18:14 |
| frickler | fungi: where and when was that "targeted announcement" sent and with which subject? I'm not aware of having received one | 18:38 |
| fungi | it was supposedly sent with emma (e2ma) to the gerrit perferred e-mail addresses of any accounts that contributed merged changes or voted with core reviewer privs on changes during the cycle | 18:43 |
| fungi | Subject: Share Your Contributor/Maintainer Experience in the OpenStack Community | 18:43 |
| fungi | anyone who has disabled deliveries from emma to their addresses (via unsubscribe link or similar) probably didn't receive it | 18:44 |
| fungi | i honestly don't remember if i received a copy either, fwiw | 18:44 |
| JayF | I did not. | 18:45 |
| JayF | (receive a copy) | 18:45 |
| fungi | would have been sent around the time of the release, on april 1 | 18:46 |
| fungi | ~16:30 utc | 18:46 |
| fungi | sounds like | 18:47 |
| JayF | double checked, I don't have it | 18:57 |
| fungi | well, regardless, i'll also be sending a reminder to openstack-discuss on thursday anyway, i've already set myself a reminder for that | 18:58 |
| mnasiadka | I did get it | 19:30 |
| mnasiadka | So it exists :) | 19:30 |
| fungi | we're getting the staff who manage the emma account to look into the missing examples to see if there's any trend | 19:31 |
| JayF | fungi: I'm hosted on Microsoft 365 if that's a valuble data point | 19:34 |
| fungi | JayF: the log from emma showed that your address had opted out of communications | 19:36 |
| fungi | sean-k-mooney's reported a delivery failure, sounds like | 19:37 |
| JayF | It's nice, but def. nonstandard, that they are doing cross-account opt outs | 19:39 |
| JayF | you're going to miss a *lot* of people that way | 19:39 |
| fungi | i expect it's a usa can-spam compliance effort | 19:39 |
| JayF | That's not required by CAN-SPAM :) | 19:40 |
| JayF | but either way, I think it's a major downside of using a proprietary spam system to send out email notifications to contributors | 19:40 |
| fungi | any more than "cookie banners" are required by gdpr, but doesn't stop a ton of services from implementing them anyway due to overzealous lawyers | 19:40 |
| JayF | I am kinda shocked we are using an email marketing product to send out important contributor information. | 19:41 |
| fungi | bulk communications get delegated to the marketing team | 19:41 |
| fungi | so they use marketing tools | 19:41 |
| clarkb | I mean I'm pretty sure my email account can't send email to that many people without my provider getting annoyed. Fungi self hosts and might be able to do it at risk fo getting further banned (though I think he halready struggles to deliver mail?) | 19:41 |
| clarkb | its a tough problem to solve. And one we backfill with the use of mailing lists which we'll do here as well | 19:42 |
| fungi | yeah a lot of the mass mail hosting providers reject messages from me because i'm not a mass mail hosting provider | 19:42 |
| JayF | I think it is a tough problem to solve; I don't disagree. "Contributors who opt out of some quantity of marketing email can't get comms from OIF" seems to be a bit of a bad tradeoff though. | 19:43 |
| fungi | the fun thing is that system is also used for ballot notifications for the openinfra governing board individual director election too | 19:44 |
| JayF | hey I figured out why I never get my election notification as the GR-voting silver rep | 19:44 |
| fungi | (there are no silver member seats, fwiw) | 19:45 |
| fungi | gold member maybe? | 19:45 |
| JayF | ah, I get to vote whether I'm the rep for GR silver membership or not | 19:45 |
| JayF | because it's individual | 19:46 |
| fungi | right | 19:46 |
| JayF | I forget the details of this, good thing there's a reminder email... :| lol | 19:46 |
| fungi | hah | 19:46 |
| clarkb | I guess in my mind sending targetted email to people we can send email to then also sending notifications to the mailing list gives us broad coverage and is pragmatic. I've been trying to reiterate this when related issues come up over the last ~week, but I feel like there is a large under appreciation for how spread thin like butter folks like fungi and I are. We can only do so | 19:46 |
| clarkb | much and making pragmatic decisions like this is the end result when we're unwilling to investin additional help | 19:46 |
| clarkb | did anyone notice we were working on Sunday? Its hard to tell sometimes | 19:49 |
| fungi | if we did it right, people only noticed the announcements! | 19:49 |
| JayF | clarkb: as someone who has known you and fungi at this point for over a decade; I personally care. From a foundational perspective, employees needing to work >40 hours, and after hours with regularity, is a sign of mismanagement. I think you all being spread thin is a major concern, but that shouldn't prevent being concerned about the results that happen down the line. It isn't an implication of you or fungi; but instead org-level | 19:51 |
| JayF | clarkb: so please take this commentary from the perspective of someone dismayed that the foundation is cutting these corners, not as someone trying to push you or fungi to perform additional heroics | 19:51 |
| clarkb | right but from where I'm sitting the feedback here is going to fungi and I and indicated as a failing on opur part | 19:51 |
| clarkb | from my perspective the feedback should be to the member orgs that we're drwning as a community and I haven't seen anyone doing that | 19:52 |
| JayF | the feedback is going in the TC channel where I'd hope gouthamr and others here would be invested in making sure we're able to comms better | 19:52 |
| JayF | and I represent a company whose contribution to the community is outsized considering our use case, so please consider that in the perspective too | 19:52 |
| clarkb | note this isn't the only place we've been getting digrunted feedback for actions we've had to take | 19:52 |
| clarkb | and it is often directed to us "you should" etc | 19:53 |
| fungi | i agree it would be great if we had a lot more volunteers to do these things, or the openinfra governing board recognized value in increasing the staff budget to bring on more people | 19:53 |
| clarkb | and yes we probably should in many cases but again I can only do so much | 19:53 |
| JayF | FWIW, I don't ever think the solution in any community is "$individual doing better". They are all organisation size-and-shaped problems, and there's no amount of personal heroism that can fix that. | 19:54 |
| fungi | and to be clear, "just use ai" isn't a solution to this problem, at least not at the moment ;) | 19:54 |
| JayF | "We have 432 problems!" "Fix them with AI!" "We have 5243 problems!" | 19:55 |
| JayF | :D | 19:55 |
| fungi | precisely | 19:55 |
| JayF | if anything; I'd argue AI means we need more human investment in the coordination areas | 19:56 |
| JayF | to keep the rails greased as code output may start increasing | 19:56 |
| fungi | may start? | 19:56 |
| JayF | fungi: just trying to make statements that are hard to disagree with :D | 19:56 |
| fungi | granted, i don't know that the increase in openstack contributions over the past two cycles is a result of people using llms, we did also have a (less significant) increase in contributor count as well as obvious increase in general user interest | 19:58 |
| JayF | Ironic landed more features this cycle through use of LLM coding tools. There's zero question in my mind around that. | 19:58 |
| fungi | cool, i mean it doesn't surprise me, i just don't have that detail of insight into the raw contributor and merged change stats | 20:06 |
| JayF | I review somewhere in the ballpark of 75%+ of everything in ironic, commit stats show a jump in overall commits but that comment is eye-tested primarily | 20:07 |
| sean-k-mooney | fungi: well i dont know ifthere was a delivery failure or not but i didnt recive it | 20:08 |
| fungi | sean-k-mooney: i wouldn't be surprised if rh e-mail was rejecting messages from the emma service, but i expect the marketing folks will be digging into that. just wanted to relay that they confirmed they could see it didn't reach you | 20:09 |
| sean-k-mooney | so our is gmail with some addtional spam filter thing | 20:11 |
| sean-k-mooney | it begins with m | 20:11 |
| fungi | right, i know rh was using a third-party spam filtering frontend mx relaying to gmail' | 20:11 |
| fungi | dns says "mimecast" is the name you're looking for | 20:12 |
| sean-k-mooney | yes mimecast | 20:13 |
| sean-k-mooney | which we dont actully have access to to configure | 20:13 |
| fungi | but i don't have enough info to know whether it was rejected at that layer anyway | 20:13 |
| sean-k-mooney | ya no wories | 20:14 |
| sean-k-mooney | the mailing list while wider then you may want is still proably the best way to distirbute it | 20:14 |
| sean-k-mooney | i know its not a 1:1 overlap betwen the list subs adn the gerrit users | 20:15 |
| sean-k-mooney | but between teh two you proably can reach most folks that might respond | 20:15 |
| gouthamr | clarkb: agree with using the ML as backfill for this, glad fungi's planning to refresh this soon... i'd argue we don't benefit from directed emails for this sort of thing.. if this was in the ML, it can be referenced and amplified by community folks all over | 20:15 |
| sean-k-mooney | if folks read the tc metting summareis i gess they will see it too | 20:16 |
| * gouthamr notes sean-k-mooney's sentiment's the same | 20:19 | |
| fungi | yeah, i don't want to spam the ml and thursday seems optimal for getting noticed but also still being fresh in everyone's minds going into the ptg next week | 20:20 |
| gouthamr | board ballots using this system is detrimental to our election process :( because one's OIF individual membership depends on their (in)action.. | 20:20 |
| gouthamr | but, no need to discuss that now i guess, it was suggested we look at this election criteria a bit deeply.. maybe we re-assemble the election wg for this | 20:22 |
| fungi | oh i was wrong about it being used for governing board elections, sorry | 20:22 |
| gouthamr | oh, phew | 20:23 |
| fungi | those use sendgrid not emma | 20:23 |
| fungi | i confused the two | 20:23 |
| fungi | granted, sendgrid has its own similar problems | 20:23 |
| gouthamr | ack | 20:23 |
| fungi | anyway, the reason emma ended up used for the contributor/maintainer survey e-mail is that it's currently tied to other announcements the foundation marketing team sends out for release day, so it was easier to let them manage all of that | 20:25 |
| clarkb | but also with the new election system you don't need email for it to work | 20:35 |
| clarkb | (email is still probably a good idea to notify people though) | 20:35 |
| clarkb | iirc you just need to login to your lfx profiel and any ballots should be there? | 20:35 |
| TheJulia | That is functionally correct | 20:36 |
| TheJulia | you login, its on the lfx dashboard | 20:37 |
| TheJulia | clarkb, Agree, email is good for notifications/reminders, but to be the singular mechanism is just error prone in the age of email becoming a communication commodity | 20:39 |
Generated by irclog2html.py 4.1.0 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!