Fossil SCM
Clarity pass on the forum capability names in www/forum.wiki to match nomenclature on the Admin -> Users page.
Commit
2490bfba999c5e341ad86f500e033d22f28312e988948fb80320cf744f6e66ea
Parent
89ab99e3805848b…
1 file changed
+23
-17
+23
-17
| --- www/forum.wiki | ||
| +++ www/forum.wiki | ||
| @@ -89,42 +89,48 @@ | ||
| 89 | 89 | for normal Fossil repository logins. |
| 90 | 90 | |
| 91 | 91 | There are several dedicated forum-related capability bits you can grant |
| 92 | 92 | a user: |
| 93 | 93 | |
| 94 | - * <b>Read</b>: The user may read forum posts | |
| 95 | - * <b>Write</b>: The user may create new forum threads and reply to | |
| 96 | - existing threads. New posts are held for moderation. | |
| 97 | - * <b>Write Trusted</b>: Same as <b>Write</b>, but posts are inserted | |
| 98 | - into the block chain immediately without being held for moderation. | |
| 99 | - * <b>Moderate</b>: User gets buttons on posts which allow them to | |
| 100 | - either delete or approve posts held for moderation. User also gets | |
| 94 | + * <b>Read Forum</b>: The user may read forum posts | |
| 95 | + | |
| 96 | + * <b>Write Forum</b>: The user may create new forum threads and reply | |
| 97 | + to existing threads. New posts are held for moderation. | |
| 98 | + | |
| 99 | + * <b>WriteTrusted Forum</b>: Same as <b>Write Forum</b> except that | |
| 100 | + posts are inserted into the block chain immediately without being held | |
| 101 | + for moderation. | |
| 102 | + | |
| 103 | + * <b>Moderate Forum</b>: User gets buttons on posts which allow them | |
| 104 | + to either delete or approve posts held for moderation. User also gets | |
| 101 | 105 | access to a page (<tt>/modreq</tt>) showing the list of pending |
| 102 | 106 | moderation tasks. |
| 103 | - * <b>Administer</b>: User can grant <b>Write Trusted</b> capability | |
| 104 | - to another user, or revoke it. (Currently unimplemented.) | |
| 107 | + | |
| 108 | + * <b>Supervise Forum</b>: User can grant or revoke | |
| 109 | + <b>WriteTrusted</b> capability for other users. (Currently | |
| 110 | + unimplemented.) | |
| 105 | 111 | |
| 106 | 112 | By default, no Fossil user has permission to use the forums except for |
| 107 | 113 | users with Setup and Admin capabilities, which get these as part of the |
| 108 | 114 | large package of other capabilities they get. |
| 109 | 115 | |
| 110 | 116 | For public Fossil repositories that wish to accept new users without |
| 111 | 117 | involving a human, go into Admin → Access and enable the "Allow |
| 112 | -users to register themselves" setting. You may also wish to give the | |
| 113 | -<tt>anonymous</tt> user category the Read Forum (2) and Write Forum (3) | |
| 114 | -capabilities: this allows people to post without creating an account | |
| 118 | +users to register themselves" setting. You may also wish to give users | |
| 119 | +in the <tt>anonymous</tt> category the Read Forum (2) and Write Forum | |
| 120 | +(3) capabilities: this allows people to post without creating an account | |
| 115 | 121 | simply by solving [./antibot.wiki | a simple CAPTCHA]. |
| 116 | 122 | |
| 117 | 123 | For a private repository, you probably won't want to give the |
| 118 | -<tt>anonymous</tt> user any forum access, but you may wish to give | |
| 119 | -capability "2" to the <tt>reader</tt> user category. | |
| 124 | +<tt>anonymous</tt> user any forum access, but you may wish to give the | |
| 125 | +Read Forum capability (2) to users in the <tt>reader</tt> category. | |
| 120 | 126 | |
| 121 | 127 | For either type of repository, you are likely to want to give at least |
| 122 | -the Write Trusted (4) capability to the <tt>developer</tt> user | |
| 123 | -category. If you did not give forum read capability (2) to | |
| 128 | +the WriteTrusted capability (4) to users in the <tt>developer</tt> | |
| 129 | +category. If you did not give the Read Forum capability (2) to | |
| 124 | 130 | <tt>anonymous</tt> above, you should give <tt>developer</tt> that |
| 125 | -capability here, if you choose to give it capability 3 or 4. | |
| 131 | +capability here if you choose to give it capability 3 or 4. | |
| 126 | 132 | |
| 127 | 133 | By following this advice, you should not need to tediously add |
| 128 | 134 | capabilities to individual accounts except in atypical cases, such as |
| 129 | 135 | to grant the Moderate Forum capability (5) to an uncommonly |
| 130 | 136 | highly-trusted user. |
| 131 | 137 |
| --- www/forum.wiki | |
| +++ www/forum.wiki | |
| @@ -89,42 +89,48 @@ | |
| 89 | for normal Fossil repository logins. |
| 90 | |
| 91 | There are several dedicated forum-related capability bits you can grant |
| 92 | a user: |
| 93 | |
| 94 | * <b>Read</b>: The user may read forum posts |
| 95 | * <b>Write</b>: The user may create new forum threads and reply to |
| 96 | existing threads. New posts are held for moderation. |
| 97 | * <b>Write Trusted</b>: Same as <b>Write</b>, but posts are inserted |
| 98 | into the block chain immediately without being held for moderation. |
| 99 | * <b>Moderate</b>: User gets buttons on posts which allow them to |
| 100 | either delete or approve posts held for moderation. User also gets |
| 101 | access to a page (<tt>/modreq</tt>) showing the list of pending |
| 102 | moderation tasks. |
| 103 | * <b>Administer</b>: User can grant <b>Write Trusted</b> capability |
| 104 | to another user, or revoke it. (Currently unimplemented.) |
| 105 | |
| 106 | By default, no Fossil user has permission to use the forums except for |
| 107 | users with Setup and Admin capabilities, which get these as part of the |
| 108 | large package of other capabilities they get. |
| 109 | |
| 110 | For public Fossil repositories that wish to accept new users without |
| 111 | involving a human, go into Admin → Access and enable the "Allow |
| 112 | users to register themselves" setting. You may also wish to give the |
| 113 | <tt>anonymous</tt> user category the Read Forum (2) and Write Forum (3) |
| 114 | capabilities: this allows people to post without creating an account |
| 115 | simply by solving [./antibot.wiki | a simple CAPTCHA]. |
| 116 | |
| 117 | For a private repository, you probably won't want to give the |
| 118 | <tt>anonymous</tt> user any forum access, but you may wish to give |
| 119 | capability "2" to the <tt>reader</tt> user category. |
| 120 | |
| 121 | For either type of repository, you are likely to want to give at least |
| 122 | the Write Trusted (4) capability to the <tt>developer</tt> user |
| 123 | category. If you did not give forum read capability (2) to |
| 124 | <tt>anonymous</tt> above, you should give <tt>developer</tt> that |
| 125 | capability here, if you choose to give it capability 3 or 4. |
| 126 | |
| 127 | By following this advice, you should not need to tediously add |
| 128 | capabilities to individual accounts except in atypical cases, such as |
| 129 | to grant the Moderate Forum capability (5) to an uncommonly |
| 130 | highly-trusted user. |
| 131 |
| --- www/forum.wiki | |
| +++ www/forum.wiki | |
| @@ -89,42 +89,48 @@ | |
| 89 | for normal Fossil repository logins. |
| 90 | |
| 91 | There are several dedicated forum-related capability bits you can grant |
| 92 | a user: |
| 93 | |
| 94 | * <b>Read Forum</b>: The user may read forum posts |
| 95 | |
| 96 | * <b>Write Forum</b>: The user may create new forum threads and reply |
| 97 | to existing threads. New posts are held for moderation. |
| 98 | |
| 99 | * <b>WriteTrusted Forum</b>: Same as <b>Write Forum</b> except that |
| 100 | posts are inserted into the block chain immediately without being held |
| 101 | for moderation. |
| 102 | |
| 103 | * <b>Moderate Forum</b>: User gets buttons on posts which allow them |
| 104 | to either delete or approve posts held for moderation. User also gets |
| 105 | access to a page (<tt>/modreq</tt>) showing the list of pending |
| 106 | moderation tasks. |
| 107 | |
| 108 | * <b>Supervise Forum</b>: User can grant or revoke |
| 109 | <b>WriteTrusted</b> capability for other users. (Currently |
| 110 | unimplemented.) |
| 111 | |
| 112 | By default, no Fossil user has permission to use the forums except for |
| 113 | users with Setup and Admin capabilities, which get these as part of the |
| 114 | large package of other capabilities they get. |
| 115 | |
| 116 | For public Fossil repositories that wish to accept new users without |
| 117 | involving a human, go into Admin → Access and enable the "Allow |
| 118 | users to register themselves" setting. You may also wish to give users |
| 119 | in the <tt>anonymous</tt> category the Read Forum (2) and Write Forum |
| 120 | (3) capabilities: this allows people to post without creating an account |
| 121 | simply by solving [./antibot.wiki | a simple CAPTCHA]. |
| 122 | |
| 123 | For a private repository, you probably won't want to give the |
| 124 | <tt>anonymous</tt> user any forum access, but you may wish to give the |
| 125 | Read Forum capability (2) to users in the <tt>reader</tt> category. |
| 126 | |
| 127 | For either type of repository, you are likely to want to give at least |
| 128 | the WriteTrusted capability (4) to users in the <tt>developer</tt> |
| 129 | category. If you did not give the Read Forum capability (2) to |
| 130 | <tt>anonymous</tt> above, you should give <tt>developer</tt> that |
| 131 | capability here if you choose to give it capability 3 or 4. |
| 132 | |
| 133 | By following this advice, you should not need to tediously add |
| 134 | capabilities to individual accounts except in atypical cases, such as |
| 135 | to grant the Moderate Forum capability (5) to an uncommonly |
| 136 | highly-trusted user. |
| 137 |