Getting Multibase ready for IETF review (align with IANA terminology and registry governance style)

.github/ISSUE_TEMPLATE/BUG-REPORT.yml

@@ -0,0 +1,31 @@
+name: "Bug Report - documentation or registry"
+description: Report possible bugs in multibase spec, process docs, and/or the multibase registry.
+title: "🐛 [DOC/PROCESS BUG] - <title>"
+labels: [
+  "bug"
+]
+body:
+  - type: textarea
+    id: description
+    attributes:
+      label: "Description"
+      description: Please enter an explicit description of your issue,  
+      placeholder: Short and explicit description of your incident, ideally with commit-specific link to lines
+    validations:
+      required: true
+  - type: input
+    id: reprod-url
+    attributes:
+      label: "Reproduction URL"
+      description: Please enter your GitHub URL to provide a reproduction of the issue
+      placeholder: ex. https://github.com/multiformats/multibase/
+    validations:
+      required: true
+  - type: textarea
+    id: context
+    attributes:
+      label: "Context"
+      description: Please provide additional context
+      placeholder: "Context or external links needed to explain the possible mistake"       
+    validations:
+      required: true

.github/ISSUE_TEMPLATE/NEW-IMPLEMENTATION.yml

@@ -0,0 +1,55 @@
+name: "Interest in Implementing - New Multibase Library or System"
+description: Express interest in possible new multibase library or system
+title: "📚 [NEW PROJECT] - <title>"
+labels: [
+  "ideation"
+]
+body:
+  - type: input
+    id: project-name
+    attributes:
+      label: "Name of Project"
+      description: Name this library or system
+      placeholder: (language-)Multibase(-usecase), for example
+    validations:
+      required: false
+  - type: checkboxes
+    attributes:
+      label: "Have read contributing"
+      description: I have read the [contributing](https://github.com/multiformats/multiformats/blob/master/contributing.md) document
+      options:
+      - label: I read it!
+    validations:
+      required: true
+  - type: textarea
+    id: problem_statement
+    attributes:
+      label: "Description of parsing, sniffing, or encoding problem solved"
+      description: Please describe the problem solved by a new multibase library or system depending on multibase codecs
+      placeholder: Feel free to provide links for context and use-case descriptions, and how this problem is not solved by existing multi-formats entries or mini-registries
+    validations:
+      required: true
+  - type: textarea
+    id: prior_art
+    attributes:
+      label: "Description of relevant prior art and status quo"
+      description: Please describe relevant prior art and how this is use-case functions today
+      placeholder: Links welcome
+    validations:
+      required: true
+  - type: textarea
+    id: solution_and_rationale
+    attributes:
+      label: "Proposed solution and rationale"
+      description: Please describe at a high level what you are exploring building and current open research questions
+      placeholder: Detail welcome
+    validations:
+      required: true
+  - type: textarea
+    id: questions
+    attributes:
+      label: "Any further questions or requests"
+      description: Anything else you'd like to ask the maintainers or community?
+      placeholder: ok to leave blank!
+    validations:
+      required: false

.github/ISSUE_TEMPLATE/NEW-REGISTRATION.yml

@@ -0,0 +1,69 @@
+name: "New Registration"
+description: Express interest in registering a new encoding
+title: "📚 [NEW REGISTRATION] - <title>"
+labels: [
+  "Registration"
+]
+body:
+  - type: input
+    id: encoding-name
+    attributes:
+      label: "Name of encoding"
+      description: Name this library or system
+      placeholder: acronyms and abbreviations are fine
+    validations:
+      required: false
+  - type: checkboxes
+    attributes:
+      label: "Have read contributing"
+      description: I have read the [contributing](https://github.com/multiformats/multiformats/blob/master/contributing.md) document
+      options:
+      - label: I read it!
+    validations:
+      required: true
+  - type: checkboxes
+    attributes:
+      label: "Have checked table"
+      description: I have reviewed the [multiformats mega-table](https://github.com/multiformats/multicodec/blob/master/table.csv) to assess viable sub-namespace for a registry if applicable
+      options:
+      - label: I read it!
+  - type: input
+    id: codepoint
+    attributes:
+      label: "Proposed codepoint"
+      description: Please put here the prefix in the target encoding. By tradition, the highest binary value in the encoding alphabet works well and has a built-in mnemonic if it doesn't conflict with any other entries
+      placeholder: x
+    validations:
+      required: true
+  - type: input
+    id: varint-value
+    attributes:
+      label: "Proposed varint value for registration in multiformats"
+      description: Please put here the UTF-8 value that corresponds to that target encoding, for inclusion in the multiformats table, formatted as an [unsigned varint](https://github.com/multiformats/unsigned-varint)
+      placeholder: See mf/unsigned-varint
+    validations:
+      required: true
+  - type: textarea
+    id: use-case
+    attributes:
+      label: "use-case"
+      description: Please describe the possible use-cases where this additional codec would be helpful, where this encoding is used currently in the wild, etc.
+      placeholder: Feel free to provide links for context and use-case descriptions
+    validations:
+      required: true
+  - type: textarea
+    id: specification
+    attributes:
+      label: "Description of relevant prior art and status quo"
+      description: Please describe relevant prior art and, if already specified in a static public document, the algorithms and configurations needed to deterministically encode/decode
+      placeholder: Links welcome
+    validations:
+      required: true
+  - type: textarea
+    id: solution_and_rationale
+    attributes:
+      label: "Proposed solution and rationale"
+      description: Please describe at a high level what you are exploring building and current open research questions
+      placeholder: Detail welcome
+    validations:
+      required: true

.github/ISSUE_TEMPLATE/config.yml

@@ -0,0 +1,5 @@
+blank_issues_enabled: true
+contact_links:
+  - name: Protocol Labs Vulnerability Disclosure Team
+    url: mailto:[email protected]
+    about: Please do NOT open issues related to security of implementations or spec here without contacting the IPFS security team first.