[zeromq-dev] [ANNOUNCE] Crossroads I/O release 1.0.0

Ciprian Dorin Craciun ciprian.craciun at gmail.com
Fri Mar 16 09:02:47 CET 2012

On Thu, Mar 15, 2012 at 20:53, Martin Sustrik <sustrik at 250bpm.com> wrote:
> Hi all!
> We would like to announce the first release of the Crossroads I/O project.
> Crossroads I/O is a fork of the ZeroMQ project.
> While we acknowledge forking can be a painful process, we felt the
> ZeroMQ trademark policy to be overly restrictive.

    Could you please elaborate more on this?

    I've read the trademark policy at the address bellow and to me it
seems quite "sensible"...

> Furthermore, the ZeroMQ community has also recently chosen to institute
> a light review process, which we feel is at odds with the technical
> quality and long-term goals we desire for the project.

    Wouldn't it have made more sense to start a more "conservative"
branch where you cherry-pick-ed the worthy patches? And leave the
current branch as an "experimental" / "development" one?

    I mean the problem is that you split not only the community, but
also lead the projects that use one or the other in two separate
directions which at some point would make them un-interoperable? (I
understood that you've provided an ZeroMQ compliant API, but for how
long can you keep both the API and the protocol compatible?)

    This move reminds me of the AMQP current status -- incompatibility
between brokers and libraries...

    I also subscribed to both mailing lists to see how things would
go, but I'm inclined to ZeroMQ especially for its "light review
process" which means it would make the project more "flexible" and
more "democratic".


More information about the zeromq-dev mailing list