<div dir="ltr"><br><div class="gmail_extra"><br><br><div class="gmail_quote">On Wed, Aug 27, 2014 at 7:51 AM, Thierry Carrez <span dir="ltr"><<a href="mailto:thierry@openstack.org" target="_blank">thierry@openstack.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi everyone,<br>
<br>
I've been thinking about what changes we can bring to the Design Summit<br>
format to make it more productive. I've heard the feedback from the<br>
mid-cycle meetups and would like to apply some of those ideas for Paris,<br>
within the constraints we have (already booked space and time). Here is<br>
something we could do:<br>
<br>
Day 1. Cross-project sessions / incubated projects / other projects<br>
<br>
I think that worked well last time. 3 parallel rooms where we can<br>
address top cross-project questions, discuss the results of the various<br>
experiments we conducted during juno. Don't hesitate to schedule 2 slots<br>
for discussions, so that we have time to come to the bottom of those<br>
issues. Incubated projects (and maybe "other" projects, if space allows)<br>
occupy the remaining space on day 1, and could occupy "pods" on the<br>
other days.<br>
<br></blockquote><div><br></div><div>Yep, I think this works in theory, the tough part will be when all the incubating projects realize they're sending people for a single day? Maybe it'll work out differently than I think though. It means fitting ironic, barbican, designate, manila, marconi in a day? </div>
<div><br></div><div>Also since QA, Infra, and Docs are cross-project AND Programs, where do they land?</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Day 2 and Day 3. Scheduled sessions for various programs<br>
<br>
That's our traditional scheduled space. We'll have a 33% less slots<br>
available. So, rather than trying to cover all the scope, the idea would<br>
be to focus those sessions on specific issues which really require<br>
face-to-face discussion (which can't be solved on the ML or using spec<br>
discussion) *or* require a lot of user feedback. That way, appearing in<br>
the general schedule is very helpful. This will require us to be a lot<br>
stricter on what we accept there and what we don't -- we won't have<br>
space for courtesy sessions anymore, and traditional/unnecessary<br>
sessions (like my traditional "release schedule" one) should just move<br>
to the mailing-list.<br></blockquote><div><br></div><div>I like thinking about what we can move to the mailing lists. Nice. </div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
Day 4. Contributors meetups<br>
<br>
On the last day, we could try to split the space so that we can conduct<br>
parallel midcycle-meetup-like contributors gatherings, with no time<br>
boundaries and an open agenda. Large projects could get a full day,<br>
smaller projects would get half a day (but could continue the discussion<br>
in a local bar). Ideally that meetup would end with some alignment on<br>
release goals, but the idea is to make the best of that time together to<br>
solve the issues you have. Friday would finish with the design summit<br>
feedback session, for those who are still around.<br>
<br></blockquote><div><br></div><div>Sounds good.</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
I think this proposal makes the best use of our setup: discuss clear<br>
cross-project issues, address key specific topics which need<br>
face-to-face time and broader attendance, then try to replicate the<br>
success of midcycle meetup-like open unscheduled time to discuss<br>
whatever is hot at this point.<br>
<br>
There are still details to work out (is it possible split the space,<br>
should we use the usual design summit CFP website to organize the<br>
"scheduled" time...), but I would first like to have your feedback on<br>
this format. Also if you have alternative proposals that would make a<br>
better use of our 4 days, let me know.<br>
<br>
Cheers,<br>
<span class="HOEnZb"><font color="#888888"><br>
--<br>
Thierry Carrez (ttx)<br>
<br>
_______________________________________________<br>
OpenStack-dev mailing list<br>
<a href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
</font></span></blockquote></div><br></div></div>