[development] module duplication in Drupal contrib

Steven Peck sepeck at gmail.com
Wed Mar 19 16:05:35 UTC 2008

A monoculture produces no innovation.
Protecting the existing contributed modules which may or may not have
active maintainers, which may or may not have maintainers who
cooperate and/or may or may not have maintainers that share a vision
is not good.
Forbidding innovation or competition produces a protected class of
elite people who were first to arrive but may not actually be doing
something now.

As this is not a new debate, I shall introduce a new one.
Fire is bad.  Support or refute this statement.


On Wed, Mar 19, 2008 at 7:25 AM, Greg Knaddison - GVS
<Greg at growingventuresolutions.com> wrote:
> Hi,
>  "Modules that duplicate functionality available from an existing
>  module are damaging to the Drupal project."
>  Please support or refute that statement and propose strategies for
>  managing CVS applications and/or projects on Drupal.org in a way that
>  will best help the Drupal project.
>  I'm using "Drupal project" in a very loose sense so you should infer
>  that it includes lots of groups of people like new users, site
>  builders, contributors, drupal.org admins, the security team, etc.
>  Thanks,
>  Greg
>  --
>  Greg Knaddison
>  Denver, CO | http://knaddison.com
>  World Spanish Tour | http://wanderlusting.org/user/greg

More information about the development mailing list