[development] Drupal Enhancement Proposals (DEPs)
adrian at bryght.com
Tue Nov 15 00:18:49 UTC 2005
-----BEGIN PGP SIGNED MESSAGE-----
On 15 Nov 2005, at 1:07 AM, Dries Buytaert wrote:
> On 14 Nov 2005, at 20:46, Ber Kessels wrote:
>> It is what got that form API in. It is what holds back Those Big
>> Issues from leveraging from yadiyadia level to Real Code Level,
>> think drupal.css, think taxonomy.module cleanup, think CCK ideals,
>> think install API. etcetc.
> Erm, the CCK plans are pretty well documented. They have been for
> about a year. Similarly, the install API has been documented too.
> Your examples show that central documentation is no guarantee for
> success (however they are often a necessary step).
I agree. DEP's should not be required, but are a tool which can,
and should be used for larger tasks.
I would also like to see DEPs used to pool our ideas together, so
that you can develop and spec enhancements that you might not
personally have a chance
to develop fully, but which other people might be interested in
Writing a DEP is at least providing a solid starting point for
someone else to expand on and develop from. Also, all DEPs won't be
developed, but something
that has a DEP has a higher chance of being developed than something
which doesn't have it.
Drupal developer and Bryght Guy
http://drupal.org | http://bryght.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (Darwin)
-----END PGP SIGNATURE-----
More information about the development