Fossil SCM
Further tweaks to §2.5.1 of the fossil-v-git doc: spelling and grammar fixes, updated references, clarifications...
Commit
c00b6a4844fb1405fb298a364a6ad5c9a23c11ce5466d73bf13ade610dc1c0de
Parent
e3e06d31f51d6b4…
1 file changed
+10
-9
+10
-9
| --- www/fossil-v-git.wiki | ||
| +++ www/fossil-v-git.wiki | ||
| @@ -403,17 +403,20 @@ | ||
| 403 | 403 | all: it may have an arbitrary number of differences relative to the |
| 404 | 404 | repository it originally cloned from. Git encourages siloed development. |
| 405 | 405 | Select work in a developer's local repository may remain private |
| 406 | 406 | indefinitely. |
| 407 | 407 | |
| 408 | -The Git preference for siloed development has been strongly adopted by Github, | |
| 408 | +The Git preference for siloed development has been strongly adopted by GitHub, | |
| 409 | 409 | who say |
| 410 | 410 | "[https://guides.github.com/activities/forking|Forking is at the core of social coding at GitHub]". |
| 411 | -As a result, as of January 2021, | |
| 412 | -[https://github.com/search?q=is:public|Github hosts 43 million distinct software projects], | |
| 413 | -most of them created as a results of Git/Github forking and very many | |
| 414 | -of them discontinued. | |
| 411 | +As a result, as of September 2021, | |
| 412 | +[https://github.com/search?q=is:public|Github hosts 46 million distinct software projects], | |
| 413 | +most of them created by forking a previously-existing project. Since | |
| 414 | +this is [https://evansdata.com/reports/viewRelease.php?reportID=9 | | |
| 415 | +roughly twice the number of developers in the world], it beggars belief | |
| 416 | +that most of these forks are still under active development. We expect | |
| 417 | +that the vast bulk of these are abandoned one-off efforts. | |
| 415 | 418 | |
| 416 | 419 | All of this is exactly what one wants when doing bazaar-style |
| 417 | 420 | development. |
| 418 | 421 | |
| 419 | 422 | Fossil's normal mode of operation differs on every one of these points, |
| @@ -478,11 +481,11 @@ | ||
| 478 | 481 | Fossil are not purely local labels. They sync along with everything |
| 479 | 482 | else, so everyone sees the same set of branch names. Fossil's design |
| 480 | 483 | choice here is a direct reflection of the Linux vs. SQLite project |
| 481 | 484 | outlook: SQLite's developers collaborate closely on a single |
| 482 | 485 | coherent project, whereas Linux's developers go off on tangents and |
| 483 | - occasionally sync changes up with each other.</p></li> | |
| 486 | + occasionally send selected change sets to each other.</p></li> | |
| 484 | 487 | |
| 485 | 488 | <li><p><b>Private branches are rare:</b> |
| 486 | 489 | [/doc/trunk/www/private.wiki|Private branches exist in Fossil], but |
| 487 | 490 | they're normally used to handle rare exception cases, whereas in |
| 488 | 491 | many Git projects, they're part of the straight-line development |
| @@ -506,13 +509,11 @@ | ||
| 506 | 509 | [https://en.wikipedia.org/wiki/Control_theory | control theory] to |
| 507 | 510 | directly affect the speed at which any system can safely make changes. |
| 508 | 511 | The larger the feedback loop, the slower the whole system must run in |
| 509 | 512 | order to avoid loss of control. The same concept shows up in other |
| 510 | 513 | contexts, such as in the [https://en.wikipedia.org/wiki/OODA_loop | OODA |
| 511 | -loop] concept originally developed to explain the success of the US F-86 | |
| 512 | -Sabre fighter aircraft over the on-paper superior MiG-15, then later | |
| 513 | -applied in other contexts, such as business process management. | |
| 514 | +loop] concept. | |
| 514 | 515 | Committing your changes to private branches in order to delay a public |
| 515 | 516 | push to the parent repo increases the size of your collaborators' |
| 516 | 517 | control loops, either causing them to slow their work in order to safely |
| 517 | 518 | react to your work, or to overcorrect in response to each change. |
| 518 | 519 | |
| 519 | 520 |
| --- www/fossil-v-git.wiki | |
| +++ www/fossil-v-git.wiki | |
| @@ -403,17 +403,20 @@ | |
| 403 | all: it may have an arbitrary number of differences relative to the |
| 404 | repository it originally cloned from. Git encourages siloed development. |
| 405 | Select work in a developer's local repository may remain private |
| 406 | indefinitely. |
| 407 | |
| 408 | The Git preference for siloed development has been strongly adopted by Github, |
| 409 | who say |
| 410 | "[https://guides.github.com/activities/forking|Forking is at the core of social coding at GitHub]". |
| 411 | As a result, as of January 2021, |
| 412 | [https://github.com/search?q=is:public|Github hosts 43 million distinct software projects], |
| 413 | most of them created as a results of Git/Github forking and very many |
| 414 | of them discontinued. |
| 415 | |
| 416 | All of this is exactly what one wants when doing bazaar-style |
| 417 | development. |
| 418 | |
| 419 | Fossil's normal mode of operation differs on every one of these points, |
| @@ -478,11 +481,11 @@ | |
| 478 | Fossil are not purely local labels. They sync along with everything |
| 479 | else, so everyone sees the same set of branch names. Fossil's design |
| 480 | choice here is a direct reflection of the Linux vs. SQLite project |
| 481 | outlook: SQLite's developers collaborate closely on a single |
| 482 | coherent project, whereas Linux's developers go off on tangents and |
| 483 | occasionally sync changes up with each other.</p></li> |
| 484 | |
| 485 | <li><p><b>Private branches are rare:</b> |
| 486 | [/doc/trunk/www/private.wiki|Private branches exist in Fossil], but |
| 487 | they're normally used to handle rare exception cases, whereas in |
| 488 | many Git projects, they're part of the straight-line development |
| @@ -506,13 +509,11 @@ | |
| 506 | [https://en.wikipedia.org/wiki/Control_theory | control theory] to |
| 507 | directly affect the speed at which any system can safely make changes. |
| 508 | The larger the feedback loop, the slower the whole system must run in |
| 509 | order to avoid loss of control. The same concept shows up in other |
| 510 | contexts, such as in the [https://en.wikipedia.org/wiki/OODA_loop | OODA |
| 511 | loop] concept originally developed to explain the success of the US F-86 |
| 512 | Sabre fighter aircraft over the on-paper superior MiG-15, then later |
| 513 | applied in other contexts, such as business process management. |
| 514 | Committing your changes to private branches in order to delay a public |
| 515 | push to the parent repo increases the size of your collaborators' |
| 516 | control loops, either causing them to slow their work in order to safely |
| 517 | react to your work, or to overcorrect in response to each change. |
| 518 | |
| 519 |
| --- www/fossil-v-git.wiki | |
| +++ www/fossil-v-git.wiki | |
| @@ -403,17 +403,20 @@ | |
| 403 | all: it may have an arbitrary number of differences relative to the |
| 404 | repository it originally cloned from. Git encourages siloed development. |
| 405 | Select work in a developer's local repository may remain private |
| 406 | indefinitely. |
| 407 | |
| 408 | The Git preference for siloed development has been strongly adopted by GitHub, |
| 409 | who say |
| 410 | "[https://guides.github.com/activities/forking|Forking is at the core of social coding at GitHub]". |
| 411 | As a result, as of September 2021, |
| 412 | [https://github.com/search?q=is:public|Github hosts 46 million distinct software projects], |
| 413 | most of them created by forking a previously-existing project. Since |
| 414 | this is [https://evansdata.com/reports/viewRelease.php?reportID=9 | |
| 415 | roughly twice the number of developers in the world], it beggars belief |
| 416 | that most of these forks are still under active development. We expect |
| 417 | that the vast bulk of these are abandoned one-off efforts. |
| 418 | |
| 419 | All of this is exactly what one wants when doing bazaar-style |
| 420 | development. |
| 421 | |
| 422 | Fossil's normal mode of operation differs on every one of these points, |
| @@ -478,11 +481,11 @@ | |
| 481 | Fossil are not purely local labels. They sync along with everything |
| 482 | else, so everyone sees the same set of branch names. Fossil's design |
| 483 | choice here is a direct reflection of the Linux vs. SQLite project |
| 484 | outlook: SQLite's developers collaborate closely on a single |
| 485 | coherent project, whereas Linux's developers go off on tangents and |
| 486 | occasionally send selected change sets to each other.</p></li> |
| 487 | |
| 488 | <li><p><b>Private branches are rare:</b> |
| 489 | [/doc/trunk/www/private.wiki|Private branches exist in Fossil], but |
| 490 | they're normally used to handle rare exception cases, whereas in |
| 491 | many Git projects, they're part of the straight-line development |
| @@ -506,13 +509,11 @@ | |
| 509 | [https://en.wikipedia.org/wiki/Control_theory | control theory] to |
| 510 | directly affect the speed at which any system can safely make changes. |
| 511 | The larger the feedback loop, the slower the whole system must run in |
| 512 | order to avoid loss of control. The same concept shows up in other |
| 513 | contexts, such as in the [https://en.wikipedia.org/wiki/OODA_loop | OODA |
| 514 | loop] concept. |
| 515 | Committing your changes to private branches in order to delay a public |
| 516 | push to the parent repo increases the size of your collaborators' |
| 517 | control loops, either causing them to slow their work in order to safely |
| 518 | react to your work, or to overcorrect in response to each change. |
| 519 | |
| 520 |