Fossil SCM
More tweaks to the forum.wiki doc
Commit
5d75504af03e0451a7dde0d6d1749b3c748dddc679acf81285222b296b2cb473
Parent
ea67aadeee78ede…
1 file changed
+9
-6
+9
-6
| --- www/forum.wiki | ||
| +++ www/forum.wiki | ||
| @@ -80,11 +80,12 @@ | ||
| 80 | 80 | <h3>Permissions</h3> |
| 81 | 81 | |
| 82 | 82 | Fossil forums use the same role-based access control mechanism as |
| 83 | 83 | for normal Fossil repository logins. |
| 84 | 84 | |
| 85 | -There are several dedicated permsissions for forums: | |
| 85 | +There are several dedicated forum-related capability bits you can grant | |
| 86 | +a user: | |
| 86 | 87 | |
| 87 | 88 | * <b>Read</b>: The user may read forum posts |
| 88 | 89 | * <b>Write</b>: The user may create new forum threads and reply to |
| 89 | 90 | existing threads. New posts are held for moderation. |
| 90 | 91 | * <b>Write Trusted</b>: Same as <b>Write</b>, but posts are inserted |
| @@ -91,11 +92,11 @@ | ||
| 91 | 92 | into the block chain immediately without being held for moderation. |
| 92 | 93 | * <b>Moderate</b>: User gets buttons on posts which allow them to |
| 93 | 94 | either delete or approve posts held for moderation. User also gets |
| 94 | 95 | access to a page (<tt>/modreq</tt>) showing the list of pending |
| 95 | 96 | moderation tasks. |
| 96 | - * <b>Administer</b>: User can grant <b>Write Trusted</b> permission | |
| 97 | + * <b>Administer</b>: User can grant <b>Write Trusted</b> capability | |
| 97 | 98 | to another user, or revoke it. (Currently unimplemented.) |
| 98 | 99 | |
| 99 | 100 | By default, no Fossil user has permission to use the forums except for |
| 100 | 101 | users with Setup and Admin capabilities, which get these as part of the |
| 101 | 102 | large package of other capabilities they get. |
| @@ -111,14 +112,16 @@ | ||
| 111 | 112 | <tt>anonymous</tt> user any forum access, but you may wish to give |
| 112 | 113 | capability "2" to the <tt>reader</tt> user category. |
| 113 | 114 | |
| 114 | 115 | For either type of repository, you are likely to want to give at least |
| 115 | 116 | the Write Trusted (4) capability to the <tt>developer</tt> user |
| 116 | -category. | |
| 117 | +category. If you did not give forum read capability (2) to | |
| 118 | +<tt>anonymous</tt> above, you should give <tt>developer</tt> that | |
| 119 | +capability here, if you choose to give it capability 3 or 4. | |
| 117 | 120 | |
| 118 | 121 | By following this advice, you should not need to tediously add |
| 119 | -capabilities to individual accounts, except in atypical cases, such as | |
| 122 | +capabilities to individual accounts except in atypical cases, such as | |
| 120 | 123 | to grant the Moderate Forum capability (5) to an uncommonly |
| 121 | 124 | highly-trusted user. |
| 122 | 125 | |
| 123 | 126 | |
| 124 | 127 | <h3>Skin Setup</h3> |
| @@ -156,12 +159,12 @@ | ||
| 156 | 159 | two login systems. |
| 157 | 160 | |
| 158 | 161 | You may instead choose to host your forums in a separate Fossil |
| 159 | 162 | repository from your other assets. A good reason to do this is that you |
| 160 | 163 | have a public project where very few of those participating in the forum |
| 161 | -have special permissions for assets managed by Fossil for the project | |
| 162 | -itself, so you wish to segregate the two user sets. | |
| 164 | +have special capability bits for assets managed by Fossil for the | |
| 165 | +project itself, so you wish to segregate the two user sets. | |
| 163 | 166 | |
| 164 | 167 | Fossil offers a way to split the difference: you can host your forum in |
| 165 | 168 | a repository separate from your other Fossil-managed content yet still |
| 166 | 169 | have single sign-on for that common set of users that will have logins |
| 167 | 170 | on both repositories. Simply enable Fossil's login groups feature in |
| 168 | 171 |
| --- www/forum.wiki | |
| +++ www/forum.wiki | |
| @@ -80,11 +80,12 @@ | |
| 80 | <h3>Permissions</h3> |
| 81 | |
| 82 | Fossil forums use the same role-based access control mechanism as |
| 83 | for normal Fossil repository logins. |
| 84 | |
| 85 | There are several dedicated permsissions for forums: |
| 86 | |
| 87 | * <b>Read</b>: The user may read forum posts |
| 88 | * <b>Write</b>: The user may create new forum threads and reply to |
| 89 | existing threads. New posts are held for moderation. |
| 90 | * <b>Write Trusted</b>: Same as <b>Write</b>, but posts are inserted |
| @@ -91,11 +92,11 @@ | |
| 91 | into the block chain immediately without being held for moderation. |
| 92 | * <b>Moderate</b>: User gets buttons on posts which allow them to |
| 93 | either delete or approve posts held for moderation. User also gets |
| 94 | access to a page (<tt>/modreq</tt>) showing the list of pending |
| 95 | moderation tasks. |
| 96 | * <b>Administer</b>: User can grant <b>Write Trusted</b> permission |
| 97 | to another user, or revoke it. (Currently unimplemented.) |
| 98 | |
| 99 | By default, no Fossil user has permission to use the forums except for |
| 100 | users with Setup and Admin capabilities, which get these as part of the |
| 101 | large package of other capabilities they get. |
| @@ -111,14 +112,16 @@ | |
| 111 | <tt>anonymous</tt> user any forum access, but you may wish to give |
| 112 | capability "2" to the <tt>reader</tt> user category. |
| 113 | |
| 114 | For either type of repository, you are likely to want to give at least |
| 115 | the Write Trusted (4) capability to the <tt>developer</tt> user |
| 116 | category. |
| 117 | |
| 118 | By following this advice, you should not need to tediously add |
| 119 | capabilities to individual accounts, except in atypical cases, such as |
| 120 | to grant the Moderate Forum capability (5) to an uncommonly |
| 121 | highly-trusted user. |
| 122 | |
| 123 | |
| 124 | <h3>Skin Setup</h3> |
| @@ -156,12 +159,12 @@ | |
| 156 | two login systems. |
| 157 | |
| 158 | You may instead choose to host your forums in a separate Fossil |
| 159 | repository from your other assets. A good reason to do this is that you |
| 160 | have a public project where very few of those participating in the forum |
| 161 | have special permissions for assets managed by Fossil for the project |
| 162 | itself, so you wish to segregate the two user sets. |
| 163 | |
| 164 | Fossil offers a way to split the difference: you can host your forum in |
| 165 | a repository separate from your other Fossil-managed content yet still |
| 166 | have single sign-on for that common set of users that will have logins |
| 167 | on both repositories. Simply enable Fossil's login groups feature in |
| 168 |
| --- www/forum.wiki | |
| +++ www/forum.wiki | |
| @@ -80,11 +80,12 @@ | |
| 80 | <h3>Permissions</h3> |
| 81 | |
| 82 | Fossil forums use the same role-based access control mechanism as |
| 83 | for normal Fossil repository logins. |
| 84 | |
| 85 | There are several dedicated forum-related capability bits you can grant |
| 86 | a user: |
| 87 | |
| 88 | * <b>Read</b>: The user may read forum posts |
| 89 | * <b>Write</b>: The user may create new forum threads and reply to |
| 90 | existing threads. New posts are held for moderation. |
| 91 | * <b>Write Trusted</b>: Same as <b>Write</b>, but posts are inserted |
| @@ -91,11 +92,11 @@ | |
| 92 | into the block chain immediately without being held for moderation. |
| 93 | * <b>Moderate</b>: User gets buttons on posts which allow them to |
| 94 | either delete or approve posts held for moderation. User also gets |
| 95 | access to a page (<tt>/modreq</tt>) showing the list of pending |
| 96 | moderation tasks. |
| 97 | * <b>Administer</b>: User can grant <b>Write Trusted</b> capability |
| 98 | to another user, or revoke it. (Currently unimplemented.) |
| 99 | |
| 100 | By default, no Fossil user has permission to use the forums except for |
| 101 | users with Setup and Admin capabilities, which get these as part of the |
| 102 | large package of other capabilities they get. |
| @@ -111,14 +112,16 @@ | |
| 112 | <tt>anonymous</tt> user any forum access, but you may wish to give |
| 113 | capability "2" to the <tt>reader</tt> user category. |
| 114 | |
| 115 | For either type of repository, you are likely to want to give at least |
| 116 | the Write Trusted (4) capability to the <tt>developer</tt> user |
| 117 | category. If you did not give forum read capability (2) to |
| 118 | <tt>anonymous</tt> above, you should give <tt>developer</tt> that |
| 119 | capability here, if you choose to give it capability 3 or 4. |
| 120 | |
| 121 | By following this advice, you should not need to tediously add |
| 122 | capabilities to individual accounts except in atypical cases, such as |
| 123 | to grant the Moderate Forum capability (5) to an uncommonly |
| 124 | highly-trusted user. |
| 125 | |
| 126 | |
| 127 | <h3>Skin Setup</h3> |
| @@ -156,12 +159,12 @@ | |
| 159 | two login systems. |
| 160 | |
| 161 | You may instead choose to host your forums in a separate Fossil |
| 162 | repository from your other assets. A good reason to do this is that you |
| 163 | have a public project where very few of those participating in the forum |
| 164 | have special capability bits for assets managed by Fossil for the |
| 165 | project itself, so you wish to segregate the two user sets. |
| 166 | |
| 167 | Fossil offers a way to split the difference: you can host your forum in |
| 168 | a repository separate from your other Fossil-managed content yet still |
| 169 | have single sign-on for that common set of users that will have logins |
| 170 | on both repositories. Simply enable Fossil's login groups feature in |
| 171 |