On Wed, Apr 8, 2015 at 1:22 AM, Edgar Magana <[email protected]> wrote:
> Kyle and Neutron Team, > > Having the mid-cyle just one month after the Liberty summit does not > really fit into the definition of “mid-cycle”. It feels like we are just > getting up to speed on Liberty BPs when we need to get ready for three days > of sprint coding. > Would you consider to move this at least one month after? > I really want to go but it feels to soon to request permission to my > management team. > > Thanks for your concerns Edgar. I guess you're right, and I will stop calling this a mid-cycle, and instead just refer to it as a the Neutron Liberty Coding Sprint. It's actually worked out really well to have it close to the first milestone, we have a lot of things we can do very early in the cycle, getting together and pushing towards the first milestone with some of them will work well. Like I indicated to Russell, we'll do our best to facilitate remote attendees over IRC and maybe Hangouts while we're there. Thanks! Kyle > Thanks, > > Edgar > > From: Kyle Mestery <[email protected]> > Reply-To: "OpenStack Development Mailing List (not for usage questions)" < > [email protected]> > Date: Tuesday, April 7, 2015 at 6:39 AM > To: "OpenStack Development Mailing List (not for usage questions)" < > [email protected]> > Subject: Re: [openstack-dev] [neutron] Liberty mid-cycle coding sprint > > On Tue, Apr 7, 2015 at 8:15 AM, Russell Bryant <[email protected]> > wrote: > >> On 04/07/2015 12:33 AM, Ben Pfaff wrote: >> > On Mon, Apr 06, 2015 at 03:00:17PM -0500, Kyle Mestery wrote: >> >> I know we're not even at the Liberty Design Summit in Vancouver yet, >> but I >> >> wanted to take this time to announce the Neutron mid-cycle coding >> sprint >> >> for Liberty. HP has been gracious enough to offer to host at it's Fort >> >> Collins, CO offices. The dates are set for June 24-26, this is >> >> Wednesday-Friday. I've got additional information on the etherpad [1]. >> >> >> >> We'll set the specific agenda in the coming weeks, but the idea is to >> focus >> >> on things like the pending neutron-lib work [2] while there, similar to >> >> what we did with the advanced services split in Utah last year. My >> >> experience running the past two mid-cycles has been that having these >> >> earlier in the cycle has been helpful for landing a lot of work near >> the >> >> first milestone of a release. I expect this to be the same for Liberty >> with >> >> the sprint in Fort Collins. >> >> >> >> Please note attendance is not required at all. We will do our best to >> >> facilitate virtual collaboration for those who cannot travel to the >> event. >> >> I wanted to get this out there for folks who have to book travel in >> advance. >> > >> > I don't know anything about these events. Naively: would OVN >> > development (some of which is in Neutron, much of which is not) be an >> > appropriate use of time at the event? >> >> Yes, I think putting OVN hacking on the agenda makes a lot of sense! > I'll add it to the etherpad now. > > >> I suspect so. FWIW, I'm not sure I'll be going, though. The dates >> aren't good for me. >> >> Bummer! But, as I said, we'll try our best to include remote people > into the coding sprint, so hopefully you can participate from afar. :) > > >> -- >> Russell Bryant >> >> __________________________________________________________________________ >> OpenStack Development Mailing List (not for usage questions) >> Unsubscribe: >> [email protected]?subject:unsubscribe >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >> > > > __________________________________________________________________________ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: [email protected]?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > >
__________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: [email protected]?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
