Re: Schedule Decision Process
Hi
2013/4/30 Tom Callaway <tcallawa(a)redhat.com>
Here is the proposal I'd like to put forth for determining the
Flock
Schedule.
* We form a "conference committee" which includes:
- Ruth, Robyn, and Myself
- One appointed member from each:
- Fedora Board
- FESCo
- FAMSco
* We open the call for talks (and for scheduled 2hr
hackfests/sprints/workshops), and collect titles and abstracts. Everyone
submits talks, as many as they're willing to give.
* When the call is closed, we take the titles and abstracts, anonymized,
and put them into the Fedora elections app. All CLA+1 contributors can
vote a score of 0-10 for each proposed talk/hackfest/sprint/workshop. We
leave this open for an announced window of time.
* When voting is done, the conference committee will review the results
and determine the final approved talks. They will see the un-anonymized
submissions. They will also reach out to Sponsors who donated at Gold or
above and requested a guaranteed talk on the schedule and confirm their
choice. In the case of Red Hat, they are guaranteed three slots, due to
the large amount of money being spent.
* The committee will reserve the "morning, before lunch" times for 45
minute talks, and "after lunch" times for 2 sprints/hackfests/workshops
in each room, unless we don't have enough good fits for the entire
schedule, then we'll adjust as necessary. We'll also have a slotted time
for lightning talks (they will not need to be submitted beforehand, we
will collect them at Flock).
* They will announce the finalized schedule (un-anonymized) and put it
on the Flock website.
thoughts?
mmh, interested what you want to use for the voting
br gnokii
~tom
==
Fedora Project
_______________________________________________
flock-planning mailing list
flock-planning(a)lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/flock-planning
--
make me rich, buy my Inkscape book http://is.gd/yq5OD0 ;)
Attachments:
- attachment.html (text/html — 2.7 KB)