> From: Lassi Kortela <xxxxxx@lassi.io>
> Date: Friday, July 31, 2020 3:14 AM
>
> Earlier this week we discussed on the SRFI 198 mailing list that there
> should be a community-wide registry for foreign error types. The set of
> known error types is necessarily evolving so it can't be in the SRFI. It
> will surely be useful to define other evolving sets of things in future
> SRFIs.
>
> To that end, we should establish some kind of lightweight registry for
> identifiers and other such things. Harold suggested, and Arthur and I
> agreed, that it could be a Git repo + low-traffic mailing list.
> Submissions could be via pull request / mailing list, quite informal.

We'll probably end up with a "low-traffic mailing list", but a real
forum would likely be better for this sort of thing, but way too much
effort for us, at least today. But how about the following:

Submissions as pull requests to the current master repo would work
well, you just need discipline about putting discussions in the mailing
list ... or scrape the repo provider's pull comments when the
decisions is made about the pull request, and post that as a digest to
the mailing list.  That would help keep the traffic lower, not bothering
people about registries they have no interest in, except for the initial
announcement, the final digest, and whatever the participants decide
should go to the mailing list anyway.

For "quite informal", from experience elsewhere I recommend selecting
a small pool of gatekeepers, and OKing additions and changes that any
two of them agree upon.

> [ Mailing list specifics. ]
>
> The Git repo could be under....
>
> We can make subdomains under scheme.org, so we could also set up a
> simple static page at https://registry.scheme.org/

My idea was first that a page we control would direct people to the
canonical copy/copies of the registry data.  In this case, one or
more git repoes hosted by different organizations, or just switch as
needed if it comes to that.

That way SRFIs can refer to that page, and with the expansion in
ambition, a particular git managed file or subdirectory listed on it.

- Harold