[drupal-devel] Making Drupal fully 'community-driven': A Proposal for restructuring the Drupal project
Following up (finally!) on a commitment I made some months back, I've prepared a set of concrete proposals for renewing Drupal's (arguably) outdated decision making structure. They are posted as a forum topic at: http://drupal.org/node/15916 Please read and comment! The 'teaser': Drupal - a highly promising and excellently designed open source software - prides itself on being "community-driven". A primary Drupal interest is promoting collaboration and the sharing of views and perspectives. Yet, paradoxically, the project decision-making structure- a relic from its very early days - is notable for its closed, centralized, and fixed nature. Most decisions on the Drupal 'core' are still made personally by the project owner and founder, Dries. The only exceptions are decisions made by one of two close associates of his. This contrasts sharply with many other open source projects, which are build on the basis of community decision making. To fully mature as a project, Drupal arguably needs to bring its structure in line with its community spirit. Hence this set of concrete proposals. Their aim is to set out new, expanded roles for decision making, while ensuring that the current values of rigourous code evaluation and development are maintained.
On 20 Jan 2005, at 11:06 PM, Nedjo Rogers wrote:
Hence this set of concrete proposals. Their aim is to set out new, expanded roles for decision making, while ensuring that the current values of rigourous code evaluation and development are maintained.
I think it works as it is presently. And I don't think I am alone. The structure is similiar to the way the linux kernel is developed, and I think we benefit from having Dries at the head. -- Adrian Rossouw Drupal developer and Bryght Guy http://drupal.org | http://bryght.com
On Fri, 21 Jan 2005, Adrian Rossouw wrote:
On 20 Jan 2005, at 11:06 PM, Nedjo Rogers wrote:
Hence this set of concrete proposals. Their aim is to set out new, expanded roles for decision making, while ensuring that the current values of rigourous code evaluation and development are maintained.
I think it works as it is presently. And I don't think I am alone.
You are not.
The structure is similiar to the way the linux kernel is developed,
Indeed.
and I think we benefit from having Dries at the head.
Yep. :) As long as Dries thinks the current development model is viable (ie not too much work for him) I do not think we need to change anything. What we should maybe try to communicate to the outside world is how our development model works. But I think there already is a rather good page by Nedjo in the handbook. Cheers, Gerhard
Hence this set of concrete proposals. Their aim is to set out new, expanded roles for decision making, while ensuring that the current values of rigourous code evaluation and development are maintained.
I think it works as it is presently. And I don't think I am alone.
You are not.
The structure is similiar to the way the linux kernel is developed,
Indeed.
and I think we benefit from having Dries at the head.
Yep. :)
Absolutely. The linux kernel analogy is a good one, I have not thought about it, but it is a very good example indeed. Goba
Op vrijdag 21 januari 2005 14:01, schreef Gabor Hojtsy:
Absolutely. The linux kernel analogy is a good one, I have not thought about it, but it is a very good example indeed.
heh! I had the same vision: http://drupal.org/node/14784#comment-23835 :) -- Regards, Bèr -- [ Bèr Kessels | Drupal services www.webschuur.com ]
participants (5)
-
Adrian Rossouw -
Bèr Kessels -
Gabor Hojtsy -
Gerhard Killesreiter -
Nedjo Rogers