[openstack-dev] [all] A proposal to separate the design summit

Jan Klare j.klare at cloudbau.de
Thu Feb 25 09:02:28 UTC 2016


Hi Qiming,

this sounds like a much more pragmatic and practical idea to me and it think just splitting the events into two not parallel parts, but keeping them in the same “week” would also solve most of the problems mentioned in this thread, but allow people to attend both summits without travelling twice as you mentioned. The main issue with this idea might be, that this will not reduce the costs of the Desing summit, but in my opinion neither will the completely splittet solution. Thanks for this suggestion.

Cheers,
Jan

> On 25 Feb 2016, at 09:13, Qiming Teng <tengqim at linux.vnet.ibm.com> wrote:
> 
> Hi, All,
> 
> After reading through all the +1's and -1's, we realized how difficult
> it is to come up with a proposal that makes everyone happy. When we are
> discussing this proposal with some other contributors, we came up with a
> proposal which is a little bit different. This idea could be very
> impractical, very naive, given that we don't know much about the huge
> efforts behind the scheduling, planning, coordination ... etc etc. So,
> please treat this as a random thought.
> 
> Maybe we can still have the Summit and the Design Summit colocated, but
> we can avoid the overlap that has been the source of many troubles. The
> idea is to have both events scheduled by the end of a release cycle. For
> example:
> 
> Week 1:
>  Wednesday-Friday: 3 days Summit.
>    * Primarily an event for marketing, sales, CTOs, architects,
>      operators, journalists, ...
>    * Contributors can decide whether they want to attend this.
>  Saturday-Sunday:
>    * Social activities: contributors meet-up, hang outs ...
> 
> Week 2:
>  Monday-Wednesday: 3 days Design Summit
>    * Primarily an event for developers.
>    * Operators can hold meetups during these days, or join project
>      design summits.
> 
> If you need to attend both events, you don't need two trips. Scheduling
> both events by the end of a release cycle can help gather more
> meaningful feedbacks, experiences or lessons from previous releases and
> ensure a better plan for the coming release.
> 
> If you want to attend just the main Summit or only the Design Summit,
> you can plan your trip accordingly.
> 
> Thoughts?
> 
> - Qiming
> 
> 
> __________________________________________________________________________
> 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




More information about the OpenStack-dev mailing list