Template:Recommended Licenses - Revision history

Thomas Herlea: Switched list and table to Wiki syntax.

2017-04-19T16:03:31Z

Switched list and table to Wiki syntax.

Thomas Herlea: Factored out the situations that lead to "Sorry, not good for OWASP", which simplified the decision tree in the table.

2017-04-19T15:38:00Z

Factored out the situations that lead to "Sorry, not good for OWASP", which simplified the decision tree in the table.

Thomas Herlea: Spelled out the license names, expanded explanations.

2017-04-19T13:10:05Z

Spelled out the license names, expanded explanations.

Thomas Herlea: Added links to licenses, updated version number where applicable.

2017-04-19T12:19:34Z

Added links to licenses, updated version number where applicable.

Jmanico at 20:22, 9 December 2012

2012-12-09T20:22:59Z

Jmanico at 20:21, 9 December 2012

2012-12-09T20:21:31Z

Jmanico at 20:20, 9 December 2012

2012-12-09T20:20:03Z

Jmanico at 20:15, 9 December 2012

2012-12-09T20:15:02Z

Jmanico at 20:09, 9 December 2012

2012-12-09T20:09:19Z

Jmanico at 20:03, 9 December 2012

2012-12-09T20:03:52Z

@@ Line 6: / Line 6: @@
 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:
-<p><ul>
+* 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].)
- <li>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].)</li>
+* Revealing to the world your project's source code (its form preferred for modification).
- <li>Revealing to the world your project's source code (its form preferred for modification).</li>
+* 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].)
-<table class="wikitable">
+{| class="wikitable"
-<caption>How to choose a license for artifcts of your OWASP project</caption>
+|+ How to choose a license for artifcts of your OWASP project
-<tr>
+|-
-  <th rowspan="2" colspan="2">Artifact</th>
+! scope="col" rowspan="2" colspan="2" | Artifact
-  <th colspan="3">Under what conditions can your work be modified and redistributed?</th>
+! scope="col"             colspan="3" | Under what conditions can your work be modified and redistributed?
-</tr>
+|-
-<tr>
+! scope="col" | As long as modifications are licensed in the same spirit
-  <th>As long as modifications are licensed in the same spirit</th>
+! scope="col" | If credit is appropriately given to you
-  <th>If credit is appropriately given to you</th>
+! scope="col" | Under any circumstances
-  <th>Under any circumstances</th>
+|-
-</tr>
+! scope="row" rowspan="2" | Standalone Tool
-<tr>
+! scope="row" | Run locally
-  <td rowspan="2">Standalone Tool</td>
-  <td>Run locally</td>
-  <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>
+; [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 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.</td>
-  <td 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.</td>
+| 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.
-<tr>
-  <td>Consumed over the network</td>
+| rowspan="4" |
-  <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/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>
-<tr>
+|-
-  <td colspan="2">Library</td>
+! scope="row" | Consumed over the network
-  <td>[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.</td>
- </tr>
-<tr>
+; [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 colspan="2">Document (includes E-Learning, presentations, books etc.)</td>
-  <td>[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.</td>
+|-
-  <td>[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.</td>
+! scope="row" colspan="2" | Library
-</tr>
-</table>

@@ Line 4: / Line 4: @@
 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.
-<table border="1" cellpadding="3">
+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>
-   <th>Artifact</th>
+   <th rowspan="2" colspan="2">Artifact</th>
-   <td colspan="4"><b>Allow commercial uses of your work?</b></td>
+   <th colspan="3">Under what conditions can your work be modified and redistributed?</th>
 </tr>
 <tr>
-   <td></td>
+   <th>As long as modifications are licensed in the same spirit</th>
-   <td colspan="3"><b>Yes</b></td>
+   <th>If credit is appropriately given to you</th>
-   <td rowspan="3"><b>No</b></td>
+   <th>Under any circumstances</th>
 </tr>
 <tr>
-   <td>&nbsp;</td>
+   <td rowspan="2">Standalone Tool</td>
-   <td colspan=3><b>Allow modifications of your work?</b></td>
+   <td>Run locally</td>
-</tr>
+   <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>
    <td 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.</td>
-   <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>
+   <td 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.</td>
 </tr>
 <tr>
-   <td>Tool Project<br/>(WebBased)</td>
+   <td>Consumed over the network</td>
    <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>
 </tr>
 <tr>
-   <td>Library Project</td>
+   <td colspan="2">Library</td>
    <td>[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.</td>
   </tr>
 <tr>
-   <td>Document Project (includes E-Learning, presentations, books, etc)</td>
+   <td colspan="2">Document (includes E-Learning, presentations, books etc.)</td>
    <td>[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.</td>
 </tr>
 </table>

@@ 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?]
 <table border="1" cellpadding="3">
 <tr>
@@ Line 23: / Line 26: @@
 <tr>
    <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 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.</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>
+   <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>
    <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>
 <tr>
    <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>
+   <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>
 </tr>
 <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>
+   <td>[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.</td>
   </tr>
 <tr>
-   <td>Document Project (includes E-Learning, presos, books, etc)</td>
+   <td>Document Project (includes E-Learning, presentations, books, etc)</td>
-   <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/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.</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>
+   <td>[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.</td>
 </tr>
 </table>

@@ Line 3: / Line 3: @@
 <table border="1" cellpadding="3">
 <tr>
-   <td></td>
+   <th>Artifact</th>
    <td colspan="4"><b>Allow commercial uses of your work?</b></td>
 </tr>
@@ Line 18: / Line 18: @@
    <td></td>
    <td><b>Yes, no restriction except attribution</b></td>
-   <td><b>Yes, as long as modification are also opensource</b></td>
+   <td><b>Yes, as long as modification are also open source</b></td>
    <td><b>No</b></td>
 </tr>
 <tr>
-   <td>ToolProject<br/>(Non-WebBased)</td>
+   <td>Tool Project<br/>(Non-WebBased)</td>
-   <td rowspan="3">Apache 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 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>GPL 3.0<br/>(requires that modifications to your code stay open source, thus prohibiting proprietary forks of your project)</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>
-   <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 http://creativecommons.org/choose] for more information and note that they label these two license as &quot;not a Free Culture License&quot;</td>
+   <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>
 <tr>
    <td>Tool Project<br/>(WebBased)</td>
-   <td>AGPL 3.0<br/>(prevents GPL's SaaS loophole)</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>
 </tr>
 <tr>
    <td>Library Project</td>
-   <td>LGPL 3.0<br/>(similar to GPL but modified for use with libraries that may be called by other proprietary programs)</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>
   </tr>
 <tr>
    <td>Document Project (includes E-Learning, presos, books, etc)</td>
-   <td>CC-BY 3.0<br/>(like Apache but for documents)</td><td>CC-BY-SA 3.0<br/>(like GPL but for documents. Alternately you can use GFDL, but projects like Debian and Ubuntu don't accept it)</td>
+   <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>
 </tr>
 </table>

@@ Line 4: / Line 4: @@
 <tr>
    <td></td>
-   <td colspan="4">Allow commercial uses of your work?</td>
+   <td colspan="4"><b>Allow commercial uses of your work?</b></td>
 </tr>
 <tr>
    <td></td>
-   <td colspan="3">Yes</td>
+   <td colspan="3"><b>Yes</b></td>
-   <td rowspan="3">No</td>
+   <td rowspan="3"><b>No</b></td>
 </tr>
 <tr>
    <td>&nbsp;</td>
-   <td colspan=3>Allow modifications of your work?</td>
+   <td colspan=3><b>Allow modifications of your work?</b></td>
 </tr>
 <tr>
    <td></td>
-   <td>Yes, no restriction except attribution</td>
+   <td><b>Yes, no restriction except attribution</b></td>
-   <td>Yes, as long as modification are also opensource</td>
+   <td><b>Yes, as long as modification are also opensource</b></td>
-   <td>No</td>
+   <td><b>No</b></td>
 </tr>
 <tr>

← Older revision		Revision as of 20:21, 9 December 2012
Line 40:		Line 40:
	</tr>		</tr>
	</table>		</table>
		+	<br/>