The Fedora Create Community exists to coordinate and integrate the community of developers working with the Fedora software. The Fedora Repository Service was intentionally designed to be the basis for a variety of information management schemes and, as such, it porvides the foundation for a rich variety of software projects. Take a look at the project types listed below to get a sense of the diverse software being created by this community to work with Fedora.
We've created a map of the structure of Duraspace to give a sense of where this fits within the bigger picture.
How to Participate
Types of Developers & Skills
Documenting Best Practices
Features & Ideas Tracker
Project Directory (Products)
Challenge Areas
Hot Topics
The repository service that is at the core of Fedora is managed by a community-based committers group that maintains the integrity of the core software, both with their own code and by working with other members of the community to integrate their contributions.
For the sake of sanity, we break these out into Complete Solutions, Services & Utilities, Libraries & Frameworks, Content Models, Workflow-ish Components, Plugins, Serializations & APIs.
Currently the most complete listing of available software is in our community software registry.
Examples of Complete Solutions
End-user facing solutions that cater to specific use case(s), ie. Institutional Repositories (IRs), Virtual Research Environments (VREs), Data Curation Systems, etc.
Self-contained, purpose-specific software that is either used on-demand or acts as an integrated part of overall deployment. These are either run constantly, on an ongoing basis, alongside the repository or invoked by a person.
Examples of Services & Services
Libraries for consuming Fedora's APIs and/or Frameworks for creating client applications on top of Fedora Repositories.
Examples of Libraries & Frameworks
CModels and associated Service Definitions & Service Implementations that can be used with the Fedora CMA
Examples of Content Models
Small chunks of code for performing specific tasks. These can be used & re-used as building blocks in larger processes. Often, these are wrappers for software & utililties that are not Fedora-specific. These are meant to be invoked by an external program or process.
Examples of Workflow Components
OSGi plugins and alternatives for components within the core (ie. Triplestores)
Examples of Plugins
Examples of Serializations & APIs
Means for exposing Fedora Repositories and Fedora Content by structures other than FOXML and Fedora's existing APIs.