[FONT=Calibri]Linking proprietary code to GPL code, regardless of how it’s done, will likely trigger in the applicable GPL license a requirement to lay open the source code for the combined product (open source part and proprietary part) upon the distribution of the combined product.[/FONT]
[FONT=Calibri]The act of distribution of the combined product is the triggering event.[/FONT]
[FONT=Calibri]See the comments in my blog entry of earlier today: “Best Buy, Samsung, and Others Named in GPL Lawsuit” - http://www.softwareceo.com/forums/blog.php?u=3.[/FONT]
[FONT=Calibri]Chip[/FONT]
[FONT=Arial]Disclaimer: my comments on this forum are for informational purposes only; they do not constitute legal advice, and should not be construed as such.[/FONT]
Categories: Operations and Legal
We have a client that is interested in developing a software product on top of some software that has a GPL license.
They want to release a version of their product that is free and open source (a community edition) plus another version - maybe just add-on modules - that they charge for and which they license commercially.
Is there any way to do that?
They're happy to buy time from a lawyer if you can point me in the direction of someone who has experience in these issues...
December 15, 2009 10:31 AM
RSS
