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 those who will continue to attend summit. 2. Unofficial work session at summits; no work sessions at PTGs. Pro: For people who would be going to the summits anyway, this option reduces travel. Con: probably no official work room available. Con: happens at the middle of a dev cycle 3. Separately organize work sessions in the style of past mid-cycle sprints; no work sessions at any of the official openstack events. Pro: we can choose schedule and location Con: harder to collaborate with other teams 4. No work sessions at all. On 10/5/16, 4:18 PM, "Eric K" <ekcs.openst...@gmail.com> wrote: >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 team, we are asked to decide whether we want to have work sessions at >the upcoming PTG in in Atlanta (Feb 20-24) to kick-off the P-cycle. We¹re >asked to have a decision no later than Oct 16, so hopefully we can discuss >it over ML and the next couple meetings and come up with a decision. > >Some more details on the schedule at the first PTG: >> The first Project Teams Gathering will happen in Atlanta, Feb 20-24, >> 2017. We'll provide a separate room for every (non-single-vendor) >> project team that asks for one, and each team will be able to organize >> its own agenda (similar to what happens at mid-cycle sprints). > >> Horizontal teams (Infrastructure, Documentation, QA...) and >> cross-project workgroups will meet on Monday-Tuesday (Monday optional). >> Vertical teams (Nova, Cinder, Swift...) will meet on Wednesday-Friday >> (Friday optional). Teams that fall in between (Packaging, Kolla, >> Horizon...) might be placed with horizontal or vertical teams, depending >> on room availability. Attendees will be encouraged to pick one >> horizontal effort and one vertical team and attend the whole week, >> although they can of course opt to only attend a single team meeting. > > __________________________________________________________________________ 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