in the last few days, several FAmSCo members have raised their concerns
about how the planning of Flock is handled.
Christoph Wickert complained in the fudcon-planning mailing list that he
as a FAmSCo member didn't know that Flock was going to replace FUDCon
EMEA. Although I knew some little info about the conference from
personal conversations and we touched this at our regular meetings, he's
correct that FAmSCo has never been officially informed about the new
Other FAmSCo members pointed out that FAmSCo had some role in the Flock
planning according discussions in this mailing list (one position in the
schedule committee etc). Yet again, we haven't been approached and
informed by anyone from the organizer's team.
We want to help Flock's organizers make Flock as successful as possible,
but we're asking for better transparency and communication with FAmSCo
and we'd like to know what is going to be FAmSCo's role in the planning.
We're full of good news today! First of all, thanks to serious effort
from Luke Macken, Kevin Fenzi, and María Leandro, among others, the
Flock website is live:
Second, we've confirmed dates and our location:
Dates: August 9-12, 2013
Location: College of Charleston (Charleston, SC, USA)
Pre-registration is now open! (See the "Register" link on the website.)
Please be sure to indicate when you register whether you need flight or
hotel funding to attend. Priority will be given to Fedora contributors
who are presenting (or leading a hackfest/workshop/sprint).
Third, with all of that in place, it's time to open the call for talks!
Submissions should be for one of the following:
* Talk (45 minutes)
* Hackfest (2 hours)
* Workshop (2 hours)
* Sprint (2 hours)
You may submit as many topics as you feel qualified to deliver.
Suggested topics include but are in no way limited to:
* Fedora Ambassadors
* Open hardware
* Special Interest Groups
Ready to submit a talk? Go to
http://flock-lmacken.rhcloud.com/submit_proposal. All submissions must
be received by May 31, 2013 at 11:59 p.m. ET.
Cheers, and see you there!
think that mail is from interest here.
@spot when you think sponsorship request will be open? You know flight are
at the lowest price between 8 and 6 weeks before the event. So its really
from interest for us europeans.
---------- Forwarded message ----------
From: Christoph Wickert <christoph.wickert(a)gmail.com>
Subject: Re: FUDCon coming this summer/fall?
Am Freitag, den 03.05.2013, 10:23 +0100 schrieb Peter Robinson:
> On Fri, May 3, 2013 at 10:13 AM, Christoph Wickert
> <christoph.wickert(a)gmail.com> wrote:
> > Am Mittwoch, den 17.04.2013, 11:26 -0400 schrieb Tom Callaway:
> >> On 04/17/2013 08:52 AM, Jaroslav Reznik wrote:
> >> > I definitely like the idea of the one big event and being at the
first one ;-) -
> >> > what budget do you expect? Speaking both about community guys (I can
> >> > the money that would be used for FUDCon EMEA could be used as travel
> >> > also internal people from Europe, we usually don't pay from Fedora
> >> > we need a coverage. As far as I know, there's no budget allocated
and it will
> >> > be really hard to get such.
> >> There is a large chunk of OSAS budget allocated for this event, and our
> >> plan is to try to fund as much travel/lodging for attendees as we
> >> possibly can. Getting people together for this event is our main
> >> priority. Including internal people. :)
> > Lets do some simple math here:
> > FUDCon EMEA attendees: ~100, around 70 of them need lodging.
> > Cheapest flights to Charleston from anywhere in Europe: USD 13,000.
> > Even if only half of the EMEA community members who typically attend a
> > FUDCon will go to FLOCK, it would cost us USD 45,000. And that's ony for
> > flights, no other travel costs or lodging. I really wonder how "bringing
> > people together" should work then. What budget do we have for travel
> > sponsorship?
> > Let's face it: EMEA is the region that suffers most from the current
> > budget. We have a proven track record for budget planning and made a
> > very reasonable and realistic budget. However, we received over 30% less
> > than what we had requested. We even received less than we've spent last
> > year, simply because controlling at Red Hat does not work.
> > And now our premier gets canceled without previous notice and it's
> > budget gets allocated to an event in NA. Well done!
> Actually the "without previous notice" isn't true. It was muted right
> from the very beginning of the initial "DoCon" proposal, it was even
> discussed in board meetings likely while you were a board member.
First of all I think that something published in a blog hardly counts as
an announcement. People cannot just follow every single block post on
the planet. A major change of policies should be discussed with all
relevant groups and people.
And AFAIR it was supposed to be an additional event, at least it was not
clear if it replaces other events. FUDCon LATAM takes place while EMEA
was canceled. The latest status we in FAmSCo had: FUDCon EMEA was
schedule for fall, possibly in October and as long as it doesn't
conflict with the new event, it will take place.
> It's also not just a NA event, Flock v2/2014 is proposed for Europe.
I know it's supposed to be a global event, but this year it's hosted in
the US and therefor most attendees will be from NA as well. And this in
the very same year that also happens to be the worst fiscal year EMEA
ever had. Very bad timing.
And what do you mean with "proposed"? Traditionally FUDCon bids are
handled by FAmSCo. I'm not saying that FLOCK needs to follow that
process, but if there was a proposal I would have appriciated a
fudcon-planning mailing list
make me rich, buy my Inkscape book http://is.gd/yq5OD0 ;)
Here is the proposal I'd like to put forth for determining the Flock
* We form a "conference committee" which includes:
- Ruth, Robyn, and Myself
- One appointed member from each:
- Fedora Board
* 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.
>From Tom's recent blog I read:
* inode0 suggested that it would be better if the scheduled part of
Flock ended on the weekend, so we are strongly considering August 7 -
13, 2013 for the dates (August 12 and 13 would be optional "hackfest
days" with no assigned schedule in advance).
I just want to be clear this wasn't my suggestion really. My concern
is that full participation with travel on both ends would require a
contributor in NA to likely take 7 full days of vacation from work to
attend the entire conference. For people coming from other regions it
would probably be even more.
The ideal timing of this from my perspective would be a 7 day block
running Sunday through Saturday, leaving weekend days on both ends for
travel and "only" requiring 5 full days of vacation to attend. That is
still a lot of vacation time but I think it is a lot easier to get one
full week off than it is to get any longer time off.
Anyway, this isn't something I want to nag about or whine and complain
about until it suits me better. I just want to be clear about what my
concern really is. I'm happy to try anything and see how it works.