Improve READMEs and CONTRIBUTING files in opensource repo (#45)

- Add CONTRIBUTING files
- Point Devbox button to landing page
- Improve TySON readme
- Add "Tarpit Law" discussion to TySON

CONTRIBUTING.md

@@ -0,0 +1,24 @@
+# Contributing
+
+When contributing to this repository, please describe the change you wish to make via a related issue, or a pull request.
+
+Please note we have a [code of conduct](CODE_OF_CONDUCT.md), please follow it in all your interactions with the project.
+
+## Opening a Pull Request
+This project is published as a standalone repo from our [opensource monorepo](https://github.com/jetpack-io/opensource).
+Pull requests should be sent to the monorepo instead, and they will automatically be published
+to this repo when merged.
+
+## Developer Certificate of Origin
+
+By contributing to this project you agree to the [Developer Certificate of Origin](https://developercertificate.org/) (DCO) which was created by the Linux Foundation and is a simple statement that you, as a contributor, have the legal right to make the contribution. See the DCO description for details below:
+
+> By making a contribution to this project, I certify that:
+>
+> a. The contribution was created in whole or in part by me and I have the right to submit it under the open source license indicated in the file; or
+>
+> b. The contribution is based upon previous work that, to the best of my knowledge, is covered under an appropriate open source license and I have the right under that license to submit that work with modifications, whether created in whole or in part by me, under the same open source license (unless I am permitted to submit under a different license), as indicated in the file; or
+>
+> c. The contribution was provided directly to me by some other person who certified (a), (b) or (c) and I have not modified it.
+>
+> d. I understand and agree that this project and the contribution are public and that a record of the contribution (including all personal information I submit with it, including my sign-off) is maintained indefinitely and may be redistributed consistent with this project or the open source license(s) involved.

README.md

@@ -2,13 +2,14 @@
 
 ### A type-safe, K-sortable, globally unique identifier inspired by Stripe IDs
 
-![License: Apache 2.0](https://img.shields.io/github/license/jetpack-io/typeid) [![Join Discord](https://img.shields.io/discord/903306922852245526?color=7389D8&label=discord&logo=discord&logoColor=ffffff)](https://discord.gg/agbskCJXk2) [![Built with Devbox](https://jetpack.io/img/devbox/shield_galaxy.svg)](https://jetpack.io/devbox/docs/contributor-quickstart/)
+![License: Apache 2.0](https://img.shields.io/github/license/jetpack-io/typeid) [![Join Discord](https://img.shields.io/discord/903306922852245526?color=7389D8&label=discord&logo=discord&logoColor=ffffff)](https://discord.gg/agbskCJXk2) [![Built with Devbox](https://jetpack.io/img/devbox/shield_galaxy.svg)](https://jetpack.io/devbox/)
 
 ## What is it?
-TypeIDs are a modern, type-safe extension of UUIDv7.
+TypeIDs are a modern, type-safe extension of UUIDv7. Inspired by a similar use of prefixes
+in Stripe's APIs.
 
 TypeIDs are canonically encoded as lowercase strings consisting of three parts:
-1. A type prefix (in all lowercase ASCII [a-z])
+1. A type prefix (at most 63 characters in all lowercase ASCII [a-z])
 2. An underscore '_' separator
 3. A 128-bit UUIDv7 encoded as a 26-character string in base32 (using [Crockford's alphabet](https://www.crockford.com/base32.html) in lowercase).
 
@@ -30,6 +31,7 @@ Here's an example of a TypeID of type `user`:
  selected for copy-pasting by double-clicking, and is a more compact encoding than the traditional hex encoding used by UUIDs (26 characters vs 36 characters).
 
 ## Implementations
+
 | Language | Status |
 | -------- | ------ |
 | [Go](https://github.com/jetpack-io/typeid-go) | ✓ Implemented |