F4 GitHub Organziations

fcrepo4

This organization is the home of the core Fedora4 API, ontologies, test compatibility kits, and reference implementation.

Current

1. fcrepo4
2. fcrepo-camel
3. fcrepo-message-consumer
4. fcrepo-module-auth-rbacl
5. fcrepo-module-auth-xacml
6. fcrepo-build-tools
7. ontology

Migrated

1. fcrepo4 (minus fcrepo-transform)
2. fcrepo-module-auth-rbacl
3. fcrepo-module-auth-xacml
4. fcrepo-build-tools
5. 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"?

1. fcrepo-transform
2. ontology-exts
3. fcrepo-camel
4. fcrepo-message-consumer - heading towards labs
5. fcrepo4-client - what is the plan?
6. fcrepo-audit
7. fcrepo-camel-toolbox
8. fcrepo-webapp-plus
9. fcrepo4-release-tests
10. fcrepo4-oaiprovider
11. fcrepo4-swordserver
12. migration-utils
13. fcrepo4-upgrade-utils

fcrepo4-labs

This organization is the home of experimental projects that are related to Fedora4.

Current

1. fcrepo4-client
2. fcrepo-audit
3. fcrepo-camel-toolbox
4. fcrepo-webapp-plus
5. fcrepo4-release-tests
6. fcrepo4-oaiprovider
7. fcrepo4-swordserver
8. migration-utils
9. fcrepo4-upgrade-utils

Migrated

NONE from above

Plan

1. Determine core Fedora capabilities/projects. These will be the set that call fcrepo4 home. Candidate list:
   1. Repository CRUD: LDP
   2. Transactions
   3. Versioning: Memento? ( Unable to locate Jira server for this macro. It may be due to Application Link configuration. )
   4. Authorization: WebAC? (Design - WebAccessControl Authorization Delegate)
   5. Fixity
2. Ensure no dependencies from fcrepo4 projects to fcrepo4-exts or fcrepo4-labs
3. Ensure dependencies from fcrepo4-exts or fcrepo4-labs on fcrepo4 are limited to kernel interfaces
4. Factor fcrepo-transform out of fcrepo4 into an independent project within fcrepo4-exts
5. For fcrepo4-exts projects, ensure package are org.fcrepo.<something-relevant>
6. Factor ontologies apart into one for each core capability area above
7. Build TCKs for the Fedora core capabilities

Becoming an fcrepo4-exts project

Requirements

1. The module is used by 3 or more installations
2. The module has two or more formally publicized "owners" (documented in README)
3. The module has an integration-test framework in-place
4. 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:

1. The module be released to Maven Central
2. The module has a parent pom of fcrepo-parent/pom.xml