Archive and tag repositories

gforcada · April 8, 2023, 2:44pm

I probably should have written it directly here rather than as GitHub issue, so here they go:

Archive more repositories?

opened 12:26AM - 04 Apr 23 UTC

We have +350 repositories that are __not archived__. ~100 of them have not be…en touched since 2018. I think is rather safe to archive them. Archiving means making them read-only, they still can be cloned, but no write operations (issues or PRs either? 🤔 ) would be allowed. This would mean that we _only_ have to try to tame the other ~250 still left 😅 This issue goes together with #73 With both put in motion, it would give us much more focus on where to spend the time, but also specially, signal to external/potential contributors where to NOT spend time on 🍀

github.com/plone/meta

Tag repositories?

opened 12:20AM - 04 Apr 23 UTC

gforcada

Following zopefoundation organization idea to put a `maintained` label to reposi…tories where ongoing maintenance support is expected, should we do something similar? i.e. _names totally up to discussion_ and an example: - `plone core`: `Products.CMFPlone` - `plone add-on`: `plone.app.mosaic` - `volto`: `plone.volto` (`volto` is an obvious choice as well 😆 ) - `plone classic ui`: `plonetheme.barceloneta` - `infrastructure`: `documentation`, `meta`... This way, given GitHub search UI, we could easily filter for repositories when searching for things, specially given that we have +350 repositories (already excluding archived ones).

The idea is to follow the zopefoundation steps and both tag our repositories, so we can filter them easily and put them som maintenance status to them, but also archive the ones that are not needed/used anymore.

Partially is my OCD playing with me, but organization and cleaning up is never a bad thing either I hope

Suggestions? Should I go ahead and ask for forgiveness?