This must be understood in the light of the philosophy of Peter Hinjens which is the community comes always first, before technical assets. Smoothing community process and interactions is (very) necessary for a project success.
Growing zeromq ideas mainstream will provide more value to the project of improving distributed software than changing drastically zeromq (to (re-)build nanomsg community).
> testing coverage completely matters.
testing matters not testing coverage.
Testing matters as way to give insight about the project, api and protocols as such integration tests more useful that unit tests. This help people jump in, it's a way to document the API/Protocol.
Achieving the API and protocols is more important than having a good code coverage. If there is no code, there is nothing to cover, and nothing to show.
He develop his ideas of good community processus in the chapter Sphere of Lights of Culture and Empire essay [1]
It hurts a lot when your assumptions are challenged. The process we use in ZeroMQ is successful beyond all expectations. See http://hintjens.com/blog:93.
What I'm doing with these "Top 10" articles is documenting our experience over the last years.
I guess people said "OUCH!" a lot when Wikipedia said you could edit any page. It is really similar here.
I think wether such an approach works heavily depends on the kind of project (and as such shouldn't be posted as a general rule). For something relatively new and/or small it may work very well, but as soon as you reach a certain complexity it's unsustainable; at least if core components are involved.
This is his writing style, he does shortcuts to keep thing readable and you have sort out the real world constraints yourself. That said the book is readable but some arguments that are difficult to understand.
Growing zeromq ideas mainstream will provide more value to the project of improving distributed software than changing drastically zeromq (to (re-)build nanomsg community).
> testing coverage completely matters.
testing matters not testing coverage.
Testing matters as way to give insight about the project, api and protocols as such integration tests more useful that unit tests. This help people jump in, it's a way to document the API/Protocol.
Achieving the API and protocols is more important than having a good code coverage. If there is no code, there is nothing to cover, and nothing to show.
He develop his ideas of good community processus in the chapter Sphere of Lights of Culture and Empire essay [1]
[1] http://cultureandempire.com/html/cande.html#toc-3