Tuesday, 2019-01-15 is the Kernel 4.20 Test Day! Continue reading
Tuesday, 2019-01-15 is the Kernel 4.20 Test Day! Continue reading
The Fedora Council met last week in Minneapolis, Minnesota. It’s a lovely city, but rather cold, so we largely stayed within the interconnected network of enclosed bridges known as the Skyway — and in our conference room working. One of our main projects was the draft below. This is a follow-on from our update to the mission statement last year. It represents the way the Fedora Council would like the Project to make that mission a reality — a guiding policy. We’d like wider community feedback on this approach (and the write-up of it), after which we plan to include the final version in the project documentation. (Update: done, here.)
— Matthew Miller, Fedora Project Leader
“Fedora creates an innovative platform for hardware, clouds, and containers that enables software developers and community members to build tailored solutions for their users.”
We do this within the context of the four foundations: freedom, friends, features, and first.
Continue reading
In mid-October Sumantro Mukherjee and Martin Bříza attended the Mentor Summit for this year’s Google Summer of Code in Sunnyvale, California, USA. Besides talking about the hard points of the program, its future direction and ways how to improve the participation in it, it’s a great place to discover many interesting open source software (and even hardware!) projects. And most importantly, you get to meet the people who stand behind those projects. Continue reading
I’ve been talking with a number of Fedora leaders, principals, and team members about the issue of Fedora lifecycle. Lifecycle here means the way we manage, schedule, and populate Fedora releases. I started the Lifecycle objective and proposed it as a lead to the Fedora Council to house what I hope will be improvements to Fedora lifecycle.
One of the most important goals is to diversify the community ownership of our releases. This involves a fairly extensive set of changes in Fedora. It will need effort from a number of teams that work on release processes and services. For that reason, I’m proposing we pause the release cycle after the release of Fedora 30.
I posted this morning to the devel list to start gathering feedback and input from a wider group on the ideas around the ideas in the writeup. The most important feedback comes from those who are involved in those processes and services. But constructive feedback is welcome from any part of Fedora. Please take the time to read the whole document and understand the goals and benefits for Fedora.
One side note: You may have seen an earlier thread from Matthew Miller about a longer-term maintenance release. The Lifecycle objective would certainly make that possible. But the point of the objective is not that in particular. It’s to allow more flexibility in what we release and when — and thus make Fedora more interesting and hospitable for many more people to participate in, and build on, the project deliverables.
I’d like to express gratitude for participation by Matthew, Jim Perrin, Adam Williamson, Josh Boyer, and others to illuminate key ideas and issues that found their way into this draft and other conversations. While it’s true that any open source community can excel at collaboration, Fedora folks like these really do walk the walk!
Photo by Kosta Bratsos on Unsplash.
Here’s your report of what has happened in Fedora Program Management this week. Fedora 29 Final is Go and will be released on Tuesday.
I’ve set up weekly office hours in #fedora-meeting. Drop by if you have any questions or comments about the schedule, Changes, elections or anything else.
Continue readingCopyright © 2024 Fedora Community Blog

This work is licensed under a Creative Commons Attribution 4.0 International License.
Theme by Anders Noren — Up ↑
Recent Comments