Skip Menu |
 

This queue is for tickets about the Module-CPANTS-Analyse CPAN distribution.

Report information
The Basics
Id: 88130
Status: open
Priority: 0/
Queue: Module-CPANTS-Analyse

People
Owner: Nobody in particular
Requestors: ether [...] cpan.org
Cc:
AdminCc:

Bug Information
Severity: (no value)
Broken in: (no value)
Fixed in: (no value)



Subject: Module::CPANTS::SiteKwalitee is missing?
Download (untitled) / with headers
text/plain 349b
Some comments refer to Module::CPANTS::SiteKwalitee, but this doesn't seem to exist: e.g. in Module::CPANTS::Kwalitee::Distname: # NOTE: The metrics in this module have moved to # Module::CPANTS::SiteKwalitee because these require an archived # distribution which you don't have while testing local Kwalitee # with Test::Kwalitee.
Download (untitled) / with headers
text/plain 525b
On Mon Aug 26 02:56:42 2013, ETHER wrote: Show quoted text
> Some comments refer to Module::CPANTS::SiteKwalitee, but this doesn't > seem to exist: > > e.g. in Module::CPANTS::Kwalitee::Distname: > > # NOTE: The metrics in this module have moved to > # Module::CPANTS::SiteKwalitee because these require an archived > # distribution which you don't have while testing local Kwalitee > # with Test::Kwalitee.
It's github-only. https://github.com/cpants/Module-CPANTS-SiteKwalitee I'll provide links to github when things are more settled.
Download (untitled) / with headers
text/plain 856b
On 2013-08-27 12:01:08, ISHIGAKI wrote: Show quoted text
> On Mon Aug 26 02:56:42 2013, ETHER wrote:
> > Some comments refer to Module::CPANTS::SiteKwalitee, but this doesn't > > seem to exist: > > > > e.g. in Module::CPANTS::Kwalitee::Distname: > > > > # NOTE: The metrics in this module have moved to > > # Module::CPANTS::SiteKwalitee because these require an archived > > # distribution which you don't have while testing local Kwalitee > > # with Test::Kwalitee.
> > It's github-only. > > https://github.com/cpants/Module-CPANTS-SiteKwalitee > > I'll provide links to github when things are more settled.
a ha! FWIW, it might be worthwhile to split the Module::CPANTS::Kwalitee:: namespace out into a separate dist too -- that will really help cut down the MCA bug queue, as most of those tickets are related to specific kwalitee metrics, not the engine itself.
Download (untitled) / with headers
text/plain 1.3k
On Wed Aug 28 04:43:15 2013, ETHER wrote: Show quoted text
> On 2013-08-27 12:01:08, ISHIGAKI wrote:
> > On Mon Aug 26 02:56:42 2013, ETHER wrote:
> > > Some comments refer to Module::CPANTS::SiteKwalitee, but this > > > doesn't > > > seem to exist: > > > > > > e.g. in Module::CPANTS::Kwalitee::Distname: > > > > > > # NOTE: The metrics in this module have moved to > > > # Module::CPANTS::SiteKwalitee because these require an archived > > > # distribution which you don't have while testing local Kwalitee > > > # with Test::Kwalitee.
> > > > It's github-only. > > > > https://github.com/cpants/Module-CPANTS-SiteKwalitee > > > > I'll provide links to github when things are more settled.
> > a ha! > > FWIW, it might be worthwhile to split the Module::CPANTS::Kwalitee:: > namespace out into a separate dist too -- that will really help cut > down the MCA bug queue, as most of those tickets are related to > specific kwalitee metrics, not the engine itself.
I believe splitting would do more harm than help, at least for now, because quite a few metrics depend on the information analyzed elsewhere in Module::CPANTS::Kwalitee/Analyse, and otherwise, it'll be ineffective as each metric file would need to traverse the directory etc (it actually does the traversal several times now, and I really don't like that). Besides, where are you going to open tickets to request new metrics after we split the distribution? :)
Download (untitled) / with headers
text/plain 932b
On 2013-08-27 18:30:30, ISHIGAKI wrote: Show quoted text
> I believe splitting would do more harm than help, at least for now, > because quite a few metrics depend on the information analyzed > elsewhere in Module::CPANTS::Kwalitee/Analyse, and otherwise, it'll be > ineffective as each metric file would need to traverse the directory > etc (it actually does the traversal several times now, and I really > don't like that).
Ok, interesting, I was actually wondering about that (what dependencies existed between metrics and what analysis needed to be done first). I wonder if those dependencies could be codified, so if a particular analyzer hadn't run, then a metric can make sure it gets run? Show quoted text
> Besides, where are you going to open tickets to request new metrics > after we split the distribution? :)
I was figuring the core metrics would stay together, in Module::CPANTS::Kwalitee, so that would be the gathering place for most tickets.


This service is sponsored and maintained by Best Practical Solutions and runs on Perl.org infrastructure.

Please report any issues with rt.cpan.org to rt-cpan-admin@bestpractical.com.