[development] Consolidating duplicate contrib modules for D7

[Jerad Bitner]

Not to say that these stats are always an accurate measure of a module
- but really, they're all we have right now and better than nothing.
It's hard to judge a module explicitly by these stats, but they are
helpful and do have value IMNSHO.

Saying they have no value at all is spitting in the eye of the people
who took the time to gather and implement them. They're what we have
available and we should use them.

Presenting them in a comparable manner and giving some general
guidance as to how they should be used, notices that they are not the
only way to judge should be part of the guidance provided.

On Fri, Dec 4, 2009 at 2:19 PM, nan wich <nan_wich at bellsouth.net> wrote:
> Jerad Bitner wrote:
>> pull in the project's stats (issue stats, usage stats, maybe some new
>> activity stats
>
>
>
> And of what value are these numbers?  IMHO, none.  For example, look at the
> issue queue for Views - does the high number mean it's a bad module? I don't
> think anyone here would agree with that. Then look at a module that has
> "only" 2000 users - does that mean it can't be trusted? No, and neither does
> one with only two users. Activity stats has some value, but very minimal as
> it doesn't take into account maintainers going on vacation or getting sick.
> I have seen very few proposed metrics that are worthwhile.
>
>
>
> In the end, it must be the community who poits out to the duplicate
> (or similar) module maintainers the situation. And then it is the
> responsibility of the maintainer(s) to investigate and determine if a
> synergy is possible.
>
>
>
> Nancy E. Wichmann, PMP
>
> Injustice anywhere is a threat to justice everywhere. -- Dr. Martin L. King,
> Jr.
>
>



-- 
~Jerad Bitner
CTO ~ Rapid Waters Development
http://rapidwatersdev.com