Re: Give up your modules!
Johan Vromans writes: First of all, one needs to know that there are bugs. Currently, only bugs that get reported via RT are automatically transmitted to the author. Are they all? I'm pretty sure I've encountered a case of not getting them for a module I took over maintenance of. When reporting a bug I always look at the module's doc and if the maintainer doesn't specifically mention RT then I instead use the e-mail address he does provide. But failed CPAN tests are not reported automatically. I think I've had reports from there mailed to me. Neither are discussions on annocpan, That was discussed on this list soon after it launched. My memory is that we decided that it was OK for AnnoCpan to alert an author the first time a comment is made on her module, and then give the option of subscribing to future alerts. Smylers
Re: Give up your modules!
- Original Message From: [EMAIL PROTECTED] I hate to let go, and would like to remain a consultant (!), but I'm willing to hand over my modules; listed below. Thanks in advance to anyone willing to take on the burden. That sounds great. I'm glad to hear you're willing to do this. Of course, you could always just offer co-maintainership via PAUSE if you don't want to give them up completely :) I know some authors have had a lot of success with similar announcements on Perlmonks or even use.perl. Cheers, Ovid -- Buy the book -- http://www.oreilly.com/catalog/perlhks/ Perl and CGI -- http://users.easystreet.com/ovid/cgi_course/
Re: Give up your modules!
On 15 Aug 2006, at 21:35, A. Pagaltzis wrote: * Sébastien Aperghis-Tramoni [EMAIL PROTECTED] [2006-08-15 12:40]: Looking at the recent and past history of the CPAN, I'd say that forks usually happen for young modules with very active development (see the Class::DBI / DBIx::Class case). Just to clarify this point, DBIx::Class is *not* a fork of Class::DBI *at all*. Neither is Class::DBI young (at least not by my definitions :-) Adrian
