Closed a2379 closed 3 months ago
Thank you for another patch!
I think it would be good to remove unmaintained implementations to make room for new ones.
Agreed. (But see below.)
The removal criteria was no mailing list or repository activity in 3+ years, or the maintainer posts notice saying the implementation is unmaintained.
These are reasonable criteria.
This brings in a wider issue: We should have a consistent way to categorize implementations as active or inactive across scheme.org. I advocate for keeping the inactive implementations represented (since people have already put in the effort to gather information about them), but placing them e.g. in separate tables or on separate pages.
Can you start a thread on the schemeorg mailing list about this?
(An earlier issue where the same issue was brought up by @jpellegrini is https://github.com/schemedoc/surveys/pull/53.)
Another issue is that the SRFI support table is hard to read in general. It's just a grid of checkmarks with mouse-over pop-up tips.
We should probably add some text. Break it down with subheadings, categorize the SRFIs - things like that.
Added a note at the bottom of the table indicating the removal criteria, as per the discussion on the mailing list: https://srfi-email.schemers.org/schemeorg/msg/24917138/
(p
(b "* On removals: ")
"Implementations will be removed from this table if either:"
(br)
(ol
(li "There is no mailing list or repository activity for three or more years from the date this
table was generated.")
(li "Their maintainer indicates that the implementation is unmaintained.")))
Let's write a complete policy (and a list of currently maintained implementations) and place it at some prominent central place on scheme.org.
I've merged it. Would someone else please complete the process? I don't have Racket installed, and don't have time right now.
I'll do it.
I think it would be good to remove unmaintained implementations to make room for new ones.
The removal criteria was no mailing list or repository activity in 3+ years, or the maintainer posts notice saying the implementation is unmaintained.
By that criteria Unsyntax is on the borderline of removal. The table is missing Cyclone and Jazz Scheme, both of which seem to be active.