Technology Varanasi • Open Source Contributor and Maintainer at FOSSASIA • iOS / Web Developer • Google Summer of Code (2018) student developer for FOSSASIA • GitHub Campus Expert! • Mentored several Open Source Programs including Google Code-In and mentoring Google Summer of Code 2019 students jogendra jogendrafx https://jogendra.github.io jogendrasingh24
distribute a creative work exclusively to the copyright holder. ➔ It exists to protect the rights of authors, artists, and other creators, allowing them to control if and how their work is used by others. ➔ In most countries, it automatically applies the moment the work is created.
or code), that work is under exclusive copyright by default. That is, the law assumes that as the author of your work, you have a say in what others can do with it. In general, that means nobody else can use, copy, distribute, or modify your work without being at risk of take-downs, shake-downs, or litigation.
popular are - ➔ MIT ➔ GPLv3 ➔ Apache 2.0 ➔ Mozilla Public License 2.0 ➔ BSD 3-Clause "New" or "Revised" license ➔ BSD 2-Clause "Simpliﬁed" or "FreeBSD" license ➔ Common Development and Distribution License ➔ Eclipse Public License version 2.0 ➔ GNU Library or "Lesser" General Public License (LGPL)
preferred by the community you’re contributing to or depending on. Your project will ﬁt right in. ➔ Apache requires Apache License 2.0 ➔ Cloud Native Computing Foundation dictates Apache License 2.0 by default ➔ GNU recommends GNU GPLv3 for most programs ➔ NPM packages overwhelmingly use the MIT or the very similar ISC licenses ➔ OpenBSD prefers the ISC License ➔ Rust crates are overwhelmingly licensed under both MIT and Apache License 2.0 ➔ WordPress plugins and themes must be GNU GPLv2 (or later)
MIT License is short and to the point. It lets people do almost anything they want with your project, including to make and distribute closed source versions. Babel, .NET Core, and Rails use the MIT License.
open licenses used for non-software material ranging from datasets to videos. Note that CC-BY-4.0 and CC-BY-SA-4.0 should not be used for software. Documentation Any open source software license or open license for media (see above) is applicable to software documentation.
but allows them to be freely used in other works. Mixed Projects If your project contains a mix of software and other material, you can include multiple licenses, as long as you are explicit about which license applies to what parts of the project.
Source licenses are copyleft. When an Open Source license is not copyleft, that means software released under that license can be used as part of programs distributed under other licenses, including proprietary (non-open-source) licenses.
it’s binary. Should I call it Open Source? No. Open Source licenses are always applied to the source code. The binaries alone cannot be Open Source, because you're not making any source code available to be open.
Contributor agreements are not open source licenses — rather, they are a way for the contributor to tell the project that it has the right to distribute the new contributions under the project's existing open source license.
One of the organizations below may be able to help: ➔ The Software Freedom Law Center. ➔ The GPL Violations Project. ➔ If the violation includes software that is one of Software Freedom Conservancy's Member Projects, you can contact the Conservancy at <email@example.com> and they will help you help that project enforce the GPL.