Thursday, 2022-01-13

opendevreviewRadosÅ‚aw Piliszek proposed openstack/governance master: [masakari] Transfer PTL role to suzhengwei  https://review.opendev.org/c/openstack/governance/+/82450908:24
*** mnasiadka_ is now known as mnasiadka08:43
*** ykarel is now known as ykarel|away09:47
*** emilien-oftc is now known as EmilienM13:35
opendevreviewGustavo Sanchez proposed openstack/governance master: Add the cinder-nimblestorage charm to Openstack charms  https://review.opendev.org/c/openstack/governance/+/82458514:36
dansmithgmann: irc or video today?14:37
dansmithah, you said irc in the email, so I assume so14:47
dansmithI'm playing post-operative nursing assistant for the next few days :/14:47
yoctozepto:-(14:49
gmanndansmith:  yeah. IRC. 14:55
gmanntc-members meeting time15:00
gmann#startmeeting tc15:00
opendevmeetMeeting started Thu Jan 13 15:00:12 2022 UTC and is due to finish in 60 minutes.  The chair is gmann. Information about MeetBot at http://wiki.debian.org/MeetBot.15:00
opendevmeetUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:00
opendevmeetThe meeting name has been set to 'tc'15:00
jungleboyjo/15:00
gmann#topic Roll call15:00
gmanno/15:00
ricolino/15:00
belmoreirao/15:00
diablo_rojoo/15:01
dansmitho/15:01
gmannwe have quorum as required in today meeting, let's start15:02
gmann#link https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee#Agenda_Suggestions15:02
gmann^^ today agenda15:02
gmann#topic Follow up on past action items15:02
yoctozeptoo/15:03
gmannno action item from previous meeting15:03
gmann#topic TC vote on gender-neutral language bylaws change.15:03
gmann#link https://lists.openinfra.dev/pipermail/foundation/2021-October/003016.html15:03
gmannNeed TC official approval for section Appendix 4, "OpenStack Technical Committee Member Policy". In the first paragraph it changes "his or her" to "their".15:03
gmannyou might have read the above email from wendar 15:04
gmannthis is section which changes need TC approval #link https://openinfra.dev/legal/openstack-technical-committee-member-policy15:04
gmannbefore we start voting about approval, any question?15:05
diablo_rojoNope.15:05
yoctozeptoeasy peasy15:05
jungleboyjPretty clear and easy.15:05
diablo_rojoFairly straight forward.15:05
yoctozeptoIndeed, no doubt I see.15:06
fungiwhat sort of majority is required for the vote?15:06
fungi(simple or 2/3?)15:06
spotzo/ sorry I'm late15:06
gmann5 as quorum ?15:07
gmannwe have 8 TC members here so let's start voting15:07
gmann#startvote TC vote on gender-neutral language bylaws changes in section Appendix 4, "OpenStack Technical Committee Member Policy"? Yes, No, Abstain15:07
opendevmeetBegin voting on: TC vote on gender-neutral language bylaws changes in section Appendix 4, "OpenStack Technical Committee Member Policy"? Valid vote options are Yes, No, Abstain.15:07
opendevmeetVote using '#vote OPTION'. Only your last vote counts.15:07
dansmithwe need to vote here instead of in gerrit?15:07
gmann#vote Yes15:08
spotz#vote yes15:08
gmanndansmith: here is fine15:08
diablo_rojo#vote yes15:08
ricolin#vote yes15:08
dansmith#vote yes15:08
yoctozepto#vote Yes15:08
belmoreira#vote yes15:08
jungleboyj#vote yes15:08
yoctozepto8/8/915:08
gmanneveryone is yes15:08
gmann#showvote15:08
opendevmeetYes (8): dansmith, yoctozepto, belmoreira, ricolin, jungleboyj, spotz, gmann, diablo_rojo15:08
gmannthanks everyone15:08
wendarthanks all!15:08
gmann#endvote15:09
opendevmeetVoted on "TC vote on gender-neutral language bylaws changes in section Appendix 4, "OpenStack Technical Committee Member Policy"?" Results are15:09
opendevmeetYes (8): dansmith, yoctozepto, belmoreira, ricolin, jungleboyj, spotz, gmann, diablo_rojo15:09
fungiyeah, looks like simple majority is all that was needed, per 9.1(d): "The amendment of Section 4.13 and the OpenStack Technical Committee Member Policy shall require the affirmative vote of the majority of the Board of Directors and the majority of the OpenStack Technical Committee."15:09
gmannwendar: anything else on this topic you would like to talk or we need from TC side ?15:09
wendarThat's it.15:09
gmannok, thanks for joining too15:10
gmannlet's move to next topic15:10
gmann#topic Gate health check15:10
gmannany highlights/news on gate. 15:10
jungleboyj\o/15:10
dansmithnoting from me on the gate (sadly)15:10
gmannthere were few devstack changes on failure/backport which are merged15:11
gmannone thing is about centos8 EOL15:11
gmann#link http://lists.openstack.org/pipermail/openstack-discuss/2022-January/026621.html15:11
gmannclarkb: sent ^^ email about that and project need attension15:12
fungiyes, we're in the process of excising centos-8 (non-stream) images from our configuration15:12
gmannI have pushed job/nodeset removal from devstack victoria/ussuri also as it needs to be done in those stable branches too15:12
gmannstable/wallaby and onwards already transitioned to centos-stream15:12
fungieveryone's assistance is appreciated in either switching jobs to centos-8-stream nodes or dropping jobs if that doesn't make sense15:12
gmannyeah15:13
gmannthese are devstack patches, please check in case anyone have objection or want to help to add centos-stream job in victoria and ussuri #link https://review.opendev.org/q/I36751569d92fbc5084b8308d423a75318ae7d40615:13
fungisome folks (e.g. openstack-helm/loci) had already started to spot problems with centos 8 package repositories and epel, disagreements on version requirements and such, so i don't expect it to remain viable much longer anyway15:14
gmannI think there is no objection overall (from any project as far as i read reply in ML thread) on removal of centos8. 15:14
yoctozeptoin kolla we are dropping centos linux 8 hard15:14
gmannk15:14
yoctozeptohard to object if it's eol anyway15:14
gmannfrickler: chateaulav Jan end is deadline right? if I read correctly ?15:14
gmannclarkb: ^^15:14
gmannchateaulav: sorry please ignore the pin15:15
gmannping15:15
fungideadline for gracefully merging fixes, yes15:15
gmanncool15:15
fungiafter that we'll break jobs/configuration for projects if necessary to remove the node definitions15:15
gmannsounds good15:15
gmannanything else on gate health ?15:16
gmann#topic Progress checks on Yoga Tracker15:16
gmann#link https://etherpad.opendev.org/p/tc-yoga-tracker15:16
gmannPlease update if any progress on any of your assigned items15:17
gmannI have marked yoga testing runtime as completed15:17
gmannyoctozepto need early feedback on tag removal patch #link https://review.opendev.org/c/openstack/governance/+/82290015:17
gmannI will review after meeting, sorry to miss this15:18
diablo_rojoTab open!15:18
yoctozeptono problem, I understand we are all busy :-)15:18
yoctozeptothanks gmann and diablo_rojo15:18
gmannother item I think good to do is 'User Survey Feedback Analysis/Responses' so that we can collect any AI/working item we need for Yoga cycle15:19
gmannjungleboyj: any plan on that^^15:19
jungleboyjNot at the moment.  I need to make time for that.15:19
jungleboyjWill put it on my backlog.  :-)15:20
dansmithI also know the unified limits thing is pending15:20
dansmithjust...a lot going on right now :/15:20
jungleboyjdansmith:  ++15:20
gmannno issue, please take time. and thanks for working on those15:20
jungleboyjSounds good.15:21
gmannanything else on any of item from tracker before we start the Z release name thing ?15:21
gmannZ Release Cycle Name15:22
gmannwe are little late on this as release team need to start the Z release schedule or so15:22
gmannI have started the process15:22
spotzI'm surprised by how many names we have already15:22
jungleboyjThank you for doing that.15:22
gmann#link https://review.opendev.org/c/openstack/governance/+/82420115:22
yoctozeptospotz: me too, z looks popular15:22
jungleboyjspotz: Yeah, I looked at that yesterday and was surprised!15:22
gmannplease review this15:22
gmann#link https://wiki.openstack.org/wiki/Release_Naming/Z_Proposals15:23
gmanncurrent proposed name and yes there are lot15:23
gmannI was also had concern if we will get only few name with Z but it is opposite :)15:23
dansmiththere's only one legit name on that list15:23
dansmithobviously Zomicron15:24
gmann:)15:24
jungleboyjZomicron ?15:24
yoctozeptois that a word?15:24
dansmithdoesn't matter15:24
fungiyeah, it's just before zomnomnom in the dictionary15:24
jungleboyjOh, I get it.15:24
dansmithlol15:24
belmoreiravery appropriate15:24
yoctozeptoxDDD15:25
jungleboyjDoot dooot da doo doo15:25
gmannas first step, please review the vote schedule #link https://review.opendev.org/c/openstack/governance/+/82420115:25
spotzWhat sort of related question, have we decided to go bacck to A or noot yet?15:25
jungleboyjspotz:  I thought we had agreed to do that.15:25
diablo_rojospotz that has always been the plan?15:25
gmannand next step is about naming process change which is what we discussed in PTG15:25
gmannspotz: yeah we agreed on that15:26
gmannL353 in https://etherpad.opendev.org/p/tc-yoga-ptg15:26
gmann#link https://etherpad.opendev.org/p/tc-yoga-ptg15:26
spotzJust confirming I knew we'd talked about it but couldn't remember if we'd 100% decided15:26
diablo_rojoTHe only thing that was up for debate was if we were changing cadence when we loop back around15:26
gmannbelmoreira: has item to propose the process change and A plan15:26
diablo_rojospotz, it was decided when they set the naming scheme way back before our times lol15:26
gmannone change for Z we talked is to 'open vote' instead of just 'TC vote'15:27
belmoreiragmann yes... time to start to think about it15:27
gmannI am wondering if we should keep old process 'TC vote' fore Z and change the process from A cycle ? 15:27
gmanndue to time constraint specially 15:27
spotzI always thought it was fun voting so I think we should open it back up15:27
belmoreiraas usual the best would be to get the input from the community15:27
gmannbelmoreira: thanks 15:27
jungleboyjspotz:  ++ 15:27
jungleboyjI am happy with that.  It felt weird with just us voting.15:28
gmannfrom Z cycle itself ?15:28
fungiin the end the tc ends up deciding whether the community vote is viable, or deciding which selections the community gets to vote on, so the tc is still deciding it15:28
jungleboyjgmann:  I am ok waiting for A to make the change, but it would be nice if it were a community vote for Z .15:28
spotz+1 jungleboyj15:28
diablo_rojoAgreed15:28
jungleboyjI know everyone is busy, so don't want to make it harder on people.15:29
gmannjungleboyj: yeah that was my hope but we are little late for Z and I do not want to delay it further 15:29
dansmithyeah, whatever is least effort is best here, IMHO15:29
dansmiththis is "fun" but not that important15:29
fungialso defining "community" is challenging. it'll be fun to see what the next opinion is on how to poll "the community" for a name choice15:29
spotzDidn't we goo through that for voting already on the TCC?15:29
dansmithif waiting until A is easier, that makes sense to me, but if it's easy to just revert to open right now for Z then just do it15:30
diablo_rojospotz, yes, but this will be at a much larger scale15:30
diablo_rojoAnd it was just the special election?15:31
gmanndansmith: we need a another formal-vote and reivew on process change and that is after we push that so it will take time15:31
dansmithah15:31
dansmithyeah15:31
dansmithmakes sense for A then15:31
gmannok, let's continue the same process 'TC vote only' for Z and work on process change for future releases in parallel 15:31
fungiyou can make it a completely open poll, that's fairly easy, but it's roughly the same as asking twitter what we should name the release. in the past we've also tried things like limiting it to the foundation individual members, limiting it to the tc electorate, and so on15:31
jungleboyjWorks for me.15:31
dansmithgmann: ++15:32
jungleboyjTwitter result ?  Zoinks !15:32
belmoreiragmann +115:32
gmanncool, I will start that once schedule is merged. 15:33
spotzgmann +115:33
jungleboyjgmann: ++15:33
ricolingmann, +115:33
diablo_rojoSounds good.15:33
gmannlet's move to next topic15:33
gmann#topic SIG i18n status check15:33
gmannianychoi[m]: has fixed the things and continue to lead this SIG.15:33
gmannI think we are ok now and we can drop this topic from agenda now?15:34
spotzSounds good15:34
gmannunless anyone has any feedback or so15:34
gmannthanks again ianychoi[m] for help15:35
gmann#action gmann to remove the SIG i18 topic from meeting agenda15:35
gmann#topic Adjutant need PTLs and maintainers15:35
gmannno update on this15:35
yoctozeptoare we waiting indefinitely?15:36
gmannhumm, Braden said still waiting for permission from company. ands there is no other help offering 15:37
gmannso I will say let's see for Yoga and if during release or next cycle it is not decided then we think about other option like retirement or so15:37
fungiis it still releaseable for yoga?15:38
gmannthis is time for next FY budget planning for most of company so i understand the waiting on permission things15:38
gmannAdrian said he will continue to help until someone will lead so I am hoping yes15:39
gmannwe will see how it goes15:39
fungijust noticing that no changes have merged to the openstack/adjutant repo since october15:39
diablo_rojoAnd they still haven't been a part of a coordinated release. 15:40
fungioh, did they never actually reach releasable state anyway?15:40
diablo_rojofungi, no I don't think so. 15:41
gmannyeah15:41
fungireleases.o.o claims adjutant 3.0.0 was included in xena15:41
fungiand 2.0.0 in wallaby15:41
diablo_rojoI was pretty sure that was empty..15:41
diablo_rojoI would have to dig in further though. 15:41
fungi1.0.0 in victoria15:42
gmannelodilles ^^ feel free to reachout to us for Adjutant release issue if any for Yoga as it facing maintainer issue15:42
fungilooks like it's been "released" as part of the coordinated openstack release as far back as ussuri15:42
fungihttps://releases.openstack.org/ussuri/index.html#ussuri-adjutant15:43
gmannk15:43
gmannlet's wait on this and we will see if any things we need to do in Yoga or ok to wait until next cycle start during PTL appointment process15:43
gmann#topic Open Reviews15:44
gmann#link https://review.opendev.org/q/projects:openstack/governance+is:open15:44
diablo_rojofungi, I'm either wrong about the not being released or missing something else then. My mistake. 15:44
gmannwe have 8 open review, let's see what all need attension 15:44
gmann[masakari] Transfer PTL role to suzhengwei #link https://review.opendev.org/c/openstack/governance/+/82450915:45
gmannthis is ready to vote, thanks yoctozepto for your leading masakari 15:46
yoctozepto:-)15:46
diablo_rojoYes, thank you for all your hard work!15:46
jungleboyj++15:46
gmannother project updates need two project-config change to merge 15:47
gmann#link https://review.opendev.org/c/openstack/project-config/+/823803 #link https://review.opendev.org/c/openstack/project-config/+/82458415:47
gmannfungi: mnaser frickler clarkb ^^ if any of you can review these15:47
fungisure15:47
gmannthanks15:48
gmannother review are in review i think. 15:48
gmannthat is all from my side for today meeting. 15:49
gmannanything else to discuss ?15:49
fungiwe discussed project renames in this week's opendev meeting15:49
jungleboyjNothing from me.15:49
gmannfungi: when it is planned ?15:50
fungi#link https://meetings.opendev.org/meetings/infra/2022/infra.2022-01-11-19.01.log.html#l-7515:50
fungimonday the 2022-01-24 is what we're planning to announce15:50
gmannok, sounds good15:50
fungino specific time decided yet, but probably late utc hours15:51
gmann+115:51
fungiso if any other renames/moves are known to be needed, please get them onto the list in our agenda wiki15:51
gmannack15:51
fungi#link https://wiki.openstack.org/wiki/Meetings/InfraTeamMeeting#Upcoming_Project_Renames15:52
gmannif nothing else, let's close today meeting. 15:53
spotzThanks gmann and everyone!15:53
gmannthanks all for joining and stay safe. 15:53
gmann#endmeeting15:53
opendevmeetMeeting ended Thu Jan 13 15:53:31 2022 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:53
opendevmeetMinutes:        https://meetings.opendev.org/meetings/tc/2022/tc.2022-01-13-15.00.html15:53
opendevmeetMinutes (text): https://meetings.opendev.org/meetings/tc/2022/tc.2022-01-13-15.00.txt15:53
opendevmeetLog:            https://meetings.opendev.org/meetings/tc/2022/tc.2022-01-13-15.00.log.html15:53
jungleboyjThank you!15:53
yoctozeptothanks gmann15:53
diablo_rojoThanks gmann!15:55
elodillesgmann: thanks! I don't know but i guess adjutant was just automatically released since it had changes and release management tooling caught it and was force approved. as far as I see there are merged bugfixes already so i think if we leave it like it is now, then it will be released the same way. Should we have any action to prevent the adjutant release?19:04
fungibug fixes which merged to master a few days after the xena release, looks like. nothing since19:38
yoctozeptofungi: did they get backported?19:44
fungii didn't check, merely looked at the dates on the commits in master19:47
yoctozeptook19:48
elodillesyepp, only some bug fixes. one is backported to xena, wallaby and victoria19:48
yoctozeptook19:48
fungimost recent merge to the master branch was october 26, three weeks after the xena release19:48
elodilles(victoria patch hasn't merged yet)19:48
gmannelodilles: thanks, no action needed. doing it in same way is good. I was wondering if there are some requried things from release team and due to no maintainer those are stuck. 19:51
gmannelodilles: thanks for reply 19:51

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