GPL 3 in JavaScript frameworks
Posted: Mon Aug 16, 2010 11:19 am
What kind of restrictions does GPL v3 imply when using a JavaScript framework?
Obviously, using a front end framework would not mean, you have to disclose the backend code that generates the HTML or additional javascript to interact with the framework. Seeing as the JS code you would implement on top of the framework would already be exposed anyway, what exactly are these frameworks hoping to achieve commercially by using a license like GPL v3???
I plan on supporting this framework by buying a license when complete, which allows me to use the framework as I see fit, but still I am curious as to what they can require of you by using OSS software under GPL v3?
Cheers,
Alex
Obviously, using a front end framework would not mean, you have to disclose the backend code that generates the HTML or additional javascript to interact with the framework. Seeing as the JS code you would implement on top of the framework would already be exposed anyway, what exactly are these frameworks hoping to achieve commercially by using a license like GPL v3???
I plan on supporting this framework by buying a license when complete, which allows me to use the framework as I see fit, but still I am curious as to what they can require of you by using OSS software under GPL v3?
Cheers,
Alex