Days 3 and 4 were reserved for workshops. Also, during these 2 days, people continued to split into smaller groups to discuss matters of their own interests, and so did I. However, I caught up with some of the presenters to ask them about the outcome of their sessions and you can read that at the end of this article. But to be fair – if you want to read something about Flock, feel free to browse the blogs that emerged in the first post-Flock week, listed here:
- me (general information) WordPress
- Amita Sharma (Diversity Panel) ami
- Bee (CommOps and metrics) networksfordata
- Sylvia Sánchez (Lailah) (translator, designer) crossingtheair
- Ratnadeep Debnath (FOSS developer and evangelist) rtnpro
- Kevin Fenzi (Fedora Infrastructure Lead) Kevin’s Musings
- Radek Vokal (packages for Fedora & Modularity) </linux>
- Scott Collier (Containers/OpenShift perspective) Notes on tech, mostly…
- Masha Leonova (Fedora Design Team) WordPress blog
- Sinny Kumari (Fedora packager group) Sinny’s blog
- Maria “tatica” Leandro (Fedora diversity – women in Open Source) tatica.org
- Randy Barlow (Fedora Engineering, Erlang) electronsweatshop
- Alex Eng (Zanata) LoOnEs
- Pravin Satpute (Internationalization Engineer) blog link
- Adam Miller (Fedora packager) blog link
- Josh Boyer (Fedora kernel) blog link
- Pierre-Yves Chibon or Pingou (French documentation, packager) blog link
- Brian Exelbierd (Containers, Atomic, event organizer) even the horse knew
- Ryan Lerch (Interaction designer, Inkscape, Blender…) blog link
- Miroslav Suchy (packager, creator of Copr) blog link
Here are my notes from the two guys I talked to.
Led by Brian Exelbierd, the Fedora Docs Learn and Hack session turned out to be more learn and discuss and not learn and hack. Brian shared the outcomes from the Fedora Docs FAD in May 2016 and started a discussion around topic based writing and tooling. There was a lot of sharing of ideas and questions about how we move forward. In general the idea of changing the style of the documents and how we build and publish them was well received. Questions for discussion in the future revolve and how to get there in a manner that makes sense for the project. Brian will be posting an update about the Docs situation at this Comms blog soon.
In parallel with Brian, Christoph Wickert led the Meet your FAmSCo team planning workshop. What is FAmSCo? It stands for the Fedora
Ambassadors Steering Committee and has existed for about ten years.
Their mission is to support the Fedora Ambassadors program. The group
of presenters gave status reports and went through several ongoing
issues, some of which the APAC community is facing:
- We need to have a clearer idea of our target audience. As
conferences are more topic-oriented, we need to created different
marketing messages for the individual target audiences such as
students, Python/Ruby developers, system administrators etc.
- We continue to work on the idea of the Fedora Outreach Steering
Committee (FOSCo), a new body that coordinates the efforts of the
ambassadors, the marketing group, the design team, CommOps and other
outreach focused groups in Fedora. In long term, FOSCo should replace
FAmSCo and take over all it’s duties, but to do that, we need to work
on the structure and get support from more groups.
- FAmSCo and the ambassadors mentors are looking to improve the
mentoring process, but we will not lower the bar. Quality is more
important then quantity, even in countries where the Fedora community
and user base still needs to grow.
- FAmSCo strives to support emerging local communities at the best, be
it financially, logistically, with manpower or simply by giving
I also talked to Justin Flory, Matthew Miller, and Langdon White; but I’ll write about that later. Expect something here or on Fedora magazine soon.