I've been trawling through many pages about software licensing and it's a real brain-beater. Legal stuff just isn't interesting, although I do know that I must release my code under a license, otherwise I'd just end up with problems later on down the road.
So I've just finished a rich web-based media manager, and I'm getting around to releasing it. It uses jQuery (including a JSON plugin, and SWFUpload). All code is my own, apart from the JSON plugin and SWFUpload (both released under MIT License, which I believe allows me to use them, I hope).
My code will be open-source. There are a few things that are worrying me.
Really, I just think I'm being over protective of it. All I want to do is release it to the public, but still retain my ownership over it, since I created it.
Any pointers as to where I should go? I've been looking at the GNU GPL, but not entirely sure.
Regards,
Jason.
EDIT:
After researching a lot more, I've settled on either the BSD or MIT License. I've read that the GPL license is a legal timebomb, not sure how true that is.
The BSD and MIT Licenses place little restriction on the end-user, basically: the copyright notice and license must be included in any redistribution of the software.
However, the BSD License does state this:
Neither the name of the nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission.
Any pointers as to which of those would be better?
You're under no obligation to choose a license. However, without a license, the default copyright laws apply, meaning that you retain all rights to your source code and no one may reproduce, distribute, or create derivative works from your work.
Place the licence file for your project in the repository before you do anything else. The default license for code repositories is Apache 2.0.
GNU General Public License (GPL) Its differential characteristics: Strong copyleft. Very strict license. It's usually called a 'viral' license: if you link your code to another piece of code licensed under the GPL and want to distribute the results, the whole product must be GPL-licensed.
Nowadays, the more liberal open source licences are usually the MIT license (here is my question on it) or the GPL. You can use these licenses and still be the copyright holder in both, but you just don't limit the users as much.
Creative Commons has some more restrictive licenses, so check those out. Some of these will allow redistribution of changed work, but only if it links back and adds a "not supported by" notice.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With