[consulting] copyright policies

[paola.dimaio at gmail.com]

Hi Ric,
I agree, but only in part.

I have designed 'functionalities' that were not there, they did not exist
that is because as a user, I spotted a requirement and asked a
developer to encode it
I ask the developers to a)not reuse it for at least one year. I am not
paying you so that you can go and sell my business intelligence to
others  2) do not sell it to my competitors for as long as I am i
business

if its an open source solution I am working with, I generally release
a portion of it for public use.

this is commonly done. every large company that uses open source will
not release
all the functionalities that are giving their business a competitive
market edge,  while also making some contributions to public code.

i think there should be a time cap to such restrictions however.

its very difficult to tell whether a developer is respecting the non
compete clause however

cheers
P

On Jan 25, 2008 12:39 PM, Ric Shreves <ric at waterandstone.com> wrote:
> If we, as developers, were not allowed to re-use code, then the
> impacts on pricing (and timelines) would be considerable (and
> negative). The reality of the situation is that code libraries are an
> integral part of a dev firm -- just as form libraries are integral
> parts of a lawyer's tools.
>
> At the end of the day, the client sd be paying for your expertise. The
> code is just a tool. As long as you are not re-selling the client's
> solution, lock, stock and barrel, then I see no problem -- either
> legal or ethical
>
>
> best,
> ric
>