Fossil SCM
Clarity tweak to the "why CLA + BSD" justification in the "Fossil vs Git" doc.
Commit
633830fe17d64b0f754b893faa3dc7d205a97c1880e31511b761c1db31fb2e6e
Parent
838c9efec8bf6e7…
1 file changed
+1
-1
+1
-1
| --- www/fossil-v-git.wiki | ||
| +++ www/fossil-v-git.wiki | ||
| @@ -313,11 +313,11 @@ | ||
| 313 | 313 | considerations pushing the organization to require one. |
| 314 | 314 | |
| 315 | 315 | Contrast a BSD-style project, where contributions are not automatically |
| 316 | 316 | relicensed merely by being distributed with the preexisting BSD code. |
| 317 | 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 | |
| 318 | +overlord or commercial-use relicensing option in order to ensure | |
| 319 | 319 | that all contributions are compatibly licensed with the existing body of |
| 320 | 320 | code. It's a way to add a "no takebacks" clause to the basic BSD |
| 321 | 321 | license. The greater necesity for having a CLA in a BSD-licensed project |
| 322 | 322 | makes signing up new contributors harder. |
| 323 | 323 | |
| 324 | 324 |
| --- www/fossil-v-git.wiki | |
| +++ www/fossil-v-git.wiki | |
| @@ -313,11 +313,11 @@ | |
| 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 | that all contributions are compatibly licensed with the existing body of |
| 320 | code. It's a way to add a "no takebacks" clause to the basic BSD |
| 321 | license. The greater necesity for having a CLA in a BSD-licensed project |
| 322 | makes signing up new contributors harder. |
| 323 | |
| 324 |
| --- www/fossil-v-git.wiki | |
| +++ www/fossil-v-git.wiki | |
| @@ -313,11 +313,11 @@ | |
| 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 in order to ensure |
| 319 | that all contributions are compatibly licensed with the existing body of |
| 320 | code. It's a way to add a "no takebacks" clause to the basic BSD |
| 321 | license. The greater necesity for having a CLA in a BSD-licensed project |
| 322 | makes signing up new contributors harder. |
| 323 | |
| 324 |