Bug #85351 for MooseX-Daemonize: typo fixes

Thu May 16 06:37:18 2013 dsteinbrunner [...] pobox.com - Ticket created

Subject:

typo fixes

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

Thu May 16 12:57:58 2013 ether [...] cpan.org - Correspondence added

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>

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.

Thu May 16 12:57:58 2013 The RT System itself - Status changed from 'new' to 'open'

Thu May 16 13:15:02 2013 dsteinbrunner [...] pobox.com - Correspondence added

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?

Thu May 16 13:15:03 2013 ether [...] cpan.org - Status changed from 'open' to 'resolved'

Thu May 16 13:20:18 2013 ether [...] cpan.org - Correspondence added

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>

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

Thu May 16 13:30:33 2013 dsteinbrunner [...] pobox.com - Correspondence added

From:

dsteinbrunner [...] pobox.com

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.