F4 GitHub Organziations
Table of Contents |
---|
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-exts
This organization is the home of non-core, extension Fedora4 projects, utilities, and ontologies that are actively maintained.
Current
NONE
Migrated
Notes:
...
fcrepo4-labs
...
- 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
...
fcrepo-
...
archive
This organization is the home of Fedora4 modules that are no longer supported.
Principles
- Core Fedora capabilities/projects are the set of components
Migrated
NONE from above
Plan
- Determine core Fedora capabilities/projects. These will be the set that call fcrepo4 home. Candidate list:
- Repository CRUD: LDP
- TransactionsBatch Atomic Operations
- 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 No dependencies from fcrepo4 projects to fcrepo4-exts or fcrepo4-labs
- Ensure dependencies Dependencies from fcrepo4-exts or fcrepo4-labs on fcrepo4 is are limited to kernel interfaces
- Factor fcrepo-transform out of fcrepo4 into an independent project
- For fcrepo4-exts projects, rename package names to either are org.fcrepo.exts or something unrelated to org.fcrepo<something-relevant>
- Each core capability area above should have its own separate ontologies, as appropriate
- Build TCKs for the Fedora core capabilities
...
Guidelines for fcrepo4-exts projects
Requirements
- The module is used by 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
- 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:
- The module be released to Maven Central
- The module has a parent pom of fcrepo-parent/pom.xml