Thursday, 2020-04-02

*** weshay|ruck is now known as weshay01:31
*** tetsuro has quit IRC02:50
*** tetsuro has joined #openstack-tc03:30
*** evrardjp has quit IRC04:36
*** evrardjp has joined #openstack-tc04:37
*** mnasiadka has quit IRC06:21
*** mnasiadka has joined #openstack-tc06:21
*** dklyle has quit IRC06:53
*** david-lyle has joined #openstack-tc06:53
*** frickler_ is now known as frickler07:05
*** slaweq has joined #openstack-tc07:08
*** tetsuro_ has joined #openstack-tc07:10
*** tetsuro has quit IRC07:13
*** tetsuro_ has quit IRC07:14
*** rpittau|afk is now known as rpittau07:17
*** tetsuro has joined #openstack-tc07:40
*** tosky has joined #openstack-tc08:02
*** e0ne has joined #openstack-tc08:15
ttxnjohnston: in the "liaisons" model, we rely on "team consensus" to designate cores and liaisons. If there is no such thing as "team consensus", the TC would step in. But in 99% of the cases those days there is team consensus, so that would just be a governance safety rail.09:02
ttxThe PTL role was originally designed as a local safety valve to make final calls. And in the early days, many such calls had to be made. But over time, that function disappeared as team consensus replaced it09:05
ttxNowadays, PTLs have become default contact points for everything, which is stressful. Since we actually only *need* accountability in very few areas (like "who has the authority to sign off on releases"), we can replace the PTL with a limited set of narrow-focused liaisons09:07
ttxThat leaves the unlikely "scenario were a safety valve would be needed. Luckily, we already have a openstack-wide safety valve, the TC. So if they ever happened, those very rare cases can be escalated there.09:08
*** tetsuro has quit IRC09:14
ttxRe: meeting chair, that can be solved with a weekly rotation between core reviewers or something, if nobody volunteers to run them all09:17
*** rpittau is now known as rpittau|bbl10:14
evrardjpdid I lose some scrollback, or are we repeating what we said a few weeks ago?11:48
* evrardjp hopes his sense of humor is well understood11:49
*** ijolliffe has joined #openstack-tc12:05
*** rpittau|bbl is now known as rpittau12:12
mnasermorning12:52
cloudnullo/13:05
gmannmorning13:05
evrardjphello everyone13:07
*** njohnston has quit IRC13:08
openstackgerritJean-Philippe Evrard proposed openstack/governance master: Clean up the TC roster  https://review.opendev.org/71699413:17
*** ianychoi_ has joined #openstack-tc13:17
*** ianychoi has quit IRC13:20
*** ianychoi_ is now known as ianychoi13:23
*** njohnston has joined #openstack-tc13:24
mnaserwhy are we doing a "cleanup" change?13:30
evrardjpIt's the first time we have that situation of not overlapping, IIRC. So I am proposing a cleanup. I don't think it's necessary, but it effectively reflects the current situation13:33
evrardjpAs discussed many times in the past, the terms have expired in March.13:34
mnaseri think historically we've all been pretty ok of just changing over once the election finishes13:35
mnaserlet's not try and be even more bureaucratic when we are tryign to reduce bureaucracy in openstack13:35
mnaserand esp when we have a few people that are running again13:35
mnaserthe logistics of remove and add, plus putting the tc at an even size for a bit seems a bit much.13:36
evrardjpI am merely reflecting conversations we had. There were concerns about the validity13:36
evrardjpI will listen to your position, as much as I listen to the position of others.13:36
mnaserthis just adds a whole bunch of headaches like who can vote on that change?  do we stop landing things for a week or two?13:38
evrardjpthat was the point that was raised.13:38
mnaserbut i guess that doesn't matter because "my term expired" so i'll sit in my 2 week timeout13:38
evrardjpplease note that I consider this a personal fail-safe.13:39
mnasera fail-safe for?13:39
fungiif the desire is to avoid people questioning the validity of decisions made with a quorum consisting of technically expired members, a workaround could be to just have the new tc re-ratify any decisions made by the current tc members in the absence of a clear quorum13:39
gmannhold on, we already changed the charter for term to be 'till next election of TC term'13:40
evrardjpgmann: yes, so we are okay with that :)13:40
fungigmann: that takes effect for anyone elected in the current election13:40
evrardjpbut the current ones are still  under the effects of the previous rules13:40
fungiit's not a time machine13:40
evrardjpas fungi says :)13:40
evrardjplet's not make a big fuss of this patch13:40
mnaserlol13:41
evrardjpand you're right fungi, it's indeed to avoid questioning the validity of the decisions.13:41
ttxGood thing we are not making any then13:41
mnasera -W on all changes13:41
mnaserif that's _really_ an issue13:41
gmannfungi: evrardjp well, i think we did that change for considering this term situation and as per bylaw range- current member can extend term till next election.13:46
gmannwhich is not going beyond 16 months or whatever it is13:46
ttxI'll just say that really NOBODY cares about the TC membership overlap or absence thereof.13:47
evrardjplet me abandon that patch real quick, so we stop talking about it?13:47
ttxIf someone is, they should be a lot more focused on other abuses, like the fact the TC can just rewrite rules as it goes13:47
ttxAND if someone really raises it as an issue, we can easily revert any change that they complain about13:48
ttxI understand the need to cross all ts and dot all is... but preemptively raising every corner case is not very productive13:49
evrardjpit took me one minute to write that patch, it takes me far more energy to discuss this13:49
evrardjpwhich I don't want to spend13:50
gmannhehe13:50
ttxexactly :)13:50
* gmann start working after coffee 13:50
*** weshay is now known as weshay|ruck13:55
fungigmann: you're thinking of the tc charter change, the bylaws say the tc has to decide in advance of the election how long the newly elected members' terms will be valid, and for the prior two elections the tc didn't say how long those terms would be so per the osf bylaws they default to 12 months. i brought it up originally in the context of considerations we should take for scheduling elections, and to13:57
fungimake sure the tc knows that it needs to actually express its member terms in the ways that the bylaws now allow it to13:57
fungi(and starting with this election, it has by amending its charter accordingly)13:58
evrardjpthat was my understanding too. The terms of the current members elected around March 2019 have expired. But let's stop this conversation, please.13:59
jungleboyjo/13:59
evrardjp#startmeeting tc14:00
openstackMeeting started Thu Apr  2 14:00:21 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
evrardjpoops14:00
evrardjpoh no, I am right, it's time for the meeting14:00
evrardjp#topic rollcall14:00
*** openstack changes topic to "rollcall (Meeting topic: tc)"14:00
gmannyeah14:00
gmanno/14:00
evrardjp#link https://media.giphy.com/media/2YtTdoSEl4m4/giphy.gif14:01
njohnstono/14:01
evrardjpo/14:01
mnasernot sure i count, but, hi, i'm here.14:01
evrardjp#link https://media.giphy.com/media/l2SpZuKuoluoknWU0/giphy.gif14:01
diablo_rojoo/14:01
evrardjp:)14:01
jungleboyjHello all!14:01
*** ianychoi has left #openstack-tc14:01
* diablo_rojo has been awake for 2 hours already14:02
jungleboyj:-)14:02
*** ianychoi has joined #openstack-tc14:02
evrardjpI think we technically have quorum :)14:02
ttxp/14:03
evrardjplet's roll14:03
evrardjp#link https://media.giphy.com/media/KR0OAYFpP7gaY/giphy.gif14:03
ttxevrardjp: :)14:03
evrardjp#topic report on tc/uc merge14:03
*** openstack changes topic to "report on tc/uc merge (Meeting topic: tc)"14:03
evrardjpWe had this in our reports meetings for a while. Now that ttx term is ending,14:03
evrardjpwe would probably need someone to keep this topic alive, or bury it.14:03
evrardjpPlease talk on the ML about what you think the next steps should be.14:03
evrardjpdoes that sound good ttx?14:04
evrardjpis that an accurate report? :p14:04
mnaserfwiw i don't think ttx cant drive it even if they're not part of the tc14:05
* mugsie slinks in late14:05
evrardjpnot disagreeing there mnaser :)14:05
mnaseri don't want to sign them up for work but they certainly are in a place with access to all the right resources at the osf14:05
evrardjpno I just want the community to be aware of what's going on14:05
evrardjpthat's merely this.14:05
mugsieI think some one on the TC should follow it, but the work can be done by anyone imho14:06
evrardjpmugsie: at least it should be clear whether we pursue this or not14:06
mugsie++14:06
ttxI'll drive simplification from where I stand14:06
evrardjpok14:06
ttxbut yes, havign a TC official relay can't hurt14:06
evrardjpwe'll make sure someone reports regularily on what's going on then14:07
jungleboyjevrardjp: ++14:07
gmann+114:07
evrardjp#action keep track of the tc/uc merger topic further14:07
evrardjpok next14:07
mnaser(i'm unsure as to why ttx can't just report themselves, but ok)14:07
ttxIf anything, driving it without wearing  the TC team jersey will facilitate14:07
evrardjpthat's true14:07
mugsiemnaser: no one is saying they can't14:07
evrardjpand yeah, we welcome the reporting from other folks :)14:08
evrardjpI think it already happened in the past multiple times! Please join! :)14:08
ttxand with more ops incoming at the election, that should be easier to convince they will keep good representation14:08
evrardjpanyway14:08
evrardjpttx: +114:08
jungleboyjYeah, that is good to see.14:08
njohnstonttx: +114:08
gmannttx: +10014:08
evrardjplet's see how it reflects in the votes :)14:08
evrardjp#topic Report on the analysis of the 2019 survey (jungleboyj), and survey 2020.14:09
*** openstack changes topic to "Report on the analysis of the 2019 survey (jungleboyj), and survey 2020. (Meeting topic: tc)"14:09
evrardjpmoving on14:09
evrardjp2019 analysis is in14:09
jungleboyjHello.14:09
jungleboyjYes.  Thank you for getting attention to it.14:09
evrardjpwhat about the trends for 2020? ;)14:09
jungleboyjSorry for causing confusion with the topic on the change.14:09
evrardjpdon't you worry about that.14:10
evrardjpthat's paperwork, I can deal with that :)14:10
gmannjungleboyj: if i remember the chat, you or aspiers will add some blog or link somewhere ?14:10
evrardjpso you don't have to*14:10
jungleboyjI think we started getting some more interesting data as I started putting %'s in place.14:10
jungleboyj:-)14:10
jungleboyjgmann:  So, it is published now.  I was hoping that aprice  might get it into one of the things that she was releasing but I didn't see that happen.14:11
evrardjpDo we need further analysis on the 2019, and iterate over the text there? Or should we jsut wrap up 2019, and keep the framework for 2020?14:11
gmannperfect, i want to circulate that to company side also.14:11
evrardjpgmann: awesome!14:11
evrardjpgmann:14:11
evrardjp#link https://governance.openstack.org/tc/user_survey/analysis-12-2019.html14:12
jungleboyjLet me follow up with aprice to see where a good place to socialize this more might be.14:12
gmann+114:12
jungleboyjI have been meaning to send out a tweet with the link too.  Will do that now.14:12
evrardjp:)14:12
jungleboyjDoes anyone know how soon we will see the 2020 results?14:12
evrardjpI don't know. Could you ask aprice? :)14:13
jungleboyjYeah.  I will.14:13
evrardjpawesome. let's report on the next meeting then14:13
jungleboyjI would like to do that analysis sooner as I think it will be more interesting as we will have more than one data point.14:13
apricejungleboyj: we incorporated it into a lot of direct outreach that we did last week for the user survey14:13
evrardjpoh, aprice! wonderful :)14:14
jungleboyjaprice:  Ah, ok.  I must have missed that.14:14
jungleboyjThat is great.  Thank you!14:14
apricei do think that we can think about different ways to socialize it more as well, but there are also other places like on Superuser where we are plugging it in14:14
apriceyeah - it's that time we bug people to take the survey, so we used that link to show them how the upstream community really cares about their feedback14:14
apriceso thank you all :)14:14
jungleboyjaprice:  Good.14:14
gmann+1 on putting on Superuser.14:14
jungleboyjAny idea when we will see the next results?14:15
apricei can think about a few ideas and share with yall if you would like14:15
gmannand to BoDs too :)14:15
aprice+114:15
*** witek has joined #openstack-tc14:15
*** asettle has quit IRC14:15
jungleboyjaprice:  Please do.14:15
evrardjpour pleasure aprice! I'm glad people can see that we care about their opinions, and want to learn from this!14:15
*** asettle has joined #openstack-tc14:15
evrardjpaprice: awesome!14:15
asettleWHAT A HUSTLE OMG I HATE LINUX14:15
asettleHello o/14:15
apricedefinitely!14:16
evrardjpasettle: hahahah14:16
evrardjpyour ircnickname (in my client) is green too. Just saying.14:16
jungleboyjasettle:  I think that messaging is off brand.  ;-)14:16
mugsieasettle: no comment14:16
evrardjphaha14:16
evrardjplet's go on14:17
evrardjp#topic Report on telemetry14:17
*** openstack changes topic to "Report on telemetry (Meeting topic: tc)"14:17
jungleboyjevrardjp:  Sounds good.14:17
evrardjpricolin_: anything to report?14:17
evrardjpshould we consider all is fine now, and the crisis is averted? ;)14:17
asettlejungleboyj, nah mate super on brand for my goddam week.14:17
asettleWhatever, mdae it14:17
ttxasettle is obviously orange14:17
asettleevrardjp, I'm green?14:18
evrardjpttx: hulk is definitely green. And she is working at SUSE, so moar green. You have to guess why I said green now.14:18
jungleboyj:-)  Yes you are.14:18
asettleCause I'm green with ... hate14:18
evrardjpOr maybe because she cares about environment? Who knows...!14:18
evrardjpanyway14:18
* jroll is suuuuper late but now here14:19
evrardjpI think we can leave the telemetry topic on the agenda for next meeting14:19
evrardjpwoot jroll!14:19
asettlejroll, I just got here too14:19
gmannevrardjp: +114:19
evrardjp#topic report on stable branch policy work14:19
*** openstack changes topic to "report on stable branch policy work (Meeting topic: tc)"14:19
evrardjpthis has been there for months, still no progress to report afaik14:20
evrardjpmnaser, any update?14:20
evrardjplast action item was you were okay to push an update to distill what happened on the ML in terms of stable branch policy14:20
jungleboyjhttps://gph.is/26kKW1Y14:20
mnaserno, i went over the mailing list thread and honestly felt like we ended up with many different options14:20
evrardjpshould we at least document it, to say that we've tried to change it, and it wasn't successful due to lack of consensus?14:21
mnaseri think our entire stable and upgrade policy needs to be cleaned up and simplified14:21
mnaseri will push up a change in what i think is best for our community given the feedback14:22
evrardjpI think this isn't too far from my idea. I will tackle a documentation.14:22
mnaseri have a lot less going on than every time we talk about this14:23
evrardjpI have written a large idea already. If you want to think of a large change, I would welcome you to contribute to it. I will push that tomorrow.14:23
evrardjpok let's move on, it seems we know the next steps14:23
evrardjpI will work with you on this mnaser14:23
evrardjp#topic report on the community goals14:23
*** openstack changes topic to "report on the community goals (Meeting topic: tc)"14:23
evrardjpgmann: do you want to say a few words?14:24
gmannU cycle goal progress:14:24
gmannContributor guide goal progress is here: http://lists.openstack.org/pipermail/openstack-discuss/2020-March/013381.html14:24
gmanndiablo_rojo: can add if anything more14:24
gmannthis is py2 drop goal updates: http://lists.openstack.org/pipermail/openstack-discuss/2020-April/013777.html14:24
gmann#link http://lists.openstack.org/pipermail/openstack-discuss/2020-March/013381.html14:25
gmann#link http://lists.openstack.org/pipermail/openstack-discuss/2020-April/013777.html14:25
diablo_rojoI think its pretty straight forward.14:25
diablo_rojoMaking progress, slowly but surely.14:25
gmannpy2 drop is very close, few projects are still left and i am reaching out to them and get those merge14:25
gmannI am going to start the audit soon, may be next week or so14:25
jungleboyjWell, the list of participating projects is a good start.14:26
jungleboyjgmann:  ++ That is great.  Thank you for all the work there.14:26
evrardjpgmann: That's a big milestone14:26
gmannfor V cycle goal: This also has two possible candidates with champion14:26
gmann#link http://lists.openstack.org/pipermail/openstack-discuss/2020-March/013528.html14:26
gmann#link https://etherpad.openstack.org/p/YVR-v-series-goals14:26
gmannitems 3rd and 4th in that etherpad.14:26
gmannwe are hoping to get those goal proposal soon, may be after u-314:27
evrardjpI would love to see those happen.14:27
gmannme and njohnston will continue tracking on those14:27
njohnstonindeed14:27
gmannOSC migration as multi cycle goal is something i am positive about but lets see14:27
gmannthat is all from my side.14:27
evrardjpyes! lbragstad and I were super thrilled to put that in our list a certain time ago. Let's not repeat mistakes of the past! :)14:28
evrardjpanyway14:28
gmann:), sure lets try again.14:28
* evrardjp and his old memories :)14:28
evrardjp#topic Report on the OSF board initiatives14:29
*** openstack changes topic to "Report on the OSF board initiatives (Meeting topic: tc)"14:29
evrardjpmnaser do you have anything to tell us from the board perspective, as you're our man there? :p14:29
mnaseri just want to speak about this, i'm not sure how this ended up on the agenda14:30
mnaserbut just to be clear, while i sit on the board, the best thing to do is to rely on the updates that jbryce publishes post board meetings/discussions, as i wouldn't feel comfortable being a "spokesperson" from the board towards teh community and the implications of that14:31
evrardjpit was regularily on the agenda... I think the last 6 months. Nothing much to usually report though14:31
mnaseri'll gladly be the other way around as a bridge of the community towards the board, but i'd be more comfortable letting folks who know this stuff better than me for now :)14:31
mnaser(and really, i'm still settling down adn figuring it all out)14:32
evrardjpok let's move on then14:33
evrardjp#topic Moving OpenDev discussion forward14:33
*** openstack changes topic to "Moving OpenDev discussion forward (Meeting topic: tc)"14:33
evrardjpI think that topic was raised by clarkb14:34
mnaserchange has landed already, opendev is a thing, it might have been added before the change landed afaik14:34
clarkbya, I put it on the agenda back when I wasn't sure what needed to be done to make progress here14:34
evrardjpyes, it's probably worth reporting what happened, for the folks who haven't followed?14:35
evrardjpAny of you two care saying a few words?14:35
clarkbsince then we've made progress. If you are wondering what the next steps are on the OpenDev side we plan to spin up proper mailing list and meeting channels so that historical record of progress from this point can be recorded in places people are likely to look at them in the future14:35
evrardjp(or pointing to links)14:35
evrardjpok14:36
evrardjpthanks for the report!14:36
clarkbessentially we've formalized the (long) planned spin off of openstack-infra software hosting activities into opendev. The two major changes that I wanted to bring up here if we hadn't made progress were removing related infra projects from openstack/goverance and adding the basis of opendev governance to opednev docs14:36
clarkbformally electing a leader and building the advisory board of involved individuals is the next thing that we wwant to do on the new mailing list14:37
mugsieglad to see it happen :)14:37
evrardjpmugsie: +114:37
evrardjpawesome14:37
clarkbonce the mailing list is up I'll send out subscription invites to the various project lists so those that are interested don't miss these conversations14:37
clarkband that way history ends up preserved where people expect it (rather than say openstack-infra mailing ist)14:38
evrardjpI like it14:39
evrardjpGlad to see you're not blocked, and this is moving forward14:39
evrardjpok let's move on14:39
evrardjplast topic for today14:39
clarkbyup EOD from me thanks14:39
clarkber EOT14:39
evrardjpthat was a short day :p14:39
evrardjphaha14:39
evrardjp#topic Technical Election Nomination Period Results14:39
*** openstack changes topic to "Technical Election Nomination Period Results (Meeting topic: tc)"14:39
evrardjpdiablo_rojo: do you want to say a few words?14:40
diablo_rojoYeah.14:40
diablo_rojoSo. Basically we had 16 projects without PTL nominations in before the close14:40
jungleboyj:-(14:40
diablo_rojoThere's a discussion going on in this etherpad for what to do: https://etherpad.openstack.org/p/victoria-leaderless14:40
diablo_rojoa few have had people step up, but there are a number that require discussion.14:41
mnaserbtw -- did we decide about tobias' nomination?14:41
evrardjpthere were 7 in Ussuri IIRC14:41
diablo_rojomnaser, the election officials feel that because his nomination wasn't into gerrit in time, that its not valid14:41
gmannwe are 9 with  no leader seems. I am positive on getting someone for tacker14:41
diablo_rojoIts a hard line, but I think its good to maintain a clear policy.14:42
mnaserdiablo_rojo: ok so even if their ML post for nomination came before that?14:42
diablo_rojoIf we had know he was having issues, we could have helped him.14:42
evrardjpgmann: I saw that, it's awesome.14:42
diablo_rojomnaser, yeah I think we are treating the elections repo in gerrit as the source of truth.14:42
mugsieyeah, the repo as the source of truth has been the thing for a while14:43
mnaserfair. i'd encourage in the future for people to not post to teh mailing list in the future14:43
mnaserthat way a new comer doesnt feel like "ok i sent my email, im good to go"14:43
gmanni really feel to relax the nomination things especially for 'Foundation Membership which automatic get disable for no vote in election for a year'14:43
mnasernot saying tobias is, but i can imagine someone seeing it that way :)14:43
fungihttps://governance.openstack.org/election/#how-to-submit-a-candidacy doesn't mention a need to send candidacies to the mailing list at all, for what it's worth14:43
ttx#link https://etherpad.openstack.org/p/victoria-leaderless14:43
mnaserbut yeah, we're having more and more leaderless projects14:43
mugsiemnaser: yeah, there was talk of automting the nomination to the ML to clarify this, but I think it came into E_NO_TIME14:44
jungleboyjfungi:  Yeah, that has always kind of just been something people do.14:44
evrardjpttx: thanks for doing so :)14:44
mnaserlets all leave commenst about the leaderless projects in the etherpad14:44
mnaserand then maybe discuss during office hours14:44
gmann+114:45
jungleboyjSo, dumb question on the Tobias situation will it default to a volunteer that is then Tobias?14:45
fungiare you soliciting input from non-tc-members in that etherpad, or just tc members?14:45
mnaserfungi: i think everyone should put comments there, not to limit to certain people :)14:45
mugsiejungleboyj: Tobias was running for the TC14:45
mnaserjungleboyj: in the case of tobias they were running for at tc seat14:45
fungijungleboyj: if you mean tobberydberg, he was submitting a candidacy for a seat on the tc, not as a ptl for a prohect14:45
fungiproject14:46
diablo_rojofungi, I think I am fine with anyone submitting opinions.14:46
jungleboyjDoh.  Ok.  I missed the context there.14:46
mnaserso if any non-tc members that are sitting here quietly reading this meeting14:46
mnaserfeel free to leave comments14:46
jungleboyjBummer that that got messed up.  Ok.14:46
mnaser(previous tc members dont count, we know fungi will always be around :P)14:46
jungleboyjHe he.14:46
fungidiablo_rojo: mnaser: thanks, in that case the infra team can take the opportunity to explain in the etherpad why they didn't produce a ptl candidate and what they actually want to do14:46
diablo_rojofungi, yeah that sounds good. Please do!14:47
mnaserfungi: yes, i think i have a very vague idea of where it might be going given the current direction14:47
jungleboyjfungi:  ++ Yeah, the discussion in there is good and should have all parties involved.14:47
diablo_rojoBasically I just wanted people to make aware of the etherpad as we will need to figure that all out at some point.14:47
gmannany deadline for that ?14:48
evrardjpasap?14:48
gmannbefore final release or after14:48
mnaserthere is none but logistically it's probably better to have it cleared out14:48
diablo_rojogmann, I think it would be nice to have decided by the time the rest of the election closes/ the final release yeah.14:48
* diablo_rojo puts election official hat on14:48
ttxfwiw I was CC-ed on an email from the CloudKitty PTL to the list that never made it14:48
gmannok14:48
diablo_rojoevrardjp, can you also tag the repo for us so we can generate the electorate?14:48
ttxMaybe some weird moderation issue14:48
mugsieyeah, we have had some of the appointmes drag on for weeks after elections14:48
mnaserdiablo_rojo: what was the tag name again?14:49
ttxfungi: is there anything from jferrieu in the moderation queue ?14:49
mnaserttx: fungi mentioned that over teh weekend the ML did oom a bunch of times14:49
diablo_rojomnaser, uhhh I think its normally $year-$month-elections or something like that?14:49
ttxcould be that he used a non-list email14:49
* evrardjp facepalms14:50
mnaserdiablo_rojo: yeah, we count this as april or march?14:50
fungittx: i'll take a look, haven't checked it yet this morning14:50
diablo_rojomnaser, april? cause thats when the polling will happen and the elections will conclude?14:51
evrardjpdiablo_rojo: seems like mnaser wants to handle this?14:51
diablo_rojoevrardjp, lol seems like it :)14:51
mnaseri'm helping driving the discussion14:51
fungimnaser: the memory issues only delayed deliveries by part of a day14:51
mnaserand helping understand what we'll be doing14:51
mnaserso i guess the tag should be apr-2020-elections14:51
mnaserbased on the previous history: https://review.opendev.org/#/admin/projects/openstack/governance,tags14:52
diablo_rojomnaser, works for me :) I had the details right and the order wrong14:52
mnaseryep14:52
mugsiewe still have one topic left, so tagging logistics can be done off line, rigth?14:52
evrardjpI agree14:52
evrardjplet's move on14:52
mugsienot sure if prakesh is here though14:52
fungiSubject: [election][cloudkitty][ptl] Announcing my PTL candidacy for CloudKitty (Justin Ferrieu)14:52
fungiReceived: Thu Apr 2 10:14:56 202014:52
fungiapproving it now14:52
mugsieprakash*14:52
evrardjpprmachan ?14:53
evrardjp#topic refstack 202014:53
*** openstack changes topic to "refstack 2020 (Meeting topic: tc)"14:53
fungievrardjp: usually "pramchan" in irc14:53
evrardjpI just copy-pasted :)14:53
mugsiehe emailed the board list last night to say he would be here, but I don't see him14:53
gmannnot sure if he joined.14:54
evrardjpI don't see him here at least14:54
evrardjpand he didn't answer on my ML14:54
evrardjpmail*14:54
evrardjpso I wasn't sure if showing up or not14:54
evrardjplet's hope this will be for the office hours then14:54
evrardjpthanks everyone for joining!14:54
evrardjp#endmeeting14: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/"14:55
openstackMeeting ended Thu Apr  2 14:55:03 2020 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:55
openstackMinutes:        http://eavesdrop.openstack.org/meetings/tc/2020/tc.2020-04-02-14.00.html14:55
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/tc/2020/tc.2020-04-02-14.00.txt14:55
openstackLog:            http://eavesdrop.openstack.org/meetings/tc/2020/tc.2020-04-02-14.00.log.html14:55
gmannthanks everyone and  evrardjp for chair14:55
jungleboyjThanks!14:55
mugsiere: refstack I suppose from the TC side - we need to decide if we a: care, b: want to do anything for the trademark program14:55
ttxThanks!14:55
njohnstonthanks evrardjp and everyone14:55
mugsiethanks evrardjp14:56
ttxmugsie: my personal opinion is... if the board does not care about it, it's not our role to sustain it14:56
ttxWe should support the board leading that14:56
ttxand answer all questions they have, provide required test coverage etc14:56
mugsieyeah, but I care about the outcome of the program, which enforces at least some layer of interop14:56
evrardjpmmm14:56
evrardjpagreed with mugsie14:56
ttxbut if there is no interest at board level in having trademark programs... it's not our role to maintain it14:57
evrardjpopenstackclient and sdk programs do, too, I think14:57
fungithat thread previously went down a rabbit hole of how to add airship tests to tempest for an airship interoperability trademark program, so there's probably still some confusion among one or more board members as to what the openstack interop, refstack and tempest relationship is14:57
evrardjpcould you clarify maintain "it" ?14:57
ttxmugsie: I'm not convinced it does increase interoperability14:57
mugsieno. but iof the issue is with maintaining the testing tools, that *could* come into our remit14:57
mnaserso14:57
gmannttx: +1 and we also do know if provider care any more. may be first question is who need it14:57
mnasergoing back to tagging14:58
evrardjpmugsie: +114:58
mnaseri just rememberd that we used the releases repo for tagging in the last election14:58
mnaserhttps://opendev.org/openstack/releases/commit/c90e38b3adac969bdb45a6dd57b5050a7870768014:58
mnasercc evrardjp diablo_rojo14:58
mugsiettx: you don't think so?14:58
mnaserour interop story is so hard14:58
evrardjpmnaser: yes, that's where I intended to do the patch14:58
ttxmugsie: I mean, in practice.14:58
gmannFrom tempest side, we keep continue the interop as one of user and support for maintaining/adding new tests14:58
mugsieI think inside of HPE there is defnietely teams who would have done a hard API breaking change to fix bugs14:59
mnaserif i have to decide what image uuid o or name i need to use per cloud14:59
ttxIt's a program where you submit results that say "I pass"14:59
mugsiethere was*14:59
mnaserit isn't interop14:59
mnaserwe all have our feelings about dockerhub but the fact that it's a central repo that are namespaced which lets you pull in any image14:59
mugsiemnaser: yeah, that is hard, but being able to use the same terraform plugin to do it *is* a level of interop14:59
mnaserthat can drive it14:59
mnasersure15:00
mugsiethats what i care about15:00
mnaseri will agree that it is a level of interop but15:00
mugsieWould I prefer the Azure image selection logic? 100%15:00
mnasermugsie: pls give us all your azure trade secrots15:00
mnaseri promise not to tell nobody15:00
mugsie:D15:00
mnaserno bamboozle15:01
ttxI wonder basically if having a text description of the services that need to be in an openstack cloud and ask people to sign a document that say "yes I run those" would not have the same effect and be 10 times easier to maintain, is all15:01
mnaserttx: given that the current process _is_ self-certification15:01
ttxexactly15:01
mnaserif someone was to not be honest about it, they wouldn't be honest about it in both ways15:01
ttxsame effect, less maintenance cost15:02
mnaserregardless if they wrote an assertion, or they just setup devstack in a vm, took the results and posted them15:02
mnaserif we're not "auditing" it ourselves, it's probably mostly meaningless15:02
ttxAnd signing a document that says "I swear its this way" is actually more committing that submitting supposedly-not-curated test results15:02
* mnaser looks at boeing and FAA15:02
mugsietrue. we should probably keep the tests still in that case to say in the signed thing "my tests passed"15:02
mnasermugsie: but if we do that, then we have to maintain a list of tests15:03
mnaserand have a system to manage/submit/deal with them15:03
mnaserand have people to keep track of that15:03
mugsierunning nova, and running nova with a crap tron of api-extenttions are two very different things15:03
ttxI see one good reason to keep it -- it's good that people have a way to check that they are compliant15:03
mugsiettx: ++15:03
ttxbut as an interoperability forcing function ? meh15:03
ttxnot convinced :)15:04
gmannmugsie: no more extensions way in nova now :)15:04
ttxI mean, if there is a lot of interest from the ecosystem, resulting in a lot of board members motivated to drive it, I don;t mind15:04
*** pramchan has joined #openstack-tc15:05
gmannpramchan: is here15:05
ttxBut if there is no interest at that level, I don;t think we should keep it just because it's something we always did15:05
mnasernow15:06
mnaserleaderless projects?15:06
ttxIt's valuable if the ecosystem finds it valuable, basically15:06
mnaserdo we want to talk through those?15:06
ttxmnaser: I think people should just weigh in on the etherpad for now15:06
mnaserttx: fair 'nuff15:07
diablo_rojoI am double meeting-ing atm so I might have to catch up later.15:07
ttxOslo is the main pain point15:07
pramchanI am in15:07
mugsiethere does seem to consenus building in there15:07
pramchanHi all pramchan here regards to regards to Refstack15:07
jungleboyjYeah, there is an OSF update meeting right now for those who may not know.15:08
*** david-lyle has quit IRC15:08
fungi"community meeting" (conference call)15:08
pramchanYe I am on that while I can have few questions answered here15:08
*** dklyle has joined #openstack-tc15:08
pramchan#link httpd://refstack.openstack.org15:09
pramchanThis has the 2020 latest runs for 2019.11 based runs for the latest Train release15:10
ttxpramchan: hi!15:10
pramchanyes15:10
evrardjppramchan: hi!15:10
pramchanyes15:11
pramchanwe do need to add a blueprint for train and get board approval so that it can cover (R,S,T) release and we can implement it15:12
*** dmellado has quit IRC15:14
pramchanSo will need volunteers to do that, after Interop WG meeting which I will discuss in community call now and here is the link15:15
pramchan#link https://opendev.org/openstack/refstack/src/branch/master/specs/15:15
fungihas the board of directors found any volunteers yet?15:15
fungior you're just hoping the tc members will be able to help get the word out that you're looking for some volunteers?15:16
gmannpramchan: volunteer on defining and ,maintaining guidelines or its execution tool refstack ?15:17
pramchanfungi I need atleast one volunteer to submit the patch for submiting once we have decoded the tests to use15:17
pramchanSo yes hoping to cathcup with new PTL of Tempest15:18
fungithat'll be masayukig, the upcoming quality assurance team volunteer15:19
gmannI think it is separate things from QA (Tempest). we maintain tests in Tempest and can continue to do that15:19
gmannpramchan: and refstack was not under QA15:19
fungiand yes, the interoperability guidelines haven't traditionally been maintanied by the quality assurance team or the tempest developers, it's been handled by the osf board of directors interoperability working gruop15:20
pramchanmasayukig and will work with mann to define what to expect after I get Boards approval for the tests to use for Train15:20
pramchanI am represnting Interoperability group from Board and once ready with test come back15:20
pramchanIf you have any advice todo or not please advice -Thanks15:21
pramchanAlso you can send email to pramachanATyahooDOTcom '15:22
ttxThanks for helping driving that process forward, pramchan !15:22
gmannpramchan: we have QA office hour on every Tuesday 13.30 UTC on #openstack-qa, please ping us there for help or question from Tempest side- https://wiki.openstack.org/wiki/Meetings/QATeamMeeting15:25
fungifor the record, here are the people with permission to approve changes into the openstack/interop project where the guidelines are maintained: https://review.opendev.org/#/admin/groups/626,members15:25
ttxyeah so those were the board members previously involved15:26
ttx+ Chris that was helping from the OSF side15:27
*** dmellado has joined #openstack-tc15:30
mnaseryep15:36
jungleboyjUgh, I missed the note on the virtual PTG planning this morning.  Sorry diablo_rojo15:43
clarkbjungleboyj: there are two more meetings next week15:44
clarkb6th and 7th at times I don't remember15:44
jungleboyjYeah, putting them on the Calendar now.15:44
jungleboyjJust found the e-mail.15:44
diablo_rojojungleboyj, no worries, there are other opportunities.15:45
jungleboyj:-)15:45
diablo_rojo(thats why I was up even before the crack of dawn)15:45
jungleboyjSo that is why you were up at 5 am.15:45
diablo_rojojungleboyj, yessir15:45
gmannis that sent on ML? or i missed those15:46
diablo_rojowith 4.5 hours of sleep and running the meeting15:46
jungleboyjI had one of those meetings last week.  So much fun.15:46
diablo_rojogmann, yeah I sent it to the ML15:46
diablo_rojowe also sent it directly to those that volunteered to help15:46
gmannohk i remember. and added 6th and 7th one.15:48
jungleboyjYeah.  On my calendar now.15:48
*** jamesmcarthur has joined #openstack-tc15:55
*** rpittau is now known as rpittau|afk15:56
fungittx: evrardjp: moving the governance tagging discussion here, the election officials actually pass the name of the git tag to their tooling to generate the electoral rolls, so the tag itself exists first16:05
fungihttps://governance.openstack.org/election/process.html "Once the email deadline is reached[...]Ask the TC chair to tag the governance repository"16:06
fungiwhich i suppose now that we have release automation, could be election officials propose the tag in the releases repo, then the tc chair approves it16:07
fungior confirms it16:07
evrardjpyup16:07
evrardjpI proposed a patch in releases for that16:07
evrardjpbut I am not sure which SHA was used for the generate-rolls (and if it ran already or not). Let's discuss that in election16:08
diablo_rojoThank you evrardjp!16:08
diablo_rojoevrardjp, the rolls havent been generated yet16:09
fungievrardjp: it hasn't been run yet, it gets run after the tag has been created16:09
fungithe rolls are run against whatever is tagged16:09
diablo_rojoYeah. That.16:09
*** jamesmcarthur has quit IRC16:11
*** jamesmcarthur has joined #openstack-tc16:12
*** jamesmcarthur has quit IRC16:16
smcginnisdiablo_rojo: I've heard negative feedback and concern from a few people now. Any chance we can move those community meetings off of zoom onto jitsi or something? At least until zoom isn't suffering multiple zero day exploits and sending tracking info to Facebook?16:16
fungismcginnis: you can count me in the set of people with those concerns about zoom16:17
diablo_rojosmcginnis, I will bring it up to people right now. I feel like I've asked before and don't remember: is jitsi available in China?16:17
*** witek has quit IRC16:17
smcginnisNot entirely sure, but we could always host our own instance to make sure it is.16:18
* smcginnis says like hosting and maintaining a communications platform is no big deal16:18
*** jamesmcarthur has joined #openstack-tc16:18
diablo_rojosmcginnis, lol16:19
diablo_rojoI am not volunteering for that job.16:19
*** jamesmcarthur has quit IRC16:21
fungiyou're clearly not following the conversation in #opendev ;)16:23
evrardjpmatrix has webrtc16:33
evrardjpwow16:34
evrardjpthat was wrong16:34
*** jamesmcarthur has joined #openstack-tc16:34
evrardjpriot can do conferences by relying on matrix for signalling webrtc16:34
mnasersmcginnis: fyi i recently learned this but zoom actually has a webrtc interface16:34
mnasersmcginnis: just refuse to start the download a few times, refresh the page and it will pop up asking you if you want to start zoom in your browser16:35
smcginnisYeah, it's pretty limited, but probably works for this type of meeting.16:35
fungimnaser: huh, that's good to know!16:36
*** evrardjp has quit IRC16:36
*** evrardjp has joined #openstack-tc16:36
mnaserfungi: https://support.zoom.us/hc/en-us/articles/214629443-Zoom-Web-Client16:37
*** asettle has quit IRC16:48
mordredsmcginnis: to echo what fungi was just saying - we're working on a jitsi/etherpad solution right now- still several kinks to work out related to browser support and whatnot17:01
smcginnismordred: Awesome, very nice!17:02
mordredand it is, in fact, a self-hosted thing17:02
*** KeithMnemonic has joined #openstack-tc17:28
*** jamesmcarthur has quit IRC17:28
*** jamesmcarthur has joined #openstack-tc17:29
*** jamesmcarthur has quit IRC17:54
*** jamesmcarthur has joined #openstack-tc17:55
*** jamesmcarthur has quit IRC18:24
*** jamesmcarthur has joined #openstack-tc18:25
*** jamesmcarthur has quit IRC18:26
*** jamesmcarthur has joined #openstack-tc18:26
*** diablo_rojo has quit IRC18:26
*** diablo_rojo has joined #openstack-tc18:29
*** pramchan has quit IRC19:01
*** jamesmcarthur has quit IRC19:15
*** jamesmcarthur has joined #openstack-tc19:16
*** jamesmcarthur has quit IRC19:16
*** jamesmcarthur has joined #openstack-tc19:16
*** jamesmcarthur has quit IRC20:02
*** jamesmcarthur has joined #openstack-tc20:02
*** jamesmcarthur has quit IRC20:19
*** jamesmcarthur has joined #openstack-tc20:26
*** iurygregory has quit IRC20:38
*** iurygregory has joined #openstack-tc20:39
*** weshay|ruck is now known as weshay20:57
*** jamesmcarthur has quit IRC21:03
*** jamesmcarthur has joined #openstack-tc21:03
*** e0ne has quit IRC21:06
openstackgerritTim Burke proposed openstack/election master: Adding Tim Burke candidacy for Swift  https://review.opendev.org/71637921:06
*** slaweq has quit IRC21:07
*** jamesmcarthur has quit IRC21:08
*** iurygregory has quit IRC21:12
*** slaweq has joined #openstack-tc21:14
*** jamesmcarthur has joined #openstack-tc21:26
*** jamesmcarthur has quit IRC21:26
*** jamesmcarthur has joined #openstack-tc21:26
*** slaweq has quit IRC21:26
*** openstackstatus has quit IRC22:56
*** openstack has joined #openstack-tc22:58
*** ChanServ sets mode: +o openstack22:58
*** tosky has quit IRC23:00
*** ijolliffe has quit IRC23:44

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