*The future of Design Summits

"Design Summits" are a key moment in OpenStack development cycles where our development community gathers to brainstorm the next steps for our  project. It always happened more or less at the same time as the  traditional "Conference", without causing too much conflict, with the  key technical contributors mostly ignoring the conference to concentrate  on the 4-day design summit. 
 
However, with the explosive growth  of OpenStack and the success of the conference, it is a problem to  prevent our best technical resources from presenting and attending the  conference. We need to discuss ways to organize those events in the  future which would enable more participation from our technical  contributors. 
 
We'll also discuss the design summit format, how  we select sessions and schedule them, as well as needed evolutions on  the ODSREG application (summit.openstack.org).

(Session proposed by Thierry Carrez)

-------------------------------------------------------------------------------------
xt
Hot feedback from the crowd
	* Paper schedules are awesome, print them the day before if possible
	* Thanks Lauren !!
	* Physical separation -with armed guards- was quite efficient
	* Need whiteboard
	* Don't mind the second projector, but maybe just in selected rooms ?
	* "Meet the TC" could also have been useful on the DS side
	* Ideal room is square (amphitheater type) but hard to find
	* Pre-packaged swag bag (tshirts specifically!) (set t-shirt size when registering?)
	* Not only Red Bull, please
	* Option for split lunch location for design space, separated from convention floor - keep conversations going over lunch
	* Live Streaming (??)
	* Starting with plenaries first day worked well to avoid bored conferencegoers wandering into design sessions
	* Travel grants ?


Separate the Design Summit from the Conference
	* The problem
		* More PTLs talk at LinuxCon than at the OpenStack Summit
		* Conflicts and context switches for developers between the two sides of the event
		* A lot of key people will be stuck at Design Summit all 4 days so the best of our tech community is invisible at the OpenStack Summit
	* The solutions
		* (1) Same place, partial overlap
			* Make the conference Monday - Thursday and the design summit Tuesday - Friday
			* Leaves most of the problem unsolved (even if the "tech track" at the conference ends up on the Monday of the conference)
			* Creates potential overcrowding of the summit on the Friday
		* (2) Same place, separated days
			* Make the Design Summit Wednesday-Saturday the week before (in a less shiny space in the same city) and the conference Monday - Thursday
			* That's a loooong week
			* Need to make the summit ATC-only to avoid overcrowding (means we have to handle invitations for exceptions)
		* (3) Separate events
			* Make the Design Summit on a completely separate week and city, a few weeks/months away from the conference
			* More organizational costs (twice as many "events")
			* More travel expenses
				* Although you could argue that #2 is about as costly in accomodation
				* Although you could argue that a significant part of the devs would skip the "conference" when non-local
			* We could make the design summit in the US when the conference is in Europe/Asia
	* How much can we change in...
		* May 12-16, 2014 (Atlanta)
			* 5 days (conference on first 3 days and design summit on last 4 days ?)
			* Rob says: place the non-DS day on the Wednesday instead
		* October/November 2014 (Paris) - back to back option would be costly
			* Palais des Congrès (Paris intramuros, west side)
		* April/May 2015 (?) - when do you plan to freeze the plan ? ASAP

Design Summit format / scheduling
	* Rooms
		* Square rooms, fishbowl
		* One or two screens
		* Space for per-project "collaboration pods" to informally handle the extra sessions, unconference-style
		* One-day "cross-project" track ?
	* Slots, sessions, topics
		* Time for cross-project workshops (upgrades, API coherence, etc.) ?
		* Loose scheduling: Staggered layout vs. tagged sessions ?
		* Process for proposals, review and scheduling
		* Do we need to finish at 6pm?


Not being discussed:
The ODSREG application (summit.openstack.org)
	* Now with comments, and under openstack-infra
	* Fixes, improvements ?
	* Move to puppet