20:02:23 #startmeeting tc-summit-planning 20:02:24 Meeting started Fri May 1 20:02:23 2015 UTC and is due to finish in 60 minutes. The chair is dhellmann. Information about MeetBot at http://wiki.debian.org/MeetBot. 20:02:25 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 20:02:27 The meeting name has been set to 'tc_summit_planning' 20:02:36 we have 2 planning tools set up 20:02:38 #link https://docs.google.com/spreadsheets/d/1vCTZBJKCMZ2xBhglnuK3ciKo3E8UMFo5S5lmIAYMCSE/edit#gid=827503418 20:02:49 and I broke down and created an etherpad 20:02:50 #link https://etherpad.openstack.org/p/liberty-cross-project-session-planning 20:03:05 I can't see the whole google doc at once, so it was hard to get an overall view 20:03:27 I thought a good goal for today would be to identify any obvious *yes* or *no* candidates on the list 20:03:34 dhellmann: yea. thanks. that was making it hard to get an overview 20:03:58 I took a stab at those in the etherpad, with yes in bold and no using strikeout 20:04:00 o/ 20:04:02 its saturday 20:04:05 so I'm not really here 20:04:12 * dhellmann pretends not to notice lifeless 20:04:50 shall we go down the list one by one? 20:06:37 dhellmann: shall we use +1/-1 on the line, and then discuss more if there's not a concensus? 20:06:44 devananda: sure 20:11:35 * annegentle waves, apologizes for being late 20:13:59 hahaha I'm early 20:15:19 annegentle: early, late, you're here :-) 20:15:23 we're using https://etherpad.openstack.org/p/liberty-cross-project-session-planning 20:15:57 annegentle: we're taking a quick temperature, and looking for obvious yes or no candidates in the full list 20:16:09 cool 20:16:48 annegentle: (I'm assuming you don't have scrollback) bold is "yes" and strikethrough is "no", but so far those are just my proposals and we're all leaving the usual votes 20:20:15 markmcclain, devananda, sdague, flaper87, annegentle, lifeless : keep in mind, we're evaluating the proposals, not trying to design solutions to the questions posed by them :-) 20:20:21 heh 20:20:44 * dhellmann notes the discussion of getting notifications to end users as an example of going too deep 20:21:23 dhellmann: mmmm, we're evaluating their relative merit for a very constrained resource 20:21:58 dhellmann: knowing if its contentious (face time might help) or trivial (face time a waste) is entirely relevant IMO 20:22:53 lifeless: fair 20:23:10 * dimsum__ wonders if you all are on the phone or irc chat? 20:23:19 dimsum__: https://etherpad.openstack.org/p/liberty-cross-project-session-planning 20:23:32 ah 20:23:46 dimsum__: I'm just here 20:24:11 yeah, we're not on the phone or anything, but most of the discussion is happening in the etherpad 20:27:09 dhellmann: by my count, we've got 10 sessions with several +1's now 20:27:45 devananda: cool, thanks, I'm following discussions but hadn't counted. Do you want to bold those? 20:27:54 dhellmann: k 20:27:57 devananda: ty 20:28:44 so 10 out of 14... 20:29:01 how many slots do we have? 20:29:11 markmcclain, devananda, sdague, flaper87, annegentle, lifeless : are we ready to eliminate any more sessions? 20:29:13 lifeless: 14 20:29:22 at least that was my count 20:29:39 lifeless: double check my math? https://docs.google.com/spreadsheets/d/1VsFdRYGbX5eCde81XDV7TrPBfEC7cgtOFikruYmqbPY/edit#gid=569963128 20:30:16 project deletion.. seemed to get lost in etherpad… what does everyone thing? 20:30:21 s/thing/think/ 20:30:32 7*2 20:31:35 lifeless: thanks 20:31:36 markmcclain: is there much to talk about? 20:31:55 from an ops perspective there's no real standard 20:32:19 and that interface would need to be available any interested project 20:32:39 yeah, this is an area where we can do some greenfield API design consistently 20:32:40 markmcclain: it seems like the design work has been done, and there's just some questions about what contexts the python API might be used from? 20:33:08 markmcclain: sounds like the model of 'pick one project and work with it, then another etc' might fit well? 20:33:47 markmcclain: I'm just wrestling with whether the initiative will actually move forward from a cross-project session: it seems like its already sufficiently mature and uncontentious... 20:34:46 Getting notifications to users looks like it has two proposals. #10 and #25. Combine them? 20:35:19 lifeless: mainly was mainly wondering if we needed to give some room even for something that most agree on 20:35:51 devananda: ah, I didn't recognize those as the same thing, interesting 20:36:39 devananda: it sounds like #25 has some cinder-specific work to propose as a standard, rather than a new service (which is what I'm getting from #10) 20:37:06 dhellmann: all the more reason to get them all talking together IMO 20:37:19 lifeless: yep 20:37:56 hrm, if I move them we'll lose our numbering 20:38:00 I'll fix that after the meeting 20:38:47 dhellmann: numbering is already cactus 20:39:00 dhellmann: I'll strike out 25 and bold 8, leaving the merge to you for later 20:39:09 lifeless: the numbers should line up with the spreadsheet rows 20:39:27 devananda: ++ 20:43:41 rather than hash out more on the topics that already have a concensus 20:43:51 i'm looking at the ones that have mixed votes 20:43:55 dhellmann: long as the numbers within the etherpad are consistent we're ok :) 20:44:27 lifeless: yep, and the titles are copied and pasted so I can re-align based on those if I have to 20:44:50 dhellmann: where would we talk about changes to the release process given the big tent ideas? (global requirements etc) 20:44:55 here's 3 more: documentation, project deletion, service users / unified policy 20:45:09 dhellmann: also, what about taking 2 slots for some of these discussions? 20:45:15 dimsum__: we have some session within the release management track for those 20:45:23 dhellmann: ack thx 20:45:26 devananda: do you have anything specific in mind? 20:46:00 in-team scaling? notifications to end-users? release models? 20:46:17 I could imagine each of those being somewhat contentous, or at least having many viewppoints that we'd benefit from hearing 20:46:17 I'm going to advocate for notifications to end users 20:46:41 lifeless: getting 2 slots? 20:46:44 we had firedrills with HP Helion release stuff a year back because of the lack of a good answer there 20:46:57 I'm not sure about needing two slots 20:47:07 yeah, I'm not inclined to give anyone 2 slots at this point 20:47:14 does release mgmt have a track? 20:47:26 crossed wires, though you were talking about what to put in the 4 slots 20:47:28 annegentle: yes 20:47:40 if not a track, at least some time on friday 20:47:44 but I think there's a track 20:47:55 lifeless: sorry. I posted two different lists. first for 'things that dont have consensus yet' and second for 'things that might be worth 2 slots' 20:48:14 relmgmt has wed afternoon 20:48:18 and a working slot on thursday 20:48:36 thanks, lifeless 20:48:38 https://libertydesignsummit.sched.org/overview/type/design+summit/Release%20Management 20:48:43 the session schedule is https://docs.google.com/spreadsheets/d/1VsFdRYGbX5eCde81XDV7TrPBfEC7cgtOFikruYmqbPY/edit#gid=569963128 20:48:49 also the link from dims 20:48:54 so lets include Roles for service users 20:49:01 with policy file rolled in 20:49:35 yeah, the policy/roles stuff seems to have some consensus 20:52:07 dhellmann: i see a "API working Group" is there somewhere a slot for the "Security WG"? 20:52:19 dimsum__: they have a track 20:52:40 other than the policy and role stuff, I don't think there were security-related proposals 20:52:49 dimsum__: https://docs.google.com/spreadsheets/d/1vCTZBJKCMZ2xBhglnuK3ciKo3E8UMFo5S5lmIAYMCSE/edit#gid=827503418 20:52:53 ah found them 20:52:54 thx 20:53:11 I'm going to nic "Cloud Service Federation" 20:53:32 I wish that logging session proposal was stronger 20:54:51 it also looks like we agree to leave out the big tent session 20:55:18 dhellmann: we don't have to take exactly what is proposed 20:55:25 that's true 20:55:42 markmcclain: do you mean we should define another logging session, or something else? 20:56:32 yeah…we can always to work community to polish up any sessions that are good in concept but missing items in the proposal 20:56:43 dhellmann: on an email thread the person who logged #24 is pointing to https://wiki.openstack.org/wiki/OpenStack_cascading_solution 20:57:15 dimsum__: that was proposed in paris ... 20:57:22 is this going to just be a repeat? 20:57:25 devananda: y, same person 20:57:28 yeah, that proposal has already been rejected 20:58:25 yep 20:58:37 not advocating, just adding data :) 20:58:42 yep 20:59:05 annegentle, devananda, markmcclain, lifeless: we're about out of time for a 1 hour slot here. Would it be productive to keep going? 20:59:13 dimsum__ ^^ 20:59:21 * dimsum__ drops off :) thx everyone 20:59:26 thanks, dimsum__ 20:59:27 theres a lottt of good sessions there 20:59:35 I can keep going a little bit longer 20:59:48 at least 15 mins 21:00:12 I need to bounce 21:00:13 gl 21:00:19 thanks, lifeless 21:00:45 I've got a few more minutes 21:01:37 annegentle, markmcclain, and devananda : should we try to finish the list, or should I go back to the proposers from some of the "needs more work" sessions and ask them for more details by monday? 21:01:50 that's going to be a tight deadline, maybe early tuesday? 21:01:54 dhellmann: so, for Lana at least, she's off for the weekend (Aussie) 21:02:04 early tues would work 21:02:05 but will be back online sooner than us 21:02:18 I think it's worthwhile to ask for more details 21:02:27 do we have enough feedback to make sure the proposers can fix things? 21:02:41 annegentle: we should look at that one again, because I'm surprised it's mixed 21:02:45 dhellmann: I've got to run -- I think we're close enough to call it done for now 21:02:55 devananda: cool, thanks 21:03:10 annegentle: it's +1 and +0, I'm not sure why that's mixed. 21:03:21 Does anyone think the docs session is *not* ready as the proposal stands? 21:03:21 dhellmann: ok 21:03:38 remember, these are our proposals to the TC, not a final list 21:03:40 dhellmann: there was just confusion about audience -- but if that's clear now, that's fine 21:03:53 dhellmann: I probably wont have time on monday for another pass, fyi. carry on w/o me :) 21:03:56 annegentle: I think you cleared that up by saying there is an ops session 21:03:59 dhellmann: and she can clear up for the proposal itself to drum up attendeses 21:04:02 devananda: cool, thanks 21:04:03 +1 for docs 21:04:06 cool 21:04:10 ok, docs is in for now then 21:04:37 so that leaves 2 slots 21:05:14 ok, I'd really like "tags for cross project consumers" 21:05:24 and then ask for more info on logging and UX 21:05:38 really? the tags one felt like something they could just sort of do, without needing a lot of face time 21:05:56 I think UX _could_ be a useful session if done right 21:06:08 27 (UX) needs to be narrowed down a bit more 21:06:12 Project deletion may come out of some of the roles-for-service-users/unified-policy-file if we ask them to? 21:06:24 Did horizon reject UX proposal? 21:06:33 (not that only horizon could host it) 21:06:43 horizon who? 21:07:02 david-lyle, #27 here: https://docs.google.com/spreadsheets/d/1vCTZBJKCMZ2xBhglnuK3ciKo3E8UMFo5S5lmIAYMCSE/edit#gid=827503418 21:07:14 hey david-lyle :) wondering about Piet's cross project UX proposal 21:07:40 I think his goal is broader than horizon 21:07:51 yes, the proposal specifically says that 21:07:53 I don't think this is new or contentious 21:08:08 I recommended concrete proposals to the mailing list 21:08:21 I don't think it hurts to discuss it 21:08:24 yeah it is broader than horizon, did he propose to the conf itself, do you know? 21:08:50 He did have a conference proposal, but I think the topic was a little different 21:09:07 more around doing UX work in OpenStack 21:09:16 more reporting less discussion 21:09:19 we should really require a link to an etherpad or wiki page next time 21:09:57 annegentle: do you want to contact Piet while I contact Rocky? 21:10:25 he's Piet on IRC 21:10:47 apparently not in this room, but in #openstack-horizon 21:12:04 dhellmann: ok will do 21:12:08 annegentle: thanks 21:12:28 david-lyle: ok, I'm going offline soon so I was hoping for email 21:12:45 ah, I can dig that up, just a sec 21:12:54 heh I should go offline soon :) 21:13:11 I have his email (looks to be sure) 21:13:23 I think that's about as far as we're going to get tonight. Shall we call it done, and pick up Tuesday? Before or during the TC meeting? 21:13:29 yep 21:13:40 (yep, I have piet's email) 21:13:45 yeah let's call it done 21:13:46 dhellmann: +1 21:14:04 uhhhh not sure on TC meeting agenda so far but seems like worthwhile to discuss there 21:14:17 ok, thanks everyone for helping with this, I think it was a really fruitful exercise 21:14:31 annegentle: I'll add it to the agenda 21:14:52 #endmeeting