Is the expectation that the ops mid-cycle would continue separately, or be held with the meeting formerly known as the Design Summit?
Personally I’d prefer they be held together, but scheduled with the thought that operators aren’t likely to be interested in work sessions, but that a good number of us would be interested in cross-project and some project specific planning sessions. This would also open up the possibility of having some sessions specific intended for operator/developer feedback sessions. On Mon, Feb 22, 2016 at 12:15 PM, Lauren Sell <lau...@openstack.org> wrote: > >> On Feb 22, 2016, at 8:52 AM, Clayton O'Neill <clay...@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. __________________________________________________________________________ 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
