Fossil SCM
Recast the "Anonymous contribution discouraged" point in fossil-v-git as "No easy drive-by contributions".
Commit
73381119d8283e5b227be5afbef54056a6de973421b2db06299d01391e52aa1e
Parent
4dcbd09feae9c12…
1 file changed
+10
-5
+10
-5
| --- www/fossil-v-git.wiki | ||
| +++ www/fossil-v-git.wiki | ||
| @@ -189,15 +189,20 @@ | ||
| 189 | 189 | directly support the enforcement of a development organization's |
| 190 | 190 | social hierarchy. Fossil is a great fit for |
| 191 | 191 | [https://en.wikipedia.org/wiki/Flat_organization|flat |
| 192 | 192 | organizations].</p></li> |
| 193 | 193 | |
| 194 | - <li><p><b>Anonymous contribution discouraged:</b> Anonymous | |
| 195 | - contribution is possible in a Fossil project, but there is no | |
| 196 | - low-friction path to it, as in Git. Fossil's closest equivalent to | |
| 197 | - Git pull requests is the [/help?cmd=bundle|bundle], which requires | |
| 198 | - higher engagement than firing off a PR.²</p></li> | |
| 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 | + a low-friction path to accepting | |
| 197 | + [https://www.jonobacon.com/2012/07/25/building-strong-community-structural-integrity/|drive-by | |
| 198 | + contributions]. Fossil's closest equivalent is its unique | |
| 199 | + [/help?cmd=bundle|bundle] feature, which requires higher engagement | |
| 200 | + than firing off a PR.² This difference comes directly from the | |
| 201 | + initial designed purpose for each tool: the SQLite project doesn't | |
| 202 | + accept outside contributions from previously-unknown developers, but | |
| 203 | + the Linux kernel does.</p></li> | |
| 199 | 204 | |
| 200 | 205 | <li><p><b>No rebasing:</b> When a remote clone syncs changes up to |
| 201 | 206 | its parent repository, the changes are sent exactly as they were |
| 202 | 207 | committed to the local repository. [#history|There is no rebasing |
| 203 | 208 | mechanism, on purpose.]</p></li> |
| 204 | 209 |
| --- www/fossil-v-git.wiki | |
| +++ www/fossil-v-git.wiki | |
| @@ -189,15 +189,20 @@ | |
| 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>Anonymous contribution discouraged:</b> Anonymous |
| 195 | contribution is possible in a Fossil project, but there is no |
| 196 | low-friction path to it, as in Git. Fossil's closest equivalent to |
| 197 | Git pull requests is the [/help?cmd=bundle|bundle], which requires |
| 198 | higher engagement than firing off a PR.²</p></li> |
| 199 | |
| 200 | <li><p><b>No rebasing:</b> When a remote clone syncs changes up to |
| 201 | its parent repository, the changes are sent exactly as they were |
| 202 | committed to the local repository. [#history|There is no rebasing |
| 203 | mechanism, on purpose.]</p></li> |
| 204 |
| --- www/fossil-v-git.wiki | |
| +++ www/fossil-v-git.wiki | |
| @@ -189,15 +189,20 @@ | |
| 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 | a low-friction path to accepting |
| 197 | [https://www.jonobacon.com/2012/07/25/building-strong-community-structural-integrity/|drive-by |
| 198 | contributions]. Fossil's closest equivalent is its unique |
| 199 | [/help?cmd=bundle|bundle] feature, which requires higher engagement |
| 200 | than firing off a PR.² This difference comes directly from the |
| 201 | initial designed purpose for each tool: the SQLite project doesn't |
| 202 | accept outside contributions from previously-unknown developers, but |
| 203 | the Linux kernel does.</p></li> |
| 204 | |
| 205 | <li><p><b>No rebasing:</b> When a remote clone syncs changes up to |
| 206 | its parent repository, the changes are sent exactly as they were |
| 207 | committed to the local repository. [#history|There is no rebasing |
| 208 | mechanism, on purpose.]</p></li> |
| 209 |