The Fedora Create Community exists to coordinate people who are working on anything external to the Core Repository.
We've created a map of the map of the structure of Duraspace to give a sense of where this fits within the bigger picture.
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. These are either run constantly, on an ongoing basis, alongside the repository or invoked by a person.
Self-contained, purpose-specific software that is either used on-demand or acts as an integrated part of overall deployment.
Examples of Services & Services
Examples of Libraries & Frameworks
CModels and associated Service Definitions & Service Implementations
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 alternative for components within the core (ie. Triplestores)
Examples of Plugins
Examples of Serializations & APIs
How to Participate
Types of Developers & Skills
Documenting Best Practices
Features & Ideas Tracker - Jira
Project Directory (Products)
Challenge Areas
Hot Topics