Thursday, 2020-03-05

*** dklyle has joined #openstack-tc00:02
*** slaweq has joined #openstack-tc00:11
*** dklyle has quit IRC00:19
*** dklyle has joined #openstack-tc00:22
*** slaweq has quit IRC00:27
*** e0ne has quit IRC00:45
*** slaweq has joined #openstack-tc01:11
*** slaweq has quit IRC01:16
*** slaweq has joined #openstack-tc02:11
*** slaweq has quit IRC02:16
* ricolin just finish his coffee and the reading to grandpa mordred'02:36
ricolin's story :D02:36
*** slaweq has joined #openstack-tc03:11
*** slaweq has quit IRC03:16
*** openstackgerrit has joined #openstack-tc04:09
openstackgerritJay Bryant proposed openstack/governance master: Analysis of 2019 User Survey Feedback  https://review.opendev.org/69858204:09
*** slaweq has joined #openstack-tc04:11
*** slaweq has quit IRC04:16
*** slaweq has joined #openstack-tc05:11
*** evrardjp has quit IRC05:35
*** evrardjp has joined #openstack-tc05:35
*** slaweq has quit IRC05:38
*** e0ne has joined #openstack-tc06:51
*** e0ne has quit IRC06:52
*** e0ne has joined #openstack-tc06:52
*** e0ne has quit IRC07:19
*** tetsuro has joined #openstack-tc07:44
*** iurygregory has joined #openstack-tc07:56
evrardjpnever heard of burrow before08:06
*** e0ne has joined #openstack-tc08:17
*** rpittau|afk is now known as rpittau08:46
*** e0ne has quit IRC08:55
*** njohnston has quit IRC09:07
*** mwhahaha has quit IRC09:07
*** gagehugo has quit IRC09:07
*** dhellmann has quit IRC09:08
*** e0ne has joined #openstack-tc09:16
*** tosky has joined #openstack-tc09:25
*** tetsuro has quit IRC09:29
evrardjptc-members: is there someone that wants to lead the meeting today?09:29
toskynot sure whether to report this, but while trying to work on the PTL doc goal, I noticed a few things that could get a fix: https://review.opendev.org/#/c/711407/09:33
*** njohnston has joined #openstack-tc09:43
*** mwhahaha has joined #openstack-tc09:43
*** gagehugo has joined #openstack-tc09:43
*** dhellmann has joined #openstack-tc09:43
*** openstackstatus has quit IRC09:45
*** e0ne has quit IRC09:45
ricolinevrardjp, I can help if you're not available10:10
*** e0ne has joined #openstack-tc10:45
evrardjpI am available, I just want to introduce a rotation, as I did it last time10:48
*** slaweq has joined #openstack-tc11:18
*** rpittau is now known as rpittau|bbl11:27
*** tetsuro has joined #openstack-tc12:03
*** tetsuro has quit IRC12:06
*** slaweq has quit IRC12:18
*** slaweq has joined #openstack-tc12:30
*** slaweq has quit IRC12:34
evrardjptc-members: meeting in an hour13:02
evrardjpmmm I might need ntp, as it seems my computer is lagging 3 minutes behind :p13:02
smcginnisevrardjp: https://docs.openstack.org/install-guide/environment-ntp-controller.html13:07
smcginnis:P13:07
evrardjpyeah chrony is da best!13:08
evrardjpthanks for the instructions, but it doesn't apply for my distro ! :p13:08
evrardjpwith only ttx in the absent ppl in the meeting, that's gonna be a meeting with tons of folks!13:09
smcginnisThere's SUSE instructions. What else would a SUSE employee be running?13:09
* evrardjp hides13:09
smcginnis:)13:09
evrardjpmy opensuse/SLE machines have ntp.13:09
evrardjpwow I am stupid, I should totally have said that I didn't see SUSE instructions.13:10
smcginnisHah!13:10
openstackgerritMerged openstack/governance-sigs master: Clarify scope to explain ownership of openstack ns in galaxy  https://review.opendev.org/71004513:10
openstackgerritRico Lin proposed openstack/governance master: Update example for zuulv3 goal  https://review.opendev.org/71145313:18
*** jamesmcarthur has joined #openstack-tc13:20
mnaserI’m not going to be able to make it to today. I apologize in advance.13:30
smcginnisHey, maybe there shouldn't be a meeting and knowledge sharing and discussions can just happen async on the ML.13:33
smcginnis:P13:33
evrardjpsmcginnis: technically this is just an official report from tc members, it's not really a meeting , like a meeting13:36
evrardjpwe chat about interesting things during office hours!13:37
smcginnisYou know what's great for reporting things? The ML.13:37
evrardjpexactly!13:37
smcginnishttps://tenor.com/4xEO.gif13:37
evrardjpmost of my links are basically pointing to ML or reviews13:37
evrardjphaha13:38
fungiwhen we stopped having meetings, some folks who don't follow ml posts said they missed the tc meeting minutes because that's how they kept up with what the tc was doing13:38
*** jamesmcarthur has quit IRC13:38
evrardjpwhich is exactly why I am doing those meetings13:38
fungiwhich is why when we reintroduced meetings we said they're just be a recap of what we've been discussing in more appropriate places, yeah13:38
evrardjpthere are meeting minutes pointing to nice links13:38
smcginnis"#startmeeting #link [link to report on ml] #endmeeting"13:39
smcginnisOK, I'll shut up now. :)13:39
evrardjpthough I would say that there are things we should also _start_ by grouping folks together13:39
ricolinI take meeting as a nice way to push thing forward:)13:39
gmanno/13:39
evrardjpand I would say that we haven't been the best at that13:39
fungiwell, to be fair, the main reason we reinstated meetings was that at the time the osf bylaws required the tc "meet" with greater frequency than our in-person events sometimes allowed13:39
evrardjpsmcginnis: imagine if those links would be prepared in the agenda, that would be like... Just a copy and paste in an email without official meeting13:40
*** jamesmcarthur has joined #openstack-tc13:40
fungi(that has since been relaxed with the last update to the bylaws at least)13:40
evrardjpfungi: Oh I thought this was still there13:40
evrardjpyay, let's stop those meetings!13:40
evrardjpricolin: I take our meetings as a nice way to remember folks to push things forward, but I would also say that 1 time per month is sadly not enough for that.13:41
*** cgoncalves has quit IRC13:41
evrardjpthough there are some updates that are hanging for 3 months.13:41
evrardjpmeh13:41
evrardjpI am trying to do my best13:41
evrardjpand hello gmann :)13:42
gmannmorning :)13:42
fungievrardjp: it now says "4. Meetings of Technical Committee. The Technical Committee shall meet at least twice per calendar year." https://www.openstack.org/legal/technical-committee-member-policy/13:42
evrardjpsmcginnis: you don't need to shut up, you're right in this case :)13:42
evrardjpbut yeah, please ! :p13:42
fungi(since that last rewrite)13:42
evrardjpfungi: oh good, I don't know why I remembered only the old ways13:43
gmanntwice in a month ?13:43
evrardjpgmann: too move things forward that would do, but I am not sure we'll get that much attention from tc members. I like the informal office hours to push things through13:43
evrardjpfungi: too bad we didn't remove a mention of a frequency at all13:44
gmannoffice hour are not much success for pushing things for any reason13:44
gmannbut meeting can also be :)13:45
evrardjpI don't expect any other format of meeting could change that13:45
*** cgoncalves has joined #openstack-tc13:45
*** jamesmcarthur has quit IRC13:45
evrardjphaha13:45
evrardjpyeah13:45
*** rpittau|bbl is now known as rpittau13:45
evrardjptbh I tried to wrap my head around our meetings to see if there is something to change to increase our productivity. And I don't think there is a silver bullet.13:46
gmannmy best take is to have a time deadline for items (at least for priority one), we do within or before xyz time else drop.13:46
evrardjpsome cases we might want to have ad-hoc meetings, and some cases we should just deal with the ML13:46
evrardjpgmann: yeah that's valid13:47
evrardjpbut I think at some point we'll drop everything. because E_NOTIME13:47
gmannthat means we do not need those things to be done then :)13:48
gmannthose or all :)13:49
evrardjpor that we need but can't insure we'll do them on time, which basically limits us on only non-risky topics13:49
evrardjpbut that's maybe me having wishful thinking that we'll do non-risky topics anyway13:50
evrardjphaha13:50
evrardjpI also have the impression that setting deadlines will trigger a question of whether the deadline is relevant, and bikeshedding over dates :/13:51
evrardjpall of this could be fine on some topics13:51
evrardjpless fine on others13:51
gmanndeadline as per topic/assignee/cycle priority etc.13:52
ricolincheck points before deadline is helpful (IMO)13:52
evrardjpwhat I thought would be a community driven roadmap, which basically means a time based backlog13:53
ricolin*are13:53
evrardjpbut I got many ppl concerned about this approach13:53
evrardjpheard*13:53
gmannat least when we start new cycle, we can say we are going to try these new things and check possibility of their doable from what we left form previous cycle work.13:53
gmannif pending items go to backlogs and if anyone pick those or show interest then we can say 'are you sure, you can finish this within this timeframe because it was a  unfinished items for xyz reason '13:54
fungievrardjp: we discussed removing the meeting frequency from the bylaws, but legal counsel weighed in that doing so may not meet the requirements (in delaware, where the osf is officially filed as a foundation) for a governing body13:55
fungibasically if it's not required to meet in some fashion with some defined minimum frequency (probably at least annually) it could be claimed that it doesn't really assemble as a "body"13:56
fungiwithout some required regular assembly, you can't know when it's ceased to exist13:57
fungiso we kept in a minimum which shouldn't be hard to satisfy13:58
evrardjpbut isn't the foundation taking care of that? I mean I am not sure this can be applied to the TC directly, but I am not a lawyer ofc13:58
fungiit's about the tc specifically13:58
fungibecause the tc is defined as a governing body in the bylaws13:59
evrardjpI see13:59
fungithough similar requirements would apply to the board and the uc for the same reason13:59
evrardjplet's get the ball rolling!14:00
evrardjp#startmeeting tc14:00
openstackMeeting started Thu Mar  5 14:00:08 2020 UTC and is due to finish in 60 minutes.  The chair is evrardjp. Information about MeetBot at http://wiki.debian.org/MeetBot.14:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:00
*** openstack changes topic to " (Meeting topic: tc)"14:00
openstackThe meeting name has been set to 'tc'14:00
evrardjp#topic rollcall14:00
njohnstono/14:00
diablo_rojo_phono/14:00
*** openstack changes topic to "rollcall (Meeting topic: tc)"14:00
evrardjpo/14:00
evrardjpthat makes us 3, mnaser and ttx won't be there14:00
evrardjp8 missing.14:00
gmanno/14:00
ricolino/14:00
evrardjptwo more for quorum14:01
evrardjpjroll: asettle jungleboyj cloudnull maybe?14:01
asettleo/ hallo14:01
evrardjpwoot!14:01
evrardjpone more, one more!14:02
jungleboyjo/14:02
evrardjpwooot!14:02
jungleboyjI am here.  :-)14:02
evrardjpwe can go ahead14:02
evrardjp#topic a little message from evrardjp14:02
*** openstack changes topic to "a little message from evrardjp (Meeting topic: tc)"14:02
evrardjpas this might be my last meeting as TC chair, I would like to say a few words before starting our official meeting...14:02
evrardjpit's been a pleasure working with all of you. we had a good team! Thank you for your support and your leadership.14:02
evrardjpI would like to highlight that some of us were more discreet than others. Those shouldn't hesitate to share their opinions, or propose new topics that motivate them! at the opposite, those who are more vocal (like me or mnaser) should always remember to let the opportunity for the less vocal ones to speak.14:03
ricolin https://gph.is/1rKtPXj14:03
evrardjpricolin: haha :)14:03
evrardjpIt would be nice if we could all reflect on what was achieved this last 6 months, and think about how we can improve further forward.14:03
evrardjpWe should discuss this in our next real life event, or, if the next event is cancelled, do it in a side meeting.14:03
evrardjpI don't want to leave the TC with the skeletons in the closet, or the elephant(s) in the room, whatever applies in your language :)14:04
evrardjpSo, I propose we discuss all the big things like glance cli or nova ptl after this official meeting, in the office hours.14:04
njohnston+114:04
evrardjpI am glad we introduced the ideas concept, and I am glad a few ideas were already proposed. Thanks zaneb for example.14:04
jungleboyj:-)14:04
evrardjpLet's leverage this framework for ambitious changes that might not fit into a simple change in the governance repo.14:04
evrardjplast, I want to especially thank gmann, who has done a tremendous work on the difficult community goals.14:04
evrardjpnow, let's get the ball rolling by reporting what happened last month.14:04
evrardjp#topic Report on tc/uc merge14:05
*** openstack changes topic to "Report on tc/uc merge (Meeting topic: tc)"14:05
evrardjpthere is nothing to report, everything is on the ML14:05
evrardjp#link http://lists.openstack.org/pipermail/openstack-discuss/2020-February/012806.html14:05
evrardjp#topic report on survey analysis: jungleboyj14:05
*** openstack changes topic to "report on survey analysis: jungleboyj (Meeting topic: tc)"14:05
evrardjpI saw this was updated today/yesterday, is there anything else to say than checking the review?14:05
evrardjp#link https://review.opendev.org/#/c/698582/14:05
jungleboyjNo, I don't think so other than if people want to provide other thoughts on the % participation.14:06
gmannI think UC meeting to discuss the same is after half an hour if I remember14:06
evrardjpgood feedback gmann14:06
gmannoh, for uc/tc merge things not survey14:06
jungleboyjSorry I didn't get an update in sooner.  Month went quickly.14:07
njohnstonI joined the UC meeting that just happened BTW, they have clarified what responsibilities they have.  I think the two main remaining points are agreeing on a mechanism for the join and how to make operators/users feel represented.14:07
evrardjpoh I thought you meant they analysed the results too :p14:07
evrardjpnjohnston: can this be done on the MLs?14:07
evrardjpjungleboyj: no worries :)14:07
njohnstonevrardjp: Yep, I just wanted to note it.14:07
cloudnullo/14:07
evrardjpok cool14:07
* cloudnull late to the party 14:08
jungleboyjRather than making a statement about being concerned about the amount of participation thought it would just be good to note that I would like to see what the trend is.14:08
evrardjpjungleboyj: I think that was the point of doing the exercise to its fullest, and re-iterate the experience in 202014:08
ricolinjungleboyj, I think the latest patch set provide great information already14:09
evrardjpbut it's indeed worth noting in the review14:09
evrardjpor in another one14:09
evrardjpI will keep that in mind when reviewing14:09
evrardjpanything else?14:09
*** jamesmcarthur has joined #openstack-tc14:09
jungleboyjOk.  Everyone take a look.  I will prioritize responding so we can get it merged.14:09
evrardjp:D14:09
jungleboyjThank you to aprice  for getting me the data I needed.14:09
evrardjpthank you for handling that new kind of effort jungleboyj!14:10
jungleboyjNo problem.14:10
evrardjpestablishing long term trends is good to have data about our community :)14:10
evrardjpuntil we have other tools to do that ofc :)14:10
jungleboyj++14:11
evrardjps/until we have/in addition to the future/14:11
evrardjpok moving on14:11
evrardjp#topic telemetry14:11
evrardjpnothing to report14:11
*** openstack changes topic to "telemetry (Meeting topic: tc)"14:11
evrardjp#topic stable branch policy14:11
*** openstack changes topic to "stable branch policy (Meeting topic: tc)"14:11
jroll\o sorry I'm late, got distracted by a baby :)14:11
evrardjp#action mnaser still write the summary of what's going on in terms of stable branch policy14:12
evrardjpjroll: no worries :)14:12
evrardjp#topic report on goal contribution guide: diablo_rojo14:12
*** openstack changes topic to "report on goal contribution guide: diablo_rojo (Meeting topic: tc)"14:12
evrardjpdiablo_rojo: is the situation clear nowadays?14:12
ricolindiablo_rojo_phon,14:12
evrardjpshould I say "state" instead of "situation" ?14:12
diablo_rojo_phonYes I would say so14:12
evrardjpok14:13
diablo_rojo_phonA consensus has been reaches14:13
diablo_rojo_phonReached14:13
diablo_rojo_phonAnd I updated the ML yesterday14:13
evrardjpcool, then I guess people can just comment on reviews and start helping on the goal then14:13
evrardjpoh awesome14:13
toskyI... sent an small update for cookiecutter14:13
toskyjust formatting14:13
evrardjptosky: I saw that, thanks!14:13
toskyjust in case: https://review.opendev.org/#/c/711407/14:13
diablo_rojo_phontosky: I saw that this morning, will review today :)14:13
*** witek has joined #openstack-tc14:14
evrardjpok let's move on14:14
evrardjp#topic report on other community goals: gmann njohnston ricolin14:14
*** openstack changes topic to "report on other community goals: gmann njohnston ricolin (Meeting topic: tc)"14:14
gmannU goals:14:14
gmann1. py2 drop I will cover later14:14
gmann2. contributor guide:14:14
gmann diablo_rojo_phon sent the updates on ML14:14
gmann#link http://lists.openstack.org/pipermail/openstack-discuss/2020-March/013003.html14:15
gmanngoal doc update patch is also merged14:15
diablo_rojo_phonCoolio. Full steam ahead then.14:15
gmannwe need to merge the tosky fix also#link https://review.opendev.org/#/c/711407/14:15
toskythere is also a fix from zaneb14:15
*** jamesmcarthur has quit IRC14:15
evrardjptosky: indeed14:16
gmannok, we have separate core on that repo so we need to ping them to get them merge soon14:16
gmannV cycle goal:14:16
evrardjpyou should review the jinja to see if I am not too rusty in my comments btw14:16
gmannML: http://lists.openstack.org/pipermail/openstack-discuss/2020-February/012866.html14:16
evrardjp#link http://lists.openstack.org/pipermail/openstack-discuss/2020-February/012866.html14:16
gmannzuulv3 goal is selected for V and grenade base job are in good shape and close to merge14:17
gmannthanks tosky again for working hard on those14:17
evrardjpthat's awesome14:17
toskyyep, I need a few final fixes14:17
gmannnjohnston sent the request for V cycle goal proposal to a few individuals also.14:17
gmannI replied on OSC thread also if anyone interesting to drive the OSC as a community goal or pop-up team.14:17
gmannbut no new proposal or volunteer14:17
njohnstonYes, so far the main thing that has come up has been the OSC matter that we'll discuss later14:17
evrardjpif we do this, we really need to pay attention to not fail like last time :p14:17
gmannyeah, key things is we need more than one volunteer for this and it can be multi cycle goal14:18
gmannother idea is - njohnston and I are going to check the backlogs and start pushing on ML for a volunteer to drive those.14:18
gmannAny feedback/ideas are welcome here.14:18
evrardjpand that all projects help, some shouldn't say "no to this"14:18
evrardjpgmann: sadly I don't have another idea than this14:19
* gmann wait for tc members to take one of the goal :)14:19
evrardjpexcept if you have someone in your company or a tc member that can take those14:19
* evrardjp sees what gmann has done there ;)14:19
gmannyeah project motivation is much required as this is for their user benefits14:19
gmannpy2 drop:14:20
ricolinI think we can start a ML for OSC and ask if anyone not in favor of that one and also ask for volunteers too14:20
gmannLatest Updates on ML: #link http://lists.openstack.org/pipermail/openstack-discuss/2020-March/012953.html14:20
gmannFew tempest plugins are failing and fixes are in progress. I started doing updates required on deployment projects.14:20
gmannphase-2 should be finished by now but it is not. Let's see how fast we can complete that and start phase-3 which is audit and requirement drop py2.14:20
gmannNot so much failure nowadays, which shows we might have fixed the big issues and going towards stabilizing this migration.14:21
gmannI will continue working on this on priority and try to finish as soon as possible.14:21
gmann that's all from my side, any question/feedback?14:21
evrardjpI have no question, that's crystal clear14:22
ricolingmann, all grenade issue with py2 drop fixed, right?14:22
gmannyeah.14:22
gmannzuulv3 jobs for grenade are also very close to nerge14:22
gmannmerge14:22
jungleboyjgmann:  Thanks for all the work there.14:23
ricolinFrom a project team point of view, it will definitely helpful if other teams can help to collect examples together and provide some brief about what this patch is special about.14:23
ricolinlike `how other teams migrate grenade to v3`14:24
gmannricolin: +1.14:24
gmannonce it is ready, tosky or i can add14:24
ricolinAlso most of zuul v3 patches didn't follow the goal defined Garrit topic14:24
ricolinAre we still plan to use that?14:25
toskythere were no many patches so far after the goal was merged14:25
ricolintosky, totally agree14:25
toskyand I changed the topic of the patches that I uploaded after the goal was merged14:25
gmannyeah, now onwards or when tosky start the goal then we can ask them to use14:25
ricolinthat's why I think collect patch from team might works too:)14:26
ricolingmann, +114:26
evrardjpanything else ricolin gmann or tosky?14:26
ricolinnope:)14:27
gmannnothing from my  side14:27
evrardjpok let's move on then14:27
evrardjp#topic report on  release naming14:27
*** openstack changes topic to "report on release naming (Meeting topic: tc)"14:27
evrardjpI think we are all good now, is there anything else to report or do mugsie/smcginnis?14:27
jungleboyjYay for Wallaby!14:28
mugsiewe are good afaik14:28
jungleboyjIt comes with a cute built-in mascot.  :-)14:28
evrardjp:)14:28
evrardjpok14:28
evrardjp#topic report on the ideas repo14:28
*** openstack changes topic to "report on the ideas repo (Meeting topic: tc)"14:28
evrardjpthis is started. thanks to those putting ideas there, like zaneb or hberaud14:28
evrardjpI have a few ones pending, but I am waiting for the nova conversation to be distilled, because it was kinda linked14:29
evrardjpanyway14:29
ricolinTeapot in review14:29
evrardjpindeed14:29
smcginnisSorry - nope, we are all good on release naming.14:29
evrardjpif you haven't read it, you should14:29
smcginnisI think it went well. Thanks everyone.14:29
evrardjpsmcginnis: thank you for handling this14:29
jungleboyjsmcginnis: ++14:29
evrardjpok next topic14:30
gmannjust updates from nova meeting.  eric message: "A couple of folks have talked to me privately about taking over the PTL role. But nothing has solidified as yet."14:30
evrardjp#topic report on volunteers to represent OpenStack at the OpenDev advisory board14:30
*** openstack changes topic to "report on volunteers to represent OpenStack at the OpenDev advisory board (Meeting topic: tc)"14:30
ricolinare we plan to start X release naming shortly?14:30
smcginnisNo problem. Pretty easy now.14:30
jungleboyjsmcginnis:  Did you get any feedback from the community?14:30
smcginnisSurprisingly no.14:30
evrardjpapparently I went too fast14:30
jungleboyjOk.  Guess that is good.14:30
jungleboyjevrardjp:  Sorry, I was too slow in thinking.14:30
jungleboyjWe can move on.14:30
smcginnisevrardjp: Nothing to see here, move along. :)14:30
jungleboyj:-)14:30
evrardjpI guess the question of ricolin could deserve some answering though :p14:31
evrardjpbut that can be done later if necessary14:31
jungleboyjhttps://gph.is/2a6mXOM14:31
evrardjpok so...!14:31
ricolinjust curious:)14:31
evrardjp#topic report on volunteers to represent OpenStack at the OpenDev advisory board14:31
*** openstack changes topic to "report on volunteers to represent OpenStack at the OpenDev advisory board (Meeting topic: tc)"14:31
evrardjpnothing to report, we'll wait for the creation of the advisory board first :p14:31
evrardjp#topic report on OSF board initiatives14:32
*** openstack changes topic to "report on OSF board initiatives (Meeting topic: tc)"14:32
evrardjpnothing to report on my side, mnaser had a last minute thing which prevent him to be in this meeting, so maybe he can report next time if there is something to report14:32
evrardjp#action mnaser (if anything to report), report on OSF board initiatives14:32
evrardjpI guess we now https://gph.is/2a6mXOM14:33
evrardjp(thanks for the gif jungleboyj :p )14:33
evrardjp#topic report on dropping projects14:33
*** openstack changes topic to "report on dropping projects (Meeting topic: tc)"14:33
evrardjp#link https://review.opendev.org/#/c/707421/14:33
evrardjpthis merged, so nothing to report. We only have to apply now.14:33
evrardjp#topic elections14:33
*** openstack changes topic to "elections (Meeting topic: tc)"14:33
jungleboyj:-)14:34
evrardjp#link https://review.opendev.org/#/c/708470/14:34
evrardjpwith this merge, I guess the only thing to report is that we'll have elections soon, and therefore tc elections soon.14:34
ricolinalso we should encourage people to join that election too14:34
jungleboyjricolin:  ++14:34
evrardjpFYI I won't apply to be chair next time14:34
gmann+114:34
ricolinPTL and TC14:34
evrardjpyes indeed!14:35
*** jamesmcarthur has joined #openstack-tc14:35
jungleboyjWonder what we can do to socialize things and drum up more interest.14:35
gmannwe should write up some motivational message for people to take leadership14:35
jungleboyj++14:35
ricolinjungleboyj, +114:35
evrardjpI think it would be nice for those leaving the tc and know that they won't run another time to make it public, and try to gather interest in the community14:35
* gmann wait for ttx :)14:35
jungleboyjevrardjp: ++14:36
gmannttx motivation is great, some ML message from him can help.14:36
zanebo/14:36
ricolinwe can put some words in ML, foundation news letter, and Super user magz14:36
ricolin*magazine14:37
jungleboyjricolin: ++14:37
ricolinAnyone here good at motivation?:)14:37
evrardjpzaneb:14:37
evrardjp:D14:37
ricolinsold!14:37
evrardjphaha14:38
evrardjpok14:38
evrardjpwell14:38
gmann+114:38
evrardjpthat's all we had today to report14:38
* zaneb reads scrollback to figure out what he was just volunteered for14:38
evrardjpI will close this one up, and we can talk about other things then14:38
gmanncan we have action item for that ? we need to do something so that more people show up for those elections14:38
ricolin+114:38
evrardjpisn't that what everyone should do though?14:39
evrardjpI am fine with defining action items14:39
zanebactually that was on my list anyway14:39
*** cgoncalves has quit IRC14:39
ricolin:)14:39
gmanneveryone can do by taking to people they thing should come up but a ML message from motivational people like ttx zaneb can help14:39
jungleboyjgmann: ++14:39
jungleboyjI also thought about reaching out to people who might be interested.14:40
gmann+1. thank jungleboyj14:40
zanebit occurred to me that it would be helpful if everyone posted a retrospective of what they actually did on the TC14:40
*** cgoncalves has joined #openstack-tc14:40
evrardjp#action asettle mugsie jroll mnaser ricolin ttx zaneb post a message on the ML if not running again in the next tc elections, and encourage people to run14:40
zanebbecause the most common question is "what does the TC actually do?"14:40
asettleevrardjp, aye aye captain14:41
evrardjpzaneb: I actually said that in the first few words of the meeting14:41
ricolinzaneb, yeah, evrardjp mentioned that part earlier, and indeed will be great if we put this two things together14:41
gmannin separate email or a collective one ?14:41
*** ccamel has joined #openstack-tc14:41
*** jamesmcarthur has quit IRC14:41
jrollevrardjp: will do14:41
* ricolin slow typer:)14:41
evrardjpgmann: I think it's better to have a separate email :)14:41
gmannok.14:41
evrardjpPeople might have different reasons14:41
evrardjpbut this can be in a thread :)14:41
zanebyeah, separately14:42
ricolinseparate but link to another one14:42
*** camelCaser has quit IRC14:42
*** jamesmcarthur has joined #openstack-tc14:42
gmannok, replying separately on single thread will be helpful.14:42
evrardjp#action all tc members, encourage folks to take a leadership role in the next elections14:42
jungleboyj++14:43
evrardjp#action tc-members: reflect on achievements done in this cycle (see also beginning of this meeting)14:44
evrardjpprobably a terrible wording, sorry for that ^14:44
evrardjpbut I suppose you get the idea14:44
evrardjpok let's wrap this up, and talk about other things, like nova or glance! :P14:45
evrardjp#endmeeting14:45
*** 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/"14:45
openstackMeeting ended Thu Mar  5 14:45:16 2020 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:45
openstackMinutes:        http://eavesdrop.openstack.org/meetings/tc/2020/tc.2020-03-05-14.00.html14:45
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/tc/2020/tc.2020-03-05-14.00.txt14:45
evrardjpthanks everyone14:45
openstackLog:            http://eavesdrop.openstack.org/meetings/tc/2020/tc.2020-03-05-14.00.log.html14:45
gmannthanks evrardjp for chair14:45
jungleboyjThanks evrardjp14:45
ricolinthanks evrardjp !14:45
njohnstonthanks evrardjp!14:45
diablo_rojo_phonThank you!14:45
evrardjpmy pleasure14:46
zanebthanks evrardjp14:46
ricolinevrardjp, and now, you can have you beer!14:46
gmannon Nova thing: if you missed my msg earlier.14:46
gmannupdates from nova meeting happening in parallel .  eric message: "A couple of folks have talked to me privately about taking over the PTL role. But nothing has solidified as yet."14:46
evrardjpI saw that14:46
gmanni hope we will get someone to fill the space14:47
evrardjpit's important14:47
evrardjpyeah I sure hope14:47
jungleboyjWell, that is positive news at least.14:47
evrardjpdid anyone reply on the current ML thread on the possible PTL changes?14:47
gmann? the one mnaser started ?14:48
evrardjpyes14:48
jungleboyjevrardjp:  Yes.14:48
ricolinreplied14:48
gmannyeah14:48
njohnston16 replies so far I think14:48
jungleboyjI appreciate mnaser 's concerns but I don't know that we can do away with the role.14:48
evrardjpI have the impression it's a very mixed signal, but the idea would be to decrease PTL pressure, not necessarily have a change. And maybe allow the teams to be organised differently. Did I summarize this wrong?14:48
ricolinI always support co-PTL stuff14:48
jungleboyjWith no lead people are likely to just assume someone else will deal with it.14:48
jungleboyjevrardjp:  Yeah.14:49
evrardjpricolin: I like the shadowing for learning exercise, and stepping people up.14:49
gmann+1. co-PTL can be helpful here. like what asettle proposed in last cycle for doc for same reason.14:49
evrardjpand I have the same concern of jroll14:49
evrardjpjungleboyj sorry14:49
jungleboyjFor some time that is how we have done it in Cinder.  Have someone shadow.  Have people who are more technical and leading that.  People who do the paperwork, etc.14:50
jungleboyjevrardjp:  Sorry for what?14:50
njohnstonI am surprised that there has not been as much discussion about the mechanism for selecting PTLs, that most of these proposals would mean dropping the PTL election process.14:50
njohnstonjungleboyj: same for Neutron14:50
evrardjpjungleboyj: I meant I have the same concern as you, but pinged jroll instead. So I was sorry.14:50
jungleboyjevrardjp:  Ah, gotcha.14:50
jrolldo we really think core teams are so loosely connected that they won't talk amongst themselves to make sure something is dealt with?14:51
jungleboyjnjohnston:  I don't think it has to mean that.  We want to leave the possibility to have elections if a team wants, otherwise, it is just uncontested.14:51
evrardjpjroll: I raised the fact that self-organising teams sometimes work :p14:51
jrolland does having a PTL actually ensure things get done? I remember lots of grumping that PTLs weren't responding to emails in the past14:51
jungleboyj:-)14:51
evrardjpI don't think it's that way I see it14:52
njohnstonjungleboyj: But if you have PTL-of-the-week, I think elections are too much.14:52
evrardjpbut the way the community is most likely shrinking make it possible to have a more distributed communication14:52
gmannyeah14:52
jungleboyjhttps://gph.is/g/4bvjLwL14:52
evrardjpso instead of talking to 1 person for a group of people, we can maybe indeed target the group directly14:52
jungleboyjnjohnston: Oh, with that approach you are right.  I don't think that the time frame can be that short but maybe the intention could work.14:53
ricolinIMO one person just sometimes to easy to be affected when company role changing.14:53
jungleboyjUnfortunately that is much more of an issue now.14:54
evrardjpricolin: haha I agree.14:54
gmanntrue. nobody knows about those kind of changes.14:54
evrardjptbh I think that nowadays the TC liaisons for project and the PTL are kinda redundant, and inefficient14:56
gmannone way is to wait for this election and see how many vacancy in current situation and what solution can fit best14:56
evrardjpI believe we should drop one of those, and the one to drop is probably not the PTL14:57
evrardjpgmann: that's fair14:57
jungleboyjgmann:  Yeah, I think seeing what the landscape looks like after this cycle is a good idea.14:57
njohnstonDo you think that standardization of the team governance model is a feature or a bug? We could allow teams to experiment with different governance structures as long as they meet minimum requirements (documentation, conflict resolution mechanism, etc.)14:57
gmannfor example: if it is >50% PTL-less projects then surly we should change the concept of PTL to anything which can work.14:57
jungleboyjSee if we have an issue and how much of one.14:57
*** jamesmcarthur has quit IRC14:58
*** jamesmcarthur has joined #openstack-tc14:58
evrardjpnjohnston: I think what matters is empowering the teams, and decreasing the pressure on individuals (like ptl)14:58
evrardjpso if the rigid structure we have doesn't work, we need to change it indeed14:59
jungleboyjYeah.14:59
zanebas I said on the mailing list, requiring a particular PTL election process reduces variance (both in the literal and statistical senses)14:59
zanebI do think it's a valid question to ask: will the success of OpenStack be determined by our healthiest projects, or our least healthy projects?14:59
zanebif the former then we should allow teams to be more flexible15:00
zanebif the latter we should continue to try to keep the floor high and other teams will have to deal with it15:00
evrardjpI don't agree with the question, but I can understand it15:00
gmannit is difficult to answer actually.15:01
fungihaving mulled it over a while now (i have a reply i've been sitting on still), i think most of the desire to get rid of ptls and liaisons and other positions of responsibility is really a desire for teams to not need to be responsible to the community any longer. some don't want to participate in coordinated releases (or even bother having releases at all), some don't want to be required to participate15:01
fungiin cycle goals, some don't want to feel compelled to follow community consensus positions15:01
njohnstonzaneb: by the health of the projects our users depend on regardless of size or strength15:01
evrardjpfungi: that would be a net loss15:01
evrardjpand your cycle goal comment is definitely a concern for me15:02
fungii'm not judging whether it's a gain or a loss at this point, just trying to understand the underlying concerns15:02
fungirearranging governance because "it might help" seems like the wrong end to start from15:02
gmannfungi: which is issue and if that happens openstack become more harder to use/consistent etc15:02
zanebnjohnston: 'healthy' in this sense meaning effective at ensuring tasks are assigned to someone15:02
fungii get the impression there are teams who don't want (or feel that they lack the bandwidth to take on) any "tasks"15:03
zanebgmann: I agree that there's no easy answer. tbh even the question doesn't sit well with my personal politics, which is why I didn't mention it on the list15:03
jungleboyjI just have a hard time seeing benefit for OpenStack as a whole coming out of saying 'hey teams, run yourself however you want.'15:05
evrardjpfor me the problem is pressure on individuals, not the team organisation. Team can already be self-organised now.15:05
fungiit's mostly coming up now because we may end up in a position of having no ptl for nova. does nova need a ptl? how will the tc solve the lack of a nova ptl if there are no volunteers? and how will the nova team as a whole deal with an appointed ptl who has no history with the nova team (if that winds up being the solution)?15:06
fungithe nova teams seems to not want as ptl. can the tc really effectively require them to have one?15:07
* jungleboyj doesn't want to think about that. ;-)15:07
fungii hit s way too many times in that last line15:08
zaneblol15:08
evrardjpmultiplying teams like breads15:08
fungimaybe that's the solution. alternate nova timelines, one with a ptl and one without ;)15:09
fungicern could be able to help us with measuring that15:09
jungleboyj*Laughing*15:09
njohnstonLOL15:10
jungleboyjI have friends working on Quantum Computing at IBM.  ;-)15:11
fungibut in seriousness, the current options to satisfy our governance are: A. someone in the nova team volunteers to be ptl, B. someone outside the nova team volunteers to be ptl and the tc appoints them to lead nova, C. the tc declares the nova team defunct and removes nova from openstack (which will take cycles since it's in the interop requirements and the trademarked services set)15:11
fungiwhich brings us to aletrnative D. we rewrite the governance around project teams15:12
zanebor E. we all quit and go work on Project Teapot ;)15:12
fungis/work on project teapot/take up goat farming/15:12
jungleboyj*SMH*15:12
evrardjpzaneb: :)15:14
fungiproject teapot is a thing which will replace nova by being able to schedule virtual machines, or project teapot is a thing which makes virtual machines unnecessary because containers magically solve all the same problems virtualization does?15:14
fungii haven't looked too closely at the proposals15:14
zanebfungi: project teapot is a baremetal-only cloud15:14
njohnstonI see two main threads here: 1.) projects where noone has the ability to make the commitment to be the PTL because that means being the one person who commits to not passing the buck when noone wants to handle a super-unpleasant but necessary to fix problem.15:15
fungiahh, okay, so would still need opennebula or something15:15
njohnston2.) Teams that as they shrink or lose capacity revert to older, recidivist tendencies because they are known patterns (telemetry, glance)15:15
zanebfungi: you could use KubeVirt or run OpenStack on top15:16
* jungleboyj needs to read the TeaPot doc.15:16
fungizaneb: i heard kubevirt was vaporware with an empty git repo15:16
zanebhttps://9ade9145f6548dc9bbda-55b0c2ba5371c8fe68fb316789a202d6.ssl.cf5.rackcdn.com/710173/4/check/openstack-tox-docs/cfa8ab3/docs/ideas/teapot/index.html15:17
zanebfungi: maybe 2-3 years ago?15:17
fungigot it, so people are using kubevirt now? cool15:17
zanebit's actually very cool. e.g. you put a node into maintenance mode and it automagically live migrates all of the VMs off it15:18
zanebpeople are using it, but not as many as would be if there were better options for running k8s on baremetal15:19
fungiyeah, found their issues list. the fact that there are users posting operational bugs indicates it's seeing use for sure15:20
fungilooks nifty15:20
*** jaosorior has quit IRC15:20
*** e0ne has quit IRC15:22
fungicouldn't kubevirt be used to manage virtual machines which contain kubernetes pods which then use kubevirt to manage other virtual machines?15:23
*** jamesmcarthur has quit IRC15:23
fungibut you still need something to deploy the operating system/hypervisor on the physical servers still i guess15:24
mugsiefungi: everything is turtles, all the way down15:24
fungijust don't necessarily need kubernetes pods running directly on bare metal15:24
*** e0ne has joined #openstack-tc15:24
fungiand then something like metal3 to orchestrate deployment and lifecycle for the physical servers15:25
jungleboyjI like turtles15:25
fungii donate to the sea turtle rescue and rehab operation here15:26
*** jamesmcarthur has joined #openstack-tc15:27
jungleboyjNice.15:27
fungithey get overrun with cold-stunned turtles who accidentally wander into the labrador current every winter15:27
fungithey were rehabilitating something like 150 sea turtles last month15:28
fungi(and those things aren't small either)15:28
jungleboyjNo they aren't.  We support sea turtle efforts on St. George Island where we have a house.15:29
jungleboyjWe have been talking about adopting a nest.15:29
fungithey wind up filling all the outdoor bathrooms at the aquarium with kiddie pools to handle the extra15:29
jungleboyjAnyway.  So, have we reached any decision about what we might do for Nova or are we just going to wait and see.15:31
fungii don't see the tc rewriting team governance between now and the upcoming election15:31
fungithat's something which will probably take a whole cycle to reason through15:32
njohnstongmann, do you want to check with efried about who he has talked to before he disappears?  Perhaps the personal calculus will change if the alternative is a TC appointee.15:33
jungleboyjnjohnston:  ++15:33
gmannnjohnston: sure. he is going on vacation soon.15:33
jungleboyjTell them I am on my way to help and watch them panic.15:33
jungleboyjWonder if we can get smcginnis to go whip them into shape?15:34
fungito play devil's advocate, what if the tc just ignores the fact that there is no nova ptl, like as an experiment/example to find out where everything will end up going wrong?15:34
gmannnjohnston: also on V cycle goal trigger of backlogs. how about discussing it tomorrow ? as per your TZ comfort.  Today i am doing nova whole day.15:34
fungisetting aside for the moment that it may not be possible for the tc to willfully ignore its own founding document/charter15:35
jungleboyjfungi:  It is an interesting exercise.15:36
*** jamesmcarthur has quit IRC15:36
njohnstongmann: Sure thing.  I don't know what TZ you are in, but would 1600 UTC/ 1100 EST/0800 PST work for you?15:36
gmannnjohnston: i am in CST. 1600 UTC is perfect.15:38
fungibasically just let everyone who needs to interface with the nova team (to get someone to fill out a ptg space request or urge them to request a release candidate for victoria) try to find someone who is willing to temporarily serve as a nova representative. and if/when nobody can be found or offers, just not include nova in things like ptgs and coordinated releases15:39
gmannPTG are ok i think. last ptg was successful without PTL also. i am not sure release things can be excluded.15:41
fungiunderstanding that we also shouldn't expect the ptg organizers nor release team members to go out of their way to hunt people down, so they'll effectively just end up leaving the nova team/project out of openstack even if the tc doesn't officially declare nova no longer part of openstack15:41
*** jamesmcarthur has joined #openstack-tc15:45
*** jamesmcarthur has quit IRC15:45
*** jamesmcarthur has joined #openstack-tc15:45
njohnstonaccording to https://opendev.org/openstack/releases/src/branch/master/data/release_liaisons.yaml the nova release liaisons are bauzas and mriedem; if that info is current then PTL-lessness would not block releases.15:49
fungiassuming they still want to serve as liaisons, yes15:50
njohnstonright15:50
gmannmriedem might not be.15:50
jungleboyjmriedem is no longer working on OpenStack.  Not sure how involved he is.15:50
gmannyeah15:50
fungiif they don't want to serve as liaisons, there's no fallback to a ptl with no longer having a ptl15:50
jungleboyjRefer back to my Quantum computing joke earlier.  ;-)15:51
njohnstonjungleboyj: That joke is funnier given Neutron's project history ;-)15:51
jungleboyjnjohnston:  OMG, I forgot about that.15:51
fungiit'll be similar for the vmt. if we get vulnerability reports for nova we'll subscribe the nova-coresec group to them. if there's no response form them and no ptl to reach out to, we'll likely just let them sit indefinitely15:52
jungleboyjI was working on Quantum at the time and did all kinds of Quantum Leap themed presentations.15:52
njohnstonniiiice15:52
fungier, well, let them sit for 3 months and then switch them to public and let them sit indefinitely15:52
njohnstonfungi: I just wanted to say thanks - you always have really insightful analysis, and I always appreciate what you bring to the conversation.  As I am still learning the TC ropes I have learned a lot from you.  Thanks!15:59
fungiyou're welcome, but keep in mind i'm not on the tc ;)16:00
jungleboyjfungi:  So, we are looking for a f ew good people ...16:00
jungleboyj:-)16:00
fungibut yeah, if the roster of liaisons is filled out by active folks on the team then not having a ptl could work (we might need additional liaison definitions for some stuff that currently isn't quite so formalized)16:01
fungion the other hand, TheJulia was advocating for getting rid of liaisons16:02
fungiwhich is a different scenario to explore16:02
*** KeithMnemonic1 has joined #openstack-tc16:19
*** KeithMnemonic has quit IRC16:23
jungleboyjgmann:  As far as a link is concerned. https://www.openstack.org/analytics16:35
jungleboyjIs that what you guys were thinking?16:35
jungleboyjricolin: ^^^  For the user survey?16:36
gmannjungleboyj:  that will be awesome. you mean to show data (TC user survey ) in same site ? I think contributors vs user data is good to show there16:39
jungleboyjWell, there was a previous comment that we should include a link to the survey results by you.  The only thing I know of that is available online is the link above.16:41
jungleboyjThe detailed information we got is internal only.16:41
gmannoh, sorry i forgot about that comment. checking...16:41
jungleboyjI will add that link if it was what you were thinking of.  Regardless, I don't think it is a bad addition.16:42
gmanni remember now. i was thinking of link of TC survey results from where you composed the summary data16:42
clarkbI've always sort of seen one of the big roles of being PTL as being something like a project manager. Basically I'm trying to ensure that the contributors around me are about to get necessary work done (and steer effort in the right direction if its maybe showing up pointed the wrong way). You don't necessarily need a PTL to do that, nor a single individual, but I do think it helps the overall team be a16:43
clarkblot more effective in getting work done and that doesn't seem to have been covered in previous discussions16:43
jungleboyjclarkb:  ++16:44
clarkbfor me this means I spend a lot of time reviewing all 5-10 of the different things we have in the fire16:44
clarkbensuring that each one is getting enough movement to make forward progress and not stall out16:44
jungleboyjgmann:  Oh, I don't think that is intended to be public.  It is that ugly spreadsheet with all the answers.16:44
jungleboyjgmann: Most of the notes from my etherpad are already there.16:45
clarkbI think the nova PTL has done a lot of similar work historically through the management of specs and getting things in prior to feature freeze, etc16:45
clarkbbasically setting realistic expectations then pushing the team to meet them16:46
* asettle has stood down on the ML16:46
evrardjpthanks asettle16:46
asettleThank you <316:47
*** e0ne has quit IRC16:53
gmannjungleboyj: this one. link to this ML- http://lists.openstack.org/pipermail/openstack-discuss/2019-September/009501.html16:53
gmannthis does not have any actual users/deployment info16:54
jungleboyjOh, I can add that link.  I forgot that that was public.17:05
openstackgerritJay Bryant proposed openstack/governance master: Analysis of 2019 User Survey Feedback  https://review.opendev.org/69858217:17
jungleboyjgmann: ricolin  ^^^17:17
gmannjungleboyj: thanks. I will check17:19
jungleboyjCool.  Thanks.17:19
*** jamesmcarthur_ has joined #openstack-tc17:21
*** jamesmcarthur has quit IRC17:24
*** rpittau is now known as rpittau|afk17:25
*** witek has quit IRC17:32
*** evrardjp has quit IRC17:35
*** evrardjp has joined #openstack-tc17:35
zanebclarkb: I think that's part of the problem. very few people in the technical community want to become a full-time project manager, and in Nova especially it's perceived (correctly) that you basically have to18:10
*** jamesmcarthur_ has quit IRC18:10
clarkbzaneb: right, I wanted to call that out because I think that hadn't been said18:11
*** slaweq has joined #openstack-tc18:11
clarkbfor me its less the expectation of being a tie breaker vote and more that you actually have to invest quite a bit of time to help everyone else and get little time for your own itches18:11
clarkbbut at the same time that role is incredibly valuable. I would argue that any change should try to address the need for the role while making it easier on the umans18:12
clarkb*humans18:12
clarkband right now I think we are punting on the role entirely18:12
clarkb(at least with the proposals)18:12
*** diablo_rojo has quit IRC18:40
*** diablo_rojo has joined #openstack-tc18:42
*** slaweq has quit IRC18:47
*** slaweq has joined #openstack-tc18:59
*** slaweq has quit IRC19:04
*** jaosorior has joined #openstack-tc19:08
*** slaweq has joined #openstack-tc20:48
*** cgoncalves has quit IRC20:53
*** cgoncalves has joined #openstack-tc20:56
*** jamesmcarthur has joined #openstack-tc20:59
*** cgoncalves has quit IRC21:10
*** cgoncalves has joined #openstack-tc21:11
*** jamesmcarthur has quit IRC21:16
*** jamesmcarthur has joined #openstack-tc21:18
*** e0ne has joined #openstack-tc21:27
*** e0ne has quit IRC21:32
*** slaweq has quit IRC21:33
*** e0ne has joined #openstack-tc21:35
*** e0ne has quit IRC21:49
*** iurygregory has quit IRC22:18
*** jamesmcarthur has quit IRC23:14
*** jamesmcarthur has joined #openstack-tc23:20
*** jamesmcarthur has quit IRC23:32

Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!