David Golden wrote:
Adam Kennedy wrote:
And therein lies the problem.
Working out when a dependency is important and when it's useless, or
vanity, or lazyness (good or bad) or whatever requires a human
judgment call.
So we can't really do anything about it.
Is it OK to use a lot of dependencies if they all work? :)
Well, if it isn't a patent violation, something along the lines of
Google's PageRank algorithm. A module's dependency Kwalitee score is
based on a combination of the Kwalitees of its dependencies.
Perhaps done as average distance from the mean?
If the average kwalitee is 13, yours is 13, and your deps are scoring
14, 15 and 16 then your KwaliteeRank is 2.
You couldn't use it as a Kwalitee element directly, but having a
KwaliteeRank on the website might get interesting.
Adam K
