doc: Clarify the Repository lifecycle#37
Conversation
Signed-off-by: Feynman Zhou <feynmanzhou@microsoft.com>
Signed-off-by: Feynman Zhou <feynmanzhou@microsoft.com>
TheFoxAtWork
left a comment
There was a problem hiding this comment.
Looks good, please make sure your governance outlines a supermajority and is linked here.
Signed-off-by: Feynman Zhou <feynmanzhou@microsoft.com>
|
Having the process outlined is goodness. Archiving a repo that's been dormant may not mean the project isn't useful for others to consume as reference. It may just be stable and doesn't need additional changes. In this case, archiving can indicate it's stable, and not taking additional changes, because there aren't any maintainers, or the project is simply stable. I'd also suggest adding text that a repo must have at least 30 days notice to its maintainers before archival is completed. Deleting a project is far more destructive and removes content that others may need. I'd suggest we clarify under what circumstances a project would be deleted, vs. archived. |
yizha1
left a comment
There was a problem hiding this comment.
Overall looks good. Just one comment.
Signed-off-by: Feynman Zhou <feynmanzhou@microsoft.com>
Signed-off-by: Feynman Zhou <feynmanzhou@microsoft.com>
Thanks @SteveLasker for the suggestions. I added a paragraph about the archival notice and removed the "Removal" section according to your inputs above. |
shizhMSFT
left a comment
There was a problem hiding this comment.
What about deleting, renaming, and transferring out a repository?
Signed-off-by: Feynman Zhou <feynmanzhou@microsoft.com>
Signed-off-by: Feynman Zhou <feynmanzhou@microsoft.com>
@shizhMSFT I added a section for Renaming. Deleting and transferring out a repository are not common cases so we could consider adding them in the future. Keep the content as minimum viable would be easier to review. |
Signed-off-by: Feynman Zhou <feynmanzhou@microsoft.com>
|
/cc @notaryproject/notaryproject-governance-maintainers to help review this PR. |
fix #36