I'm interested to know what type of measures folks around here take to address IP ownership issues when they accept or provide patches.
I know that the Cygwin project requires a copyright assignment from anyone who provides more than a "trivial"
patch. The assignment may have to include a statement from
the contributor's employer as well. http://cygwin.com/contrib.html
If your change is going to be a significant one in terms of the size of your code changes, be aware that you will have to sign over the copyright ownership of your code changes to Red Hat or the FSF (depending on the source file) before we can include your changes in the main source tree. Your employer may also have to send us a disclaimer stating that they have no claims to your contribution. This is necessary for liability reasons. Here is our standard assignment form for changes to Cygwin that you can fill out, sign, and send back. It shouldn't end up being that much of a pain. If you have any questions, please send them to the cygwin mailing list.
Perl itself is completely lax in this area, so
I find it hard to believe that they would require that
level of diligence.
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
Outside of code tags, you may need to use entities for some characters:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] ||