Open Stack

On 05/06/18 16:22, Jay S Bryant wrote:
> 
> 
> On 6/5/2018 7:31 AM, Sean McGinnis wrote:
>> On Tue, Jun 05, 2018 at 11:21:16AM +0200, Thierry Carrez wrote:
>>> Jay Pipes wrote:
>>>> On 06/04/2018 05:02 PM, Doug Hellmann wrote:
>>>>> [...]>
>>>> Personally, I've very much enjoyed the separate PTGs because I've
>>>> actually
>>>> been able to get work done at them; something that was much harder
>>>> when the
>>>> design summits were part of the overall conference.
>>> Right, the trick is to try to preserve that productivity while making it
>>> easier to travel to... One way would be to make sure the PTG remains a
>>> separate event (separate days, separate venues, separate registration),
>>> just co-located in same city and week.
>>>
>>>> [...]
>>>>> There are a few plans under consideration, and no firm decisions
>>>>> have been made, yet. We discussed a strawman proposal to combine
>>>>> the summit and PTG in April, in Denver, that would look much like
>>>>> our older Summit events (from the Folsom/Grizzly time frame) with
>>>>> a few days of conference and a few days of design summit, with some
>>>>> overlap in the middle of the week.  The dates, overlap, and
>>>>> arrangements will depend on venue availability.
>>>> Has the option of doing a single conference a year been addressed?
>>>> Seems
>>>> to me that we (the collective we) could save a lot of money not having
>>>> to put on multiple giant events per year and instead have one.
>>> Yes, the same strawman proposal included the idea of leveraging an
>>> existing international "OpenStack Day" event and raising its profile
>>> rather than organizing a full second summit every year. The second PTG
>>> of the year could then be kept as a separate event, or put next to that
>>> "upgraded" OpenStack Day.
>>>
>> I actually really like this idea. As things slow down, there just
>> aren't enough
>> of big splashy new things to announce every 6 months. I think it could
>> work
>> well to have one Summit a year, while using the OSD events as a way to
>> reach
>> those folks that can't make it to the one big event for the year due
>> to timing
>> or location.
>>
>> It could help concentrate efforts to have bigger goals ready by the
>> Summit and
>> keep things on a better cadence. And if we can still do a PTG-like
>> event along
>> side one of the OSD events, it would allow development to still get the
>> valuable face-to-face time that we've come to expect.
> I think going to one large summit event a year could be good with a
> co-located PTG type event.  I think, however, that we would still need
> to have a Separate PTG type event at some other point in the year.  I
> think it is going to be hard to keep development momentum going in the
> projects without a couple of face-to-face meetings a year.
> 

I personally think a single summit (with a PTG / Ops Mid Cycle before or
after) + a separate PTG / Ops Mid Cycle would be the best solution.

We don't need to rotate locations - while my airmiles balance has really
appreciated places like Tokyo / Sydney - we can just reuse locations.

For example saying that the week of May 20 something every year in
Vancouver[1] (or $NORTH_AMERICAN_CITY) is the OpenStack Summit + Kata +
OpenDev + Edge conference massively reduces planning / scouting.

Then having the PTG (or OpenStack Foundation Developer & Ops Team
Gathering to make any new groups feel as welcomed, and not "tacked on")
in Denver + $NON_NORTH_AMERICAN_CITY[2] (again, as static locations to
reduce planning / scouting) seems like a good idea.

1 - But lets just say Vancouver please :)

2 - not sure if this is actually a good idea, but I don't the same
    visa problems that some of our contributors do, or have knowledge
    of how tax write off work so if I am wrong please tell me.

>>> Thinking on this is still very much work in progress.
>>>
>>> -- 
>>> Thierry Carrez (ttx)
>>>
>> __________________________________________________________________________
>>
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe:
>> OpenStack-dev-request at 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-request at lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev