I am looking for some advice on the risks involved with the different
types of licenses
e.g. GPL 2/3, LGPL, MIT, BSD
Any expert on the list for a quick consultation?
Thank you,
Rex Chung
CEO and Founder
Ankoder - Video Encoding On Demand
http://www.ankoder.com
--------------------------------------
Sydney: +61 421 591 943
HK: +852 6901 2682
Twitter: @rexchung @ankoder
your point assumes you're creating a compiled application...which is
possibly the minority of software startups nowadays.
This allows for many other shades of grey and other benefits... 8)
On Sun, 2009-10-25 at 11:23 +1100, Silvia Pfeiffer wrote:
> GPL2/3 - basically means that if you use that code in your
> application, you have to open source your application
--
Rob Manson
Managing Director
MOB - start something!
Innovative mobile & online business
http://MOB-labs.com.au
m: +61423215731
e: roB...@MOB-labs.com.au
l: http://www.linkedin.com/in/robertmanson
t: http://twitter.com/nambor
s: http://slideshare.net/robman
-----------------------------------------------------------------------
Create & manage your own Augmented Reality layer with just a few clicks
http://buildAR.com - Extend your reality
-----------------------------------------------------------------------
And your point assumes that the GPLs definition of a "derivative work"
applies only to compiled code.
Frankly, nobody knows what constitutes a derivative work with respect
to the GPL. In the compiled world, you've got the static-vs-dynamic
linking debate. In the non-compiled world, you've got projects like
Drupal / Wordpress imposing same-license restrictions on modules/
plugins/themes, claiming they're derivative works.
1989 called and they want their license back.
Cheers,
Nathan de Vries