Open Stack

On Mon, Feb 8, 2016 at 6:26 AM, Thierry Carrez <thierry at openstack.org>
wrote:

> Daniel P. Berrange wrote:
>
>> [...]
>> I really agree with everything you say, except for the bit about the
>> community doing organization - I think its fine to let function event
>> staff continue with the burden of planning, as long as their goals are
>> directed by the community needs.
>>
>
> Exactly.
>
> I might suggest that we could be a bit more radical with the developer
>> event and decouple the timing from the release cycle. The design summits
>> are portrayed as events where we plan the next 6 months of work, but the
>> release has already been open for a good 2-3 or more weeks before we meet
>> in the design summit. This always makes the first month of each
>> development
>> cycle pretty inefficient as decisions are needlessly postponed until the
>> summit. The bulk of specs approval then doesn't happen until after the
>> summit, leaving even less time until feature freeze to get the work done.
>>
>
> I agree that the developer event happens too late in the cycle (3 weeks
> after final release, 5 weeks after RC1 where most people switch to next
> cycle, and 8 weeks after FF, where we start thinking about the next cycle).
> That said, I still think the dev event should be "coupled" with the cycles.
> It just needs to happen earlier.
>
> --
> 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
>


The OpenStack Summit is a great thing as it is now. It creates big
momentum, it's a strong motivator for the engineers (as enjoy our time
there) and the Companies are happy too with the business related side. I
see it also as the most successful Team building activity, Community and
Company wide. For Companies, the costs to send engineers to the Summit or
to a dedicated Design event are exactly the same. Besides, many Companies
send US based employees only to the US Summit, and EU based only to the
other side. The OpenStack Summit is probably the most advanced and
successful OpenSource event, if you take out of it the engineering side, it
won't be the same.

I think, the issue here is that we need to have a better and more
productive way to work together. Probably the motivation behind a separate
design summit and also this discussion is focused to improve that, as we
see that face to face is effective. Maybe this is the limitation we need to
resolve, rather than changing an amazing event.

Thanks,
Fausto
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20160208/242fdae0/attachment.html>