Date: Thu, 28 Mar 2024 21:18:47 -0400 (EDT) Message-ID: <1028364356.29366.1711675127106@lyrasis1-roc-mp1> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_29365_1939030916.1711675127105" ------=_Part_29365_1939030916.1711675127105 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
The Fedora software is completely developed and maintained by the user c= ommunity. There is no dedicated development staff that implements Fedora. T= he project receives technical and organizational stewardship from DuraSpace= , but the implementation of Fedora comes completely from the shared contrib= utions of the community.
That said, there is a coordinated process for engaging in Fedora develop= ment. If you have any interest at all in becoming more familiar with the in= ner workings of the Fedora software, you are welcomed and encouraged to joi= n the process =E2=80=93 Java skills not required!
The calendar is= divided into six-month phases (Jan - June and July - Dec). We try to estab= lish the community developer commitments prior to the start of the coming p= hase. Each phase is then sub-divided into two-week sprints. Developmen= t 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 giv= en community developer will participate in is collaboratively determined be= tween 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 toolin= g and documentation, and the project processes. In order for the investment= in time to be mutually beneficial, the minimum number of sprints i= n a developer's first phase is three, although more are encouraged= . Additionally, it is recommended that new team members schedule their firs= t 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 d= evelopers to the project over the course of the year cumulatively totalling= 50% of an FTE, that institution is invited to join the Fedora advisory tea= m=E2=80=A0.
=E2=80=A0 An invitation is also offered to institutions contributin= g at the "gold level" of DuraSpace membership.
Fedora development is driven by use ca= ses submitted by the community; all features are aimed at satisfying on= e or more of these use cases. It is therefore critically important that fea= tures are tested by stakeholders to verify that they actually satisfy the r= elevant use cases.
The use cases relating to a particular feature can be found on the Roadmap page. Whenever a use case is ready t= o 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 i= n 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. = p>