Pieter Hintjens

Alternatively, implementing it in CZMQ would make it very easy to wrap. On Fri, May 15, 2015 at 10:40 AM, KAPP Arnaud [email protected] wrote: > Hello, > > Are you...

Changing culture can be heavy, yes. However we've found that merging rapidly gives new contributors the incentive to learn and stay. It's worked very well in dozens of projects now....

The use of a single master branch for all work is aggressive, yet it has proven successful in multiple projects now, of all sizes and maturities. Merging to master forces...

We had a few significant breakthroughs in the ZeroMQ process. One was to split off reviewing PRs from merging them. We simply do not do blocking reviews. This sounds insane...

With libzmq we also had few test cases. We enabled Travis, and said, "breaking existing test cases is a reason to revert (or not merge) a patch", and with this...

@tuncer here's my latest proposal for that: http://hintjens.com/blog:85 Basically you allow APIs to evolve naturally, and you tag them RAW, DRAFT, STABLE, LEGACY, RETIRED depending on use. This gives you...

You need to sign into Travis with the credentials of that organization, I think. On Mon, Mar 9, 2015 at 5:46 PM, Zachary Kessin [email protected] wrote: > anyone know how...

Yes, you can use dealer as substitute for pull or push. Dealer is in fact identical to the two combined (bidirectional, where pull and push restrict flow to one direction...

Dealer can send to dealer, it's exactly the same (except biirectional). On Tue, Apr 15, 2014 at 12:56 AM, krakatoa [email protected] wrote: > Excuse me guys, I couldn't manage to...

Travis failed, shall I merge this anyhow?