Closed gforcada closed 1 year ago
We could update their README
files just before archiving them by mentioning how to ask to get a repository active again.
How should that go? ๐ค
This repository is archived, if you consider using it again,
please refer to XXX to get in unarchived.
Of course the XXX
should be cleared up ๐
IMHO we could point users to https://community.plone.org so we have a safe space to handle those requests. Polluting even more CMFPlone seems like a not so much of a good idea to me.
This way, we point users to newer approaches (squid -> varnish recipes, as a simple example, or most of the js packages -> mockup) as a solution, rather un-archiving a repository. ๐ค
@gforcada Can you show a list of the repositories that would be archived? If I see the specific names it might remind me if some of them should still be active for some reason.
I would suggest the following modification. I would assume the task would fall to the AI Team.
This repository is archived and read only.
If you want to unarchive it, then post to the [Admin & Infrastructure (AI) Team category on the Plone Community Forum](https://community.plone.org/c/aiteam/55).
Thanks @stevepiercy for the suggestion โจ
@davisagli a first quick list might be:
Those are the repositories that have not been modified for the longest.
One can go to the Repositories
tab in plone
organization, filter by archived:false
and go to the last pages ๐
@gforcada +1, that list makes sense to archive
@davisagli thanks! all of them archived ๐งน โจ
May I ask if you agree on the following batch?
@gforcada Yep, looks all right with me
@davisagli thanks! archived them all ๐งน ๐๏ธ
A last short one and I would be happy about it for a while ๐
@gforcada go for it
I would have suggested opening an issue in plone/meta
if someone wants to unarchive, but I am too late. :-D
Plone 5.2 is out of maintenance in October this year, and out of security support one year later. One of those would be a good time to archive Products.Archetypes
and friends. I suppose this year would be fine: if we need a security release of such a product, we can always unarchive.
We have +350 repositories that are not archived.
~100 of them have not been 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 ๐