Welcome to the Treehouse Community
Want to collaborate on code errors? Have bugs you need feedback on? Looking for an extra set of eyes on your latest project? Get support with fellow developers, designers, and programmers of all backgrounds and skill levels here with the Treehouse Community! While you're at it, check out some resources Treehouse students have shared here.
Looking to learn something new?
Treehouse offers a seven day free trial for new students. Get access to thousands of hours of content and join thousands of Treehouse students and alumni in the community today.
Start your free trial
myackley35
34,574 PointsLicences for jQuery Plugins
I'm currently working through the jQuery Plugins badge and I was curious how to approach using plugins and other code with the other licences that you might run into such as GPL, etc. and how dual licensed plugins can be used in projects both personal and non-commercial. I've done a lot of Google-searching and have never really found a clear cut answer and I'm not real big on legalese so I was hoping that someone could clear this up for me.
Thanks!
1 Answer
seth123
Courses Plus Student 226 PointsCould you go into a little bit more detail?
I understood your question as such:
"I am creating a jQuery plugin. Some of the code contained in my plugin is from other plugins. The code snippets from other plugins each have their own licence types. How do I legally use these sections of code from other jQuery plugins within the jQuery plugin that I am coding?"
Answer: It depends on each individual license type and the intended application of your plugin.
Are you selling your plugin or giving it away for free? Is your plugin geared towards commercial use or personal use or both?
Let's say for easy example:
Situation - You are using plugins/code sections that you allowed to use for non-commercial use. You are using these plugins/code to create a non-commercial use plugin.
Solution - In the packaging of your plugin (.rar file or .zip file) include a license.txt file in which you document which code(s) and plugin(s) you used in the creation of your plugin and where the user can locate the original code(s) and/or plugin(s) as well as the license type(s) and restriction(s) or allowed use(s) of those plugin(s) and code(s).
Reason - Not everyone does it this way but I would highly recommend it for a number of reasons. 1) You can revisit your projects at a future date and modify them easily. 2) You're paying dues to those whose work you built on. 3) You're keeping everyone happy. 4) You're providing clear documentation of your lawful usage intent of the created content. 5) Prevents you from being sued or having to deconstruct your creations. 6) You're helping other developers.
You can also include comments within the code structure itself documenting where the code came from and the license used. Really only useful if the user will be able to see the source code - though I would also include it within the source code regardless for the same reasons as above.
Did I understand your question properly?