Skip Menu |
 

This queue is for tickets about the MooseX-Daemonize CPAN distribution.

Report information
The Basics
Id: 85351
Status: resolved
Priority: 0/
Queue: MooseX-Daemonize

People
Owner: Nobody in particular
Requestors: dsteinbrunner [...] pobox.com
Cc:
AdminCc:

Bug Information
Severity: (no value)
Broken in: (no value)
Fixed in: 0.18



Subject: typo fixes
Download (untitled) / with headers
text/plain 343b
MooseX/Daemonize/Core.pm 48: compability -> compatibility 92: numnber -> number 197: aquiring -> acquiring 230: compatability -> compatibility 238: compatability -> compatibility 280: compatability -> compatibility MooseX/Daemonize.pm 222: dont -> don't 360: persistant -> persistent 419: aquiring -> acquiring 543: overriable -> overridable
Subject: Re: [rt.cpan.org #85351] typo fixes
Date: Thu, 16 May 2013 09:57:40 -0700
To: "dsteinbrunner [...] pobox.com via RT" <bug-MooseX-Daemonize [...] rt.cpan.org>
From: Karen Etheridge <ether [...] cpan.org>
Download (untitled) / with headers
text/plain 914b
On Thu, May 16, 2013 at 06:37:19AM -0400, dsteinbrunner@pobox.com via RT wrote: Show quoted text
> > MooseX/Daemonize/Core.pm > 48: compability -> compatibility > 92: numnber -> number > 197: aquiring -> acquiring > 230: compatability -> compatibility > 238: compatability -> compatibility > 280: compatability -> compatibility > > MooseX/Daemonize.pm > 222: dont -> don't > 360: persistant -> persistent > 419: aquiring -> acquiring > 543: overriable -> overridable
You've submitted a rather large number of tickets such as these to many distributions. Have you considered instead, either: - sending patches that can be easily applied to the source, or - writing and releasing a Test::* module that can check for issues such as this? I understand you mean well, but submitting manually-produced tickets that require manual action, for spelling mistakes *in code comments*, is not the most productive use of anyone's time.
From: dsteinbrunner [...] pobox.com
On Thu May 16 12:57:58 2013, ETHER wrote: Show quoted text
> You've submitted a rather large number of tickets such as these to > many > distributions. Have you considered instead, either: > > - sending patches that can be easily applied to the source, or
I do for projects on github because it is easy for me to do. It is easiest to submit these types of bugs for projects without repos or non github repos. Show quoted text
> - writing and releasing a Test::* module that can check for issues > such as > this?
I have thought about it bit I for the moment at least parts of the checking seems to need human filtering. Show quoted text
> I understand you mean well, but submitting manually-produced tickets > that > require manual action, for spelling mistakes *in code comments*, is > not the > most productive use of anyone's time.
You could choose to ignore the corrections or ask for a patch. I have come across maintainers that are happy just to have the feedback but I can imagine getting lots of it can be tedious. I'll try to send patches when I see you are the maintainer. Deal?
Subject: Re: [rt.cpan.org #85351] typo fixes
Date: Thu, 16 May 2013 10:20:03 -0700
To: "dsteinbrunner [...] pobox.com via RT" <bug-MooseX-Daemonize [...] rt.cpan.org>
From: Karen Etheridge <ether [...] cpan.org>
Download (untitled) / with headers
text/plain 1023b
On Thu, May 16, 2013 at 01:15:03PM -0400, dsteinbrunner@pobox.com via RT wrote: Show quoted text
> I do for projects on github because it is easy for me to do. It is easiest to submit these types of bugs for projects without repos or non github repos.
A ha, I see the problem! Would you like a commit bit for the repositories hosted on gitmo (lots of Moose extensions?) :) (You can also fork a repository on github that isn't on github originally -- I submitted a lot of my early Moose patches that way, before I got a commit bit.) Show quoted text
> You could choose to ignore the corrections or ask for a patch. I have come across maintainers that are happy just to have the feedback but I can imagine getting lots of it can be tedious. I'll try to send patches when I see you are the maintainer. Deal?
ok! I don't want to dissuade you, as you are definitely improving the dists you touch... I guess I'm a victim of having been given comaint on lots of dists that were originally written by... shall we say, not the most literarily-inclined :D
From: dsteinbrunner [...] pobox.com
Download (untitled) / with headers
text/plain 822b
On Thu May 16 13:20:18 2013, ETHER wrote: Show quoted text
> On Thu, May 16, 2013 at 01:15:03PM -0400, dsteinbrunner@pobox.com via > RT wrote:
> > I do for projects on github because it is easy for me to do. It is
> easiest to submit these types of bugs for projects without repos or > non github repos. > > A ha, I see the problem! Would you like a commit bit for the > repositories > hosted on gitmo (lots of Moose extensions?) :) > (You can also fork a repository on github that isn't on github > originally > -- I submitted a lot of my early Moose patches that way, before I got > a > commit bit.)
I might go for forking from github but it would seem that since Moose itself seems to have been moved to github that the rest of the gitmo would move there, also.... Of course, that is just an outsiders view of it.


This service is sponsored and maintained by Best Practical Solutions and runs on Perl.org infrastructure.

Please report any issues with rt.cpan.org to rt-cpan-admin@bestpractical.com.