Barry Margolin wrote:
In article <[email protected]>, Alexander Terekhov
<[email protected]> wrote:
Rjack wrote:
Barry Margolin wrote:
In article <[email protected]>,
[email protected] (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.
http://digital-law-online.info/lpdi1.0/treatise27.html
"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.
The clean room procedure only makes sense if you're
reverse-engineering a program, not if you're using your own
memory and talents.
Cleanroom procedures seem a little awkward when you consider that
most open source code is so public it's used to paper bathroom walls.
_______________________________________________
gnu-misc-discuss mailing list
[email protected]
http://lists.gnu.org/mailman/listinfo/gnu-misc-discuss
