...
- Determine core Fedora capabilities/projects. These will be the set that call fcrepo4 home. Candidate list:
- Repository CRUD: LDP
- Transactions
- Versioning: Memento? (
)Jira server DuraSpace JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key FCREPO-1275 - Authorization: WebAC? (Design - WebAccessControl Authorization Delegate)
- Fixity
- Ensure no dependencies from fcrepo4 projects to fcrepo4-exts or fcrepo4-labs
- Ensure dependencies from fcrepo4-exts or fcrepo4-labs on fcrepo4 are limited to kernel interfaces
- Factor fcrepo-transform out of fcrepo4 into an independent project within fcrepo4-exts
- For fcrepo4-exts projects, rename ensure package names to either are org.fcrepo.exts or something unrelated to org.fcrepo<something-relevant>
- Factor ontologies apart into one for each core capability area above
- Build TCKs for the Fedora core capabilities
Requirements for Entry to fcrepo4-exts
- The module is used by X-number of installations (2? 3? 4?)
- The module has one or more formally publicized "owners"
- The module has an integration-test framework in-place
- The module has a unit-test framework in-place
- The module has a package namespace of org.fcrepo.<something-relevant>