[development] Switching themes in modules
alan.g.dixon at gmail.com
Mon Jun 26 16:38:08 UTC 2006
I'm a newcomer to the drupal culture here, and it looks to me also
that in some ways Drupal is too large for the way it works now (and
presumably that's part of the motivation for Dries' road trip). Kind
of a no-brainer in a way, all successful organizations of people have
to go through painful changes in how they work as they grow.
My only input into this particular thread is that big email lists
aren't a very productive forum for this kind of conversation and I
hope that the core people who are responsible for the next steps can
be given the support to do whatever they need to ('cause someone's not
going to be happy, but it's inevitable), and that they let the rest of
us know in good time...
On 6/24/06, Bèr Kessels <ber at webschuur.com> wrote:
> I know people disagree with me. I know a lot of people think "well then: fix
> it". I know that even more people think "sigh, there he goes again". But tell
> me: why the ## do we have so much stuff in core, from which everyone agrees
> that it should not be there, or that it badly needs a rewrite? Yet I hardly
> ever see patches/issues like "Complete clean up of hook_user", or "removed
> archive.module from core", or "complete clean up of the upload.module code",
> get trough, or being made at all? The only answer I can give is: "Drupal is
> too large, for the way it works now". I don't have a ready made solution
> either, but the fact that we have so much cruft in core, so much good patches
> in the queues collecting dust, and the fact that we still don't have a proper
> media handling system shows that this is somehow right!
> In any case, this very patch, the reason for this "fork", which was never a
> fork, made me loose a lot of confidence in Drupal and its way of working.
Alan Dixon, Web Developer
More information about the development