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
Jump to: navigation, search
m (Added links to licenses, updated version number where applicable.)
m (Switched list and table to Wiki syntax.)
 
(2 intermediate revisions by the same user 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://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?]
 
[http://opensource.org/licenses/category Which other open source licenses are eligible for an OWASP project?]
−
<table border="1" cellpadding="3">
+
 
−
<tr>
+
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.
−
  <th>Artifact</th>
+
 
−
  <td colspan="4"><b>Allow commercial uses of your work?</b></td>
+
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:
−
</tr>
+
 
−
<tr>
+
* 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].)
−
  <td></td>
+
* Revealing to the world your project's source code (its form preferred for modification).
−
  <td colspan="3"><b>Yes</b></td>
+
* 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].)
−
  <td rowspan="3"><b>No</b></td>
+
 
−
</tr>
+
{| class="wikitable"
−
<tr>
+
|+ How to choose a license for artifcts of your OWASP project
−
  <td>&nbsp;</td>
+
|-
−
  <td colspan=3><b>Allow modifications of your work?</b></td>
+
! scope="col" rowspan="2" colspan="2" | Artifact
−
</tr>
+
! scope="col"            colspan="3" | Under what conditions can your work be modified and redistributed?
−
<tr>
+
|-
−
  <td></td>
+
! scope="col" | As long as modifications are licensed in the same spirit
−
  <td><b>Yes, no restriction except attribution</b></td>
+
! scope="col" | If credit is appropriately given to you
−
  <td><b>Yes, as long as modification are also open source</b></td>
+
! scope="col" | Under any circumstances
−
  <td><b>No</b></td>
+
|-
−
</tr>
+
! scope="row" rowspan="2" | Standalone Tool
−
<tr>
+
! scope="row" | Run locally
−
  <td>Tool Project<br/>(Non-WebBased)</td>
+
 
−
  <td rowspan="3">[https://apache.org/licenses/LICENSE-2.0.html Apache License] (newest version as of 2016 is 2.0):<br/>(fewest restrictions, even allowing proprietary modifications and proprietary forks of your project, and more up-to-date than BSD license)</td>
+
|
−
  <td>[https://www.gnu.org/licenses/gpl.html GPL] (newest version as of 2016 is 3.0):<br/>(requires that modifications to your code stay open source, thus prohibiting proprietary forks of your project)</td>
+
; [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.
−
  <td colspan="2" rowspan="4">Sorry, such licenses are not opensource and are not eligible to become an OWASP Sponsored Project. If this is really what you want, consider using CC-BY-ND or CC-BY-NC-ND. See http://creativecommons.org/choose for more information and note that they label these two license as &quot;not a Free Culture License&quot;</td>
+
 
−
</tr>
+
| rowspan="3" |
−
<tr>
+
; [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.
−
  <td>Tool Project<br/>(WebBased)</td>
+
 
−
  <td>[https://www.gnu.org/licenses/agpl.html AGPL] (newest version as of 2016 is 3.0):<br/>(prevents GPL's SaaS loophole)</td>
+
| rowspan="4" |
−
</tr>
+
; [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.
−
<tr>
+
 
−
  <td>Library Project</td>
+
|-
−
  <td>[https://www.gnu.org/licenses/lgpl.html LGPL] (newest version as of 2016 is 3.0):<br/>(similar to GPL but modified for use with libraries that may be called by other proprietary programs)</td>
+
! scope="row" | Consumed over the network
−
</tr>
+
 
−
<tr>
+
|
−
  <td>Document Project (includes E-Learning, presos, books, etc)</td>
+
; [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.
−
  <td>[https://creativecommons.org/licenses/by/4.0/ CC-BY] (newest version as of 2016 is 4.0):<br/>(like Apache but for documents)</td>
+
 
−
  <td>[https://creativecommons.org/licenses/by-sa/4.0/ CC-BY-SA] (newest version as of 2016 is 4.0):<br/>(like GPL but for documents. Alternately you can use GFDL, but projects like Debian and Ubuntu don't accept it)</td>
+
|-
−
</tr>
+
! scope="row" colspan="2" | Library
−
</table>
+
 
 +
|
 +
; [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.)
How to choose a license for artifcts of your OWASP project
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
GPL (newest version as of 2016 is 3.0)

The "General Public License" protects users' 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.
Apache License (newest version as of 2016 is 2.0)

Has the fewest restrictions, even allowing proprietary modifications and proprietary forks of your project, and is more up-to-date than the BSD license.
CC0 (newest version as of 2016 is 1.0)

The "Public Domain Dedication" means that anybody can copy, modify, distribute and perform the work, even for commercial purposes, all without asking permission.
Consumed over the network
AGPL (newest version as of 2016 is 3.0)

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.
Library
GPL or LGPL (newest version as of 2016 is 3.0)

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.
Document (includes E-Learning, presentations, books etc.)
CC-BY-SA (newest version as of 2016 is 4.0)

The "Creative Commons Attribution-ShareAlike" is like the GPL, but for documents.
CC-BY (newest version as of 2016 is 4.0)

The "Creative Commons Attribution" is like the Apache License, but for documents.
Retrieved from "https://wiki.owasp.org/index.php?title=Template:Recommended_Licenses&oldid=228845"