[consulting] Contract protection clause

[jeff at ayendesigns.com]

One of the first clients I did work for back in 19<cough>, in BASIC 
<cough,cough>, had 'a system' for picking a horse. He created a database 
and kept it current with all stats.


If I had done it in Drupal, it would be (and usually is with GPL) 
complex. An application that reads a db, does some calcs and spits out 
some answers, ok. An application for picking a horse, ok. But the 
specific pieces of statistics he used, and how he used them, that was 
his IP. It's not a straight-forward thing protecting IP, but IP, at the 
end of a day, is the most important asset to any business, because 
without it, it wouldn't need customers or employees.



On 03/23/2011 01:43 PM, netsperience wrote:

>    In my contracts and proposals I state that the client is fully
> licensed to use the Drupal core and contributed modules code under the GPL
>
> I would further interpret that any custom modules I add to the project
> that work with the Drupal framework could fall under the same GPL
>
> It's also important to carefully read the contract provided by a client,
> I often annotate it when it states that client will "own" the code with
> a reference to the GPL: http://www.gnu.org/licenses/
>
> When I explain the reasons, and how the client is benefiting from the
> open source code we are using that was created by others, it is usually
> not a problem.
>
> The point in question seems to be more about intellectual property,
> probably from a client who recently saw "The Social Network" :)
>
> Randall Goya (decibel.places) http://netsperience.org
>
> Drupal: http://drupal.org/user/58977
> Twitter: http://twitter.com/decibelplaces
> Facebook: http://www.facebook.com/people/Decibel-Places/100000187748486
> LinkedIn: http://www.linkedin.com/in/rgoya
>
>
> _______________________________________________
> consulting mailing list
> consulting at drupal.org
> http://lists.drupal.org/mailman/listinfo/consulting