Thursday, 2019-01-31

*** cdent_ has joined #openstack-tc00:27
*** cdent has quit IRC00:30
*** cdent_ is now known as cdent00:30
*** tosky has quit IRC00:46
*** jamesmcarthur has quit IRC01:21
*** jamesmcarthur has joined #openstack-tc01:23
*** jamesmcarthur has quit IRC01:27
*** jamesmcarthur has joined #openstack-tc01:58
*** mriedem has quit IRC02:04
*** whoami-rajat has joined #openstack-tc02:11
*** jamesmcarthur has joined #openstack-tc02:22
*** dims has quit IRC02:38
*** jamesmcarthur has quit IRC02:47
*** dims has joined #openstack-tc02:55
*** ricolin has joined #openstack-tc03:18
*** jamesmcarthur has joined #openstack-tc04:48
*** jamesmcarthur has quit IRC04:54
*** lbragstad has quit IRC05:16
*** e0ne has joined #openstack-tc06:12
*** jamesmcarthur has joined #openstack-tc06:50
*** jamesmcarthur has quit IRC06:54
*** e0ne has quit IRC07:05
*** Luzi has joined #openstack-tc07:06
*** ricolin has quit IRC08:25
*** ricolin has joined #openstack-tc08:25
*** tosky has joined #openstack-tc08:34
*** jpich has joined #openstack-tc08:39
*** ricolin has quit IRC08:44
*** ricolin has joined #openstack-tc08:44
*** jamesmcarthur has joined #openstack-tc08:51
*** jamesmcarthur has quit IRC08:55
*** e0ne has joined #openstack-tc09:15
*** dtantsur|afk is now known as dtantsur09:21
ttxThreads dropped10:45
*** e0ne has quit IRC10:46
*** jamesmcarthur has joined #openstack-tc10:52
*** e0ne has joined #openstack-tc10:52
*** jamesmcarthur has quit IRC10:56
*** purplerbot has quit IRC10:57
*** purplerbot has joined #openstack-tc10:57
cdentttx?10:58
* cdent figures it out11:03
*** e0ne has quit IRC11:24
*** e0ne has joined #openstack-tc11:34
*** jamesmcarthur has joined #openstack-tc12:52
*** jamesmcarthur has quit IRC12:57
*** e0ne has quit IRC13:01
*** e0ne has joined #openstack-tc13:04
*** jamesmcarthur has joined #openstack-tc13:15
*** ssbarnea has quit IRC13:17
*** zbr has joined #openstack-tc13:17
*** zbr is now known as zbr|ssbarnea13:18
*** zbr|ssbarnea has quit IRC13:19
*** zbr|ssbarnea has joined #openstack-tc13:20
*** jamesmcarthur has quit IRC13:20
*** zbr|ssbarnea has quit IRC13:21
*** e0ne has quit IRC13:25
*** zbr|ssbarnea has joined #openstack-tc13:26
*** e0ne has joined #openstack-tc13:29
*** e0ne has quit IRC13:30
*** e0ne has joined #openstack-tc13:32
*** e0ne has quit IRC13:34
*** e0ne has joined #openstack-tc13:35
*** mriedem has joined #openstack-tc13:37
*** jamesmcarthur has joined #openstack-tc13:46
*** jamesmcarthur has quit IRC13:51
*** lbragstad has joined #openstack-tc13:57
*** e0ne has quit IRC14:13
*** e0ne has joined #openstack-tc14:45
*** cdent has quit IRC14:57
mnaserit's a keyword15:00
mnaseranyways, hi all.15:00
ttxhi!15:01
mnaserso i hate to drag this conversation into this, but we know the summit is planned for shanghai (yay, excited)15:02
mnaserbut i guess so will the ptg.. or not confirmed yet?15:02
ttxNot confirmed yet. we want to do some analysis first to see ho many days we'd need there15:03
ttxWe need that first before announcing specific days :)15:04
smcginnistc-members office hours ping15:05
dhellmanno/15:05
evrardjpforgot to say hi but I am here :)15:05
* lbragstad is multi-tasking currently15:05
mnaserttx: cool, that's pretty exciting15:05
ttxdhellmann: aren't you in PTO?15:05
dhellmannttx: cancelled due to illness15:05
dhellmannor rescheduled, rather15:05
dimso/15:06
ttxah, sorry to hear that15:06
dhellmannthis year's flu is *harsh*15:06
dhellmanndid anyone have questions about the agenda items for the meeting next week? I realize that the email was a bit sparse15:06
smcginnisGiven the current political climate, I am a little concerned how many contributors would be able to make it to a PTG in Shanghai.15:07
*** Luzi has quit IRC15:07
smcginnisdhellmann: Nothing stood out to me as missing or our of place.15:07
dhellmannsmcginnis: I share that concern :-/15:07
ttxsmcginnis: it's difficult to predict what the situation willbe like in November, but I understand15:07
smcginnisYes, true.15:08
ttxlike if you had told me we would be where we are 10 months ago...15:08
mnaserin a really odd and weird way, i think this might be a good exercise to know how some of our zte contributors might have felt not long ago, i guess.15:08
mnaseri don't think it'll be too problematic (coming from a canadian, hah)15:09
smcginnishah15:09
mnaserbtw, this is a cool article i'd love to share when we get closer to the summit15:10
mnaserhttps://paranoidbeavers.ca/travel-laptop-setup.html15:10
mnaserkonstantin (mricon) does a lot of security stuff for the LF and it's a pretty awesome guide15:10
dhellmannwe didn't go to quite those lengths, but did take separate laptops when we went to hong kong15:12
ttxWould love feedback on the two threads I started on the ML15:12
ttxalthough ideally you would post any lengthy answer on the thread :)15:12
dhellmannI like the idea of having formal short-term teams, although I wonder if we couldn't just use the SIG mechanism for them instead of creating a separate thing.15:13
ttxdhellmann: I really like the idea of documenting scope and disband criteria15:14
ttxso the documentation required for a $thing is different than from a SIG15:14
ttxBut we could call them short-term SIG or whatever15:14
dhellmannwhat sort of criteria do you see for disbanding? isn't that just "we're done with the work we set out to do?"15:15
ttxdhellmann: example at https://github.com/kubernetes/community/tree/master/wg-k8s-infra15:16
ttxerr15:16
ttxhttps://github.com/kubernetes/community/blob/master/wg-k8s-infra/charter.md15:16
ttxI suspect dims can talk more about the benefits of setting those up separately15:17
lbragstadmnaser nice post - thanks!15:17
cmurphycriteria would be things like "support needed for image encryption is present in X, Y, Z projects"15:18
ttxanother thing that is relatively different in $thing compared to SIG is the need for buy-in from affected teams15:18
dhellmanncmurphy : your point on the thread about buy-in from the project teams is also important; thanks for raising that15:19
ttxso there is a clear list of them15:19
ttxSIGs are a bit more blurry in that respect15:19
dhellmannthat seems to be a big reason SIGs have had trouble gaining traction15:20
dhellmannat least some of them15:20
ttxIt's difficult to come up with a definitive list of affected teams for SIGs as they are first to  discuss what to do15:20
dimsdhellmann : when the discussion is kinda finalized and turned into specifications, the wg can get disbanded as the sigs are going to use that input and turn it into actual $things15:20
ttxBut SIGs could definitely spawn $things15:20
dimsright15:21
mnaseri like that15:21
dhellmannso our SIGs might spawn pop-up teams to plan specific work which is then done by project teams?15:21
dimsanother example is wg-lts being formed right now.15:21
ttxhmm... we may have different meanings for $things :/15:22
ttxI see SIGs as one of the way to discuss a need for a pop-up team. Pop-up teams coordinate work on a specific objective across multiple project teams.15:23
dimsin k8s world, when KEPs are filed, then the SIGs take over and wg (that work across SIGs) are not needed any more15:23
ttxPop-up teams need buy-in from affected teams15:23
dimsright15:23
ttxdims: ah, interesting. Maybe due to there being a difference between SIGs and code owners already ?15:24
dimsin k8s WGs there is no expectation that SIG will do what was decided/discussed there. that debate will be in KEPs15:24
dimsttx y that's another check/balance15:24
dimshere i guess we want cross cutting teams with a specific mandate and authorization from projects to do the work agreed upon?15:26
dhellmannit seems like a key aspect is to have the work team be discoverable, scoped, and to have some sort of process for getting "approval" from the project teams involved15:28
dhellmannI guess that's 3 key aspects :-)15:29
dimsagree dhellmann15:29
dims:)15:29
dhellmannI'm not sure if "mandate" is quite right, but something like that15:29
dimsdhellmann : also helps folks to talk to their employer to get time to do stuff i think15:30
dhellmannperhaps15:30
ttxThe goal is not to add layers of bureaucracy, it's really to help cross-project work driven by people who lack name recognition to engage directly and jJFDI15:30
dhellmanndo we have some examples of things we think might be "done" through popup teams?15:30
ttxso a bit of process structure might (might) help them15:30
dhellmannI could see goals being managed by these teams15:31
ttxgoals could be a particular form of pop up team -- tied to a cycle AND affecting most project teams15:32
dhellmannas well as "smaller" cross project work. I guess the think we keep pointing to is cinder multi-attach15:32
dimsthinking back ... the python3 effort was a pop-up team15:32
dhellmanns/think/thing15:32
ttxdims: yes15:32
dimswith the wiki tying all the folks and work together ...15:32
ttxtehre was one recently where someone asked us for advice on "steps" to follow to drive some cross-project objective15:33
ttxbut that was ages ago, like last month or something15:33
smcginnisSigned glance images or something like that.15:33
dhellmannsmcginnis : yeah, that was it15:33
ttxsmcginnis: wow your neurons are still working15:33
dimsunaffected by the polar vortex thingy!15:34
* ttx is impressed15:34
ttxanyway, that's great feedback, don't hesitate to contribute it to the thread15:34
dhellmannhow about the "help most needed" list? what do we see happening there?15:35
dhellmannttx: do you want to add something to our tracking wiki page to keep up with the popup team process work?15:35
* lbragstad still needs to parse that thread - but thanks for starting it ttx 15:38
evrardjpttx: about the help most needed removal, what message will it be sending to remove that? It could as well be interpreted as "We don't need help" or as "All the projects need help". And I guess that's not the initial intent, right?15:41
evrardjp(Just thinking about how to ship that message)15:41
ttxdhellmann: wanted to gut-check it before making it an effort we collectively track15:42
ttxso maybe next week after the thread discussion?15:42
dhellmannttx: sounds good15:43
dhellmannevrardjp : I think the point is to move the list and reform it, rather than eliminate it completely15:44
dhellmannthe list as it stands now hasn't helped us, so we should try something else15:44
evrardjpyeah I got that, I am just concerned of the miscommunication that can go with it. I guess we just need to be careful15:44
*** jamesmcarthur has joined #openstack-tc16:00
*** cdent has joined #openstack-tc16:15
*** jamesmcarthur has quit IRC16:16
*** jamesmcarthur_ has joined #openstack-tc16:16
*** jamesmcarthur has joined #openstack-tc16:17
*** jamesmcarthur_ has quit IRC16:20
*** e0ne has quit IRC16:46
*** spsurya has quit IRC16:54
lbragstadfungi per your note here http://lists.openstack.org/pipermail/openstack-discuss/2018-November/000080.html do you happen to know if there is a link to the archive handy?17:05
lbragstadI can't seem to find/discover it17:05
lbragstadfungi nevermind - i was able to dig one up17:08
*** cdent has quit IRC17:26
smcginnisHuh, I had assumed we would still be able to browse the archives on lists.o.o.17:29
lbragstadyeah - that's where i tripped17:35
*** jpich has quit IRC17:38
clarkbthe archives arestill there18:12
clarkbjust not listed on the master list of lists18:12
*** dtantsur is now known as dtantsur|afk18:39
*** e0ne has joined #openstack-tc18:39
*** jamesmcarthur has quit IRC18:46
*** e0ne has quit IRC18:48
*** ricolin has quit IRC18:52
lbragstadclarkb ack - thanks19:09
*** jamesmcarthur has joined #openstack-tc19:14
dhellmannyeah, the archives are at http://lists.openstack.org/pipermail/openstack-tc/19:31
*** jamesmcarthur has quit IRC19:36
*** jamesmcarthur has joined #openstack-tc19:47
*** jamesmcarthur has quit IRC20:42
*** jamesmcarthur has joined #openstack-tc20:44
*** jamesmcarthur has quit IRC20:49
*** zaneb has quit IRC20:50
*** jamesmcarthur has joined #openstack-tc20:51
*** jamesmcarthur has quit IRC21:04
*** bodgix_ has joined #openstack-tc21:26
*** bodgix has quit IRC21:26
*** bodgix_ has quit IRC21:27
*** bodgix has joined #openstack-tc21:27
*** bodgix has quit IRC21:39
*** bodgix has joined #openstack-tc21:40
*** jamesmcarthur has joined #openstack-tc21:51
*** jamesmcarthur has quit IRC22:08
*** jamesmcarthur has joined #openstack-tc22:26
*** jamesmcarthur has quit IRC22:41
*** mriedem has quit IRC23:00
*** whoami-rajat has quit IRC23:00
*** jamesmcarthur has joined #openstack-tc23:22
*** jamesmcarthur has quit IRC23:26

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