For a variety of reasons, the Fedora Linux 37 retrospective survey got off to a late start. But it’s here now! If you can think back to last fall, please take a few minutes to provide your feedback. Please remember that this survey is about the process of producing F37, not the end result. I haven’t done much with past survey results, but this will be the third survey, which means we can start looking for trends! Please submit your anonymous responses to the survey by Thursday 9 March.
After the release of Fedora Linux 35, I conducted a retrospective survey. I wanted to see how contributors felt about the release process and identify possible areas we can improve. There was no particular reason to start this with F35 except for that’s when I got around to doing it. So how did F35 go? Let’s look at the results from the 63 responses.
Continue reading2017 was a busy year for the Bodhi project. This post explains a bit about what Bodhi does, highlights, and goals for 2018.
Bodhi is designed to democratize the package update testing and release process for RPM-based Linux distributions. It provides an interface for developers to propose updates to a distribution, and an interface for testers to leave feedback about updates through a +1/-1 karma system.
Lets summarize some of events from the past week or two:
On Thursday December 7th, 2017 we held Go/No-Go meeting for F27 server edition. During the meeting we run into some infrastructure issues due to datacenter move, so even the meeting minutes were not completely recorded, we successfully finished the meeting. At the end of the meeting we have agreed to release the Fedora 27 RC 1.6 compose as the Fedora 27 release. The release date is set on December 12th, 2017.
“I contributed!” is a special series on the Fedora Community Blog which helps Fedora contributors understand and get a feel of the activity happening in different areas in Fedora, especially areas other than what they personally participate in. These visualizations for 2015 are made using Gource videos generated by threebean using fedmsg2gource – a CLI tool used to generate Gource videos from fedmsg history,
In this third and final part of the series, we present some subsystem videos which produced interesting patterns in Gource visualizations.
To help better understand what these videos represent as well as to learn more about Gource and fedmsg2gource, check out the earlier articles in the “I contributed!” Gource series here and here.
The Infrastructure Team consists of dedicated volunteers and professionals managing the servers, building the tools and utilities, and creating new applications to make Fedora development a smoother process. We’re located all over the globe and communicate primarily by IRC and email.
Fedora experienced a significant amount of growth and development over the last year. With the growth and recent changes, there were new challenges that Fedora and the Marketing team had to face. The Magazine went really well with significant growth concerning the overall traffic (many thanks to Paul, Ryan, Joe, Chris, Justin) and with more infrastructure stability (thanks to Chris again and Patrick). On the other hand, the institutional part of Marketing experienced difficulties in keeping current with the changes that 2015 brought.
There were many strengths that were preserved (organizing tasks, using a ticketing workflow, discussion in the IRC channel, and communications in general), but the Year in Review analysis is targeted towards identifying and setting goals for improvement in this current year.
“I contributed!” is a special series on the Fedora Community Blog which helps Fedora contributors understand and get a feel of the activity happening in different areas in Fedora, especially areas other than what they personally participate in. These visualizations for 2015 are made using Gource videos generated by threebean using the fedmsg2gource repo.
In this first part of the series, we demonstrate the aggregate Gource visualization for all of Fedora in 2015.
2015 was an important milestone for the Community Operations (CommOps) team in so many ways. CommOps is the newest official sub-project in Fedora, and the team’s role is to assist other sub-projects in Fedora. This is done by building and improving interactions within the internal Fedora community, as well as by increasing communication across the Project as a whole. In other words, CommOps is all about bringing more “heat and light” to the different areas of Fedora.
Since 2015 was the inaugural year of CommOps, the past year was a busy and engaging one. For many of us, it felt like the lists of tasks we completed (and list of tasks to be completed) grew, and continues to each day. For CommOps, this is fantastic and exciting, as it represents concrete actions we can take to improve Fedora Community Operations.
There are a few particular highlights from the past year that helped us really define our role in the Project, and we have some concrete goals we think will help Fedora succeed in the coming year.
Copyright © 2024 Fedora Community Blog
This work is licensed under a Creative Commons Attribution 4.0 International License.
Theme by Anders Noren — Up ↑
Recent Comments