The goal of CPAN Digger is to help you find ways to improve CPAN modules. Originally it started with the list of packages most recently uploaded to CPAN. We assume that it is a lot more likely for a Pull-Reqest to be accepted in a project that recently saw activity than in a project that has not been changed for a long time.
We also show the releases of individual CPAN authors and every distribution on CPAN.
A number of issues we try to encourage people to fix.
- Make sure the META files include a link to the public VCS (Version Control System) of the project. This will let MetaCPAN display the link and it will make it easy for any potential contributor to find the VCS (git, mercurial, etc.) repository of the project. It will make it easier to contribute to the project.
- Explicit link to the bug-tracker of the project. If it does not exist in the META-files of the project, MetaCPAN will link to RT by default even if the project has a GitHub repository with Issues enabled. Even if you would like to use RT, it would be better to state this explicitely in the META files.
- CI - Most projects have test and Perl has the amazing CPAN Testers, but developers can get feedback to their source code from a Continous Integration (CI) system much faster. They can avoid releasing broken versions. They can also create setups that the CPAN Testers don't support. We would like to encourage setting up CI for each project.
- Have a valid license key in the META files will make it easier for a process to verify that all the packages in a dependency meet the licensing requirements of the project.
- CPAN Cover runs the tests of many CPAN uploads and collects the test coverage report of them. We include the percentages with a link to the full report. We would like to encourage people to contribute tests to open source Perl projects thereby increasing their quality.
- We think that the CPAN Dashboard could be a great tool for every CPAN developer. We would like to encourage CPAN authors to configure it for themselves.