Becoming a co-maintainer of a CPAN-module
The story of becoming a co-maintaner of Pod::Tree, improving its distribution, refactoring the code and even accepting contributions from other people.
- Becoming a co-maintainer of a CPAN-module - the first steps (Pod::Tree 1.17_01, 1.18)
- Update the packaging to include license and link to repository in the META files. Use GitHub as bug tracking. (Pod::Tee 1.19)
- Add Travis-CI for Continous Integration
- Refactoring the tests to use Test::More (Pod::Tree 1.20)
- Check test coverage - add compile tests
- Run Perl::Tidy on the code to make layout unified. Currently there is a mix of tab and spaces.
- Perl::Critic: use Path::Tiny instead of ReadFile and WriteFile
- use strict; use warnings; no diagnostics
- Perl::Critic: Move packages to their own files - release Pod::Tree 1.21
- Perl::Critic: fix the most important issues it finds and enable Test::Perl::Critic
- Refactor pod and code to eliminate indirect method calls
- Fixing the release, adding a version number (release Pod::Tree 1.22 and 1.23)
- Fix Perl::Critic test failures reported by CPAN Testers
- Enforce consistent version numbers of Perl all the modules in a distribution
- Perl::Critic exclude some policies - fix others (Pod::Tree 1.24)
- How to declare requirements of a CPAN distribution?
- Check CPANTS (Kwalitee)
- Eliminate more of the indirect calls
- Fixing test failure on Windows - Properly quoting regexes - Accepting GitHub pull request
- Set minimum version number in every Perl file
- Make the Changes file standard compliant
- Eliminate extensive use of short-circuit. For example is_ok $obj and $node = $obj, last;
- Write tests to check round-trip and what might be missing from the round-trip regenerating the original POD.
Published on 2015-09-14