Reputation
357
Top tag
Next privilege 500 Rep.
Access review queues
Badges
1 8
Impact
~6k people reached

  • 0 posts edited
  • 0 helpful flags
  • 42 votes cast
Mar
28
comment How is client-side javascript covered by the GPL?
@Alison, ah OK, sorry, I mis-understood the full question then. No, the server side would not have to be GPLed. As long as the comms between the client and server are some format unlike a machine level functional invocation, like XML, you have nothing to worry about. Simply serving GPL code, be it HTML or JS, doesn't make the server-side code delivering it, or communicating with it in a non-remote invocation format, a derivative work.
Mar
28
comment How is client-side javascript covered by the GPL?
@Scott Whitlock , the GPL clearly does not force you to release the server side code, I have to disagree there is any uncertainty there. Only the AGPL could enforce that. Overall, the FSF does answer GPL questions like these, it might be worth asking them if someone is relying on the answer to this.
Mar
28
comment How is client-side javascript covered by the GPL?
@Alison Unaltered. You could reasonably say you have fulfilled your requirement if the JavaScript is available by typing the URL to the JavaScript into a browser you see the unaltered JavaScript source. It would be safer to make it available as a download, though, for completeness.
Mar
28
comment How is client-side javascript covered by the GPL?
@objectiveME , it does not count unless the JS is unaltered. Both the GPL v2 and v3 have reasonably specific text about this. v3 is slightly clearer and has less room for misunderstandings.
Mar
28
comment How is client-side javascript covered by the GPL?
It has to be unaltered, both in GPL V2 and V3. OK, that may not be the same thing, I'm assuming human writable == human readable.