Page tree

Old Release

This documentation covers an old version of Fedora. Looking for another version? See all documentation.

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

Join Development Sprints

The Fedora software is completely developed and maintained by the user community. There is no dedicated development staff that implements Fedora. The project receives technical and organizational stewardship from DuraSpace, but the implementation of Fedora comes completely from the shared contributions of the community.

That said, there is a coordinated process for engaging in Fedora development. If you have any interest at all in becoming more familiar with the inner workings of the Fedora software, you are welcomed and encouraged to join the process – Java skills not required!

The calendar is divided into six-month phases (Jan - June and July - Dec). We try to establish the community developer commitments prior to the start of the coming phase. Each phase is then sub-divided into two-week sprints. Development takes place in units of "sprints", and the expectation is that developers who are contributing to a given sprint have support from their respective institutions to have full focus on Fedora development during the sprint.

The exact scheduling of which sprints during a development phase any given community developer will participate in is collaboratively determined between the developer and the Fedora technical lead.

For a developer who is new to the project, we have found that it usually takes a full sprint to become acquainted with the codebase, related tooling and documentation, and the project processes. In order for the investment in time to be mutually beneficial, the minimum number of sprints in a developer's first phase is three, although more are encouraged. Additionally, it is recommended that new team members schedule their first two sprints to be consecutive: the first to acclimate to the project, and the immediate second to excel.

It should also be noted that if an institution contributes one or more developers to the project over the course of the year cumulatively totalling 50% of an FTE, that institution is invited to join the Fedora advisory team†. 

Reasons to join development sprints

  • Increase detailed understanding of Fedora to bring back to home institution
  • Drive the Fedora technical agenda from the ground up
  • Collaborate with other developers in Fedora technical community
  • Give back to the open source process
  • Gain membership to the Fedora advisory team
  • 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.

† An invitation is also offered to institutions contributing at the "gold level" of DuraSpace membership.

Join Testing and Validation Effort

Fedora development is driven by use cases submitted by the community; all features are aimed at satisfying one or more of these use cases. It is therefore critically important that features are tested by stakeholders to verify that they actually satisfy the relevant use cases. 

The use cases relating to a particular feature can be found on the Roadmap page. Whenever a use case is ready to be tested, a comment to that effect will be added to that use case's wiki page (along with the Fedora version the use case should be tested against). Each Fedora release is accompanied by a one-click installer, so use cases can be tested and validated easily in a desktop environment.

If you have an interest in one or more Fedora use cases, 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, David Wilcox, directly with your feedback. 

Join the Community

 

  • No labels