Category: Development & Packaging (page 1 of 15)

All articles in this category are related to engineering teams in the Fedora Project, in particular teams working on packaging and release engineering.

2024 Git Forge Evaluation

Vol. I – Fedora Council 2024 Hackfest

During the Council’s February 2024 hackfest, we discussed the future of Fedora’s git forge – that is, the platform Fedora uses for version control and tracking for packages, source code, documentation, and more. This topic has been around for quite some time. If you are just coming into this conversation, or would like a refresher, #git-forge-future is a good place to start.

Instead of one huge post, the Fedora Council divided the follow-ups from our hack-fest into a mini-series of posts throughout April that will cover all the topics we discussed and made decisions on. In each post, we will walk through one core topic, and share our discussion and thought process on how we reached our outcomes. The first in this series, because why not start strong 🙂 , is an update on our git forge evaluation. Read on for important information.

Continue reading

Forthcoming Kubernetes (K8S) changes in F40/Rawhide

The Kubernetes team has released Kubernetes v1.29, which is the version that will be included in Fedora 40. There are four important changes to Kubernetes in Fedora associated with this release that may merit attention.

Continue reading

Kubernetes and Fedora Linux 37 Update

Kubernetes updates for Fedora Linux 37 have been on hold pending an update to the version of Go available Go has now been updated (thanks Alejandro Sáez!). Kubernetes 1.25.15 was submitted to testing on 29 October and will be available for general download 1 week later. See Fedora dist-git for current information on what versions of Kubernetes are available for Fedora in stable and testing.

Kubernetes Support On Fedora Linux 37

Kubernetes v1.25 is the version available for Fedora Linux 37 from Fedora repositories. Starting with Kubernetes v1.25.12, Kubernetes developers changed the version of the go language used to compile Kubernetes from v1.19 to v1.20. Fedora 37 currently provides go language v1.19. As a result, the latest version of Kubernetes available in the Fedora repository is v1.25.11 which is several versions behind the current v1.25 release. Kubernetes v1.25.12 included an important security patch for clusters that include Windows nodes.

Continue reading

A new way to find a package reviewer

Package reviews are an important part of how Fedora delivers well-built RPMs. When one contributor wants to add a new package, another packager has to check it first. It’s how we all hold each other to the high standard we’ve set for ourselves. Of course, that means to add a new package to the repos, you first have to find someone to do the review. Last week, I added a new way to do that: the Package Review Swaps category on Fedora Discussion. Huge thanks to Felix Kaechele for the idea and initial process design.

Continue reading

Important changes to software license information in Fedora packages (SPDX and more!)

On behalf of all of the folks working on Fedora licensing improvements, I have a few things to announce!

New docs site for licensing and other legal topics

All documentation related to Fedora licensing has moved to a new section in Fedora Docs, which you can find at Other legal documentation will follow. This follows the overall Fedora goal of moving active user and contributor documentation away from the wiki.

Fedora license information in a structured format

The “good” (allowed) and “bad” (not-allowed) licenses for Fedora are now stored in a repository, using a simple structured file format for each license (it’s TOML). You can find this at This data is then presented in easy tabular format in the documentation, at

Historically, this information was listed in tables on the Fedora Wiki. This was hard to maintain and was not conducive to using the data in other ways. This format will enable automation for license validation and other similar process improvements.

New policy for the License field in packages — SPDX identifiers!

We’re changing the policy for the “License” field in package spec files to use SPDX license identifiers. Historically, Fedora has represented licenses using short abbreviations specific to Fedora. In the meantime, SPDX license identifiers have emerged as a standard, and other projects, vendors, and developers have started using them. Adopting SPDX license identifiers provides greater accuracy as to what license applies, and will make it easier for us to collaborate with other projects.

Updated licensing policies and processes

Fedora licensing policies and processes have been updated to reflect the above changes. In some cases, this forced deeper thought as to how these things are decided and why, which led to various discussion on Fedora mailing lists. In other cases, it prompted better articulation of guidance that was implicitly understood but not necessarily explicitly stated. 

New guidance on “effective license” analysis

Many software packages consist of code with different free and open source licenses. Previous practice often involved  “simplification” of the package license field when the packager believed  that one license subsumed the other — for example, using just “GPL” when the source code includes parts licensed under a BSD-style license as well. Going forward, packagers and reviewers should not make this kind of analysis, and rather use (for example) “GPL-2.0-or-later AND MIT”. This approach is easier for packagers to apply in a consistent way. 

When do these changes take effect?

The resulting changes in practice will be applied to new packages and licenses going forward. It is not necessary to revise existing packages at this time, although we have provided some guidance for package maintainers who want to get started. We’re in the process of planning a path for updating existing packages at a larger scale — stay tuned for more on that!

Thank you everyone!

A huge thanks to some key people who have worked tirelessly to make this happen: David Cantrell, Richard Fontana, Jilayne Lovejoy, Miroslav Suchý. Behind the scenes support was also provided by David Levine, Bryan Sutula, and Beatriz Couto. Thank you as well for the valuable feedback from Fedora community members in various Fedora forums. 

Please have a look at the updated information. If you have questions, please post them to the Fedora Legal mailing list: 

Backwards-incompatible changes in Bodhi

The 6.0 release of Bodhi — Fedora’s update gating system — will be published in a few days. We will deploy it to production a couple weeks after the Fedora release. It includes backwards-incompatible changes. Here’s what you need to know.

Continue reading

Anaconda is getting a new suit and a wizard

In January, we published “Anaconda is getting a new suit” to let you know that we’re looking to modernize and improve Anaconda’s user experience. Before starting the redesign work for the Anaconda installer, the team reviewed user feedback and usability study data that we’ve gathered over the years. 

Continue reading

Collecting ideas for “Feature Spotlight” articles

How do we – as in, the developers and package maintainers who are working on Fedora Linux – make sure people actually know about all the cool stuff we’re doing? That’s the question at the heart of previous discussions on the “devel” mailing list (How do we announce new packages?) and on discourse (Idea for collecting “Cool New Features / Cool New Packages” article ideas).

As it turns out, the answer to that question is: “If what you’ve worked on isn’t big or noteworthy enough, then there’s no place for you”. That’s not good, and it’s why I started working on “Feature Spotlight”.

Continue reading

Anaconda is getting a new suit

It’s quite some time since we created the current GTK based UI for Anaconda: the OS installer for Fedora, RHEL, CentOS. For a long time we (the Anaconda team) were looking for possibilities to modernize and improve the user experience. In this post, we would like to explain what we are working on, and—most of all—inform you about what you can expect in the future.

Continue reading

Copyright © 2024 Fedora Community Blog

Creative Commons License
This work is licensed under a Creative Commons Attribution 4.0 International License.

Theme by Anders NorenUp ↑