Thursday, 2021-04-29

openstackgerritGhanshyam proposed openstack/governance master: Update TC onboarding guide  https://review.opendev.org/c/openstack/governance/+/78694201:17
*** evrardjp has quit IRC02:33
*** evrardjp has joined #openstack-tc02:33
*** jamesmcarthur_ has quit IRC04:04
*** jamesmcarthur has joined #openstack-tc04:04
*** jamesmcarthur has quit IRC04:09
*** vishalmanchanda has joined #openstack-tc04:24
*** jamesmcarthur has joined #openstack-tc04:27
*** openstackgerrit has quit IRC05:01
*** jamesmcarthur has quit IRC05:12
*** jamesmcarthur has joined #openstack-tc05:13
*** jamesmcarthur has quit IRC05:17
*** jamesmcarthur has joined #openstack-tc05:43
*** slaweq has joined #openstack-tc05:55
*** jamesmcarthur has quit IRC05:55
*** jamesmcarthur has joined #openstack-tc06:10
*** ralonsoh has joined #openstack-tc06:25
*** jamesmcarthur has quit IRC06:28
*** jamesmcarthur has joined #openstack-tc06:41
*** e0ne has joined #openstack-tc06:42
*** jamesmcarthur has quit IRC06:46
*** jamesmcarthur has joined #openstack-tc07:00
*** jamesmcarthur has quit IRC07:05
*** andrewbonney has joined #openstack-tc07:19
*** rpittau|afk is now known as rpittau07:27
*** jamesmcarthur has joined #openstack-tc07:30
*** e0ne has quit IRC07:43
*** tosky has joined #openstack-tc07:44
*** dirk has quit IRC07:45
*** dirk has joined #openstack-tc07:51
*** e0ne has joined #openstack-tc08:06
*** dklyle has quit IRC08:18
*** jamesmcarthur has quit IRC08:23
*** jamesmcarthur has joined #openstack-tc08:39
*** bnemec has quit IRC09:27
*** bnemec has joined #openstack-tc09:28
*** jeremyfreudberg has quit IRC09:36
*** tobberydberg has quit IRC09:47
*** tobberydberg has joined #openstack-tc09:52
*** jeremyfreudberg has joined #openstack-tc10:09
*** akahat is now known as akahat|ruck10:50
*** iurygregory has quit IRC10:54
*** iurygregory has joined #openstack-tc10:58
*** pojadhav is now known as pojadhav|rover11:10
*** jamesmcarthur has quit IRC12:38
*** jamesmcarthur has joined #openstack-tc12:38
*** tdasilva has joined #openstack-tc13:13
*** jeremyfreudberg has quit IRC13:27
*** jeremyfreudberg has joined #openstack-tc13:28
*** vishalmanchanda has quit IRC13:30
gmanno/13:33
spotzo/13:44
*** jeremyfreudberg has quit IRC14:03
*** jeremyfreudberg has joined #openstack-tc14:08
*** openstackgerrit has joined #openstack-tc14:15
openstackgerritMerged openstack/governance master: Remove expired extra-atc from Ironic  https://review.opendev.org/c/openstack/governance/+/78756514:15
yoctozepto\o/14:31
*** belmoreira has joined #openstack-tc14:37
*** dklyle has joined #openstack-tc14:47
gmanntc-members: meeting time14:59
yoctozeptoindeed14:59
gmann#startmeeting tc15:00
openstackMeeting started Thu Apr 29 15:00:17 2021 UTC and is due to finish in 60 minutes.  The chair is gmann. Information about MeetBot at http://wiki.debian.org/MeetBot.15:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:00
*** openstack changes topic to " (Meeting topic: tc)"15:00
openstackThe meeting name has been set to 'tc'15:00
gmann#topic roll call15:00
*** openstack changes topic to "roll call (Meeting topic: tc)"15:00
gmanno/15:00
belmoreirao/15:00
mnasero/15:00
yoctozeptoo/15:00
TheJuliao/15:00
gmannlet's start15:02
gmann#link https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee#Agenda_Suggestions15:02
gmanntoday agenda ^^15:02
gmann#topic Follow up on past action items15:02
*** openstack changes topic to "Follow up on past action items (Meeting topic: tc)"15:02
gmannno action item form last meeting #link http://eavesdrop.openstack.org/meetings/tc/2021/tc.2021-04-15-15.00.html15:03
gmann#topic PTG15:03
*** openstack changes topic to "PTG (Meeting topic: tc)"15:03
gmannwe have captured the discussion in PTG etherpad #link https://etherpad.opendev.org/p/tc-xena-ptg15:03
gmannI have also summarized the discussion on ML http://lists.openstack.org/pipermail/openstack-discuss/2021-April/022120.html15:04
jungleboyjo/15:04
gmannif anything I missed, feel free to add it15:04
spotzo/15:04
gmannanything on PTG things?15:05
spotzNot from my sidee15:05
gmannok, I will remove this topic for next weekly meeting onwards.15:05
gmann#action gmann drop PTG topic from agenda15:06
gmann#topic TC tracker for Xena cycle (gmann)15:06
*** openstack changes topic to "TC tracker for Xena cycle (gmann) (Meeting topic: tc)"15:06
gmannas discussed in PTG, I have created the Xena cycle tracker etherpad15:06
gmann#link https://etherpad.opendev.org/p/tc-xena-tracker15:06
gmannI added all the working item with assignee15:06
gmannone item I forget to ask assignee during PTG is 'OpenStack to a yearly release cycle'15:07
gmannitem #11 in etherpad15:07
gmannI would like to ask volunteer for this.15:07
* jungleboyj nominates TheJulia ;-)15:09
TheJuliaI have an absurd number of items on my plate, fwiw15:09
jungleboyjI was kidding.15:09
jungleboyjgmann:  What were the next items for that?15:09
spotzMore seriously maybe one person for the change and one person against the change?15:09
gmannthere are two Ai we collected15:10
gmann1. Reach out to Project team + operators about feedback via ML.15:10
gmann2. Encourage "Operation Docs and Tooling" SIG to add upgrades and operational education guideline15:10
TheJuliathe problem is it becomes an argument of "who is the loudest winds"15:10
gmannwe did not conclude to change it but more about getting more feedback and improve the education bits15:11
jungleboyjOk.  I think 1 is the most important there as we have feedback from a couple of people.  Would like to get more input.15:11
gmannyeah15:11
yoctozeptoI like this version with "winds"15:11
gmannanyways I will keep it open in case anyone take this.15:11
jungleboyj++15:12
gmannmnaser: as you missed the last hr of PTG. we distributed the working item to all the TC members with having each TC member taking at least one item.15:12
spotzI was more for making sure both sides were represnted to make sure the information was fully collected15:12
TheJuliajungleboyj: ++ to feedback15:12
gmannmnaser: and one I added for you is 'Stable core team process change' L34 in https://etherpad.opendev.org/p/tc-xena-tracker15:12
jungleboyjspotz:  ++15:12
mnaserfair enough :) thanks for putting my name down15:12
gmannmnaser: hope that is ok, if not I can help jungleboyj on this15:12
mnasernope, thats okay for me15:12
gmanncool, thanks15:13
gmannand for tracking, I am thinking to keep checking status in every alternate weekly meeting.15:13
gmannis that ok for all?15:13
jungleboyjThat makes sense.15:14
yoctozeptook for me15:14
gmannweekly check might be very frequent so i thought once in a 2 week is reasonable time in term of progress also15:14
spotzDO we have a way to get all PTL email addresses?15:14
gmannyeah, in project yaml15:14
spotzOk thanks15:14
gmannspotz: this one #link https://governance.openstack.org/tc/reference/projects/15:14
gmanneach project has PTL email as mandatory and IRC as optional15:15
spotzperfect!15:15
mnaserthat wfm wrt alternate meeting15:16
gmannok15:16
gmannI think we should add email id for SIG chair/co-chair too #link https://governance.openstack.org/sigs/15:16
gmannI will add it in case SIG wiki page does not have or old info15:17
gmann#action gmann to add SIG chair/co-chair info in sig doc site15:17
gmannok, anything else on Xena tracker ?15:17
yoctozeptonot from me15:18
gmannok, let's move15:18
gmann#topic Gate performance and heavy job configs (dansmith)15:18
*** openstack changes topic to "Gate performance and heavy job configs (dansmith) (Meeting topic: tc)"15:18
gmanndansmith updated that he might not be available today.15:18
gmannone thing to inform about dropping Bionic support from devstack (Xena onwards)15:19
gmann#link https://review.opendev.org/c/openstack/devstack/+/78875415:19
gmannwe can reduce the maintenance of fixing bionic bugs that way15:19
gmannbut there are few jobs running on Bionic which needs to be migrated to focal first.15:20
gmannanything else on gate check?15:20
gmannyoctozepto: ?15:20
yoctozeptodo we have a list of those bionic jobs?15:20
gmannyoctozepto: I need to fetch all form here #link http://logstash.openstack.org/#/dashboard/file/logstash.json?query=message:%5C%22Failed%20to%20start%20rtslib-fb-targetctl.service%5C%2215:21
gmannone is cinder-plugin-ceph-tempest-mn-aa15:21
yoctozeptohah, that's one way15:21
gmannand in octavia also15:21
gmannI will put this on ML and then we can wait for bionic drop patch15:21
yoctozeptowell, I can see nova too15:22
gmannthat is in gate to merged15:22
yoctozeptoack15:22
gmann#link https://review.opendev.org/c/openstack/nova/+/778885/1015:22
gmannbasically finding via 'rtslib-fb-targetctl' failure but there might be few more.15:22
gmannI am more concern on 3rd party CI where migration to new distro happens very late.15:23
gmannbut we have to trigger them at some point15:24
yoctozeptoperhaps this cycle precisely15:24
gmannyeah15:24
yoctozeptoas we simply don't support bionic at this point15:24
yoctozeptoso it's only by luck15:24
yoctozeptothat those pass15:24
gmannanyways let's put this on ML and see if project need more time.15:24
yoctozeptook15:24
gmanntrue, and as this is start of cycle, it is perfect time.15:25
gmannlet's move next15:25
gmann#topic TC's context, name, and documenting formal responsibilities (TheJulia)15:25
*** openstack changes topic to "TC's context, name, and documenting formal responsibilities (TheJulia) (Meeting topic: tc)"15:25
gmannwe have on topic from TheJulia15:25
gmannTheJulia: go ahead15:25
* yoctozepto asked on #openstack-infra if we can have a better way to list the bionic jobs15:26
TheJuliaGreetings, after the discussion during the ptg last week, I'm worried that the TC has has essentially dropped the responsibilites that came with the user committee and is also seeming to not want to recognize the reality that as leaders, non-technical questions must be part of the discussion.15:26
TheJuliaI honestly feel, the name is now out of sync, and I realize the fear of bylaws changes is a concern, but I don't believe the board would object if the TC passed a resolution to amend it's name15:26
gmanni see, what all responsibilities from UC ?15:27
gmannI remember we excluded few of them like local user groups reach-out/management etc15:28
TheJuliaWell, so that is an interesting conundrum aside from the implication of representation of the users of the software, much of the formal responsibilities seems not to be documented, at least in bylaws15:28
TheJuliaso a single unified list needs to be accessible as well15:28
jungleboyj++15:28
TheJuliaeven if it is just for consensus building amongst the committee15:28
spotz++15:29
TheJuliaThe bottom line is time has changed and evolved, so must practices and expectations.15:29
jungleboyjI think it is important that the Users are represented but don't really know what that entails.  :-)15:29
yoctozeptoagreed15:29
gmannyeah i agree that, I think we merged few of them. if not then we should add in #link https://governance.openstack.org/tc/reference/role-of-the-tc.html15:29
jungleboyjTheJulia: ++15:29
belmoreira+115:29
jungleboyjgmann: ++15:29
gmannwe merged the charter from uc, i remember that15:30
gmann#link https://governance.openstack.org/tc/reference/user-committee-charter.html15:31
TheJuliaIt seems like there seems to be some agreement that work in this area needs to be done to clean up/consolidate. Motivation to merge doesn't tell me what the responsibilities were much less what the committee now believes it should be doing.15:32
jungleboyjAgreed.15:32
spotzLooking at the TC role page it doesn't seem to cover all that we need to do since the Foundation isn't just OpenStack anymore15:32
TheJuliaAgain, times change, and so on and so forth15:33
gmannyeah15:33
gmannwe should add those resp in TC role doc to make very clear #link https://governance.openstack.org/tc/reference/role-of-the-tc.html15:33
TheJuliaOne thing, a high level index on that might be useful since it is an overflow of words to have to skim it :)15:34
spotzAs I mentioned during the PTG, to all intent and purpose we are not the Governing Board of OpenStack overseeing the project not just the technical side15:34
TheJuliaThat is really all, and I would encourage the TC to consider addressing it's name. Again, I don't think from a board member pov, that will be much of an issue since there will be a round of bylaws cleanup due to the foundation rename this year15:34
spotznot=now15:34
gmannwe also need to do more work on UC repo too, merging it in tc or so15:34
TheJuliaSo it may actually be a *good* time15:34
jungleboyjYeah.  I think it is a good time.15:35
TheJuliaSo, I've voiced my concerns, thanks for listening everyone!15:35
gmannTheJulia: agree, thanks for raising it which is very imp15:35
jungleboyjTheJulia: Thank you for raising.15:35
gmannI will add AI for me to start adding those in our doc or repo merge etc15:36
yoctozeptoTheJulia: thanks15:37
ricolinsorry I'm late, was in another meeting call15:37
gmann#action gmann to start updates to consume/merge UC responsibility in TC15:37
jungleboyjSounds good.15:37
spotz+115:37
belmoreira+115:38
gmannand as we have many user facing faces in TC it will be much easy for us to engage the users/feedback/circulating it to projects15:39
gmannanything else on this topic?15:39
gmannok, moving next then15:40
gmann#topic Open Reviews15:40
*** openstack changes topic to "Open Reviews (Meeting topic: tc)"15:40
gmann#link https://review.opendev.org/q/project:openstack/governance+is:open15:40
gmannwe have 4 formal-vote and 2 documentation changes open15:40
yoctozeptoyou have my votes on everything15:41
spotzI wasn't sure if we shhould vote so was just reviewing15:41
gmannspotz: in case you missed to add Recall-Vote in this ? i saw only code review +1 from your. https://review.opendev.org/c/openstack/governance/+/78694215:41
gmannyoctozepto: great, thanks15:42
gmannspotz: ok, you can Recall-Vote so that we can merge them as per change type.15:42
yoctozeptoRollcall-Vote*15:42
gmannwe have different set of criteria on number of vote/time to be open or so15:42
spotzgmann adding votes15:43
yoctozeptothough it's hard to mistake anyhow15:43
gmanncool thanks15:43
gmannyoctozepto: :) i always mistype that :)15:43
yoctozeptono problem15:43
yoctozeptohere to help :-)15:43
gmannok, that's all form me. anything else to discuss today ?15:44
fungicatching up, but remember there were no new responsibilities which "came with the uc," the uc was defunct and the most effective way to let it go without an expensive rewrite of parts of the foundation bylaws was to say the tc was also the uc... but the bylaws do not actually give the uc any explicit responsibilities, so the "uc responsibilities" are whatever the tc-members want them to be15:44
* jungleboyj will do code reviews here when I am not in two meetings at once. :-)15:44
fungiif tc members want there to be specific uc-oriented responsibilities then they're free to take those on15:45
yoctozeptogood point, fungi15:45
gmannfungi: agree, as we merged both entity now, we can reflect them in tc-role doc too15:45
yoctozeptothough TheJulia is right that we should strive to cover that role as well to have a healthier community15:45
gmannbut i remember we decided not to take marketing stuff like user groups reachout or so15:45
jungleboyjRight.  I think part of the reason this is important is really, OpenStack is transitioned to a period of more use than development.15:45
spotzThe problem gmann is that if we don't there's no one else who will. So we need to decide if that's ok15:46
jungleboyjAs a leadership body we need to keep that in mind.15:46
ricolinjungleboyj, true15:46
gmannlet's start adding the things and see if something new comes up or its just things we should reflect in our doc too15:46
fungi"marketing stuff like user groups reachout" was a responsibility the old uc claimed it had, but ultimately the foundation staff were taking care of most of that for them15:47
gmannspotz: that part is moved to foundation side, at least that is what i know from uc-tc merge discussion15:47
spotzok15:47
gmannfungi: indeed, that is what i think you or ttx  mentioned that time too15:47
TheJuliaI think contextually, it is lost on many, the foundation staff responsibilities are different than they were even just two years ago.15:47
TheJuliaIt is easy for people to get stuck in that context, and not move forward, so without re-evaluating and coming back to "what are the responsibilities of x group", then that continue which ultimately may hinder other aspects or cause whole areas to not receive attention.15:48
yoctozeptook, gmann already put an action on himself to collect those extra reqs from uc that make sense, and we will discuss them in the following meetings15:49
yoctozeptonot much to dwell on today unless we have concrete ideas already15:50
fungikeep in mind i'm not disagreeing that the tc might want to consider taking on some of that, just pointing out the "old uc" didn't really do it either, convincing community volunteers to oversee those sorts of things isn't easy15:50
gmannyeah, let's discuss each resp one by one and discuss.15:50
yoctozeptoneed to keep in mind to deliver those that the community would care about15:50
yoctozeptoand not just art for art15:50
gmannyeah, once we have exact list of what UC was doing and TC need to adopt then we can have concrete discussion15:51
TheJuliayoctozepto: even if it is just a call or encouragement, then it can go very far.15:51
yoctozeptoit can indeed15:51
fungiyou probably want to follow up with the foundation staff, since they were the folks doing those things15:52
gmannalong with that we need to cleanup UC repo also which was pending item also #link https://github.com/openstack/governance/blob/master/reference/user-committee-repos.yaml15:52
gmannfungi: +115:52
yoctozeptolike, if it was not for you, TheJulia, we would probably be not discussing this now at all ;-)15:52
yoctozeptothanks for the gentle nudge15:52
TheJulia:)15:52
gmannand i am sure during those repo cleanup we will get more points/responsibility15:52
yoctozepto++15:53
gmannanyways, I am adding this in our Xena tracker too in case we forget about this even i added AI15:53
yoctozepto++15:53
spotz++15:53
TheJuliabottom line, the repos are hard to find data. Indexing is a huge issue on how to just find information. It is a classic problem though :(15:53
jungleboyjMakes sense.15:53
gmannwe have 7 min left, any other topic.15:53
gmannif nothing let's close meeting.15:55
gmannthanks everyone for joining15:55
gmann#endmeeting15:55
*** openstack changes topic to "OpenStack Technical Committee office hours: Tuesdays at 09:00 UTC, Wednesdays at 01:00 UTC, and Thursdays at 15:00 UTC | https://governance.openstack.org/tc/ | channel logs http://eavesdrop.openstack.org/irclogs/%23openstack-tc/"15:55
openstackMeeting ended Thu Apr 29 15:55:46 2021 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:55
openstackMinutes:        http://eavesdrop.openstack.org/meetings/tc/2021/tc.2021-04-29-15.00.html15:55
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/tc/2021/tc.2021-04-29-15.00.txt15:55
openstackLog:            http://eavesdrop.openstack.org/meetings/tc/2021/tc.2021-04-29-15.00.log.html15:55
jungleboyjGood meeting!  Thanks guys!15:55
spotzThanks everyone!15:56
yoctozeptothanks15:56
spotz*kicks jungleboyj*15:56
yoctozeptojungleboyj: all tc meetings are good meetings15:56
jungleboyjHey, what was that for?15:56
yoctozeptowe are the good guys here15:56
ricolin:)15:56
jungleboyjOh thanks guys and gals?15:57
spotz:)15:57
yoctozeptooh, right15:57
yoctozeptofolks*15:57
jungleboyjfolks it is then.15:57
yoctozeptothough in some communities they say guys is genderless15:57
yoctozeptowhatever ye prefer15:57
jungleboyjThat is how I use it but don't want to offend.15:57
spotzYeah and I used to as well yoctozepto to be honest then got yelled at for it15:57
jungleboyjspotz: Sister from a different mister.  ;-)15:57
gmannyeah, i use guys a lot but not sure if that is right thing or not15:58
yoctozeptospotz: me too, though I tend to forget because "folks" sometimes offend people15:58
yoctozeptoso I am lost from time to time15:58
spotzy'all!:)15:58
yoctozeptooh, perfect15:58
yoctozeptothough "we are the good y'all" does not work15:58
spotzWe are the good peeps?:)15:59
* yoctozepto in search for new English words to fill that void15:59
yoctozeptoI guarantee "peeps" would at least bring some smiles :D15:59
spotzI only pick on jungleboyj cause we're like family:)16:00
jungleboyjAwwww.  :-)16:01
yoctozeptoawww16:01
yoctozepto*the whole tc melts from cuteness overload*16:01
*** e0ne has quit IRC16:06
*** jamesmcarthur has quit IRC16:07
spotzNeed more caffeine!16:13
*** jamesmcarthur has joined #openstack-tc16:14
*** jamesmcarthur has quit IRC16:34
*** jamesmcarthur has joined #openstack-tc16:36
*** tdasilva_ has joined #openstack-tc16:51
*** tdasilva has quit IRC16:53
*** jamesmcarthur has quit IRC16:55
*** jamesmcarthur has joined #openstack-tc16:56
*** iurygregory has quit IRC16:58
*** rpittau is now known as rpittau|afk16:59
*** andrewbonney has quit IRC17:19
*** ralonsoh has quit IRC17:26
*** iurygregory has joined #openstack-tc17:31
*** iurygregory has quit IRC17:31
*** iurygregory has joined #openstack-tc17:38
*** belmoreira has quit IRC18:16
*** pojadhav|rover is now known as pojadhav|away18:45
*** jamesmcarthur has quit IRC19:26
*** jamesmcarthur has joined #openstack-tc20:31
*** jamesmcarthur has quit IRC21:14
*** slaweq has quit IRC21:21
*** jamesmcarthur has joined #openstack-tc21:22
openstackgerritMerged openstack/governance master: Update TC onboarding guide  https://review.opendev.org/c/openstack/governance/+/78694222:56
*** tosky has quit IRC23:40

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