This site is the archived OWASP Foundation Wiki and is no longer accepting Account Requests.
To view the new OWASP Foundation website, please visit https://owasp.org
Difference between revisions of "Template:Recommended Licenses"
From OWASP
m (Switched list and table to Wiki syntax.) |
|||
| (9 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
| − | + | [http://www.datamation.com/osrc/article.php/12068_3803101_1/Bruce-Perens-How-Many-Open-Source-Licenses-Do-You-Need.htm Why are you recommending these licenses?]<br/> | |
| − | + | [http://opensource.org/licenses/category Which other open source licenses are eligible for an OWASP project?] | |
| − | + | Choosing a license under which an artifact is distributed and enforcing the license are prerogatives of the copyright holders over that artifact. By default, each contributor is copyright holder over the contributed piece. Contributors must all agree on the license and cooperate in enforcing it or must assign their copyright to the entity which becomes responsible for choosing and enforcing the license. | |
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | + | OWASP is a collaborative initiative for the public good and most of its output is expected to be functional, rather than aesthetic. The problem OWASP tackles is so large that OWASP acknowledges a need to collaborate with the commercial world. Therefore, in order to become an OWASP Sponsored Project, you should be comfortable with: | |
| − | + | ||
| − | + | * Allowing arbitrary uses for your work, for example for commercial purposes. (If you disagree, consider using [https://creativecommons.org/licenses/by-nc/4.0/ CC-BY-NC].) | |
| − | </ | + | * Revealing to the world your project's source code (its form preferred for modification). |
| + | * Allowing your work, under certain conditions (see below), to be modified by others and redistributed. (If you disagree, consider using [https://creativecommons.org/licenses/by-nd/4.0/ CC-BY-ND].) | ||
| + | |||
| + | {| class="wikitable" | ||
| + | |+ How to choose a license for artifcts of your OWASP project | ||
| + | |- | ||
| + | ! scope="col" rowspan="2" colspan="2" | Artifact | ||
| + | ! scope="col" colspan="3" | Under what conditions can your work be modified and redistributed? | ||
| + | |- | ||
| + | ! scope="col" | As long as modifications are licensed in the same spirit | ||
| + | ! scope="col" | If credit is appropriately given to you | ||
| + | ! scope="col" | Under any circumstances | ||
| + | |- | ||
| + | ! scope="row" rowspan="2" | Standalone Tool | ||
| + | ! scope="row" | Run locally | ||
| + | |||
| + | | | ||
| + | ; [https://www.gnu.org/licenses/gpl.html GPL] (newest version as of 2016 is 3.0):<br/>The "General Public License" protects users' [https://www.gnu.org/philosophy/free-sw four essential freedoms], among other things by requiring someone who ''distributes'' software derived from yours to also publish the source code for the modifications. Anyone can charge money for distributing copies of the software, but cannot prevent its recipients from redistributing it for free. The GPL allows the copyright holders to distribute the software under additional licenses, too, which can be a way to make it proprietary-friendly. | ||
| + | |||
| + | | rowspan="3" | | ||
| + | ; [https://apache.org/licenses/LICENSE-2.0.html Apache License] (newest version as of 2016 is 2.0):<br/>Has the fewest restrictions, even allowing proprietary modifications and proprietary forks of your project, and is more up-to-date than the BSD license. | ||
| + | |||
| + | | rowspan="4" | | ||
| + | ; [https://creativecommons.org/publicdomain/zero/1.0/ CC0] (newest version as of 2016 is 1.0):<br/>The "Public Domain Dedication" means that anybody can copy, modify, distribute and perform the work, even for commercial purposes, all without asking permission. | ||
| + | |||
| + | |- | ||
| + | ! scope="row" | Consumed over the network | ||
| + | |||
| + | | | ||
| + | ; [https://www.gnu.org/licenses/agpl.html AGPL] (newest version as of 2016 is 3.0):<br/>The "Affero General Public License" extends the GPL to SaaS: users of the modified software must be able to obtain the source code of the modifications. | ||
| + | |||
| + | |- | ||
| + | ! scope="row" colspan="2" | Library | ||
| + | |||
| + | | | ||
| + | ; [https://www.gnu.org/licenses/gpl.html GPL] or [https://www.gnu.org/licenses/lgpl.html LGPL] (newest version as of 2016 is 3.0):<br/>The "Lesser General Public License" relaxes the GPL for libraries: if the library is not modified, just integrated (function calls, global variables,...), with other software, it does not require the source code of the other software to be published. The Free Software Foundation recommends the LGPL only for libraries which have established competitors for the same functionality, otherwise they recommend the full GPL. | ||
| + | |||
| + | |- | ||
| + | ! scope="row" colspan="2" | Document (includes E-Learning, presentations, books etc.) | ||
| + | |||
| + | | | ||
| + | ; [https://creativecommons.org/licenses/by-sa/4.0/ CC-BY-SA] (newest version as of 2016 is 4.0):<br/>The "Creative Commons Attribution-ShareAlike" is like the GPL, but for documents. | ||
| + | |||
| + | | | ||
| + | ; [https://creativecommons.org/licenses/by/4.0/ CC-BY] (newest version as of 2016 is 4.0):<br/>The "Creative Commons Attribution" is like the Apache License, but for documents. | ||
| + | |||
| + | |- | ||
| + | |} | ||
Latest revision as of 16:03, 19 April 2017
Why are you recommending these licenses?
Which other open source licenses are eligible for an OWASP project?
Choosing a license under which an artifact is distributed and enforcing the license are prerogatives of the copyright holders over that artifact. By default, each contributor is copyright holder over the contributed piece. Contributors must all agree on the license and cooperate in enforcing it or must assign their copyright to the entity which becomes responsible for choosing and enforcing the license.
OWASP is a collaborative initiative for the public good and most of its output is expected to be functional, rather than aesthetic. The problem OWASP tackles is so large that OWASP acknowledges a need to collaborate with the commercial world. Therefore, in order to become an OWASP Sponsored Project, you should be comfortable with:
- Allowing arbitrary uses for your work, for example for commercial purposes. (If you disagree, consider using CC-BY-NC.)
- Revealing to the world your project's source code (its form preferred for modification).
- Allowing your work, under certain conditions (see below), to be modified by others and redistributed. (If you disagree, consider using CC-BY-ND.)
| Artifact | Under what conditions can your work be modified and redistributed? | |||
|---|---|---|---|---|
| As long as modifications are licensed in the same spirit | If credit is appropriately given to you | Under any circumstances | ||
| Standalone Tool | Run locally |
|
|
|
| Consumed over the network |
| |||
| Library |
| |||
| Document (includes E-Learning, presentations, books etc.) |
|
| ||
