[openstack-dev] [all] Dublin PTG format
jeremyfreudberg at gmail.com
Mon Nov 27 22:03:25 UTC 2017
-1 from me.
If one is a big name in OpenStack and/or has fingers in many pies,
then moving away from the 2/3 split makes sense. That is to say, if
you have the capacity for lots of interests, and lots of people are
interested in you, then flexible scheduling allows all those interests
to get satisfied.
But not every PTG atendee is like that. For example, I myself am a
full-time undergraduate student, who's essentially only works on
OpenStack (mostly Sahara) in his free time. I was fortunate enough to
attend PTGs in Atlanta and in Denver. And one of the main reasons I
was able to attend was because the Sahara team events were laid out as
_two consecutive marathon days_. Thanks, 2/3 split. Horizontal and
"theme" stuff is fun (and important to many), but not everyone has the
luxury of tacking on two extra days of extra stuff. My assumption is
that others for whom OpenStack contributions are a hobby and not part
of one's job probably share this sentiment, that we need to get-in and
get-out as quickly as we can, and can only really devote time to our
I also share Jay's intuition that it will be harder to get focus out
of several half-days then a few whole-days. For Sahara (at least from
my own observation) certainly that would be only the way to get enough
focus that we can really regroup, reset, and take stock of what we
have moving forward to the next dev cycle. A half-day feels disjointed
enough that it might as well be remote.
On Mon, Nov 27, 2017 at 5:58 AM, Thierry Carrez <thierry at openstack.org> wrote:
> Hi everyone,
> We are in the final step in the process of signing the contract with the
> PTG venue. We should be able to announce the location this week !
> So it's time to start preparing. We'll have 5 days, like in Denver. One
> thing we'd like to change for this round is to give a bit more
> flexibility in the topics being discussed, especially in the first two days.
> In Denver, we selected a number of general "themes" and gave them all a
> room for 2 days on Monday-Tuesday. Then all the "teams" that wanted a
> project team meeting could get a room for 2 or 3 days on
> Wednesday-Friday. That resulted in a bit of flux during the first two
> days, with a lot of empty rooms as most of the themes did not really
> need 2 days, and a lot of conflicts were present.
> For Dublin, the idea would be to still predetermine topics (themes and
> teams) and assign them rooms in advance. But we would be able to assign
> smaller amounts of time (per half-day) based on the expressed needs.
> Beyond those pre-assigned themes/teams we'd add flexibility for other
> groups to book the remaining available rooms in 90-min slots on-demand.
> A bit like how we did reservable rooms in the past, but more integrated
> with the rest of the event. It would all be driven by the PTGbot, which
> would show which topic is being discussed in which room, in addition to
> the current discussion subject within each topic.
> We have two options in how we do the split for predetermined topics. We
> used to split the week between Mon-Tue (themes) and Wed-Fri (teams). The
> general idea there was to allow some people only interested in a team
> meeting to only attend the second part of the week. However most people
> attend all 5 days, and during event feedback some people suggested that
> "themes" should be in the mornings and "teams" in the afternoons (and
> all Friday).
> What would be your preference ? The Mon-Tue/Wed-Fri split means less
> room changes, which make it easier on the events team. So all else being
> equal we'd rather keep it the way it is, but I'm open to changing it if
> attendees think it's a good idea.
> If you have any other suggestion (that we could implement in the 3
> months we have between now and the event) please let me know :)
> Thierry Carrez (ttx)
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
More information about the OpenStack-dev