[development] D7 contrib module development

Stella Power stella at stellapower.net
Sun Mar 8 16:46:41 UTC 2009

>   However, in the end, you get what you pay for!

Well, Drupal is free and you don't pay for it. :)

To be honest, I think this is an absolutely terrible idea.  It's just not
scalable.  We've got thousands of contributed modules and themes, which
makes for millions of lines of code.  To ask that we can have a core team of
developers managing contrib patches, means that they need to get familiar
with all those projects and how they work, the various potentially complex
code and features in each.  It's just not realistic.  It's also not
realistic to expect those same developers to review _all_ of the patches
that need to get committed.  Don't forget this doesn't just include patches
that get submitted via the issue queues but all of the changes that the
maintainers themselves commit as they're working on new features, etc.  Most
Drupal contributors provide their time and effort for free - again it's not
realistic, this proposal sounds like a full time job.

I also really dislike this proposal because, as you pointed out, the rate of
changes to contrib will decrease.  This includes both features and bug
fixes.  It goes against the whole "the drop is always moving" and in doing
so, removes one of the great things about Drupal.

If you really want to help improve contrib, then help by writing more
"comparisons of duplicated modules" (http://drupal.org/node/266179 - though
the handbook is a bit messed up since the upgrade).  Help by working with
contrib project maintainers and convince them to merge their duplicate
modules.  Help by reviewing contrib modules and providing patches.

So a big -1 for this proposal.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.drupal.org/pipermail/development/attachments/20090308/f04dbbd7/attachment-0001.htm 

More information about the development mailing list