Migrating this repo to ipfs-shipyard

[Gozala]

We should do #336 before migrating this anywhere (or maybe it can be part of it, can't remember if you can do the rename).

If we want to explore ipfs/notes#436 based on this project I think it would make sense to migrate it (or fork it) into https://github.com/ipfs-shipyard/

Alternatively we could consider creating separate org as both IPLD and IPFS projects have one. I do not personally have strong preferences where to migrate or whether to just iterate over this here, but this did come up multiple times so I think it's best to have discussion here.

[Gozala]

/cc @mikeal @autonome @lidel

[carsonfarmer]

I don't think our team has any strong preferences here? Happy to have this live over in ipfs-shipyard or any other PL-based org? Textile is also happy to support development under our org on GitHub, but are also aware that there are always politics to these things that just aren't worth worrying about :)

[mikeal]

Why shipyard instead of the main org?

[lidel]

I'd move it to ipfs/ org to give it proper prominence:
this will be important low level plumbing that we expect to be used widely on the web, and possibly in js-ipfs itself at some point.

Note: I don't have admin to do the move, nor know how to do it across orgs

[carsonfarmer]

Sounds good to me