Lassi Kortela <xxxxxx@lassi.io> writes:

> IMHO the ideal approach would be a SRFI that specifies a metadata file shipped
> in Scheme implementations' source release tarballs. We could then download all
> the latest tarballs, read the metadata files, and use that data to generate
> parts of the website.

IMO this would be best done in a package.scm/json file, which would
specify dependencies, documentation locations, etc. It could also be
used to build and install the implementation (including inside
containers) in a package-manager-nonspecific way.

There's already the "Snow.md" spec in the R7RS large repo, and I started
my own package management SRFI (links below).  I agree that a package
management/metadata SRFI is desperately needed. But it would need buy-in
from the likes of Guix, Akku, etc.

If libraries shipped a package.scm as well, then scheme.org could become
a repository for both implementation and library documentation, without
having to update it by hand.

https://github.com/johnwcowan/r7rs-work/blob/master/Snow.md
https://git.antr.me/srfi-package/tree/srfi-2XX.html