...

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

      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 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 X-number of installations (2? 3? 4?)3 or more installations
2. The module has two or more formally publicized "owners" 
3. The module has an integration-test framework in-place
4. The module has a unit-test framework in-placeThe module has a package namespace of org.fcrepo.<something-relevant> (if java)

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 (if java)

...