Thursday, 2019-01-17

*** tosky has quit IRC00:29
*** jamesmcarthur has joined #openstack-tc01:24
*** jamesmcarthur has quit IRC01:28
*** whoami-rajat has joined #openstack-tc01:32
*** mriedem has quit IRC01:39
zanebdiablo_rojo, ildikov: question for y'all re Upstream Institute syllabus http://lists.openstack.org/pipermail/openstack-discuss/2019-January/001793.html01:42
ildikovzaneb: hi01:45
ildikovzaneb: just glanced through that mail01:45
ildikovzaneb: I think we can think of the common chapters of the Contributor Guide to link to the vision document01:46
ildikovzaneb: as far as the training is concerned I would probably start with making people aware that the vision document exists01:47
zanebildikov: totally agree, even just doing that would be of huge benefit imho01:48
ildikovzaneb: and we can iterate on how much time we spend on the topic with the aim of trying not to overwhelm people too much01:48
zaneb+101:48
ildikovAs one challenge with the training is that it's easy to overload people's brains01:49
ildikovSo making sure we raise awareness is the key here to start with01:49
* diablo_rojo catches up01:49
ildikovAnd I agree that's a good info for new contributors to know about01:50
ildikovGood if it's part of the culture01:50
ildikovzaneb: are you looking for guidance on where to link to it from in the Contributor Guide?01:51
diablo_rojoIt should be relatively easy to add mention of the vision document to the governance section of the contributor guide01:51
diablo_rojoSimilar to how we did with the reviewing the openstack way01:52
ildikovEither there or the intro section01:52
zanebildikov: I submitted a patch already for that https://review.openstack.org/#/c/631366/ (happy to get feedback on the review obviously), but the main thing I'm looking for guidance on is how to move from having a link in the guide to getting it incorporated in the training01:52
diablo_rojoI think Governance would be a better fit? But thats just me.01:53
diablo_rojoWe usally go through the into pretty quickly01:53
ildikovzaneb: ah sorry, on my phone so didn't open the review yet01:54
diablo_rojoSo if we want it to get more attention, it should live in governance01:54
* zaneb looks at the governance section01:54
ildikovzaneb: I think we can make it part of an existing module by adding an exercise to it01:54
ildikovAs the training is heavily using the guide as you pointed it out01:54
diablo_rojozaneb, the way the training works is that we have people read through the guide and anything linked to from the relevant section of the guide and then have the students do exercises01:55
ildikovI would still keep it lightweight and let students ask questions, etc01:55
diablo_rojoSo like ildikov said, an exercise is the best way to make sure people are actually paying attention to it.01:55
diablo_rojo+201:57
ildikovAs deep diving into a vision document can go heavy weight easily :)01:57
diablo_rojoIts something we can mention and have people ask questions about during breaks too01:57
ildikovWe could start the governance section exercise with this01:57
ildikovOr finish the OpenStack intro block with it01:58
diablo_rojoI vote the first option- starting the governance section with it01:59
ildikov+1 to encourage people to ask questions during the break if they're interested in the details01:59
ildikovCool, let's do that then01:59
zanebdiablo_rojo: I think it would certainly be relevant in the governance section for anybody looking to start a new project...01:59
ildikovzaneb: +102:00
zanebbut for contributors to existing projects, it feels more like an intro thing? like, I know it seems like chaos but we are all actually working towards the same thing and here's where you can read about it02:00
ildikovIf we start the governance section exercises with that it's still right after the intro and sending that message02:01
diablo_rojoI think that is two different audiences02:01
* zaneb hasn't actually been to one of the trainings so I'll defer to the experts02:01
diablo_rojozaneb, you should come to the one in Denver :)02:02
ildikovAnd then we can point out how we try to make sense of the chaos02:02
zanebdiablo_rojo: I should, but I'm sure it'll conflict with something I'm obliged to be at :/02:02
diablo_rojoIf it doesn't feel right in the governance section after Denver we can change it02:02
ildikovAnd yeah, people already contributing is a different story02:03
diablo_rojoWell if you can come Saturday at least that would be cool.02:03
diablo_rojoI know Sunday is normally a crapshoot for TC members cause thats when the board stuff is.02:03
zanebyeah. will keep Sat in mind when I book flights though, thanks02:03
ildikovI think it's worthwhile to come and check it out even if it's for a few hours only and the whole thing02:04
ildikovzaneb: +102:04
diablo_rojoI agree with ildikov :)02:04
diablo_rojoWe'd love to see you there even if its just for a little while zaneb02:05
ildikov+2 :)02:05
*** jaosorior has joined #openstack-tc05:15
*** Bhujay has joined #openstack-tc05:20
*** Bhujay has quit IRC05:21
*** Bhujay has joined #openstack-tc05:21
*** diablo_rojo has quit IRC06:04
*** Bhujay has quit IRC06:07
*** Bhujay has joined #openstack-tc06:07
*** Bhujay has quit IRC06:08
*** Bhujay has joined #openstack-tc06:08
*** Bhujay has quit IRC06:10
*** Bhujay has joined #openstack-tc06:10
*** Bhujay has quit IRC06:11
*** Bhujay has joined #openstack-tc06:11
*** Bhujay has quit IRC06:13
*** Bhujay has joined #openstack-tc06:13
*** Bhujay has quit IRC06:14
*** Bhujay has joined #openstack-tc06:14
*** Bhujay has quit IRC06:16
*** Bhujay has joined #openstack-tc06:16
*** Bhujay has quit IRC06:17
*** Bhujay has joined #openstack-tc06:17
*** Bhujay has quit IRC06:19
*** Bhujay has joined #openstack-tc06:19
*** Bhujay has quit IRC06:20
*** Bhujay has joined #openstack-tc06:20
*** Bhujay has quit IRC06:22
*** Bhujay has joined #openstack-tc06:22
*** Bhujay has quit IRC06:23
*** Bhujay has joined #openstack-tc06:23
*** Luzi has joined #openstack-tc06:43
openstackgerritZane Bitter proposed openstack/governance master: Cloud Vision: clarify meaning of design goals  https://review.openstack.org/63143507:08
*** e0ne has joined #openstack-tc07:52
*** Bhujay has quit IRC08:13
*** jpich has joined #openstack-tc08:38
*** tosky has joined #openstack-tc08:40
*** Bhujay has joined #openstack-tc08:56
*** david-lyle has joined #openstack-tc09:16
*** dklyle has quit IRC09:19
*** dtantsur|afk is now known as dtantsur09:25
*** david-lyle has quit IRC09:29
*** dklyle has joined #openstack-tc09:32
*** david-lyle has joined #openstack-tc09:49
*** dklyle has quit IRC09:51
*** david-lyle has quit IRC09:56
*** dklyle has joined #openstack-tc10:00
*** Bhujay has quit IRC10:37
*** Bhujay has joined #openstack-tc10:53
*** cdent has joined #openstack-tc10:54
*** e0ne has quit IRC11:44
*** e0ne has joined #openstack-tc11:52
*** Bhujay has quit IRC12:34
*** Bhujay has joined #openstack-tc12:35
*** Bhujay has quit IRC12:36
*** Bhujay has joined #openstack-tc12:36
*** Bhujay has quit IRC12:37
*** Bhujay has joined #openstack-tc12:40
*** Bhujay has quit IRC12:42
*** irclogbot_3 has quit IRC12:47
*** irclogbot_3 has joined #openstack-tc12:56
openstackgerritGhanshyam Mann proposed openstack/governance master: Add Version Based Feature Discovery in Technical Vision  https://review.openstack.org/62151612:56
*** logan- has joined #openstack-tc13:09
*** eumel8 has joined #openstack-tc13:11
*** edmondsw_ has joined #openstack-tc13:27
*** edmondsw has quit IRC13:29
*** edmondsw_ is now known as edmondsw13:29
*** irclogbot_3 has quit IRC13:35
*** irclogbot_3 has joined #openstack-tc13:46
*** e0ne has quit IRC13:53
*** e0ne has joined #openstack-tc13:59
*** mriedem has joined #openstack-tc14:58
ttxoffice hour time again15:01
smcginniso/15:01
fungiindeed!15:02
mugsieo/15:02
fungitonyb went ahead and approved the tc election schedule15:04
openstackgerritThierry Carrez proposed openstack/governance master: Do not expect releases of heat-cfnclient  https://review.openstack.org/63152815:04
fungiplanning to send an announcement to the openstack-discuss ml todayish15:05
smcginnisAwesome15:05
lbragstado/15:06
cdenthola15:07
* cdent raises the flag higher15:08
cdenttc-members, it's office hours15:08
smcginnisI think we swapped times with the Wednesday office hours on activity this week.15:15
lbragstadyup15:16
* cdent looks at the logs15:19
cdentinteresting, so between now and then we already decided to change when the elections happen without checking with the electorate?15:20
smcginnisIs that something that needs that broad of buy-in?15:20
cdenti meant the ordering of when ptl when tc15:21
cdentI don't know if it does or not15:21
mugsiedid that pass?15:21
ttxyeah, that was quick15:21
smcginnisI guess I'm pretty ambivalent towards the timing of that, just as long as we have enough time for those affected to be able to book travel if they now have a compelling argument to their management to now go when they couldn't before.15:21
smcginnisI'm fine with whatever the election team wants to do.15:22
cdentit's not a big deal to me, it just means some adjustments in my scheming15:23
cdentand if I have schemes in progress, I have to assume others do too15:23
* smcginnis pictures cdent scheming with a maniacal look on his face15:23
cdenthave you seen 2019 yet? that face has been there for a long time15:24
smcginnis:)15:24
* mugsie has been avoiding news in 201915:24
mugsiethe news*15:24
cdentgood choice15:25
cdentI'm currently contemplating my answer to dhellmann's question about what would you prune (besides asking that he prune his quotes)15:26
cdentthe whole thread has been for sake of generating conversation, so I'm not sure if I should go for "here's one extreme" or be more inclusive15:27
smcginnisBeing more extreme could certainly stimulate more conversation. Maybe not some that you really want to have though.15:28
fungisorry, sort og afk in here since i ended up chairing the overlapping security sig meeting today15:29
*** zhipeng has quit IRC15:33
*** Luzi has quit IRC15:33
*** zhipeng has joined #openstack-tc15:40
*** jaosorior has quit IRC15:56
fungiso anyway, catching up on the discussion in here, the timing of tc-then-ptl elections this round was due to 1. not wanting to have ptls elected too far in advance of the start of the next release cycle, 2. needing to have tc elections within the required timeframe per the (current) bylaws, 3. avoiding having tc and ptl elections overlap leading to even worse confusion, and 4 avoiding having either15:59
fungioverlap with the summit/ptg15:59
*** diablo_rojo has joined #openstack-tc16:01
*** jamesmcarthur has joined #openstack-tc16:05
*** e0ne has quit IRC16:25
*** evrardjp has joined #openstack-tc17:02
cdentthanks for joining in on that role thread cmurphy17:10
*** jpich has quit IRC17:19
*** dtantsur is now known as dtantsur|afk17:37
cmurphyyou're welcome cdent18:09
cdentcmurphy: you state one of the several common positions in a very comprehensible way, which is good to have in the mix18:10
cmurphyglad i could well represent that side of things18:12
cmurphyfungi: i'm not saying you do, i'm saying you could ;)18:13
*** e0ne has joined #openstack-tc18:14
*** e0ne has quit IRC18:16
fungi;)18:33
*** e0ne has joined #openstack-tc18:36
*** jamesmcarthur has quit IRC19:33
*** e0ne has quit IRC19:44
*** jamesmcarthur has joined #openstack-tc19:50
*** jamesmcarthur has quit IRC20:06
*** jamesmcarthur has joined #openstack-tc20:08
*** jamesmcarthur has quit IRC20:21
*** jamesmcarthur has joined #openstack-tc20:22
*** irclogbot_3 has quit IRC20:41
*** irclogbot_3 has joined #openstack-tc20:49
*** openstackgerrit has quit IRC20:56
*** cdent has quit IRC21:48
*** mriedem has quit IRC21:49
*** jamesmcarthur has quit IRC21:52
*** jamesmcarthur has joined #openstack-tc21:53
*** mriedem has joined #openstack-tc21:56
*** jamesmcarthur has quit IRC22:03
*** mriedem has quit IRC23:17
*** tosky has quit IRC23:57

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