Tuesday, 2023-12-19

opendevreviewTakashi Kajinami proposed openstack/governance master: Move yaql to Heat's governance  https://review.opendev.org/c/openstack/governance/+/90399214:52
opendevreviewTakashi Kajinami proposed openstack/governance master: Move yaql to Heat's governance  https://review.opendev.org/c/openstack/governance/+/90399214:54
JayFtc-members: meeting in ~50 minutes, last one of the year \o/17:10
JayF#startmeeting tc18:00
opendevmeetMeeting started Tue Dec 19 18:00:19 2023 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
JayF#topic Roll Call18:00
rosmaitao/18:00
gmanno/18:00
slaweqo/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#info Three noted absences: dansmith, spotz, jamespage18:01
frickler\o18:01
knikollao/18:01
JayFthat makes the six of us 18:01
JayFThere are no due action items; going to skip that topic.18:01
JayF#topic Gate Health Check18:02
JayFAny observations on the gate?18:02
gmanni have not observed any frequent failure this week. 18:02
JayFIt's been looking better than usual to me; which I think is to be expected during this time of year.18:02
gmannyeah, less traffic 18:02
slaweqme neighter18:02
slaweqall looks good IMO18:02
fungiwe had a few incidents over the weekend... an automatically upgraded haproxy minor release included a regression that took the opendev.org site (gitea/git) and zuul dashboard offline. also a regression in the zuul timer trigger resulted in lots of extra periodic job runs until we emergency fixed it18:02
JayFSorry you all had to lose part of your weekend; thanks for getting it back to a happy place.18:03
fungiyeah, i was just glad we got everything straightened out by the time activity picked back up for monday18:04
JayFThanks for that for sure. I'm going to move on if there's nothing else?18:04
JayF#topic Leaderless Projects18:05
JayF#link https://etherpad.opendev.org/p/2024.1-leaderless18:05
gmannone thing, how we want to go for ec2-api, PTL appointment proposal is up and marking it inactive alos #link https://review.opendev.org/c/openstack/governance/+/903163  #link https://review.opendev.org/c/openstack/governance/+/90262518:05
gmannboth can be done also but we should decide either way18:06
gmannPTL appointment make sense to me and no negative vote there18:06
JayFAbsolutely, please, lets get votes on these, either positive or negative. It's especially awkward with the inactive proposal as it's stacked on a passing vote item.18:07
JayFIt's hard to tell explicit abstentions from inattention.18:07
JayFThanks for taking care of this gmann, we've made a lot of progress.18:07
JayFGoing to move on if there are no other comments.18:08
gmannnp!18:08
JayF#topic Implementation of Unmaintained branch statuses18:08
JayFrosmaita: any updates from last week? I'd presume not?18:08
rosmaitanope18:08
fungimy change to update the security site merged18:08
JayFCan you link that fungi?18:08
JayFI'm honestly not 100% sure what exactly you're referencing18:09
fungi#link https://review.opendev.org/901137 Update stable branch terminology for unmaintained18:09
fungifairly minor18:09
JayFUseful though, thank you!18:09
JayF#topic TC Charter updates & Openinfra Bylaw Changes18:10
JayF#link https://review.opendev.org/c/openstack/governance/+/903236/18:10
JayF#link https://review.opendev.org/c/openstack/governance/+/903239/18:10
gmanni replied to frickler comment on #link https://review.opendev.org/c/openstack/governance/+/90323618:10
JayFIt's important we vote on these and either approve or reject them in a timely fashion. 18:10
JayFI'm going to note, I'm not sure we emailed the list specifically about this charter change18:11
gmannyeah, other tc-members also can reply and add you point so that we can move fast in charter change and then resolution18:11
JayFI'm not seeing it in my search, unless someone can confirm we did it, I'm going to take an action to send that email18:11
JayFso it's eligible to land next week18:11
JayF#action JayF to send email publicizing charter changes18:11
gmannI usually used to mentioned those in my weekly summary email but no separate email18:12
gmannbut a separate email is also ok18:12
gmannbut I would like to ask what is tc plan, do we want to wait till holidays end or we cna do before18:12
fungiit's not often the tc is asked to approve bylaws changes, so can't hurt to call it out in a dedicated announcement18:12
JayFfrickler: you are here, many of the TC members are here, are there concerns we want to try to work out here and now?18:13
JayFfungi: I prefer separate emails for these things generally, I think it's easy to ignore recurring stuff 18:13
gmannremmeber there is hard deadline but it make sense to do soon for foundation staff to get bylaws change in effect18:13
fricklerwell I'm still not fine with approving the diversity wordings18:13
fricklerIMO in the current state, we could as well drop the whole thing18:13
gmannfrickler: any other suggestion you have for having some way to handle the diversity thing if that happen?18:14
JayFfrickler: I had similar concerns to yours, brought them up in the syncronous session we had with OIF representatives and lawyer, and basically got the impression that the existing language and tenor of the board made the existing diversity language essentially toothless as it is.18:14
gmannmy suggestion is to improve our diversity requirement over time and we can merge the current version which is coming from bylaws chnage discussion18:15
JayFfrickler: I am fairly certain if we had a situation, with bylaws and charter as they are now, where diversity rule was threatened, that rule would be changed/waived by the board in the same way you are concerned it could be waived by the TC in the new charter :/18:15
gmannas it will be in charter, tc has always time to improve/revise it.18:16
frickleras a compromise just deleting the second sentence could work for now I guess18:16
rosmaitagmann: ++ it doesn't leave us any worse off than we are now, and it will be easier for the TC to make revisions with it in the charter instead of the bylaws18:16
gmannyeah18:17
JayFAIUI, any changes to that text has to be vetted by the counsel for foundation, yes?18:17
frickleror if all other members agree to the current text, I'll leave it at my minority -118:17
fricklers/all/majority of/18:17
fungiat least changes to the charter don't need approval of the foundation board of directors and vetting by legal counsel18:18
JayFfrickler: I think that's a likely endpoint, based on the conversation in the sync meeting. I am onboard with any efforts you want to make to help add more teeth to a diversity requirement. I do not know how to structure such a requirement.18:18
gmannfrickler: you can start a separate review for that either remove it completly  or other idea to improve it18:19
fungithat's something we could ask for help from foundation counsel on18:19
gmannthat is the whole idea of moving things to charter so that TC has easy way to update/improve those18:19
fungibut would be better done as an iterative measure with limited scope18:19
rosmaitajust for the record, i'm opposed to eliminating that second sentence (about waiving the diversity requirement)18:20
JayFrosmaita: ++ I am as well *for purposes of this initial change*. I am open to further changes in diversity language in a separate change.18:20
gmannthat is why it will be easy to propose the new review for improvements otherwise we will go back and forth in current change18:20
gmannJayF: rosmaita: ++18:21
slaweqgmann++18:21
JayFAny further discussion on this topic?18:23
JayF#topic 2024.1 TC Tracker18:24
JayF#link https://etherpad.opendev.org/p/tc-2024.1-tracker18:24
JayFAny updates on TC Tracker items over the last week?18:25
JayFI suspect the answer is no with folks busy for the holidays, going to give a minute or so for anyone to pipe up before moving on.18:25
gmannno updates from me18:26
JayF#topic Open Discussion and Reviews18:26
JayF#link https://review.opendev.org/q/status:open+repo:openstack/governance18:26
JayFPlease take a look at governance changes, we have a few we've called out specifically but they aren't the only ones.18:26
JayFAnything for open discussion?18:26
fricklerregarding zuul config errors there seem to be new ones created time and again, so I've given up on those, too18:26
fricklermost of them by changes to zuul itself18:27
JayFfrickler: Bugs around ironic branches getting recrated contributed to that too, rpittau is working on a better solution for that.18:27
JayF(basically actually making release automation understand/handle retirement of our bugfix branches)18:27
frickleryeah, stale stable branches not getting cleaned up is another issue contributing there18:28
fungizuul has made it possible to separate errors from deprecation warnings now, but yes its expectations do evolve over time18:28
frickleralso please review https://review.opendev.org/c/openstack/openstack-manuals/+/90349818:29
fricklerto fix links to release pages18:30
gmannfrickler: I was good on that, just want to know the plan. commented there18:30
JayFyeah, I looked over it, +2, if you are good with it, +2A it gmann and it's landed18:30
JayFfrickler: feel free to ping me on these anytime, fwiw18:31
gmannmaybe elodilles can confirm if release team is planning to fix page link  from 2024.2 onwards18:31
JayFJust noting18:32
JayF#info Next meeting Jan 9 2024.18:32
JayFHave a good holiday everyone, either get rested up or find a quiet corner to hide and get stuff done in while everyone else is gone ;) 18:32
JayFAnything else?18:32
slaweqhave a good holiday :)18:33
fricklerJayF: does https://review.opendev.org/c/openstack/governance/+/903992?usp=dashboard need a special topic set?18:33
slaweqand see You all next year!18:33
rosmaitayes, i'd like to discuss the strategy for the ec2api PTL and make-inactive patches18:33
rosmaitasounds like JayF is in favor of both making the project inactive *and* appointing a PTL18:33
JayFrosmaita: There is nothing saying both can't land. An inactive project can have a PTL.18:33
JayFIn fact, an inactive project getting a PTL is a great step to getting activity.18:34
gmannfrickler: its project-update, done18:34
JayFfrickler: gmann: I still have to go to the topic glossary everytime to figure out the right one; ty gmann :) 18:35
gmannbut we can wait for murano PTL +1 but seems they are not replying18:35
frickleras mentioned earlier, IMO murano should also be marked inactive18:35
gmannI agree18:35
rosmaitalooks like https://review.opendev.org/c/openstack/governance/+/903259 is ready to merge18:36
JayFrosmaita: IMO the best possible outcome is we nominate a PTL for ec2-api, they fix the gate and get marked re-active super fast. Second-best is they fix the gate and are marked re-active by D-cycle. Either way, if the gate is broken and they aren't landing patches; it shouldn't be in "C"18:36
slaweq+1 to what JayF said18:37
JayFrosmaita: I'll run the check-review-status and land things right after this meeting18:37
gmann++18:37
JayFAnything else on this topic, or additional topics?18:41
JayFLast call before I close up the meeting?18:43
rosmaitanothing from me, happy holidays to anyone celebrating18:44
JayFHave a good holiday all o/18:44
JayF#endmeeting18:44
opendevmeetMeeting ended Tue Dec 19 18:44:46 2023 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)18:44
opendevmeetMinutes:        https://meetings.opendev.org/meetings/tc/2023/tc.2023-12-19-18.00.html18:44
opendevmeetMinutes (text): https://meetings.opendev.org/meetings/tc/2023/tc.2023-12-19-18.00.txt18:44
opendevmeetLog:            https://meetings.opendev.org/meetings/tc/2023/tc.2023-12-19-18.00.log.html18:44
gmannhappy holiday everyone18:44
slaweqo/18:45
JayFhttps://review.opendev.org/c/openstack/governance/+/903243 needs one more18:48
JayFI'm going to hold "Move yaql to Heat governance" for one week, to give the PTL of the departing project some window to see an email and respond. It has sufficient votes but has only been open a few hours. If this creates a hardship, someone ping me and I can land it.18:49
gmannmake sense18:49
JayFactually I think 903243 is good to land, I misread the votes18:49
opendevreviewMerged openstack/governance master: Mark ec2-api project inactive  https://review.opendev.org/c/openstack/governance/+/90262518:56
opendevreviewMerged openstack/governance master: Mark senlin project inactive  https://review.opendev.org/c/openstack/governance/+/90262618:56
opendevreviewMerged openstack/governance master: Appoint Andrey Pavlov as PTL of Ec2Api  https://review.opendev.org/c/openstack/governance/+/90316319:05
opendevreviewMerged openstack/governance master: Deprecate cinderlib  https://review.opendev.org/c/openstack/governance/+/90325919:05
opendevreviewMerged openstack/governance master: Move CHAIR.rst as official reference document  https://review.opendev.org/c/openstack/governance/+/90324319:05
opendevreviewMerged openstack/openstack-manuals master: Fix release links for numeric series  https://review.opendev.org/c/openstack/openstack-manuals/+/90349819:16

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