comment on

Hmmm, that's a pickle, and quite frankly, I've never thought about it (my employer does not own me, and I don't sign nothing).

A lot of patches I submit are very minimal and I can't imagine any IP issues arising. A typical example is rt.cpan.org: Bug #5614 unresolved external symbol _get_elapsed.

For my modules, I like all bug reports/suggestions/etc to be submitted via RT.cpan.org, so much for documentation I guess.

All the bug reports and patches I've gotten so far have basically been a courteous "you've missed a spot here/there", not amounting to much more than someone pointing out a typo (which I do credit the author for in a Changes file).

Do you really need permission from the person who owns you to point out a typo?

Does IBM have any guidelines?

MJD says "you can't just make shit up and expect the computer to know what you mean, retardo!"
I run a Win32 PPM repository for perl 5.6.x and 5.8.x -- I take requests (README).
** The third rule of perl club is a statement of fact: pod is sexy.

In reply to Re: What if it were you instead of Linus? by PodMaster
in thread What if it were you instead of Linus? by grantm

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.


Pathologically Eclectic Rubbish Lister
	PerlMonks