Every distribution should have a LICENSE file, that corresponds to the licensing information contained in your Makefile.PL.
You can create this file from the command line by installing App::Software::License - e.g.
cpanm App::Software::License. Then, just invoke the
Last week, I travelled to Lyon, France for my first QA
. Although it is even longer
than a YAPC (four full days rather than three), there were no formal talks, no
job fair... just thirty Perl programmers put together in a few rooms to work
on problems together and improve the Perl ecosystem. I felt very privileged to
have been invited, and came ready with a list of projects, problems, and
topics of conversation.
Is the PAUSE module list (www.cpan.org/modules/00modlist.long.html) useful anymore? Do any cpan clients, or other tools, make use of it?
I've seen many users (via http://www.nntp.perl.org/group/perl.modules) isubmit their module for registration immediately after upload, so there seems to be an impression that it is a necessary step, despite the PAUSE documentation saying it's not (however it is quite vague as to *how* useful this measure actually is).
This list doesn't even seem to be up to date - e.g. I don't see my module Test::LWP::UserAgent in the list, despite registeri…
A few weeks ago a casual exchange occured on irc... I might as well quote it rather than paraphrase: