tac
tac copied to clipboard
ossf
Deprecation Policy for archiving projects, SIGs, WGs
We may want to consider a deprecation policy for projects, SIGs , or WGs where possible. This would aid in the justification for archiving and allow for a proposed date to officially archive.
Agreed. I think we should make sure we record why a project, SIG, etc. gets archived. It will help in the future if someone wants to reintroduce something similar it can help us understand if it will be more successful, or if something new has come up that would mean a group that had "finished" its work should restart on something new.
We may need to beef that up but we already have some of this built into the TI lifecycles:
https://github.com/ossf/tac/blob/main/process/working-group-lifecycle.md#to-become-archived https://github.com/ossf/tac/blob/main/process/project-lifecycle.md#archived https://github.com/ossf/tac/blob/main/process/sig-lifecycle.md#to-become-archived
I think we should make sure we record why a project, SIG, etc. gets archived.
Seems reasonable. I encourage people to allow the answer "no one was found who was willing to maintain it". In such cases, if we do later find maintainers, the problem is clearly resolved :-).
I think we should make sure we record why a project, SIG, etc. gets archived.
Seems reasonable. I encourage people to allow the answer "no one was found who was willing to maintain it". In such cases, if we do later find maintainers, the problem is clearly resolved :-).
The process to archive a TI involves submitting a PR against the TAC repo with the appropriate template which explicitly requests the reason. See:
https://github.com/ossf/tac/blob/main/process/templates/PROJECT_NAME_archived_stage.md https://github.com/ossf/tac/blob/main/process/templates/WG_NAME_archived_stage.md https://github.com/ossf/tac/blob/main/process/templates/SIG_NAME_archived_stage.md
Are the templates @lehors points out sufficient, or so we also need a short process written up so folks understand how to use them?
I think between the process doc (e.g. https://github.com/ossf/tac/blob/main/process/working-group-lifecycle.md#to-become-archived) and the template (e.g. https://github.com/ossf/tac/blob/main/process/templates/WG_NAME_archived_stage.md) we have sufficient artifacts.
Lets use the process in place (https://github.com/ossf/tac/blob/main/process/working-group-lifecycle.md#to-become-archived), gather feedback, and iterate from there.