You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the current CFF governance process, the PMC Council is responsible for the lifecycle of PMCs, PMCs are responsible for the lifecycle of Projects, and Projects are responsible for the lifecycle of repositories.
We need to think about the incubation > active > attic model for lifecycle, and decide how repos will flow through that process (if we keep a lifecycle model).
The text was updated successfully, but these errors were encountered:
I'd say that we want a repo lifecycle. It should be easy to get an incubation repo within a working group and we should definitely clean up unmaintained repositories.
New working groups will have to be sponsored by TOC. I imagine that most new WGs will be seeded from within existing ones. I.e. people will search for an incubation place and approach the TOC only when incubation was "successful".
Update GOVERNANCE.md to include simple lifecycle statement of incubation, active, attic. Also be clear about the difference between extension and core. Core needs to be something that will be reflected in conformance tests for distro certification. However, leave the final structure of lifecycle steps, naming, etc... to the TOC.
In the current CFF governance process, the PMC Council is responsible for the lifecycle of PMCs, PMCs are responsible for the lifecycle of Projects, and Projects are responsible for the lifecycle of repositories.
We need to think about the incubation > active > attic model for lifecycle, and decide how repos will flow through that process (if we keep a lifecycle model).
The text was updated successfully, but these errors were encountered: