Re: [openstack-dev] [Congress] PTG planning

2016-10-14 Thread Eric K
Based on ML and IRC discussions and the feedback that almost all of us expect to be able to make the PTG, I have put down our team for work sessions at the PTG. I'm looking forward to interacting with more project teams in Atlanta. Thanks all! On 10/7/16, 3:24 AM, "Masahito MUROI"

Re: [openstack-dev] [Congress] PTG planning

2016-10-07 Thread Eric K
Thanks for the additional notes, Thierry! On 10/6/16, 12:53 AM, "Thierry Carrez" wrote: >Good summary. It is true that for small-to-medium sized teams (which did >not routinely organize midcycles), there is a tough choice to make. > >See a couple of remarks inline: >

Re: [openstack-dev] [Congress] PTG planning

2016-10-07 Thread Masahito MUROI
Thanks summarizing it, Eric. Combination of 1. and 2. looks good. Basically, we'll have work sessions in PTG for next release. Other teams and operator could come, so it's easy for Congress team to discuss anything with them. Then if needed, we can have unofficial work session of Congress

Re: [openstack-dev] [Congress] PTG planning

2016-10-06 Thread Thierry Carrez
Good summary. It is true that for small-to-medium sized teams (which did not routinely organize midcycles), there is a tough choice to make. See a couple of remarks inline: Eric K wrote: > Here are some of our choices as a team, as well as some first thoughts on > pros and cons: > > 1. Do work

Re: [openstack-dev] [Congress] PTG planning

2016-10-05 Thread Eric K
Here are some of our choices as a team, as well as some first thoughts on pros and cons: 1. Do work sessions at PTGs; no organized work sessions at summits. Pro: schedule lines up wit beginning of dev cycle Pro: work room available Pro: easy to collaborate with other teams Con: extra travel for

[openstack-dev] [Congress] PTG planning

2016-10-05 Thread Eric K
Hi all, As you know, the traditional design summit will be split into the work sessions at PTGs and the community forums at the summits. The release schedules will be re-aligned so that the PTGs coincide with the beginning of the dev cycle for each release. http://www.openstack.org/ptg As a