tags:

views:

73

answers:

1

I'm setting up a new project and I want to choose a license that is as limiting as possible while still being open source.

  • Apache License 2.0
  • Artistic License/GPL
  • Eclipse Public License 1.0
  • GNU General Public License v2
  • GNU General Public License v3
  • GNU Lesser General Public License
  • MIT License
  • Mozilla Public License 1.1
  • New BSD License
+1  A: 

This really depends on what you mean by 'restrictive.' If you mean, which one make it hardest to use free code in your proprietary application without giving credit to the authors of the code - its the GPL. The opposite of that would be the BSD license. However, I like that license because it makes it harder for people to use my hard work for free without contributing derivative works back to the world. It's free as in 'free speech' - not free beer. So, if you are looking for free beer, stay away from GPL code.

Shane C. Mason
I think what you mean is that the GPL places the highest burden on users of my open source code to provide attribution to me while BSD places the least stringent requirements on those users. If so, it sounds like GPL is what I need. Thanks.
cheese_doodle
Yes, that is exactly what I mean - if you want your code and derivative works to stay free, the GPL is the way to go.
Shane C. Mason