Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Transferring all multiformats to this organization #4

Closed
20 of 50 tasks
RichardLitt opened this issue Aug 2, 2016 · 10 comments
Closed
20 of 50 tasks

Transferring all multiformats to this organization #4

RichardLitt opened this issue Aug 2, 2016 · 10 comments

Comments

@RichardLitt
Copy link
Member

RichardLitt commented Aug 2, 2016

What

We need to move all multiformats to this organization.

*This list can be edited. Please check off or mark as irrelevant any repositories. *

List

There are a wide variety of multiformats. These are the main ones:

  • multiaddr
  • mulithash
  • multikey
  • multicodec
  • multistream
  • multibase

I am not sure that these exist, but I found them referenced in various places:

I would also like to have all of the implementations in here:

  • multiaddr: protocol design
    • multiaddr: impl in Go
    • multiaddr: impl in JS
    • multiaddr: impl in Java
    • multiaddr: impl in Haskell
    • multiaddr: impl in Python
    • multiaddr: impl in Rust
  • multihash: protocol spec
    • multihash: impl in Go
    • multihash: impl in JS
    • multihash: impl in Scala
    • multihash: impl in Java
    • multihash: impl in Clojure
    • multihash: impl in Rust
    • multihash: impl in Haskell
    • multihash: impl in Python
    • multihash: impl in Elixir
    • multihash: impl in Swift
    • multihash: impl in Ruby
  • multicodec: protocol spec
    • multicodec: impl in Go
    • multicodec: impl in JS
  • multistream: protocol spec
    • multistream: impl in Go
    • multistream: impl in JS
  • multibase / baseN: protocol spec May not exist?
    • multibase / baseN: impl in Go
    • multibase / baseN: impl in JS

One's that @jbenet needs to move over, from his list of repos:

And diasdavid: diasdavid/js-multistream, diasdavid/multistream-netcat, diasdavid/node-multiplex-stream-muxer, diasdavid/js-multistream-netcat.

@jbenet
Copy link
Member

jbenet commented Aug 3, 2016

go-peerstream is a libp2p thing if anything

@jbenet
Copy link
Member

jbenet commented Aug 3, 2016

thanks @RichardLitt ! moved mine

@RichardLitt
Copy link
Member Author

@jbenet Should we not move over all of the implementations, then? We could ask people to move them to this organization.

@jbenet
Copy link
Member

jbenet commented Aug 5, 2016

Yeah I'd be in favor of moving to this org. It's very much a request
though, their choice
On Thu, Aug 4, 2016 at 17:03 Richard Littauer notifications@github.com
wrote:

@jbenet https://github.com/jbenet Should we not move over all of the
implementations, then? We could ask people to move them to this
organization.


You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
#4 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAIcofxUvhbMxwA6iYj10--VRr5lj637ks5qclO0gaJpZM4Ja8el
.

@RichardLitt
Copy link
Member Author

Can I have approval that none of these exist as specs anywhere, or written in some repo?

@RichardLitt
Copy link
Member Author

Pinged all of the authors - thanks, all. I'm going to consider this closed when we have responses from them.

@daviddias
Copy link
Member

multicast - See this roadmap file
multihop - See this roadmap file
multipart - See this roadmap file

These are not multiformats

multi-multiplexing (multimux?) - See ipfs/specs#33

Not a thing

multiplex - See this roadmap file

Also not a multiformat

@RichardLitt
Copy link
Member Author

What about -proc and -transport?

@daviddias
Copy link
Member

I don't think those are things either

@RichardLitt
Copy link
Member Author

Well that settles that then. And, on second thought, since none of the other implementations mandatorily need to move here in any timeframe, I am going to close this issue. Discussion can continue; reopen as needed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants