Fossil SCM
Rewrote the "Trust over hierarchy" point in fossil-v-git for clarity.
Commit
d178c782d3b2ed7208389950eb466ee85effa39ac546c5b06663eb6939547799
Parent
b798e89a7eb3e26…
1 file changed
+9
-7
+9
-7
| --- www/fossil-v-git.wiki | ||
| +++ www/fossil-v-git.wiki | ||
| @@ -177,19 +177,21 @@ | ||
| 177 | 177 | |
| 178 | 178 | <ul> |
| 179 | 179 | <li><p><b>Personal engagement:</b> SQLite's developers know each |
| 180 | 180 | other by name and work together daily on the project.</p></li> |
| 181 | 181 | |
| 182 | - <li><p><b>Trust over hierarchy:</b> Fossil supports developers given | |
| 183 | - direct commit capability on the repository rather than support a | |
| 184 | - hierarchical "dictator and lieutenants" contribution style. D. | |
| 182 | + <li><p><b>Trust over hierarchy:</b> SQLite's developers check | |
| 183 | + changes into their local repository, and these are immediately and | |
| 184 | + automatically sync'd up to the central repository; there is no | |
| 185 | + "[https://git-scm.com/book/en/v2/Distributed-Git-Distributed-Workflows#_dictator_and_lieutenants_workflow|dictator | |
| 186 | + and lieutenants]" hierarchy as with Linux kernel contributions. D. | |
| 185 | 187 | Richard Hipp rarely overrides decisions made by those he has trusted |
| 186 | - with commit access on his repositories. | |
| 187 | - [/doc/trunk/www/admin-v-setup.md|Some users] have more power over | |
| 188 | - what they can do with the repository, but Fossil does not otherwise | |
| 188 | + with commit access on his repositories. Fossil allows you to give | |
| 189 | + [/doc/trunk/www/admin-v-setup.md|some users] more power over what | |
| 190 | + they can do with the repository, but Fossil does not otherwise | |
| 189 | 191 | directly support the enforcement of a development organization's |
| 190 | - social hierarchy. Fossil is a great fit for | |
| 192 | + social and power hierarchies. Fossil is a great fit for | |
| 191 | 193 | [https://en.wikipedia.org/wiki/Flat_organization|flat |
| 192 | 194 | organizations].</p></li> |
| 193 | 195 | |
| 194 | 196 | <li><p><b>No easy drive-by contributions:</b> Git |
| 195 | 197 | [https://www.git-scm.com/docs/git-request-pull|pull requests] offer |
| 196 | 198 |
| --- www/fossil-v-git.wiki | |
| +++ www/fossil-v-git.wiki | |
| @@ -177,19 +177,21 @@ | |
| 177 | |
| 178 | <ul> |
| 179 | <li><p><b>Personal engagement:</b> SQLite's developers know each |
| 180 | other by name and work together daily on the project.</p></li> |
| 181 | |
| 182 | <li><p><b>Trust over hierarchy:</b> Fossil supports developers given |
| 183 | direct commit capability on the repository rather than support a |
| 184 | hierarchical "dictator and lieutenants" contribution style. D. |
| 185 | Richard Hipp rarely overrides decisions made by those he has trusted |
| 186 | with commit access on his repositories. |
| 187 | [/doc/trunk/www/admin-v-setup.md|Some users] have more power over |
| 188 | what they can do with the repository, but Fossil does not otherwise |
| 189 | directly support the enforcement of a development organization's |
| 190 | social hierarchy. Fossil is a great fit for |
| 191 | [https://en.wikipedia.org/wiki/Flat_organization|flat |
| 192 | organizations].</p></li> |
| 193 | |
| 194 | <li><p><b>No easy drive-by contributions:</b> Git |
| 195 | [https://www.git-scm.com/docs/git-request-pull|pull requests] offer |
| 196 |
| --- www/fossil-v-git.wiki | |
| +++ www/fossil-v-git.wiki | |
| @@ -177,19 +177,21 @@ | |
| 177 | |
| 178 | <ul> |
| 179 | <li><p><b>Personal engagement:</b> SQLite's developers know each |
| 180 | other by name and work together daily on the project.</p></li> |
| 181 | |
| 182 | <li><p><b>Trust over hierarchy:</b> SQLite's developers check |
| 183 | changes into their local repository, and these are immediately and |
| 184 | automatically sync'd up to the central repository; there is no |
| 185 | "[https://git-scm.com/book/en/v2/Distributed-Git-Distributed-Workflows#_dictator_and_lieutenants_workflow|dictator |
| 186 | and lieutenants]" hierarchy as with Linux kernel contributions. D. |
| 187 | Richard Hipp rarely overrides decisions made by those he has trusted |
| 188 | with commit access on his repositories. Fossil allows you to give |
| 189 | [/doc/trunk/www/admin-v-setup.md|some users] more power over what |
| 190 | they can do with the repository, but Fossil does not otherwise |
| 191 | directly support the enforcement of a development organization's |
| 192 | social and power hierarchies. Fossil is a great fit for |
| 193 | [https://en.wikipedia.org/wiki/Flat_organization|flat |
| 194 | organizations].</p></li> |
| 195 | |
| 196 | <li><p><b>No easy drive-by contributions:</b> Git |
| 197 | [https://www.git-scm.com/docs/git-request-pull|pull requests] offer |
| 198 |