Joining the Package Maintainers
So, you have decided to become a package maintainer in the Fedora Project? This guide will lead you through your first package submission. It can be a completely new package, or update to an existing package.
Admission to the
which is a prerequisite for many packaging tasks,
is not automatic.
You should at least skim through How to Get Sponsored into the Packager Group now,
so that in the likely case that you want to apply,
you are prepared for it.
If you do not know how to create an RPM package, refer to Packaging Tutorial: GNU Hello.
Read the Packaging Guidelines. You need to be thoroughly familiar with these. They govern all package submissions. If you have questions, ask on the Fedora List.
Make sure you have an account in Red Hat Bugzilla.
The email address that you use for your Bugzilla account should be the same email address as you use in the Fedora Account System for all things related to Fedora Packaging.
Create an account in the Fedora Account System. (This is not the same as the Bugzilla account.)
Visit the account system home: https://accounts.fedoraproject.org/
Click on New account and fill in the blanks. Note that the email you give should be the same as the one you gave Bugzilla. This allows the system to link privileges between the two accounts.
After you create your account, please be sure to agree to the Fedora CLA: Click on the edit profile link on the right, then the Agreements tab. If this says view you have agreed already, if it says sign you still need to agree.
You will also need to upload a public RSA SSH key. You need to use the matching private key to access Fedora machines via SSH. Keep in mind that uploading new public SSH key to all servers can take some time (about half hour). You can read more about this here.
Consider joining the following mailing lists:
devel-announce is a low traffic, announcements only list where important development information is posted.
devel is a high traffic mailing list where discussions about the development of Fedora are held.
Next, you should introduce yourself to the community on the devel mailing list. The primary purpose of this is to begin the process of building trust by allowing the Fedora community members to get to know you a bit more.
We want to break anonymity and foster real-world community within the project. You are under no obligation to reveal personal secrets. The objective is to establish a level of trust between yourself and the other members of the project. But you should at least use your real name when communicating with us. Also, a brief description of who you are, your motivations and perhaps a description of the software you have submitted for review are advisable.
Subject: Self Introduction: <Your name> Body: Add any information you believe is applicable including past experience in free and open source projects, a link to the review request you have filed and a brief description of yourself. You can also post your GPG key information if you want to.
Feel free to participate in all the discussion that goes on in any of the lists. Community discussion and feedback is always encouraged.
Software components included in Fedora need to be maintained actively, and bugs — especially security issues — need to be fixed in a timely manner. As a Fedora package maintainer, it is your primary responsibility to ensure this.
Read some other package submissions to learn about packaging and gain familiarity with the process and requirements.
One way of doing this is to join the package-review mailing list. All comments on Fedora package reviews are sent to this (read-only from your point of view) list.
The first thing to do when you set up Fedora packaging is to configure your username and email address for Git. These are linked in each commit you do to Fedora packages.
git config --global user.name "John Doe" git config --global user.email email@example.com
Follow Installing Packager Tools.
Being a Fedora packager means doing package maintenance. To get started, you need to find some packages to maintain.
Even packages that already exist in Fedora need regular maintenance. The Fedora version may be behind the latest upstream release, there may be bugs to be fixed upstream or in the packaging scripts, the packaging scripts can be improved even if the resulting package already works and so on.
To get involved in the maintenance of some packages, you should know what is going on with them. Subscribe to notifications about packages you consider interesting by adjusting the Watch setting for them in the Package Sources.
There are also mailing lists for notifications about activity in any package. Note that the volume of these mailing lists is very high. Most probably they are only useful as input for automatic processing:
If you intend to add a new package to Fedora, follow New Package Process for New Contributors.
Want to help? Learn how to contribute to Fedora Docs ›