[development] Drupal Enhancement Proposals (DEPs)

neil at civicspacelabs.org neil at civicspacelabs.org
Mon Nov 14 08:39:01 UTC 2005

Overall I think this is a good idea.

On Sat, Nov 12, 2005 at 09:41:42PM +0200, Adrian Rossouw wrote:
> What we would essentially do is create a document, that has an  
> official number, a status and an owner. This document
> would be modelled on JEPs (http://www.jabber.org/jeps/jep-0143.html),  
> and would explain the basic goals of the project,
> reasoning behind it, requirements, security considerations and so forth.

I think we should keep proposals written clearly and concisely. The
longer something is, the less people will want to read it.

> How I imagine the basic workflow would be, is that someone writes a  
> proposal, in the correct format, that gets published as a draft.
> At a certain point the draft then gets sent to drupal-devel, and  
> developer comments are factored in. Then it gets published on
> Drupal.org, and user comments get factored in. At this point, we have  
> a proposed DEP, and anyone who has any interest
> in working towards that knows what has been decided to be the best  
> approach, who is working on it, and what is the status of it.

Is this the best order- developers followed by users? I'm guessing it
should be flexible. API changes go to developers first; functionality
changes go to users first.


More information about the development mailing list