Fossil SCM
Tweaks to the "[/doc/trunk/www/whyallinone.md|Why All In One]" document.
Commit
e1361f12decb7a14ea5877884391f070a82472ee7f07ee546712405e95fc79c9
Parent
a204e322668828b…
1 file changed
+7
-1
+7
-1
| --- www/whyallinone.md | ||
| +++ www/whyallinone.md | ||
| @@ -13,11 +13,11 @@ | ||
| 13 | 13 | takes exception to this idea, writing: |
| 14 | 14 | |
| 15 | 15 | > *I don't want forum/web software built into my dvcs.* |
| 16 | 16 | > *I don't see how this improves over git.* |
| 17 | 17 | |
| 18 | -The commenter is, of course, entitled to his opinion. However, here | |
| 18 | +The commenter hold whatever opinions he wants, of course. However, here | |
| 19 | 19 | are a few reasons why bundling other project management software with |
| 20 | 20 | the DVCS might be useful: |
| 21 | 21 | |
| 22 | 22 | 1. There is single software package to install and manage for the |
| 23 | 23 | project website. |
| @@ -46,5 +46,11 @@ | ||
| 46 | 46 | |
| 47 | 47 | 6. Single sign-in for all aspects of the project. The same |
| 48 | 48 | username/password works for code, wiki, forum, tickets, and chat. |
| 49 | 49 | |
| 50 | 50 | 7. Reduce the number of external dependencies for the project. |
| 51 | + | |
| 52 | + 8. Consistent look-and-feel across all aspects of the project, including | |
| 53 | + [project-specific extensions](./serverext.wiki). | |
| 54 | + The [SQLite Release Checklist][8] is a noteworthy example of this. | |
| 55 | + | |
| 56 | +[8]: https://www.sqlite.org/src/ext/checklist/top/index | |
| 51 | 57 |
| --- www/whyallinone.md | |
| +++ www/whyallinone.md | |
| @@ -13,11 +13,11 @@ | |
| 13 | takes exception to this idea, writing: |
| 14 | |
| 15 | > *I don't want forum/web software built into my dvcs.* |
| 16 | > *I don't see how this improves over git.* |
| 17 | |
| 18 | The commenter is, of course, entitled to his opinion. However, here |
| 19 | are a few reasons why bundling other project management software with |
| 20 | the DVCS might be useful: |
| 21 | |
| 22 | 1. There is single software package to install and manage for the |
| 23 | project website. |
| @@ -46,5 +46,11 @@ | |
| 46 | |
| 47 | 6. Single sign-in for all aspects of the project. The same |
| 48 | username/password works for code, wiki, forum, tickets, and chat. |
| 49 | |
| 50 | 7. Reduce the number of external dependencies for the project. |
| 51 |
| --- www/whyallinone.md | |
| +++ www/whyallinone.md | |
| @@ -13,11 +13,11 @@ | |
| 13 | takes exception to this idea, writing: |
| 14 | |
| 15 | > *I don't want forum/web software built into my dvcs.* |
| 16 | > *I don't see how this improves over git.* |
| 17 | |
| 18 | The commenter hold whatever opinions he wants, of course. However, here |
| 19 | are a few reasons why bundling other project management software with |
| 20 | the DVCS might be useful: |
| 21 | |
| 22 | 1. There is single software package to install and manage for the |
| 23 | project website. |
| @@ -46,5 +46,11 @@ | |
| 46 | |
| 47 | 6. Single sign-in for all aspects of the project. The same |
| 48 | username/password works for code, wiki, forum, tickets, and chat. |
| 49 | |
| 50 | 7. Reduce the number of external dependencies for the project. |
| 51 | |
| 52 | 8. Consistent look-and-feel across all aspects of the project, including |
| 53 | [project-specific extensions](./serverext.wiki). |
| 54 | The [SQLite Release Checklist][8] is a noteworthy example of this. |
| 55 | |
| 56 | [8]: https://www.sqlite.org/src/ext/checklist/top/index |
| 57 |