Slashdot Mirror
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?
It's not allowed to distribute GPL software on Apple's App store, because people who license their code under the GPL are dogmatic cunts who would rather fight a battle against the changing tides than see their software gain mainstream acceptance.
But me no buts, neckbeards. GPL is in decline, steadily eroding as they try to make licensing terms even more restrictive with GPL 3.0. BSD, MIT, Apache, and other permissive licenses are a better choice for someone who cares about freedom.