Current Release

This documentation covers the current version of Fedora. Looking for another version? See all documentation.

Join the Community

There are many ways to get involved in the community for both Developers and Non-Developers.

Communication Channels

There are a wide variety of communication channels available for all Fedora users. 

Join the Development Effort

If you have interest in becoming more familiar with the Fedora software, you are welcomed, and encouraged to join the process – Java skills not required!

Reasons to join the development effort

    • Increase detailed understanding of Fedora to bring back to you home institution
    • Contribute to the Fedora technical progress
    • Collaborate with other developers in the Fedora technical community
    • Give back to the open source process
    • Ensure the longevity of Fedora as a robust, open source repository platform
    • Increase your skill and confidence in using standard (widely applicable) open source software collaboration tools and techniques.

Tech Calls

A great place to get started is by joining either of our two scheduled Tech Calls. Join us at any time to familiarize yourself with current Fedora work, ask questions, and get to know the Tech Team and Committer Team.

The Weekly Tech Call 

    • Calls take place every Thursday at 11am Eastern
    • All skill levels are welcome

EU/UK Tech Meeting

    • Calls take place on the 2nd Tuesday of each month at 13:00 UTC (8AM ET)
    • All skills levels are welcome

Join Testing and Validation Effort

Fedora is the reference implementation of the Fedora API Specification.  Its development, therefore, is informed by the specification, which in turn is an expression of a number of community defined use cases for a content repository designed for durable access to data.

Each Fedora release is accompanied by a Docker Image, so use cases can be tested and validated easily in a desktop environment.

There is an API Test Suite created to ensure conformance with the Fedora API Specification and, therefore, one means to test the Fedora software, though there are a myriad of ways to test the software.

If you have an interest in the Fedora API Specification and/or resulting software, please join the testing and validation effort. You can leave feedback as a comment on the relevant wiki page, and/or contact the Fedora Product Manager, Arran Griffith or Fedora Developer Dan Field, directly with your feedback. 

Check out the Guide for New Developers

Guide for New Developers