Ben Swartzlander wrote: > On 03/09/2017 12:10 PM, Jonathan Bryce wrote: >> Putting that aside, I appreciate your providing your input. The most >> consistent piece of feedback we received was around scheduling and >> visibility for sessions, so I think that is definitely an area for >> improvement at the next PTG. I heard mixed feedback on whether the >> ability to participate in multiple projects was better or worse than >> under the previous model, but understanding common conflicts ahead of >> time might give us a chance to schedule in a way that makes the >> multi-project work more possible. Did you participate in both Cinder >> and Manila mid-cycles in addition to the Design Summit sessions >> previously? Trying to understand which types of specific interactions >> you’re now less able to participate in. > > Yes in the past I was able to attend all of the Manila and most of the > Cinder sessions at the Design summit, and I was able to attend the > Cinder midcycles in person and (since I'm the PTL) I was able to > schedule the Manila midcycles to not conflict.
On that particular bit of feedback ("making it impossible to participate in 2 or more vertical projects") it is feedback that I definitely heard :) While the event structure made it generally a lot easier to tap into other teams (and a *lot* of them did just that), the horizontal/vertical split definitely made it more difficult for Manila folks to attend all Cinder sessions, or for Storlets folks to attend all Swift sessions. On a personal note, it made it more difficult for *me* to attend all Architecture WG and Stewardship workgroup and Release Team and Infra sessions, which were all going on at the same time on Monday/Tuesday. So it's not something that only affected vertical projects. We can definitely improve on that, and come up with a more... creative way to split usage of rooms than a pretty-arbitrary grouping of projects into "vertical" and "horizontal" groups. There is no miracle solution (there will always be someone needing to be in two places at the same time), but the strawman split we tried for the first one is certainly not the optimal solution. If you have suggestions on how we can better map room/days, I'm all ears. I was thinking about taking input on major team overlaps (like the one you pointed to between Manila and Cinder) as a first step, and try to come up with a magic formula that would minimize conflicts. -- 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