On Fri, May 23, 2014 at 8:58 AM, Stephen Gallagher
<stephen(a)gallagherhome.com> wrote:
On 05/22/2014 08:05 PM, Tom Callaway wrote:
> Thanks to everyone for giving our schedule a good look, you caught
> several bugs, and we've fixed them. Here is the revised schedule.
>
> A few more items:
>
> * Please do not request to add any additional speakers to your talks.
> We're stretching our subsidy budget very thin as is. (Jaromir, I added
> Petr Kovar to yours, but he will be the last.)
>
> * We'll be going through and reaching out to each of you who requested
> travel or hotel subsidy individually. If you want to try to figure out
> what you think is a nice affordable flight for you, that would be nice.
> Don't book it, just find the details and save it for when we email you.
> Please be patient with us and realize that we have a lot of people to
> pay for.
>
> * If you've asked for hotel subsidy, you need to be sharing that hotel
> room to help us keep costs down. Find a roommate (ideally another
> speaker, but another Flock attendee who needs a room is fine). If you've
> found one already, please send us that information.
>
> * This is your _last_ chance to point out issues in the schedule. We'll
> be making it live tomorrow.
>
The schedule looks good except for one thing: the Fedora.next joint
session was scheduled for one hour. It would be ideal if it could be
extended by at least an additional half-hour (possible to eat into
lunch, maybe? Pardon the pun).
Running over is why it's right before lunch indeed.
The format of that talk is going to be a three-part event: an
overview
of Fedora.next, a status update from the individual working groups and
then a Q&A session. I think one hour is a bit tight for the amount of
material we need to cover.
Server, Workstation, and Env & Stacks all have their own sessions.
There's also a Fedora.next advocating talk, a governance workshop, a
talk about Fedora.next and Spins, and an F22 Fedora.next session. We
already have a LOT of Fedora.next content. Repeating a bunch of
content that is already split out into separate sessions isn't a good
use of anyone's time. Make your overviews and updates in the joint
session short and it should be doable within an hour or a bit over.
josh