David Golden wrote:
I want to endorse imacat on her contributions. She runs one of the best
smoke testers on cpan-testers: it's really strict and seems to catch
lots of people out on subtle dependency problems. She's also been very
responsive to questions I've had about failed test report
On Aug 24, 2006, at 7:58 AM, Shlomi Fish wrote:
Maybe it would be a good idea to spend some TPF (or whatever)
grants on giving
bounties for resuming maintenance of several critically
unmaintained CPAN
modules? With their authors' permissions, of course.
In that case, I think I'll abandon
On 24 Aug 2006, at 16:05, imacat wrote:
Hope this helps. Please tell me if you need any more information.
That's great, thanks - I'll give it a try.
--
Andy Armstrong, hexten.net
On Thu, 24 Aug 2006 14:05:34 +0100
Andy Armstrong <[EMAIL PROTECTED]> wrote:
> On 24 Aug 2006, at 13:59, David Golden wrote:
> What specifically is imacat doing that makes her an example of best
> practice and how may others do something similar?
This may be off-topic. I do not know what is
On 24 Aug 2006, at 14:13, David Golden wrote:
She would have to answer that definitively, but from what I can
tell, it looks like she might be using an isolated, fresh perl
installation (that isn't even in the $PATH) that gets reset after
each smoke. From test reports I've seen, it looks li
Andy Armstrong wrote:
What specifically is imacat doing that makes her an example of best
practice and how may others do something similar?
She would have to answer that definitively, but from what I can tell, it
looks like she might be using an isolated, fresh perl installation (that
isn't e
On 24 Aug 2006, at 13:59, David Golden wrote:
I want to endorse imacat on her contributions. She runs one of the
best smoke testers on cpan-testers: it's really strict and seems to
catch lots of people out on subtle dependency problems. She's also
been very responsive to questions I've had
On Thursday 24 August 2006 15:43, Dana Hudes wrote:
> Just because I haven't had time to update Net::Whois in years doesn't
> mean I haven't got plans or indeed scraps of code. It actually is an
> interesting case because its really a wrapper around external service
> which refuses to standardize (
imacat wrote:
On Thu, 24 Aug 2006 09:46:33 +0100
Oh I see. You may not know me. I personally have submit numerous
patches, bug reports, tests reports, debug reports to numerous packages,
perl modules or not. You may not know how much time I have spent on
submitting patches and bug reports
Just because I haven't had time to update Net::Whois in years doesn't
mean I haven't got plans or indeed scraps of code. It actually is an
interesting case because its really a wrapper around external service
which refuses to standardize (despite efforts toward that) and changes
willy-nilly. It
On Aug 24, 2006, at 4:31 AM, Ovid wrote:
- Original Message
From: Ken Williams <[EMAIL PROTECTED]>
Having a "name and shame" mentality about this is IMO wrong.
I hope you're not saying I suggested that. I did not name anyone.
I didn't ask for a list of modules whose authors we
On 24 Aug 2006, at 08:33, Andreas J. Koenig wrote:
That's what the DSLIP status already knows as
S (Support Level): a (abandoned)
I guess the problem is that there's not a pervasive culture of people
setting their modules to abandoned when they decide to abandon them.
I imagine that a lot
On Thu, Aug 24, 2006 at 06:46:56PM +0800, imacat wrote:
> Oh I see. You may not know me. I personally have submit numerous
> patches, bug reports, tests reports, debug reports to numerous packages,
> perl modules or not. You may not know how much time I have spent on
> submitting patches an
On 24 Aug 2006, at 08:09, Johan Vromans wrote:
Maybe it is just a little thing, but it might be a small step forward:
how about adding a CPAN flag indicating the author has given up
interest in maintaining a specific module? This makes it easy for an
author to formally give up a module, without h
On Thu, 24 Aug 2006 09:46:33 +0100
Nicholas Clark <[EMAIL PROTECTED]> wrote:
> On Wed, Aug 23, 2006 at 06:52:26PM +0800, imacat wrote:
> > I'm not a skilled C/XS programmer, or I would consider taking over
> > them. Can anybody have advice on this issue?
> The author made these modules availab
- Original Message
From: Ken Williams <[EMAIL PROTECTED]>
> Having a "name and shame" mentality about this is IMO wrong.
I hope you're not saying I suggested that. I did not name anyone. I didn't
ask for a list of modules whose authors we should hunt down.
I only asked for those auth
> On Thu, 24 Aug 2006 09:41:31 +0200, Johan Vromans <[EMAIL PROTECTED]>
> said:
> [EMAIL PROTECTED] (Andreas J. Koenig) writes:
>> That's what the DSLIP status already knows as
>>
>> S (Support Level): a (abandoned)
> Yes, but instead of "abandoned" I was thinking of "scheduled t
On Thu, Aug 24, 2006 at 03:16:22PM +0800, imacat wrote:
> On Wed, 23 Aug 2006 14:28:13 +0100
> Nicholas Clark <[EMAIL PROTECTED]> wrote:
> > On Wed, Aug 23, 2006 at 06:52:26PM +0800, imacat wrote:
> > > But this ain't right. Crypt-Cracklib is critical to security and
> > > user management, Cry
See:
http://community.livejournal.com/perl/126545.html
for a special offer of the Web-CPAN.berlios.de project to get an "Ozy and
Millie" T-Shirt in exchange for code contributions.
So fire up your text editor and start writing some code!
Regards,
Shlomi Fish
-
[EMAIL PROTECTED] (Andreas J. Koenig) writes:
> That's what the DSLIP status already knows as
>
> S (Support Level): a (abandoned)
Yes, but instead of "abandoned" I was thinking of "scheduled to be
abandoned", where the original DSLIP flag still has value.
Maybe this is a bit too much of fine-tu
> On Thu, 24 Aug 2006 09:09:55 +0200, Johan Vromans <[EMAIL PROTECTED]>
> said:
>> That said, there ought to be a way for the community to move forward
>> without having the original author be the bottleneck.
> Maybe it is just a little thing, but it might be a small step forward:
On Wed, 23 Aug 2006 14:28:13 +0100
Nicholas Clark <[EMAIL PROTECTED]> wrote:
> On Wed, Aug 23, 2006 at 06:52:26PM +0800, imacat wrote:
> > But this ain't right. Crypt-Cracklib is critical to security and
> > user management, Crypt-Rijndael is the current US governmental standard
> > encryption
Ken Williams <[EMAIL PROTECTED]> writes:
> The fact that they made their contribution in the first place, and
> people found it useful, seems like it should be honored rather than
> vilified.
I agree fully.
> That said, there ought to be a way for the community to move forward
> without having t
23 matches
Mail list logo
