I would LOVE to have access to this stuff, for many of the same reasons. Knowing what to support, knowing how safe it might be to change an API ( pretty safe if nobody uses it ).

But on the subject of implementation, I don't understand why everyone is having such difficulties coming up with a solution.

Just put an entry in wherever we keep the other CPAN configuration and do an always|never|ask config entry that starts with 'ask' by default.

(During CPAN.pm first setup)

To better understand how often and where modules are being
used, so they can be better supported, CPAN.pm can allow
modules the option of reporting back ONLY your platform
(Linux) and perl version (5.005_03) whenever that module
is installed. These support statistic are aggregated
centrally, and no other information about you is recorded.
It would be greatly appreciated if you could report your
use to help us make CPAN better for you.

Report usage and platform statistic (ASK/always/never)

[download]

If you always want to report, then it's done transparently in the back on any install. If you never want to report, we just never do it. If set to ASK ( the default ), you would get.

This module would like to report back usage and platform
statistics containing only your platform (Linux) and perl
version (5.005_03) to the CPAN statistics server at
stats.cpan.org. This support statistics are used to help
the developers which modules and platforms need the most
attention paid to them.

Report support statistics for this install? (YES/no/always/never)

[download]

This follows a couple of basic principles.

1. Default to reporting
2. Never actually report without approval
3. Make it trivially easy to permanently disable at any time
4. Make it easy for people to report.

In some theoretical forced-non-interactive run ( can we do this? ) we would just not report for that run, and ask next time we did an interative installation.

This covers both the "just fuck off and die" and the "I'd love to help, as long as I don't have to do anything" cases quite cleanly.

Putting the stats stuff into CPAN.pm is good enough for now. I guess we could theoretically allow the database to record statistics in several different catagories... so you could write a mirror log stats interface to the same stats system? Or possibly ever hook into other types of things, like debian mirror logs etc. Anyway, I'm drifting into speculation land here.

Comments?

In reply to Re: Gathering module usage statistics by Anonymous Monk
in thread Gathering module usage statistics by Juerd

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.