Choosing a License

License

As you may know, I publish a lot of code for others to use. Often I forget to specify a license for the code - and I get a few comment asking me what license it is under. So I have created a license page for both Bin-Co and OpenJS. I hate restricting use of my code - so I choose the most permissive one around - the BSD License.

I know that many people feel strongly about software license. I still get a lot of flank from my LUG because I prefer using BSD License over their favorite GPL.

GPL was not an option as most of my code are snippets that are meant to be used with other code. GPL will not allow my code to be used within proprietary projects. Another option is LGPL - but I still prefer BSD.

Basically, all scripts, codes and programs from any of my sites are in the BSD License. That means that you can do anything with the scripts - except claim that you wrote it. You can use, copy, sell, modify or whatever you want with it - but you cannot claim authorship.

Importance of Choosing a License

If you are planning to release your code publicly, it is very important that you say what license you are using. If you fail to specify a license, many people will not use your code. It was a big mistake waiting this long before putting up a license on my sites.

If you want help in deciding the license, these links should be of help…

More Links

4 Responses to “Choosing a License”

Abhijit Nadgouda at August 10th, 2007 at 7:37 am

Licenses are the necessary evil. The complications today arise because of incompatibilities between licenses.

Binny V A at August 11th, 2007 at 9:52 pm

Licenses are necessary. It is evil only if it is a proprietary license ;-)

AGPL License » Bin-Blog at November 20th, 2007 at 10:05 pm

[...] license. If they are not lawyers, they will not be able to understand what the license says. I have opted to use the BSD license due to factors like this - BSD license basically gives you the right to do anything with it - [...]

Leave a Reply



Subscribe to Feed