15:00:10 #startmeeting tc 15:00:10 Meeting started Thu Jan 20 15:00:10 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:10 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 15:00:10 The meeting name has been set to 'tc' 15:00:17 #topic Roll call 15:00:23 o/ 15:00:45 o/ 15:00:48 o/ 15:00:49 o/ 15:01:42 o/ 15:01:44 lourot: as fungi mentioned we have not discussed it yet. feel free to add it in TC meeting agenda (we can discuss next time or today also if you are ok) 15:02:28 today mentioned absence: Amy Marrich (spotz), Rico Lin (ricolin) 15:02:35 o/ 15:02:51 o/ 15:03:16 let's start 15:03:18 #link https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee#Agenda_Suggestions 15:03:20 today agenda ^^ 15:03:34 #topic Follow up on past action items 15:03:53 gmann to remove the SIG i18 topic from meeting agenda 15:03:58 it is done 15:04:10 #topic Gate health check 15:04:15 any news on gate 15:04:22 one is centos stream 8 issue. 15:04:50 with devstack workaround by yatin, we have tempest/nova centos stream job 8 working fine 15:04:55 and they are voting again 15:04:55 I haven't had anything through the gate in a week, but only because of me, not the gate :) 15:05:36 there was also a centos stream 8 package/index issue for a good chunk of today, but should hopefully have abated now 15:06:05 details on the ml 15:06:46 k 15:07:10 o/ 15:07:13 on stable, I am trying to cap on stable/train and testing it in many project #link https://review.opendev.org/q/topic:%22train-tempest-cap%22+(status:open%20OR%20status:merged) 15:07:29 currently master tempest is used which can stop working on stavle/train anytime 15:07:33 stable/train 15:07:56 fix seems working but need more result before we merge it 15:08:13 anything else on this topic? 15:09:20 let's move next 15:09:23 #topic Z Release Cycle Name 15:10:09 we are little late on that due to holidays and all sorry about that 15:10:17 now we have started the process #link http://lists.openstack.org/pipermail/openstack-discuss/2022-January/026620.html 15:10:24 \o/ 15:10:31 schedule is also merged #link https://review.opendev.org/c/openstack/governance/+/824201 15:10:36 to summary: 15:10:53 nomination will be closed on 24th jan, election from 25th to 1st Feb 15:11:30 and as discussed, we will continue with the existing process of 'electorate as TC only' 15:12:04 but as discussed in PTG, we will work on the new process change for release naming soon. 15:12:33 belmoreira will be putting it up for review, but no hurry. 15:13:06 here are the proposed name (not yet final) #link https://wiki.openstack.org/wiki/Release_Naming/Z_Proposals 15:13:07 Makes sense that the changeover would happen with the alphabet turnover 15:13:27 ++ 15:13:42 +1 15:13:55 yeah 15:14:00 But please review the names and add in 'Proposed Names that do not meet the criteria' section if they are not eligible names as per criteira 15:14:08 #link https://governance.openstack.org/tc/reference/release-naming.html#release-name-criteria 15:15:19 before we start the election, may be on friday I will ask community also to check the same and let us know if any offending name due to culture/history etc 15:15:30 this friday I mean 15:16:27 Good call. 15:16:42 I can't believe all the proposals! 15:16:43 also one things, Z release schedule is also prepared by elodilles and under review, feel free to add your feedback #link https://review.opendev.org/c/openstack/releases/+/824489 15:17:21 jungleboyj: indeed, I was thinking may be we will get hardly 5-10 names due to Z letter or our time constraints 15:17:53 but having lot of names show clearly community is much interested in release names they will be working one 15:18:25 that is all on this from me, anything else to discuss or any other process/step/work I missed here? 15:19:27 if nothing, let's move next 15:19:31 #topic Z cycle Technical Elections 15:19:40 #link https://review.opendev.org/c/openstack/election/+/825017/4 15:20:02 I have pushed the election schedule, please review and check 15:20:12 and we need two volunteer from TC to run this election 15:20:54 I am available but I will be helping as coordinating way wherever need help but will not be able to lead 15:21:15 proposed my name as election official #link https://review.opendev.org/c/openstack/election/+/825009 15:21:18 I am happy to help advise/support, but I will be super busy with PTG things at that point so I can't volunteer to run it. 15:21:46 diablo_rojo: ack. advice/support will be great help. 15:22:40 jungleboyj: I think you were interested last time? are you available to help? 15:22:44 I think it was spotz and I that went through some education before the last one? 15:23:24 Though I don't remember what I learned. Think it is all pretty well documented, right? 15:23:31 yeah, spotz is up for TC terms this time so she might not be able to be official 15:23:41 Oh, that is right. 15:23:55 Ok. I can volunteer to help out. 15:23:56 jungleboyj: I think so, mine also first time but we can take help of diablo_rojo if any question 15:24:15 gmann: Ok. I will join you. :-) 15:24:18 Yes definitely 15:24:21 cool, thanks jungleboyj 15:24:28 I will be able to help answer questions + give direction 15:24:37 diablo_rojo: Sounds good. :-) 15:24:38 i did it last time, but still considering if I will re run 15:24:40 and I think ianychoi[m] is also there and helena too to help 15:25:02 jungleboyj I can help with my experience from the last time 15:25:30 belmoreira: thanks. that will be great. may be once schedule is merged, we can start the meeting for that. 15:25:36 Sweet. So, sounds like we have plenty of help to get gmann and I up to speed. 15:25:55 yeah 15:26:03 please review the schedule #link https://review.opendev.org/c/openstack/election/+/825017/4 15:26:12 current election official as well as TC 15:26:18 anything else on this? 15:26:51 feel free to reach out to me with questions too 15:27:02 sure, thanks 15:27:17 #topic Adjutant need PTLs and maintainers 15:27:19 #link http://lists.openstack.org/pipermail/openstack-discuss/2021-October/025555.html 15:27:24 no updates on this 15:27:57 I will remove it from agenda and we will see during release or next election if there is no PTL or so.. 15:28:13 #topic Open Reviews 15:28:19 At that point we remove the project? 15:28:34 dansmith: no, continue in current state 15:28:38 diablo_rojo: ^^ 15:28:56 elodilles: mentioned there is ok for release as release team does in past too. 15:29:33 so let's have Yoga release (unless any issues occur) and during next cycle PTL election or assignment we will discuss it based on situation 15:29:47 like we do for any projects lacking leadership or maintainer 15:30:08 so nothing blocking in Yoga for now 15:31:07 diablo_rojo yeah after Yoga, we will see the situation. (I did not notice you mentioned 'At that time') 15:31:52 #link https://review.opendev.org/q/projects:openstack/governance+is:open 15:32:08 we have 4 open reviewsd 15:32:13 #link https://review.opendev.org/c/openstack/governance/+/822900 15:32:20 let's discuss tag one first 15:32:38 I did review on WIP one as yoctozepto proposed and left some comment 15:32:51 gmann, okay makes sense 15:33:05 gmann: thanks, I also replied 15:33:11 yoctozepto: I agree on the tag used in website. I think we can update the link there to point to doc instead of tag? 15:33:32 like stable policy field/question is also pointed to stable policy doc not to tag 15:33:48 gmann: yeah, I guess more-or-less moving these sensible ones might make sense 15:33:56 and dropping others 15:34:02 now it's surely dropping too much 15:34:41 yoctozepto: you mean to keep those (VMT ) tag and so does tag framework and remove rest of others? 15:35:23 gmann: well, we can move them to docs but we can also keep them around in this change and iterate 15:35:34 this way we can remove some parts without affecting releases 15:35:39 and then remove more 15:35:40 surely that would only be a stopgap? 15:35:40 yoctozepto: I see. sure that is good plan 15:35:45 okay yeah 15:35:53 "and then remove more" was the important part :) 15:36:00 and once we update the release script and website then we can remove completly 15:36:08 ++ 15:36:08 gmann: exactly 15:36:58 yoctozepto: can you please update the patch accordingly and we can review. 15:37:08 gmann: sure thing 15:37:22 yoctozepto: thanks 15:37:48 two reviews from ricolin who is not here in meeting but I have added my comment for project health tool 15:38:12 one open review and need review is FIPS goal #link https://review.opendev.org/c/openstack/governance/+/816587 15:38:26 ade_lee_: anything you want to mention about it or just waiting for us to review/vote 15:38:45 I put in a new version that I think addresses the issues raised before 15:38:55 but yeah, just waiting for review/vote 15:39:35 ade_lee_: thanks for that. 15:39:46 tc-members ^^ please review and provide your feedback. 15:40:23 or if any question, ade_lee_ is here and we have ~20 min left in meeting 15:41:36 if nothing, let's review the proposal 15:41:47 that is all from me today, anything else to discuss ? 15:42:02 Nothing from me. 15:42:30 nor from me 15:42:39 ok, let's close the meeting, 15:42:47 Thank you! 15:42:48 thanks everyone for joining and stay safe 15:42:51 #endmeeting