| |||||||||||||
OSBC: Life at the edge of the GPLOSBC: Life at the edge of the GPLPosted Mar 30, 2009 11:11 UTC (Mon) by michaeljt (subscriber, #39183)In reply to: OSBC: Life at the edge of the GPL by jeffnorman Parent article: OSBC: Life at the edge of the GPL
So in other words, if you created your own set of header files and your own stub shared libraries for compiling and linking against, with only the most basic knowledge of the implementation required for this task, that the applications linking against them could still count as derivative works? I suppose that this is perfect for people putting their work under the GPL.
(Log in to post comments)
OSBC: Life at the edge of the GPL Posted Mar 30, 2009 14:56 UTC (Mon) by jeffnorman (guest, #57684) [Link]
in a clean room, the "dirty" team will prep a new API spec that will be limited to the specific functionality required, and reviewed by legal to make sure its all non-copyrightable. The "clean" team will then write a new set of headers and stubs from the new spec. This will provide maximum protection (though never perfect) from a derivative works claim. Cumbersome, no doubt.
|
|||||||||||||