[development] Duplicated modules

Gerhard Killesreiter gerhard at killesreiter.de
Wed Mar 11 01:59:34 UTC 2009

Hash: SHA1

Thomas Zahreddin schrieb:
> You asked for a suggestion, here are my thoughts:
> Am Dienstag, den 10.03.2009, 15:14 -0700 schrieb Karoly Negyesi:
>> Hi,
>> OK all you wiseasses, now you pissed me off enough to bring these
>> issues into wider public, so tell me what to do in these situations.
>> 1) There is a Drupal module, older than my boots, gets a much needed
>> rewrite by two guys. Comes a third one, and he is, of course, welcome
>> to the party. There is a discussion of what we do and what we not to
>> do. Come next day, said third guy does what we all three agreed not
>> do. Following a debate, he packs his toys and starts a new project.
>> Said third guy contributes heavily to Drupal project for extremely
>> long but quality and quantity does not always correlate.
> So what can we learn form this (and many other stories)?
> My answer to all three examples:
> we need a better way to make decisions, since this sounds like the third
> one does not agree in the end and to lay the responsibility in the hand
> of teams: team members should not only be developers of the module, also
> developers interested in cooperating / interacting (e.g. via an API)
> with this module and _users_ of this module and maybe developers of
> drupal core (since this is also a 'module' that will interact with a
> contrib module). I want to call this circle decision board. 
> These boards / circles follow the principles of decisioning by
> sociocracy (no crazy people - a practical approach for some European
> companies) feel free to ask for more details and / or check
> http://en.wikipedia.org/wiki/Sociocracy .

"Sociocracy is a system of governance using consent-based decision
making among equivalent individuals and an organizational structure
based on cybernetic principles. "

The problem in Open Source Software development is that the individuals
are usually not equivalent.

This is either explicit (one is the maintainer of the project and the
other isn't) or implicit (one is longer with the project or whatever).

> Means e.g. all decisions are made in consent. Means in difference to

Ponies for everybody...?

Version: GnuPG v1.4.9 (GNU/Linux)


More information about the development mailing list