Re: [openstack-dev] [all] Austin Design Summit track layout

2016-03-31 Thread Thierry Carrez
OK, please find attached the final layout. Changes: - Swapped Oslo and Stable fishbowl sessions on Thursday afternoon. - Swapped Fuel and Swift workroom sessions on Thursday afternoon This will be pushed to the official schedule ASAP and then PTLs will be able to tweak titles and descriptions

Re: [openstack-dev] [all] Austin Design Summit track layout

2016-03-30 Thread Anita Kuno
On 03/30/2016 05:24 AM, Thierry Carrez wrote: > See new version attached. This will be pushed to the official schedule > tomorrow, so please reply here today if you see any major issue with it. > > Changes: > - swapped the release and stable slots to accommodate mriedem > - moved Astara fishbowl

Re: [openstack-dev] [all] Austin Design Summit track layout

2016-03-30 Thread Hongbin Lu
regards, Hongbin -Original Message- From: Thierry Carrez [mailto:thie...@openstack.org] Sent: March-30-16 5:25 AM To: openstack-dev@lists.openstack.org Subject: Re: [openstack-dev] [all] Austin Design Summit track layout See new version attached. This will be pushed to the official schedule

Re: [openstack-dev] [all] Austin Design Summit track layout

2016-03-30 Thread Thierry Carrez
Matt Riedemann wrote: 1:30pm on Thursday (first slot after lunch is unconference for nova) would work for me. OK, I'll make that swap too (unless Josh hits me with a trout over the night) -- Thierry Carrez (ttx) __

Re: [openstack-dev] [all] Austin Design Summit track layout

2016-03-30 Thread Thierry Carrez
John Dickinson wrote: Yes, I checked on that. Based on where in the schedule that is, and based on the way we're planning on doing the working sessions, it will be just fine for me to not be in that particular session. It's much better for the community that we have the contiguous block that

Re: [openstack-dev] [all] Austin Design Summit track layout

2016-03-30 Thread Matt Riedemann
On 3/30/2016 10:42 AM, Ihar Hrachyshka wrote: Thierry Carrez wrote: Ihar Hrachyshka wrote: I'd then have the same problem than Matt here as I'm the Release CPL for Nova. That said, given I think I'm the only person probably having the issue, I can say fair enough and

Re: [openstack-dev] [all] Austin Design Summit track layout

2016-03-30 Thread John Dickinson
Yes, I checked on that. Based on where in the schedule that is, and based on the way we're planning on doing the working sessions, it will be just fine for me to not be in that particular session. It's much better for the community that we have the contiguous block that I personally be present

Re: [openstack-dev] [all] Austin Design Summit track layout

2016-03-30 Thread Ihar Hrachyshka
Thierry Carrez wrote: Ihar Hrachyshka wrote: I'd then have the same problem than Matt here as I'm the Release CPL for Nova. That said, given I think I'm the only person probably having the issue, I can say fair enough and try to clone myself before the Summit :-)

Re: [openstack-dev] [all] Austin Design Summit track layout

2016-03-30 Thread Thierry Carrez
Ihar Hrachyshka wrote: I'd then have the same problem than Matt here as I'm the Release CPL for Nova. That said, given I think I'm the only person probably having the issue, I can say fair enough and try to clone myself before the Summit :-) Actually, now that I am a release CPL for Neutron,

Re: [openstack-dev] [all] Austin Design Summit track layout

2016-03-30 Thread Ihar Hrachyshka
Sylvain Bauza wrote: Le 29/03/2016 09:48, Thierry Carrez a écrit : Matt Riedemann wrote: I see one problem. The single stable team fishbowl session is scheduled for the last slot on Thursday (5pm). The conflict I have with that is the nova team does it's

Re: [openstack-dev] [all] Austin Design Summit track layout

2016-03-30 Thread Thierry Carrez
See new version attached. This will be pushed to the official schedule tomorrow, so please reply here today if you see any major issue with it. Changes: - swapped the release and stable slots to accommodate mriedem - moved Astara fishbowl to Thu morning to avoid conflict with Tacker - moved

Re: [openstack-dev] [all] Austin Design Summit track layout

2016-03-30 Thread Vladimir Kozhukalov
On Wed, Mar 30, 2016 at 11:01 AM, Thierry Carrez wrote: > John Dickinson wrote: > >> On Thursday, I'd like to proposed swapping Swift's 1:30pm session with >> Fuel's 2:20pm session. This will give Swift a contiguous time block in the >> afternoon, and Fuel's session would

Re: [openstack-dev] [all] Austin Design Summit track layout

2016-03-30 Thread Thierry Carrez
Matt Riedemann wrote: On 3/29/2016 2:48 AM, Thierry Carrez wrote: Matt Riedemann wrote: I see one problem. The single stable team fishbowl session is scheduled for the last slot on Thursday (5pm). The conflict I have with that is the nova team does it's priority/scheduling talk in the last

Re: [openstack-dev] [all] Austin Design Summit track layout

2016-03-30 Thread Thierry Carrez
Mark McClain wrote: Would it be possible to move the Astara fish bowl session to Thursday morning? It would avoid the conflict with Tacker. We’re hoping to see where the teams could cooperate across projects in the future. Yes, I'll move it to Thursday 9am, unless someone objects. --

Re: [openstack-dev] [all] Austin Design Summit track layout

2016-03-30 Thread Thierry Carrez
John Dickinson wrote: On Thursday, I'd like to proposed swapping Swift's 1:30pm session with Fuel's 2:20pm session. This will give Swift a contiguous time block in the afternoon, and Fuel's session would line up right after their full morning (albeit after the lunch break). I have not had a

Re: [openstack-dev] [all] Austin Design Summit track layout

2016-03-29 Thread John Dickinson
On Thursday, I'd like to proposed swapping Swift's 1:30pm session with Fuel's 2:20pm session. This will give Swift a contiguous time block in the afternoon, and Fuel's session would line up right after their full morning (albeit after the lunch break). I have not had a chance to talk to anyone

Re: [openstack-dev] [all] Austin Design Summit track layout

2016-03-29 Thread Matt Riedemann
On 3/29/2016 2:48 AM, Thierry Carrez wrote: Matt Riedemann wrote: I see one problem. The single stable team fishbowl session is scheduled for the last slot on Thursday (5pm). The conflict I have with that is the nova team does it's priority/scheduling talk in the last session on the last day

Re: [openstack-dev] [all] Austin Design Summit track layout

2016-03-29 Thread Mark McClain
> On Mar 28, 2016, at 6:28 AM, Thierry Carrez wrote: > > Hi everyone, > > Please find attached in PDF the proposed layout for the various tracks at the > Design Summit in Austin. I tried to take into account all the talk conflicts > and the constraints that you

Re: [openstack-dev] [all] Austin Design Summit track layout

2016-03-29 Thread Sylvain Bauza
Le 29/03/2016 09:48, Thierry Carrez a écrit : Matt Riedemann wrote: I see one problem. The single stable team fishbowl session is scheduled for the last slot on Thursday (5pm). The conflict I have with that is the nova team does it's priority/scheduling talk in the last session on the last

Re: [openstack-dev] [all] Austin Design Summit track layout

2016-03-29 Thread Thierry Carrez
Matt Riedemann wrote: I see one problem. The single stable team fishbowl session is scheduled for the last slot on Thursday (5pm). The conflict I have with that is the nova team does it's priority/scheduling talk in the last session on the last day for design summit fishbowl sessions (non-meetup

Re: [openstack-dev] [all] Austin Design Summit track layout

2016-03-28 Thread Matt Riedemann
On 3/28/2016 5:28 AM, Thierry Carrez wrote: Hi everyone, Please find attached in PDF the proposed layout for the various tracks at the Design Summit in Austin. I tried to take into account all the talk conflicts and the constraints that you communicated, although as always there is no perfect

[openstack-dev] [all] Austin Design Summit track layout

2016-03-28 Thread Thierry Carrez
Hi everyone, Please find attached in PDF the proposed layout for the various tracks at the Design Summit in Austin. I tried to take into account all the talk conflicts and the constraints that you communicated, although as always there is no perfect solution. Let me know if you see major