*** amrith is now known as _amrith_ | 00:21 | |
*** ebalduf has quit IRC | 00:22 | |
*** _amrith_ is now known as amrith | 00:40 | |
*** vilobhmm111 has quit IRC | 00:41 | |
*** vilobhmm11 has joined #openstack-meeting-cp | 00:46 | |
*** annegentle has joined #openstack-meeting-cp | 00:49 | |
*** annegentle has quit IRC | 00:54 | |
*** harlowja has quit IRC | 01:00 | |
*** harlowja has joined #openstack-meeting-cp | 01:03 | |
*** sdake has quit IRC | 01:28 | |
*** sdake has joined #openstack-meeting-cp | 01:32 | |
*** amrith is now known as _amrith_ | 01:59 | |
*** sdake_ has joined #openstack-meeting-cp | 02:20 | |
*** sdake has quit IRC | 02:22 | |
*** openstackstatus has quit IRC | 03:01 | |
*** sdake_ has quit IRC | 03:06 | |
*** sdake has joined #openstack-meeting-cp | 03:07 | |
*** ebalduf has joined #openstack-meeting-cp | 03:16 | |
*** sdake has quit IRC | 03:17 | |
*** sdake has joined #openstack-meeting-cp | 03:18 | |
*** sdake has quit IRC | 03:28 | |
*** sheel has joined #openstack-meeting-cp | 03:41 | |
*** sekrit has quit IRC | 03:51 | |
*** sekrit has joined #openstack-meeting-cp | 04:05 | |
*** persia has quit IRC | 04:31 | |
*** persia has joined #openstack-meeting-cp | 04:33 | |
*** askb has joined #openstack-meeting-cp | 04:38 | |
*** xyang1 has quit IRC | 04:48 | |
*** askb has quit IRC | 06:23 | |
*** ebalduf has quit IRC | 06:37 | |
*** vgridnev has joined #openstack-meeting-cp | 06:47 | |
*** vgridnev has quit IRC | 08:02 | |
*** openstackstatus has joined #openstack-meeting-cp | 08:29 | |
*** ChanServ sets mode: +v openstackstatus | 08:29 | |
-openstackstatus- NOTICE: jobs depending on npm are now working again | 08:33 | |
*** vilobhmm11 has quit IRC | 09:09 | |
*** vgridnev has joined #openstack-meeting-cp | 09:17 | |
*** Kiall has quit IRC | 10:14 | |
*** Kiall has joined #openstack-meeting-cp | 10:14 | |
*** sdague has joined #openstack-meeting-cp | 10:20 | |
*** kmartin has quit IRC | 10:28 | |
*** vgridnev has quit IRC | 11:39 | |
*** _amrith_ is now known as amrith | 11:44 | |
*** ChanServ changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings" | 11:45 | |
*** vgridnev has joined #openstack-meeting-cp | 12:03 | |
*** jhesketh has quit IRC | 12:07 | |
*** jhesketh has joined #openstack-meeting-cp | 12:07 | |
*** raildo-afk is now known as raildo | 12:18 | |
*** sigmavirus24_awa is now known as sigmavirus24 | 12:47 | |
*** annegentle has joined #openstack-meeting-cp | 12:51 | |
*** xyang1 has joined #openstack-meeting-cp | 13:26 | |
samueldmq | thingee: fyi I updated patch 295940 to fix oslo reference, as per dhellmann's review | 13:27 |
---|---|---|
*** annegentle has quit IRC | 13:38 | |
*** ebalduf has joined #openstack-meeting-cp | 13:59 | |
*** rpjr_ has joined #openstack-meeting-cp | 14:05 | |
*** sdake has joined #openstack-meeting-cp | 14:07 | |
*** sdake has quit IRC | 14:12 | |
*** sdake has joined #openstack-meeting-cp | 14:21 | |
*** sigmavirus24 is now known as sigmavirus24_awa | 14:55 | |
*** sigmavirus24_awa is now known as sigmavirus24 | 14:55 | |
thingee | samueldmq: thank you! | 15:49 |
*** angdraug has joined #openstack-meeting-cp | 16:04 | |
*** annegent_ has joined #openstack-meeting-cp | 16:08 | |
*** vgridnev has quit IRC | 16:21 | |
*** vgridnev has joined #openstack-meeting-cp | 16:21 | |
*** david-lyle has quit IRC | 16:36 | |
*** xyang1 has quit IRC | 16:47 | |
*** annegent_ has quit IRC | 16:49 | |
*** annegentle has joined #openstack-meeting-cp | 16:49 | |
*** angdraug has quit IRC | 16:58 | |
*** xyang1 has joined #openstack-meeting-cp | 17:02 | |
*** vgridnev has quit IRC | 17:04 | |
*** david-lyle has joined #openstack-meeting-cp | 17:06 | |
*** david-lyle has quit IRC | 17:11 | |
*** annegentle has quit IRC | 17:14 | |
*** annegentle has joined #openstack-meeting-cp | 17:14 | |
*** annegentle has quit IRC | 17:15 | |
*** annegentle has joined #openstack-meeting-cp | 17:15 | |
*** david-lyle has joined #openstack-meeting-cp | 17:17 | |
*** david-lyle has quit IRC | 17:23 | |
*** david-lyle has joined #openstack-meeting-cp | 17:56 | |
*** david-lyle has quit IRC | 17:56 | |
*** david-lyle has joined #openstack-meeting-cp | 17:58 | |
*** vgridnev has joined #openstack-meeting-cp | 17:58 | |
*** vilobhmm11 has joined #openstack-meeting-cp | 18:13 | |
*** vilobhmm111 has joined #openstack-meeting-cp | 18:14 | |
*** annegentle has quit IRC | 18:16 | |
*** annegentle has joined #openstack-meeting-cp | 18:16 | |
*** vilobhmm11 has quit IRC | 18:18 | |
*** sdake_ has joined #openstack-meeting-cp | 18:26 | |
*** sdake has quit IRC | 18:26 | |
*** vilobhmm111 has quit IRC | 18:39 | |
*** angdraug has joined #openstack-meeting-cp | 18:44 | |
*** hemna is now known as hemnafk | 18:48 | |
*** annegentle has quit IRC | 18:49 | |
*** annegentle has joined #openstack-meeting-cp | 18:50 | |
*** annegentle has quit IRC | 18:52 | |
*** nikhil has quit IRC | 19:07 | |
*** nikhil has joined #openstack-meeting-cp | 19:11 | |
*** david-lyle_ has joined #openstack-meeting-cp | 19:13 | |
*** vgridnev has quit IRC | 19:14 | |
*** david-lyle has quit IRC | 19:15 | |
*** sigmavirus24 is now known as sigmavirus24_awa | 19:17 | |
*** david-lyle_ has quit IRC | 19:19 | |
*** david-lyle has joined #openstack-meeting-cp | 19:29 | |
*** vilobhmm11 has joined #openstack-meeting-cp | 19:30 | |
*** david-lyle has quit IRC | 19:31 | |
*** david-lyle has joined #openstack-meeting-cp | 19:31 | |
*** david-lyle has quit IRC | 19:37 | |
*** dtroyer_zz has joined #openstack-meeting-cp | 20:00 | |
sdague | ok, who is around to help with session scheduling? | 20:01 |
ttx | o/ | 20:01 |
dims | o/ | 20:01 |
sdague | #startmeeting newton-cross-project-session-scheduling | 20:01 |
openstack | Meeting started Thu Apr 7 20:01:51 2016 UTC and is due to finish in 60 minutes. The chair is sdague. Information about MeetBot at http://wiki.debian.org/MeetBot. | 20:01 |
openstack | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 20:01 |
*** openstack changes topic to " (Meeting topic: newton-cross-project-session-scheduling)" | 20:01 | |
openstack | The meeting name has been set to 'newton_cross_project_session_scheduling' | 20:01 |
sdague | ok, potentially useful for logging | 20:02 |
* mtreinish lurks | 20:02 | |
* harlowja sorta lurks | 20:02 | |
sdague | #link https://etherpad.openstack.org/p/newton-cross-project-sessions | 20:02 |
dims | hmm, won't add my nick at the top :) | 20:02 |
sdague | I added up all the scores earlier, and the results of the top 21 sessions were sent out to the tc ML | 20:02 |
sdague | #link http://lists.openstack.org/pipermail/openstack-tc/2016-April/001159.html | 20:03 |
*** shamail has joined #openstack-meeting-cp | 20:03 | |
sdague | first order of business, do we think any sessions should be 2x ? | 20:03 |
sdague | #topic any 2x sessions | 20:03 |
*** openstack changes topic to "any 2x sessions (Meeting topic: newton-cross-project-session-scheduling)" | 20:03 | |
ttx | I don't think there is a session that really needs everyone and therefore would justify a more complex setup than 3x7 | 20:03 |
sdague | ttx: oh, sorry, different question | 20:04 |
sdague | though that's a good one | 20:04 |
ttx | let me see if there is anything really too short | 20:04 |
dtroyer_zz | o/ | 20:04 |
sdague | should any session be a double block | 20:04 |
sdague | as in run long | 20:04 |
ttx | yeah, I started typing before you topiced | 20:04 |
sdague | but I agree we should look to do a 3 track by default and only do something diffferent if we have to | 20:04 |
ttx | sdague: not sure any of the big topics is advanced enough that a double session would make it make progress a lot more than a single-session | 20:05 |
dims | sdague : does not seem so | 20:05 |
dims | i mean don't see anything running too long | 20:05 |
sdague | ok, fair enough, I'm fine with that | 20:05 |
ttx | Co-installability is a long topic, but we are just breaking the subject | 20:05 |
sdague | the deployment tools one was the only thing I was wondering about | 20:05 |
ttx | single CLI maybe | 20:06 |
sdague | but maybe if we stick that early in the day it will let those folks continue to discuss later | 20:06 |
ttx | deployment, they can decide to continue it on Friday | 20:06 |
ttx | or even Tuesday yes | 20:06 |
sdague | ok, so I also thought there were a few natural pairings like deployment & coinstall | 20:06 |
sdague | I stuck those in there | 20:07 |
ttx | sdague: Maybe we should be clear that those are long topics that will surely not be solved in 40min and encourage people to meet afterwards | 20:07 |
sdague | yep | 20:07 |
dtroyer_zz | the continue on Friday is good, with some time inbetween to dig in small groups maybe | 20:07 |
sdague | ok, should we start proposing things into slots and see where we get to? | 20:07 |
ttx | Room sizes will be roughly equivalent so no need to prioritize by popularity | 20:07 |
ttx | Let me see if we group them by themes | 20:08 |
harlowja | def some kind of 'tech tebt theme' | 20:08 |
dtroyer_zz | 23 might follow the 13 then 6 chain well | 20:08 |
dims | "API/CLI" is probably a theme | 20:09 |
dims | 9 and 23 are non-technical (community) | 20:10 |
ttx | I think there are three big themes | 20:11 |
ttx | General policy/community decisions, like the EOL | 20:12 |
ttx | Implementation of things that are already there or in progress, like CLI | 20:12 |
ttx | And more... long-term technical design discussion | 20:12 |
dtroyer_zz | I like 9 and 24 being together, there is some connection between them | 20:13 |
ttx | That makes 3x7 | 20:13 |
dtroyer_zz | I think 9 should be ahead of 24, it might inform it somewhat | 20:13 |
ttx | Though I did have to shoehorn 4 into the first category | 20:13 |
sdague | right 9 & 24 pair | 20:13 |
dims | sorry i typoed before. yes 9/24 | 20:13 |
sdague | so, I want to tweak this a little because I think we have audience overlap as well, let me propose a thing | 20:14 |
ttx | sdague: saw my categorization on the etherpad ? makes sense for room split ? | 20:14 |
sdague | well, except I think deploy & coinstall should go back to back | 20:14 |
ttx | ok | 20:15 |
sdague | because coinstallability is basically held back by the deploy folks | 20:15 |
dims | ttx : 4 is borderline between practical and astroturf :) | 20:15 |
sdague | they are the stake holders | 20:15 |
ttx | Let's move Quto to room C then | 20:15 |
ttx | Quota | 20:15 |
sdague | sure | 20:15 |
ttx | and/or policy | 20:15 |
sdague | the 2 policy should go back to back | 20:15 |
ttx | 4/20 is a bit in-between room B and C | 20:16 |
*** annegentle has joined #openstack-meeting-cp | 20:16 | |
dims | 13 and 6, which one do we want to talk about first? | 20:16 |
dtroyer_zz | 13 I think? | 20:17 |
sdague | yeh, I'd rather make sure the pairings land together, and not across a break | 20:17 |
dims | sure | 20:17 |
ttx | maybe swapping 22 and 23 ? | 20:17 |
sdague | sure, I'd be fine with that | 20:17 |
dtroyer_zz | those two may have a similar audience | 20:18 |
ttx | 22 sounds more practical/immediate than 23 | 20:18 |
dims | agree | 20:18 |
ttx | I like the split | 20:18 |
sdague | ok, let me stare at this for a second and make sure I'm not screwed in my time blocks | 20:18 |
dtroyer_zz | We should swap 9 and 24 | 20:19 |
* ttx adds too | 20:19 | |
dims | 26 and 11 probably should be back to back | 20:19 |
dims | good | 20:19 |
ttx | I think I'm not screwed | 20:20 |
sdague | ok, so we ruined dtroyer_zz | 20:20 |
dtroyer_zz | swap the devstack pair with the policy pair? | 20:21 |
ttx | ideally we'd put the design summit split discussion at the end of the day, to limit bikeshedding | 20:21 |
sdague | yeh | 20:21 |
ttx | and move the CLI discussion earlier | 20:21 |
sdague | dtroyer_zz: what about move CLI early? | 20:21 |
ttx | so that we unscrew dtroyer | 20:21 |
dtroyer_zz | I think the split discussion that has consequences for 24 | 20:21 |
dtroyer_zz | CLi early is good | 20:22 |
ttx | like swap with discovery | 20:22 |
sdague | ttx I pushed it 2 blocks earlier | 20:22 |
sdague | before the coffee break | 20:22 |
ttx | let me see if we spread out the popular ones enough | 20:22 |
*** sdake_ is now known as sdake | 20:23 | |
dtroyer_zz | can we swap (14,20) with (26,11)? | 20:23 |
ttx | good for me | 20:23 |
ttx | but maybe sdague wanted to be at the cross-project one | 20:24 |
sdague | ok, that completely eliminates me from the room A meta discussions | 20:24 |
sdague | which might be fine | 20:24 |
dims | ttx is all day in room A except for one | 20:24 |
sdague | yeh, that's fine | 20:25 |
dims | we don't let him out :) | 20:25 |
sdague | so, I would invert 26,11 if we keep them there anyway | 20:25 |
ttx | sdague: ok move them and let's see how it works | 20:26 |
sdague | but, yeh, I can live with the jump | 20:26 |
dtroyer_zz | so B: 22, 1 11, 26, 16, 14, 20 | 20:26 |
dtroyer_zz | howzzat? | 20:27 |
sdague | actually can we stick policy in C | 20:27 |
sdague | in the midblock | 20:27 |
ttx | sdague: we could swap 24 and 9 (or 14 with 20) depending on which discussion from room A you prefer to be around for | 20:27 |
sdague | how about that? | 20:28 |
dtroyer_zz | works for me | 20:28 |
sdague | it moves policy to the C room, and I inverted the order on the devstack ones so I can be in the service one | 20:28 |
sdague | the v3 one I'm still not a huge fan of | 20:28 |
dims | lgtm | 20:29 |
dtroyer_zz | maybe that's the one you need to be in then? | 20:29 |
*** shamail has quit IRC | 20:29 | |
ttx | let's check moderators quickly | 20:29 |
sdague | dtroyer_zz: I'm not a huge fan of it on the schedule, because I don't see what is going to happen there that wouldn't happen in an email :) | 20:29 |
sdague | it's not like anything is controversial there, it just needs to be written down | 20:30 |
dtroyer_zz | ah, gotcha. | 20:30 |
sdague | right, there is definitely a mordred conflict | 20:31 |
sdague | 23 <-> 25? | 20:32 |
sdague | dtroyer_zz: that would put CLI in the first block | 20:32 |
ttx | 19/25 ? | 20:33 |
ttx | hmm, or 12<->25 | 20:33 |
sdague | sure, I think 19 <-> 25, 23 <-> 25, or 12 <-> 25 would all be fine | 20:34 |
ttx | arh no | 20:34 |
sdague | what does 12 - 25 break? | 20:34 |
ttx | we need thingee in that cross-project one | 20:34 |
sdague | oh, right | 20:34 |
ttx | conflict with 24 | 20:34 |
ttx | revert | 20:35 |
sdague | yep | 20:35 |
dtroyer_zz | 19<->25? | 20:35 |
ttx | I think mordred would want to be in co-installability | 20:35 |
sdague | sure, or 23 <-> 25? | 20:35 |
ttx | works for me | 20:35 |
dtroyer_zz | I can live with it, but those two probably have some audience overlap | 20:36 |
dtroyer_zz | er, 23 and 22 | 20:36 |
sdague | dtroyer_zz: possibly | 20:36 |
ttx | dtroyer_zz: how about we swap 19 and 23 now then | 20:36 |
dtroyer_zz | sure | 20:37 |
sdague | ok, ttx you c/p | 20:37 |
sdague | so we don't collide again | 20:37 |
sdague | the joys of bubble sort on schedule | 20:37 |
dims | y | 20:37 |
dims | :) | 20:37 |
ttx | been off the wheel for the last 5 min, so taht was not me :) | 20:37 |
sdague | ah, ok | 20:37 |
sdague | ok, done | 20:37 |
sdague | that looks about as sane a first pass as I can imagine | 20:38 |
ttx | I think I preferred 19/23 the other way, but that may be a bit selfish | 20:38 |
sdague | I can take that and propose it to the dev list, and ask for feedback | 20:38 |
ttx | (I would rather attend CLI on my last free slot) | 20:38 |
sdague | so, we could | 20:39 |
dtroyer_zz | I'd prefer to be in 10 over 17, so ya, it can go back | 20:39 |
sdague | 19<->23 and 1<->22 | 20:39 |
ttx | sdague: that is a risky recipe, note that there is no way to please everyone | 20:39 |
sdague | ttx: well, not so much feedback as hard conflicts at this point | 20:39 |
sdague | because who knows who is on the conf schedule | 20:39 |
ttx | sdague: 19<->23 and 1<->22 +1 | 20:39 |
sdague | dtroyer_zz: ? | 20:40 |
dtroyer_zz | +1 | 20:40 |
thingee | o/ | 20:40 |
sdague | ok | 20:40 |
sdague | people generally good with this as a draft? | 20:40 |
ttx | sdague: it's fine posting it as a strawman and ask for conflicts, just say that it is already the result of an optimization, so we won't likely be able to accommodate every request | 20:41 |
dims | sdague : LGTM | 20:41 |
ttx | LGTM | 20:41 |
dtroyer_zz | LGTM2 | 20:41 |
sdague | ttx: yeh, I will word it correctly to only ask for resolution if you have a hard conflict | 20:41 |
sdague | ok, I'll send that out in the morning | 20:42 |
ttx | hmm, let me check something else quickly | 20:42 |
sdague | oh no | 20:42 |
ttx | conference talks | 20:42 |
ttx | I have the list of conflicts there pre-canned for DS planning | 20:42 |
ttx | Monty has talks at 11:15 and 4:40 | 20:43 |
ttx | + robclark at 4:40 | 20:43 |
dims | he looks clear for those 2 slots | 20:43 |
dtroyer_zz | that may be ok, modulo distance? | 20:43 |
ttx | I don't care about distance. Run | 20:43 |
dims | haha | 20:43 |
* dtroyer_zz makes note to bring roller blades | 20:44 | |
dims | this is texas :) | 20:44 |
ttx | yes, looks good | 20:44 |
sdague | whew | 20:44 |
sdague | ok, thanks all. | 20:44 |
ttx | fun uh | 20:45 |
sdague | #action sdague to send email with schedule to list | 20:45 |
dtroyer_zz | cool | 20:45 |
dims | nice | 20:45 |
sdague | #action ttx to carve out 3x7 schedule block | 20:45 |
sdague | I can fill out details once you put the blocks there | 20:45 |
ttx | mind you, that talk conflict data was lifted off the schedule a few weeks ago so likely to be corrupt by now | 20:45 |
sdague | sure | 20:45 |
dtroyer_zz | gotta start somewhere | 20:46 |
ttx | sdague: alright, will create that tomorrow morning | 20:46 |
sdague | sounds good | 20:46 |
sdague | thanks all | 20:46 |
ttx | It's pretty solid I think | 20:46 |
sdague | yeh, me too | 20:46 |
ttx | sdague: thx a lot for driving | 20:46 |
sdague | no prob | 20:46 |
sdague | #endmeeting | 20:46 |
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings" | 20:46 | |
openstack | Meeting ended Thu Apr 7 20:46:28 2016 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 20:46 |
openstack | Minutes: http://eavesdrop.openstack.org/meetings/newton_cross_project_session_scheduling/2016/newton_cross_project_session_scheduling.2016-04-07-20.01.html | 20:46 |
openstack | Minutes (text): http://eavesdrop.openstack.org/meetings/newton_cross_project_session_scheduling/2016/newton_cross_project_session_scheduling.2016-04-07-20.01.txt | 20:46 |
openstack | Log: http://eavesdrop.openstack.org/meetings/newton_cross_project_session_scheduling/2016/newton_cross_project_session_scheduling.2016-04-07-20.01.log.html | 20:46 |
*** rpjr__ has joined #openstack-meeting-cp | 20:56 | |
*** david-lyle has joined #openstack-meeting-cp | 20:56 | |
*** rpjr_ has quit IRC | 20:57 | |
*** raildo is now known as raildo-afk | 21:11 | |
*** rpjr_ has joined #openstack-meeting-cp | 21:57 | |
*** rpjr__ has quit IRC | 22:00 | |
*** xyang1 has quit IRC | 22:00 | |
*** rpjr_ has quit IRC | 22:14 | |
*** rpjr_ has joined #openstack-meeting-cp | 22:28 | |
*** rpjr__ has joined #openstack-meeting-cp | 22:32 | |
*** angdraug has quit IRC | 22:32 | |
*** rpjr___ has joined #openstack-meeting-cp | 22:32 | |
*** rpjr_ has quit IRC | 22:35 | |
*** annegentle has quit IRC | 22:35 | |
*** rpjr__ has quit IRC | 22:36 | |
*** rpjr___ has quit IRC | 22:48 | |
*** rpjr_ has joined #openstack-meeting-cp | 22:54 | |
*** sdake has quit IRC | 22:54 | |
*** sdague has quit IRC | 22:57 | |
*** dtroyer_zz has left #openstack-meeting-cp | 22:57 | |
*** sdake has joined #openstack-meeting-cp | 22:58 | |
*** rpjr_ has quit IRC | 23:06 | |
*** sdake has quit IRC | 23:12 | |
*** vilobhmm111 has joined #openstack-meeting-cp | 23:15 | |
*** vilobhmm11 has quit IRC | 23:17 | |
*** markvoelker has quit IRC | 23:29 | |
*** vilobhmm111 has quit IRC | 23:46 | |
*** markvoelker has joined #openstack-meeting-cp | 23:59 |
Generated by irclog2html.py 2.14.0 by Marius Gedminas - find it at mg.pov.lt!