Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • ...interesting.

    The Database: cpanstats.db.gz (2008/08/05) (0MB compressed, 411MB uncompressed)

    • Can I also note that I'm finding that the "current month" numbers cause more harm than good, since they invariable show a massive "crash" in testing numbers for the current month.

      Unless you plan to estimate the current month forwards by a $current * $monthdays / $monthday type multiplication, we're far better off without it on the graph.

    • Fixed for the next update. The path to the compressed file was incorrect :(
  • You don’t have an on-site newsfeed. Your use.perl journal is sufficient for those of us who subscribe to all use.perl journals, but as a way of providing a dedicated feed for the site (and as a place for permalinks), it is not that great.

    Is stats.cpantesters.org driven by any sort of CMS? Is the code available somewhere? I would volunteer to write a patch. (Alternatively, if you take a look at XML::Atom::SimpleFeed [cpan.org], that should make it a snap to add a feed.)

    • Good idea I'll have a look at that. At the moment the site is built as a static site on a daily basis, So it might even make it easier creating the templates and the XML feed as I add a new entry.

      The current code is all available in the tarball (see the link at the bottom of the index page), although a lot is shortly going to change once the new generator code is in place.

      • Ah, I didn’t notice that.

        Hmm, the 0.46 tarball is a 404 and the -latest tarball only contains 0.44.

        Hmm, you have all the updates in a single big file without detailed dates. That’s not ideal to retrospectively generate timestamps from… do you have each change of the update.html recorded in a repository? It would be nice not to have to make up datetimes with an empty time part.

        Also, once you start to generate feeds it would be nice for each update to have a separate permalink. That’s

        • Hmm, the 0.46 tarball is a 404 and the -latest tarball only contains 0.44.

          Oops sorry about that. All fixed. I forgot to update the the mainsite with the last two updates.

          Regards the feed, I'll set that up so the content is driven from a standalone file, that will also be used to create the templates for the main static site, for the update pages and the index.