>>     A library collection would basically be the same thing, but putting
>>     all libraries in a monorepo with collective ownership instead of
>>     separate repo per library, each owned by one person.
>>
>> The trouble with a monorepo is "once mono, always mono"
>
> That would be exactly desirable for Scheme Live. We have to be able to
> change not only modules, but module boundaries. Otherwise we're blinded
> to important possibilities in the design space.
>
This is the approach used by Gerbil Scheme, that is a monorepo of
plenty of libraries on top of a Racket-like module system on top of
Gambit Scheme (but has been retargeted in the past and could be
retargeted again), and to a point used by my Gerbil-Utils which is a
set of more experimental extensions to Gerbil, that I use a staging
area before inclusion to Gerbil itself (when, in my copious free time,
I can get the stuff documented).

A lot of things could be done to make Gerbil nicer, more portable,
more coherent, etc.—but it's a great starting point.

—♯ƒ • François-René Rideau • Co-Founder and CEO, MuKn.io
Every great truth begins as heresy and ends as superstition.
        — Thomas Henry Huxley