- Prepared by Herbert Damker for the TSC on 2024-08-22
- Referenced within issue: ...
...
- Previous proposal hasn't considered the split between API Repository and CAMARA Sub Projects as introduced with https://github.com/camaraproject/Governance/issues/142
- Sandbox / Incubated / Graduated will now be defined for API Repositories, not Sub Projects
- Proposed relation of API Repositories and CAMARA Sub Project
- Sub Projects are (as currently defined) consisting of one or multiple API repositories
- the Maintainers of the Sub Project are the union of the Maintainers of the API repositories belonging to the Sub Project
- existing Sub Projects can maintain a mix of API Repositories on different maturity levels and can either propose new API repositories themselves or accept API repositories as part of their Sub Project
- NEW: Sandbox API repositories can initially exist independent of a Sub Project
- that will postpone the the decision about the inclusion of an API into a Sub Project vs the creation of a new Sub Project to the Incubation, where much more information about the API and already and initial version is available
- Sandbox API repositories are encouraged to get accepted by existing Sub Project
- Projector to build up the necessary prerequisites to be able to apply for the creation of a new CAMARA Sub Project during Incubation
- Sub Projects are (as currently defined) consisting of one or multiple API repositories
- The maturity level of an API Repository should give the audience a clear indication in which life cycle phase the contained APIs are
...
The purpose of a Sandbox API Repository is to describe, develop and define the a proposed API openly within the CAMARA community. The creation of a new Sandbox API Repository will be decided by the API Backlog Working Group, based on either a proposal for a new API development from a CAMARA participant or a enhancement proposal from an existing CAMARA Sub Project. The proposal will be presented in a form as defined by the API Backlog Working Group
...