On 2013-11-21, at 9:06 AM, David Cantrell wrote: > On Wed, Nov 20, 2013 at 12:29:37PM +0200, Gabor Szabo wrote: > >> I tried to collect my thoughts and your comments on getting more >> people to use MetaCPAN instead of search.cpan.org. >> >> It is not going to be easy and thus it got a bit long: >> http://szabgab.com/moving-from-sco-to-metacpan.html >> >> I'd be glad to read your opinion on this! > > The most important issue to address is why should we prefer metacpan to > search.cpan. You don't cover this at all.
I'm not here to tell anyone which site to prefer, but a few things that MetaCPAN has to offer: 1) Author profile pages * This can make it much easier to track down an author who is MIA. If you've added your G+, Twitter, etc to your profile, we now have multiple ways of trying to contact you about the patch you never applied. 2) ++ * This gives you a simple bookmarking system to track modules you approve of * This gives other people an idea of what is generally found useful among CPAN authors 3) Linking to line numbers in source code. * Being able to refer to an exact line of source is quite valuable: https://metacpan.org/source/MIYAGAWA/Plack-1.0029/lib/Plack/App/File.pm#L70 4) Easy links to repositories * When you want to patch something, just look to the left and you'll find the repo link, provided the author has added it to the META.* files 5) [Insert feature here] * It's easy to patch MetaCPAN. Many fixes and/or features get deployed on the same day they're submitted. MetaCPAN isn't perfect and some people just prefer search.cpan.org. It's good to have choices. What Gabor is addressing, though, is that since MetaCPAN doesn't do well with Google, people are often just presented with *one* option (search.cpan.org) when searching for a module. That's what we'd like to fix. Olaf -- Olaf Alders o...@wundersolutions.com http://www.wundersolutions.com http://twitter.com/wundercounter
