Fossil SCM
Linked to the new material showing Fossil's idea of user power hierarchy from the comment in fossil-v-git.wiki about Fossil's support for the organization's social and power hierarchies. It's not that Fossil has *no* support for enforcing this, it's that it's usually a fairly loose match between the two systems. This is an important point, because some people new to Fossil expect 1:1 mapping and get disappointed when we tell them it just doesn't do that.
Commit
b72795a339e262a791dfe804ef4ee2e5078044dd4bdf7a7efe7c6a70ac9e8f4c
Parent
182c4d7abc5d7e9…
1 file changed
+2
-2
+2
-2
| --- www/fossil-v-git.wiki | ||
| +++ www/fossil-v-git.wiki | ||
| @@ -326,12 +326,12 @@ | ||
| 326 | 326 | "[https://git-scm.com/book/en/v2/Distributed-Git-Distributed-Workflows#_dictator_and_lieutenants_workflow|dictator |
| 327 | 327 | and lieutenants]" hierarchy as with Linux kernel contributions. D. |
| 328 | 328 | Richard Hipp rarely overrides decisions made by those he has trusted |
| 329 | 329 | with commit access on his repositories. Fossil allows you to give |
| 330 | 330 | [./caps/admin-v-setup.md|some users] more power over what |
| 331 | - they can do with the repository, but Fossil does not otherwise | |
| 332 | - directly support the enforcement of a development organization's | |
| 331 | + they can do with the repository, but Fossil [./caps/index.md#ucap | | |
| 332 | + only loosely supports] the enforcement of a development organization's | |
| 333 | 333 | social and power hierarchies. Fossil is a great fit for |
| 334 | 334 | [https://en.wikipedia.org/wiki/Flat_organization|flat |
| 335 | 335 | organizations].</p></li> |
| 336 | 336 | |
| 337 | 337 | <li><p><b>No easy drive-by contributions:</b> Git |
| 338 | 338 |
| --- www/fossil-v-git.wiki | |
| +++ www/fossil-v-git.wiki | |
| @@ -326,12 +326,12 @@ | |
| 326 | "[https://git-scm.com/book/en/v2/Distributed-Git-Distributed-Workflows#_dictator_and_lieutenants_workflow|dictator |
| 327 | and lieutenants]" hierarchy as with Linux kernel contributions. D. |
| 328 | Richard Hipp rarely overrides decisions made by those he has trusted |
| 329 | with commit access on his repositories. Fossil allows you to give |
| 330 | [./caps/admin-v-setup.md|some users] more power over what |
| 331 | they can do with the repository, but Fossil does not otherwise |
| 332 | directly support the enforcement of a development organization's |
| 333 | social and power hierarchies. Fossil is a great fit for |
| 334 | [https://en.wikipedia.org/wiki/Flat_organization|flat |
| 335 | organizations].</p></li> |
| 336 | |
| 337 | <li><p><b>No easy drive-by contributions:</b> Git |
| 338 |
| --- www/fossil-v-git.wiki | |
| +++ www/fossil-v-git.wiki | |
| @@ -326,12 +326,12 @@ | |
| 326 | "[https://git-scm.com/book/en/v2/Distributed-Git-Distributed-Workflows#_dictator_and_lieutenants_workflow|dictator |
| 327 | and lieutenants]" hierarchy as with Linux kernel contributions. D. |
| 328 | Richard Hipp rarely overrides decisions made by those he has trusted |
| 329 | with commit access on his repositories. Fossil allows you to give |
| 330 | [./caps/admin-v-setup.md|some users] more power over what |
| 331 | they can do with the repository, but Fossil [./caps/index.md#ucap | |
| 332 | only loosely supports] the enforcement of a development organization's |
| 333 | social and power hierarchies. Fossil is a great fit for |
| 334 | [https://en.wikipedia.org/wiki/Flat_organization|flat |
| 335 | organizations].</p></li> |
| 336 | |
| 337 | <li><p><b>No easy drive-by contributions:</b> Git |
| 338 |