Fossil SCM
Better text justifying the use of a CLA in conjunction with the GPL in the "Fossil vs Git" article.
Commit
838c9efec8bf6e7c98de94ce03e77756db5039eb6d0bc653ec438d1783c4b3fd
Parent
f5321731f9fe253…
1 file changed
+7
-3
+7
-3
| --- www/fossil-v-git.wiki | ||
| +++ www/fossil-v-git.wiki | ||
| @@ -301,14 +301,18 @@ | ||
| 301 | 301 | license agreement] (CLA) because by the very act of distributing |
| 302 | 302 | binaries, you are bound to also distribute the source under a compatible |
| 303 | 303 | license. There are GPL-based projects that do require a CLA, but this is |
| 304 | 304 | typically done in order to allow a corporation to "own" the |
| 305 | 305 | contributions so that it can legally relicense them to those who do not |
| 306 | -wish to be subject to the GPL, usually for a hefty fee. A CLA is not | |
| 307 | -necessary for the legal integrity of a GPL-based | |
| 306 | +wish to be subject to the GPL. The GPL is being used in this case not so | |
| 307 | +much to promote the FOSS philosophy but as a prod to drive companies | |
| 308 | +toward the "commercial version," which is naturally available only for a | |
| 309 | +significant fee. Because a CLA is unnecessary for the legal integrity of | |
| 310 | +a GPL-based | |
| 308 | 311 | [https://en.wikipedia.org/wiki/Free_and_open-source_software|FOSS] |
| 309 | -project, so it's often dispensed with. | |
| 312 | +project, it's often dispensed with when there aren't other | |
| 313 | +considerations pushing the organization to require one. | |
| 310 | 314 | |
| 311 | 315 | Contrast a BSD-style project, where contributions are not automatically |
| 312 | 316 | relicensed merely by being distributed with the preexisting BSD code. |
| 313 | 317 | Such projects often require a CLA even when there is no corporate |
| 314 | 318 | overlord or commercial-use relicensing option. It is one way to ensure |
| 315 | 319 |
| --- www/fossil-v-git.wiki | |
| +++ www/fossil-v-git.wiki | |
| @@ -301,14 +301,18 @@ | |
| 301 | license agreement] (CLA) because by the very act of distributing |
| 302 | binaries, you are bound to also distribute the source under a compatible |
| 303 | license. There are GPL-based projects that do require a CLA, but this is |
| 304 | typically done in order to allow a corporation to "own" the |
| 305 | contributions so that it can legally relicense them to those who do not |
| 306 | wish to be subject to the GPL, usually for a hefty fee. A CLA is not |
| 307 | necessary for the legal integrity of a GPL-based |
| 308 | [https://en.wikipedia.org/wiki/Free_and_open-source_software|FOSS] |
| 309 | project, so it's often dispensed with. |
| 310 | |
| 311 | Contrast a BSD-style project, where contributions are not automatically |
| 312 | relicensed merely by being distributed with the preexisting BSD code. |
| 313 | Such projects often require a CLA even when there is no corporate |
| 314 | overlord or commercial-use relicensing option. It is one way to ensure |
| 315 |
| --- www/fossil-v-git.wiki | |
| +++ www/fossil-v-git.wiki | |
| @@ -301,14 +301,18 @@ | |
| 301 | license agreement] (CLA) because by the very act of distributing |
| 302 | binaries, you are bound to also distribute the source under a compatible |
| 303 | license. There are GPL-based projects that do require a CLA, but this is |
| 304 | typically done in order to allow a corporation to "own" the |
| 305 | contributions so that it can legally relicense them to those who do not |
| 306 | wish to be subject to the GPL. The GPL is being used in this case not so |
| 307 | much to promote the FOSS philosophy but as a prod to drive companies |
| 308 | toward the "commercial version," which is naturally available only for a |
| 309 | significant fee. Because a CLA is unnecessary for the legal integrity of |
| 310 | a GPL-based |
| 311 | [https://en.wikipedia.org/wiki/Free_and_open-source_software|FOSS] |
| 312 | project, it's often dispensed with when there aren't other |
| 313 | considerations pushing the organization to require one. |
| 314 | |
| 315 | Contrast a BSD-style project, where contributions are not automatically |
| 316 | relicensed merely by being distributed with the preexisting BSD code. |
| 317 | Such projects often require a CLA even when there is no corporate |
| 318 | overlord or commercial-use relicensing option. It is one way to ensure |
| 319 |