Archiving my OEX packages

Over the last 9 years, I published more than 90 packages in OEX.
And over this time, conditions and environments changed.
In the beginning, there was

• no Docker
• no IPM/ZPM
• no embedded Python, no AI
• Caché, Ensemble, CSP, ZEN, .... were dominating

As time changed, also product versions and external languages changed.
Adjustment of a few packages was no issue in the beginning,
and was a matter of support quality to my "consumers".

With the actual volume, I see no way to keep this target up for all my packages.
and based on the quality checks, I have the impression it is not just my problem.
Recent changes caused enough issues just by version updates.

So I proposed the Idea of a DEPRECATED label to OEX packages

It would be fair to signal to other users of OEX that there is no
intention to do any maintenance for a package.
Also, as a kind of warning, if it is used.

In addition, a DEPERCATED package should be free for
adoption and reworking, and eventually fixing
by some other member of the community.

There was almost no echo. 
Actually, my only option was to unpublish it. ~90 packages in total.
A lot of once well-working code was unavailable that could be an
example for beginners or a source of some tricks.
So I changed my mind and marked packages that could be useful,

 no maintenance or update

As a temporary workaround, also using GitHub Archiving feature
to prevent changes by accident. 

So I expect most of these 90 packages to reappear over time.
And with them also all comments and related articles.
I understand this as a kind of museum to show how easy
or complicated the environment once was. 
And without ignoring past achievements.