> However even a shared Google Sheet would suffice, and
> even allow for commenting if needed.

We could think about what to use to keep track of collaborative editing.

* Google Sheets is one possibility

* Or just GitHub issues/pull requests
   (I guess this would be my favorite approach since the tools
   are familiar and intergrate seamlessly with Git and CI servers,
   and it's easy to do "code reviews" using the GitHub UI.)

* Or we could just divide the SRFIs among ourselves
   (who edits which number) and merge the edited SRFIs
   to a shared master branch once done. The CI server
   would collect the versions in the shared master branch
   and draw up the dashboard based on that.

* We could have one GitHub repo for collecting all the edited
   SRFIs in this trial phase. Later, once the final HTML format is
   published and announced, we could start to use the official
   SRFI repos (one repo per document) to track edits via pull
   requests. GitHub has hooks to send each pull request to a CI
   server for checking, so this would provide a nice way for
   everyone to verify edits while they are in progress. Of course,
   a volunteer could also download the checking tool to their own
   computer if they want to check more often.

* We might be able to run the checking tool on AWS Lambda or
   some such run-a-function-on-demand service, since it doesn't
   need to keep state.