Fedora services

Our directory and identity management tool provides community members with a single account to login on Fedora services. Registering an account there is one of the first things to do if you plan to work on Fedora.

Personal web space provided to community members to share files, git repositories or host static web pages. The top-level domain is an index of the existing pages.

Centrally managed preferences for Fedora notifications via email or matrix

Multilingual discussion platform providing community support to our users. You can ask us anything about Fedora!

Ask not what Fedora can do for you, but you can do for Fedora? This site is a starting place for brand new contributors to help them figure out where they can hop on board!

Achievement system for Fedora contributors, awarding badges based on activity in the community.

Feed aggregating the blogs of the community members that opted in, to share their opinion to a broader audience.

Probably the best place to find documentation about Fedora, including the changes between releases (and a big kudos to the translation teams to keep this resource up to date in the different languages!).

Fedora Magazine is a WordPress-based site which delivers all the news of the Fedora Community.

Any page that does not fit in the main docs website: user and team pages, change proposals or legacy documents.

Bug tracker shared with and run by Red Hat, used to track issues with the Fedora packages.

The Fedora Calendar (or fedocal), you might have already guessed, is a public calendar service. You can create your own calendar, or subscribe to others. Want to be kept abrest of releases, freezes, and events? This is the tool for you.

Forum based oriented towards the development of Fedora, not to be mistaken with ask.fp.o.

As a member of the community, you can now vote for the different steering committees and for this you will use the Election application. Voting is a right and a duty as a member of the community; it is one of the things you can do to influence the development of Fedora.

Mailing lists are used for communication within the community. There are lists for generic topics and lists more dedicated to a specific topic, there is for sure one for you.

Fedora Infrastructure runs a friendly matrix bot that you may know named zodbot. Among its many and varied functions is logging matrix meetings, the archives of which you can find here.

Nuancier is a simple voting application for the supplementary wallpapers included in Fedora.

Pastebin server, which can easily be used from the command line with fpaste.

Overview and trends for language translations across Fedora.

Next-gen translation platform for Fedora.

The tool you will use to push your packages to the Fedora repositories as an update, first an update to be tested (repository: updates-testing) then a stable update (repository: updates). Behold — the Magic Cabbage.

Copr is an easy-to-use automatic build system providing a package repository as its output. You can make your own repositories!

Koji is the software that builds RPM packages for the Fedora project. It uses Mock to create chroot environments to perform builds that are both safe and trusted.

Web interface atop the Fedora Module Build Service.

A meta-app over the other packaging apps; the best place to find out what is in the Fedora repositories. Which packages are present in which version, who is maintaining them, what patches have been applied, what bugs have been reported against them. All these kind of questions can be answered here.

Ever wonder exactly what is in the new release of a Fedora package? This is where the change histories of all the packages in Fedora for every release of Fedora (and EPEL) are kept.. forever! A gold mine.

The Fedora Blocker Bug Tracker tracks release blocking bugs and related updates in Fedora releases currently under development.

As part of the kernel testing initiative we provide a webapp where users and automated systems can upload test results. If you have access to hardware where we could catch tricky driver issues, your assistance here would be much appreciated.

Koschei is a continuous integration system for RPM packages. It tracks dependency changes done in Koji repositories and rebuilds packages whose dependencies change. It can help packagers to detect failures early and provide relevant information to narrow down the cause.

Platform for collecting and analyzing package crashes reported via ABRT (Automatic Bug Reporting Tool). It makes it easy to see what problems users are hitting the most, and allows you to filter them by Fedora release, associate, or component.

These pages contain periodically generated reports with information on the current state of all Fedora package review tickets — a super useful window on bugzilla.

DataGrepper is an HTTP API for querying the datanommer database. You can use it to dig into the history of the fedora messaging message bus. You can grab events by username, by package, by message source, by topic…​ you name it.

Small API exposing the metadata contained in different RPM repositories.

Fedora is distributed to millions of systems globally. This would not be possible without the donations of time, disk space, and bandwidth by hundreds of volunteer system administrators and their companies or institutions. Your fast download experience is made possible by these donations. The list on the MirrorManager site is dynamically generated every hour, listing only up-to-date mirrors.

Pagure is a git-centered forge. With pagure you can host your project with its documentation, let your users report issues or request enhancements using the ticketing system and build your community of contributors by allowing them to fork your projects and contribute to it via the now-popular pull-request mechanism.

The Product Definition Center is repository and API for storing and querying metadata related to packages, product releases, engineering processes and artifacts which are required to support automation of release engineering workflows.

Code named anitya, this project tracks upstream tarball locations and publish notifications to the fedora messaging bus when new ones are found. Other daemons will then be responsible for filing bugs, attempting to automatically build packages, perform some preliminary QA checks, etc..

Sometimes the Fedora Infrastructure team messes up (or lightning strikes our datacenter(s)). Sorry about that. You can use this website to check the status.