[development] Consolidating duplicate contrib modules for D7

Shai Gluskin shai at content2zero.com
Mon Nov 30 20:50:12 UTC 2009

I think the important part is giving users good information. Asking the docs
team to write module comparison pieces is a good thing too. But I'm against
any plan that tries to put controls on module creation because the freedom
to scratch an itch has led to great creativity and ingenuity. But helping
module developers know what is already out there, that's always a good

When the d.o. re-design launches, I think it is going to be a different
world. And I think it will be a lot clearer where energies should be spent
on helping site builders and other Drupal constitutents get what they need.

Content2zero Web Development <http://content2zero.com>

On Mon, Nov 30, 2009 at 3:22 PM, Andrew Berry <andrewberry at sentex.net>wrote:

> On 2009-11-30, at 2:44 PM, Brian Vuyk wrote:
> > Node Access: http://drupal.org/project/node_access
> > Nodeaccess: http://drupal.org/project/nodeaccess
> IMO there should be a CVS policy disallowing namespaces to be
> differentiated with dashes, underscores, spaces, and so on. This is a
> perfect example of the confusion this can cause.
> > is it worth starting something along the lines of #D7CX to consolidate
> the dupes in the name of a better user experience?
> I think that if this is something you want to do, you should try and find
> some of the more popular maintained modules and try to get one or two sets
> of projects on board. Once there are a few big projects starting down this
> path, I think it would really help to encourage the smaller projects to work
> together.
> --Andrew
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.drupal.org/pipermail/development/attachments/20091130/ca4380e0/attachment.html 

More information about the development mailing list