> I'm eager to make use of the thought and energy that you and Lassi have brought to these ideas. I've been wanting an index like this for a long time, and I love the prospect of being able to contribute to Devdocs.io or something like it, too.

Heh, same here :D I too have that gift/curse of being easily excited.
Lots of energy and ambition but follow-through does not come naturally.
It's a good thing we have more measured people on board.

Since the energy is here let's take advantage of it while it lasts :) I
created a new GitHub organization, <https://github.com/schemedoc>, for
more general work on Scheme documentation, metadata, and collections /
APIs for that data.

The point would be to aggregate data about RnRS, SRFIs, implementation
and libraries into the same place, but (eventually) not be a primary
source for any of that stuff -- each of those things would be sourced
from its respective communities once those have stable social/technical
processes in place for producing parseable documentation and keeping it
up to date. In the meantime, we can collect scraped and manually
gathered data into that organization and explore how to best store and
access it.

To get started, I'll translate my tiny Python REST API server that runs
<https://schemedoc.herokuapp.com/> into Scheme. I'll also move my RnRS
scraper into that organization. I would suggest keeping the SRFI stuff
under the SRFI organizations (but having code under SchemeDoc to
download and it and include it into the total documentation collection).

IMHO it would be awesome if all Lisps (Scheme, Common Lisp, Emacs Lisp,
Clojure) could export and query documentation using the same format/API.
We are all using S-expressions anyway, with only slight variations.
Different communities could host host APIs and documentation sets with
their own social processes and infrastructure, but the public interface
(HTTP REST API and S-expressions) could easily be the same (well, the
technical aspects are easy, the social aspects not :D)