I would strongly agree with chx and others that in some way we need additional committers. I think that it does make sense for Dries to be providing overall guidance, but I think it would be helpful if in some/many cases Dries would lay out criteria for a proposed change to be accepted and then delegate review and commit implementation details to others. A few of the modules Robert mention (maybe blog, tracker, and help) should either go or get a serious revamping. I general, however, many of the module in core serve as reference implementations of certain APIs and allow you to build a reasonable little site with just core - there can and should be other or more feature-rich implementations in contrib. -Peter On Mon, Apr 20, 2009 at 12:13 PM, Gábor Hojtsy <gabor@hojtsy.hu> wrote:
On Mon, Apr 20, 2009 at 6:03 PM, Robert Douglass <rob@robshouse.net> wrote:
So, in my opinion, if you want to take Drupal to the moon, you do two things: 1) give more people the keys to the car, and 2) shed a bunch of the pieces that we currently call "core".
Would that solve our other problem: that many contrib modules got updates later, so it turns out after a stable release that certain APIs are not complete or suitable for important contrib stuff? If we move more of the modules which use these APIs outside of core, we go to pure API design without validation of those APIs with real life modules, no? While I agree some modules would be best to go, maybe moving all is not the solution. Poll was joked to be one of the best API validation modules (for drag and drop, AHAH, etc). While that was a joke to some degree, it also has roots in reality.
Gábor