develooper Front page | perl.module-authors | Postings from November 2011

Re: The module authors pledge

Thread Previous | Thread Next
Leon Timmermans
November 10, 2011 04:00
Re: The module authors pledge
Message ID:
On Tue, Nov 8, 2011 at 5:22 PM, Neil Bowers <> wrote:
> One of the problems I see with CPAN is that there are many modules
> which have been left unattended. Many of these have outstanding bugs,
> and a good number have patches and forked versions, some of which you can
> find on RT. You'll also find people offering to take over the maintainership
> of modules. While reviewing modules I've identified a lot of fixes, and
> documentation improvements, but it can take a lot of effort to get them out.
> If the author or current maintainer of a module is unresponsive, there's
> a well-defined, but lengthy, process to request co-maintainership.
> There are good reasons for this -- I'll assume you've read them.
> But in reality, plenty of authors lose interest
> To make life easier for the perl modules cabal, how about a voluntary
> pledge[*], which module authors can take publically, and in particular
> can take to I'll be emailing the following to
>    I hereby give permission to grant co-maintainership
>    to any of my modules, if the following conditions are met:
>    (1) I haven't released the module for a year or more
>    (2) There are outstanding issues on RT which need addressing
>    (3) Email to my CPAN email address hasn't been answered after a month
>    (4) The requester wants to make worthwhile changes that will benefit CPAN
>    Should I die, then the time-limits in (1) and (3) do not apply.
> This means it will be archived, and easily accessed. I'll put this in the
> README for my modules.
> If others, and particularly the modules cabal, think this is a good idea,
> maybe we could have a canonical place this this, which can be easily
> referred to. Perhaps PAUSE could let me record it, so there's one place
> the modules cabal can check? Or you could put it in module metadata?
> So, what do y'all think?

I've been having the same idea. I'd say the right place is a clearly
named file your CPAN home dir, preferably something explicit and
standardized about when you're ok with it and when not.


Thread Previous | Thread Next Perl Programming lists via nntp and http.
Comments to Ask Bjørn Hansen at | Group listing | About