Email list hosting service & mailing list manager

Future of Lassi Kortela (12 Jan 2023 16:13 UTC)
Re: Future of Arthur A. Gleckler (12 Jan 2023 19:27 UTC)
Re: Future of Lassi Kortela (12 Jan 2023 21:47 UTC)
Re: Future of Arthur A. Gleckler (12 Jan 2023 21:51 UTC)
Re: Future of Jakub T. Jankiewicz (13 Jan 2023 15:00 UTC)
Re: Future of Arthur A. Gleckler (14 Jan 2023 05:28 UTC)

Future of Lassi Kortela 12 Jan 2023 16:13 UTC

For the longest time, I've been trying to think of what to do with the
subdomain It could be taken in a number of directions
with no clearly correct answer.

One idea was to collaboratively write a canonical Scheme manual and put
it there. That idea now seems impractical to me. There are no
indications that we will be able to cover enough ground to be
comprehensive. It's probably unwise as well, since there is lots of
existing Scheme documentation (including about stuff that isn't tied to
one implementation) and it would be convenient to gather that somewhere.

What I suggest we do is turn into a
style documentation browser featuring as much existing documentation as
we can find, all browsable and searchable using a unified interface. How
does this sound?

We can and should still try to write new documentation (e.g. but at the docs site it would be one
offering among many.

IMHO the best outcome of all is if we can convince the authors of
existing Scheme docs to merge their work into bigger documents. Over
time we'd end up with fewer manuals that are more thorough. This seems
like a win for users. But this kind of agreement rarely happens among
authors, so it's not wise to bet on it. Let it occur "organically" if
and when it does. Don't bet the docs site on it.