Earlier this month, I received the Rainbow badge in Fedora Badges. Rainbow is the fifth badge in a series for receiving “karma cookies” from others in IRC. Every time I receive a new badge in this series, I like to reflect back on the past and where my Fedora journey has taken me since October 2015.
Today, I am pleased to announce my new role as the Fedora Magazine editor-in-chief. After deciding to shift focus to other areas of the Fedora Project, I am receiving the torch from Ryan Lerch. Ryan has helped lead the Magazine, edit pieces from other contributors, contribute his own pieces, and decide strategic direction for the Magazine.
He leaves big shoes to fill, but I hope to offer my own leadership, creativity, and direction in coming years as well. I’d like to thank both Ryan, Paul Frields, and Remy DeCausemaker for their mentorship and guidance towards becoming involved with Fedora and the Magazine. I’m excited to have the opportunity to help guide the Fedora Magazine in how it fits with the rest of Fedora.
Tomorrow, August 22, 2016, marks the end of the Google Summer of Code 2016 program. This year, I participated as a student for the Fedora Project working on my proposal, “Ansible and the Community (or automation improving innovation)“. You can read my original project proposal on the Fedora wiki. Over the summer, I spent time learning more about Ansible, applying the knowledge to real-world applications, and then taking that experience and writing my final deliverable. The last deliverable items, closing plans, and thoughts on the journey are detailed as follows.
From August 2 – 5, the annual Fedora contributor conference, Flock, was held in the beautiful city of Kraków, Poland. Fedora contributors from all over the world attend for a week of talks, workshops, collaboration, fun, and community building (if you’re tuning in and not sure what Fedora is exactly, you can read more here). Talks range from technical topics dealing with upcoming changes to the distribution, talks focusing on the community and things working well and how to improve, and many more. The workshops are a chance for people normally separated by thousands of miles to work and collaborate on real issues, problems, and tasks in the same room. As a Fedora contributor, this is the “premier” event to attend as a community member.
Although my report comes a little late, it comes with a lot of thought and reflection over the week at Flock. I participated as a speaker for my talk with Jona Azizaj titled, “University Outreach: New task or new mindset?” I also worked with Bee Padalkar on running the Community Operations (CommOps) team workshop for planning our own future tasks in coming months and knowing what issues or topics the community had in mind. And lastly, due to last-minute scheduling issues, I helped plan and organize the Diversity Panel with Amita Sharma and many other incredible contributors.
Without further ado, this is my analysis and report on the events at Flock 2016. And for anyone wondering what “żegnajcie” in the title means, Google Translate tells me that means “farewell!” in Polish.
This week wraps up for July and the last period of Google Summer of Code (GSoC 2016) is almost here. As the summer comes to a close, I’m working on the last steps for preparing my project for deployment into Fedora’s Ansible infrastructure. Once it checks out in a staging instance, it can make the move to production.
This week and the last were busy, but I’ve made some more progress towards creating the last, idempotent product for managing WordPress installations in Fedora’s Infrastructure for GSoC 2016. The past two weeks had me mostly working on writing the standard operating procedure / documentation for my final product as well as diving more into handling upgrades with WordPress. My primary playbook for installing WordPress is mostly complete, pending one last annoyance.
Earlier this month, I received some of the most exciting news I have had all year. After much finger-crossing and (hopefully) hard work, I am traveling to Kraków, Poland, for the Fedora Project‘s annual Flock conference. Flock is described by the organizers as the following.
Flock, now in its fourth year, is a conference for Fedora contributors to come together, discuss new ideas, work to make those ideas a reality, and continue to promote the core values of the Fedora community: Freedom, Friends, Features, and First.
This year, I am attending as a contributor to the project, giving a talk, and leading a workshop!
Ever wondered what goes on behind the magic of Fedora Badges? How does a badge go from being a design to an earn-able entity? This short but handy guide breaks down the entire process for you. This post is adapted from a series of notes I took while watching Ralph Bean demo the procedure at PyCon. This guide is a supplement, not a replacement, for the official Badges SOP.
This week, with an initial playbook for creating a WordPress installation created (albeit needing polish), my next focus was to look at the idea of creating a WordPress multi-site network. Creating a multi-site network would offer the benefits of only having to keep up a single base installation, with new sites extending from the same core of WordPress. Before making further refinements to the playbook, I wanted to investigate whether a WordPress network would be the best fit for Fedora.
This week is busy and continues to keep the pace of previous weeks. A lot has happened this week in the Fedora Project and I’ve taken on a few new tasks too. In addition to existing work on Google Summer of Code, Community Operations, Marketing, and more, I wanted to take some time this week to focus on CommOps Ticket #71. This ticket originally focused on improving accessibility of design resources for Fedora Ambassadors. However, after an interesting conversation with Máirín Duffy on the Design Team workflow, I discovered the availability was not the main issue. Instead, it seemed like communicating was an area needing focus.