On Thu, 2018-03-15 at 11:53 -0400, Matthew Miller wrote:
Location is still being worked on. But let's talk about the
I think last Flock was... fine... but didn't have the positive energy
I've gotten from it in years past. I think we should change it up a
little bit this time around.
I have yet to attend a Flock, but hope to in the future.
Brian and I talked about this quite a bit after the recent Mindshare
and Documentation FADs. Those were both incredible, successful
events. Specifically, I think they were more generally succesful than
the "do-con" we've pushing Flock towards. Flock is vitally important,
but instead of focusing all of the get-together-and-do energy in one
place and time, we should plan on having more hackfests throughout
2. Planning the Next Strategy.
I agree with both of the items above... As for new ideas I think there
should be a mix of continued strategy, items introduced since the last
Flock and the generation of new ideas. With regards to hackfests it
would be great to have more local / regional hackfests between two
It sounds more like the thought is less about changing Flock and more
about changing what happens between two Flocks.
3. Building Community Connections and Engagement.
We do amazing work as a global project, but there's no substitute
for direct human interaction. Flock helps tie us together and the
in-person interactions help us function better on IRC and mailing
lists throughout the year. To me, it's always been very
energizing, and we should emphasize that.
I feel strongly about this as well. When Canonical decided to cancel
the Ubuntu Developer Summits a great deal was lost in the community.
Canonical still had their own 'sprints', but the community was, in
general, left without an in-person event.
So, based on this, Brian and I came up with a draft idea of how
sessions should work. Not broken down into exact days or anything
yet, but basically in this order:
1. Plenary (one big room with everyone)
Call this what you will. There are many names such as Keynote or
opening session. The purpose of this is to excite the attendees and
build energy for the rest of the event.
2. New Ideas Talks
I agree with this as well as the process of method of choosing the
3. Topic-Focused Discussions
- SIG and Team meetings
- Regional planning for the next year
- Basically, mini-strategic-hackfests for various groups
This is the area that I think could focus on the item of growing local
/ regional hackfests. There could be sessions on how to run a
successful regional event and in-person assistance for those trying to
plan such events.
4. A Wrap Up / Readout session (Plenary, again)
- could include a leadership panel dicussion
- five-minute summaries from the various breakouts
What do you all think?
Overall, good thoughts. It is good to start thinking about Flock early.
I wanted to throw out an idea borrowed from my time in the Ubuntu
community. There were events that were global on scale, but local in
execution that I think Fedora could potentially benefit from. The one
that comes to my mind as the best example was the Ubuntu Global Jam.
These included guidance from the core community, but were executed at a
local level. The events were all held on the same day or within the
At their peak there were metrics shared about local and regional
participation. The events combined local participation with IRC and
video events to make a global event. These events are no longer run,
but I felt they were successful when the community had the 'energy' to
While the events could be much smaller and simpler in scope I think
merging local participation coordinated on a global level would help
build a sense of global community for people who are not sure how to
participate yet. (for example: the new Fedora user who is not full
exposed to the community yet).
If there is an interest I can try to organize my thoughts a bit more
and put something together on this item.
Fedora Project Leader
flock-planning mailing list -- flock-planning(a)lists.fedoraproject.org
To unsubscribe send an email to flock-planning-leave(a)lists.fedoraproj