...
- fcrepo4
- fcrepo-module-auth-rbacl
- fcrepo-module-auth-xacml
- fcrepo-build-tools
- ontology - split out audit, indexing, oai-pmh, objState
fcrepo4-exts
This organization is the home of non-core, extension Fedora4 projects, utilities, and ontologies that are actively maintained.
...
- Need to establish owners
- If no owner is established, the given project will be demoted to fcrepo4-labs
- Do we need to rename packages out of "org.fcrepo"?
- ontology-exts
- fcrepo-camel
- fcrepo-message-consumer - heading towards labs
- fcrepo4-client - what is the plan?
- fcrepo-audit
- fcrepo-camel-toolbox
- fcrepo-webapp-plus
- fcrepo4-release-tests
- fcrepo4-oaiprovider
- fcrepo4-swordserver
- migration-utils
- fcrepo4-upgrade-utils
...
- fcrepo4-client
- fcrepo-audit
- fcrepo-camel-toolbox
- fcrepo-webapp-plus
- fcrepo4-release-tests
- fcrepo4-oaiprovider
- fcrepo4-swordserver
- migration-utils
- fcrepo4-upgrade-utils
Migrated
NONE from above
Plan
- Determine core Fedora capabilities/projects. These will be the set that call fcrepo4 home. Candidate list:
- Repository CRUD: LDP
- Transactions
- Versioning: Memento?
- Authorization: WebAC?
- Fixity
- Ensure no dependencies from fcrepo4 projects to fcrepo4-exts or fcrepo4-labs
- Ensure dependencies from fcrepo4-exts or fcrepo4-labs on fcrepo4 is limited to kernel interfaces
- For fcrepo4-exts projects, rename package names to either org.fcrepo.exts or something unrelated to org.fcrepo
- Build TCKs for the Fedora core capabilities