F4 GitHub Organziations
fcrepo4
This organization is the home of the core Fedora4 API, ontologies, test compatibility kits, and reference implementation.
Current
- fcrepo4
- fcrepo-camel
- fcrepo-message-consumer
- fcrepo-module-auth-rbacl
- fcrepo-module-auth-xacml
- fcrepo-build-tools
- ontology
Migrated
- fcrepo4 (minus fcrepo-transform)
- 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.
Current
NONE
Migrated
Notes:
- 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"?
- fcrepo-transform
- 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-labs
This organization is the home of experimental projects that are related to Fedora4.
Current
- 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? (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, ensure package are org.fcrepo.<something-relevant>
- Factor ontologies apart into one for each core capability area above
- Build TCKs for the Fedora core capabilities
Becoming an fcrepo4-exts project
Requirements
- The module is used by X-number of 3 or more installations
- The module has two or more formally publicized "owners" (documented in README)
- The module has an integration-test framework in-place
- The module has a unit-test framework in-place
Considerations
For Java projects that are intended to be shared or used via Maven machinery, it is recommended that:
- The module be released to Maven Central
- The module has a parent pom of fcrepo-parent/pom.xml