Thursday, 2019-12-05

*** jamesmcarthur has joined #openstack-tc00:04
*** diablo_rojo has quit IRC00:06
*** jamesmcarthur has quit IRC00:08
*** tosky has quit IRC00:10
*** njohnston has quit IRC02:06
*** njohnston_ has joined #openstack-tc02:06
*** ricolin has joined #openstack-tc02:11
*** slaweq has joined #openstack-tc02:29
*** slaweq has quit IRC02:35
*** jamesmcarthur has joined #openstack-tc02:45
*** slaweq has joined #openstack-tc02:51
*** slaweq has quit IRC02:56
*** jamesmcarthur has quit IRC03:04
*** diablo_rojo has joined #openstack-tc03:06
*** jamesmcarthur has joined #openstack-tc03:19
*** slaweq has joined #openstack-tc03:21
*** slaweq has quit IRC03:26
*** slaweq has joined #openstack-tc03:34
*** jamesmcarthur has quit IRC03:35
*** slaweq has quit IRC03:39
*** diablo_rojo has quit IRC03:46
*** jamesmcarthur has joined #openstack-tc03:51
*** jamesmcarthur has quit IRC03:54
*** jamesmcarthur has joined #openstack-tc03:55
*** slaweq has joined #openstack-tc03:58
*** jamesmcarthur has quit IRC04:00
*** slaweq has quit IRC04:03
*** tetsuro_ has quit IRC04:06
*** tetsuro has joined #openstack-tc04:06
*** slaweq has joined #openstack-tc04:22
*** jamesmcarthur has joined #openstack-tc04:25
*** slaweq has quit IRC04:27
openstackgerritColleen Murphy proposed openstack/governance master: Add RBAC investment opportunity for 2019  https://review.opendev.org/68238004:32
*** jamesmcarthur has quit IRC04:32
*** slaweq has joined #openstack-tc04:33
*** slaweq has quit IRC04:38
*** slaweq has joined #openstack-tc05:02
*** slaweq has quit IRC05:07
*** slaweq has joined #openstack-tc05:17
*** slaweq has quit IRC05:22
*** slaweq has joined #openstack-tc05:25
*** slaweq has quit IRC05:30
*** slaweq has joined #openstack-tc05:45
*** slaweq has quit IRC05:54
*** slaweq has joined #openstack-tc05:58
*** slaweq has quit IRC06:03
*** Luzi has joined #openstack-tc06:03
*** slaweq has joined #openstack-tc06:11
*** slaweq has quit IRC06:18
*** njohnston_ has quit IRC07:01
*** njohnston has joined #openstack-tc07:04
*** jamesmcarthur has joined #openstack-tc07:34
*** jamesmcarthur has quit IRC07:38
*** jcapitao has joined #openstack-tc07:42
*** iurygregory has joined #openstack-tc08:01
*** rpittau|afk is now known as rpittau08:32
*** bodgix has quit IRC08:34
*** tosky has joined #openstack-tc08:36
*** bodgix has joined #openstack-tc08:38
*** iurygregory has quit IRC08:45
*** iurygregory has joined #openstack-tc08:47
*** slaweq has joined #openstack-tc08:47
*** slaweq_ has joined #openstack-tc08:50
*** slaweq has quit IRC08:52
*** slaweq_ has quit IRC08:59
*** lpetrut has joined #openstack-tc09:04
*** iurygregory is now known as iurygregory_cour09:20
*** iurygregory_cour is now known as iury_course09:20
*** bodgix has quit IRC09:54
*** lpetrut has quit IRC09:54
*** njohnston has quit IRC09:54
*** ricolin has quit IRC09:54
*** dmellado has quit IRC09:54
*** mugsie has quit IRC09:54
*** ccamel has quit IRC09:54
*** cloudnull has quit IRC09:54
*** TheJulia has quit IRC09:54
*** mnasiadka has quit IRC09:54
*** rpittau has quit IRC09:54
*** EmilienM has quit IRC09:54
*** flwang has quit IRC09:54
*** frickler has quit IRC09:54
*** masayukig has quit IRC09:54
*** jbryce has quit IRC09:54
*** aprice has quit IRC09:54
*** iury_course has quit IRC09:54
*** openstackgerrit has quit IRC09:54
*** mtreinish has quit IRC09:54
*** evrardjp has quit IRC09:54
*** cmurphy has quit IRC09:54
*** logan- has quit IRC09:54
*** smcginnis has quit IRC09:54
*** asettle has quit IRC09:54
*** amotoki has quit IRC09:54
*** coreycb has quit IRC09:54
*** knikolla has quit IRC09:54
*** ildikov has quit IRC09:54
*** ttx has quit IRC09:54
*** spotz has quit IRC09:54
*** tosky has quit IRC09:54
*** Luzi has quit IRC09:54
*** tetsuro has quit IRC09:54
*** Jeffrey4l has quit IRC09:54
*** tbarron has quit IRC09:54
*** irclogbot_2 has quit IRC09:55
*** bnemec has quit IRC09:55
*** corvus has quit IRC09:55
*** ianw has quit IRC09:55
*** sapd1_ has quit IRC09:55
*** stephenfin has quit IRC09:55
*** aspiers has quit IRC09:55
*** gagehugo has quit IRC09:55
*** dhellmann has quit IRC09:55
*** dirk has quit IRC09:55
*** persia has quit IRC09:55
*** zaneb has quit IRC09:55
*** jroll has quit IRC09:55
*** gouthamr has quit IRC09:55
*** bauzas has quit IRC09:55
*** lxkong has quit IRC09:55
*** fungi has quit IRC09:55
*** gmann has quit IRC09:55
*** diablo_rojo_phon has quit IRC09:55
*** jeremy__bouncer has quit IRC09:55
*** adriant has quit IRC09:55
*** tonyb has quit IRC09:55
*** purplerbot has quit IRC09:55
*** dansmith has quit IRC09:55
*** tobberydberg has quit IRC09:55
*** timburke has quit IRC09:55
*** tristanC has quit IRC09:55
*** dtruong has quit IRC09:55
*** andreaf has quit IRC09:55
*** csatari has quit IRC09:55
*** johnsom has quit IRC09:55
*** jungleboyj has quit IRC09:55
*** jcapitao has quit IRC09:55
*** dklyle has quit IRC09:55
*** clarkb has quit IRC09:55
*** jrosser has quit IRC09:55
*** tdasilva has quit IRC09:55
*** mgagne has quit IRC09:55
*** dtroyer has quit IRC09:55
*** mwhahaha has quit IRC09:55
*** tonyb[m] has quit IRC09:55
*** mnaser has quit IRC09:55
*** melwitt has quit IRC09:55
*** ChanServ has quit IRC09:55
*** bodgix has joined #openstack-tc10:04
*** dmellado has joined #openstack-tc10:04
*** ricolin has joined #openstack-tc10:04
*** njohnston has joined #openstack-tc10:04
*** lpetrut has joined #openstack-tc10:04
*** masayukig has joined #openstack-tc10:04
*** aprice has joined #openstack-tc10:04
*** jbryce has joined #openstack-tc10:04
*** frickler has joined #openstack-tc10:04
*** flwang has joined #openstack-tc10:04
*** EmilienM has joined #openstack-tc10:04
*** mnasiadka has joined #openstack-tc10:04
*** TheJulia has joined #openstack-tc10:04
*** rpittau has joined #openstack-tc10:04
*** cloudnull has joined #openstack-tc10:04
*** ccamel has joined #openstack-tc10:04
*** mugsie has joined #openstack-tc10:04
*** evrardjp has joined #openstack-tc10:04
*** mtreinish has joined #openstack-tc10:04
*** openstackgerrit has joined #openstack-tc10:04
*** iury_course has joined #openstack-tc10:04
*** tosky has joined #openstack-tc10:04
*** jcapitao has joined #openstack-tc10:04
*** Luzi has joined #openstack-tc10:04
*** tetsuro has joined #openstack-tc10:04
*** dhellmann has joined #openstack-tc10:04
*** spotz has joined #openstack-tc10:04
*** dklyle has joined #openstack-tc10:04
*** dirk has joined #openstack-tc10:04
*** clarkb has joined #openstack-tc10:04
*** Jeffrey4l has joined #openstack-tc10:04
*** persia has joined #openstack-tc10:04
*** jrosser has joined #openstack-tc10:04
*** zaneb has joined #openstack-tc10:04
*** jeremy__bouncer has joined #openstack-tc10:04
*** jroll has joined #openstack-tc10:04
*** tbarron has joined #openstack-tc10:04
*** gouthamr has joined #openstack-tc10:04
*** bauzas has joined #openstack-tc10:04
*** adriant has joined #openstack-tc10:04
*** tonyb has joined #openstack-tc10:04
*** irclogbot_2 has joined #openstack-tc10:04
*** bnemec has joined #openstack-tc10:04
*** corvus has joined #openstack-tc10:04
*** tdasilva has joined #openstack-tc10:04
*** mgagne has joined #openstack-tc10:04
*** dtroyer has joined #openstack-tc10:04
*** ianw has joined #openstack-tc10:04
*** tonyb[m] has joined #openstack-tc10:04
*** sapd1_ has joined #openstack-tc10:04
*** lxkong has joined #openstack-tc10:04
*** mwhahaha has joined #openstack-tc10:04
*** purplerbot has joined #openstack-tc10:04
*** fungi has joined #openstack-tc10:04
*** stephenfin has joined #openstack-tc10:04
*** aspiers has joined #openstack-tc10:04
*** gagehugo has joined #openstack-tc10:04
*** dtruong has joined #openstack-tc10:04
*** andreaf has joined #openstack-tc10:04
*** dansmith has joined #openstack-tc10:04
*** tobberydberg has joined #openstack-tc10:04
*** diablo_rojo_phon has joined #openstack-tc10:04
*** timburke has joined #openstack-tc10:04
*** tristanC has joined #openstack-tc10:04
*** gmann has joined #openstack-tc10:04
*** csatari has joined #openstack-tc10:04
*** johnsom has joined #openstack-tc10:04
*** jungleboyj has joined #openstack-tc10:04
*** melwitt has joined #openstack-tc10:04
*** mnaser has joined #openstack-tc10:04
*** ChanServ has joined #openstack-tc10:04
*** orwell.freenode.net sets mode: +o ChanServ10:04
*** ttx has joined #openstack-tc10:04
*** cmurphy has joined #openstack-tc10:04
*** logan- has joined #openstack-tc10:04
*** smcginnis has joined #openstack-tc10:04
*** asettle has joined #openstack-tc10:04
*** amotoki has joined #openstack-tc10:04
*** coreycb has joined #openstack-tc10:04
*** knikolla has joined #openstack-tc10:04
*** ildikov has joined #openstack-tc10:04
*** logan- has quit IRC10:05
*** logan- has joined #openstack-tc10:06
*** e0ne has joined #openstack-tc10:23
*** jcapitao is now known as jcapitao|afk10:46
*** e0ne_ has joined #openstack-tc10:53
*** e0ne has quit IRC10:56
*** jcapitao|afk is now known as jcapitao10:57
*** iury_course has quit IRC11:55
*** iurygregory has joined #openstack-tc11:56
*** iurygregory is now known as iury_course11:56
*** jcapitao is now known as jcapitao|lunch12:07
njohnstono/12:35
evrardjphello njohnston!12:36
njohnstonhello evrardjp!12:36
evrardjphow are things?12:36
njohnstonThings are wonderful!  And for you?12:37
asettleo/12:39
evrardjpclose to holidays :)12:39
evrardjphey asettle!12:39
njohnstonDo you have any special plans for the holidays evrardjp?12:40
njohnstonHello asettle!12:40
evrardjpnjohnston: a little bit of tc stuff, a little bit of learning, a whole lot of chil out.12:41
evrardjpif that's the proper term12:41
njohnstonevrardjp: Spot on12:42
asettleHI ALL :D12:44
evrardjpwhat's up asettle?12:44
asettleNot a huge amount. It's cold.12:46
*** jamesmcarthur has joined #openstack-tc12:53
*** slaweq_ has joined #openstack-tc13:01
*** slaweq_ has quit IRC13:04
jungleboyjevrardjp: are we having a meeting today?13:07
jrollyes13:07
jrollin... 52 minutes13:07
*** jamesmcarthur has quit IRC13:07
jungleboyjOk. May be a little late. Getting kids to school.13:09
evrardjpok13:09
*** jamesmcarthur has joined #openstack-tc13:12
*** jcapitao|lunch is now known as jcapitao13:22
*** jamesmcarthur has quit IRC13:25
*** jamesmcarthur has joined #openstack-tc13:26
*** jamesmcarthur has quit IRC13:31
ricolino/13:42
*** mriedem has joined #openstack-tc13:54
evrardjpwe have quite a large series of topics13:57
*** jamesmcarthur has joined #openstack-tc13:57
evrardjp#startmeeting tc14:00
openstackMeeting started Thu Dec  5 14:00:07 2019 UTC and is due to finish in 60 minutes.  The chair is evrardjp. Information about MeetBot at http://wiki.debian.org/MeetBot.14:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:00
*** openstack changes topic to " (Meeting topic: tc)"14:00
openstackThe meeting name has been set to 'tc'14:00
evrardjp#topic roll call14:00
*** openstack changes topic to "roll call (Meeting topic: tc)"14:00
ricolino/14:00
njohnstono/14:00
evrardjp#link https://media.giphy.com/media/2YtTdoSEl4m4/giphy.gif14:00
*** diablo_rojo has joined #openstack-tc14:00
ttxo/14:01
diablo_rojoo/14:01
zaneboh hey, this is happening :)14:01
ttxexciting14:01
evrardjpyes indeed14:01
jungleboyjO/14:01
evrardjpone missing for quorum14:01
evrardjpwoot14:01
evrardjpwe have quorum!14:02
evrardjpjust in case: tc-members the meeting has started!14:02
evrardjplet's first start with the follow up action items from previous meeting14:02
evrardjp#link https://media.giphy.com/media/xUA7b2z8NcgvyIthGU/giphy.gif14:02
evrardjp:)14:02
evrardjp#topic follow up previous action item (ricolin): SIG guideliness14:03
jroll\o14:03
*** openstack changes topic to "follow up previous action item (ricolin): SIG guideliness (Meeting topic: tc)"14:03
evrardjpI meant guidelines ofc14:03
ricolinevrardjp, we already got a patch up for that and looks might get landed anytime soon14:03
ricolinhttps://review.opendev.org/#/c/69536614:03
evrardjpnothing else to do than reviewing?14:03
ricolinI assume only needs final approve. And will try to provide it to new SIG and see if that guideline helps14:04
ricolinthat all14:04
*** jamesmcarthur has quit IRC14:04
evrardjpok. Do you want to report here if that helped, at the next meeting?14:04
evrardjpor do you want to give a little more time?14:05
ricolinreport what?14:05
evrardjpIn the latter, I will scratch that action item, and I will have that as a "longer term" action item14:05
evrardjpreport on whether it helps or not :)14:05
ricolinevrardjp, yes14:05
ricolinsure14:05
evrardjpok14:05
evrardjplet's move on then14:06
evrardjp#topic follow up previous action item (ttx): large scale sig14:06
*** openstack changes topic to "follow up previous action item (ttx): large scale sig (Meeting topic: tc)"14:06
ttxThe group was created and had its first meeting14:06
evrardjpthat's good news!14:06
ttx#link https://wiki.openstack.org/wiki/Large_Scale_SIG14:06
evrardjpis the initial attendance as expected?14:07
ttxTwo short-term objectives have been defined14:07
ttx- Scaling within one cluster, and instrumentation of the bottlenecks there14:07
ttx- Document large scale configuration and tips &tricks14:07
ttxyes, pretty good turnout, essentially APAC and Europe for now14:07
ttxNow we'll see if the excitement holds14:08
evrardjpsounds good14:08
ttxI'll help drive it until it can fly by itself14:08
ttxNext meeting in two weeks14:08
evrardjpmaybe jroll could help on the America's side?14:08
evrardjpok14:08
evrardjpdo you want to do a status report in a few months?14:08
cloudnullo/14:08
* ricolin expect Line team will shows up in Large scale SIG:)14:09
ttxWell for now it is a bit convenient not to have anyone from teh US from a meeting org perspective, so I'm not exactly chasing more down14:09
evrardjpI see14:09
ttxLINE, YAhoo!Japan, CERN, China Mobile...14:09
evrardjp:)14:09
ttxStackHPC14:09
ttxOVH14:09
evrardjpyeah definitely europe/apac14:09
evrardjpreport next month to see how this flies?14:10
ttxI like that those were not necessarily very invested upstream before14:10
ttxSo we'll see14:10
ttxsure14:10
evrardjpthat's good news indeed :)14:10
evrardjpI will keep the topic for next month if you don't mind14:10
ttxwfm14:11
evrardjpthat looks important to keep an heartbeat on14:11
evrardjpok next14:11
evrardjpis gmann there?14:11
evrardjpor mnaser?14:11
evrardjpI will skip the two topics of them for now, moving to ricolin again then :)14:12
evrardjp#topic ricolin report on multi-arch sig and other sigs14:12
*** openstack changes topic to "ricolin report on multi-arch sig and other sigs (Meeting topic: tc)"14:12
ricolinFor multi-arch we got a great number of people shows their interest on, which means there's definitely value to form it asap14:13
evrardjpnice to hear14:13
evrardjpwould that be joined by the power folks, combined by the people you know focusing on ARM?14:13
ricolinrigth now we have Linaro to provide around 10 server, which might get online early next year14:14
jungleboyjNice.14:14
evrardjpnice indeed14:14
ricolinstill looking for more:)14:14
ricolinevrardjp, that's good idea, I should ask them14:14
evrardjpdid you ping tonyb for his opinion on this? He might be able to provide you contacts14:14
ricolinevrardjp, yes, he also replied the ML too14:15
ricolin#link http://lists.openstack.org/pipermail/openstack-discuss/2019-November/010970.html14:15
evrardjpawesome!14:15
ricolinhe's onboard!14:15
evrardjpI missed this, sorry14:15
evrardjpamazing14:15
ricolinNP14:15
evrardjpoh yeah I remember now14:15
evrardjpok cool14:15
evrardjpis there anything else that we should be aware or that we can help, regarding SIGs?14:16
evrardjp(not necesarily the multi-arch one)14:16
ricolinI will take action to contact to Infra team to see if we got more ARM server in our Nodepool14:16
ricolinWe got two thing going on in SIGs14:16
evrardjpthat might be good to discuss with mnaser about that too, as he is already very involved in infra14:16
mnasereh, timezones are confusing.  hi, i'm here.14:17
evrardjp(he is kinda our liaison to deal with the static hosting story that I wanted to chat here)14:17
ricolinOne is we're tagging SIGs to match their current state https://review.opendev.org/#/c/695625/14:17
ricolin#link https://review.opendev.org/#/c/695625/14:17
ricolinanother is the combine of self-healing SIG and auto-scaling SIG discussion14:17
ricolin#link http://lists.openstack.org/pipermail/openstack-discuss/2019-November/010989.html14:17
mnaserturns out most of static hosting was actually done by andreas, i'm working on figuring out the next steps.14:17
evrardjpmnaser: yeah we'll come to that soon, we're finishing the report on what's going on in sigs14:18
evrardjp(if there is more to say)14:18
ricolinnope14:18
ricolinthat's all14:19
evrardjphaha ok14:19
evrardjpthanks for the work there ricolin14:19
ricolinalso ttx been promote to meta-sig core14:19
evrardjpoh great!14:19
evrardjpdo we need to track the merger of those sigs (self healing and auto scaling) ?14:20
evrardjpI suppose you could do a little summary at next meeting?14:20
evrardjp(you = ricolin or ttx)14:20
ricolinI will do it since I'm driving that atcion too14:20
evrardjpok perfect14:20
evrardjpnice to see progress there!14:21
evrardjpok let's go to one of the many topics for mnaser then14:21
evrardjp#topic mnaser report on the infra liaison14:21
*** openstack changes topic to "mnaser report on the infra liaison (Meeting topic: tc)"14:21
evrardjpwhat's happening with the static hosting?14:21
evrardjpis there more to say than what you said above?14:22
mnaserthere's not much to report, turns out andreas has done a lot of the work and we were blocked for a while with the afs volume being pending creation and some infra patches pending to merge14:22
mnaserso there's not much progress but we've also been blocked for waiting for a bit too14:22
evrardjpcan anyone around here help on that, or is there tribal knowledge that will be prevent people from this team to step up?14:23
evrardjpor any other blocker14:23
evrardjpI am just curious on how to help this forward14:23
mnaserit was blocked on the infra team because of afs things and job creation (i.e. openstack/project-config patches)14:23
mnaserthey didn't have the infrastructure ready for us (yet)14:23
evrardjpoh I see14:24
evrardjpI will keep this in the topics for next meeting, so we track if it's still blocked on infra side, ok for you?14:24
mnasersure14:24
evrardjpin the meantime, I suppose you're pinging on this to track the status update?14:25
mnaseri'm sorry, i don't follow14:25
evrardjp(just to know that both teams aren't waiting for each other at some point)14:25
mnaserno, i'm not pinging the infra team, afaik they just finished their work a day or two ago14:25
evrardjp"oh but we did that, you can go ahead now"14:25
evrardjpI see14:26
evrardjpso this work can be unblocked soon then?14:26
mnaserhopefully14:26
evrardjp(sorry if I ask stupid questions, it's because I am not sure to have full context)14:26
evrardjpok14:26
evrardjpcool14:26
evrardjplet's talk about that next meeting14:26
mnaserit's being taken care of :)14:26
evrardjpyeah, sorry for checking! :p14:26
evrardjpok next14:27
evrardjp#topic mnaser report on sync with swift team14:27
*** openstack changes topic to "mnaser report on sync with swift team (Meeting topic: tc)"14:27
evrardjpI had this topic pending14:27
mnaseri think that should have been removed a while back14:27
evrardjpit was on py3, I think we can remove14:27
evrardjpok14:27
evrardjpsounds good14:27
evrardjpnext14:27
evrardjp#topic ttx report on Technical vision reflection update14:28
*** openstack changes topic to "ttx report on Technical vision reflection update (Meeting topic: tc)"14:28
*** Luzi has quit IRC14:28
evrardjp#link https://media.giphy.com/media/Y4tXwMTNHStfxDxduD/giphy.gif14:28
ttxI have not started that yet. I hope to get it going early January14:28
evrardjpok14:28
ttxso that I can report about it at next meeting14:28
ttxI might start it end of December tho14:28
evrardjpthat would be good, if you want to discuss about it in January14:29
evrardjpholidays and stuff :)14:29
evrardjpok14:29
evrardjpnext14:29
evrardjp#topic mnaser summary of the maintain issue with Telemetry14:30
*** openstack changes topic to "mnaser summary of the maintain issue with Telemetry (Meeting topic: tc)"14:30
mnaserit seems like catalyst picked up ceilometer work and ran away with it14:30
evrardjpI still have that in the topics, it was discussed in the PTG, continued over ML14:30
mnaserlike, literally, ran away with it14:30
mnaserother projects suggested working together to leverage their backends14:30
mnaserand the current roadmap for ceilometer is "add the api again, add mongodb support again, go back in time"14:30
jroll:/14:31
evrardjpI remember a tweet pointing to that ML thread indede14:31
evrardjpyes.14:31
mnaserhttps://storyboard.openstack.org/#!/story/200689314:31
mnaserhttps://storyboard.openstack.org/#!/story/2006894v14:31
evrardjpmnaser: did we start a conversation with them, to engage into not running back in time? :p14:32
mnaseri tried to politely steer the convo in the ML14:32
evrardjp#link https://storyboard.openstack.org/#!/story/200689414:32
evrardjp#link https://storyboard.openstack.org/#!/story/200689314:32
jrollfwiw, I know we discussed putting metrics directly in prometheus at some point, I did some poking at that, and the python client is... not awesome. gets weird with multithread/process wsgi runners, and doesn't do any sort of quantile metrics (I was surprised this is up to the client, not the server)14:32
mnaserand i think i got a "this is what the ceilometer team is doing."14:32
jrollbut just a data point, we'd need to do some work there first14:33
mnaserand then there was a few other proposals from other teams like monasca to integrate14:33
evrardjpjroll: this was the next topic as a smooth transition :)14:33
mnaserthat were ignored, i asked for an update on what was the final decision, no answer, yoctozepto did as well (2 days ago) -- nothing. http://lists.openstack.org/pipermail/openstack-discuss/2019-December/011337.html14:33
evrardjpmnaser: :/14:33
jrollaha, I shall wait14:33
mnaserhttp://lists.openstack.org/pipermail/openstack-discuss/2019-November/011236.html14:34
mnaserasked on nov 2814:34
*** e0ne_ has quit IRC14:35
evrardjpI see it didn't really result in new stance14:35
mnaserhttp://lists.openstack.org/pipermail/openstack-discuss/2019-November/010972.html14:35
mnaserthat is where it starts to feel concerning tbh14:35
mnaser"we're going to maintain and support our use case"14:35
*** jamesmcarthur has joined #openstack-tc14:36
jrollI wonder if they're unwilling to support monasca/etc, or just saying it works well14:36
mnaseryes i get it, this is open source, no one is entitled, but we also ask people to do whats best for openstack, not whats best to maintain your legacy piece of code14:36
evrardjpisn't that fair though? Are they refusing code from others?14:36
jrollwonder if lxkong is around14:36
mnaserits probably late there14:36
jrollyeah14:36
zaneb3.30am14:36
evrardjpjroll: agreed, that's basically my question14:36
mnaseranyways, i don't want to sit and send emails to the entire ML every other day if there's no reasonable outcome that that the tc has any influence obn14:36
ricolinI don't think that means they will refusing others14:37
mnaserif you're going to invest all that time14:37
zanebon one hand, it's fair to say that if nobody else is contributing, they'll contribute what they want to contribute14:37
evrardjpmnaser: not being an official project is the only thing we can do, but this is not something I want to arrive to right now14:37
evrardjpand that's only if it's not open to contributions14:37
mnasermight as well as invest it in the right way14:37
ricolinzaneb, true14:37
mnaserzaneb: yeah personally im torn on that14:37
zanebon the other hand, who is going to show up and contribute when they're making it clear that they're only interested in maintaining their legacy stuff from 5 years ago?14:37
mnaser"do the right thing if you're gonna do the work anyways" vs "anything better than nothing"14:38
evrardjpzaneb: yes indeed14:38
*** e0ne has joined #openstack-tc14:38
evrardjpalso if it works for them, could that work for others? just curious14:38
zanebI think we should discuss with them whether they could continue to meet their goals as an unofficial project14:39
evrardjpzaneb: it will not be the only project to be single vendor in openstack :p14:39
mnaseradding the api back is a serious change in direction14:39
zanebbecause I don't see that they're getting great benefit from it being in OpenStack, and for other people it's only creating confusion14:40
ttxevrardjp: we could also force a PTL change, but that's also nuclear and it's not as if we had likely candidates14:40
evrardjpI agree, but as TC we probably shouldn't intervene on the project, but helping on the ecosystem, and I haven't seen evidence it's not helping the ecosystem as a whole right now14:40
zanebif they're ok with it leaving OpenStack officially, then our job is relatively easy14:40
*** jamesmcarthur has quit IRC14:40
jungleboyjYeah.14:40
zanebif not then we have some hard discussions to have14:41
jungleboyjIs there a precedent for forcing at PTL change?14:41
evrardjpI don't want to go there though -- I know it's a radical change for users, but is it for a bad thing for the ecosystem?14:41
ricolinI been promised by telemetry PTL of a status report, we should ask some questions to them to clarify the current status14:41
mnaserlets not go down the forced PTL change route discussion14:41
zanebyes, let's not14:41
jungleboyjmnaser:  ++14:41
gmanno/, sorry i missed the time change thing.14:41
evrardjpricolin: good idea, and if it still benefits everyone in the community would be a nice question14:41
njohnstonmnaser++14:41
jungleboyjOk, wanted to make sure that others felt that way.14:41
evrardjpmnaser: agreed14:42
mnaserwe're discussing the issue much more than trying to gather an update14:42
mnaserdoes anyone wanna come up with some next steps14:42
evrardjpricolin: just did14:42
evrardjpwell14:42
mnaserok, so ricolin has an action item of getting a status update, id hope before the next meeting cause that would mean a month of work (in maybe) not the ideal direction.14:42
evrardjpbetween the lines :)14:42
evrardjpok you want a status update before next meeting14:43
evrardjpthat sounds good, can we discuss this at next week's office hours?14:43
mnaseri dont want one, i think it would be beneficial, because a month is a long time14:43
evrardjpthat's fair14:43
ricolinWondering if there's any other resources/info. we need from them?14:44
ricolinbesides status update14:44
evrardjpricolin: I guess what would matter for mnaser would be having a good chat of what's going on, why the decision -- while people seem so eager to not do that14:44
evrardjpwow my english is terrible14:45
evrardjpI think users need answers on the direction taken, to know how they can contribute or not. And if it's not the direction that some people want to take, ensuring that the voices are heard14:46
ricolinevrardjp, it's better than your chinese:)14:46
mnasergiven my constant complaints about magnum (which ended up cleaning up a lot of it's stuff), i did really end up feeling pretty awful in the whole thing because it pushes people14:46
mnaserand the employer of this PTL is the same as the magnum one at the time, so id rather sit and talk from the sidelines14:46
evrardjpok14:46
ttxI wonder if someone should not raise the situation again (not mnaser) to show that the concern is a TC concern14:46
mnaseri assume that s/not/now/14:47
ttxnow raise, not mnaser yes14:47
ricolinI will take that action tomorrow and asking for the status report too from PTL:)14:48
evrardjpricolin: I can do that with you, as my chinese is awful :p14:48
evrardjplet's sync on that14:48
ricolinyes, definitely14:48
ttxit can only help if the person is close to teh APAC tz, so +114:48
ricolinttx evrardjp sweet!14:48
evrardjp#action ricolin evrardjp talk with PTLs about the direction of telemetry (see meeting log for detailed AP)14:48
evrardjp#topic mnaser report on oslo metrics project14:49
*** openstack changes topic to "mnaser report on oslo metrics project (Meeting topic: tc)"14:49
evrardjpjroll: you also wanted to say a few words about this?14:49
jrollI'll let mnaser speak first, I just have some recent experience with prometheus here14:49
mnaseri didn't progress on this, i think bnemec is not as involved in openstack-y things and he spoke with the LINE team, maybe ttx can help with the intro/sharing of the code :<14:49
jrollwas LINE using prom, IIRC?14:50
mnaseryeah14:50
mnaseri think?14:50
jrollcool, I'd love to see the code14:50
bnemecYeah, we talked in Shanghai. We're waiting on them to propose the new library and make the code available.14:50
evrardjpok14:50
* ttx checks notes14:50
jrollas I mentioned before, the official python client for prom has some problems that make it not ideal for usage in openstack14:50
jrollbut they seem relatively solvable14:50
ricolinthey got a presentation for their structure, back in summit14:50
evrardjpjroll: can you push from your side to see the code, so I can ask you in a month how is this going?14:51
evrardjpthat would be amazing14:51
ricolinbnemec, is there any update from them now?14:51
ttxyes, os.metrics instrumenting oslo.messaging to send to Prometheus14:51
* ricolin knows it still early to ask14:51
jrollevrardjp: I have no contacts there, all I could do is ask on the ML, not sure if that's helpful14:52
evrardjpargh14:52
bnemecI don't think they're using prometheus from the OpenStack side, they're just exporting metrics in a way it can consume.14:52
evrardjpjroll: maybe bnemec has :p14:52
evrardjpand he seems just here14:53
evrardjp:D14:53
bnemecThey did a presentation during the forum. Can probably contact those folks.14:53
evrardjpawesome!14:53
evrardjpI think if you can contact them, and introduce to jroll that would be the first step14:53
gmannjroll: you can reach out to dinesh (he used to be on irc, i can check his irc name)14:54
jrollI don't want intros, only code14:54
jrollheh14:54
evrardjpfair14:54
jrollI am happy to reply in an email chain about how excited I am to see the code, if that will motivate them14:54
evrardjpbut those ppl can give you links14:54
evrardjpok let's settle for that then14:54
evrardjp#action jroll to use his email client to see code14:55
evrardjpahem ahem14:55
jroll-.-14:55
*** e0ne has quit IRC14:55
evrardjpoh come on, that was hilarious.14:55
ttx"."14:56
fungitough crowd14:56
evrardjpok we have so many things14:56
evrardjplet's continue14:56
evrardjp#topic gmann report on community goals for U/V/py2 drop/rolling to py3/goal select process schedule14:56
ttxgood thing we have an office hour to go deeper14:56
*** openstack changes topic to "gmann report on community goals for U/V/py2 drop/rolling to py3/goal select process schedule (Meeting topic: tc)"14:56
*** jeremyfreudberg has joined #openstack-tc14:56
jungleboyj*sad_trombone.wav*14:56
evrardjpjungleboyj: :)14:56
evrardjpI will give you gifs14:56
evrardjp#link https://media.giphy.com/media/3oEhn3lV6Yk1Ku6WRi/giphy.gif14:57
gmannUssuri goal update: 1. py2 drop - this is going on, many services has merged the patches and other are in progress. This is in good progress. 2. PTl and Contributor guide- goal is not yet merged - https://review.opendev.org/#/c/691737/14:57
evrardjpoh wait, a better python drop14:57
evrardjp#link https://media.giphy.com/media/zzkFADpR7k2NG/giphy.gif14:57
gmannI have only one concern left there is to have template for PTL guide so that projects can maintain the conssitency14:57
gmannconsistency14:57
evrardjpdiablo_rojo: ^14:57
jungleboyjgmann:  ++14:58
diablo_rojogmann, I think that there were concerns that having as its own separate document might be too time consuming for a small amount of people14:58
gmannbecause not all read the expectation till we have the defined template . for example projects does not read the py drop schedule and start dropping the py2 from python client lib also and i have to -1 them every time14:58
diablo_rojoI also think that there may not be that much different than needs to be mentioned?14:58
diablo_rojoAlso that its fine living in CONTRIBUTING.rst because being a PTL is form of contribution14:59
evrardjpgmann: arrgh14:59
gmanndiablo_rojo: i think common PTL guide we have currently does not reflect all PTL works.14:59
diablo_rojo(I think I also wrote all/most of this in the review of the template yesterday)14:59
diablo_rojogmann, no? Well that should probably get updated with all the common work that PTLs do them14:59
diablo_rojoOnly the project specific stuff should live in the template15:00
evrardjpok let's talk one topic at a time, now talking about the U - PTL goal part15:00
gmannok, we can discuss that in office hour.15:00
evrardjpwe are in the office hour basically :)15:00
diablo_rojoLol sorry15:00
gmann:)15:00
gmannV goal-  zuulv3 goal is under review which we decided to have as pre-selected as V cycle15:01
evrardjpok that's good15:01
gmanngoal schedule - I am going to propose the schedule up by today.15:01
evrardjpthanks15:01
gmannthat's all from my side15:01
evrardjpfor all those points (before we circle back to the problems), do you need any help?15:01
gmannwe are good on these.15:02
evrardjpok15:02
gmannwe will discuss more on PTL goal next in office hour15:02
evrardjpyou mean next week?15:02
evrardjpor is my agenda broken?15:02
gmanntoday15:03
*** rpittau is now known as rpittau|afk15:03
evrardjpor after the meeting15:03
evrardjpok15:03
evrardjpgot it15:03
gmannyeah after meeting15:03
evrardjpsounds good, I need to accelerate then15:03
evrardjp#action gmann discuss about the issues in the U goals at the next office hours15:03
evrardjp#topic jungleboyj update on the blog post about the analysis of the Foundation user survey15:03
*** openstack changes topic to "jungleboyj update on the blog post about the analysis of the Foundation user survey (Meeting topic: tc)"15:03
jungleboyj:-)  I have this in my sprint plan for the week.15:04
evrardjpjungleboyj: are you there? Do you have an eta? :p15:04
evrardjpwoot15:04
evrardjpawesome15:04
jungleboyjSo, should have something for this next week.15:04
evrardjpI am writing that down for next meeting15:04
jungleboyjevrardjp:  Sounds good.15:04
evrardjpmugsie: are you there?15:04
evrardjpit's for the next topic which also takes time15:04
evrardjp#topic mugsie update on release naming progress15:04
*** openstack changes topic to "mugsie update on release naming progress (Meeting topic: tc)"15:04
evrardjpI want to put this to bed15:05
evrardjpit's been far too long15:05
smcginnis++15:05
jungleboyjevrardjp: ++15:05
evrardjpI thought we reached consensus during PTG, but I was wrong15:05
ttxWhat's the standing objection at this point ? Not enough votes?15:06
evrardjpgmann: thinks it's not respecting opinions of the people, if I am not mistaken15:06
evrardjpwhich leads to me to think it's possible to invert the things: tc proposes names and community votes15:06
evrardjpinstead of the opposite: community propose names and tc votes15:07
evrardjpthough it will still make the life of the voting complex15:07
smcginnisI liked the community proposed named better.15:07
smcginnis*names15:07
jungleboyjsmcginnis:  Agreed.15:07
mnasersmcginnis: +9million15:07
zanebevrardjp: that would be a ton more work for the TC15:07
evrardjpme too, as it was also transparent for which tc member has voted, so it was still transparent for members15:07
jungleboyjI thought that that is the important thing.15:07
evrardjpok15:08
evrardjpso we are all in agreement again15:08
evrardjpI am glad. Let's vote in majority for this and make it15:08
gmannonly issue I have is let community decide the final name and anything else is all fine to me(who choose the name etc)15:08
zanebspeaking with my community member hat on, the fun part is looking for names15:08
ttxzaneb: yes15:08
mnaserwait what are we voting in majority for?15:08
jungleboyjzaneb: ++15:08
zanebvoting is boring and the outcome is usually terrible no matter who chooses it15:08
fungialso conducting a vote of the entire community has a lot of rough edges15:09
jungleboyjWe may get some heat for the votes, but that is part of the work of leadership.15:09
smcginniszaneb: ++15:09
ttxmnaser: community propose names and tc votes15:09
smcginnisCould care less about voting on it.15:09
ttxmnaser: I know you disagree :)15:09
mnaserill make my own little twitter poll15:09
smcginnisCommunity elects TC, TC picks the name.15:09
mnaserand then the community can have my vote if im on tc15:09
ttxmnaser: sure, that works too15:09
mnaser:P15:09
smcginnisAnd the community can lobby for their preferences.15:09
gmannthat is what current proposal in review is so what is difference15:10
evrardjpyeah people circled to the current proposition15:10
ttxWe should definitely try to pick the community's consensus rather than our personal preference15:10
evrardjpbecause they like it15:10
ttxif they differ15:10
jungleboyjMakes sense.15:10
evrardjpI think we'll never get a full "I agree on this proposal" and this sounds the best we ever had on the topic15:11
evrardjpI propose we continue with the current proposal15:11
jungleboyjevrardjp:  ++15:11
ttxI want it changed before we get to W15:11
evrardjpok15:11
ttxand this one fills the bill. Not my preferred option, but I can live with it15:11
jungleboyjYeah.  We need to move foward.15:11
evrardjpI am sorry if it doesn't please some people here, but it's the one that gets the most ppl "ok"15:12
evrardjpit's the "compromis a la belge"15:12
evrardjpnoone is really happy with it, but it works on average15:12
jungleboyjI beg your pardon?  ;-)15:12
evrardjpok let's move on15:12
gmannttx: if i understand your comment. you mean to get vote from community on that review ?15:12
gmannor get their opinion via ML15:13
ttxgmann: try to pick a name that seems to be supported by the community, rather than your own unique preference15:13
ttxi.e. not a time to be original, more a time to try to sense what would please / represents the community15:14
gmannohk15:14
evrardjpit involves tc members talking to the community15:14
ttxWhich is somethign we did every time we bent the rules in the old system15:14
ttxlike to propose "Train"15:14
mnaseri hate to be that guy, but (to my disagreement) we mentioned those meetings are status updates, not full on discussions on what we want to do.  i'm not opposed to changing the theme but just want to be aware of time15:14
gmannwhich is very difficult :) this is kind of getting their vote in different way15:14
* mnaser doesnt want to walk out but also has $things15:14
evrardjpfair15:14
evrardjpyou're right mnaser15:14
jrollmnaser: ++15:14
ttxok, moving on let's close tat meeting15:14
evrardjplet's move on15:14
mnaserthis is healthy office hours discuss imho15:15
mnasers/discuss/discussion/15:15
evrardjp#topic ttx update on a possible merge tc/uc15:15
*** openstack changes topic to "ttx update on a possible merge tc/uc (Meeting topic: tc)"15:15
ttxNot started yet, expecting to start the discussion in January after the ops meetup. Will report next meeting.15:15
evrardjpmnaser: agreed15:15
evrardjpok15:15
evrardjp#topic evrardjp report on the concepts repo15:15
*** openstack changes topic to "evrardjp report on the concepts repo (Meeting topic: tc)"15:15
evrardjpcrazy ideas*15:15
evrardjpnot done, I will work on it during my holidays next week15:15
evrardjp#topic extra topics15:16
*** openstack changes topic to "extra topics (Meeting topic: tc)"15:16
evrardjp#info evrardjp patches pending15:16
evrardjpwe have plenty of patches pending, please vote15:16
evrardjplike plenty plenty15:16
evrardjp#info mnaser summary on the stable branch policy discussion since summit15:16
evrardjp(this is the last item for the report, we can close the meeting afterwards -- I have at least two topics to talk in office hours -- the tc election dates, and a reflection)15:17
mnaserwe seem to have come to some sorts of consensus, i am finding time to draft up a change to openstack/governance soon, the consensus seems to be "stable teams are kept as is, stable cores can add other stable cores"15:17
evrardjpok15:18
evrardjpsounds good15:18
evrardjpno report next month, as I suppose you'll draft up the change, ok?15:18
jungleboyjSounds good to me.15:18
evrardjpthanks everyone!15:18
jungleboyjThanks!15:18
zanebcan we have one volunteer to retroactively vote for https://review.opendev.org/681266 for compliance?15:18
evrardjp#endmeeting15:18
*** openstack changes topic to "OpenStack Technical Committee office hours: Tuesdays at 09:00 UTC, Wednesdays at 01:00 UTC, and Thursdays at 15:00 UTC | https://governance.openstack.org/tc/ | channel logs http://eavesdrop.openstack.org/irclogs/%23openstack-tc/"15:18
openstackMeeting ended Thu Dec  5 15:18:44 2019 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:18
openstackMinutes:        http://eavesdrop.openstack.org/meetings/tc/2019/tc.2019-12-05-14.00.html15:18
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/tc/2019/tc.2019-12-05-14.00.txt15:18
openstackLog:            http://eavesdrop.openstack.org/meetings/tc/2019/tc.2019-12-05-14.00.log.html15:18
ttxThanks evrardjp !15:19
diablo_rojothanks evrardjp!15:19
ricolinthx evrardjp :)15:19
evrardjpI will do better time management next time. I thought we had progress, so didn't want to interrupt15:20
* jroll sees jungleboyj and diablo_rojo as good candidates to vote on 68126615:20
evrardjpzaneb: not sure what's missing though15:20
gmannevrardjp: thanks15:20
zanebevrardjp: I replied on the list15:20
jrollevrardjp: we need 2/3 majority to change the charter, which is 9 members, only 8 voted15:20
* jungleboyj goes to look.15:20
zanebone of gmann, mugsie, jungleboyj, diablo_rojo, mnaser15:21
evrardjpI thought this was formal vote. you're right.15:21
zanebyeah, it had the wrong tag15:21
evrardjpit was a honest mistake, my bad15:21
* diablo_rojo opens tab15:21
zanebI don't think we document that tag in the house rules15:21
zanebso the rules are spread between the charter and the house rules doc15:22
evrardjpnope but it's documented I think15:22
evrardjpyeah that kinda is bad15:22
zanebit is, in the charter itself15:22
jungleboyjI was in support of it.15:22
zanebI can propose a patch to reference that15:22
evrardjpI guess it wouldn't hurt15:22
evrardjpcan you tackle that zaneb?15:22
diablo_rojoOh yeah, I agreed with this change. Somehow missed the review.15:22
diablo_rojoYou want me to +2 now?15:22
jungleboyjI think it is better to keep an odd number and slowly reduce.15:23
jungleboyjIt is merged.  :-)15:23
evrardjpdiablo_rojo: yes15:23
evrardjpin the comments15:23
zanebjungleboyj, diablo_rojo: if you can just leave a comment approving, then we can call it closed15:23
gmannvote now on merged one ? I too agree on that but missed the vote15:23
diablo_rojojungleboyj, I know is ;) But I think they need to meet the threshold now for formalities sake15:23
evrardjpyou can still comment15:23
evrardjpnot technically vote I think15:23
evrardjpbut that's good enough for us15:23
jungleboyjAh.  Ok.  Done.15:24
evrardjpthanks15:24
zanebthanks, that's that sorted15:24
jungleboyjJust wanted to make sure I was looking at the right vote.  :-)15:24
evrardjpthanks zaneb for noticing too15:24
diablo_rojoAlso done.15:24
jungleboyjdiablo_rojo:  ++15:24
jungleboyjThe rules are no longer broken.15:24
gmanndone15:24
zaneb\o/15:24
diablo_rojo#nailedit15:25
evrardjpediting nails?15:25
zanebjungleboyj, diablo_rojo, gmann: thanks!15:25
gmannI want to discuss the Contributor & PTL guide goal to close it asap. if all ok ?15:25
jungleboyjgmann: ++15:25
evrardjpyeah it's office hours15:25
evrardjpI think during office hours we probably need to chat about election dates though, so let's keep that in mind15:26
gmanndiablo_rojo: i replied on the PTL guide requirement on template patch. if i understand clearly- you mean we do not need separate guide for PTL ?15:26
gmannevrardjp: sure.15:26
gmannmy impression from goal was two separate guide.15:26
*** e0ne has joined #openstack-tc15:29
diablo_rojogmann, correct. I think initially I thought they should be separate, but after putting together the template, I think it can be all one doc15:29
diablo_rojoHappy to update whatever goal phrasing.15:29
evrardjpassuming goal phrasing is updated, would that remove the concern of yours gmann?15:30
diablo_rojoI don't want to put too much load on PTLs/ex PTLs since there aren't many of them to help out with this part of the goal15:30
evrardjpI am not sure I understood the fundamental issue there15:30
jungleboyjThat template looks pretty good.15:30
*** jcapitao is now known as jcapitao|afk15:30
diablo_rojoevrardjp, basically the original thought was that the two documents would be separate15:30
diablo_rojoI have combined them to simplify the goal/make it easier on PTLs/ex PTLs15:31
gmannbut having PTL specific tasks/best practice in Contributor guide is not right place i think as per the audience of both the guide15:31
diablo_rojobut that might not be clear enough in the current phrasing of the goal15:31
evrardjpyeah but that's details, not a fundamental issue?15:31
evrardjpoh now I see gmann's concern15:31
jungleboyjI assume if the team already has a separate set of documents linking to them from there isn't an issue?15:31
evrardjpcan this be done at the same time in two files?15:31
diablo_rojogmann I can see the argument for having it separate, but I also think being a PTL is another form of contribution15:31
jungleboyjdiablo_rojo:  ++15:32
diablo_rojowhile it might not be the focus of a new contributor, it could be a goal long term15:32
gmannfor exmple for nova case- https://docs.openstack.org/nova/latest/contributor/ptl-guide.html15:32
diablo_rojo(hence why it is at the bottom of the template)15:32
evrardjpso the document would be from new contributor to core to ptl?15:32
gmanni am ok if project does not have project specific PTL guide but if they have it might be too much text in same guide15:33
jungleboyjgmann:  Right, and for the teams that are like that just put an intro and a link in that section.15:33
jungleboyjevrardjp:  ++15:33
diablo_rojogmann, okay so the concern is that its too much in one doc?15:33
evrardjpthat sounds a reasonable approach as the structure would stay consistent, but the details can be cross linked if too heavy15:34
diablo_rojogmann, I would hope there isnt **that** much different between roles, but I guess thats something to learn with this goal :)15:34
evrardjpthat's fine for me15:34
jungleboyjevrardjp: ++15:34
fungiseems like if the contributing.rst mentions a separate ptl-notes.rst or whatever that ought to be sufficient for people to find it without making it mandatory that everyone keep theirs in a separate file15:34
diablo_rojoevrardjp, yeah I have the common ptl guide linked in the template already15:34
jungleboyjI don't think it is really worth arguing over.15:34
evrardjpjungleboyj: ++15:34
evrardjpit seems like people are in agreement over the goal, but not over the details15:34
evrardjpso that's already a good thing15:35
gmannbut where project specific PTL tips goes ?15:35
fungigmann: what if a team doesn't have ptl tips unique to their team?15:35
gmannevrardjp: yes, it is all on implementation details, goal is all agreed15:35
fungithat seems like it could be a majority of teams15:35
diablo_rojogmann, in the contributing.rst further down in the ptl section15:35
evrardjpgmann: If I understood correctly, that's inside the same document, however, that can be cross linked (the full text doesn't need to be copied twice)15:35
gmannfungi: yeah they can have common guide link and keep the guide open for future notes15:35
diablo_rojoI mention the common guide we have and then I encourage people to add specifics to their project after15:35
diablo_rojohttps://review.opendev.org/#/c/696001/2/CONTRIBUTING.rst15:36
diablo_rojo5915:36
diablo_rojoI can change the template to actually mention the link instead of having it in a note15:36
diablo_rojoThat's easy.15:36
diablo_rojo(gotta clean up whitespace anyway apparently)15:36
fungiseems like just asking teams to update their contributing.rst to have some consistent sections is already a lot and asking them to also maintain a new document with ptl notes they may not even need is going to reduce the chances that teams bother to get it done15:36
gmann yeah if we cross link it is fine but I mean we should provide a guide to each project saying that this is PTL guide and mention the best practice or notes you want to transfer as KT to new PTL15:37
diablo_rojofungi, +215:37
*** jamesmcarthur has joined #openstack-tc15:37
diablo_rojogmann, okay so I just need to update the template to make the link not a note anymore and actual text?15:37
jungleboyjSo, just word it as having the separate document is optional.15:37
diablo_rojoEasy. Will do that today.15:37
diablo_rojojungleboyj, can add that too15:38
diablo_rojosince Nova and maybe others potentally already have that.15:38
jungleboyjdiablo_rojo:  ++15:38
diablo_rojoI figured that was obvious, but I can make it explicit :)15:38
gmannthey can have common guide link as default or any project specific guide + common guide etc15:38
fungialso remember that every repository has a contributing.rst file, there's already going to be a lot of duplication... making a team with 20 or 50 repos keep a synchronized copy of a ptl notes doc in all of those is questionable15:38
jungleboyjdiablo_rojo:  I agree but I think that addresses the concerns here.  :-)15:39
openstackgerritBrian Haley proposed openstack/governance master: Add ovn-octavia-provider project  https://review.opendev.org/69709515:39
fungicontributing.rst should tell people where to find information on how to contribute to that repository15:39
diablo_rojojungleboyj, +215:39
gmannfungi: that is why i was thinking a separate guide and have them in single place15:39
*** jcapitao|afk is now known as jcapitao15:40
diablo_rojofungi, +2, while a lot of the template might be the same across all repos for a single project, I think there are things that will be different too.15:40
fungigmann: that only makes sense for teams which need it though, and so isn't really goal material on its own?15:40
gmannlike PTL-guide and that exist in spec repo or wiki or any common place not per repo under project15:40
gmannsure, i thought we discussed that we want every project to do PTL KT transfer guide for new PTL but I am ok to drop that as part of goal and let project do if they need15:41
fungisure, having the contributing.rst template include a default reference to the openstack ptl guide seems reasonable, and teams can adjust that if they have a team-specific ptl guide somewhere they want referenced15:41
gmannagree.15:42
evrardjpwoot15:42
*** jamesmcarthur has quit IRC15:42
diablo_rojogmann, I still think it should be mentioned as part of the goal, but the pressure to write out an entire separate doc is a little much. It would be great, but filling out a section of the contrib.rst is enough for me.15:42
diablo_rojofungi, +215:42
evrardjpit seems you are reaching consensus15:42
diablo_rojoevrardjp, don't jinx it!15:42
fungiasking teams to document any team-specific things ptls need to know seems fine. asking teams to make up their own processes so they have something to document outside the openstack ptl guide is not something which makes sense on the other hand ;)15:42
evrardjpdiablo_rojo: hahaha15:43
diablo_rojofungi, lol agreed15:43
gmanndiablo_rojo: yeah, we can mention that in template (you already mentioned) and in goal detail also that project need their PTL tips/work can still link to Contributors.rst section15:43
diablo_rojogmann, can do15:44
diablo_rojoI'll get those changes up today.15:44
gmanndiablo_rojo: thanks.15:44
fungii do also think that generally the contributing.rst template should be kept as brief as possible. it'll be best as durable links to things contributors need to be aware of so that the documentation being linked to can be updated more centrally without needing to push regular updates to every repo15:44
jungleboyjfungi:  ++15:45
diablo_rojofungi, +215:45
diablo_rojoI tried to keep my text that I did add terse.15:45
evrardjpdiablo_rojo: you wanted to chat over election dates15:45
diablo_rojoevrardjp, I did..15:45
fungilike "here's the bug tracker for this repo, here's where you can find instructions for proposing changes, here's where you can view our team's policies..."15:45
evrardjptc-members ^15:45
diablo_rojoHas everyone seen the email I sent yesterday about the primary three options?15:46
evrardjpsorry I meant: tc-members, we should talk about election dates15:46
jungleboyjYep.15:46
njohnstonyes15:46
gmannfungi: yeah, that is main objective. links not changeable text15:46
jrollyeah, I read that15:46
gmannevrardjp: yeah15:46
diablo_rojoCool. So. Thoughts?15:46
diablo_rojoGlad so many people read my email lol15:46
evrardjpI have seen the options, but there isn't a fourth one, based on fungi's answer?15:46
* diablo_rojo didn't see replies with opinions15:46
jungleboyj:-)15:47
* gmann have not read the email or coffee yet :(15:47
jungleboyjEveryone is opinionated.15:47
zanebwas going to reply to the thread, but I think clearly our old formula is no longer fit for purpose with the new events plan15:47
evrardjpI don't have enough information to have an opinion15:47
fungiyeah, my term duration subthread was more to ask whether i'm misinterpreting or too strictly interpreting the bylaws and charter15:47
diablo_rojoevrardjp, I think its a shifting of all dates forward to match the charter requirement?15:47
jungleboyjzaneb: ++15:47
evrardjpzaneb: agreed15:47
njohnstonzaneb: ++15:47
diablo_rojogmann, I sent the email so I don't need to read it again, but I also have not caffeinated yet15:47
evrardjpyes, because we can't update the charter for the current elected members15:48
* diablo_rojo is horizontal on her couch wrapped up in blankets with her laptop 15:48
zanebdiablo_rojo: speaking of which, could you update your vote on https://review.opendev.org/695071 after caffeine? ;)15:48
evrardjpterrible position, you're gonna get problems when you're gonna get older15:48
gmanndiablo_rojo: :) read it quickly15:48
fungiright now i feel like the combination of what the osf bylaws require of the tc and what the tc charter says result in painting us (tc members and election officials) into a bit of a corner shcheduling-wise15:49
* diablo_rojo swaps tc hat for election official hat15:49
evrardjpterrible position to type*15:49
jungleboyjevrardjp: ++15:49
jungleboyjThat was how I got a bulging disk.15:49
diablo_rojoI really just want a decision on the dates for today if we can, and then we can figure out what else needs to change as a result later?15:49
diablo_rojoif that's feasible?15:49
* jungleboyj realizes how old that sounds now15:49
evrardjpjungleboyj: :)15:50
evrardjpmmm15:50
diablo_rojozaneb, lol, will do15:50
zanebevrardjp, jungleboyj: I thought this was TC office hours not geriatrics office hours15:50
evrardjpzaneb: you're still welcome15:50
*** jeremyfreudberg has quit IRC15:50
* jungleboyj laughs15:50
zaneblol15:50
evrardjp:p15:50
fungiit's all goiters and bunions up in here15:50
evrardjpdiablo_rojo: doesn't have an answer with that15:50
jungleboyjewwww15:50
evrardjpdiablo_rojo: do our opinion matter?15:51
evrardjp(assuming we respect the charter)15:51
jrolldo we think the combined election would be difficult for the electorate? if not, and it's easier for officials, I'd prefer that15:51
evrardjpI trust the elections wg15:51
diablo_rojoevrardjp, yeah they do, I dont think the election offcials have the authority to decide on their own?15:51
diablo_rojoUnless you just want to delegate to us?15:51
fungijroll: we did a combined election last time, and it went well enough15:51
jrollah, ok15:51
evrardjpdifference between authority and trust :)15:52
jungleboyjfungi: ++15:52
jrollcombined is my vote then :)15:52
jungleboyjThat is true.15:52
gmannyeah, i think combined election was easy for electorate too15:52
fungigranted, we had no polls to run last time because there were no contested ptl seats and exactly the required number of tc candidates to fill the open seats there15:52
njohnstonI trust the elections officers... and chances are that, like the last election, we will have a very small number of contested PTL slots (if any) so there is little work to do there15:52
jrollyeah, I don't imagine this election would be very contentious either15:52
diablo_rojonjohnston, this is true15:52
gmannfungi: which i assume going to be the same this time15:52
evrardjpdoes that work with current charter?15:52
diablo_rojoI expect reducing the seats will encourage polling for the TC election though15:52
jungleboyjTrue ...15:52
jungleboyjdiablo_rojo:  ++15:52
diablo_rojoevrardjp, uhhhh, I will defer to fungi on that one15:53
njohnstondiablo_rojo++15:53
gmanni  mean for PTL15:53
diablo_rojoI think no?15:53
fungithe scheduling challenge with combining the elections, as i see it, is that the bylaws require that the terms for tc seats are set before anyone is elected to fill them, so we can't say now that folks elected months ago are going to serve for 13 months instead of the default 1215:53
zanebdiablo_rojo: you'd hope so, but...15:53
diablo_rojoUnless we shift up all the elections to conclude early15:53
evrardjpexactly15:53
fungiso that means that we're stuck holding the tc election at the start of march15:53
evrardjpok so15:53
fungione year from when those seats were previously elected15:53
evrardjpwhy not doing PTL at the same time?15:53
diablo_rojozaneb, I like to be blissfully unaware of the inner workings of the charter, but I probably should come to terms with needing to know it at some point15:54
jungleboyj:-(15:54
evrardjpfungi: not sure when we say "term expires" in March 2020, does that mean beginning of end of march15:54
fungiif we elect "v" cycle ptls at the start of march, that's before ussuri milestone 3 so they sit around for a while before their terms start15:54
zanebdiablo_rojo: sorry, that was reference to the previous comment about reducing the seats encouraging polling15:54
evrardjpmemory is fading (another topic for geriatric office hours)15:54
evrardjpfungi: "sitting around" sounds unlikely15:55
jungleboyjfungi: Does that really matter?15:55
fungievrardjp: the bylaws say "12 months" so it's ostensibly open for interretation15:55
evrardjpbetter transition :)15:55
zanebevrardjp: it's a year after the last election imho15:55
diablo_rojozaneb, ah, yeah thats true I suppose lol15:55
gmannyeah it will be too early for PTL election ussuri is planned to release on May15:55
evrardjpzaneb: indeed, which is why my memory is fading15:55
fungijungleboyj: in the past we've had ptl candidates say that the further out their terms end from the time they self-nominate, the harder it is for them to be sure they can commit to serving the full term15:55
*** iury_course has quit IRC15:55
fungii don't know whether that's still the case15:56
jungleboyjHmmm, interesting.15:56
diablo_rojoSo we can stick to option 1 then?15:56
zaneb"Voting ends Mar 05, 2019 23:45 UTC."15:56
evrardjpwe are not saying that15:56
evrardjpthanks zaneb!15:56
diablo_rojoThat does the TC election in March waits a week and then does the PTL election?15:56
evrardjpwould it be possible to have everything ending on March 5th?15:57
evrardjpor around that date15:57
diablo_rojoevrardjp, we could but that would be suuuuuper early for PTL elections I think15:57
gmanni vote for the combined election every time and change the charter or bylaw for TC term things15:57
diablo_rojowith the concern that too early makes it hard for people to commit15:57
gmannthat can solve the problem which can occur everytime15:58
evrardjpgmann: yes we agree on changing the charter for the future, we are just concerned about this one15:58
diablo_rojoI personally (as an election official) like the combined election approach15:58
fungithat would mean the election concluding on r10 in the ussuri release schedule: https://releases.openstack.org/ussuri/schedule.html15:58
gmanncannot we do for this time also? i mean change before the election dates finalized15:58
evrardjpno because it wouldn't apply to current terms15:58
fungi7 weeks before r3 when rc1 is targeted15:58
jungleboyjIf we are not likely to have a lot of PTL changes then maybe it doesn't matter that it is early?15:58
evrardjpwe need to do it before voting for the next terms though15:59
evrardjpbut that's another convo15:59
evrardjphere we are just voting about the dates15:59
gmannevrardjp: ah for previous elected one. right.15:59
evrardjpproposition 3 is still over in March15:59
diablo_rojojungleboyj, I dont think thats a correct statement? I think there could still be turnover (there usually is and not always with polling), but that doing it too early makes it hard for people to commit.16:00
evrardjpand it's the simplest for the election team16:00
diablo_rojojungleboyj, if that makes sense :)16:00
evrardjpand it's indeed a problem for charter, but that sounds like a reasonable problem.16:00
fungiyeah, per my suggestion on the ml, i think the tc could amend its charter to declare seats filled for something like "14 months or until the second election from when they were elected" but that would only be for terms starting after the charter was amended16:00
diablo_rojoThe turnover and the polling are not related.16:00
* jroll has to go but trusts the decision will be emailed16:00
evrardjpfungi: yes we agree for that, let's just focus on the dates right now :)16:00
jungleboyjdiablo_rojo: Gotcha.16:01
diablo_rojofungi, +2 for that change for hopefully avoiding future complications16:01
fungievrardjp: yep, i was clarifying why it's not relevant to the scheduling discussion16:01
zanebthe previous year's election concluded on 30 April 2018, so last year's was fully 2 months early. that's how we got into this predicament16:01
evrardjpoh ok16:01
diablo_rojojungleboyj, cool, I'm glad that makes sense. Its early and I didn't sleep much lol.16:01
evrardjpI think it's fine if we run with a small tc for a month16:02
evrardjpone time, and we won't have the problem later16:02
diablo_rojozaneb, yeah that coupled with how we calculate when to do tc elections, the event not being till june, etc etc.16:02
evrardjp(well I guess technically two times)16:02
*** jeremy__bouncer has quit IRC16:02
fungiso to restate my original question, does the tc stick to an election precisely 12 months from when those seats were previously elected this time, or run an election later and consider itself at half-capacity for a few weeks after those terms expired, or just pretend it's "close enough"?16:03
* jungleboyj doesn't have a strong opinion.16:03
fungimakes sense to at least separate that question from when to schedule ptl elections16:04
evrardjpI don't think people will have a strong opinion for a shorter tc during 2 to 4 weeks16:04
zanebthe half-capacity thing seems ok16:04
* diablo_rojo puts tc hat on over the top of election official hat16:04
evrardjpit sems okay for me16:04
jungleboyj:-)16:04
diablo_rojoI like the close enough option, but I am biased lol16:04
jungleboyjdiablo_rojo:  I am kind of there too but don't want to look like I am just ignoring rules.16:04
evrardjpso basically we are heading to 3rd option, and half a tc for a series of weeks16:05
gmannone question on half-capacity- does that effect the TC changes voting system? like 2/3 vote required mean 2/3 of current TC not the total supposed TC16:05
zanebevrardjp: for formal purposes, anyway16:05
fungiyeah, i'm not a lawyer and so not really sure if the tc can declare it close enough to "12 months" to continue operating normally. governance/law isn't quite so stringent as programming specifications16:05
evrardjphalf a tc because we expect ppl won't be signing off to PTL because the end goal might be too far.... yeah that sounds fine for me. We want to empower people being ptls :)16:06
diablo_rojogmann, I am guessing it would16:06
evrardjpWe don't need to be too formal16:06
diablo_rojoevrardjp, +2 for empowering people to be PTLs16:06
jungleboyjevrardjp: ++16:06
evrardjpWe do need to be formal16:06
jungleboyjThat is the more important.16:06
evrardjpok16:07
evrardjpso we have the results!16:07
evrardjpthanks everyone16:07
diablo_rojoUhh so which option are we going with?16:07
jungleboyjHe he.16:07
diablo_rojo3?16:07
jungleboyjYes?16:07
diablo_rojo+ charter change?16:07
evrardjpyes16:08
evrardjp+ half tc16:08
diablo_rojo(also we will likely need to push the extra atc deadline)16:08
diablo_rojoLord, this got complicate.d16:08
evrardjpisn't that what you wanted?16:08
gmannhalf-tc need changes but it depends on how we read that - https://governance.openstack.org/tc/reference/charter.html#motions16:08
jungleboyjdiablo_rojo:  See what happens when people read your e-mails?16:08
*** jeremy__bouncer has joined #openstack-tc16:08
evrardjpjungleboyj: hahaha16:08
gmannany motion need 'a minimum of positive votes of at least one third of the total number of TC'16:08
gmanntotal number we will consider as half-tc for those week? or what16:09
* diablo_rojo offers jungleboyj an election official hat16:09
evrardjpgmann: correct16:09
fungigmann: my reading of the charter is yes16:09
* jungleboyj tries it on and is not sure about the fit16:09
evrardjpbut the chair can decide to not merge it temporarily16:09
* diablo_rojo hands jungleboyj a different election official hat16:09
evrardjpto wait for a larger tc16:09
fungibasically 7 seats expire at the start of march, leaving 6 tc members active at that time16:09
fungiso calculations about majority are based on a tc of 6 members16:10
evrardjpbecause it's holding off for about 2 to 4 weeks16:10
asettleShitttt sorry I'm here16:10
asettleo/16:10
diablo_rojoasettle, lol16:10
evrardjpthe meeting was 2 hours ago16:10
evrardjphaha16:10
diablo_rojoyou missed so many fun conversations16:10
fungibecause the charter says if people leave the tc within 4 weeks of a scheduled election then those seats will remain vacant and get filled at the next election16:10
diablo_rojoand have A LOT of scrollback to catch up on16:10
asettleevrardjp, I know how the hell did I miss that16:10
gmannevrardjp: fungi but it does not say active TC it say total TC. or its me over reading it. I am ok with active TC but we should agree on that so that no issue on merging the patches during those weeks16:11
fungithat's an excellent point16:11
fungiit could be interpreted as the tc no longer has quorum at that point (or maybe it still does because it's calculated against a smaller total number of seats with the recent change which merged)16:12
openstackgerritZane Bitter proposed openstack/governance master: Link to Charter Amendment section from House Rules  https://review.opendev.org/69751116:12
evrardjpmy point is that we are discussing for two to 4 weeks16:12
jungleboyjSeems it would need to be against a smaller total number.16:12
gmannasettle: not just you, i joined late too in impression of 9 AM for me(i still cannot used to daylight saving things )16:12
evrardjpUTC doesn't have daylight saving :)16:13
evrardjplet's use UTC everywhere! :)16:13
zanebfungi: it says 'members' not 'seats'. not sure what we can read into that16:13
gmannyeah that is what i need to do, UTC16:13
fungiyeah, if you're calculating it against a tc of 11 seats and have only 6 members, then you could get by for a few weeks requiring unanimity to pass formal resolutions and lacking quorum for any changes to the charter16:13
asettleI'm glad gmann :D16:13
zanebfungi: and honestly that wouldn't be a bad thing16:14
gmannzaneb: but later it will be same situation like on TC seat patch. i see only 3 vote positive and it was merged and do body knews TC were half that time16:14
fungiif you're calculating it against the number of tc members on the other hand, then yeah you'd need 3 (4?) for formal votes and 4 (5?) for charter changes16:14
gmannyeah16:15
evrardjpfungi: which sounds far -- no change to the charter should be done during that time16:17
fungiyep, i think it's reasonable16:17
fungithough i'm not on the tc, so want to be sure the tc thinks it's reasonable16:18
evrardjpI am not the only voice of the tc, but I personally think it's fine16:18
evrardjps/but/16:18
evrardjps/but// *16:18
jungleboyjevrardjp: ++16:18
gmannfair enough and TC chair can make sure that. I think this is way to proceed further.16:19
fungiright, hashing some of this out in office hour was mostly intended to help speed up the ml discussion we need to have about it16:19
evrardjpyes indeed16:19
gmann+116:19
fungithat and the resulting change in gerrit to set the election schedule are where the real discussion should take place anyway16:20
evrardjpif truly necessary we can rediscuss this in the next week's office hours, or bring ppl to vote on reviews.16:20
fungiand gerrit gives us a means of getting a more official blessing from the tc members16:20
jungleboyjfungi: ++16:21
jungleboyjAre we getting diablo_rojo the answer she needs though?16:21
fungihopefully one or more tc members will reply to the ml thread with the answer as to what ought to get formally proposed in gerrit, and then we can collect some tc member votes there16:22
diablo_rojojungleboyj, lol I don't think so16:22
jungleboyjdiablo_rojo:  That was what I feared.16:22
diablo_rojojungleboyj, its alright, I can wait for answers on the thread...assumping people share opinions there16:23
jungleboyjOk.  Sounds like that is the best way to go forward then.16:23
jungleboyjAnd now the TC is aware of the issue and where to work it.  :-)16:24
diablo_rojoInded.16:25
diablo_rojo*Indeed16:25
fungithanks!16:26
jungleboyjSo we are settled on working this through the Mailing List?16:27
jungleboyjSeems like everyone has burned out.16:28
fungii take full responsibility for burning people out ;)16:28
fungiit's a skill16:28
jungleboyjfungi:  As you should with your rules and understanding details.16:28
fungii'm occasionally tempted to enroll in night classes for a law degree, and then i suddenly feel an overwhelming desire for a shower16:29
* jungleboyj laughs16:29
evrardjpI thought this was clear16:30
gmannfungi: diablo_rojo thanks again for continuing great job on election.16:30
evrardjpyes indeed!16:30
jungleboyjNo thank you.  No law degree for me.16:30
jungleboyj++16:30
gmannyeah, may we can summarize the discussions here then other TC can reply16:30
diablo_rojogmann, thanks16:30
jungleboyjOk.  Sounds good.16:31
jungleboyjSorry, I got pulled into a call so I missed the finality of that decision.  :-)16:31
diablo_rojoSo.. I think we are in favor of the charter change that will make terms 14 months or until two elections after being elected16:31
diablo_rojo?16:31
diablo_rojoAnd the combined election at its current suggested dates16:31
diablo_rojowhich leaves us with 6 tc members for a few weeks16:32
diablo_rojo?16:32
gmannI think yes.  + TC will get/notify all TC member about no charter change during that half-tc week.16:33
jungleboyjdiablo_rojo:  That was the summary that I was expecting.  Then we went down the legal rabbit hole.16:33
jungleboyjgmann: ++16:33
diablo_rojoOkay. I will try to capture all that on the thread.16:34
gmannthanks diablo_rojo .16:35
jungleboyjdiablo_rojo: Thanks for your work on that.16:35
evrardjpI will summarize16:36
evrardjpoh ok you summarize16:36
evrardjpperfect16:36
fungiand also, from the other subthread, the fact that the tc has already merged a change to shrink its size, so we'll be electing 5 seats rather than 7 this time around16:36
gmanncorrect.16:37
jungleboyjfungi: ++16:37
*** jamesmcarthur has joined #openstack-tc16:38
diablo_rojoLOL16:38
diablo_rojoevrardjp, if you want to do it.. I will totally let you :)16:38
evrardjpgo ahead16:39
evrardjpI will confirm :p16:39
*** slaweq_ has joined #openstack-tc16:41
diablo_rojoevrardjp, kk16:41
*** e0ne has quit IRC16:42
*** jamesmcarthur has quit IRC16:42
*** openstackgerrit has quit IRC16:42
*** ricolin has quit IRC16:54
*** jamesmcarthur has joined #openstack-tc17:00
*** slaweq_ has quit IRC17:02
*** jamesmcarthur has quit IRC17:36
*** lpetrut has quit IRC17:40
*** jamesmcarthur has joined #openstack-tc17:46
*** jcapitao has quit IRC17:46
*** jamesmcarthur has quit IRC17:50
*** jamesmcarthur has joined #openstack-tc17:58
*** jamesmcarthur has quit IRC17:59
*** lpetrut has joined #openstack-tc18:07
*** jamesmcarthur has joined #openstack-tc18:10
*** jamesmcarthur has quit IRC18:11
*** jamesmcarthur has joined #openstack-tc18:26
*** jamesmcarthur has quit IRC18:32
*** nicolasbock1 has joined #openstack-tc18:59
*** nicolasbock1 has quit IRC19:18
*** jaosorior has joined #openstack-tc21:22
*** e0ne has joined #openstack-tc21:32
*** persia has quit IRC21:43
*** persia has joined #openstack-tc21:45
*** stephenfin has quit IRC21:50
*** e0ne has quit IRC21:52
*** jaosorior has quit IRC21:53
*** stephenfin has joined #openstack-tc21:57
*** jamesmcarthur has joined #openstack-tc22:31
*** jamesmcarthur has quit IRC22:45
*** jamesmcarthur has joined #openstack-tc22:45
*** jamesmcarthur has quit IRC23:28
*** tosky has quit IRC23:38
*** jamesmcarthur has joined #openstack-tc23:38
*** jamesmcarthur has quit IRC23:52

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