| opendevreview | Goutham Pacha Ravi proposed openstack/election master: Add candidature directories for 2026.2 https://review.opendev.org/c/openstack/election/+/974803 | 05:06 |
|---|---|---|
| opendevreview | Elod Illes proposed openstack/openstack-manuals master: [www] Set Victoria, Wallaby, and Xena state as EOL https://review.opendev.org/c/openstack/openstack-manuals/+/974816 | 09:57 |
| gouthamr | tc-members: a gentle reminder that our weekly meeting will be hosted here in ~50 minutes | 16:09 |
| gouthamr | #startmeeting tc | 17:00 |
| opendevmeet | Meeting started Tue Jan 27 17:00:24 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:00 |
| gouthamr | Today's meeting agenda can be found at https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee | 17:00 |
| gouthamr | #topic Roll Call | 17:00 |
| gtema | o/ | 17:00 |
| frickler | \o | 17:01 |
| gouthamr | courtesy ping: noonedeadpunk, spotz[m], cardoe, mnasiadka, bauzas | 17:02 |
| bauzas | o/ | 17:02 |
| cardoe | o/ | 17:02 |
| cardoe | Sorry. | 17:02 |
| gouthamr | noted absence: t o n y b | 17:02 |
| gouthamr | alright, lets get started.. | 17:05 |
| mnasiadka | o/ | 17:05 |
| gouthamr | #topic Last Week's AIs | 17:05 |
| gouthamr | ty for running the meeting last week, mnasiadka! | 17:05 |
| mnasiadka | np | 17:05 |
| noonedeadpunk | oops | 17:06 |
| noonedeadpunk | o/ | 17:06 |
| gouthamr | we took one regarding the uWSGI replacement email | 17:07 |
| gouthamr | ty noonedeadpunk for tackling this | 17:08 |
| gouthamr | Propose a Community Goal for MariaDB/MySQL Character Set support | 17:08 |
| gouthamr | this one was you as well, noonedeadpunk ^ | 17:08 |
| gouthamr | any update regarding this? | 17:08 |
| noonedeadpunk | unfortunatelly, not :( | 17:08 |
| noonedeadpunk | let me try to prio this one | 17:08 |
| noonedeadpunk | eventually I realized it's not a realistic goal for 2026.1 anyway, so I kinda postponed it a bit... | 17:09 |
| noonedeadpunk | but probably we should just roll it out for review, and hopefully by 2026.2 we get somewhere then | 17:09 |
| gouthamr | makes sense | 17:09 |
| noonedeadpunk | s/we/I/ | 17:09 |
| gouthamr | very early for this, but, mnasiadka said that he'd not be available on Feb 17th | 17:10 |
| gouthamr | can anyone run that meeting in his stead? | 17:11 |
| noonedeadpunk | I have no idea about my availability in February | 17:11 |
| mnasiadka | Yes, I’m off from this Friday to 26th of Feb | 17:11 |
| gouthamr | ^ good to know, | 17:11 |
| noonedeadpunk | I will be off for a week somewhere in Feb, but don't know when exactly | 17:12 |
| gouthamr | okay, i'll poll closer to the day | 17:12 |
| gouthamr | the last AI i saw was that we need some attention on open governance patches | 17:12 |
| gouthamr | this is still needed, we have only been merging the ones that don't need a formal-vote | 17:12 |
| gouthamr | #link https://review.opendev.org/q/status:open+repo:openstack/governance | 17:13 |
| gouthamr | that's all the AIs i saw, was anyone working on anything else? | 17:13 |
| gouthamr | #topic 2026.2 Elections | 17:15 |
| gouthamr | ianychoi and slaweq continue to be our election officials | 17:15 |
| gouthamr | and tonyb is teh TC liaison | 17:16 |
| gouthamr | last week, they posted up the dates for teh upcoming elections: https://governance.openstack.org/election/ | 17:16 |
| gouthamr | #link https://governance.openstack.org/election/ (2026.2 Elections) | 17:16 |
| bauzas | ack | 17:16 |
| gouthamr | the Nominations period begins soon, it runs between Feb 04, 2026 23:45 UTC and Feb 18, 2026 23:45 UTC | 17:17 |
| mnasiadka | oh boy, that means I need to submit my election before vacation - ty for reminding gouthamr | 17:17 |
| gouthamr | ++ | 17:17 |
| gouthamr | i wanted to bring this up to mention that we'd be kinda short staffed during this nomination period | 17:18 |
| gouthamr | we'll either have ianychoi or slaweq but not both throughout this nomination period | 17:18 |
| gouthamr | so, they asked if any of the TC members could attest nominations with a +1 | 17:18 |
| gouthamr | they'd consider that and single-core merge the nomination patches | 17:19 |
| fungi | ideally would be tc members who aren't running for reelection or for ptl | 17:19 |
| gouthamr | yes ^ | 17:20 |
| gouthamr | that'd mean cardoe frickler bauzas and tonyb | 17:20 |
| mnasiadka | Just wanted to write that :) | 17:20 |
| cardoe | heh | 17:21 |
| cardoe | I'll do so. | 17:21 |
| gouthamr | ty | 17:21 |
| gouthamr | if anyone's looking to make early nominations, please follow up with this change: https://review.opendev.org/c/openstack/election/+/974803 | 17:22 |
| gouthamr | alright that's all i had for $topic | 17:22 |
| gouthamr | #topic TC Tracker, PTG Follow up | 17:23 |
| gouthamr | #link https://etherpad.opendev.org/p/tc-2026.1-tracker (Technical Committee activity tracker - 2026.1) | 17:23 |
| gouthamr | #link https://etherpad.opendev.org/p/oct2025-ptg-os-tc-summary | 17:23 |
| gouthamr | #link https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack.org/message/RX3MZE33GEDV5JDHORZKRUKVDP47UMLJ/ (OS/PTG Summary) | 17:23 |
| gouthamr | i've been strapped for time on the vision doc, but, was curious to work on it alongside the call to action that fungi posted: | 17:25 |
| gouthamr | #link https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack.org/thread/MPLKSGH2IKULPOA3XIYROV3WKB2DF43X/ ([dev][ops][tc] Taking OpenStack to the Next Level in 2026) | 17:25 |
| fungi | that also got presented during the openinfra governing board meeting a couple of hours ago | 17:25 |
| fungi | feedback is still most welcome of course, just noting that the urgency to get it before the board meeting is now past | 17:26 |
| gouthamr | oh, i wasn't there.. did you have a slide deck or notes that you could share? | 17:27 |
| fungi | it wasn't anything beyond what's in the e-mail you linked | 17:28 |
| gouthamr | i can see that foundation staff will be leading a number of initiatives, some of these are familiar to us having discussed this in past PTGs, meetings and other avenues | 17:28 |
| fungi | there was a slide in the foundation staff presentation deck, but it was essentially the same points | 17:28 |
| gouthamr | i want to see the intersection of the TC's efforts for this. For one, i think we need to press the accelerator on cleaning up the SIGs | 17:29 |
| opendevreview | Michal Nasiadka proposed openstack/election master: kolla: Add Michal Nasiadka PTL candidacy https://review.opendev.org/c/openstack/election/+/974902 | 17:29 |
| gouthamr | and rewrite the technical vision as we discussed | 17:29 |
| gouthamr | i'd like to know how/where we can help with the other efforts | 17:30 |
| gouthamr | for one, when you have more to share on the User Survey, do share... | 17:31 |
| fungi | will do | 17:31 |
| opendevreview | Michal Nasiadka proposed openstack/election master: TC: Add Michal Nasiadka candidacy https://review.opendev.org/c/openstack/election/+/974904 | 17:33 |
| gouthamr | thank you.. a suggestion would be to create a wiki page perhaps? or a section on teh website to share all the different tasks you folks are doing | 17:33 |
| fungi | i'll bring that up with the other community managers, and figure out how we might get our efforts better publicized | 17:34 |
| gouthamr | ++ | 17:34 |
| bauzas | honestly I was there where the first vision began, but I still wonder whether it was useful | 17:34 |
| gouthamr | the part i found useful was that project teams undertook an exercise to reflect on the vision and it helped us shape some of our attitudes and tasks | 17:36 |
| fungi | it did, at least partly, help us refocus the "what is openstack?" question | 17:37 |
| bauzas | hmmmm, maaaybe ? :-) | 17:37 |
| bauzas | the Big Tent disappeared now :)à | 17:37 |
| fungi | yeah, that vision was, to some extent, an answer to the emerging concerns around all the new unrelated projects we'd added to openstack | 17:38 |
| bauzas | yup now this is different, but OK, let's try to discuss it if we want | 17:39 |
| clarkb | and it came back up in the context of replacing projects with rewrites, using different testing frameworks, etc | 17:39 |
| clarkb | the idea being lets make sure our definition of openstack is currently accurate then measure these big questions against that | 17:40 |
| gouthamr | agree | 17:41 |
| gouthamr | alright, looking at the tracker, and ongoing work | 17:42 |
| gouthamr | we'll have a few housekeeping tasks in the next few weeks | 17:42 |
| gouthamr | we'll need to refresh the DPL liaisons across teams | 17:42 |
| gouthamr | we'll need to check on the inactive projects: https://governance.openstack.org/tc/reference/emerging-technology-and-inactive-projects.html#current-inactive-projects | 17:43 |
| gouthamr | couple of these that i've seen no "revival" sorta activity | 17:45 |
| gouthamr | this means that they'll head to retirement in the Hibiscus cycle | 17:46 |
| gouthamr | per the timeline on that page ^ | 17:46 |
| mnasiadka | I think we haven’t properly retired Monasca yet? | 17:47 |
| gouthamr | yes, not entirely: | 17:48 |
| gouthamr | #link https://review.opendev.org/q/hashtag:%22monasca-retirement%22+status:open | 17:48 |
| gouthamr | frickler noted that the requirements team has been slow to respond to reviews | 17:48 |
| mnasiadka | So that’s only requirements | 17:48 |
| gouthamr | prometheanfire tonyb perhaps you can help merge these patches? ^ | 17:48 |
| gouthamr | mnasiadka: what else are you thinking? | 17:48 |
| frickler | maybe we should add the reqs project also to the inactive list ;-/ | 17:48 |
| gouthamr | #link https://review.opendev.org/q/hashtag:%22monasca-retirement%22+(status:open%20OR%20status:merged) | 17:49 |
| gouthamr | ^ that's the list of patches that've merged | 17:49 |
| mnasiadka | frickler: that would be interesting | 17:49 |
| mnasiadka | Monasca repos also have some open patches from what I see (in Gerrit) | 17:50 |
| gouthamr | ah, i missed those | 17:50 |
| clarkb | the release team should have permissions to abandon those and I think also to merge the requirements changes | 17:51 |
| clarkb | (via the openstack meta config acl list) | 17:51 |
| clarkb | TC too maybe? | 17:51 |
| gouthamr | https://review.opendev.org/q/project:%5E.*monasca.*+status:open | 17:51 |
| gouthamr | 176 changes o.O | 17:51 |
| gouthamr | yes, the TC does | 17:51 |
| gouthamr | we've got a script somewhere that we can run and abandon these? | 17:52 |
| clarkb | yes I think the requirements eol tagging script does it | 17:52 |
| clarkb | *releases branch eol tagging script | 17:52 |
| frickler | https://opendev.org/openstack/releases/src/branch/master/tools/abandon_patches_on_branch.sh | 17:52 |
| frickler | might need amending the wording of the msg for that purpose | 17:53 |
| gouthamr | neat, ack | 17:53 |
| gouthamr | #topic Open Discussion | 17:55 |
| * gouthamr will try and get aprice in a meeting regarding the foundation marketing themes | 17:57 | |
| fungi | don't forget to register for the ptg! | 17:57 |
| fungi | #link https://ptg.openinfra.org/ PTG April 20-24, 2026 | 17:58 |
| gouthamr | +1 | 17:59 |
| gouthamr | alright, lets wrap this up.. | 17:59 |
| gouthamr | thank you all for participating | 17:59 |
| gouthamr | #endmeeting | 17:59 |
| opendevmeet | Meeting ended Tue Jan 27 17:59:55 2026 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 17:59 |
| opendevmeet | Minutes: https://meetings.opendev.org/meetings/tc/2026/tc.2026-01-27-17.00.html | 17:59 |
| opendevmeet | Minutes (text): https://meetings.opendev.org/meetings/tc/2026/tc.2026-01-27-17.00.txt | 17:59 |
| opendevmeet | Log: https://meetings.opendev.org/meetings/tc/2026/tc.2026-01-27-17.00.log.html | 17:59 |
| mnasiadka | fungi: it’s funny that the registration forces you to fill out company name, “None” still works, but well | 18:02 |
| fungi | mnasiadka: yeah, i think it may be something baked into that event management platform | 18:03 |
| fungi | i'll mention it to the staff who are more familiar with it, in case it's something they have the ability to fix | 18:04 |
| sean-k-mooney | the ptl/dpl nominiation period isnt for a few weeks right? | 18:05 |
| gouthamr | sean-k-mooney: begins on Feb 4th | 18:06 |
| gouthamr | https://governance.openstack.org/election/ | 18:06 |
| sean-k-mooney | ack | 18:06 |
| clarkb | which is ~1 week away | 18:06 |
| frickler | will be a close call to get the DPL reset done before that | 18:06 |
| sean-k-mooney | ill bring it up for watcher in this weeks irc call. we will likely then propose the reset and reafirmation patch on thrusday if no objection | 18:07 |
| sean-k-mooney | im currently assumign we wont end up chanign any of the liasons this cycle but we can dicusss that on the review patches | 18:08 |
| gouthamr | ++ ty for checking sean-k-mooney | 18:08 |
| sean-k-mooney | ill note that for those that observe lunar newywar the nomitation period is nto great | 18:09 |
| gouthamr | Yes :( | 18:09 |
| gouthamr | i think we'll have a hard time with several PTLs that might be away starting ~Feb 16 | 18:10 |
| fungi | it comes up every year. we'd need to shift the release schedule or when we hold elections relative to releases in order to fix it longer term | 18:11 |
| fungi | but both options are theoretically possible | 18:11 |
| gouthamr | shifting elections is possible, we'd have to ensure the nomination window opens as soon as the new year begins or something.. but given how long the election cycle is, we'd either have people miss the nominations or the voting period | 18:12 |
| sean-k-mooney | im not nessiarly saying we shoudl just noting it | 18:13 |
| sean-k-mooney | when did that page get a count down timer. did i just miss that forever or is it new? | 18:13 |
| clarkb | there are a lot of conflicts through the year too. So moving things doesn't necessarily make things better just shifts it around | 18:14 |
| sean-k-mooney | what critira are we applying for inactive project and revival efforts? | 18:14 |
| JayF | Is there a way to pre-indicate my +1 to DPL? I'm likely to be out for medical reasons during the refresh window | 18:15 |
| gouthamr | ^ this would count JayF | 18:16 |
| cardoe | I'll actually be on PTO during the nomination period as well. | 18:16 |
| gouthamr | ^ ack | 18:16 |
| sean-k-mooney | JayF: you can just create teh 2 patches to the repo to reset adn opt in again | 18:17 |
| sean-k-mooney | there woudl only really be a conflcit if some one decieed to run for ptl at teh same time | 18:17 |
| sean-k-mooney | in which case i actully have no idea what happens | 18:18 |
| JayF | if someone tries to run for ironic PTL that isn't a current DPL they would be unlikely to be taken as a leader for the project regardless of policy | 18:18 |
| fungi | in theory, nobody could run for ptl of a dpl team without the team deciding to move off the dpl model | 18:18 |
| gouthamr | for now, the nomination folder hasn't been created for any team that had the DPL model in 2026.1 | 18:18 |
| gouthamr | https://review.opendev.org/c/openstack/election/+/974803 | 18:18 |
| sean-k-mooney | fungi: yes and no orgianly we did nto revert back to the ptl model but htat was chagned | 18:18 |
| sean-k-mooney | this is part of why i didnt want us to i proceed with the chagne that reqruied opt in each cycyle | 18:19 |
| sean-k-mooney | gouthamr: ack although you could just create that with the candiate patch | 18:20 |
| JayF | Having folks check in once a cycle that they are still around and interested in leadership isn't a bad thing. Our method for doing it is a bit onerous though :) | 18:20 |
| gouthamr | you could, but that’s something the election officials would watch for | 18:21 |
| JayF | I'd rather be annoyed as an active Ironic DPL than for us to let a team stagnate with an absentee DPL team | 18:21 |
| sean-k-mooney | if a porject wanted to adopt the dpl model for next cycle it would need to do so before the nomination peroid correct? | 18:21 |
| fungi | yeah, in theory there could be a different re-opt-in mechanism for liaisons. resetting to ptl if there are neither enough liaison volunteers nor any candidate for ptl is fairly pointless, as the team has no leadership at that point either way | 18:21 |
| gmaan | TC should be proposing the DPL reset by default and projects can -1 that to keep the DPL model. that is the easiest and shortest way to continue unless there is change in DPL liaisons | 18:24 |
| gmaan | if it is too frequent then reset can be done once in a two cycle (yearly) | 18:25 |
| fungi | the reason it came up is that we have one week to get that done before the ptl nomination window, and some liaisons might be on vacation right now | 18:25 |
| fungi | (the reason it came up just now, i mean) | 18:26 |
| gmaan | yeah, I think I faced the same when I as TC was supposed to propose DPL reset much in advance to election. | 18:26 |
| gmaan | I think we made some notes on that to avoid the same situation | 18:26 |
| sean-k-mooney | ya that and im in the process of reachign out to the cyborg ptl to understand there intetion for next cycle. i was going to suggest moving cyborg to the dpl model and have volenteered to help with some of the relase liason duties this and next cycle given the over lack of mantaince that is currently happenign in the cyborg project | 18:28 |
| gmaan | of if it is very late then no harm to skip the reset this cycle and just check if any DPL team is inactive or so | 18:28 |
| gmaan | sean-k-mooney: ++ good point but even they respond late you can propose PTL->DPL any time right after election | 18:29 |
| gmaan | it should be done once in a cycle but can be proposed anytime in cycle | 18:29 |
| sean-k-mooney | ack | 18:30 |
| sean-k-mooney | currently cyborgs gate is blocked because fo the oslo.db release but i have a ptch up to adrfess that i bleive | 18:30 |
| sean-k-mooney | i need to do some testing locally | 18:31 |
| sean-k-mooney | but thre are a number of other issue in term of testing runtimes and over all maintaince | 18:31 |
| gmaan | yeah, that's true. | 18:31 |
| sean-k-mooney | that why i asked about what do we consier an inactive project | 18:32 |
| gmaan | well, I proposed it inactive I think 2 cycle back or last cycle then we got response from PTL so abandon that proposal | 18:33 |
| gmaan | but agree that just raising hand for PTL is not enough and gate status is more important | 18:34 |
| sean-k-mooney | yes but there have only been 2 patches merged this cycle effectivly and many of even the both patches have not been merged | 18:34 |
| sean-k-mooney | so its still effectivly an inactive core team | 18:34 |
| fungi | and responsiveness to private security bugs | 18:34 |
| gmaan | moving to DPL and shared maintenance/leadership is good idea though | 18:34 |
| gmaan | fungi: ++ yeah | 18:34 |
| sean-k-mooney | i was orginally goign to wait a bit and start a mailign thread but i tought the nominationls were after FF | 18:35 |
| gmaan | sean-k-mooney: agree, may be good to start your proposal (you volunteer to help in DPL model) on ML and if current PTL respond | 18:35 |
| fungi | at least now that we have tc liaisons to the vmt, there are tc members getting escalated to for those specific cases, so someone on the tc to lobby for inactive status | 18:35 |
| sean-k-mooney | gmaan: im not sure if they are back form pto but i emailed them this afternoon. if i dont hear back by the end of the week ill start a thread on the public mailing list | 18:37 |
| sean-k-mooney | one of the thing i noticed is the current ptl does not ahve access to the cyborg launch pad group or i think the release/stable gerrit group | 18:37 |
| gmaan | yeah and it it goes leaderless then it is good indicator to reiterate the leadership model and maintenance core list also | 18:37 |
| gmaan | they did not ask I think but those access permission are doable quickly | 18:38 |
| sean-k-mooney | so i have a list of mantiance/paperwork tihngs that need to get adressed adn was plannign to start the converstation on how to make progress on it next week | 18:38 |
| sean-k-mooney | cyborg is fortually owne by the openstack admins group i bleive so ya | 18:39 |
| sean-k-mooney | we dont have to go chasing anyone for the lauchpad permissions in this case | 18:39 |
| fungi | thinking about inactivity criteria, we essentially already identified problem domains by defining dpl liaison roles. each one corresponds to some set of people elsewhere in openstack who will end up shouldering additional burden if the project isn't being actively maintained | 18:39 |
| sean-k-mooney | well https://launchpad.net/openstack-cyborg is but not https://launchpad.net/~cyborg-team | 18:40 |
| gmaan | not openstack-admin but OpenStack Cyborg Team | 18:40 |
| sean-k-mooney | right and unfortinly openstack cyborg team does not have the openstack admins as a maintainer | 18:41 |
| sean-k-mooney | https://launchpad.net/~cyborg-team/+members#active | 18:41 |
| gmaan | yeah, 'OpenStack Administrators' should be owner for that team | 18:41 |
| sean-k-mooney | so https://launchpad.net/~zhipengh512 is the only admin of that team | 18:42 |
| gmaan | yeah | 18:42 |
| sean-k-mooney | which effectivly mean they are the only person that can mange teh membership or configure the lauchpad project | 18:42 |
| fungi | if they add ~openstack-admins to the team and set it to administrator role, then we can take it from there | 18:42 |
| gmaan | yeah | 18:42 |
| sean-k-mooney | the problem is i think they may be inactive but we woudl need to confirm that | 18:43 |
| sean-k-mooney | last coment on gerrit was 3 years ago | 18:44 |
| sean-k-mooney | cybrog has not created any serise in lauchpad since zed either which was one of the thign on my list | 18:44 |
| sean-k-mooney | the bug triage team is also cofnigured to that restricted team so we cant actully tirage new bug properly either | 18:45 |
| fungi | also the project description on lp says bug tracking uses storyboard, even though the team moved from sb to lp 5 years ago with https://review.opendev.org/c/openstack/project-config/+/787306 | 18:45 |
| gmaan | Yeah, I also checked and they are not active any more at least from gerrit activity. maybe current PTL knows them and get it done? | 18:46 |
| sean-k-mooney | perhaps | 18:47 |
| sean-k-mooney | li liu (the current ptl) is invoved in cyborg purly in there personal time | 18:47 |
| sean-k-mooney | while i can reach out to them via other means since they happen to be employed at ibm i dont know if they have a personal relationship with Zhipeng and or have a beter way to reach out | 18:48 |
| sean-k-mooney | anyway ill let ye knwo fi i hear back and ill likely start a mail thread on the general topic of cyborg maintance next week | 18:49 |
| gmaan | last option can be to ask LP maintainers to tranfer team ownership. If i remember correctly we did that in past. I think gouthamr did for almost for all such cases. | 18:51 |
| fungi | worst case, we *can* reach out to the lp admins to get control reassigned, but would rather reserve that for the last possible fallback because we don't want to pester them unless we've exhausted all other options first | 18:51 |
| gmaan | yeah | 18:51 |
| sean-k-mooney | i guess in the meain time i can also email zhieng about adding https://launchpad.net/~openstack-admins as an admin to https://launchpad.net/~cyborg-team and see if i get a responce | 18:51 |
| gmaan | ++ | 18:52 |
| fungi | i'm happy to take care of flipping the remaining switches in lp once that's in place | 18:52 |
| sean-k-mooney | li liu responeded and said to proceed with starting a mailing list thread so ill work on that tomrrow. | 19:10 |
| opendevreview | Goutham Pacha Ravi proposed openstack/governance master: Reset the DPL model for watcher project https://review.opendev.org/c/openstack/governance/+/974926 | 19:20 |
| opendevreview | Goutham Pacha Ravi proposed openstack/governance master: Reset the DPL model for requirements project https://review.opendev.org/c/openstack/governance/+/974927 | 19:22 |
| opendevreview | Goutham Pacha Ravi proposed openstack/governance master: Reset the DPL model for release mgmt project https://review.opendev.org/c/openstack/governance/+/974928 | 19:23 |
| opendevreview | Goutham Pacha Ravi proposed openstack/governance master: Reset the DPL model for Oslo project https://review.opendev.org/c/openstack/governance/+/974929 | 19:23 |
| opendevreview | Goutham Pacha Ravi proposed openstack/governance master: Reset the DPL model for Ironic project https://review.opendev.org/c/openstack/governance/+/974930 | 19:24 |
| opendevreview | Goutham Pacha Ravi proposed openstack/governance master: Reset the DPL model for Freezer project https://review.opendev.org/c/openstack/governance/+/974931 | 19:24 |
| gouthamr | thanks for chasing that down, sean-k-mooney | 19:32 |
| gouthamr | and the reset thingy, i'm still pretty green behind the ears on stuff, but, i suspect most teams of the teams above are active, and would like to retain the DPL model.. ofcourse the tragedy of the commons affects the critical non-service project teams (requirements, oslo) | 19:34 |
| opendevreview | Merged openstack/openstack-manuals master: [www] Set Victoria, Wallaby, and Xena state as EOL https://review.opendev.org/c/openstack/openstack-manuals/+/974816 | 22:27 |
| cardoe | We recently merged https://review.opendev.org/c/openstack/governance/+/971178 but we haven't updated the permissions on the repo in gerrit. | 22:39 |
| gouthamr | gtema should be able to fix that | 22:40 |
| gouthamr | https://review.opendev.org/admin/groups/q/filter:keystoneauth | 22:40 |
| gouthamr | or if they want to get rid of the group altogether and use the openstacksdk ones, this file needs an update: https://github.com/openstack/project-config/blob/master/gerrit/acls/openstack/keystoneauth.config | 22:41 |
Generated by irclog2html.py 4.0.0 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!