Re: [openstack-dev] [all] Newton Design Summit - Proposed slot allocation
Emilien Macchi wrote: On Thu, Mar 17, 2016 at 1:29 PM, Thierry Carrez wrote: Emilien Macchi wrote: On Thu, Mar 17, 2016 at 11:43 AM, Kirill Zaitsev wrote: Is it too late to ask for a half-day Contributors Meetup for murano? We had an extremely successful contributors meetup in Tokyo and I guess it is an error on our side, that we have not requested one for in Austin. Puppet OpenStack team can survive without 1/2 day for community meetup, 1/4 could work and we can share the room with you if Thierry can't find a slot for you. Yeah, all the meetup spaces we have for Friday have been allocated, and some of them will be pretty small :) Two options: share with another team, or just gather in one corner of the large room full of roundtables we'll have for lunch... At this stage given available room sizes I'd recommend the latter. Sharing the half day works for us, we don't need so much time. If it works for you, you can split the half day, PuppetOpenStack the first 1/4 and Murano for the second 1/4. OK noted... In the schedule the half-day will be marked as Puppet *and* Murano (there are no 1/4th days :) ), so you'll have to warn your contributors about when the topic switches. Cheers, -- Thierry Carrez (ttx) __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [all] Newton Design Summit - Proposed slot allocation
On 16 March 2016 at 15:26, Thierry Carrez wrote: > Hi PTLs, > > Here is the proposed slot allocation for project teams at the Newton > Design Summit in Austin. This is based on the requests the mitaka PTLs have > made, space availability and project activity & collaboration needs. > > | fb: fishbowl 40-min slots > | wr: workroom 40-min slots > | cm: Friday contributors meetup > | | full: full day, half: only morning or only afternoon > > Neutron: 9fb, cm:full > Nova: 18fb, cm:full > Fuel: 3fb, 11wr, cm:full > Horizon: 1fb, 7wr, cm:half > Cinder: 4fb, 5wr, cm:full > Keystone: 5fb, 8wr; cm:full > Ironic: 5fb, 5wr, cm:half > Heat: 4fb, 8wr, cm:half > TripleO: 2fb, 3wr, cm:half > Kolla: 4fb, 10wr, cm:full > Oslo: 3fb, 5wr > Ceilometer: 2fb, 7wr, cm:half > Manila: 2fb, 4wr, cm:half > Murano: 1fb, 2wr > Rally: 2fb, 2wr > Sahara: 2fb, 6wr, cm:half > Glance: 3fb, 5wr, cm:full > Magnum: 5fb, 5wr, cm:full > Swift: 2fb, 12wr, cm:full > OpenStackClient: 1fb, 1wr, cm:half > Senlin: 1fb, 5wr, cm:half > Monasca: 5wr > Trove: 3fb, 6wr, cm:half > Dragonflow: 1fb, 4wr, cm:half* > Mistral: 1fb, 3wr > Zaqar: 1fb, 3wr, cm:half > Barbican: 2fb, 6wr, cm:half > Designate: 1fb, 5wr, cm:half > Astara: 1fb, cm:full > Freezer: 1fb, 2wr, cm:half > Congress: 1fb, 3wr > Tacker: 1fb, 3wr, cm:half > Kuryr: 1fb, 5wr, cm:half* > Searchlight: 1fb, 2wr > Cue: no space request received > Solum: 1fb, 1wr > Winstackers: 1wr > CloudKitty: 1fb > EC2API: 2wr > > Infrastructure: 3fb, 4wr, cm:day** > Documentation: 4fb, 4wr, cm:half > Quality Assurance: 4fb, 4wr, cm:day** > PuppetOpenStack: 2fb, 3wr, cm:half > OpenStackAnsible: 1fb, 8wr, cm:half > Release mgmt: 1fb, cm:half > Security: 3fb, 2wr, cm:half > ChefOpenstack: 1fb, 2wr > Stable maint: 1fb > I18n: cm:half > Refstack: 3wr > OpenStack UX: 2wr > RpmPackaging: 1fb***, 1wr > App catalog: 1fb, 2wr > Packaging-deb: 1fb***, 1wr > > *: shared meetup between Kuryr and Dragonflow > **: shared meetup between Infra and QA > ***: shared fishbowl between RPM packaging and DEB packaging, for > collecting wider packaging feedback > > We'll start working on laying out those sessions over the available > rooms and time slots. Most of you have communicated constraints together > with their room requests (like Manila not wanting overlap with Cinder > sessions), and we'll try to accommodate them the best we can. If you have > extra constraints you haven't communicated yet, please reply to me ASAP. > It's be nice if Neutron didn't overlap as much with Nova, Ironic, QA and infra sessions, but I appreciate this could be a tall order. Thanks, Armando > Now is time to think about the content you'd like to cover during those > sessions and fire up those newton etherpads :) > > Cheers, > > -- > Thierry Carrez (ttx) > > __ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [all] Newton Design Summit - Proposed slot allocation
On Thu, Mar 17, 2016 at 11:43 AM, Kirill Zaitsev wrote: > Is it too late to ask for a half-day Contributors Meetup for murano? > > We had an extremely successful contributors meetup in Tokyo and I guess it > is an error on our side, that we have not requested one for in Austin. Puppet OpenStack team can survive without 1/2 day for community meetup, 1/4 could work and we can share the room with you if Thierry can't find a slot for you. > -- > Kirill Zaitsev > Murano team > Software Engineer > Mirantis, Inc > > On 16 March 2016 at 12:57:30, Thierry Carrez (thie...@openstack.org) wrote: > > Hi PTLs, > > Here is the proposed slot allocation for project teams at the Newton > Design Summit in Austin. This is based on the requests the mitaka PTLs > have made, space availability and project activity & collaboration needs. > > | fb: fishbowl 40-min slots > | wr: workroom 40-min slots > | cm: Friday contributors meetup > | | full: full day, half: only morning or only afternoon > > Neutron: 9fb, cm:full > Nova: 18fb, cm:full > Fuel: 3fb, 11wr, cm:full > Horizon: 1fb, 7wr, cm:half > Cinder: 4fb, 5wr, cm:full > Keystone: 5fb, 8wr; cm:full > Ironic: 5fb, 5wr, cm:half > Heat: 4fb, 8wr, cm:half > TripleO: 2fb, 3wr, cm:half > Kolla: 4fb, 10wr, cm:full > Oslo: 3fb, 5wr > Ceilometer: 2fb, 7wr, cm:half > Manila: 2fb, 4wr, cm:half > Murano: 1fb, 2wr > Rally: 2fb, 2wr > Sahara: 2fb, 6wr, cm:half > Glance: 3fb, 5wr, cm:full > Magnum: 5fb, 5wr, cm:full > Swift: 2fb, 12wr, cm:full > OpenStackClient: 1fb, 1wr, cm:half > Senlin: 1fb, 5wr, cm:half > Monasca: 5wr > Trove: 3fb, 6wr, cm:half > Dragonflow: 1fb, 4wr, cm:half* > Mistral: 1fb, 3wr > Zaqar: 1fb, 3wr, cm:half > Barbican: 2fb, 6wr, cm:half > Designate: 1fb, 5wr, cm:half > Astara: 1fb, cm:full > Freezer: 1fb, 2wr, cm:half > Congress: 1fb, 3wr > Tacker: 1fb, 3wr, cm:half > Kuryr: 1fb, 5wr, cm:half* > Searchlight: 1fb, 2wr > Cue: no space request received > Solum: 1fb, 1wr > Winstackers: 1wr > CloudKitty: 1fb > EC2API: 2wr > > Infrastructure: 3fb, 4wr, cm:day** > Documentation: 4fb, 4wr, cm:half > Quality Assurance: 4fb, 4wr, cm:day** > PuppetOpenStack: 2fb, 3wr, cm:half > OpenStackAnsible: 1fb, 8wr, cm:half > Release mgmt: 1fb, cm:half > Security: 3fb, 2wr, cm:half > ChefOpenstack: 1fb, 2wr > Stable maint: 1fb > I18n: cm:half > Refstack: 3wr > OpenStack UX: 2wr > RpmPackaging: 1fb***, 1wr > App catalog: 1fb, 2wr > Packaging-deb: 1fb***, 1wr > > *: shared meetup between Kuryr and Dragonflow > **: shared meetup between Infra and QA > ***: shared fishbowl between RPM packaging and DEB packaging, for > collecting wider packaging feedback > > We'll start working on laying out those sessions over the available > rooms and time slots. Most of you have communicated constraints together > with their room requests (like Manila not wanting overlap with Cinder > sessions), and we'll try to accommodate them the best we can. If you > have extra constraints you haven't communicated yet, please reply to me > ASAP. > > Now is time to think about the content you'd like to cover during those > sessions and fire up those newton etherpads :) > > Cheers, > > -- > Thierry Carrez (ttx) > > __ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > > > __ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > -- Emilien Macchi __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [all] Newton Design Summit - Proposed slot allocation
Is it too late to ask for a half-day Contributors Meetup for murano? We had an extremely successful contributors meetup in Tokyo and I guess it is an error on our side, that we have not requested one for in Austin. -- Kirill Zaitsev Murano team Software Engineer Mirantis, Inc On 16 March 2016 at 12:57:30, Thierry Carrez (thie...@openstack.org) wrote: Hi PTLs, Here is the proposed slot allocation for project teams at the Newton Design Summit in Austin. This is based on the requests the mitaka PTLs have made, space availability and project activity & collaboration needs. | fb: fishbowl 40-min slots | wr: workroom 40-min slots | cm: Friday contributors meetup | | full: full day, half: only morning or only afternoon Neutron: 9fb, cm:full Nova: 18fb, cm:full Fuel: 3fb, 11wr, cm:full Horizon: 1fb, 7wr, cm:half Cinder: 4fb, 5wr, cm:full Keystone: 5fb, 8wr; cm:full Ironic: 5fb, 5wr, cm:half Heat: 4fb, 8wr, cm:half TripleO: 2fb, 3wr, cm:half Kolla: 4fb, 10wr, cm:full Oslo: 3fb, 5wr Ceilometer: 2fb, 7wr, cm:half Manila: 2fb, 4wr, cm:half Murano: 1fb, 2wr Rally: 2fb, 2wr Sahara: 2fb, 6wr, cm:half Glance: 3fb, 5wr, cm:full Magnum: 5fb, 5wr, cm:full Swift: 2fb, 12wr, cm:full OpenStackClient: 1fb, 1wr, cm:half Senlin: 1fb, 5wr, cm:half Monasca: 5wr Trove: 3fb, 6wr, cm:half Dragonflow: 1fb, 4wr, cm:half* Mistral: 1fb, 3wr Zaqar: 1fb, 3wr, cm:half Barbican: 2fb, 6wr, cm:half Designate: 1fb, 5wr, cm:half Astara: 1fb, cm:full Freezer: 1fb, 2wr, cm:half Congress: 1fb, 3wr Tacker: 1fb, 3wr, cm:half Kuryr: 1fb, 5wr, cm:half* Searchlight: 1fb, 2wr Cue: no space request received Solum: 1fb, 1wr Winstackers: 1wr CloudKitty: 1fb EC2API: 2wr Infrastructure: 3fb, 4wr, cm:day** Documentation: 4fb, 4wr, cm:half Quality Assurance: 4fb, 4wr, cm:day** PuppetOpenStack: 2fb, 3wr, cm:half OpenStackAnsible: 1fb, 8wr, cm:half Release mgmt: 1fb, cm:half Security: 3fb, 2wr, cm:half ChefOpenstack: 1fb, 2wr Stable maint: 1fb I18n: cm:half Refstack: 3wr OpenStack UX: 2wr RpmPackaging: 1fb***, 1wr App catalog: 1fb, 2wr Packaging-deb: 1fb***, 1wr *: shared meetup between Kuryr and Dragonflow **: shared meetup between Infra and QA ***: shared fishbowl between RPM packaging and DEB packaging, for collecting wider packaging feedback We'll start working on laying out those sessions over the available rooms and time slots. Most of you have communicated constraints together with their room requests (like Manila not wanting overlap with Cinder sessions), and we'll try to accommodate them the best we can. If you have extra constraints you haven't communicated yet, please reply to me ASAP. Now is time to think about the content you'd like to cover during those sessions and fire up those newton etherpads :) Cheers, -- Thierry Carrez (ttx) __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [all] Newton Design Summit - Proposed slot allocation
Armando M. wrote: It's be nice if Neutron didn't overlap as much with Nova, Ironic, QA and infra sessions, but I appreciate this could be a tall order. It's difficult not to overlap with Nova, since they have a session on every time slot from Wednesday to Friday ;) So I can guarantee *all* your sessions will overlap with Nova sessions. We'll do what we can to reduce overlap with Ironic/QA/Infra. -- Thierry Carrez (ttx) __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [all] Newton Design Summit - Proposed slot allocation
On Thu, Mar 17, 2016 at 1:29 PM, Thierry Carrez wrote: > Emilien Macchi wrote: >> >> On Thu, Mar 17, 2016 at 11:43 AM, Kirill Zaitsev >> wrote: >>> >>> Is it too late to ask for a half-day Contributors Meetup for murano? >>> >>> We had an extremely successful contributors meetup in Tokyo and I guess >>> it >>> is an error on our side, that we have not requested one for in Austin. >> >> >> Puppet OpenStack team can survive without 1/2 day for community >> meetup, 1/4 could work and we can share the room with you if Thierry >> can't find a slot for you. > > > Yeah, all the meetup spaces we have for Friday have been allocated, and some > of them will be pretty small :) Two options: share with another team, or > just gather in one corner of the large room full of roundtables we'll have > for lunch... > > At this stage given available room sizes I'd recommend the latter. Sharing the half day works for us, we don't need so much time. If it works for you, you can split the half day, PuppetOpenStack the first 1/4 and Murano for the second 1/4. -- Emilien Macchi __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [all] Newton Design Summit - Proposed slot allocation
On 2016-03-18 08:53:11 +0530 (+0530), Armando M. wrote: > It's be nice if Neutron didn't overlap as much with Nova, Ironic, QA and > infra sessions, but I appreciate this could be a tall order. It seems like every project wants to avoid overlap with Infra sessions, so I'm not sure it will be easy to accommodate since we have to have our sessions _sometime_. However, we do usually try to make sure we have scouts in any Infra-relevant sessions for other teams, so give us a heads up on which ones those are and we will try to get someone to volunteer to sit in if we're not already spread too thin. -- Jeremy Stanley __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [all] Newton Design Summit - Proposed slot allocation
Emilien Macchi wrote: On Thu, Mar 17, 2016 at 11:43 AM, Kirill Zaitsev wrote: Is it too late to ask for a half-day Contributors Meetup for murano? We had an extremely successful contributors meetup in Tokyo and I guess it is an error on our side, that we have not requested one for in Austin. Puppet OpenStack team can survive without 1/2 day for community meetup, 1/4 could work and we can share the room with you if Thierry can't find a slot for you. Yeah, all the meetup spaces we have for Friday have been allocated, and some of them will be pretty small :) Two options: share with another team, or just gather in one corner of the large room full of roundtables we'll have for lunch... At this stage given available room sizes I'd recommend the latter. -- Thierry Carrez (ttx) __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [all] Newton Design Summit - Proposed slot allocation
On 2016-03-16 10:37:36 -0400 (-0400), Emilien Macchi wrote: [...] > If PuppetOpenStack and Infra could avoid overlaps, that would be > awesome. Some people are working on both groups and to continue the > best of our collaboration I would like to set this constraint. We'll do our best! We (Infra) also generally try to avoid overlap with Release Management, Stable Branch, Quality Assurance, and also Infra-related sessions for other teams. -- Jeremy Stanley __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [all] Newton Design Summit - Proposed slot allocation
On 03/16/2016 03:37 PM, Emilien Macchi wrote: > If PuppetOpenStack and Infra could avoid overlaps, that would be > awesome. Some people are working on both groups and to continue the > best of our collaboration I would like to set this constraint. > > Thanks a lot, Same for packaging + infra. Last time in Tokyo, Clack was nice enough to not attend the Infra sessions to attend the packaging-deb one. I hope the same thing will not happen again to someone (else?) from Infra, and that we can get some (much needed) time with them, so we can discuss the packaging jobs on infra. Cheers, Thomas Goirand (zigo) __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [all] Newton Design Summit - Proposed slot allocation
On Wed, Mar 16, 2016 at 10:37:36AM -0400, Emilien Macchi wrote: > If PuppetOpenStack and Infra could avoid overlaps, that would be > awesome. Some people are working on both groups and to continue the > best of our collaboration I would like to set this constraint. Please count Fuel in for this request, would be nice if at least fishbowl sessions for Fuel did not overlap with PuppetOpenStack and Infra. -- Dmitry Borodaenko __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [all] Newton Design Summit - Proposed slot allocation
On Wed, Mar 16, 2016 at 5:56 AM, Thierry Carrez wrote: > Hi PTLs, > > Here is the proposed slot allocation for project teams at the Newton Design > Summit in Austin. This is based on the requests the mitaka PTLs have made, > space availability and project activity & collaboration needs. > > | fb: fishbowl 40-min slots > | wr: workroom 40-min slots > | cm: Friday contributors meetup > | | full: full day, half: only morning or only afternoon > > Neutron: 9fb, cm:full > Nova: 18fb, cm:full > Fuel: 3fb, 11wr, cm:full > Horizon: 1fb, 7wr, cm:half > Cinder: 4fb, 5wr, cm:full > Keystone: 5fb, 8wr; cm:full > Ironic: 5fb, 5wr, cm:half > Heat: 4fb, 8wr, cm:half > TripleO: 2fb, 3wr, cm:half > Kolla: 4fb, 10wr, cm:full > Oslo: 3fb, 5wr > Ceilometer: 2fb, 7wr, cm:half > Manila: 2fb, 4wr, cm:half > Murano: 1fb, 2wr > Rally: 2fb, 2wr > Sahara: 2fb, 6wr, cm:half > Glance: 3fb, 5wr, cm:full > Magnum: 5fb, 5wr, cm:full > Swift: 2fb, 12wr, cm:full > OpenStackClient: 1fb, 1wr, cm:half > Senlin: 1fb, 5wr, cm:half > Monasca: 5wr > Trove: 3fb, 6wr, cm:half > Dragonflow: 1fb, 4wr, cm:half* > Mistral: 1fb, 3wr > Zaqar: 1fb, 3wr, cm:half > Barbican: 2fb, 6wr, cm:half > Designate: 1fb, 5wr, cm:half > Astara: 1fb, cm:full > Freezer: 1fb, 2wr, cm:half > Congress: 1fb, 3wr > Tacker: 1fb, 3wr, cm:half > Kuryr: 1fb, 5wr, cm:half* > Searchlight: 1fb, 2wr > Cue: no space request received > Solum: 1fb, 1wr > Winstackers: 1wr > CloudKitty: 1fb > EC2API: 2wr > > Infrastructure: 3fb, 4wr, cm:day** > Documentation: 4fb, 4wr, cm:half > Quality Assurance: 4fb, 4wr, cm:day** > PuppetOpenStack: 2fb, 3wr, cm:half > OpenStackAnsible: 1fb, 8wr, cm:half > Release mgmt: 1fb, cm:half > Security: 3fb, 2wr, cm:half > ChefOpenstack: 1fb, 2wr > Stable maint: 1fb > I18n: cm:half > Refstack: 3wr > OpenStack UX: 2wr > RpmPackaging: 1fb***, 1wr > App catalog: 1fb, 2wr > Packaging-deb: 1fb***, 1wr > > *: shared meetup between Kuryr and Dragonflow > **: shared meetup between Infra and QA > ***: shared fishbowl between RPM packaging and DEB packaging, for collecting > wider packaging feedback > > We'll start working on laying out those sessions over the available > rooms and time slots. Most of you have communicated constraints together > with their room requests (like Manila not wanting overlap with Cinder > sessions), and we'll try to accommodate them the best we can. If you have > extra constraints you haven't communicated yet, please reply to me ASAP. If PuppetOpenStack and Infra could avoid overlaps, that would be awesome. Some people are working on both groups and to continue the best of our collaboration I would like to set this constraint. Thanks a lot, > Now is time to think about the content you'd like to cover during those > sessions and fire up those newton etherpads :) > > Cheers, > > -- > Thierry Carrez (ttx) > > __ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev -- Emilien Macchi __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [all] Newton Design Summit - Proposed slot allocation
It would be great if at least one Fuel slot did not overlap with Ironic sessions. Vladimir Kozhukalov On Fri, Mar 18, 2016 at 6:26 PM, Jeremy Stanley wrote: > On 2016-03-18 08:53:11 +0530 (+0530), Armando M. wrote: > > It's be nice if Neutron didn't overlap as much with Nova, Ironic, QA and > > infra sessions, but I appreciate this could be a tall order. > > It seems like every project wants to avoid overlap with Infra > sessions, so I'm not sure it will be easy to accommodate since we > have to have our sessions _sometime_. However, we do usually try to > make sure we have scouts in any Infra-relevant sessions for other > teams, so give us a heads up on which ones those are and we will try > to get someone to volunteer to sit in if we're not already spread > too thin. > -- > Jeremy Stanley > > __ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev