[openstack-dev] [all] A proposal to separate the design summit
lauren at openstack.org
Mon Feb 22 17:15:38 UTC 2016
> On Feb 22, 2016, at 8:52 AM, Clayton O'Neill <clayton at oneill.net> wrote:
> I think this is a great proposal, but like Matt I’m curious how it
> might impact the operator sessions that have been part of the Design
> Summit and the Operators Mid-Cycle.
> As an operator I got a lot out of the cross-project designs sessions
> in Tokyo, but they were scheduled at the same time as the Operator
> sessions. On the other hand, the work sessions clearly aren’t as
> useful to me. It would be nice would be worked out so that the new
> design summit replacement was in the same location, and scheduled so
> that the operator specific parts were overlapping the work sessions
> instead of the more big picture sessions.
Great question. The current plan is to maintain the ops summit and mid-cycle activities.
The new format would allow us to reduce overlap between ops summit and cross project sessions at the main event, both for the operators and developers who want to be involved in either activity.
> On Mon, Feb 22, 2016 at 11:32 AM, Matt Fischer <matt at mattfischer.com> wrote:
>> Cross-post to openstack-operators...
>> As an operator, there's value in me attending some of the design summit
>> sessions to provide feedback and guidance. But I don't really need to be in
>> the room for a week discussing minutiae of implementations. So I probably
>> can't justify 2 extra trips just to give a few hours of feedback/discussion.
>> If this is indeed the case for some other folks we'll need to do a good job
>> of collecting operator feedback at the operator sessions (perhaps hopefully
>> with reps from each major project?). We don't want projects operating in a
>> vacuum when it comes to major decisions.
>> Also where do the current operators design sessions and operators midcycle
>> fit in here?
>> (apologies for not replying directly to the first message, gmail seems to
>> have lost it).
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
More information about the OpenStack-dev