There are plenty of open source licenses out there. What should a person especially keep in mind while they're selecting a license for their project?

closed as primarily opinion-based by Zizouz212, user114, michaelpri, Unihedron, Madara Uchiha Jun 23 '15 at 19:43

Many good questions generate some degree of opinion based on expert experience, but answers to this question will tend to be almost entirely based on opinions, rather than facts, references, or specific expertise. If this question can be reworded to fit the rules in the help center, please edit the question.

  • 1
    See gnu.org/licenses/license-recommendations.html and choosealicense.com – user114 Jun 23 '15 at 19:36
  • 1
    This question is too broad, maybe if you are having issues to choose, edit the question to get more useful answers. My answer right now, would be 'It depends on your goals and libraries you plan to link to your project' – E. Celis Jun 23 '15 at 19:38
  • 1
    @Tichodroma I know about this resource, but it is mostly consisted out of recommendations for free software -compliant licenses without actually explaining why should a person use it. – r3bl Jun 23 '15 at 19:39
  • @ecelis It should be more specific now. – r3bl Jun 23 '15 at 19:41

Mainly you want to decide if you license it permissive or not. Other than that, some licenses are matured more and are tested better in courts. Choose a license should be helpful in picking a license.

Basically it recommends MIT if you want a permissive license, Apache if you want to consider software patents and GPL if you want to keep the project open source.

Not the answer you're looking for? Browse other questions tagged or ask your own question.