We may need further registries, for example for standardized feature
identifiers that extend the small list in R7RS-small.

I would have proposed to use the SRFI process for it. Whenever there
is a major change in the registry, an updated SRFI (only containing
that registry) is issued while the previous version will be withdrawn.

I think it is simpler or safer than inventing a new process, whose
life may depend on the lifetime of the git repo chosen.

Marc

Am Fr., 31. Juli 2020 um 10:14 Uhr schrieb Lassi Kortela <xxxxxx@lassi.io>:
>
> 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.
>
> Harold and I thought xxxxxx@srfi.schemers.org would be a fitting
> name for the mailing list. The SRFI domain is currently by far the
> easiest place for us to set up new Scheme mailing lists, and Arthur is
> good at administering them.
>
> The Git repo could be under
>
> - https://github.com/scheme-requests-for-implementation
> - https://github.com/srfi-explorations
> - some other organization
>
> We can make subdomains under scheme.org, so we could also set up a
> simple static page at https://registry.scheme.org/