A Fedora account is required to access the applications and infrastructure used by the Fedora community. It only takes a minute to set up! You can learn more about the Fedora project here.

NeuroFedora is a community supported initiative, and team members work on it in their free time. Usually, this is about 5—​10 hours a week on average, depending on our professional work loads and so on. We are always looking for more hands to help with NeuroFedora, and we are more than happy to help people learn the technical skills required to contribute. Please get in touch if you would like to join the team!

Infrastructure overview

NeuroFedora relies completely on the infrastructure maintained by the Fedora community:

Community organisation, governance, and dissemination


Packages and software


Contributor roles

There are various roles in which you can contribute to NeuroFedora. For a complete description of contributor roles in the Fedora community, please refer to this wiki page.

The NeuroFedora team are happy to help new members join the Fedora community, and to learn the skills necessary to contribute. Please get in touch with us using one of the communications channels!

The Fedora Join SIG also helps newcomers start with contributing to Fedora. Take a look at their documentation.

Suggest software for inclusion

If there’s more useful Free software out there that is not yet in NeuroFedora, you can bring it to our attention. You can do so using our suggestion form.

Package and maintain software

Making packages available in the Fedora repositories requires the team to build them from source to produce RPMs. These RPMs are then made available in the Fedora repositories for all Fedora users to easily install on their systems using dnf. They can also be used to easily create container images that users can run with Podman (or Docker). You can help the team by becoming a Fedora package maintainer.

EPEL support

Read more about Extra Packages for Enterprise Linux (EPEL) here.

We primarily focus on Fedora branches. If you need a certain package that is (co-)maintained by us in Enterprise Linux (EL), please file a bug against that package, mentioning which epel branch you require and we’ll see what we can do depending on time and capacity.

If you are already a packager, we are happy to add you as a co-maintainer, so you can take care of porting to any or all EPEL branches.

Test packaged software

Packages that we provide must go through the Fedora Quality Assurance (QA) process. You can simply enable the updates-testing repository and help by testing updates.

File bugs and report general issues

Any bugs with the software include in NeuroFedora should ideally be reported to the Fedora Bugzilla instance. You will need a bugzilla or Fedora account to do so. This page provides step by step instructions on filing bugs.

Any other issues related to NeuroFedora should be filed at our Pagure project instance.

Improve documentation

User documentation is a most important resource. You can help by improving or contributing to our documentation. You can improve pre-existing pages by clicking on the "Edit this page" in the top right corner. The sources are kept here.

We are also always looking for people to write about NeuroFedora, the tools, community, and neuroscience on the NeuroFedora blog.

Help other users

We’ve set up communication channels to help users troubleshoot issues and get help. You can help by remaining present in the communication channels and answering users' questions.

Spread the word

Help us spread the word! Write about NeuroFedora, share your opinions on social media, help more people learn about the project and get involved!