Crossroads I/O is a fork of the ZeroMQ project

http://www.crossroads.io/

by dochtman • 14 years ago

71 39 14 years ago

crossroads.io

jameskilton• 14 years ago

So I can't find the reason why this project exists instead of just contributing to 0MQ directly.

to3m• 14 years ago

From the web site (http://www.crossroads.io/faq):

```Why was Crossroads I/O forked from ZeroMQ?

The contribution and trademark policies of the ZeroMQ project were, as of March 2012, incompatible with our long-term goals.

Who is behind the fork?

The main work on the fork was done by two of the original developers of ZeroMQ, Martin Sustrik and Martin Lucina, with help and advice from other members of the ZeroMQ community.'''

Ecio78• 14 years ago

I've read it, and yet not understood which are those incompatibilities in the goals

raphinou• 14 years ago

I agree with you. When you fork a project, there better be a good reason. And when there is a good reason, there's no reason to be vague in the explanation. (and I can't think of a vaguer explanation than what they write)

Giving an example of a problem solved by the fork would help, though I'm not sure a solid example of a goal not possible within 0mq can be found based on the project goals.

rch• 14 years ago

Looks like a move from GPL to LGPL.

I had assumed that zmq was BSD licensed to begin with - so I've learned something.

krakensden• 14 years ago

I think this email from the guy in charge of 0MQ now is fairly clear: http://lists.zeromq.org/pipermail/zeromq-dev/2012-February/0...

On a related note, developers can be mean

hogu• 14 years ago

from reading the email thread it appears this is the main issue:

zeromq is looser about what ends up in master. They view master as sort of a global staging area, and what ends up in release branches is viewed as stable/vetted code. As a result, master can be quite unstable.

The people that forked wanted a more stable master, with lots of code reviews before patches end up in master.

arjn• 14 years ago

Can someone please elaborate ? I very recently started an investigation (proof of concept) into zeromq for my team. What are the long term implications ?

dripton• 14 years ago

Probably none. You can still use ZeroMQ. If Crossroads ends up better than ZeroMQ, you can switch.

jrockway• 14 years ago

Especially as the ZMQ API is so simple. init/send/recv. That's about it.

SoftwareMaven• 14 years ago

The real question for me, since I very recently brought 0MQ into my project: should I stay with that or switch to Crossroads? I don't want to get stuck on the lagging branch.

astrodust2• 14 years ago

My vote is for the first one that can handle TLS over a special type of connection pair.

asok• 14 years ago

ishbits• 14 years ago

psadauskas2• 14 years ago

From the FAQ:

Why do you not accept pull requests?

Pull requests can change while being reviewed. This makes it impossible to ensure that the code being merged is the same code that has been reviewed and discussed, which compromises integrity of the codebase.

If only Git had some sort of cryptographically secure token that would uniquely identify commits, and make tampering evident.

mato3• 14 years ago

It does. But to my knowledge, no one submits pull requests as a set of SHA1 hashes.

storborg2• 14 years ago

What is a pull request if not an ordered list of SHA1 hashes and comments?

cpeterso2• 14 years ago

(I think psadauskas is being sarcastic.)

Crossroads I/O is a fork of the ZeroMQ project

Related Stories