Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Determine how project lifecycle will be handled #8

Closed
chipchilders opened this issue Sep 25, 2020 · 3 comments
Closed

Determine how project lifecycle will be handled #8

chipchilders opened this issue Sep 25, 2020 · 3 comments
Assignees
Labels
stale An issue that has not had activity in some time, but that still needs some discussion

Comments

@chipchilders
Copy link
Contributor

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).

@loewenstein
Copy link

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

@chipchilders
Copy link
Contributor Author

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.

@chipchilders chipchilders self-assigned this Oct 23, 2020
@AP-Hunt
Copy link
Contributor

AP-Hunt commented Dec 6, 2022

Closing off as no longer relevant

@AP-Hunt AP-Hunt closed this as completed Dec 6, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
stale An issue that has not had activity in some time, but that still needs some discussion
Projects
Status: Done
Development

No branches or pull requests

3 participants