Fossil SCM
Moved the GitHub forking stats down in the fossil-v-git doc to a spot where it fits better. Updated the stats, and tightened up the prose.
Commit
c0269e34774f0f27f5e4dd031a2208a315a2fe22ab26aa0fe1bca5f627b9820c
Parent
ab48b9da17238e1…
1 file changed
+11
-11
+11
-11
| --- www/fossil-v-git.wiki | ||
| +++ www/fossil-v-git.wiki | ||
| @@ -403,21 +403,10 @@ | ||
| 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, | |
| 409 | -who say | |
| 410 | -"[https://guides.github.com/activities/forking|Forking is at the core of social coding at GitHub]". | |
| 411 | -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 | 408 | All of this is exactly what one wants when doing bazaar-style |
| 420 | 409 | development. |
| 421 | 410 | |
| 422 | 411 | Fossil's normal mode of operation differs on every one of these points, |
| 423 | 412 | with the specific designed-in goal of promoting SQLite's cathedral |
| @@ -500,10 +489,21 @@ | ||
| 500 | 489 | Fossil places a lot of emphasis on synchronizing everyone's work and on |
| 501 | 490 | reporting on the state of the project and the work of its developers, so |
| 502 | 491 | that everyone — especially the project leader — can maintain a better |
| 503 | 492 | mental picture of what is happening, leading to better situational |
| 504 | 493 | awareness. |
| 494 | + | |
| 495 | +By contrast, "…[https://guides.github.com/activities/forking|forking is | |
| 496 | +at the core of social coding at GitHub]". As of January 2022, | |
| 497 | +[https://github.com/search?q=is:public|Github hosts 47 million distinct | |
| 498 | +software projects], most of which were created by forking a | |
| 499 | +previously-existing project. Since this is | |
| 500 | +[https://evansdata.com/reports/viewRelease.php?reportID=9 | roughly | |
| 501 | +twice the number of developers in the world], it beggars belief that | |
| 502 | +most of these forks are still under active development. The vast bulk | |
| 503 | +of these must be abandoned one-off efforts. This is part of the nature | |
| 504 | +of bazaar style development. | |
| 505 | 505 | |
| 506 | 506 | You can think about this difference in terms of |
| 507 | 507 | [https://en.wikipedia.org/wiki/Feedback | feedback loop size], which we |
| 508 | 508 | know from the mathematics of |
| 509 | 509 | [https://en.wikipedia.org/wiki/Control_theory | control theory] to |
| 510 | 510 |
| --- www/fossil-v-git.wiki | |
| +++ www/fossil-v-git.wiki | |
| @@ -403,21 +403,10 @@ | |
| 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 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, |
| 423 | with the specific designed-in goal of promoting SQLite's cathedral |
| @@ -500,10 +489,21 @@ | |
| 500 | Fossil places a lot of emphasis on synchronizing everyone's work and on |
| 501 | reporting on the state of the project and the work of its developers, so |
| 502 | that everyone — especially the project leader — can maintain a better |
| 503 | mental picture of what is happening, leading to better situational |
| 504 | awareness. |
| 505 | |
| 506 | You can think about this difference in terms of |
| 507 | [https://en.wikipedia.org/wiki/Feedback | feedback loop size], which we |
| 508 | know from the mathematics of |
| 509 | [https://en.wikipedia.org/wiki/Control_theory | control theory] to |
| 510 |
| --- www/fossil-v-git.wiki | |
| +++ www/fossil-v-git.wiki | |
| @@ -403,21 +403,10 @@ | |
| 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 | All of this is exactly what one wants when doing bazaar-style |
| 409 | development. |
| 410 | |
| 411 | Fossil's normal mode of operation differs on every one of these points, |
| 412 | with the specific designed-in goal of promoting SQLite's cathedral |
| @@ -500,10 +489,21 @@ | |
| 489 | Fossil places a lot of emphasis on synchronizing everyone's work and on |
| 490 | reporting on the state of the project and the work of its developers, so |
| 491 | that everyone — especially the project leader — can maintain a better |
| 492 | mental picture of what is happening, leading to better situational |
| 493 | awareness. |
| 494 | |
| 495 | By contrast, "…[https://guides.github.com/activities/forking|forking is |
| 496 | at the core of social coding at GitHub]". As of January 2022, |
| 497 | [https://github.com/search?q=is:public|Github hosts 47 million distinct |
| 498 | software projects], most of which were created by forking a |
| 499 | previously-existing project. Since this is |
| 500 | [https://evansdata.com/reports/viewRelease.php?reportID=9 | roughly |
| 501 | twice the number of developers in the world], it beggars belief that |
| 502 | most of these forks are still under active development. The vast bulk |
| 503 | of these must be abandoned one-off efforts. This is part of the nature |
| 504 | of bazaar style development. |
| 505 | |
| 506 | You can think about this difference in terms of |
| 507 | [https://en.wikipedia.org/wiki/Feedback | feedback loop size], which we |
| 508 | know from the mathematics of |
| 509 | [https://en.wikipedia.org/wiki/Control_theory | control theory] to |
| 510 |