Can the scope of this group be expanded a little?

We encourage users to post events happening in the community to the community events group on https://www.drupal.org.
augustin's picture

Hello,

I welcome any initiative that aims to reduce time wasted, redundancy etc.

This group was created to allow people to post their new module ideas, BEFORE they create them, before they start coding.

What about all the modules already created, where redundancy already exist?
Can this group be used to find a proper resolution?

Example:
On the dev list, we found those four very related modules:
http://drupal.org/project/default_filter
http://drupal.org/project/filterbynodetype
http://drupal.org/project/filter_default
http://cvs.drupal.org/viewvc.py/drupal/contributions/modules/input_forma...
+ 1 Drupal core issue with patch.

The duplication and redundancy already exists.
The best would be to review the functionality of each module, see which ones can be dropped and which one could carry on to be supported. What code from one can be contributed to the other?

My question is: can this group be used to find a solution to resolve this kind of duplication, or should another group be created for that?

Comments

Never mind

augustin's picture

Forget about it.
I think I have a better solution.
I'd like to create a group which has an even wider scope, and I'll link to this group, since I support the initiative behind this group.

--
www.reuniting.info
Healing with Sexual Relationships.
www.wechange.org
We live in a world of solutions.

.

--
www.reuniting.info
Healing with Sexual Relationships.
www.wechange.org
We live in a world of solutions.

What about a group called

alex_b's picture

What about a group called "Contributed Module Duplication"?

Contributed Module Ideas

Group organizers

Group notifications

This group offers an RSS feed. Or subscribe to these personalized, sitewide feeds:

Hot content this week