Thanks for the additional notes, Thierry! On 10/6/16, 12:53 AM, "Thierry Carrez" <[email protected]> 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: > >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 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. > >+Pro: PTGs are organized in cheaper locations and closer to the center >of mass of contributors, hopefully making it less costly to travel to >overall >+Pro: More team time (for Congress: 2-3 days instead 2-3 hours) for a >better return on travel investment > >> 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 > >+Con: extra travel for those who will continue to attend summit > >-- >Thierry Carrez (ttx) > >__________________________________________________________________________ >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
