Of course Flock will have the usual State of Fedora FPL keynote, but I
think it would be great to have other keynotes each day of Flock as well.
Any suggestions on whom we should approach (even better if you know them!)?
The call for submissions for Flock talks/workshops/hackfests/sprints is
ending tonight at midnight Eastern time. I figured I'd highlight the
* The web app will stop taking new submissions at the deadline.
* We will export the anonymized submissions out of the web app and
import them into the Elections (Voting) app.
* We will open the election for a week (7 days), announce it widely, let
everyone who has a FAS account with FPCA (CLA) signed to vote on each
proposal. Range voting of 0-10 for each talk.
* People who have pre-registered for Flock will get a direct email
asking them to vote. (Registration will remain open).
* When voting closes, the scheduling committee will meet to make the
final schedule (and do it as fast as we can).
* We will then publish the schedule and notify the speakers of their
acceptance. Any speakers who need financial subsidy will have it handled
at this point.
* All other subsidies will be handled after the speakers are taken care
of, money permitting.
* We will continue to attempt to lock in Sponsors.
* We will start having weekly public IRC planning meetings at 14:00 UTC
(10 AM Eastern Time) on Wednesday to cover these (and the other details).
Hi, can someone let me know: Is there a designated liaison from C of C's IT
group to Flock or from Flock to C of C? I'd like to get in contact with
those people. I want to be sure certain dots are connected, so to speak,
and to share a few lessons learned at a recent Bar Camp held here at C of C.
-- Garrett Mitchener, associate professor of mathematics, College of
I'm interested in what people think about this.
Right now, when you submit a proposal for a talk (or hackfest/workshop),
the title and abstract are made public, but the identify of the speaker
The intent was to try to remove bias on voting for the speaker as
opposed to the topic, but several people have disagreed with that intent.
Should we make the name of the proposed presenter public as well? (Note
that the selection committee was always going to be able to see the full
data including presenter names).
If you could take one second to click "reply" and say whether you think
you'll stay through the night of the 12th or take a late flight out that
day, it would help me get an idea to finish making the room blocks today. I
don't want to overbook us.
Tom Callaway píše v Čt 09. 05. 2013 v 12:03 -0400:
> Hello Ambassadors (and FAmSCo)!
> Hopefully by now, you have heard about Flock, the new Fedora contributor
> conference in Charleston, SC, USA (August 9 - 12, 2013).
> I wanted to extend a personal invitation to all Fedora ambassadors to
> attend Flock. Each and every one of you represents the heart and soul of
> the Fedora Community. We will have some funding available to cover
> travel and lodging costs, but priority will be given to those who are
> accepted to speak (or lead a workshop, hackfest/sprint), so please,
> consider submitting a talk/workshop/hackfest/sprint for consideration now!
> For more information about Flock, see the website:
> To register and submit a talk/workshop/hackfest/sprint proposal, go to:
> Additionally, I wanted to extend a special invitation to the active
> members of FAmSCo. We would LOVE it if you could have an in-person
> FAmSCo meeting at Flock
> Finally, I would like to ask FAmSCo to appoint one of its members to
> serve on the Flock scheduling committee. This committee will meet to
> review the submitted sessions (and the votes given to those sessions by
> the community), and determine the final Flock schedule. This work will
> likely not happen until June, but we want to get the committee in place
> before this.
Yesterday at the meeting, we agreed that Christoph Wickert and Truong
Ang. Tuan would be FAmSCo representatives in Flock planning.
So if you set some coordinative meeting, please invite them, too.
why is the flocktofedora.org website so slow? Response times are almost
unbearable and it's not only me who has noticed it.
>From what I understand, it runs on OpenShift. I don't have such problems
with other websites run on OpenShift.