I'm not sure. In his article on "Building Online Communities" (http://hintjens.com/blog:117) he says he experimented with building online communities for three years and gathering results, and that ZeroMQ is his biggest success (at being organised to defend to both vendor capture, or takeover by a single powerful/competent/rude contributor). For background of why that was his focus, he wrote this (http://hintjens.com/blog:125#toc15) about his experiences with working on OpenAMQ:
"""In late 2009, the Chair and Red Hat sat down and decided, in a secret meeting, to rewrite the spec. [...] From scratch. By himself. After years and years of committee work. After years of investment by others in working code. Without asking anyone except Red Hat. And then, to force this spec through the working group using his usual tactics: bullying and lobbying. [...]
One of my spin-off projects was the Digital Standards Organization, and I came to understand what was needed to protect a standard from predatory hijack. I summarized the definition of a "Free and Open Standard" as "a published specification that is immune to vendor capture at all stages in its life-cycle." What the "free" part means is, if someone hijacks your working group and starts to push the standard in hostile directions (as Red Hat did), can you fork the standard and continue? Does the license allow forking, yes or no? And secondly, does the license prohibit "dark forks," namely private versions of the standard?
If either answer is "no," then you are at the mercy of others. And when there is money on the table, or even the promise of money, the predators will move in. The AMQP experience gave me a lot of material for my later book on psychopaths. [...]
If we'd managed to build a thriving community around OpenAMQ, it would have survived. So the lesson here is simple: community before code. Today this is obvious to me. Eight years ago, it wasn't."""
And reference this (http://hintjens.com/blog:120) Social Architecture FAQ which talks about rude but highly skilled people contributing to projects (read that with "community before code" and the quote "if you want to go fast go alone, if you want to go far go together" in mind).
"""In late 2009, the Chair and Red Hat sat down and decided, in a secret meeting, to rewrite the spec. [...] From scratch. By himself. After years and years of committee work. After years of investment by others in working code. Without asking anyone except Red Hat. And then, to force this spec through the working group using his usual tactics: bullying and lobbying. [...]
One of my spin-off projects was the Digital Standards Organization, and I came to understand what was needed to protect a standard from predatory hijack. I summarized the definition of a "Free and Open Standard" as "a published specification that is immune to vendor capture at all stages in its life-cycle." What the "free" part means is, if someone hijacks your working group and starts to push the standard in hostile directions (as Red Hat did), can you fork the standard and continue? Does the license allow forking, yes or no? And secondly, does the license prohibit "dark forks," namely private versions of the standard?
If either answer is "no," then you are at the mercy of others. And when there is money on the table, or even the promise of money, the predators will move in. The AMQP experience gave me a lot of material for my later book on psychopaths. [...]
If we'd managed to build a thriving community around OpenAMQ, it would have survived. So the lesson here is simple: community before code. Today this is obvious to me. Eight years ago, it wasn't."""
And reference this (http://hintjens.com/blog:120) Social Architecture FAQ which talks about rude but highly skilled people contributing to projects (read that with "community before code" and the quote "if you want to go fast go alone, if you want to go far go together" in mind).