Last modified: 2013-10-06 06:15:14 UTC
Josh Gay has reminded me that jQuery and its extensions are one work when it comes to the GPL's terms. So I figured we'd throw together a bug report to remind us to give it a look. I don't suspect this will be terribly difficult, as probably most or all of our extensions are using GPL'd versions of jQuery.* anyway. But it's something to keep in mind. Ta!
To clarify, JQuery itself is licensed under the MIT license. However, some JQuery extensions are licensed GPLv2. Therefore when you distribute JQuery + JQuery extension, you create a combined work, which should licensed under GPLv2. This does not mean you need to change anything in the JQuery file itself. However, when providing source to the JQuery extension that is licensed under the GPL, you should provide complete and corresponding source code for that program, which means you should provide source code of both JQuery and the JQuery extension(s) and a copy of the license. (You can of course also distribute JQuery seperately as is under the MIT license; so this means you can have some redundency, which might make any automated set-ups you have easier).
Is there any work to do on adding/removing components here? Or can this be resolved by making sure there's adequate labeling on the components that exist? (bug 36866 ? )
I'd recommend before closing this ticket that a comment about this issue be added to but 36866. The point made in this ticket that is non-trivial is that when you have a single minified javascript file that combines a GPL licensed work and a permissively licensed work into a single combined work, then the terms of the GNU GPL has some requirements that you might not comply with if you take some of the approaches discussed in 36866.
