Deprecating/Archiving Repos

[michael-ciniawsky]

There needs to be a standard process for admis when to archive a repo and how to do it. Are we going to archive them in webpack-contrib or do we prefer to make a separate org for that purpose. The separate org approach has the benefit that we are able to deprecate a repo first and ask for new maintainers/volunteers taking over ownership before finally archiving it otherwise. It's also imho cleaner and reduces the noise in webpack-contrib

[michael-ciniawsky]

We also need to track potential candidates for depreciation and archivation somehow and find consensus

[TheLarkInn]

@evilebottnawi and myself just had a discussion about this.

So far I think there is at least a few repo's that could use an archive:

-[ ] webpack-contrib/gzip-loader (92 people)
-[ ]

My idea is this:

1. In front of the name of repo, mark that this is deprecated, add this same information to the readme in giant H1 markdown. (#)
2. We set an explicit deprecation date in README, this will be 60 days
3. Archive Repo (but do not delete)
4. The first 2 steps will have to be via a PR approved by owners on webpack-contrib.

[TheLarkInn]

Thoughts @d3viant0ne?