Neither am I an attorney, but here is a snippet of a canned memorandum of understanding I gain agreement on when I start work for a new client:

15. Any custom scripts or forms developed for the client's web sites or server shall be jointly owned and copyrighted by the vendor and the client and the actual author(s) retained by the vendor to develop such scripts. Such scripts shall be licensed under the Gnu Public License and may be released by the vendor or the client under such terms to the general public, unless the subject of a seperate agreement prior to the development of such scripts.
Folks who know nothing about gpl focus on the hours, rates, deliverables. Folks who know about oss licensing issues focus on the hours, rates, deliverables. I have developed in house software that handled client specific applications in highly competitive, limited markets. That business logic was proprietary. And I agree with the comments above about the need to respect those boundaries if one expects the trust and continued business of a client.

But my stock contract, the point from where I start negotiations, is that I may, but am not required to release code developed under gpl, leaving me free to reuse code. The three days I spent on code for a previous client becomes the two hour solution for a new client.

-- Hugh

In reply to Re: self developed modules for client use by hesco
in thread self developed modules for client use by arc_of_descent

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


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • 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:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, 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, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.