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"?

...

fcrepo4-

...

labs

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

Current

...

fcrepo-

...

archive

This organization is the home of Fedora4 modules that are no longer supported.

Principles

1. Core Fedora capabilities/projects are the set of components

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. TransactionsBatch Atomic Operations
   3. 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

      )
   4. Authorization: WebAC ? (Design - WebAccessControl Authorization Delegate)
   5. Fixity
2. Ensure no No dependencies from fcrepo4 projects to fcrepo4-exts or fcrepo4-labs
3. Ensure dependencies 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 Each core capability area above should have its own separate ontologies, as appropriate
7. Build TCKs for the Fedora core capabilities

...

Guidelines for fcrepo4-exts

...

projects

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
5. The module should contain documentation in GitHub release notes of the specific version of Fedora 4 its integration tests build against, when applicable

Considerations

For Java projects that are intended to be shared or used via Maven machinery, it is recommended that:

...