• Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
    Be the first to like this
No Downloads

Views

Total Views
404
On Slideshare
0
From Embeds
0
Number of Embeds
0

Actions

Shares
Downloads
10
Comments
0
Likes
0

Embeds 0

No embeds

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
    No notes for slide

Transcript

  • 1. CPANTS 2012 OSDC.TW April 15, 2012 Kenichi Ishigaki (@charsbar)
  • 2. 你好
  • 3. I‘m charsbar ( 石垣 憲一 ),from Shibuya.pm, Tokyo, Japan.
  • 4. Im glad nothing is shaking orswaying this year.
  • 5. Today Ill talkabout something called CPANTS and Kwalitee.
  • 6. So, whatsCPANTS?
  • 7. CPAN Testing Service.
  • 8. One of the QAtools to keep CPANhealthy and useful.
  • 9. Actually, we have another tool ofthe same origin.
  • 10. CPAN Testers.
  • 11. Whatsdifferent?
  • 12. Both of them do testing.
  • 13. CPAN Testers test things module authors wrote to assure quality
  • 14. and portability.
  • 15. Theyre doingreally awesome.
  • 16. Lets see.
  • 17. CPAN Testersare not perfect, though.
  • 18. They cant help if authors dontwrite (good) tests.
  • 19. CPANTS tests things moduleauthors dont(or cant) test.
  • 20. Your distribution is really extractable?
  • 21. If not,we cant use it.
  • 22. Does it use"strict" pragma in everywhere?
  • 23. If it does,Perl guesses less.
  • 24. That makes iteasier for people to collaborate.
  • 25. Does it have POD tests?
  • 26. If it does, youll haveat least readable documentation.
  • 27. Is it used inother modules?
  • 28. If it is, someonethinks it useful.
  • 29. And so on.
  • 30. We have 24 tests, plus 10 extras now toassure Kwalitee.
  • 31. Some of them are "nice to have."
  • 32. Some of them are what annoyed people in the past.
  • 33. Broken meta data.
  • 34. Broken build tool.
  • 35. Versioninconsistency.
  • 36. License issue.
  • 37. You probablycant remember all of the past incidents.
  • 38. CPANTS can.
  • 39. Thats one of thereasons why CPANTS is important.
  • 40. To attract attention,CPANTS also offers a "game".
  • 41. More than 50authors share the highest markaround the world.
  • 42. As for Taiwanese,Gugod is maintaining a nice list.
  • 43. Acme::CPANAuthors::Taiwanese
  • 44. With a simplescript, youll get a list like this.
  • 45. Most Kwalitativeauthors in Taiwan (with 5 or more dists)
  • 46. Name KwaliteeDRBEAN 98.214CINDY 95.833GSLIN 95.313CLSUNG 94.583SHELLING 94.444SNOWFLY 92.262AUDREYT 91.837IJLIAO 91.667CORNELIUS 90.694GUGOD 90.126
  • 47. Note thatKWALITEE ISNOT QUALITY.
  • 48. Kwalitee is notkind for peoplewith long track record.
  • 49. Anyway.
  • 50. You can get a lot of information from the CPANTS site.
  • 51. However.
  • 52. CPANTS projecthad not been in a good state for some time.
  • 53. I wanted to useits database at YAPC::Asia, but I couldnt.
  • 54. So I decided to set up my own mirror.
  • 55. cpants.charsbar.org
  • 56. I fixed some ofthe major issues at that time.
  • 57. But there are toomany things to be done.
  • 58. Ive been working on its refactoring.
  • 59. As a proof of concept, Ive renewed anAcme::CPANAuthors site.
  • 60. acme.cpanauthors.org
  • 61. I also testedqueries not to scan tableswithout using indices.
  • 62. During Perl QAHackathon held inParis this spring,
  • 63. cpants.perl.orgstarted redirecting to my mirror.
  • 64. New metrics is on the way.
  • 65. Moose and thelikes will be takeninto account soon.
  • 66. Theres still lots to be done.
  • 67. Fasterworker/analyser. Query tuning.
  • 68. Better UI.
  • 69. JSON API.Incoming links.
  • 70. More metrics. More tests.
  • 71. If you find anything, feelfree to ping me.
  • 72. Metrics repository:github.com/daxim/Module-CPANTS-Analyse Acme site repository:github.com/charsbar/www-acme-cpanauthors IRC channel: #perl-qa on irc.perl.org
  • 73. 問題 ?
  • 74. 謝謝