[development] One core, many distributions

Adrian Rossouw adrian at bryght.com
Sat Nov 19 19:54:03 UTC 2005

Hash: SHA1

On 19 Nov 2005, at 9:29 PM, Larry Garfield wrote:
> My recommendation would be to have another "level" of modules,  
> "endorsed" (or
> something less stupid sounding).  First, strip the core shipped  
> modules down
> to a minimum: the required modules, throttle, taxonomy, path, menu,  
> upload,
> comment, image, page (the one node type), and possibly xml-rpc.   
> (The exact
> list is subject to debate, of course.)  That creates a core system  
> that is
> lean, mean, but still functional for a basic bunch-of-pages site.
This is one of the things I've wanted to do forever.

I would like to see separate repositories too, with stricter security  
review rules
and a group of commiters, with their own assigned modules/tasks.  
so that we can implement a code signing system that is required  
before we
allow modules to be downloaded to their machines via the install system,
and only allow them to get other modules which haven't matured enough  
yet, if they physically
edit a very big warning laden file.

The same file would have an option to disable  all traces of internet  
downloading from the system,
to allow for closed systems.

And i believe the default node module included, should be  
or more pointedly. CCK.

- --
Adrian Rossouw
Drupal developer and Bryght Guy
http://drupal.org | http://bryght.com

Version: GnuPG v1.2.4 (Darwin)


More information about the development mailing list