I'm a software engineer, not a lawyer, and my university doesn't offer any courses geared toward licensing software. In fact, their law-related courses are lacking (but slowly growing in number). Where can I go to learn about open-source licenses and how to choose them?
The first question is if your code will be part of a broader open source ecosystem — many open source communities have a few favorite licenses they use. If it will be, consider using the licenses vetted and accepted by your community. If you're on your own, first ask yourself how you want others to use your software.
Yes, it is possible to make an open source project into a closed source project. The copyright holder can change the license of a project at any time, or cease to distribute source code of new releases.
– Cost: Open-source software tends to be free, so it's usually the best choice for individual users. The closed source can cost more, as it has to be designed for the user's needs. – Service: Closed source software is the winner here, as there are usually dedicated service teams that can help you when things go wrong.
Closed source means computer programs whose source code is not published except to licensees. It is available to be edited only by the organization that developed it and those licensed to use the software.
There are lots described here: http://www.gnu.org/licenses/license-list.html#SoftwareLicenses
The decision of which one to use can be political, but should ultimately be determined by your plans/desires for the software. If you want to ensure it is always free then choose GPL or another "Copyleft" license. If you don't mind some commercial use, choose another one that's compatible with that.
I almost always end up usign MIT or BSD (they're equivalent), since it
That, and the GNU/GPL bunch are generally extremists when you encounter them in the wild.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With