Have you ever made an open source to Github or other source storage online (Bitbucket or Gitlab) ? Say YES…
However, you’re rarely to attend which is the license should be used with your source. So i hope that throughout this tutorial, you will close to get knowledge about it. Firstly, may you want to know Why do you need a license for any software source code? Simplest answer is Copyright. You would’ve holding someone’s source on Github, so you have to follow some rules by owner it. The next question is to make any rule, who will define them out? An organization? Maybe…Or Government plus their ministries managing? Here is a brief content about a software license extracted from Wiki(read more):
A software license is a legal instrument (usually by way of contract law, with or without printed material) governing the use or redistribution of software. Under United States copyright law all software is copyright protected, in source code as also object code form. The only exception is software in the public domain. A typical software license grants the licensee, typically an end-user, permission to use one or more copies of software in ways where such a use would otherwise potentially constitute copyright infringement of the software owner’s exclusive rights under copyright law.
Yup, this time we known that the license be decided by United States copyright law.
Copyright Law of the United States | U.S. Copyright Office
Note: H.R. 5728, the STELA Reauthorization Act of 2014 ( P.L. 113-200) signed into law December 4, 2014, amended title…
Skip all things, only focus to license of software. There are many type of licenses in the real world. Some of those(as the popularly licenses) are:
- GNU AGPLv3
- GNU GPLv3
- Apache License 2.0
- MIT License
Permissions of this strongest copyleft license are conditioned on making available complete source code of licensed works and modifications, which include larger works using a licensed work, under the same license. Copyright and license notices must be preserved. Contributors provide an express grant of patent rights. When a modified version is used to provide a service over a network, the complete source code of the modified version must be made available.
Permissions of this strong copyleft license are conditioned on making available complete source code of licensed works and modifications, which include larger works using a licensed work, under the same license. Copyright and license notices must be preserved. Contributors provide an express grant of patent rights.
A permissive license whose main conditions require preservation of copyright and license notices. Contributors provide an express grant of patent rights. Licensed works, modifications, and larger works may be distributed under different terms and without source code.
A short and simple permissive license with conditions only requiring preservation of copyright and license notices. Licensed works, modifications, and larger works may be distributed under different terms and without source code.
Non-judgmental guidance on choosing a license for your open source project
So, what is the software used to GNU AGPLv3 or GNU GPLv3? What are anything else used to Apache License 2.0 or MIT License?
- Secure project(software), belong to gov or a private organization → prefer to use GNU AGPLv3 or GNU GPLv3.
- Free project(software), scalable, contributing…will be open source near feature → prefer to use Apache License 2.0 or MIT License.
- And if you have never cared about your personal owned on your source → kind to use this http://choosealicense.com/licenses/unlicense/ :]
Btw, if you are an Apple developer, so i suggest you use Apache License 2.0 as Swift language used to use:
How to use above licenses in my software?
Aha, It was easy to use, follow the file i gave you about each license, probably export to txt file or readable file as much as you can. Normally, we still had kept it in .txt file likes Apple, you seen.
A month ago, Vaper for ios was announced open source on Github. And let’s see they were making a license how to?
Beside MIT License, they’re defined a LICENSE file:
Everyone who wants to fork codes from github respo must be obeyed MIT License rules. That’s all. Simple, clear and legal.
I hope you’ve enjoyed this introduction to License. If you have any questions, comments or feedback please leave it below.
P/S: Thanks for the resource gathered in this article, that was in the internet. And super thanks the article’s author.