<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html style="direction: ltr;">
<head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
</head>
<body style="direction: ltr;" bidimailui-charset-is-forced="true"
bidimailui-detected-decoding-type="UTF-8" bgcolor="#ffffff"
text="#000000">
<p style="margin-bottom: 0cm; margin-top: 0pt;">I have three clauses
in my standard contract that address this. One is to define the
licensing of elements (graphics, code, etc.). The second, below,
intellectual property...you would add to that list. The third is
about confidential information and the protection of it.</p>
<p style="margin-bottom: 0cm; margin-top: 0pt;"><br>
</p>
<p style="margin-bottom: 0cm; margin-top: 0pt;">Each party shall
retain ownership of the Intellectual Property that they possess
upon the signing of this contract. In the case of PROVIDER, this
includes, but is not limited to, functions, methods, libraries,
techniques, standards and general know-how with regards to
software development, subject matter, and web site development.</p>
<p style="margin-bottom: 0cm; margin-top: 0pt;"><br>
</p>
<p style="margin-bottom: 0cm; margin-top: 0pt;"><br>
</p>
<p style="margin-bottom: 0cm; margin-top: 0pt;">On 03/23/2011 11:51
AM, Joe Murray wrote:<br>
</p>
<blockquote
cite="mid:AANLkTimZE9mg3DbNQAs_guVVmY3kmnwo10dd_926i65D@mail.gmail.com"
type="cite">You might try a non-competiton clause, where the focus
is not on working with named competitors. You have to watch for
GPL violations in the terms of your contract. It is theoretically
possible to avoid GPL violations by doing code that only writes to
APIs rather than modifies other code that is integral to the
project, or by using data (ie configurations in the database). Of
course, this is not legal advice, and you should consult a lawyer.<br>
<br clear="all">
Joe Murray, PhD<br>
President, JMA Consulting<br>
<a moz-do-not-send="true"
href="mailto:joe.murray@jmaconsulting.biz">joe.murray@jmaconsulting.biz</a><br>
skype JosephPMurray twitter JoeMurray<br>
416.466.1281<br>
<br>
Message: 4<br>
<div class="gmail_quote">
<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt
0.8ex; border-left: 1px solid rgb(204, 204, 204);
padding-left: 1ex;">
Date: Wed, 23 Mar 2011 08:44:23 -0700<br>
From: Bob Morse <<a moz-do-not-send="true"
href="mailto:bob@morsemedia.net">bob@morsemedia.net</a>><br>
Subject: [consulting] Contract protection clause<br>
To: <a moz-do-not-send="true"
href="mailto:consulting@drupal.org">consulting@drupal.org</a><br>
Message-ID: <<a moz-do-not-send="true"
href="mailto:33DA2428-972C-4A75-AE33-97BACA672CB9@morsemedia.net">33DA2428-972C-4A75-AE33-97BACA672CB9@morsemedia.net</a>><br>
Content-Type: text/plain; charset=us-ascii<br>
<br>
We have a client who is concerned with protecting his new
Drupal website we will be developing. He is asking for a
clause in the contract that somehow states we will not turn
around and sell his site with a new design slapped on top to a
competitor. I'm not sure how to separate out, ahead of time,
what would be very common elements and what would be unique
based on the internal processes of a competing business.<br>
<br>
How might I write something that assures the client we won't
resell the unique aspects of his web application without also
writing something that prevents us from making a website for
another company that uses many of the same elements but with
the details being unique to that company's internal process
and interactions with clients?<br>
<br>
<br>
<br>
------------------------------<br>
<br>
_______________________________________________<br>
consulting mailing list<br>
<a moz-do-not-send="true" href="mailto:consulting@drupal.org">consulting@drupal.org</a><br>
<a moz-do-not-send="true"
href="http://lists.drupal.org/mailman/listinfo/consulting"
target="_blank">http://lists.drupal.org/mailman/listinfo/consulting</a><br>
<br>
<br>
End of consulting Digest, Vol 62, Issue 16<br>
******************************************<br>
</blockquote>
</div>
<br>
<pre wrap="">
<fieldset class="mimeAttachmentHeader"></fieldset>
_______________________________________________
consulting mailing list
<a class="moz-txt-link-abbreviated" href="mailto:consulting@drupal.org">consulting@drupal.org</a>
<a class="moz-txt-link-freetext" href="http://lists.drupal.org/mailman/listinfo/consulting">http://lists.drupal.org/mailman/listinfo/consulting</a>
</pre>
</blockquote>
</body>
</html>