Re: [openstack-dev] [all] Dublin PTG format

[Frank Kloeker]

Am 2017-11-27 11:58, schrieb Thierry Carrez:
[...]

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 :)


Hi Thierry,

I'd like the idea about themes and teams. Themes bring the opportunity 
to learn work methods and learn ways of working together, across 
OpenStack project teams and new people who are interested. There are so 
many things to learn from the OpenStack community like documentation, 
code review, code testing, automation, project work. This is the chance 
to prove the 4 O's and to give a platform for it.
Call it Summit 2.0. For 2 days, people who are not members of any 
project team but who are interested in their work or in the workings of 
the OpenStack community.
The other 3 days are really for project team work. I think 2 days would 
be also enough plus 1 day cross-project team work.
I'm not sure if I explained that correctly. I learned so much about 
working methods in the community. I think there may be more people 
proving it and maybe new enthusiastically people are joining in.


These are my thoughts about themes and teams :)

kind regards

Frank (@eumel8)

__
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

Re: [openstack-dev] [all] Dublin PTG format

[Dmitry Tantsur]

On 11/27/2017 11:58 AM, Thierry Carrez 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).


I'm not sure about "most people", I guess you're more informed than me :) I used 
to be on board with "let us make more people attend by stretching the teams 
part" previously. But after seeing actual budget problems, I started to think 
that allowing people to travel only for 3 days is a feature.


Side note: I expect a substantial share of people, especially from Europe, to 
arrive on Monday morning and leave on Friday evening.




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.


I'm kind of +0 on experimenting with it, taking into account what I mentioned 
above.



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 :)




__
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

Re: [openstack-dev] [all] Dublin PTG format

[Jean-Philippe Evrard]

On 29 November 2017 at 03:20, Masayuki Igawa  wrote:
> On 11/28, Ghanshyam Mann wrote:
>> Mon-Tue/Wed-Fri works as most suitable format. There are always
>> conflict for many of us but that can be adjusted by working with team
>> planning.
>>
>> Another thing can help is to give flexibility to team to have team
>> topic even on Mon-Tue, which mean team need dedicated room on Mon-Tue
>> also. For example, if QA want to discuss few of the topic on Mon-Tue
>> and have Code sprint/Help room etc on rest of week. This can help me
>> or other QA members to join other team discussion on Wed-Fri. But that
>> is based on special request and team requirement of number of topics
>> to discuss.
>>
>> morning/afternoon format will be little hectic and less productive due
>> to changing rooms and topic etc, at least for me :)
>
> Yeah, I totally agree with that. Regarding to the QA team members,
> most of members are not dedicated to the upstream work. So, if we can
> concentrate on it during the rest of 3 days, the days could be really
> productive. And I felt it in the past PTG.
>
> -- Masayuki
>
>
>>
>> -gmann
>>
>>
>> On Mon, Nov 27, 2017 at 7:58 PM, Thierry Carrez  
>> 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-requ...@lists.openstack.org?subject:unsubscribe
>> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>> __
>> 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
>
> --
>
> __
> 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
>

I like the 2+3 days format. I'd prefer that to fragmenting. If people
want to roam around they are free.
On top of that PTG bot is a helper to find what's going to happen next.

I heard once (ok, maybe more than once): "If it ain't broke, don't fix it"!

Best regards,
JP

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: 

Re: [openstack-dev] [all] Dublin PTG format

[Masayuki Igawa]

On 11/28, Ghanshyam Mann wrote:
> Mon-Tue/Wed-Fri works as most suitable format. There are always
> conflict for many of us but that can be adjusted by working with team
> planning.
> 
> Another thing can help is to give flexibility to team to have team
> topic even on Mon-Tue, which mean team need dedicated room on Mon-Tue
> also. For example, if QA want to discuss few of the topic on Mon-Tue
> and have Code sprint/Help room etc on rest of week. This can help me
> or other QA members to join other team discussion on Wed-Fri. But that
> is based on special request and team requirement of number of topics
> to discuss.
> 
> morning/afternoon format will be little hectic and less productive due
> to changing rooms and topic etc, at least for me :)

Yeah, I totally agree with that. Regarding to the QA team members,
most of members are not dedicated to the upstream work. So, if we can
concentrate on it during the rest of 3 days, the days could be really
productive. And I felt it in the past PTG.

-- Masayuki


> 
> -gmann
> 
> 
> On Mon, Nov 27, 2017 at 7:58 PM, Thierry Carrez  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-requ...@lists.openstack.org?subject:unsubscribe
> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> 
> __
> 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

-- 


signature.asc
Description: PGP signature
__
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

Re: [openstack-dev] [all] Dublin PTG format

[Matt Riedemann]

On 11/28/2017 3:46 AM, Chris Dent wrote:

On Tue, 28 Nov 2017, Flavio Percoco wrote:

Others have raised concerns about being able to properly keep the 
momentum of

the day going if we adopt the new format. I have to admit that I'm also
concerned about this. Switching context every half day may not be ideal.


This is the real crux of the biscuit. For team oriented work being
able to get into the nova-zone (or whatever) for an extended period
is important. Having to switch in and out of that per day would not
be pleasant and would also make the time less effective.

At base, I think part of the challenge with how we manage this stuff
is that because the available time is such a scarce resource (10
days out of 365) we want to make sure we touch upon everything that
matters. But bouncing from topic to topic means that each topic and
the people involved do not get the depth of engagement for it to
really matter. In the end what matters is not so much that we talk
about any particular topic, but that we talk about any topic, so
that we develop the shared language that allows us to talk about it
more later.

Which is just a long-winded way of saying: Let's not parcel time
into small chunks.



Agree with Chris. And stepping back, the more things get split up and 
time sliced, the more the PTG becomes like a summit with a very rigid 
schedule - which is something teams were trying very hard to get away 
from when we started doing midcycle meetups. The 2-3 days of just 
focusing on a few set of things at a deep level to move forward was 
necessary because 40 minutes every 6 months doesn't cut it.


--

Thanks,

Matt

__
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

Re: [openstack-dev] [all] Dublin PTG format

[Davanum Srinivas]

On Tue, Nov 28, 2017 at 4:46 AM, Chris Dent  wrote:
> On Tue, 28 Nov 2017, Flavio Percoco wrote:
>
>> Others have raised concerns about being able to properly keep the momentum
>> of
>> the day going if we adopt the new format. I have to admit that I'm also
>> concerned about this. Switching context every half day may not be ideal.
>
>
> This is the real crux of the biscuit. For team oriented work being
> able to get into the nova-zone (or whatever) for an extended period
> is important. Having to switch in and out of that per day would not
> be pleasant and would also make the time less effective.
>
> At base, I think part of the challenge with how we manage this stuff
> is that because the available time is such a scarce resource (10
> days out of 365) we want to make sure we touch upon everything that
> matters. But bouncing from topic to topic means that each topic and
> the people involved do not get the depth of engagement for it to
> really matter. In the end what matters is not so much that we talk
> about any particular topic, but that we talk about any topic, so
> that we develop the shared language that allows us to talk about it
> more later.
>
> Which is just a long-winded way of saying: Let's not parcel time
> into small chunks.

+1 to " Let's not parcel time into small chunks."

> --
> Chris Dent  (⊙＿⊙') https://anticdent.org/
> freenode: cdent tw: @anticdent
> __
> 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
>



-- 
Davanum Srinivas :: https://twitter.com/dims

__
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

Re: [openstack-dev] [all] Dublin PTG format

[Chris Dent]

On Tue, 28 Nov 2017, Flavio Percoco wrote:


Others have raised concerns about being able to properly keep the momentum of
the day going if we adopt the new format. I have to admit that I'm also
concerned about this. Switching context every half day may not be ideal.


This is the real crux of the biscuit. For team oriented work being
able to get into the nova-zone (or whatever) for an extended period
is important. Having to switch in and out of that per day would not
be pleasant and would also make the time less effective.

At base, I think part of the challenge with how we manage this stuff
is that because the available time is such a scarce resource (10
days out of 365) we want to make sure we touch upon everything that
matters. But bouncing from topic to topic means that each topic and
the people involved do not get the depth of engagement for it to
really matter. In the end what matters is not so much that we talk
about any particular topic, but that we talk about any topic, so
that we develop the shared language that allows us to talk about it
more later.

Which is just a long-winded way of saying: Let's not parcel time
into small chunks.

--
Chris Dent  (⊙＿⊙') https://anticdent.org/
freenode: cdent tw: @anticdent__
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

Re: [openstack-dev] [all] Dublin PTG format

[Flavio Percoco]

On 27/11/17 14:21 -0500, Doug Hellmann wrote:

Excerpts from Thierry Carrez's message of 2017-11-27 11:58:04 +0100:

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 :)



What sort of options do we have for trying the new morning/afternoon
split approach without increasing the burden on the events team?

Can we print the signs so they have both the project team names and
a theme listed on the same sign so we can avoid changing them at
all?

Can we have the project teams or theme room organizers manage their
own signs, placing them in prepared holders outside of the rooms?


Regardless of the format, I think we can experiment with something like this.
It will give teams more flexibility.


Or do we need signs at all? The rooms all have names or numbers
already right?


Or this!

Flavio

--
@flaper87
Flavio Percoco


signature.asc
Description: PGP signature
__
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

Re: [openstack-dev] [all] Dublin PTG format

[Flavio Percoco]

On 27/11/17 11:58 +0100, Thierry Carrez 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).


If most of the people attend the full week, then I would argue that the format
we used in Denver is the one that will bring more people together, People
interested in attending the full PTG and those interested only in team
discussions will participate.

If we change the format, there's a risk that we'll exclude folks only interested
in team specific rooms as it'll likely increase their travel expense and travel
time.

If we were to adopt this new format, we could work on making sure that team
discussions happen in consecutive days to avoid teams like Sahara to have
sessions on Monday afternoon and then Thursday afternoon. However, I doubt this
will work well for everyone interested only in team discussions.


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.


Others have raised concerns about being able to properly keep the momentum of
the day going if we adopt the new format. I have to admit that I'm also
concerned about this. Switching context every half day may not be ideal.


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 :)


My suggestion is to keep it as-is. This is our 3rd PTG and the first one outside
the U.S. I would prefer us to gather some extra data and feedback before we do
any drastic change to the format of the event.

Flavio

--
@flaper87
Flavio Percoco


signature.asc
Description: PGP signature
__
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

Re: [openstack-dev] [all] Dublin PTG format

[Ghanshyam Mann]

Mon-Tue/Wed-Fri works as most suitable format. There are always
conflict for many of us but that can be adjusted by working with team
planning.

Another thing can help is to give flexibility to team to have team
topic even on Mon-Tue, which mean team need dedicated room on Mon-Tue
also. For example, if QA want to discuss few of the topic on Mon-Tue
and have Code sprint/Help room etc on rest of week. This can help me
or other QA members to join other team discussion on Wed-Fri. But that
is based on special request and team requirement of number of topics
to discuss.

morning/afternoon format will be little hectic and less productive due
to changing rooms and topic etc, at least for me :)

-gmann


On Mon, Nov 27, 2017 at 7:58 PM, Thierry Carrez  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-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

__
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

Re: [openstack-dev] [all] Dublin PTG format

[Jeremy Freudberg]

-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
main project.


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  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-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

__
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

Re: [openstack-dev] [all] Dublin PTG format

[Sean McGinnis]

> 
> What sort of options do we have for trying the new morning/afternoon
> split approach without increasing the burden on the events team?
> 
> Can we print the signs so they have both the project team names and
> a theme listed on the same sign so we can avoid changing them at
> all?
> 

RaspberryPi powered displays that automatically pull data from the PTG bot?


__
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

Re: [openstack-dev] [all] Dublin PTG format

[Colleen Murphy]

On Mon, Nov 27, 2017 at 11:58 AM, Thierry Carrez  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)

I felt like the 2/3 day split worked well for the discussions I
participated in. We were able to come up with ideas and common
understanding in cross-project discussions on the first two days, and
then solidify a plan to implement those ideas within the team during
the last three days. The colocation of the project teams in the last
three days allowed us to pull other people in if we needed to revisit
something from the first two days. I'm not sure that changing the
split is solving a problem that we have.

Colleen

__
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

Re: [openstack-dev] [all] Dublin PTG format

[Jay Bryant]

Thierry,

I have been happy with the current 2 day/3 day split.  I am concerned that
I would have a harder time getting focus from the project team splitting
across multiple half days.  That is just my hunch.

Jay

On Mon, Nov 27, 2017, 1:21 PM Doug Hellmann  wrote:

> Excerpts from Thierry Carrez's message of 2017-11-27 11:58:04 +0100:
> > 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 :)
> >
>
> What sort of options do we have for trying the new morning/afternoon
> split approach without increasing the burden on the events team?
>
> Can we print the signs so they have both the project team names and
> a theme listed on the same sign so we can avoid changing them at
> all?
>
> Can we have the project teams or theme room organizers manage their
> own signs, placing them in prepared holders outside of the rooms?
>
> Or do we need signs at all? The rooms all have names or numbers
> already right?
>
> Doug
>
> __
> 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
>
__
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

Re: [openstack-dev] [all] Dublin PTG format

[Doug Hellmann]

Excerpts from Thierry Carrez's message of 2017-11-27 11:58:04 +0100:
> 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 :)
> 

What sort of options do we have for trying the new morning/afternoon
split approach without increasing the burden on the events team?

Can we print the signs so they have both the project team names and
a theme listed on the same sign so we can avoid changing them at
all?

Can we have the project teams or theme room organizers manage their
own signs, placing them in prepared holders outside of the rooms?

Or do we need signs at all? The rooms all have names or numbers
already right?

Doug

__
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

[openstack-dev] [all] Dublin PTG format

[Thierry Carrez]

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-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev