Hey #CPAN authors, you have Opinions on how to best develop and package #Perl modules. What's the best way in 2025?

I've used Dist::Zilla, but there are other options that might encourage contributors who don't use it. What are they?

I'm using a plain ExtUtils::MakeMaker-based setup for https://metacpan.org/dist/Log-Any-Adapter-MacOS-OSLog, but keeping prerequisites and version numbers in sync is a chore. I'd like to adopt a better workflow for my other dists.

Log-Any-Adapter-MacOS-OSLog-v0.0.1

log to macOS' unified logging system

MetaCPAN

Sorry to all the #dzil haters, but in the end I'm going back to Dist::Zilla for this and my other #Perl #CPAN distributions. I tried the alternatives, but they all failed me for one reason or another.

And in the end, it's just hard to argue with a negative line count delta.

The good news is that I've got it configured to maintain build/main and build/release branches that one can fork and contribute to without having to install all my dependencies.

I think I feel another blog post coming on.

@mjg I have been slowly moving my modules to Dist::Zilla. It helps me ensure that I don't miss steps. My only issue is that they are all a bit of a mishmash of plugins at the moment. I really need to figure out the author bundles...
@timlegge I also have ambitions of an author bundle, especially since I now have a configuration that enables both DZil and plain contributors.