Initial process upgrades for Multiformats registry group and org

.github/ISSUE_TEMPLATE/BUG-REPORT.yml

@@ -0,0 +1,31 @@
+name: "Bug Report - documentation or registries"
+description: Report possible bugs in multiformats spec, process docs, and/or the mf-wide 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/multiformats/
+    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-PROJECT.yml

@@ -0,0 +1,61 @@
+name: "Propose New Multi- Project"
+description: Express interest in possible new multiformats project
+title: "📚 [NEW PROJECT] - <title>"
+labels: [
+  "ideation"
+]
+body:
+  - type: input
+    id: name
+    attributes:
+      label: "Name"
+      description: Name this multi- in a word, if you can
+      placeholder: Multi-thingy for now
+    validations:
+      required: false
+  - type: checkboxes
+    attributes:
+      label: "Have read contributing"
+      description: I have read the [contributing](./contributing.md) document
+      options:
+      - label: I read it!
+    validations:
+      required: true
+  - type: textarea
+    id: problem_statement
+    attributes:
+      label: "Description of problem solved"
+      description: Please describe the problem solved by a mini-registry within multiformats
+      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 a new multi- registry or new tooling for existing registries would enable and discuss tradeoffs and rationale (for new sub-registry in particular)
+      placeholder: Detail welcome
+    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: textarea
+    id: registry_design
+    attributes:
+      label: "Proposed sub-namespace"
+      description: Please describe the range of entries your project would need and any considerations about the greater multiformats namespace
+      placeholder: Registration space need not be contiguous and one entry in the macro-registry can be annotated differently in multiple sub-registries
+    validations:
+      required: true

.github/ISSUE_TEMPLATE/TRANSLATION-ANNOUNCEMENT.yml

@@ -0,0 +1,21 @@
+name: "Translation Announcement"
+description: Announcement of intent to translate
+title: "📚 [TRANSLATION/LOCALIZATION] - <title>"
+labels: [
+  "community"
+]
+body:
+  - type: textarea
+    id: description
+    attributes:
+      label: "Language or Localization offered"
+      description: Please describe the language and/or alphabet/localization standard you would like to target for a translation and/or localization of this specification.
+      placeholder: ISO codes always nice but not required!
+    validations:
+      required: true
+  - type: checkboxes
+    attributes:
+      label: "Want help"
+      description: Check this box if you'd like potential helpers tagged into the thread for review.
+      options:
+      - label: Would collaborate!

.github/ISSUE_TEMPLATE/config.yml

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

README.md

@@ -7,7 +7,19 @@
 
 > The main repository for discussing multiformats
 
-Currently, we have the following formats. More formats are being discussed and worked on.
+Multiformats is a set of self-describing protocol values. These values are
+foundational in that they are low-level building blocks for both data and
+network layers of the composable protocols making up IPFS, IPLD, libp2p, and
+many other decentralized data systems. This repository's issues and pull
+requests are currently the primary venue for the coordination between the
+various registries making up the group, each of which is separately being
+hardened as specifications and public, formal registries over time.  See
+[contributing.md][./contributing.md] for more details on governance and process.
+
+## Current Registries
+
+Currently, we have the following formats, each of which corresponds to a
+specification and a registry. More formats are being discussed and worked on.
 
 | Repo | Captain | Status | IETF |
 |------|---------|--------|------|
@@ -26,54 +38,79 @@ See the project directory, below, for implementations and other related reposito
 
 ## Table of Contents
 
-- [Background](#background)
-  - [An Example: Multihash](#an-example-multihash)
-  - [A note on the word Multiformats](#a-note-on-the-word-multiformats)
-- [Project Directory](#project-directory)
-  - [Protocols](#protocols)
-  - [Protocols in Progress](#protocols-in-progress)
-  - [Implementations](#implementations)
-    - [Go Implementations](#go-implementations)
-    - [JavaScript Implementations](#javascript-implementations)
-    - [Other Implementations](#other-implementations)
-  - [Other Repositories](#other-repositories)
-- [Contribute](#contribute)
-- [License](#license)
+- [multiformats](#multiformats)
+  - [Current Registries](#current-registries)
+  - [Table of Contents](#table-of-contents)
+  - [Background](#background)
+    - [A note on the word Multiformats](#a-note-on-the-word-multiformats)
+  - [Project Directory](#project-directory)
+    - [Implementations](#implementations)
+      - [Multiaddr Implementations](#multiaddr-implementations)
+      - [Multihash Implementations](#multihash-implementations)
+      - [Multicodec Implementations](#multicodec-implementations)
+      - [Other Implementations](#other-implementations)
+    - [Other Repositories](#other-repositories)
+  - [Maintainers](#maintainers)
+  - [Contribute](#contribute)
+  - [License](#license)
 
 ## Background
 
-Every choice in computing has a tradeoff. This includes formats, algorithms, encodings, and so on. And even with a great deal of planning, decisions may lead to breaking changes down the road, or to solutions which are no longer optimal. Allowing systems to evolve and grow is important.
+Every choice in computing has a tradeoff. This includes formats, algorithms,
+encodings, and so on. And even with a great deal of planning, decisions may lead
+to breaking changes down the road, or to solutions which are no longer optimal.
+Allowing systems to evolve and grow is important.
 
-Multiformats is a collection of protocols which aim to future-proof systems, today. They do this mainly by allowing data to be self-describable. This allows interoperability, protocol agility, and helps us avoid lock in. Currently, our protocols (both works in progress and implemented) cover the following areas:
+Multiformats is a collection of protocols which aim to future-proof systems,
+today. They do this mainly by allowing data to be self-describable. This allows
+interoperability, protocol agility, and helps us avoid various forms of lock-in.
+Currently, these interlocking protocols (both works in progress and implemented)
+cover the following areas:
 
 - [multiaddr](https://github.com/multiformats/multiaddr): network addresses
 - [multibase](https://github.com/multiformats/multibase): base encodings
 - [multicodec](https://github.com/multiformats/multicodec): serialization codes
-- [multigram](https://github.com/multiformats/multigram): protocol negotiation and multiplexing over datagrams
+- [multigram](https://github.com/multiformats/multigram): protocol negotiation
+  and multiplexing over datagrams
 - [multihash](https://github.com/multiformats/multihash): cryptographic hashes
 - [multikey](https://github.com/ipfs/specs/issues/58): cryptographic keys and artifacts
 - [multistream](https://github.com/multiformats/multistream): stream wire protocols
-- [multistream-select](https://github.com/multiformats/multistream-select): Friendly protocol multiplexing.
-
-The self-describing aspects of the protocols have a few stipulations:
-
-- they must be in the value (not passed in out of band, in function calls, implicit choices, or documentation);
-- they must be compact and have a binary-packed representation (as opposed to a sparser encoding) or they will hinder performance;
-- they must have a human readable representation.
-
-Several of the multiformats are stable, and we're working on the others. We are trying to prioritize their usage as soon as possible. What they offer -- protocol interoperability and future-proofing --  would have real-world consequences.
-
-Towards that end, we are encouraging implementations of these protocols; if you know of any, please link them here (or add them to the organization!).
+- [multistream-select](https://github.com/multiformats/multistream-select):
+  Friendly protocol multiplexing.
+
+Several of the multiformats are stable, and work on the others is ongoing.
+Implementers and refiners of the drafts of any one of these registries or their
+tooling are welcome to [contribute][./contributing.md], without needing to
+understand deeply or track progress on the others. Across these otherwise quite
+different use-cases and mechanisms, the self-describing aspects of the protocols
+have a few stipulations in common:
+
+- the "prefixes" use to self-describe a value must be inline with the value (not
+  passed out-of-band, in function calls, implicit choices, or documentation);
+- they must be compact and have a binary-packed representation (as opposed to a
+  sparser encoding) or they will hinder performance;
+- they must have a human-readable representation.
 
 ### A note on the word Multiformats
 
-Multiformats is the name for the organization, but it can also be used to refer to protocols; for instance, in the sentence "Use one of the multiformats". Formats is interchangeable with protocols, here. We try to capitalize Multiformats when it refers to the organization, on GitHub.
+`Multiformats` is the name for the community (and the "organization" in GitHub's
+actor model), but `multiformats` can also be used to refer to protocols; for
+instance, in the sentence "Use one of the multiformats". Formats is
+interchangeable with protocols, here, as each format is designed in tandem with
+one or more protocols which handle those self-describing values centrally. We
+try to capitalize Multiformats when it refers to the organization.
 
 ## Project Directory
 
 Below, a list of all of the projects in the Multiformats organization is listed.
 
-**Captains** are the active leads for each project. Their responsibilities are to make sure that issues and pull requests are attended to in a timely manner, and general upkeep. If you have questions about a repository, or need feedback, please contact them as appropriate.
+**Captains** are the active leads for each project. Their responsibilities are
+to make sure that issues and pull requests are attended to in a timely manner,
+and general upkeep. If you have questions about a repository, or need feedback,
+please contact them as appropriate.  If any of the specifications defining these
+formats are formalized and finalized in a standards body, these captains may
+continue on as Registrars of the table of entries which can keep growing after
+stabilizing the syntax and tooling interfaces.
 
 ### Implementations
 
@@ -155,15 +192,15 @@ As well as specifications, we also have some implementations in the organization
 
 ## Contribute
 
-Please contribute! [Dive into the issues](https://github.com/multiformats/multiformats/issues)!
-
-Check out our [contributing document](contributing.md) for more information on how we work, and about contributing in general. Please be aware that all interactions related to multiformats are subject to the IPFS [Code of Conduct](https://github.com/ipfs/community/blob/master/code-of-conduct.md).
-
-If you're interested in proposing a new format (in addition to multihash, multistream, and so on), [open an issue](https://github.com/multiformats/multiformats/issues/new) in this repository, explaining the name of the format, what it is for, and why you think it should become one of the multiformats. Pointing to any existing implementations would also be great, if there are any. If you want to implement a multiformat in a new language, open an issue in the main repository for the relevant multiformat: for instance, if you want to write rust-multicodec, open an issue in the multiformats/multicodec repository. This will allow others to know that you're working on it, and potentially join in the effort.
-
-Small note: If editing the README, please conform to the [standard-readme](https://github.com/RichardLitt/standard-readme) specification.
+Check out our [contributing document](contributing.md) for more information on
+how we work, and about contributing in general.
 
 ## License
 
-This repository is only for documents. All of these are licensed under the [CC-BY-SA 3.0](https://ipfs.io/ipfs/QmVreNvKsQmQZ83T86cWSjPu2vR3yZHGPm5jnxFuunEB9u) license © 2016 Protocol Labs Inc. Any code is under a [MIT](LICENSE) © 2016 Protocol Labs Inc.
+This repository is only for documents. All of these are licensed under the
+[CC-BY-SA
+3.0](https://ipfs.io/ipfs/QmVreNvKsQmQZ83T86cWSjPu2vR3yZHGPm5jnxFuunEB9u)
+license © 2016 Protocol Labs Inc. Any code is under a [MIT](LICENSE) © 2016
+Protocol Labs Inc.
 
+[Code of Conduct]: https://github.com/ipfs/community/blob/master/code-of-conduct.md