Thursday, 2019-09-05

*** diablo_rojo has joined #openstack-tc00:02
*** zhurong has quit IRC00:38
*** markvoelker has joined #openstack-tc01:00
*** markvoelker has quit IRC01:05
*** zhurong has joined #openstack-tc01:21
*** markvoelker has joined #openstack-tc02:01
*** markvoelker has quit IRC02:05
*** jamesmcarthur has quit IRC02:49
*** jamesmcarthur has joined #openstack-tc02:50
*** jamesmcarthur has quit IRC02:55
*** jamesmcarthur has joined #openstack-tc03:20
*** markvoelker has joined #openstack-tc03:31
*** markvoelker has quit IRC03:41
*** ricolin has joined #openstack-tc03:49
*** markvoelker has joined #openstack-tc04:30
*** markvoelker has quit IRC04:35
*** jamesmcarthur has quit IRC04:47
*** Luzi has joined #openstack-tc04:55
*** adriant has quit IRC05:11
*** adriant has joined #openstack-tc05:12
*** jamesmcarthur has joined #openstack-tc05:17
*** jamesmcarthur has quit IRC05:22
*** markvoelker has joined #openstack-tc05:30
*** markvoelker has quit IRC05:35
*** njohnston has quit IRC06:15
*** jamesmcarthur has joined #openstack-tc06:19
*** jamesmcarthur has quit IRC06:23
*** zhurong has quit IRC06:37
*** openstackgerrit has quit IRC06:51
*** jamesmcarthur has joined #openstack-tc06:59
*** markvoelker has joined #openstack-tc07:06
*** jamesmcarthur has quit IRC07:06
*** markvoelker has quit IRC07:10
*** tosky has joined #openstack-tc07:23
evrardjptimburke: sorry I paraphrased.07:34
evrardjpit's exactly what I thought though :)07:34
*** zhurong has joined #openstack-tc07:53
*** jamesmcarthur has joined #openstack-tc08:02
*** jamesmcarthur has quit IRC08:07
*** e0ne has joined #openstack-tc08:41
*** markvoelker has joined #openstack-tc08:45
*** markvoelker has quit IRC08:50
*** jamesmcarthur has joined #openstack-tc09:04
*** jamesmcarthur has quit IRC09:08
*** openstackgerrit has joined #openstack-tc09:34
openstackgerritThierry Carrez proposed openstack/governance master: Update member roster based on Sept 2019 election  https://review.opendev.org/68035609:34
gmanntimburke: and that is for U master also or until Train (stable) branch only?09:39
gmannbecause if we remove the py2.7 support in U cycle then we still keep the py2.7 support until stable/train for every project.09:40
*** jamesmcarthur has joined #openstack-tc09:40
*** jamesmcarthur has quit IRC09:45
toskyand now that we have Extended Maintenance, that means a loooong time09:50
*** njohnston has joined #openstack-tc09:59
gmanntosky: yeah but I do not expect much maintenance cost as it will be all stable branches only and less code flow there.10:36
toskygmann: sure; it's just means more care when touching the code to not break it (even though the tempest jobs should catch issues)10:37
gmannyeah. Tempest need to keep all those py2.7 jobs until Train EM10:38
gmannon Tempest master10:38
*** jamesmcarthur has joined #openstack-tc10:41
*** jamesmcarthur has quit IRC10:46
*** markvoelker has joined #openstack-tc10:46
*** markvoelker has quit IRC10:52
*** jamesmcarthur has joined #openstack-tc11:18
*** jamesmcarthur has quit IRC11:23
*** lpetrut has joined #openstack-tc11:27
*** jamesmcarthur has joined #openstack-tc12:00
*** markvoelker has joined #openstack-tc12:02
openstackgerritGraham Hayes proposed openstack/governance master: Update Project Liasons for new TC roster  https://review.opendev.org/68038612:07
mugsiegmann: we never said we would force projects to drop 2.7 - just that they could12:12
mugsiethe updates just removes the *requirement* to test on 2.712:12
gmannmugsie: if we remove the test on 2.7 then project needs to say no-support-for-py2712:13
gmanni mean we have to do it when py2.7 is going to be removed in Jan 202012:13
mugsiesure, but us removing the 2.7 from the U PTI doesn't mean that tempest can remove 2.7 in U12:14
mugsieprojects can start dropping it as they see fit, but we are not forcing them to drop it (yet)12:14
gmannTempest case is different Tempest master is running on all stable branch so we need to tests 2.712:15
mugsietempest will be stuck for a long time with 2.7 I think12:15
gmannyeah we are not forcing to remove now but when we will plan the same in U cycle then project can remove the py2.7 gate and also classifier from setup.cfg to remove the support of py2.712:16
gmannyes, Tempest might be able to remove in Y or Z :)12:17
toskyit's the same for the tempest plugins then; maybe worth highlighting this, as each project may accidentally remove py2 support from them12:21
mugsieyea, thats a good point12:22
* mugsie has nearly done it with old API tests in the past12:22
gmanntosky: yes. we are keeping py35 testing also on all tempest plugins so same plan we need to follow for py2.712:22
*** Sundar has joined #openstack-tc12:24
gmannMay be it will be good to mention the same in PTI runtime doc so that we do not miss12:24
toskyyes, that's the idea12:24
SundarHello, for the projects where no PTLs have been elected yet, it was said that TC will follow up. I had sent an email announcing candidacy for Cyborg PTL and subsequently filed https://review.opendev.org/679912 . What else should I do now?12:25
gmannSundar: fungi or someone else will update the new PTL names in governance and on top of that you can propose the patch to add your name as cyborg  PTL. then TC will approve that.12:30
Sundargmann: Thanks.12:32
*** ijolliffe has joined #openstack-tc12:36
asettleo/12:54
* mugsie will be a few minutes late to the meeting12:56
asettlemnaser, do we need gif game?!12:58
mnaserwait, it's in another hour right?12:58
* lbragstad is pretty sure it is in 2 minutes12:59
lbragstadbah nevermind...12:59
ttxyes one more hour12:59
lbragstadi'm susceptible to off-by-one errors today12:59
asettleDamn I also got a notification it was now13:00
asettleI won't be able to make the meeting in an hour13:00
asettleWe've got the SUSE all hands and I'm in the office for it so gotta look livey13:01
asettlelively*13:01
ricolino/13:03
*** jamesmcarthur has quit IRC13:04
*** mriedem has joined #openstack-tc13:07
mugsiethe invite shows 5 mins ago :/13:08
mugsieI also have a conflict in an hour13:09
ttxInvite says 14utc?13:10
gmannyeah  1400 UTC13:10
mugsieoh. the ical file from eavesdrop is 1300 it seems13:11
ttxhmm13:12
ttxmugsie: blaming code I wrote will lead you nowhere good Graham!13:12
asettleHAHAHAHA13:13
mugsiettx: DTSTART;VALUE=DATE-TIME:20181101T140000Z13:13
mugsieIt seems I have to shout at outlook devs13:14
ttx\o/13:14
ttxI'm starting to analyze/track solutions for the leaderless teams at https://etherpad.openstack.org/p/ussuri-leaderless13:15
ttxfeel free to play along13:15
openstackgerritGhanshyam Mann proposed openstack/governance master: Add Tempest and Plugins req in Train tested Runtime  https://review.opendev.org/68040713:21
dhellmanndid I miss the patch to confirm the new TC roster? or do we not have one, yet?13:41
dhellmannah, I missed it https://review.opendev.org/#/c/680356/13:41
*** Luzi has quit IRC13:46
openstackgerritMohammed Naser proposed openstack/governance master: Add Mohammed Naser nomination as chair  https://review.opendev.org/68041413:47
*** bnemec has quit IRC13:48
*** bnemec has joined #openstack-tc13:48
*** jeremyfreudberg has joined #openstack-tc13:48
dhellmannmnaser : I think we'll want to land https://review.opendev.org/#/c/680356/, then have you update the gerrit group so the new members can vote on ^^13:51
dhellmannIIRC, that's how we've done it in the past13:51
dhellmanntc-members : if you're going to miss the meeting it would be good to get your votes on https://review.opendev.org/#/c/680356/ in now13:52
mnaserdhellmann: my patch sits on top of that, but yes, fair enough13:52
dhellmannmnaser : yeah, that's right, but I'm thinking about who the right set of voters is for each. The outgoing TC confirms the incoming, and the incoming selects their chair.13:53
mnaserfair13:53
mnaserill abandon13:53
mnaserand then restore then13:53
dhellmannmnaser : no, that's not what I'm suggesting13:53
dhellmannjust don't approve it :-)13:53
mnaserright but there mgiht be a bunch of RC+1 for some non-tc members?13:53
dhellmannsorry if I wasn't clear; we just need to pause in between to update the gerrit group with the right voters13:53
mnaseri am not sure what happens with gerrit if yo uremove someone, if their RC gets removed or not13:54
mugsieit doesn't13:54
dhellmannit doesn't, but we can just count by hand13:54
mnaserdoing math.. pfft13:54
dhellmannone benefit of shrinking the tc to 9 members is you could use your fingers ;-)13:54
mnaserill just abandon and restore it later, it's easier for me tbh\13:54
dhellmannok, if that's easier, go for it13:54
mnaserso that way i can just continue to use check-review13:55
mnasertc-members: meeting in 5!13:55
* mnaser goes back to listing all countries ive traveled to since 201413:55
zanebmnaser: remember to write really small13:57
mnaseri'm finally getting nexus/global entry/$whatever_its_called13:57
mnaserthe neat thing is for the visa applications for china, you have a code you can just put in and it puts in your previous application13:57
mnaserso that should be easy for shanghai13:58
evrardjpo/13:58
ttxmnaser: at the end of the meeting it would be good to discuss https://etherpad.openstack.org/p/ussuri-leaderless13:59
ttxand get volunteers for actions in there13:59
mnasersure13:59
mnaser#startmeeting tc14:00
openstackMeeting started Thu Sep  5 14:00:09 2019 UTC and is due to finish in 60 minutes.  The chair is mnaser. Information about MeetBot at http://wiki.debian.org/MeetBot.14:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:00
mnaser#topic roll call14:00
*** openstack changes topic to " (Meeting topic: tc)"14:00
mnaser\o/14:00
openstackThe meeting name has been set to 'tc'14:00
*** openstack changes topic to "roll call (Meeting topic: tc)"14:00
ttxo/14:00
ricolino/14:00
dhellmanno/14:00
njohnstono/14:00
gmanno/14:00
fungithanks ttx for pushing the tc members update. do you know if there's one yet for the ptls?14:00
ttxfungi: no, that one is a bit more... complex to make14:00
lbragstado/14:01
ttx(and arguably slightly less urgent)14:01
zanebo/14:01
fungisorry, will pick back up on discussion of election topics after the meeting14:01
jungleboyjo/14:01
ttxafter teh 13-member TC, today we have... the 17-member TC14:01
dhellmannthe new tc should confirm that one14:01
* jungleboyj is starting early, though double booked. :-)14:01
*** Sundar has quit IRC14:02
mnasera lot of math and counting but i think we have quroum14:02
mugsieo/14:02
evrardjpttx:  :)14:02
mnaserlets get started i guess14:02
dhellmannmnaser : I count 1014:02
mnaser#topic Follow up on past action items14:02
*** openstack changes topic to "Follow up on past action items (Meeting topic: tc)"14:02
mnaser#info mnaser to contact Alan to mention that TC will have some presence at Shanghai leadership meeting14:03
mnaseri have done this and let them know we'll be around, but nothing more yet in terms of planning14:03
mnaserthere is a confirmed time and date, so for those new TC members, please update https://etherpad.openstack.org/p/PVG-TC-PTG14:03
mnaseri'll try to add more context because we have new members :)14:04
gmanndone14:04
mnaserevery time we have a summit, there is usually a 1 day meeting that involves OSF staff+board+TC+UC+(other OSF projects)14:05
mugsiemnaser: and the date / time of the leadership meeting would be helpful14:05
*** lpetrut has quit IRC14:05
mnaser#link https://wiki.openstack.org/wiki/Governance/Foundation#OpenStack_Board_of_Director_Meetings14:05
mnaserso it'll be at 3 november, a day before the summit starts, so just a heads up on that :)14:06
mnaserwe can follow up more on that later, but that action item is done and we can remove it14:06
mnaser#info ricolin update SIG guidelines to simplify the process for new SIGs14:06
ttxit's a good way to catch up with jet lag14:06
mnaserhah14:06
mnaserricolin: wanna update us on this?14:06
jungleboyjSo it conflicts with Upstream Institute again.14:06
ricolinI'm currently working on etherpad for that, and will ask SIG chairs to join edit once I'm done with the draft version. https://etherpad.openstack.org/p/SIGs-guideline14:06
gmannjungleboyj: yeah but depends on place. if it is different then yes14:07
ricolin#link https://etherpad.openstack.org/p/SIGs-guideline14:07
ricolinfeedback welcome:)14:07
ttxfwiw we do not have to all be there14:07
jungleboyjOUI is going to be at the Lenovo Offices.  So, will need to figure out how to work that out.14:07
ttxjust to represent14:07
dhellmannjungleboyj : it always will14:07
ttxthere is no room for everyone in every leadership body anyway14:07
mnaser+2 to what ttx mentioned, it is just an update so there's no decision making or anything, we just need representation :)14:07
jungleboyjttx:  Ok.14:07
ttxwhat's important is that whoever shows up knows what to say14:08
mnaserricolin: thanks.  that looks really good14:08
ttxso preparation is more important than being there really14:08
mnaserso next step is followingh up with SIG chairs to update/edit ?14:08
ricolinmnaser, I assume, need to know how each SIG feel about the current docs before we can simplify it14:09
mnaser++ cool, i assume you'll be continuing to drive this forward yourself?14:09
ricolinyes14:09
mnaserawesome, thanks for driving all this SIG stuff :)14:09
mnaser#action ricolin Follow up with SIG chairs about guidelines https://etherpad.openstack.org/p/SIGs-guideline14:09
ricolinHope that's any helpful for Ansible, container SIG and others14:10
ttx#siglife14:10
ricolinmnaser, evrardjp ^^^14:10
mnaseryes we're a fresh little bunch :-)14:10
mnaser#info ttx contact interested parties in a new 'large scale' SIG (help with mnaser, jroll reaching out to Verizon Media)14:10
ricolin#siglife! :)14:10
evrardjpI will have a look ricolin14:10
ttxI'm a bit behind, as August was not really great for that. Will get it done over the next month14:11
mnaseri didn't help much with this unfortunately, jroll hasn't mentioned anything yet here but i remember him saying that verizon gave a "now now we are dealing with fires but it sounds good"14:11
mnaserok ill readd it as an action item again but dropping the verizon part, we can follow on that later, i dont think its that pressing for time14:11
ttx++14:11
mnaser#action ttx contact interested parties in a new 'large scale' SIG (help with mnaser)14:11
mnaser#topic Active Initiatives14:12
*** openstack changes topic to "Active Initiatives (Meeting topic: tc)"14:12
mnaser#info mugsie to sync with dhellmann or release-team to resolve proposal bot for project-template patches14:12
mnaseri think smcginnis brought this up here a few days ago too14:12
mnaserwe're starting to get train branch requests but i dont know if that code has landed or not14:12
mugsieI hav the code, I am in the process of testing it, should have something early next week14:12
mnaserawesome14:12
mugsiebut, fair warning it will land in about 3 places14:13
mugsieat least 2 anyway14:13
dhellmannmugsie: that's surprising; maybe we can talk about the details after this?14:13
mugsiedhellmann: sure, np14:14
evrardjpmugsie: I wouldn't mind syncing with you, as I started to do a few things about it.14:14
mugsieI am popular today :)14:14
evrardjpagreed with dhellmann , happy to see that :)14:14
mnasercool, this can be an office hour-y thing or discussed later, but sounds good14:14
dhellmannmugsie : you're popular every day, friend14:14
mnasersmcginnis: ^ just fyi if you want to go back and read scrollback :)14:14
mnaser#info Shanghai TC sessions: https://etherpad.openstack.org/p/PVG-TC-brainstorming14:15
mnaserwe need to start adding forum session ideas for the TC14:15
mnaseralso -- did we add our usual few (i see goals there which is good)14:15
mnaser(extended maintenance? bahaha)14:16
evrardjpdhellmann: :)14:16
mugsiebased on the thread built off the election results, do we need a "where is OpenStack leadership going to come from in the long run"?14:16
mnaserany ideas can go in there and then we can trim them down and clear them up :)14:16
dhellmannthe topic is good, but I would change the phrasing of the title :-)14:17
ttx"The future of stewardship in OpenStack"?14:17
jungleboyjttx:  ++14:17
dhellmannyeah, something like that14:17
gmannon goal sessions: we will have single sessions for U (if not finished we have 2 entry for U cycle goal till now ) as well as V cycle goal discussions.14:17
mugsiettx: ++14:17
njohnstonttx: ++14:18
ttxbecause it's not just the TC nominees. It's hard to get volunteers to run elections and other community processes14:18
ttxit's not purely a leadership issue14:18
ricolingmann, +1 on separate those two topics14:18
dhellmanngmann : would it make sense to split those into 2 sessions so you have time to get into details?14:18
jungleboyjYeah ... It's a whole new world.14:18
gmannohk. I am wondering if we select the U cycle goal before that14:18
ttxit's  a lack of time / interest / recognition for doing community janitorial tasks imho14:18
ttxbut then that's already discussing it14:19
fungiright, you could consider the people doing those other tasks leaders of a sort i suppose, even if not elected leaders14:19
mnaser:)14:19
gmannin that case we can utilize it for V goal discussion ?14:19
mnaseri think we should take all those ideas and put them in that etherpad14:19
mnaserwe can save discussion for office hours (or if we're done earlier)14:19
ricolinI think we need some more time to discuss about what we gonna early start(initial) V-cycle goals, I think that will need time14:20
ttxyes, good office hour topic for this week and the next14:20
ttxsince we'll need to submit forum topics soon14:20
mnasercool, yes i think i saw the email that its open now14:20
ttxit is14:20
dhellmanngmann : even if you have the U goals selected, it would be good to have time to discuss implementation. We skipped that for Train, IIRC, and it has caused issues.14:20
*** tiffanie has joined #openstack-tc14:20
mugsieyeah14:20
gmanndhellmann: nice idea. +114:21
mugsieand it allows teams to socialise ideas to do them, or co-ordinate work14:21
mnaseri think we can move onto next item and discuss the rest of this in office hours? :>14:21
dhellmannthere should probably always be 2 goals sessions: "implementing goals for N" and "choosing goals for N+1"14:21
mugsie++14:21
dhellmannk14:21
ricolinI think so14:21
gmanndone14:22
mnaser#info Forum selection commitee: http://lists.openstack.org/pipermail/openstack-discuss/2019-August/008188.html14:22
mnaseri think we already have a few volunteers and we can close this one out right?14:22
mugsieyeah - I thought we had people14:22
ttxyes14:22
ttxthere was a thread14:22
mnaseri just wanted to leave it there to confirm that we're all good14:23
mnaserso we can drop it for the next one14:23
*** jamesmcarthur has joined #openstack-tc14:23
*** tiffanie has left #openstack-tc14:23
*** tiffanie has joined #openstack-tc14:23
mnaser#info Make goal selection a two-step process (needs reviews at https://review.opendev.org/#/c/667932/ )14:23
mugsiesame as ^14:23
mnaserthis merged, thanks for the awesome work ttx14:23
mugsie++14:24
ttxwell now it needs to be applied and see if it flies14:24
gmann++14:24
ttxjust in time :)14:24
mnaserheh14:24
mnaser#topic leaderless projects14:24
*** openstack changes topic to "leaderless projects (Meeting topic: tc)"14:24
mnaser#link https://etherpad.openstack.org/p/ussuri-leaderless14:25
mnaserttx: started to do the work on figuring out "wat do"14:25
ttxyes, gives some situational awareness14:25
ttxcybord sounds like a no-brainer14:26
mnasercyborg is easy, yep14:26
ttxwe just need to propose that change14:26
evrardjpthanks for this ttx. I have the impression some names are reoccuring ?14:26
mnaserdesignate seems like it has potential so i'd trust mugsie to make that call14:26
ttx(don't forget the "appointed" key)14:26
ttxevrardjp: yes14:26
mnaserttx: i think we're still waiting for the ptl change to happen.. or do we do that..14:26
ttxdesignate: mugsie tooke (yet another) action14:26
mugsiemnaser: yeah, I am meeting the suse people after this meeting, and then the other person tomorrow I think14:27
ttxopenstacksdk... I can reach out to mordred. Since he lives on a boat, he tends to miss things14:27
ttxThe others are all more complicated14:27
mnaseri think reaching out to nova ptl (efried) if they're interested in managing placement too?14:27
ttxRe: I18n, I can reach to ianychoi... he did not run because he was an election official14:28
ttxso if that was the ONLY reason for not running, he might save it14:28
fungiyes, he seems willing to cover i18n14:28
*** tiffanie has quit IRC14:28
fungii think he realized that only after volunteering to be an election official14:28
ttxfungi: did you talk to him already?14:28
*** tiffanie has joined #openstack-tc14:28
mnaserok that's pretty good in that case14:28
evrardjpttx: I thought mordred lived in a plane, surprised of this14:28
fungihe mentioned it in #openstack-election14:28
ttxok14:29
*** lpetrut has joined #openstack-tc14:29
mnaserok so that might be relatively easy too14:29
fungievrardjp: well, more that mordred has been on vacation for a few weeks and likely forgot elections were coming up14:29
evrardjpso fir i18n there was a conversation about moving to sig already14:29
mnaseri think for now lets focus our efforts on the tough ones if we have someone who has expressed interest14:29
ttxevrardjp: I've mixed feelings about that. They produce files that are shipped with most deliverables14:30
mnaseri think {powervm,win}stackers would probably have the same outcome.  and figuring out what to do with placementc14:30
ttxso it's hard to object that they are on the projectteam side of the fence14:30
openstackgerritGraham Hayes proposed openstack/governance master: Appoint Sundar Nadathur as Cyborg PTL  https://review.opendev.org/68042614:30
dhellmannttx: is that still true? I thought they were focusing on translating documentation now14:30
evrardjpttx: in any case, i18n can be first covered as a project then changed governance :)14:30
ttxdhellmann: someone changed openstack and did not warn me?14:31
dhellmannit's possible I'm wrong14:31
ttxdhellmann: if that is true... and no more zanata...14:31
ttxthen yes, SIG all the way14:31
ttxor merge with docs14:31
mnaseri think its jsut docs cause we dropped the whole logging translation thing14:31
dhellmannthey did API error messages at one point, too14:32
dhellmannthat's the part I'm no longer sure of14:32
zanebthere are other things in code that get tranlated other than logs14:32
mugsiehorizon?14:32
ttxhmm, ok so needs some checking14:32
dhellmannah, yeah, horizon, too14:32
gmanncontributors guide14:32
mnaserfor now, we have someone who is expressed interest so we can figure out that stuff later14:32
gmannbut those are one time things not so change frequently14:32
evrardjpzaneb: you mean there are still things in code that should be moved away ? ;)14:32
mugsiei got a zanata commit 7 weeks ago anyway for designate-dash14:32
mnaserplacement and *stackers are the issue we should focus our time on14:33
dhellmanneven if they're doing some code work, it could be a SIG because those are meant to be cross-project14:33
ttxyes14:33
evrardjpyeah we still have babel in most of the projects so I suppose there is a reason for this14:33
dhellmannmnaser : yeah14:33
ttxSo.. *stackers first14:33
ttxMy position is that they should be moved to SIGs14:33
mugsiettx: ++14:33
dhellmannif they aren't active enough to have a PTL, are they going to produce a SIG lead?14:33
ttxThey are special interests, and currently outside of the scope of the projects they produce extras for14:33
*** tiffanie has quit IRC14:34
mnaserlooks like the last change to nova-powervm is july 2214:34
ttxdhellmann: maybe not, but I just want that variance out of the projectteam list14:34
evrardjpcould we discuss about history of those in terms of missing deadlines?14:34
*** tiffanie has joined #openstack-tc14:34
dhellmannttx : sure. What about removing them from the project team list and suggesting they apply to be a SIG if they want to.14:34
dhellmannrather than converting them automatically14:34
evrardjpdhellmann: I like this.14:34
ttxIt's not a part of openstack, as long as their products are not adopted by the other project teams14:34
mnaseri agree with dhellmann on that.  esp seeing the code activity..14:34
mnaserhttps://review.opendev.org/#/q/project:openstack/nova-powervm14:35
mnaserreview activity is dead too14:35
ttxand I'd argue that at this point it's very unlikely that they will ever be merged mainline14:35
evrardjpI would prefer ML call first, because it's quite a process to say we close something14:35
mnasertbh, i'm inclined to take more of a strict action here14:35
mnaserwe've been appointing it for a while14:35
ricolinevrardjp, +1 for ML14:35
ttxso I'd jump on the occasion that they missed elections twice in a row and remove them, If they want to continue as an official part of openstack they can, as a SIG14:35
mnaserand there's no activity and almost no review activity14:35
gmann+114:36
dhellmannttx: +114:36
mnaserthe last merged change was from someone who doesnt even work on the project anymore, 5 weeks ago14:36
evrardjpttx: I would say yes: ML notification -> removal of offical14:36
mnaserhttps://review.opendev.org/#/q/project:openstack/nova-powervm+is:merged14:36
ttxAnyone volunteering to take one bullit for the team and proposing that?14:36
mnaserthe project is quite obviously dead14:36
jungleboyjttx: ++14:36
dhellmannttx: I'll do it, I'm a lame duck ;-)14:36
ttxRico and I took the bullet of raising that thread 6 months ago :)14:37
ttxdhellmann: thx !14:37
zanebgate is broken as well by the looks of it14:37
evrardjpdhellmann: thanks :)14:37
ricolindhellmann, cool!14:37
mnaserhttps://review.opendev.org/#/q/project:openstack/compute-hyperv+is:merged14:37
ttxThat leaves placement14:37
mnaserthe winstackers does seem to be active though14:37
mnaserso i dont think powervm and winstackers is in the same spot14:37
evrardjpdhellmann: can we assign you all the hard tasks? I might have a queue.14:37
ttxmnaser: sure, but they also did not oppose to transition to SIG14:37
mnaserfair enough, ok, so that will fit their interest14:38
mnasersounds good to me14:38
mnaserok, placement.14:38
mugsiewinstackers is very active - but I am going to step back on anything to do with them14:38
mnasercdent is unable to run bc employer, edleafe is not around, and cdent couldnt find anyone14:38
dhellmannevrardjp : no, only the "easy but unpleasant" tasks14:38
ttxTo me it's a clear special interest - making sure openstack runs well on windows14:38
jungleboyj++14:38
ttxwhich is NOT something openstack teams otherwise guarantee14:39
dhellmannwait, I thought we were talking about winstackers before? which team did I just agree to deprecate?14:39
mugsiepowerstacker14:39
ttxPowerVMstackers AND winstackers14:39
evrardjppowerstackers14:39
dhellmannok, let's finish the conversation, and I'll make 2 patches if we're doing both14:39
ttxEverything I said applied to both14:39
evrardjpso they also missed the deadlines twice?14:39
ttxyes14:39
ttxboth14:39
evrardjpthat's fine for me then.14:40
mnaserso: placement14:40
dhellmannok, 2 patches and 1 email thread coming up14:40
mnaserlooks like nova meeting is happening right now14:41
gmannyeah14:41
mugsiemnaser: please lets not suggest merging before we ask people ar ethey interested14:41
mnasermaybe someone can bring it up in the open discussion part if someone from the nova team is interested in helping14:41
gmannon the perfect time of placement topic :)14:41
mnasermugsie: i am not suggesting merging14:41
mnaseri am suggesting that the ptl for nova or someoen from the nova team ptls it14:41
ttxI'm willing to give them an opportunity to find someone and step up, as I think it's better as a standalone team (to get adoption from other services)14:41
gmanni can bring there14:41
ttxBut if they don't then yes, I'd +1 asking Nova if they would take it14:42
mriedemnova nearly didn't have a ptl nomination for U so asking for double duty is a stretch14:42
evrardjpI agree with the Frenchman again14:42
mugsieI would be very hesitent in agreeing to re-merge14:42
ttxmriedem: yes. Also it's a bit unfair after all the drama to dump it back on the Nova team, imho14:43
ttxshould be the plan B14:43
*** jamesmcarthur has quit IRC14:43
mriedemlet's call it plan F14:43
ttxheh14:43
zanebmriedem++14:43
ttxI wish there was 6 options14:43
mugsieyeah, I see it as asking the neutron team to take octavia if there is no ptl14:43
evrardjpstrong letter choice14:43
jungleboyjevrardjp: ++14:44
njohnstonmugsie: ++14:44
ricolinmugsie, lol14:44
johnsommugsie Hey now, we haven't been without a PTL since the project started.....14:44
ttxso plan A would be to find someone to volunteer. My discussion with gibi actually seeded my idea for multi-headed PTLs14:44
johnsomJust throwing that out there...14:44
johnsomAnd no, we can't take placement on either. grin14:45
ttxsince gibi is still on placement, just not wanting all the dreaded PTL load14:45
evrardjpjohnsom: hahaha14:45
evrardjpttx: maybe that's something we should fix14:45
zanebI think this highlights that we're still failing to explain the PTL role14:45
evrardjpbut that will be a longer convo14:45
mugsieso, action it to reach out to people in both nova and placement to see who is interested, then we can circle back?14:45
ttxjohnsom: mugsie is known for poor examples and misdirected blaming. He accused eavesdrop for being early to the meeting a few hours ago14:45
zanebif a project has nobody working on it, that's one thing14:46
evrardjpmugsie: that sounds logical14:46
mnaseri think this highlgihts why we should kill the ptl role and just replace it by liaisons that dont have to be cycled unless they need to14:46
ttxjohnsom: while everyone knows Outlook is to blame for everything14:46
mnaserbut14:46
mnaserthat's for another dicussion14:46
zanebbut if there are active cores, surely someone can put their name at the top14:46
mnaserall this is nice14:46
mnaserbut it doesn't get us a placement ptl14:46
johnsomttx So true14:46
mugsiemnaser: it gives us a process - lets start on the action I suggested, and go from there14:46
mugsiewe aren't going to fix in the next 70 mins14:47
mnasersorry, i missed that message14:47
*** lpetrut has quit IRC14:47
ttx16:45 <mugsie> so, action it to reach out to people in both nova and placement to see who is interested, then we can circle back?14:47
ttx16:45 <mugsie> so, action it to reach out to people in both nova and placement to see who is interested, then we can circle back?14:47
ttxoops14:47
ttxthat works for me14:47
mugsieI had one item I added to the agenda - can we look at that quickly? I have to go talk to prospective PTLs in 10 mins14:47
mugsie(naming things)14:48
mnaseruh sure i was going over the email one, let me open th ewiki quick14:48
mnaser#topic release naming14:48
*** openstack changes topic to "release naming (Meeting topic: tc)"14:48
ttxwho takes the placement reachout action?14:48
mnasermugsie: all yours14:48
mugsie#link https://civs.cs.cornell.edu/cgi-bin/results.pl?num_winners=1&id=E_844843c6ddc940b714:49
zanebmugsie: I admire your optimism to get that covered in 10 minutes14:49
gmanni have not checked but wondring if Tetsuro is interested for placement14:49
mugsieresults are dependant on what algorithm we choose14:49
mnasergmann / ttx / mugsie: nova and placmeent is largely the same core set so it'll probably be the same group of people answering that question14:49
ttxyes.14:49
ricolinzaneb, now be positive!14:49
dhellmannoh, good, so now we have to vote on how to count votes?14:49
mugsieit is one of : stay the same | Cites | ICAO alpha14:49
mugsiepersia: suggested a run off election with those 314:50
ttx5-414:50
zanebricolin: have you met me?14:50
dhellmannI think we have to say that geographic names are not working and drop that option, since we do not know where the next summits will be.14:50
ttxhow would that change the result?14:50
ttxCondorcet needs no run-offs14:50
ttx(Not that I like this result)14:51
dhellmannright, that's the point of condorcet in the first place14:51
dhellmannthis was "advisory" right? not binding?14:51
mugsiedhellmann: sure?14:51
smcginnisI like ICAO alpha, but that patch suggests changing it now, not when we wrap the alphabet.14:51
mugsieI honestely expected ICAO to win hands down14:51
gmannttx: mnaser mugsie sorry i was typing on nova meeting too for API updates. if no one raised hand to reachout to placemrnt i can do ?14:51
mnasergmann: please! :)14:51
ttxit is pretty tight14:51
dhellmannsmcginnis : we need to change now because we need to decouple selection from the foundation site location process14:52
gmannsure.14:52
ttxWe could do a re-run with our new membership14:52
ricolingmann, sweet!14:52
ttxsince they are the ones to live with it14:52
njohnstonDo we need to have lawyer review of the ICAO names to make sure e.g. OpenStack Victor won't fall afoul?14:52
dhellmannttx: yes, I like that14:52
ttxoh or....14:52
ricolinttx that's true14:52
mnasernjohnston: good call14:52
smcginnisdhellmann: In that case, I would choose cities until we wrap up Z, then ICAO names.14:52
ttxWe propose ICAO, and we vote. If it does not pass... means we really stay14:52
ttxthe same14:53
ricolinnjohnston, I actually think we do14:53
evrardjpIs it brexit? How many times can we vote?14:53
jungleboyjHmmm, I like W for ICAO.  :-)14:53
mnaserttx: we can either do that, or we abandon the ones that weren't popular and leave the voting to happen in Gerrit.14:53
ttxevrardjp: we'll need to vote on whatever change in Gerrit anyway14:53
dhellmannttx: was there something about ICAO being not trademarkable, so we don't have to worry about njohnston's question?14:53
smcginnisTo avoid end user confusion, I strongly recommend the TC votes for a new scheme for the next A-Z.14:53
mugsiesmcginnis: yeah, that was supposed to follow on from this14:54
ttxdhellmann: if it's expressedly tied to teh ICAO, then I'd argue it's not, but I can have a check14:54
jungleboyjsmcginnis:  ++14:54
jungleboyjI think if we stop naming we lose some of our identity.  That is my one bit of input.14:54
mnaseri think that's an obviously losing choice based on the voting14:54
mnaserso maybe we can just abandon the choices that lost14:54
ttxSo... how about... we propose the most popular process change (ICAO) and then if it does not pass, that means we really keep the current process up to Z14:54
mnaserand leave the remaining ones as a vote14:54
mugsiewell, stop naming things basically got 0 votes :)14:55
ttxthen we start the discussion for post-Z era14:55
zanebfor elections we specify the Schulze/Beatpath method14:55
ttxindeed14:55
mugsieoh, then cities won14:55
zanebin which major cities comes out on top14:55
smcginnisShould I propose an updated one that calls out cities until we reach Z, ICAO alpha starting with the next A?14:55
ttxheh we managed to create a cycle. Perfect14:55
jungleboyjttx ++14:55
ttxAnd yes Schulze is a superior method for breaking them14:56
ricolinso one more vote to clear all concerns and live with it till Z?14:56
mugsiesmcginnis: I would have them as separate patches14:56
zanebICAO already lost to no change14:56
mugsieand I am not sure about having openstack alpha / beta :P14:56
mnaseri think we're entering discussion territory rather than action update14:56
jungleboyjmugsie: ++14:56
gmann:)14:56
smcginnismugsie: I'm just concerned that some have indicated the choice would need to be effective immediately.14:56
mnaserso maybe we should close out the meeting and leave this discussion to office hours?14:56
zanebmajor cities beat no change (but lost to ICAO)14:56
dhellmannmnaser : ++14:56
gmannyeah14:57
ricolinmnaser, yep14:57
smcginnisAnd no change would get my vote for now, but not after we reach A.14:57
ttxthat means the top 3 are extremely close14:57
gmannand i sleep during that :)14:57
zaneb(I didn't vote for major cities, FWIW)14:57
mnasercool, well, thanks for attending. :)14:57
mnaser#endmeeting14:57
*** 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:57
openstackMeeting ended Thu Sep  5 14:57:32 2019 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:57
openstackMinutes:        http://eavesdrop.openstack.org/meetings/tc/2019/tc.2019-09-05-14.00.html14:57
lbragstado/14:57
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/tc/2019/tc.2019-09-05-14.00.txt14:57
openstackLog:            http://eavesdrop.openstack.org/meetings/tc/2019/tc.2019-09-05-14.00.log.html14:57
gmannzaneb: :)14:57
jungleboyjThanks!14:57
gmannmnaser: thanks for chair14:57
ricolinmajor cities still leave some potential issues IMO14:57
mnaserand office hours time14:57
smcginnisIn 3 minutes. :)14:58
ttxsmcginnis: we do whatever we want. But I'd argue it should be the just-chosen TC membership's choice14:58
ttxnot the past membership choice14:58
openstackgerritDoug Hellmann proposed openstack/governance master: remove powervmstackers team  https://review.opendev.org/68043814:58
smcginnisttx: I agree. Just giving the new TC my opinion.14:58
ttxso we could in theory do a re-run with the 3 tied top options14:58
*** cmurphy|afk is now known as cmurphy14:58
jungleboyjWe will name them after things I find funny.  ;-)14:58
zanebsmcginnis: right, the poll was explicitly for V-Z14:58
openstackgerritDoug Hellmann proposed openstack/governance master: remove winstackers team  https://review.opendev.org/68043914:58
ttxsince they are so close that they would be affected by the change in TC membership14:58
smcginnisI'd just like it to be clear if folks are voting on V-Z or V-A-Z.14:59
smcginnisI don't think that was clear, and I have a feeling there would be some slightly different results if it was.14:59
zanebsmcginnis: "Rank the options for choosing the name of new OpenStack releases for releases between V and Z."14:59
ttxIt was clearly mentioned it was ONLY FOR V-Z14:59
smcginnisAh, OK.14:59
ttxotherwise I would have voted differently14:59
openstackgerritDoug Hellmann proposed openstack/governance master: remove winstackers team  https://review.opendev.org/68043914:59
ttx(I don;t like ICAO for V-A-Z14:59
openstackgerritDoug Hellmann proposed openstack/governance master: remove powervmstackers team  https://review.opendev.org/68043815:00
jungleboyjsmcginnis:  I think we should leave it as is for V-Z and then come up with a new process for the next A-Z.15:00
smcginnisjungleboyj: ++15:00
dhellmannmnaser : the thread on removing winstackers and powervmstackers is at http://lists.openstack.org/pipermail/openstack-discuss/2019-September/009127.html15:00
jungleboyjI could be convinced to have it be ICAO for V-Z while we figure out something better for the next Alphbetical trip.15:00
smcginnisBut if we can't do by Summit cities due to other changes, TC selecting city names would be a good backup.15:00
ttxjungleboyj: I just want the pain to go away. And as someone who ran that naming in the past, it just burns out people unnecessarily15:00
jungleboyjttx:  Understood.  That is not a pain I have experienced.15:01
ttxso I want a thing for V-Z where we don;t run a subjective process15:01
mugsieICAO then?15:01
ttxmugsie: that is why I voted it #1 in my vote yes15:01
johnsomJust an aside to the earlier conversation about the PTL roll. I created a list of "what I did as PTL" to help others considering or becoming Octavia PTL. It is a non-trivial list of things I did/do while PTL. It's also hard to delegate much of this with small teams.15:01
johnsomhttps://www.irccloud.com/pastebin/HjVOFPGq/15:02
ttxit was arguably the most deterministic option15:02
mriedemjohnsom: nova also has one https://docs.openstack.org/nova/latest/contributor/ptl-guide.html15:02
johnsomYeah, I know some of the projects have something a bit more formal.15:02
*** jamesmcarthur has joined #openstack-tc15:02
dhellmannjohnsom : it would be great to add that to the project's documentation, too15:03
ricolinisn't we added a new PTL guideline now, or that's still under plan?15:03
mriedemthe amount of cat herding in nova shouldn't be the same for placement either15:03
ttxjohnsom: how much of this difficulty to delegate is the assumption that the PTL will do it if nobody else does ?15:03
jungleboyjCinder has been working on putting that together.15:03
jungleboyjSomething like that at least.15:03
johnsomdhellmann Agreed, see list above lol15:03
jungleboyjdhellmann:  ++15:04
johnsomttx Some, some degree it is "administrivia" that is "not in my wheelhouse", some is just that it's a small team doing a lot of work.15:04
*** e0ne has quit IRC15:05
ttxjohnsom: was wondering if my recent "multi-headed PTL" suggestion would help or not15:05
jungleboyjWe have been doing that informally for a while.15:05
johnsomA ray of hope for us is two new folks were interested in contributing to OpenStack for the first time this week. You can bet I jumped on helping them get started....15:05
jungleboyj'The Shadow PTL'15:05
dhellmannjohnsom : if there is too much administrivia, maybe we need to take a look at whether those things are actually useful15:05
ttxjungleboyj: yes there is no barrier to doing that currently, but it's... comfortable for other team members to just let the PTL do it in some cases, which reinforces the fact that it's a lot of work15:06
zanebjohnsom: 3,4,23,30,31,33 look like the PTL's core responsibilities (and even some of those could be delegated). the rest are either everyone's responibility, or someone's responsibility regardless of whether they are PTL, or eminently delegatable15:06
johnsomttx Basically Octavia is doing the multi-headed thing informally. I am still helping with a lot of those roles/tasks.15:06
johnsomdhellmann I agree. For example, I find ask.openstack.org to be frustrating in that it doesn't notify on specific topics, so questions show up there that don't get answered until you go look. It's also very restrictive in how you can reply, etc.  Personally I would like to see that disappear.15:08
smcginnisjohnsom: ++15:08
dhellmannjohnsom : oh, I never paid that any attention when I was oslo PTL. Bring questions to the mailing list.15:08
evrardjpzaneb: I agree on the delegation15:08
dhellmannor let the folks who want to use that site answer15:09
evrardjpjohnsom: thanks for that list15:09
evrardjpI am diff-ing with brain right now15:09
johnsomRight, mailing list or even better IRC channels15:09
njohnstonneutron has been doing the multi-headed PTL thing for a while in johnsom's list - 5, 15/16, 17, 18, 20, and 25 each have specific roles.  I think that works well for a big project.  I wonder if the big ones can help the small ones - instead of octavia etc. needing to have a neutron liaison, have someone from neutron check in to see if help is needed (for example)15:09
zanebthe notifications being broken on ask.openstack is annoying. I have reported it multiple times to no avail15:10
ttxjohnsom: there is a group around cycle management, a group around event/meeting management, and a group around project health management15:10
johnsomFrankly I feel bad for the people posting there as the latency is pretty high15:10
zaneb(I get notifications, but about the wrong stuff. most people just started filtering them to spam)15:10
fungijohnsom: i get ask.o.o notifications on topics i've subscribed to (not that i'm going to defend that service as necessarily being a useful one)15:10
ttxzaneb: I'm trying to get it killed completely15:10
johnsomzaneb Same here15:10
evrardjpttx: that would be nice15:11
ttxIt generates google juice, but I'd argue that it's bad juice misdirecting people15:11
ttxI'd rather redirect people interested in that to answer openstack questions on serverfault15:11
ttxor wherever it is that openstack is covered in the SO universe15:12
* zaneb takes a moment to mourn his ask.openstack karma15:12
smcginnisSomething SO based would be better IMO.15:12
evrardjpzaneb: :)15:12
ttxall the badges!15:12
ttxgamification is so 200815:12
zanebmy goal in life is to overtake jpichon15:13
* ttx checks15:13
evrardjpzaneb: you will be happy to finally win over those 38 downvotes.15:13
fungiyes, the argument in favor of ask.o.o in the past was that we needed a place to corral all the users who are disinclined to use e-mail and desire a web forum for such things15:13
ttxzaneb: wow you are indeed an ask master15:14
fungibut i question whether that's really a cross-section of the internet we need to spend our time coddling15:14
mnaserdid we come to terms on a final decision for the release name?15:14
ttxmnaser: Ussuri?15:14
ttx(exit stage left)15:14
mnasero15:14
mnaserno15:14
mnaseri meant moving forwards.15:14
jungleboyj*sad trombone.wav*15:15
zanebttx: I actually quite like it in principle. I help a lot more people this way than through IRC (no longer have global TZ coverage there) or mailing list (very few people post there)15:15
*** tosky has quit IRC15:15
ttxMy suggestion is to bring up a new vote for the newly-chosen TC members with the 3 tied-to-the-top options15:15
zanebhowever, notifications not working mean that latency and follow-up is poor15:15
mnaserthat seems to be the only one actionable suggested item15:16
ttx(and say in advance which cycle-breaking method will be used to break things if need be :)15:16
mnaseranyone else has any other ideas?15:16
johnsomI will also throw in that storyboard has hurt more than helped.15:16
jungleboyjjohnsom:  ++15:16
zanebttx: +1 for that suggestion. especially about specifying the cycle-breaking thing in advance ;)15:16
zanebyeah, unfortunately I think that's true about storyboard15:17
njohnstonttx: +1 from me as well15:17
evrardjpjohnsom: I would agree with you15:17
ttxbut yeah, those options are so close in the current poll that the lines are sure to move once we introduce a couple of new voters15:17
mnaserok, fair enough15:18
ricolin+1 on have a new poll with new TC voters15:19
ttxAlso make it even clearer that it is V-Z we are talking about15:19
jungleboyjricolin: ttx ++15:20
*** jamesmcarthur has quit IRC15:21
evrardjpjohnsom: if you were to say that, in your list of things to do as PTL, you couldn't delegate an item, what would that one/those ones be? I think 24/25/3015:22
evrardjpand 35.15:22
evrardjp(that would have been my case, not sure about yours)15:22
*** jamesmcarthur has joined #openstack-tc15:22
zaneb3 & 4 can't be delegated15:23
ttxhmm not sure15:23
ttxPTG things for example could be delegated to someone handling all meetings15:23
johnsomYeah 4 really, since those are sent privately. Otherwise, I'm not sure any of it *can't* be delegated....15:23
ttxwe could send them to an "event liaison"15:24
zanebttx: well right now the foundation will send them (often off-list) to the contact point, and that's the PTL. I'm fine if that's the one thing that people are signing up for as PTL15:25
johnsomttx There would be value in formalized mailing lists. We also get left out of a bunch or foundation e-mail. Survey questions for example.15:25
ttxAs long as we have an email, we should be fine15:25
ttxbut yes, by default it would land on PTL15:25
ttxwe had cases in the past where PTL could not be at PTG and delegated all contacts15:26
fungithe main reasons those are sent to the ptls are: 1. many ptls are not so good about paying attention to general announcements on mailing lists, and 2. the risk that more than one person on a large team takes it upon themselves to duplicate that work and submit extra/conflicting information to the event organizers15:26
fungiso long as there's a clear single point of contact *or* some means of coordinating to ensure correct and timely responses, then i'm sure it could be someone other than ptls15:27
*** jamesmcarthur has quit IRC15:27
*** jamesmcarthur has joined #openstack-tc15:31
njohnstonPoint of personal curiosity: do we know if there is a timeline for the announcement for the V summit location?  Will it be in Shanghai?15:32
ttxstill very much in flux. But yes i certainly hope that by Shanghai we can present the event plan for 202015:33
njohnstonttx: Thanks!15:33
ttxthere should be some discussion about that at next week Board meeting fwiw15:34
jungleboyjttx: ++ I know that would be helpful for me and my company to know that plan.15:41
*** jeremyfreudberg has quit IRC15:46
evrardjpjohnsom: very valuable input, because you are basically crystallizing what I have been thinking and living for a while.15:50
johnsomevrardjp Cool. Happy to throw my $0.02 in15:51
evrardjpit's worth more than that15:55
evrardjpmugsie: so for the sync15:59
evrardjpwe have one minute remaining15:59
evrardjphttps://review.opendev.org/#/c/673019/315:59
mugsieah - that looks good16:00
evrardjpWe are missing all the things to arrive to that patch, not sure what you are addressing, I assume 516:00
evrardjp(on the commend from smcginnis)16:00
evrardjpcomment*16:00
*** altlogbot_1 has quit IRC16:01
mugsieI was doing a lot of ^ in the releases repo, so it had the releases.yaml file to get the name from16:01
mugsiebut - I think we can work somethign into ^ (maybe adding the releases repo as a job requirement, so it is cloned by zuul16:02
*** irclogbot_2 has quit IRC16:02
*** altlogbot_1 has joined #openstack-tc16:03
*** irclogbot_2 has joined #openstack-tc16:05
evrardjpmugsie: I can't fully remember, but I think this was runned on the releases repo, so you had immediately the things16:06
*** irclogbot_2 has quit IRC16:07
*** irclogbot_3 has joined #openstack-tc16:08
dhellmannthe release tools need to stay in project-config because they run with special privileges, but that job can clone the releases repo to get data16:08
mugsieyeah, so the job that runs the "make_branch" job, would need to have requried-projects: openstack/releases to get the series_status.yaml file16:14
dhellmannit may already clone that repo; I don't remember16:17
mugsieyeah, I am having trouble tracking down the job ... I had it book marked, but I can;t find it now16:17
dhellmannmugsie : we're currently discussing evrardjp's patch in #openstack-release16:18
evrardjpI think the job is running on releases anyway, so files are available .. but yeah, to another channel!16:19
evrardjpthanks dhellmann for the reminder of the channel switch :)16:20
*** cdent has joined #openstack-tc16:21
cdentgmann: I feel like you jumped a gun the bit on the placement ptl message, so I've responded on the list16:21
*** e0ne has joined #openstack-tc16:23
*** e0ne has quit IRC16:31
mriedemfyi on the whole closing osc gaps thing,16:43
mriedemthe mass open cloud NU/BU mentor project thing i submitted has a draft available https://docs.google.com/document/d/1Punt4597VtAndhkwDbG-XrfBQUcXJE-Jmzg2vMIW8Ws/edit16:43
mriedemplease don't edit, should be read-only and formal by tomorrow,16:43
mriedembut point for the tc is (1) they want to support up to 5 mentees, which would effectively make this a pop-up team,16:44
mriedemand (2) it's focused on just the identified compute api gaps in osc but with 5 people contributing thats probably more than what those compute api gaps give them to work on, so might need help from other teams, like cinder16:44
mriedemiow, i'm hedging my bets on this16:44
mriedemthe real struggle is going to be an influx of patches with like me and dtroyer only doing reviews and these students sitting twiiddling their thumbs waiting for reviews16:45
cdentthe struggle is real16:46
mriedemthe threat is real https://en.wikipedia.org/wiki/Volume_8:_The_Threat_Is_Real16:46
*** spsurya has quit IRC16:48
*** jaosorior has quit IRC16:51
dtroyermriedem: careful or you'll be on another core team… :)16:55
mriedemthat just means ignoring reviews as a core rather than not a core :)16:56
*** markvoelker has quit IRC17:04
*** markvoelker has joined #openstack-tc17:13
*** jaosorior has joined #openstack-tc17:21
*** ricolin has quit IRC17:35
*** cdent has quit IRC17:50
*** jamesmcarthur has quit IRC17:51
*** jamesmcarthur has joined #openstack-tc18:04
*** jamesmcarthur has quit IRC18:07
*** zaneb has quit IRC18:15
*** zaneb has joined #openstack-tc18:16
*** jamesmcarthur has joined #openstack-tc18:23
*** mriedem has quit IRC18:31
*** mriedem has joined #openstack-tc18:33
*** e0ne has joined #openstack-tc18:54
*** e0ne has quit IRC19:07
*** e0ne has joined #openstack-tc19:12
*** e0ne has quit IRC19:14
*** e0ne has joined #openstack-tc19:16
*** e0ne_ has joined #openstack-tc19:18
*** e0ne has quit IRC19:21
*** jamesmcarthur has quit IRC19:37
*** jamesmcarthur has joined #openstack-tc19:38
*** jamesmcarthur has quit IRC19:42
*** e0ne_ has quit IRC19:49
*** e0ne has joined #openstack-tc19:54
*** e0ne_ has joined #openstack-tc19:59
*** e0ne has quit IRC20:00
*** ijolliffe has quit IRC20:02
*** ijolliffe has joined #openstack-tc20:04
*** jamesmcarthur has joined #openstack-tc20:09
*** e0ne_ has quit IRC20:19
*** ijolliffe has quit IRC20:29
*** ijolliffe has joined #openstack-tc20:31
*** lpetrut has joined #openstack-tc20:34
openstackgerritJeremy Stanley proposed openstack/governance master: Update projects.yaml for Ussuri PTLs  https://review.opendev.org/68050720:34
fungimugsie: ^20:34
*** ijolliffe has quit IRC20:36
*** lpetrut has quit IRC20:38
*** jamesmcarthur has quit IRC20:48
*** zaneb has quit IRC20:48
*** zbitter has joined #openstack-tc20:48
*** zbitter is now known as zaneb20:49
*** jamesmcarthur has joined #openstack-tc20:50
*** markvoelker has quit IRC21:05
*** diablo_rojo has quit IRC21:06
*** diablo_rojo has joined #openstack-tc21:07
*** markvoelker has joined #openstack-tc21:11
*** markvoelker has quit IRC21:15
-openstackstatus- NOTICE: Gerrit is being restarted to pick up configuration changes. Should be quick. Sorry for the interruption.21:15
*** jamesmcarthur has quit IRC21:29
*** jamesmcarthur has joined #openstack-tc21:50
*** jamesmcarthur has quit IRC21:55
*** claudiub has joined #openstack-tc22:07
claudiubHello. Regarding the winstackers team removal. Sorry for missing the PTL nomination, I was under the impression that the deadline was this week. :( To be fair, my focus has shifted more towards Kubernetes at the moment, which would explain my lack of activity and being out of sync with the release schedule. If it is possible, Lucian Petrut could possibly take over in my stead.22:16
*** jamesmcarthur has joined #openstack-tc22:16
claudiubHe's been a core in most Windows / Hyper-V related things alongside me, and he's at least as knowledgeable as me, and best of all, he's still active.22:16
fungiclaudiub: do you think winstackers would be more appropriate as a sig producing openstack-related support software for using openstack on/with windows, rather than as a team producing deliverable components of openstack?22:18
*** jamesmcarthur has quit IRC22:21
claudiubhm, we do indeed deliver OpenStack support on Windows, but we also deliver os-win, which is a library which is currently being consumed by quite a few projects, including nova, os-brick, cinder, glance, ceilometer, designate, and networking_hyperv (which is in the Winstackers governance), so technically, it is a deliverable component, IMO, which requires maintenance, updates, bugfixes, etc.22:25
*** jamesmcarthur has joined #openstack-tc22:25
fungii agree, that does make the sig proposition tricky22:26
claudiubonce again, I apologise for my negligence. :)22:28
*** jamesmcarthur has quit IRC22:30
*** mriedem has quit IRC22:50
*** jamesmcarthur has joined #openstack-tc23:58

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