Beefy Boxes and Bandwidth Generously Provided by pair Networks
Perl: the Markov chain saw

Re: Reporting bugs in corporate-sponsored CPAN code

by Joost (Canon)
on Oct 02, 2009 at 22:38 UTC ( #798951=note: print w/ replies, xml ) Need Help??

in reply to Reporting bugs in corporate-sponsored CPAN code

Personally, any module that's released via any work-related entity that I run into trouble with I patch and release publicly ASAP. That's just the most efficient way of dealing with it, but that's just because I'm usually the public maintainer of that code. When you're working with a large group so that changes may take more time, it might be a good idea to put the bug (and possibly patch) in whatever public ticketing system is the most useful - is available for all CPAN modules, but if you have your own system, it may be better to use that.

Aside from that, if you're putting up modules as "open source", I just want to plug as a code repository. It makes publicly forking / patching other people's code a breeze and gives you a very clear view of whatever other people are doing with the code.

edited to add: my repos @ github

Comment on Re: Reporting bugs in corporate-sponsored CPAN code

Log In?

What's my password?
Create A New User
Node Status?
node history
Node Type: note [id://798951]
and the web crawler heard nothing...

How do I use this? | Other CB clients
Other Users?
Others wandering the Monastery: (8)
As of 2015-11-28 00:14 GMT
Find Nodes?
    Voting Booth?

    What would be the most significant thing to happen if a rope (or wire) tied the Earth and the Moon together?

    Results (735 votes), past polls