Open Stack

Folks,

Thanks for your input on the midcycle agenda at today’s meeting.  I’ve updated the tentative agenda to reflect most of the requests that were made today as well as to accommodate some folks we know will be joining us remotely.  The basic flow is now:

1.) We kick off with Scoring sessions on the morning of Day 1.  This is stuff we mostly know how to do now, but which absolutely needs doing since we have to produce a Guideline in a few months.  So we'll get the blocking and tackling done early and get our juices flowing.  Since these are preliminary discussions, this also means that if we have a few folks trickling in late due to travel arrangements, they’ll still have plenty of chances to make their voices heard later in the scoring process.

2.) Once Scoring is done, we move to Strategy sessions in the afternoon of Day 1.  These discussions are likely to be more intense and will inform much of our thinking for the remaining sessions in the midcycle, and the timeslot here is more friendly to some folks who’ve expressed an interest in joining us remotely.

3.) On the morning of Day 2, we kick of with sessions on Tests.  These conversations are likely to have been influenced by our Strategy discussions on the previous day, but we’ll have had an evening to mull over what we talked about (and/or what we continued to talk about over dinner).

4.) Sandwiching the lunch break (see what I did there?) on Day 2 we’ll have the RefStack sessions, since those should dovetail nicely with Tests.

5.) Following lunch on Day 2 we’ll conclude with the Outcomes sessions (as well as a wrap-up to review action items and some time for parking lot discussions).  

I’ve also dropped two sessions from the agenda: the "Publishing DefCore Information and Docs” session (which feels small enough that we could tackle it in any given weekly meeting or even with an ML discussion), and the “Strategy: Levels of Interoperability” session (because I think this will actually end up getting discussed in the “Value from DefCore” session anyway).  This gives us a little more flexibility in the schedule, although it’s still a pretty full agenda.  You’ll notice a few built-in “fudge time” sessions for each grouping, so we’ll have a little leeway if we need to run over on something or need to take a break.

Please review and let me know if there are any other suggestions before we finalize:

https://etherpad.openstack.org/p/DefCoreSpring2016MidCycle

See you in Austin!

At Your Service,

Mark T. Voelker