Hi Darren, > I have a question concerning best practices for CPAN as they affect me. […] > > Due to various historical reasons I had until a few years ago considered CPAN > a good distribution mechanism for both Perl modules as well as standalone > documentation which didn't have any Perl code in it. Even with my > documentation-only distros I followed typical CPAN practices of writing them > as .pod files and giving them names that fit into the CPAN module namespace > and giving each version uploaded to CPAN a distinct version number. > > However, as various alternatives such as GitHub have matured I suspect that > using CPAN to distribute documentation-only things is not that appropriate > and that such things should go out on other channels. > > My question for you is partly whether there is any other precedent than my > own usage for putting tarballs on CPAN that contain only documentation, or > whether everyone else has always used them for this with actual code. > […]
If the documentation is related to Perl in some way, then I think it’s fine. And there are advantages to putting it on CPAN: People can find & read it online via MetaCPAN People can install it and use perldoc on it If it’s not related to Perl in any way, for example a Blueberry muffin recipe, then it doesn’t really belong on CPAN (but feel free to send me a copy ;-) Cheers, Neil
