This echos a post I made on this list a few months ago as well, during the last time we discussed trimming core. I used the term "endorsed modules", but same idea. Views and flexinode/cck are far more useful in core than, say, blogapi. I'm not even entirely sure what that does. :-) One proposal that had been floated for the "1st tier" modules (whatever they're called) was automatic downloading. Core is/should be small, but people need to be able to get the functionality they want quickly and easily. Being able to download and install a stable module from within the UI would make that much easier, as well as not require separate download tarballs for each "distribution profile". I freely confess to not knowing all that would need to go into this drupal-get module, though. I vaguely recall someone mentioning that they were doing something along these lines. If that's you, what were you doing? -- Larry Garfield On Mon, May 1, 2006 2:40 pm, Jeff Eaton said:
=> Core should be core required files and code only. For the rest of this posting, I will call these the "framework files" or just "framework," but the name is mostly not important to me. It's just for clarity.
=> There should be a group of the most useful, best coded modules which are maintained and supported like the core itself. For the rest of this posting, I will call these the "core modules"
This is something that I've suggested before -- some things, like node.module and so on, are obviously always going to be a part of the "framework files". This meshes very well, IMO, with Robert's vision of 'targeted distributions.'
I think providing the current mix of Drupal core modules as a 'Classic Drupal' distro, or something like that, would be a fine way to let people keep on going as they have been. Those who want something else can get framework + a distro, or framework + a custom mix of modules and themes, etc.
--Jeff