[zeromq-dev] Governance of language bindings

Toralf Wittner toralf.wittner at gmail.com
Mon Jan 25 19:37:48 CET 2010

On Mon, 25 Jan 2010, Martin Sustrik wrote:
> Decoupling the core library from the bindings can be done on several levels:
> 1. Source code. Instead of packing everything into the same repository
> each binding can have separate repository with its own maintainers etc.
> 2. Quality assurance. The community around each binding can make sure
> that the binding works as expected.
> 3. Release cycle. With stable ABI, individual binding releases don't
> have to be synchronised with releases of 0MQ core.
> 4. Packages for individual language bindings can be created separately
> each depending on the core 0MQ but not depending each on another.

I would say all of it is good. Most language communities already have 
established repositories for 3rd party libraries, so having pointers to those
libraries on the 0MQ website should be sufficient.

> In overall, my feeling at the moment is that core 0MQ should include
> just small subset of language bindings to ensure basic usability of the
> product. The rest should be handed to focused development communities.
> www.zeromq.org can serve as a directory of existing language bindings.
> zeromq-dev at lists.zeromq.org can still be used to discuss the bindings,
> so that developers have at least an idea of what's being done even if
> the language binding doesn't concern them personally.

To put in my two cents, I think 0MQ should ship with C/C++ only.


More information about the zeromq-dev mailing list