These same issues recently came up around the Apache::Session module. 
Jefery Baker maintained that module for years, and then for about 2
years there were no releases.  There were a couple of annoying bugs
that never got fixed that tripped up a lot of people.

However,  once enough of a stink was made, Jefery noticed what was
going on, released a new version with the pending patches, and
voluntarily handed over maintainance to Casey West after a call for a
new maintainer.  The relevant thread is here:

http://www.jsw4.net/info/list-archives/mod_perl/04-wk08/msg00060.html

The original thread that sparked the response from Jefery is here:

http://www.jsw4.net/info/list-archives/mod_perl/04-wk08/msg00054.html

I just mention this to remind anyone looking to take over a module to
do it in a courteous manner.  Remember, "Do not meddle in the affairs
of Perl Programmers for they are subtle and quick to anger" (Sorry
JRRT :).  Going to the modules authors list should be a last resort,
and they will expect a full year of silence from the author before
they will consider handing over a module.

I would ask on the module authors list for an alternate contact
address for the maintainer, and mention what you would like to do to
improve the module, and why it is necesary.  Having patches ready is
also important.

If the author responds, has no time to work on the module, but is
still hesitant to hand it over (after all he/she may not know you and
will want only the best for their module), then I'd package up a
release with all outstanding patches, fully test it and mail it over. 
The owner would then only need to untar it, test it and see if it is
safe to upload.  You may loose out on some of the glory, but things
will get moving again.

So remember, use baby steps...

Cheers,

Cees


On Tue, 19 Oct 2004 14:22:57 -0500, Jason A. Crome <[EMAIL PROTECTED]> wrote:
> As would I :)  I'm not excited about maintaining a fork, but I'd rather do
> that than let C::S languish.
> 
> I think I am going to post to the Perl module authors mailing list and think
> some more about a possible fork.  I'll keep the list posted.
> 
> 
> 
> Jason

---------------------------------------------------------------------
Web Archive:  http://www.mail-archive.com/[EMAIL PROTECTED]/
              http://marc.theaimsgroup.com/?l=cgiapp&r=1&w=2
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to