On 2004-10-19, Cees Hek <[EMAIL PROTECTED]> wrote:
>
> 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.
That's how I became the co-maintainer of CGI::Application. :)
I collected patches for what seemed should go in the next release. Then
I presented the "release candidate" to Jesse, who was being unresponsive
at the time. It worked. Not only did we get a release shortly
afterwards, Jesse seemed sufficiently impressed with my efforts that he
made me an official co-maintainer (as far as CPAN/PAUSE is concerned).
The benefit of this route is that if your release candidate receives no
response from the author, you've got a great start on a fork. :)
Mark
--
http://mark.stosberg.com/
---------------------------------------------------------------------
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]
