The story of becoming a co-maintaner of Pod::Tree, improving its distribution, refactoring the code and even accepting contributions from other people.

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