Lassi Kortela <xxxxxx@lassi.io> writes:

| Of course, we can try to hasten the emergence of such a standard
by auto-converting RnRS arglists and perhaps writing a SRFI to
specify a standard documentation dump format for implementations
(after surveying the existing implementations to find out what
kind of dump format would be easiest for them; and whether any
implentors would be interested in the project in the first
place). All that would be left then would be libraries. With luck
they could use the same dump format as implementations (but
frankly I have no idea what I'm talking about re: library
documentation).

That's a great idea.  Let's put it on the to-do list.

| IMHO the only tenable CI solutions are:
|
| 1. Each SRFI in its own repo, CI using webhook server.
| 2. All SRFIs in one repo, CI using Travis.
|
| If both of those are a no-go, I would just leave out CI and only
run the tool manually as you suggest.

Rather than declare them no-go, let's just postpone the decision
and see how things go.