IvorW combobulus at
Wed Mar 1 14:11:20 GMT 2006

> -----Original Message-----
> From: Jacqui Caren [mailto:jacqui.caren at]
> Sent: 01 March 2006 13:38
> To: Perl M[ou]ngers
> Subject: Re: Devel::LeakTrace
> Andy Armstrong wrote:
> > The problem with keeping the change to the minimum required 
> in this  
> > case is that apart from a bit of boiler plate the module just  
> > implements a fairly simple algorithm - and it's the algorithm that  
> > doesn't scale. So most of it will have to change.
> Which usually takes a while longer for an author to review :-)
> It would be NICE if people replied saying thanks for your
> patch, I will look at it in ~Feb and should get back to you
> Marchish, but it almost never happens.
> At least an email like that gives you a chance to send a
> timely reminder, without hassling.
As an author, I tend to respond to the initial email, definnitely thanking if a patch is involved. Personally I tend to be wary of committing to dates, as my CPAN development time is strictly spare time only, not work time.

I also usually recommend that the corresponent raises an RT ticket and posts the patch there. That way, others can see and use the patch.

The worst experience I've had was with notification coming via cpanra(n)?tings, by way of an adverse review. I know my main published CPAN address was deliberately blocked, but this was previously acting as a venus spamtrap. The module in question had a different email address which would have worked, and instructions to submit a bug report via RT, so I was mightily peeved.

In my books, the Perl world is a community, and works really well if everyone behaves sensibly. So, let's not piss in the cider vat.


More information about the mailing list