> I'm afraid that I don't understand.  Based on the subject line, it sounds
> like this would be for storing a registry of data types supported by the
> proposed serialization mechanism.  Do we really need more than a simple
> text file, or perhaps a Git repo, for that?

I have to agree with this. Git is ubiquitous, free, vendor-neutral,
simple and fundamentally decentralized: every time people make changes,
they effectively make distributed backups of the whole change history.

Storing the master list in a database is admirable from a dogfooding
perspective, but my confidence in our abilities and available
person-hours is not quite that high :) Storing the ground-truth for any
assets in Git is a good default unless there are some exotic
requirements - whether those assets are code, specs, websites,
documentation or configuration.

If we store it in Git we can also store it as S-expressions from the
get-go. It's really easy to generate reports and tools from that.

No strong opinion either way on Google Sheets.