[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: reinvent (for GPL) code u wrote for employer who owns it?

From: Alexander Terekhov
Subject: Re: reinvent (for GPL) code u wrote for employer who owns it?
Date: Thu, 26 Mar 2009 11:19:41 +0100

"Barry Margolin" <> schrieb im Newsbeitrag">
In article <>,
Alexander Terekhov <> wrote:

Rjack wrote:
> Barry Margolin wrote:
> > In article <>,
> > (Name withheld by request) wrote:
> >
> >> How might one ethically/legally re-write a suite of scripts one > >> wrote
> >> for a former employer, so that the new code may be shared under GPL?
> >
> > IANAL, but I think this is likely to be difficult. You have to > > ensure
> > that your new code looks nothing like the old code.

"One way to avoid infringement when writing a program that is similar to
another program is through the use of a "clean room" procedure. This is
what was done when companies cloned the BIOS of the IBM personal
computer to produce compatible systems. In a clean room procedure, there
are two separate teams working on the development of the new program.

How can you use the clean room procedure when the original programmer is
writing the new program?  There are no teams, there's just one guy.

What? Other GNUtians can't help that one guy? Shame on you, GNUtians.


(GNG is a derecursive recursive derecursion which pwns GNU since it can
be infinitely looped as GNGNGNGNG...NGNGNG... and can be said backwards
too, whereas GNU cannot.)

reply via email to

[Prev in Thread] Current Thread [Next in Thread]