Tuesday, 2017-06-20

*** openstack has joined #openstack-tc00:17
*** emagana has joined #openstack-tc03:13
*** emagana has quit IRC03:57
*** emagana has joined #openstack-tc04:37
*** emagana has quit IRC04:47
*** emagana has joined #openstack-tc06:59
*** emagana has quit IRC07:04
*** jpich has joined #openstack-tc07:15
*** cmurphy_ is now known as cmurphy07:18
ttxsdague: could you confirm that we require a voting job for assert:supports-upgrade (see https://review.openstack.org/#/c/472547/ )07:50
ttxOffice hour time, I'll be around for the coming hour if you have questions or want to discuss anything09:01
* johnthetubaguy is a touch late, but also around for office hours09:17
ttxHi johnthetubaguy!09:17
ttxHad a question for you regarding SWG09:18
johnthetubaguyah, yes09:18
ttxSince Colette stopped leading it and we dropped the meeting, it's essentially dead09:19
ttxone issue with dropping meeting is that it means you need a driver*09:19
ttxLike what I do for the TC, i.e. updating status and issuing emails every week09:19
johnthetubaguyyes, been thinking along similar lines recently09:19
ttxSo, basically I don't think the meetingless approach can work without someone dedicating a significant amount of time to beating the asynchronous drum09:20
johnthetubaguytotally agreed09:20
ttxFrom the TC experience I would say that it ends up being as much (if not more) time for the leader to drive the group09:20
ttxbut with bonus points in visibility and accessibility09:21
johnthetubaguyI can totally believe its more work09:21
ttxso, overall worth it09:21
ttxbut that means you have to find someone willing to dedicate that sort of time leading the group. So the timing with Colette limiting her involvement was not ideal09:22
ttxI'd say we have two options09:22
ttxWe find someone who followed the training who is willing to spend time driving the group09:22
ttxWe dissolve the SWG into the TC09:23
ttxi.e. take over a number of the things and follow them at TC level09:23
ttxI would prefer the first option, but if the only people driving happen to be TC members, the overhead is costly09:23
johnthetubaguyI was hoping to help drive that, but its taking a long time to get myself a new job actually sorted09:23
ttxSo ideally, we'd find a non-TC member to drive it09:23
ttxjohnthetubaguy: if you still have plans to lead that, maybe we should wait a bit before dumping a "we are dead unless someone steps up" thread09:25
johnthetubaguymore non-elected TC people driving efforts would be great, and this is a good one to consider09:25
ttxjohnthetubaguy: I could see someone else leading it, but probably not from day 009:25
ttxso if you could bootstrap it that would really help09:25
johnthetubaguyeven if I am just helping hand things over to someone else we find could work09:25
johnthetubaguyyeah, happy to help bootstrap, etc09:26
ttxThe way i do it for the TC is to go through the open initiatives twice per week and update the status on the wiki page. Once per week I use that to see a status update email09:26
ttxto send*09:26
johnthetubaguywhat if we try the SWG as having a roll-up into your wiki page, for visibility?09:26
ttxjohnthetubaguy: the way I see it, some initiatives are shared (and would appear) and some aren't (and should live in their own place)09:27
johnthetubaguymore like a sub group I guess I mean09:27
johnthetubaguyyeah, true09:27
ttxI don't really want to make it appear as a TC subgroup though. Would really want non-technical people to get involved09:27
ttxquite a few of the marketing team at the Foundation attended the training last time09:28
ttxThe first group was pretty technical so that triggered a lot of TC-driven actions09:28
johnthetubaguyI see what you mean about the implication there, don't want to put people off participating09:28
ttxBut imho stewardship should go beyond us09:28
ttxand making it appear as a TC-driven or TC-subgroup thing would likely discourage bringing stewardship initiatives to other groups09:29
johnthetubaguyyeah, that's probably true09:29
johnthetubaguythe "i'm not technical so that can't be for me" problem09:30
ttxjohnthetubaguy: ok, then I propose we wait a bit until you get your situation sorted out, you resurrect the team and set up regular reporting, then look around and find someone for succession planning09:30
ttx(or continue doing it if you prefer :)09:30
johnthetubaguyyeah, that can be a TC TODO task to make sure I don't drop it09:31
johnthetubaguyheh, I think resurrect is probably more accurate09:31
ttxack, will add a note to the CT status page so that we don't drop it09:32
johnthetubaguysweet, thanks09:32
ttxjohnthetubaguy: in the mean time, should I clear the meeting slot we currently have on calendar ?09:35
ttxprobably should09:35
johnthetubaguyttx: looking through cdent's latest vision doc, one of the heading is "Including a Wider Community", not sure that covers it, but struggling to think of an alternative09:35
johnthetubaguyttx: yeah, good point, we should do that09:35
ttxI'm on it09:35
*** dims has quit IRC10:16
*** dims has joined #openstack-tc10:21
*** emagana has joined #openstack-tc11:23
*** emagana has quit IRC11:27
ttxflaper87: well said on that thread! Icecream must be the worse analogy ever (given the amount of vetting food gets before it can be sold on the street)12:19
*** lbragstad_ has quit IRC12:49
*** mugsie_ is now known as mugsie12:52
*** mugsie has quit IRC12:53
*** mugsie has joined #openstack-tc12:53
*** emagana has joined #openstack-tc13:35
*** emagana has quit IRC13:39
*** emagana has joined #openstack-tc14:08
*** lbragstad_ has joined #openstack-tc14:38
*** lbragstad_ is now known as lbragstad14:42
*** hongbin has joined #openstack-tc14:46
* dtroyer peeks in14:52
*** jpich has quit IRC15:47
*** rockyg has joined #openstack-tc19:02
*** rockyg has quit IRC21:57
*** openstack has joined #openstack-tc22:16
*** dhellmann has quit IRC22:18
*** dhellmann has joined #openstack-tc22:19
*** dhellmann has quit IRC22:20
*** dhellmann has joined #openstack-tc22:20
*** emagana has quit IRC23:17
*** emagana has joined #openstack-tc23:17
*** emagana_ has joined #openstack-tc23:20
*** emagana has quit IRC23:21
*** emagana_ has quit IRC23:25
*** emagana has joined #openstack-tc23:27
*** emagana has quit IRC23:31

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