Tuesday, 2024-03-26

opendevreviewSlawek Kaplonski proposed openstack/project-team-guide master: Add info about recheck comments with "unrelated failure" info  https://review.opendev.org/c/openstack/project-team-guide/+/91406510:20
opendevreviewDr. Jens Harbott proposed openstack/governance master: Appoint Jens Harbott as Skyline PTL  https://review.opendev.org/c/openstack/governance/+/91424813:51
fricklertc-members: I started making an etherpad for leaderless projects mostly copied from the previous cycle https://etherpad.opendev.org/p/2024.2-leaderless , with ^^ I also offer to fill one of the spots13:53
jamespagethanks frickler :)14:06
fricklerfreyes_: if you still want to get appointed as Charms PTL, you should submit a patch like the above14:12
freyes_frickler, ack, thanks14:12
opendevreviewFelipe Reyes proposed openstack/governance master: Appoint Felipe Reyes as OpenStack Charms PTL  https://review.opendev.org/c/openstack/governance/+/91425414:28
JayFfrickler: looking at that list, I suspect the answer for some of those projects will be retirement :/15:41
TheJuliaI would strongly encourage such if people are not clammoring to step up and do the needful. 15:45
JayFI think over half the list is already inactive, although I haven't explicitly cross checked, just going from memory.15:47
TheJuliaAnd I'd also note the desire might be strong, but we should be talking about what problems are actually solved while looking at the actual usage and then make a determination if resources/time/risk justifies it, or not.15:48
dansmithwell, murano is already in that camp right?16:00
JayFYeah. 16:03
fricklerthere should be more, like the projects that will likely have a non-functional release this cycle, see the current discussion in #-release16:09
TheJuliaAt some point, wouldn't it make sense to just hold release of them? The show must go on for everything else seeing active maintainers/work16:19
bauzastc-members: the 5 of us RHers + rosmaita had a conversation. Eventually, it led to me being stepping down16:21
bauzasJayF: please then unabandon your change16:22
JayFbauzas: I know that is not pleasant for you personally, and I appreciate it a lot.16:22
JayFbauzas: Thanks for the sacrifice16:22
bauzasI'll be clear, I won't run for another election if the TC doesn't modify its charter16:23
bauzasbut that's no longer my problem16:23
JayFYou're welcome to comment on and participate in tc activities even if you won't have a vote; I agree it should be a priority to fix the charter to avoid this kinda issue in the future.16:24
JayFI should say that differently; you're not just welcome to; I think it'd be a nice thing if you did.16:24
bauzasI'm pretty done for now with engaging with the TC, but I just hope you'll understand16:25
JayFI completely understand16:25
dansmithit really sucks that stepping up for the TC is a personal decision, but the disqualification is an affiliation one.. it'd be one thing if redhat (and everyone else) was nominating people by quota or something16:27
dansmithbut the current situation makes it very expensive for the individual to put themselves out there only to be squashed like this16:27
TheJuliaPeople do so for the Board all the time, the difference is the conflict is resolved by the secretary of the board before the individual is seated.16:28
JayFIt's tough for sure. The affiliation limitation is about risk management and ensuring no appearance of impropriety for someone outside of our community looking in. Those are not topics that the TC often has as top line concerns :/ 16:28
JayFThe process leading (figuratively) into a brick wall certainly helped make this more painful, as TheJulia points out16:29
dansmiththe board is also different in that only some of the seats are elected right?16:30
TheJuliadansmith: 2/3rd of the seats are elected16:30
TheJuliadansmith: only 1/3rd is elected by individual members16:30
dansmithright16:30
TheJuliaAs a result with the tighter affiliation restriction of the board as a body, we've hit it a few times over the years.16:34
fungiright, but all seats together count toward the affiliation limit there16:34
fungiso if a company has a platinum seat, that's one fewer employee who can be elected by individual members16:34
JayFbauzas: I hate to ask more of you, but can you revise your vote https://review.opendev.org/c/openstack/governance/+/914024 here?16:34
TheJuliafungi: indeed16:35
gmannbauzas: very unfortunate and disappointed to see you step down, sorry for that. as you mentioned I already started the discussion for charter change on this, would like you to participate in that discussion in PTG https://etherpad.opendev.org/p/apr2024-ptg-os-tc#L4616:39
gmannI added Ping section there, feel free to add your name so that we remember to ping you once we schedule/start the discussion16:40
bauzasgmann: I'll probably need to be off the TC discussions a bit of time16:40
gmannhumm16:40
gmannfrickler: thanks for the leaderless project tracking. 16:41
gmannfor inactive projects, it seems 6 out of 11 leaderless projects are already marked Inactive in last cycle and seeing no leader in this cycle a clear indication to discuss about retiring them17:03
JayFtc-members: almost time for the meeting17:59
JayF#startmeeting tc18:00
opendevmeetMeeting started Tue Mar 26 18:00:17 2024 UTC and is due to finish in 60 minutes.  The chair is JayF. Information about MeetBot at http://wiki.debian.org/MeetBot.18:00
opendevmeetUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.18:00
opendevmeetThe meeting name has been set to 'tc'18:00
JayFWelcome 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.18:00
JayFToday's meeting agenda can be found at https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee.18:00
JayF#topic Roll Call18:00
JayFo/18:00
rosmaitao/18:00
frickler\o18:00
slaweqo/18:00
gmanno/18:00
gouthamro/18:00
jamespageo/18:01
dansmitho/18:01
JayF#info There are no absences noted in the TC agenda.18:01
JayFI'm going to give a couple more minutes for the remaining TC members to arrive.18:02
spotz[m]o/18:02
JayFGoing to move on with the rest of the agenda.18:04
JayFThere were no action items last TC meeting; going to hop over that agenda item18:04
JayF#topic Gate Health Check18:04
JayFThanks again to slaweq for the email to the list about rechecks, it's generating a lot of healthy discussion and visibility into gate issues.18:04
JayFAnything specific to note about the gate this week?18:04
dansmithnothing from me (because no data, unfortunately)18:05
* frickler hasn't seen much either18:05
JayFFair enough :)18:05
slaweqnothing from me18:05
JayF#topic Implementation of Unmaintained branch statuses18:05
gmannnothing specific from my side except setup for stable/2024.1 and master is going on so granade, devstack jobs will be testing the correct branches soon18:05
JayFack ty gmann 18:05
slaweqjust please review https://review.opendev.org/q/topic:%22rechecks-docs%22 when You will have few minutes18:06
JayF#undo18:06
opendevmeetRemoving item from minutes: #topic Implementation of Unmaintained branch statuses18:06
JayF#link https://review.opendev.org/q/topic:%22rechecks-docs%2218:06
JayFThanks :)18:06
JayF#topic Implementation of Unmaintained branch statuses18:06
slaweqsmall adition about rechecks reasons in dics18:06
gmannslaweq: +1 on adding it in zuul comment. good idea18:06
slaweqgmann it was actually Sean's idea18:07
fricklerwe merged some more unmaintained transition changes earlier, I'm deleting affected branches now18:07
gmannyeah, i saw thanks to sean too:)18:07
JayFthanks frickler, and I'll note I saw on releases.opendev.org this morning it is starting to look really nice18:07
JayFer, releases.openstack.org18:08
JayFAnything else on this topic?18:08
JayF#topic 2024.2 Dalmatian TC Election18:09
JayFAs all of us are aware, we were unable to execute election results due to affiliation policy issues.18:09
JayFI'd like to thank Red Hat employees, and Sylvain, for figuring this out internally so we can keep a diversely affiliated TC.18:10
JayF#link https://review.opendev.org/c/openstack/governance/+/91391218:10
jamespageseconded18:10
JayF#link https://review.opendev.org/c/openstack/governance/+/91402418:10
JayFThe first governance link is just for the minutes, noting that we have a -1 on the election results.18:10
JayFThe second one is a resolution, authored by me, documenting the adjudication of the election.18:10
JayFPlease do vote on 914024, the clock starts today so we can merge and seat the new TC just before next week's meeting.18:11
JayFAny comments or concerns for the meeting?18:11
rosmaitajust that we will probably face this issue again, so would be good to have discussions at the PTG18:12
gouthamrJayF: i want to note that it was a harrowing process for having to do this - like bauzas mentioned, we hope there's a codified process worked out for this.. and are determined to help achieve it. 18:12
noonedeadpunko/18:12
JayFAgreed, and that is a stellar segue into...18:12
JayF#topic TC vPTG 2024.218:12
gmann#link https://etherpad.opendev.org/p/apr2024-ptg-os-tc#L4618:13
JayF#link https://etherpad.opendev.org/p/apr2024-ptg-os-tc18:13
spotz[m]I think this is already on the PTG agenda if not we'd like some time to through out ideas and governance for the future18:13
gmannrosmaita: link for ^^ as you mention about the PTg discussion over this topic18:13
rosmaita\o/18:13
JayFIt's my intention to map topics to timeslots this afternoon/tomorrow, and send an email out to the list about it. If you have topics to present beyond what is already on the etherpad, please put them in -- even just a placeholder subject line -- for scheduling purposes.18:13
JayFAnything else about PTG or scheduling?18:15
slaweqI still need to  finish and propose analysis of the latest user survey. I plan to do it next week. I am not sure if you maybe wants to add something about it to the PTG agenda18:16
JayFI think it's wise to have a spot to talk about it separately18:16
JayFI'll put in a placeholder for you, thanks slaweq 18:16
slaweqthx18:16
JayF#topic Open Discussion18:16
JayFI have one item for this from me18:17
JayFI will not be here next week, completely OOO/PTO and away from computers as much as possible.18:17
JayFI would like to ask someone to take on ensuring 914024 is merged a week from today, as long as it's valid to merge, and coordinating the update of governance results as well.18:17
JayFAdditionally, just ensuring that gmann is still willing to chair the meeting next week as I will be away18:18
gmannsure, its video one right18:18
JayFIt is.18:19
clarkbI did a fair bit of work to clear out debian buster, opensuse leap 15.2, and centos 7 from nodepool and our mirrors. The next cleanup is ubuntu xenial though I don't think I'll have time to look into that until next week. This has opened up space for ubuntu noble mirroring and images if anyone is interested in pushing that along. First step is probably jobs to build and test the18:19
clarkbimage in diskimage builder. Then we add the mirror then image builds to nodepool.18:19
gmannok, I will chair. 18:19
rosmaitai can watch that patch18:19
rosmaitaonce it merges, i think my tc term will be over?18:19
JayFYes18:19
JayF#info JayF (chair) PTO next week18:19
rosmaitaworks for me if no one has any objection18:19
JayF#action gmann To chair TC meeting next week18:20
JayF#action rosmaita will merge 914024 if eligible and see to it new TC is seated before next TC meeting 18:20
JayFAny other items for open discussion?18:20
JayFLast call before I close the meeting18:21
rosmaitaquestion about the timing ... when can i merge 914024?  I guess at 0:00 UTC 2 April 2024?18:21
JayFIf we're doing it down to the second, I restored the patch at 9:23am PST. I would not object to it merging anytime on that Tuesday to make life simpler.18:22
gmannrosmaita: did not calculate time but "tox -e check-review-status" will surly give you the right answer for eligibility of merging 18:22
fungiwhich probably means tc election results announcement happening the day before release day, best case18:23
JayF++ I trust the script for everything(*) (there are some exceptions; this isn't one)18:23
gmannyeah, that is very helpful.18:24
JayFAnything else?18:24
rosmaitascript says "earliest: 2024-03-29 18:30:02"18:24
rosmaitaso everyone go over and vote as soon as the meeting is over, and we can merge it friday18:25
rosmaitaunless "earliest" means something else?18:26
JayFearliest means that, but this also means the script doesn't consider abandon/restore18:26
JayFwhich is convienient in this case18:26
rosmaita:D18:26
fricklerconvenient, but debatable?18:26
JayFIf I were landing it, I'd let any single TC member's objection push me to "7 days from when it was restored" which is that April 2, around 9:23a pst18:26
JayFfrickler: yeah, that's kinda what I'm getting at with ^18:27
frickleryes, after going through so many loops in order to do the right thing, this should be handled correctly, too, imo18:28
JayFrosmaita: so I'd suggest waiting until noonish eastern time a week from today18:28
dansmith#bikeshedding18:28
rosmaitaok, it was restored at 12:23PM EDT, so that will be the merge target18:29
JayFsounds good18:29
JayFthanks all18:29
JayF#endmeeting18:29
opendevmeetMeeting ended Tue Mar 26 18:29:28 2024 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)18:29
opendevmeetMinutes:        https://meetings.opendev.org/meetings/tc/2024/tc.2024-03-26-18.00.html18:29
opendevmeetMinutes (text): https://meetings.opendev.org/meetings/tc/2024/tc.2024-03-26-18.00.txt18:29
opendevmeetLog:            https://meetings.opendev.org/meetings/tc/2024/tc.2024-03-26-18.00.log.html18:29
spotz[m]+118:29
spotz[m]Thanks all18:29
slaweqo/18:30
JayFgmann: https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee#Next_Meeting has been updated for next meeting, I added an agenda item for electing a new TC chair, obviously that one gets wiped if we don't get the resolution passed :)18:50
gmannJayF: ack, thanks18:51
JayFI assume you still have moderator code and information for foundation zoom room as former chair?18:51
JayFIf not, I can forward your own email back to you ;) 18:51
gmannI think so but let me re-confirm18:51
gmannJayF: yes, I have that.18:52
JayFgood stuff, thanks for taking care of things in next weeks' meeting18:53
JayFgmann: Do you object to me scheduling your item around "project inactive state process" with my item "Raising the bar for activity", as they likely will have similar or interwoven results20:37
JayFI've done it that way for now, but we can make them adjacent instead of the same topic if later desired20:42
JayFtc-members: I've proposed some high-level topic<->time mappings here, https://etherpad.opendev.org/p/apr2024-ptg-os-tc -- I will likely email the list this schedule around this time tomorrow -- please let me know if you have conflicts or objections20:43
gmannJayF: scheduling them in near slot is ok but let's keep them a separate topic as we anyways need to amend the process for projects identified inactive after m-2 20:49
JayFgmann: I changed "Complete" to "Revise" to make that more clear, and moved that topic, as a separate item, to be grouped with the other "ongoing tc activites" items20:50
gmannJayF: sounds good. thanks20:50
fungii'm sure i'll join those sessions either way, but one thing we should touch on is that we have some forcing functions which have caused us to increasingly scrutinize release-managed projects and teams with a ptl model, but some similar inactivity could be flying under the radar in independent release projects and dpl led teams22:00
JayFfungi: good point, would you mind making it in the etherpad so it's not lost before the ptg?22:05
fungisure, done22:09
JayFt!22:11
JayF ^y22:11
*** zbitter is now known as zaneb23:22
spotz[m]JayF: times work for me23:51

Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!