I can’t remember how writing an annual reflection became a tradition, but after writing them for the last two years, it is now a habit. Every time I look back on all that the last year brought into my life, it is surreal. Many things that happened, I could never have expected one or two years ago. And perhaps now, I see that life is defined by the unexpected moments: the things that surprise us, warm our hearts, sadden us, and remind us of our humanity. Thus, I present my year in review of 2017.
This category is about the popular Linux distribution, Fedora. Fedora is a free and open source Linux distribution. It focuses on its four foundations of Freedom, Friends, Features, First. Some of the articles here are useful for users, many are aimed for other contributors.
The past year was a busy for Fedora. The community released Fedora 26 and 27. Different sub-projects of Fedora give their share of time for the overall success of Fedora. But in a project as big as Fedora, it’s hard to keep track of what everyone is doing! If you’re a developer, you likely know more about what’s happening inside the code of Fedora, but you may not know what’s happening with the Fedora Ambassadors. Or maybe you’re involved with Globalization (G11n) and translating and know what’s happening there, but you’re not as familiar with what the Fedora Design team is working on.
Share your 2017 “Year in Review”
To communicate with the rest of the Fedora community what we worked on in 2017, the Fedora Community Operations team (CommOps) encourages every sub-project of Fedora put together their own “Year in Review” article on the Fedora Community Blog. The CommOps team has created an easy to use template to document your top three highlights of 2017 and one goal for 2018.
Over the summer, I migrated my desktop environment to i3, a tiling window manager. Switching to i3 was a challenge at first, since I had to replace many things that GNOME handled for me. One of these things was changing screen brightness.
xbacklight, the standard way of changing backlight brightness on laptops, doesn’t work on my hardware.
Recently, I discovered brightlight, a tool that changes backlight brightness. I decided to try it, and it worked with root privileges. However, I found there was no RPM package in Fedora for brightlight. I decided this was the right time to try creating a package in Fedora and learn how to create an RPM.
In this article, I’ll cover and share how I…
- Created the RPM SPEC file
- Built the package in Koji and Copr
- Worked through an issue with debug package
- Submitted the package to Fedora package collection
Since I became a Fedora contributor in August 2015, I’ve spent a lot of time in the community. One of the great things about a big community like Fedora is that there are several different things to try out. I’ve always tried to do the most help in Fedora with my contributions. I prefer to make long-term, in-depth contributions than short-term, “quick fix”-style work. However, like many others, Fedora is a project I contribute to in my free time. Over the last month, I’ve come to a difficult realization.
After deep consideration, I am resigning from the Fedora Council effective at the end of the Fedora 26 release cycle.
A new release of Fedora makes headlines this month. With every release, it also means a new round of the Fedora community leadership elections. On 24 July 2017, the call for nominations went out for candidates. The Fedora Engineering Steering Committee (FESCo), Fedora Ambassador Steering Committee (FAmSCo), and the Fedora Council all have seats open. Already, discussions on nominations are happening. The candidate interview templates are being prepared. Even now, the nomination lists are filling up. However, I want to share an opinion on the upcoming FAmSCo election specifically.
The Fedora Diversity FAD (a.k.a. Fedora Activity Day, or a sprint) took place during the weekend of DevConf, 27-29 January. The original planning for this FAD started in August 2016, after the Flock 2016 conference. At Flock, the Diversity Team held a panel with open discussion about diversity and inclusion efforts in Fedora. Based on the feedback received during and after the panel, it was a priority for us to continue working on the objectives we had established before Flock. For the FAD, a majority of the Fedora Diversity Team was present along with a few others.
- Amita Sharma (amsharma)
- Bhagyashree “Bee” Padalkar (bee2502)
- Brian Exelbierd (bex)
- Jona Azizaj (jonatoni)
- Justin W. Flory (jflory7)
- Maria “tatica” Leandro (tatica)
- Marina Zhurakhinskaya (marinaz)
- Radka Janek (rhea)
We made significant progress in accomplishing our larger objectives and to contribute to the Fedora Project mission and goals. The primary objectives we established for our FAD were completing plans for the demographic survey, building a campaign based on those results, and analyzing our Code of Conduct to find ways to better impact the community. This report covers each of these objectives, what we accomplished, and what we plan to do next.
Transparency is the best policy and communication is key. This is why I felt it was important to make this announcement ahead of time to make clear expectations for the coming months. This past December, I was happy to accept a Production Engineer Intern position at Jump Trading, LLC. From June to August, I will be working at their office in Chicago, IL. I’m excited for this opportunity to learn from some of the sharpest people in the industry and to leave my own mark as an intern during the summer.
During the hiring process, I was happy to ensure that contributing to open source software would still be possible during my time of employment. I saw during my on-site interview that Jump Trading employs open source software throughout the company but also contributes back to open source, either with hours or donations. However, while I am still able to contribute to Fedora, I do not anticipate being able to maintain the level of activity that I contribute at now during my internship.
This article was originally published on the Fedora Magazine.
Open source projects are built online and a lot of their community members are placed all over the world. Even though projects have people from around the world, this doesn’t stop ambitious community members to organize open source conferences or events in their own cities. Whether they’re focused generally to open source or for a specific project, you can find a variety of conferences, hackathons, workshops, or meet-ups all over the world. Fedora benefits from having Ambassadors to attend these events to introduce Fedora and spread the word about the community. It’s not uncommon to see Fedora participating in these events, and Linux Weekend 2017 in Tirana, Albania was not an exception.
From March 25-26, 2017 in Tirana, Albania, nearly 130 people attended the first-ever Linux Weekend 2017. Linux Weekend was organized by Open Labs Hackerspace at the Universiteti Politeknik i Tiranës as an introduction to Linux for beginners. Throughout Tirana, universities have a strong focus on Windows or macOS operating systems and little focus is given to Linux. Open Labs community members wanted to organize an event that would promote Linux as an open source alternative and demonstrate some of its benefits over proprietary environments. The event collected representatives from various communities, including Fedora, Ubuntu, OpenSUSE, NextCloud, MusicBrainz, and more.
Before looking too far ahead to the future, it’s important to spend time to reflect over the past year’s events, identify successes and failures, and devise ways to improve. Describing my 2016 is a challenge for me to find the right words for. This post continues a habit I started last year with my 2015 Year in Review. One thing I discover nearly every day is that I’m always learning new things from various people and circumstances. Even though 2017 is already getting started, I want to reflect back on some of these experiences and opportunities of the past year.
When people first think of “open source”, their mind probably first goes to code. Something technical that requires an intermediate understanding of computers or programming languages. But open source is a broad concept that goes beyond only binary bits and bytes. Open source projects hold great regard for community participation. The community is a fundamental piece of a successful open source project. For my experience getting involved with open source, I began in the community and worked my way around from there. At the age of fifteen, I was beginning my open source journey and I didn’t even know it.