Beefy Boxes and Bandwidth Generously Provided by pair Networks
Keep It Simple, Stupid
 
PerlMonks  

comment on

( [id://3333] : superdoc . print w/replies, xml ) Need Help??

If you have had just one bug report for any of the modules, then you can claim (with justification) that your code is getting free external testing and that that is to the direct benefit of the company. If you have had a bug report with a suggested solution, and maybe even supporting unit test code, then you have a clearly winning argument.

Some of the module code I've released to CPAN has been developed on company time and the company is happy for me to do that. It was a real bonus when the first bug report come in and it fixed a potential issue in production code!


True laziness is hard work

In reply to Re: Need arguments to keep my modules on CPAN by GrandFather
in thread Need arguments to keep my modules on CPAN by dk

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post; it's "PerlMonks-approved HTML":



  • Are you posting in the right place? Check out Where do I post X? to know for sure.
  • Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
    <code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
  • Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
  • Want more info? How to link or How to display code and escape characters are good places to start.