----- Original Message -----
From: "Tom Callaway" tcallawa@redhat.com To: "Planning discussion for Flock (Fedora Contributor Conference)" flock-planning@lists.fedoraproject.org Sent: Saturday, June 1, 2013 7:55:36 PM Subject: Re: Keynotes
On 05/30/2013 07:47 AM, Jaroslav Reznik wrote:
I really like this idea - better than keynote. Especially if you realize when talking to people being at FUDCon that on that FUDCon we talked/decided X and they are - "Really? Wow, I didn't know. When? Who?". So recap in the morning for everyone to be on the same board and allow people to potentially join the upcoming discussion - worth $1 billion!
I've been brainstorming on this idea... here are some thoughts about it:
- We could have a 30 minute recap session first thing in the morning
(except for the first day).
- In order for that to happen, we'd need willing volunteers to gather
all that information together, summarize it into the recap, and then present it the next day. Anyone doing that is probably not going to be able to do much else.
- We would be able to keep morning keynotes.
Very interested in other thoughts here.
So after doing a bit more research, here are my thoughts:
We have a number of "categories" - most of them are projects of some sort, some with more levels of complication/detail to share than others, I suspect.
We might consider the following:
* Having a lead/owner for each track/category that has feedback into the schedule (likely a bit in consensus with the folks on those teams/groups/SIGs) * Trying to arrange those sessions maybe in blocks of 2 days (??? this gets murky here...) - so that folks who are likely needing to do double duty in multiple groups aren't missing half the things they are interested in, or can at least participate equally if they overlap. ie: Docs/Trans probably wouldn't want to overlap, nor Ambassadors/Trans; QA/releng/infra may need some major wrangling, etc. * Having summary sessions in the evening or morning - perhaps rather than having the "5 minute update" - give people 5-20 minutes (depending on group, how much they expect to be covering in terms of "things everyone else should be aware of") to basically cover: ** State of Team/Group/SIG ** Major topics covered during Flock ** Feedback/concerns ** What their roadmap for next 1, 2, 3, whatever they want to commit to in terms of releases looks like. Basically: What have you decided to plan on?
I don't think this should be unduly terribly hard - this is what the folks in openstack-land do - just *one* summary session. (The way they do it though is on the last day, in each hour slot of time there is *one* session covering *one* project's/team's summary session - but other regular sessions running in the same time slot, just hopefully not horrifically overlapping).
I would suggest that each group have their own running etherpad(s) - so that the burden isn't ridiculous for the track organizer/owner - we don't need people making pretty slides all night long (or all day long) - just a basic recap of what went on, what the state of the project is, etc.
I guess I haven't narrowed it down much - we could either (or both, even) do longer recap sessions (which would be awesome for taping, BTW) - as well as mini-recaps in the morning. Or we might just ask around which tracks expect that they'll have major agreements/progress to be reporting out on that might want a longer slot to share info at the end, and otherwise just do the mini-morning updates each day.
-r
~tom
== Fedora Project _______________________________________________ flock-planning mailing list flock-planning@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/flock-planning