views:

72

answers:

1

My apologies in advance for not doing enough research in this area, but all answers so far I have found have been contradictory and / or too confusing for my current understanding of GPL / AGPL.

If I wish to use an AGPL JavaScript library in a proprietary (not open source) product, am I essentially out of luck? Technically the source of the part of the application that links to the library would be available (it's JavaScript, after all), but somehow this does not seem sufficient, especially given that I will likely be purchasing a license for a separate (unrelated to this question) library available under a dual purpose GPL license, GXT. I'm also using GWT which further muddies the waters somewhat.

I know this is a legal matter, and that ultimately the lawyers will likely make the decision on the matter, but I was hoping to at least gain some indication of the legality of the matter from fellow programmers / lawyers in the know on this subject.

+1  A: 

I think so... You want to look at clause 13, which requires that you make the full source available to users who can access it over the network.

https://secure.wikimedia.org/wikipedia/en/wiki/GNU_General_Public_License

The GNU General Public License v3 cannot be linked with any other license except for GNU AGPLv3 (per section 13).[2]

However, code licensed under several other licenses can be combined with a program under the GPL without conflict, as long as the combination has the GPL applied to the whole.

NinjaCat