aixtal

Recent Actions

• Commented on What's wrong with CPAN?
  >Why do you think the review system is "unpractical and obsolete"? Hard to say, but the fact is that almost nobody uses it. I can still see a few points that are annoying. - The login system (bitcard) is too...
• Commented on What's wrong with CPAN?
  I would add Lack of community tools and therefore engagement, reviewing, etc. Of course there is a review system on CPAN, but it is unpractical and obsolete. As a result, even a widespread module such as LWP has had only...

Comment Threads

• robrwo.myopenid.com commented on What's wrong with CPAN?

  I think the module information could be crowd-sourced. Users (using Google/Twitter OpenID/OAuth accounts) log in to the system, and post annotations to distributions:
  - reviews (using cpanratings)
  - bug reports (using rt)
  - annotations (using annocpan)
  - links to relevant questions on trusted forums like stack exchange or mailing list archives
  (some of this might be machine-generatable)
  - similar modules

  Other users can vote up/down on these annotations.

• Olaf Alders commented on What's wrong with CPAN?

  Not a stretch at all. That's a feature request that would belong in metacpan-web. :)

• Olivier Mengué (dolmen) commented on What's wrong with CPAN?

  Another metric of the "CPAN community engagement" would be some statistics on rt.cpan.org tickets.

  Check this gist for some tools to query RT.

• Neil Bowers commented on What's wrong with CPAN?

  Spooky timing. I was working on this over the weekend, and have RT as one of the inputs, but couldn't work out how to get the info I was after. So emailed the perl RT support. Thanks.

• Duncan commented on What's wrong with CPAN?

  There are quite a lot of modules on CPAN which are over ten years old and which haven't seen an update in that time. That doesn't mean that they need an update, but it does show that the timelines are quite long.

  I think it would be worth adding a heartbeat function. Every user who maintains at least one module should get an email once per year asking them to confirm their details. (That's one per author per year, not one per author per module per year.)

  If they fail to reply for five years then they should be removed from the list of maintainers of their modules. Any modules…