Sourcecode @type definitions

[mnot]

The RFC Series Editor will maintain a complete list of the preferred values on the RFC Editor web site, and that list is expected to be updated over time.

This list is extremely hard to find, and the process for its maintenance isn't clear. Is there a reason we just don't establish an IANA registry for it and create an appropriate review process?

[jrlevine]

IANA registries are for parameters used by people who implement RFCs, not for our internal bookkeeping.
I agree the list could be easier to find but that should be fixable.

[mnot]

But people who write RFCs are implementing this RFC :)

[rjsparks]

Whatever the right noun is in the new RFC model, it's the RFC mumble that is responsible for maintenance. I would encourage that this list end up super easy to find and to suggest modifications to (rather than ask IANA to manage it for them). If we end up in a world where the RFC Editor uses github more, having this be in a repo looks attractive.

[jrlevine]

Github is a possibility although these lists are simple enough we could keep them in Hedgedoc.