Closed dsyme closed 2 years ago
project matures and is used by thousands, or ends up archived.
@dsyme Can we define rules when project may be archived by backup admin?
For example :
Backup admin may decide to archive projects after 3-5 years of primary admin absence (no activity in issues and/or commits). During the archiving, the project is renamed (prefixed by zzarchive-
) and marked as read-only on GitHub.
Backup admin may decide to archive projects after 3-5 years of primary admin absence (no activity in issues and/or commits). During the archiving, the project is renamed (prefixed by zzarchive-) and marked as read-only on GitHub.
Yes, I will add that, but I will make it 1 year minimum with no maximum. Sometimes silly projects get created that we know we can archive quite quickly.
Yes, I will add that, but I will make it 1 year minimum with no maximum. Sometimes silly projects get created that we know we can archive quite quickly.
Done via direct commit to master, thanks!
This is a set of updates to clarify current project policy for "fsprojects" as agreed by @sergey-tihon and myself.
cc @sergey-tihon