Some of the new features follow:
Almost all the BackPAN distributions have also been analyzed.
You can subscribe your kwalitee report feed of your distributions (http://cpants.cpanauthors.org/author/PAUSEID/feed).
Finally Moose and friends are correctly considered as "use strict" equivalents, and new valid_signature metric is introduced (both have been implemented in Module::CPANTS::Analyse 0.86 months ago, but have not been introduced on the previous site for various reasons). On the other hand, some of the experimental metrics about debian packages are disabled because the data source has not been updated for a while.
If you find anything, tell me via github's issue tracker:
https://github.com/charsbar/www-cpants/issues
Happy holidays!
I also announce that I've unofficially set up a Module::CPANTS::* based site (http://cpants.charsbar.org/) to provide kwalitee data for acme.cpanauthors.org. As I found I would need significant changes at the first try (because the latest Module::CPANTS::Analyse doesn't correspond well with other Module::CPANTS modules, and they use old and deprecated ways of writing of Catalyst/DBIC), I tentatively set up a local repository and committed all the necessary changes there so as to hide all the dirty trial and errors. I'll move on to the public github repository when ready. So please be patient.
Compared to the transition from CPAN/CPANPLUS to App::cpanminus, PPM, which once used a remote API server but now downloads indices (summary) and store them in a local database, seems to be taking a different (or opposite) track. Its XML based spec is apparently old-fashioned (actually, the original Open Source Description spec, on which PPM spec was based, was deprecated years ago). And the one on the CPAN is way behind the one bundled in ActivePerl. Certainly it's not good for everyone.
However, ActiveState (and some other repositories) provides packages not only for perls for Windows, but also (threaded) perls for Linux and Mac OS X (and you can provide your own packages easily). If conditions are met, and you are a person who wishes to install modules with least hassles, or install the same modules into several or dozens of machines, PPM might be one of your options.
That said, there're several things we can/should improve now. I started writing a new PPM client (and an API server, which is not uploaded to anywhere but my dev server yet; I will create a public repository later, maybe after I refactor it a bit) so that you could use the latest PPM repositories even when you use other perls than ActivePerl. I also took over the maintenance of PPM::Make (to make a PPM repository), CPAN::Search::Lite (yet another CPAN search site with PPM support), and PAR::WebStart (to let CPAN::Search::Lite users to launch CPAN/PPM client from a page you visit via your web browser). If you have any issues, please let me know via RT or via email or via Github or whatever.
Thank you all in Taiwan. I really enjoyed OSDC this year. See you next year, or maybe in October in Japan :)
However, I sometimes felt sorry. YAPC::Asia is allegedly the largest YAPC with more than 500 attendees, but that's largely because Tokyo area is by far the largest metropolitan area with around 35 million people. Most of the attendees are Japanese. I don't have exact figure this year (as the organizers didn't use Act), but last year, only 22 people (of 539 registered people) were from abroad, and another dozen or so were (hopefully) English speaking people living in Japan (discerned by their name). As for talks, 23 (of 79 talks, including lightning ones and longer tutorials) were in English last year, 10? of 67 (plus several lightning talks) this year. For your information, 29 of 69 were English in 2008. 21 of 44 in 2007. 19 of 40 in 2006. Tendency is obvious.
I don't say this is completely a bad thing, as it denotes that YAPC::Asia has stimulated Japanese people quite impressively, at least in the Tokyo area, and several dozens of new speakers have been born. I even found several more people said they'd like to speak next year. That's really awesome.
But, too much Japanese talks started causing actual problems. This year we had no definite lunch time. You needed to go get some food outside the venue when you were hungry or maybe when there were no talks you really wanted to attend (the organizers didn't provide lunch this year). There were no English talks between 16:00 (day 1) or even 13:00 (day 2) and lightning talks (17:00), then dinner or closing. Actually some of the talks in-between had English slides to help them, but, oh well. You could chat. You could hack. You could walk around as weather was fine. Attending sessions is just a part of YAPC.
Lots of Japanese people take it for granted that YAPC::Asia will take place again in Tokyo (or at least in Japan) next year. I'm happy to believe Japan is one of the best places for YAPC (besides the natural language barrier (Japanese people are not so good at communicating in English), it is safe, has lots to see, has numbers of experienced and disciplined volunteers, to name a few). However, is it really good, especially for you in other areas of Asia, that YAPC::Asia will continue to be held in Japan for years to come? Isn't there anyone who wants to see YAPC::Asia in your area? A local Perl Workshop is sufficient for you? I wonder.