Conformance: a bottom-up approach Lassi Kortela (14 May 2024 15:13 UTC)
Re: Conformance: a bottom-up approach Antero Mejr (14 May 2024 19:26 UTC)
Organization and tooling, etc. Lassi Kortela (14 May 2024 19:43 UTC)
Other Scheme domains Lassi Kortela (14 May 2024 19:58 UTC)
Re: Other Scheme domains Antero Mejr (14 May 2024 21:47 UTC)
Re: Other Scheme domains Andrew Whatson (15 May 2024 01:27 UTC)
PreScheme and scsh sites Lassi Kortela (15 May 2024 11:23 UTC)
Re: PreScheme and scsh sites Andrew Whatson (15 May 2024 15:20 UTC)
Re: PreScheme and scsh sites Lassi Kortela (15 May 2024 17:02 UTC)

Re: Conformance: a bottom-up approach Antero Mejr 14 May 2024 19:26 UTC

Lassi Kortela <xxxxxx@lassi.io> writes:

> To find some common ground re: "does an implementation qualify as Scheme", how
> about building a conformance chart from the bottom up?
>
> Split RnRS into a list of features, and for each feature, determine useful
> conformance levels.

I like this idea. At the top level, there can be "gold standard"
implementations: those that comply closely to the R6/R7RS spec + the
most SRFIs, like Gauche and STklos.

As a tangent, I think doing the work to maintain better documentation
may be more difficult than it needs to be, because the info is split
across 8+ repositories and 3 Github organizations (schemedoc, schemeorg,
schemeorg-community). Also, building the documentation requires having
many different Scheme implementations installed (like the srfi-metadata
table).

Do you think there would be value in a web infrastructure consolidation
to a single Github organization, and decide on a single Scheme
implementation to build it? The website (and Scheme documentation in
general) seems a bit fragmented/siloed. Oftentimes I need to switch
between the r7rs.org website, Gauche website, and SRFI website just to
write basic code.