[zeromq-dev] Contribution process, revisited

Benjamin Henrion bh at udev.org
Tue Mar 22 17:30:51 CET 2011

On Tue, Mar 22, 2011 at 5:25 PM, Pieter Hintjens <ph at imatix.com> wrote:
> Hi All,
> After some time playing with multiple gits for 0MQ releases, I'd like
> to reopen the discussion on best practices for our community on
> contribution workflow.
> My goals here is consistency, simplicity, and freedom. Also if it
> doesn't make sense on a grey Monday morning before coffee, it's too
> complex.
> Some observations:
> * The neatest organization seems to be "one ego per git". We've been
> using this rule to divide the original core 0MQ git into separate
> projects, and it feels right.
> * We end up with many gits, each with a clear owner, and with flow of
> changes going between them N-to-N.
> * github pull requests don't work except between an original git and
> its forks. Thus they are useless for general distributed work.

Can you explain why they do not work?

I used it before, and it worked perfectly.

Benjamin Henrion <bhenrion at ffii.org>
FFII Brussels - +32-484-566109 - +32-2-4148403
"In July 2005, after several failed attempts to legalise software
patents in Europe, the patent establishment changed its strategy.
Instead of explicitly seeking to sanction the patentability of
software, they are now seeking to create a central European patent
court, which would establish and enforce patentability rules in their
favor, without any possibility of correction by competing courts or
democratically elected legislators."

More information about the zeromq-dev mailing list