Fossil SCM

Toned down the "corporate overlord" stuff in the "Fossil vs Git" doc.

wyoung 2019-07-12 14:51 UTC bsd-vs-gpl
Commit 133927979ce166b4b72aaf403e2e6407f360f9d26ce9ae3ea7fbe11bd498d78f
1 file changed +2 -2
--- www/fossil-v-git.wiki
+++ www/fossil-v-git.wiki
@@ -313,12 +313,12 @@
313313
project, it's often dispensed with when there aren't other
314314
considerations pushing the organization to require one.
315315
316316
Contrast a BSD-style project, where contributions are not automatically
317317
relicensed merely by being distributed with the preexisting BSD code.
318
-Such projects often require a CLA even when there is no corporate
319
-overlord or commercial-use relicensing option in order to ensure
318
+Such projects often require a CLA even when there are no corporate
319
+interests, to ensure
320320
that all contributions are compatibly licensed with the existing body of
321321
code. It's a way to add a "no takebacks" clause to the basic BSD
322322
license.
323323
324324
A CLA makes signing up new contributors harder. It's an extra
325325
--- www/fossil-v-git.wiki
+++ www/fossil-v-git.wiki
@@ -313,12 +313,12 @@
313 project, it's often dispensed with when there aren't other
314 considerations pushing the organization to require one.
315
316 Contrast a BSD-style project, where contributions are not automatically
317 relicensed merely by being distributed with the preexisting BSD code.
318 Such projects often require a CLA even when there is no corporate
319 overlord or commercial-use relicensing option in order to ensure
320 that all contributions are compatibly licensed with the existing body of
321 code. It's a way to add a "no takebacks" clause to the basic BSD
322 license.
323
324 A CLA makes signing up new contributors harder. It's an extra
325
--- www/fossil-v-git.wiki
+++ www/fossil-v-git.wiki
@@ -313,12 +313,12 @@
313 project, it's often dispensed with when there aren't other
314 considerations pushing the organization to require one.
315
316 Contrast a BSD-style project, where contributions are not automatically
317 relicensed merely by being distributed with the preexisting BSD code.
318 Such projects often require a CLA even when there are no corporate
319 interests, to ensure
320 that all contributions are compatibly licensed with the existing body of
321 code. It's a way to add a "no takebacks" clause to the basic BSD
322 license.
323
324 A CLA makes signing up new contributors harder. It's an extra
325

Keyboard Shortcuts

Open search /
Next entry (timeline) j
Previous entry (timeline) k
Open focused entry Enter
Show this help ?
Toggle theme Top nav button