| *** openstack has joined #openstack-tc | 00:17 | |
| *** emagana has joined #openstack-tc | 03:13 | |
| *** emagana has quit IRC | 03:57 | |
| *** emagana has joined #openstack-tc | 04:37 | |
| *** emagana has quit IRC | 04:47 | |
| *** emagana has joined #openstack-tc | 06:59 | |
| *** emagana has quit IRC | 07:04 | |
| *** jpich has joined #openstack-tc | 07:15 | |
| *** cmurphy_ is now known as cmurphy | 07:18 | |
| ttx | sdague: could you confirm that we require a voting job for assert:supports-upgrade (see https://review.openstack.org/#/c/472547/ ) | 07:50 |
|---|---|---|
| ttx | Office hour time, I'll be around for the coming hour if you have questions or want to discuss anything | 09:01 |
| * johnthetubaguy is a touch late, but also around for office hours | 09:17 | |
| ttx | Hi johnthetubaguy! | 09:17 |
| johnthetubaguy | hey | 09:18 |
| ttx | Had a question for you regarding SWG | 09:18 |
| johnthetubaguy | ah, yes | 09:18 |
| ttx | Since Colette stopped leading it and we dropped the meeting, it's essentially dead | 09:19 |
| ttx | one issue with dropping meeting is that it means you need a driver* | 09:19 |
| ttx | Like what I do for the TC, i.e. updating status and issuing emails every week | 09:19 |
| johnthetubaguy | yes, been thinking along similar lines recently | 09:19 |
| ttx | So, basically I don't think the meetingless approach can work without someone dedicating a significant amount of time to beating the asynchronous drum | 09:20 |
| johnthetubaguy | totally agreed | 09:20 |
| ttx | From the TC experience I would say that it ends up being as much (if not more) time for the leader to drive the group | 09:20 |
| ttx | but with bonus points in visibility and accessibility | 09:21 |
| johnthetubaguy | I can totally believe its more work | 09:21 |
| ttx | so, overall worth it | 09:21 |
| johnthetubaguy | cool | 09:21 |
| ttx | but 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 ideal | 09:22 |
| ttx | I'd say we have two options | 09:22 |
| ttx | We find someone who followed the training who is willing to spend time driving the group | 09:22 |
| ttx | or | 09:22 |
| ttx | We dissolve the SWG into the TC | 09:23 |
| ttx | i.e. take over a number of the things and follow them at TC level | 09:23 |
| ttx | I would prefer the first option, but if the only people driving happen to be TC members, the overhead is costly | 09:23 |
| johnthetubaguy | I was hoping to help drive that, but its taking a long time to get myself a new job actually sorted | 09:23 |
| ttx | So ideally, we'd find a non-TC member to drive it | 09:23 |
| ttx | johnthetubaguy: if you still have plans to lead that, maybe we should wait a bit before dumping a "we are dead unless someone steps up" thread | 09:25 |
| johnthetubaguy | more non-elected TC people driving efforts would be great, and this is a good one to consider | 09:25 |
| ttx | johnthetubaguy: I could see someone else leading it, but probably not from day 0 | 09:25 |
| ttx | so if you could bootstrap it that would really help | 09:25 |
| johnthetubaguy | even if I am just helping hand things over to someone else we find could work | 09:25 |
| johnthetubaguy | yeah, happy to help bootstrap, etc | 09:26 |
| ttx | The 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 email | 09:26 |
| ttx | to send* | 09:26 |
| johnthetubaguy | what if we try the SWG as having a roll-up into your wiki page, for visibility? | 09:26 |
| ttx | johnthetubaguy: 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 |
| johnthetubaguy | more like a sub group I guess I mean | 09:27 |
| johnthetubaguy | yeah, true | 09:27 |
| ttx | I don't really want to make it appear as a TC subgroup though. Would really want non-technical people to get involved | 09:27 |
| ttx | quite a few of the marketing team at the Foundation attended the training last time | 09:28 |
| ttx | The first group was pretty technical so that triggered a lot of TC-driven actions | 09:28 |
| johnthetubaguy | I see what you mean about the implication there, don't want to put people off participating | 09:28 |
| ttx | But imho stewardship should go beyond us | 09:28 |
| ttx | and making it appear as a TC-driven or TC-subgroup thing would likely discourage bringing stewardship initiatives to other groups | 09:29 |
| johnthetubaguy | yeah, that's probably true | 09:29 |
| johnthetubaguy | the "i'm not technical so that can't be for me" problem | 09:30 |
| ttx | johnthetubaguy: 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 planning | 09:30 |
| ttx | (or continue doing it if you prefer :) | 09:30 |
| johnthetubaguy | yeah, that can be a TC TODO task to make sure I don't drop it | 09:31 |
| johnthetubaguy | heh, I think resurrect is probably more accurate | 09:31 |
| ttx | ack, will add a note to the CT status page so that we don't drop it | 09:32 |
| ttx | TC* | 09:32 |
| johnthetubaguy | sweet, thanks | 09:32 |
| ttx | johnthetubaguy: in the mean time, should I clear the meeting slot we currently have on calendar ? | 09:35 |
| ttx | probably should | 09:35 |
| johnthetubaguy | ttx: 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 alternative | 09:35 |
| johnthetubaguy | ttx: yeah, good point, we should do that | 09:35 |
| ttx | I'm on it | 09:35 |
| ttx | https://review.openstack.org/475712 | 09:37 |
| *** dims has quit IRC | 10:16 | |
| *** dims has joined #openstack-tc | 10:21 | |
| *** emagana has joined #openstack-tc | 11:23 | |
| *** emagana has quit IRC | 11:27 | |
| ttx | flaper87: 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 |
| sdague | heh | 12:42 |
| *** lbragstad_ has quit IRC | 12:49 | |
| *** mugsie_ is now known as mugsie | 12:52 | |
| *** mugsie has quit IRC | 12:53 | |
| *** mugsie has joined #openstack-tc | 12:53 | |
| *** emagana has joined #openstack-tc | 13:35 | |
| *** emagana has quit IRC | 13:39 | |
| *** emagana has joined #openstack-tc | 14:08 | |
| *** lbragstad_ has joined #openstack-tc | 14:38 | |
| *** lbragstad_ is now known as lbragstad | 14:42 | |
| *** hongbin has joined #openstack-tc | 14:46 | |
| * dtroyer peeks in | 14:52 | |
| *** jpich has quit IRC | 15:47 | |
| *** rockyg has joined #openstack-tc | 19:02 | |
| *** rockyg has quit IRC | 21:57 | |
| *** openstack has joined #openstack-tc | 22:16 | |
| *** dhellmann has quit IRC | 22:18 | |
| *** dhellmann has joined #openstack-tc | 22:19 | |
| *** dhellmann has quit IRC | 22:20 | |
| *** dhellmann has joined #openstack-tc | 22:20 | |
| *** emagana has quit IRC | 23:17 | |
| *** emagana has joined #openstack-tc | 23:17 | |
| *** emagana_ has joined #openstack-tc | 23:20 | |
| *** emagana has quit IRC | 23:21 | |
| *** emagana_ has quit IRC | 23:25 | |
| *** emagana has joined #openstack-tc | 23:27 | |
| *** emagana has quit IRC | 23:31 | |
Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!