Fossil
Check-in [eebd7135]
Not logged in

Many hyperlinks are disabled.
Use anonymous login to enable hyperlinks.

Overview
Comment:Prose polishing in the "License" section of fossil-v-git
Downloads: Tarball | ZIP archive | SQL archive
Timelines: family | ancestors | descendants | both | bsd-vs-gpl
Files: files | file ages | folders
SHA3-256: eebd7135117f4b3f3c711653abe545b9508c2796a288b7d2e2f13a8254b58682
User & Date: wyoung 2019-07-14 11:28:52
Context
2019-07-14
11:37
Another bit of prose polishing in fossil-v-git check-in: fcdefd97 user: wyoung tags: bsd-vs-gpl
11:28
Prose polishing in the "License" section of fossil-v-git check-in: eebd7135 user: wyoung tags: bsd-vs-gpl
11:02
Moved the "BSD vs GPL" section up in the fossil-v-git doc and made it a sub-section of a new "Linux vs SQLite" section which has two other sub-sections: "Development Organization," which contains an expanded version of what used to be called "Cathedral vs. Bazaar" and "Scale," which contains what is left of the prior version's "Linux vs. SQLite" section. These are sub-sections of a common parent because they were mutually repetitive, and they're all aspects of the "Linux vs. SQLite" comparison, not separate things at all. check-in: bab2656d user: wyoung tags: bsd-vs-gpl
Changes
Hide Diffs Unified Diffs Ignore Whitespace Patch

Changes to www/fossil-v-git.wiki.

301
302
303
304
305
306
307
308
309
310

311
312
313
314
315
316
317
318
[https://github.com/git/git/blob/master/Documentation/SubmittingPatches#L306|an
implicit CLA], but contributors agree to both passively.
[http://fossil-scm.org/home/doc/trunk/www/contribute.wiki|The Fossil
project's contribution process] requires active steps and processing
time: the printing, signing, mailing, reception, and processing of the
CLA.

We think this additional friction has an upside: it improves contributor
community cohesion, because everyone who pushed past that legal friction
made an affirmative, active step to get into the community. We think it

makes for a better, more carefully-designed, simpler DVCS.


<h3 id="branches">2.4 Individual Branches vs. The Entire Change History</h3>

Both Fossil and Git store history as a directed acyclic graph (DAG)
of changes, but Git tends to focus more on individual branches of
the DAG, whereas Fossil puts more emphasis on the entire DAG.







|
|
|
>
|







301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
[https://github.com/git/git/blob/master/Documentation/SubmittingPatches#L306|an
implicit CLA], but contributors agree to both passively.
[http://fossil-scm.org/home/doc/trunk/www/contribute.wiki|The Fossil
project's contribution process] requires active steps and processing
time: the printing, signing, mailing, reception, and processing of the
CLA.

We think there's an upside to this difference, in Fossil's favor: it
improves contributor community cohesion, because everyone who pushed
past that legal friction made an affirmative, active step to get commit
capability on the Fossil project repository. We think it makes for a
better, more carefully-designed, simpler DVCS.


<h3 id="branches">2.4 Individual Branches vs. The Entire Change History</h3>

Both Fossil and Git store history as a directed acyclic graph (DAG)
of changes, but Git tends to focus more on individual branches of
the DAG, whereas Fossil puts more emphasis on the entire DAG.