Beefy Boxes and Bandwidth Generously Provided by pair Networks
Clear questions and runnable code
get the best and fastest answer

Re: Reporting bugs in corporate-sponsored CPAN code

by JavaFan (Canon)
on Oct 02, 2009 at 23:02 UTC ( #798953=note: print w/replies, xml ) Need Help??

in reply to Reporting bugs in corporate-sponsored CPAN code

I'd say what you should depends a lot on information that you aren't providing. What does your $WORK do with external bug reports? What does $WORK do with internal bug reports? How does $WORK appreciate internal bug reports that actually don't affect $WORK? Who's maintaining $WORK module? Is the CPAN version the same as the $WORK version? Can you just fix the bug and check in the code? Can you just walk up to the desk of the person who made the module and ask her/him to fix it?
  • Comment on Re: Reporting bugs in corporate-sponsored CPAN code

Replies are listed 'Best First'.
Re^2: Reporting bugs in corporate-sponsored CPAN code
by Tanktalus (Canon) on Oct 03, 2009 at 06:01 UTC

    Of course, answering those would only be helpful for my particular case. That said, I'd point out that in my case, the development of said module is corporately motivated (we don't sell the module - but we do sell the code that the module provides an interface to). And I do not have anything to do with development of said module, though I like to beat them about the head once in a while when it stops working for me. It was just this week that I realised that this may not be the community's preferred method, even if it provides me with a sense of temporary relief ;-)

    I have access to open internal bugs. I do not have authority to modify the code (i.e., I can, but that's due to a lack of control from the version control system, not because I'm supposed to, and there would be repercussions if I did). The $WORK version's sole purpose is to escape $WORK and be used by customers of the main product line, so I hope it matches CPAN, though I expect some sort of delay.

    And, no, I can't just walk up to their desk. For starters, I work from $HOME. Second, the development of said code has moved from our primary location to a location in the US. And from there, to India. (And I've not been picky - I pestered the developers that owned it back when my former team lead switched positions and took it over, as well as when it went to the US, and again in India - I'm an equal-opportunity basher, and I've not found one group particularly better or worse than another.) Getting to said desk would take all day. And a few grand.

    I guess the most important question you posed is what they do with external bug reports. The thing is, I don't know. That's a good question, and I should pose that to them next week. Thanks for that bit of the obvious: sometimes the obvious isn't so much when you're inside the box ;-)

      I guess the most important question you posed is what they do with external bug reports. The thing is, I don't know.
      I thought that one of the reasons why companies release software as open source is that it instantly gives them a free user and test-base and solutions to bugs may be "donated" to their software without costing them much. So, external bug reports should get equal --if not more-- attention than internal ones. One could even consider publishing the internal bug-reports on the external bug-tracker, in the hope that it gets solved faster and cheaper than doing it themselves.

      It probably also depends on whether the company still has an active team available dealing with the development and maintainance of this software.


      A program should be light and agile, its subroutines connected like a string of pearls. The spirit and intent of the program should be retained throughout. There should be neither too little or too much, neither needless loops nor useless variables, neither lack of structure nor overwhelming rigidity." - The Tao of Programming, 4.1 - Geoffrey James

      Of course, answering those would only be helpful for my particular case.
      Well, I would say your answers are only helpful in your particular case. But I think anyone who has a choice between reporting something internally or externally and who is wondering how to report a bug could benefit from thinking about the questions I raised. I don't think there's a general answer - each case will be different.

Log In?

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

How do I use this? | Other CB clients
Other Users?
Others surveying the Monastery: (4)
As of 2022-08-19 21:15 GMT
Find Nodes?
    Voting Booth?

    No recent polls found