Ask Slashdot: Choosing the Right Open Source License

NicknamesAreStupid writes: I need to choose an open source license. I am developing an open source iOS application that use a significant number of other open source projects which, in turn, use a number of different open source licenses such as MPL/GPL, MIT, and BSD. I am also using sample code from Apple's developer site, which has their own terms of use. The code dependencies are such that my code would not be of much use without theirs. If this project is used, then it would be nice to pick a license that best fits in with this mashup. I am interested in maintaining the freedom of my code but do not want to create a catch-22 or make life hard for people who need to use this project for personal use or profit. My inclination is to use MIT's, as I have done so before. I asked an IP lawyer about this matter, and she replied (pro bono), "it probably doesn't matter." Of course, that advice was worth every penny. Moving away from legal issues and looking at this from a social perspective, which license would appeal most and offend least? I thought about no license but was warned (pro bono), "If you do not, then someone else may." Any suggestions?

Comments

Re:No GPL

[caseih]

You've been misinformed. I don't blame you, but you've apparently never read the GPL. It explicitly says:

You are not required to accept this License, since you have not signed it. However, nothing else grants you permission to modify or distribute the Program or its derivative works. These actions are prohibited by law if you do not accept this License. Therefore, by modifying or distributing the Program (or any work based on the Program), you indicate your acceptance of this License to do so, and all its terms and conditions for copying, distributing or modifying the Program or works based on it.

Thus you are free to download and use it for any purpose, provided you do not redistribute it or derive software from it. Pretty clear.

Perhaps you meant to say there's a lot of GPL software you'd like to incorporate into your own software but you can't because of the license. You would be correct. And you won't get any sympathy either. As they say, write your own code!

GPL/BSD

[phantomfive]

If you want your software to be used by as many people/corporations as possible, use BSD.
If you don't want corporations to take advantage of your software without giving back, then use GPL.

BSD expands usage at the cost of community; GPL increases community at the cost of usage. Both approaches are valid.