Fossil SCM

Clarified the placement of "moderator" and "subscriber" in the power hierarchy expression within www/capabilities.md, since each could float up and down somewhat within the fixed hierarchy we give here. Also fixed a broken URL.

wyoung 2019-08-23 11:49 caps-doc

Commit ba88f4f2a7ba879c834abd49d5a3c07c1aacf84d8d16e0e505a5c5465f04ef72

Parent 832f107ebbb4a82…

1 file changed +17 -2

~ www/capabilities.md

M www/capabilities.md

+17 -2

		--- www/capabilities.md
		+++ www/capabilities.md
		@@ -10,11 +10,11 @@
10	10	case-sensitive: “A” and “a” are different capabilities. We
11	11	explain how we came to assign each character [below](#impl).
12	12
13	13	[an]: https://en.wikipediAsa.org/wiki/Alphanumeric
14	14	[avs]: ./admin-v-setup.md
15		-[rbac]: https://en.wikipedia.org/wiki/Role-based_access_contro
	15	+[rbac]: https://en.wikipedia.org/wiki/Role-based_access_control
16	16	[sync]: /help?cmd=sync
17	17
18	18
19	19	## <a name="cat"></a>User Categories
20	20
		@@ -83,15 +83,30 @@
83	83	defined in user categories, you can assign caps to individual users. For
84	84	the most part, you want to simply read the [reference material
85	85	below](#ref) when doing such work.
86	86
87	87	However, it is useful at this time to expand on the mathematical
88		-expression [above](#cat), which covered only the four user categories.
	88	+expression [above](#cat), which covered only the four fixed user categories.
89	89	If we bring the individual user capabilities into it, the full hierarchy
90	90	of user power in Fossil is:
91	91
92	92	> setup ≥ admin ≥ moderator ≥ developer ≥ reader ≥ subscriber ≥ anonymous ≥ nobody
	93	+
	94	+The two additions at the top are clear: [setup is all-powerful](#apsu),
	95	+and admin users are [subordinate to the setup user(s)](#a).
	96	+
	97	+The moderator insertion could go anywhere from where it’s shown now down
	98	+to above the “anonymous” level, depending on what other caps you give to
	99	+your moderators. Also, there is not just one type of moderator: Fossil
	100	+has [wiki](#l), [ticket](#q), and [forum](#5) moderators, each
	101	+independent of the others. Usually your moderators are fairly
	102	+high-status users, with developer capabilities or higher.
	103	+
	104	+The placement of “subscriber” in that hierarchy is shorthand for the
	105	+sort of subscriber who has registered an account on the repository
	106	+purely to [receive email alerts and announcements](#7). Users higher up
	107	+the hierarchy can also be subscribers.
93	108
94	109
95	110	## <a name="new"></a>New Repository Defaults
96	111
97	112	When you create a new repository, Fossil creates only one user account
98	113

	--- www/capabilities.md
	+++ www/capabilities.md
	@@ -10,11 +10,11 @@
10	case-sensitive: “A” and “a” are different capabilities. We
11	explain how we came to assign each character [below](#impl).
12
13	[an]: https://en.wikipediAsa.org/wiki/Alphanumeric
14	[avs]: ./admin-v-setup.md
15	[rbac]: https://en.wikipedia.org/wiki/Role-based_access_contro
16	[sync]: /help?cmd=sync
17
18
19	## <a name="cat"></a>User Categories
20
	@@ -83,15 +83,30 @@
83	defined in user categories, you can assign caps to individual users. For
84	the most part, you want to simply read the [reference material
85	below](#ref) when doing such work.
86
87	However, it is useful at this time to expand on the mathematical
88	expression [above](#cat), which covered only the four user categories.
89	If we bring the individual user capabilities into it, the full hierarchy
90	of user power in Fossil is:
91
92	> setup ≥ admin ≥ moderator ≥ developer ≥ reader ≥ subscriber ≥ anonymous ≥ nobody















93
94
95	## <a name="new"></a>New Repository Defaults
96
97	When you create a new repository, Fossil creates only one user account
98

	--- www/capabilities.md
	+++ www/capabilities.md
	@@ -10,11 +10,11 @@
10	case-sensitive: “A” and “a” are different capabilities. We
11	explain how we came to assign each character [below](#impl).
12
13	[an]: https://en.wikipediAsa.org/wiki/Alphanumeric
14	[avs]: ./admin-v-setup.md
15	[rbac]: https://en.wikipedia.org/wiki/Role-based_access_control
16	[sync]: /help?cmd=sync
17
18
19	## <a name="cat"></a>User Categories
20
	@@ -83,15 +83,30 @@
83	defined in user categories, you can assign caps to individual users. For
84	the most part, you want to simply read the [reference material
85	below](#ref) when doing such work.
86
87	However, it is useful at this time to expand on the mathematical
88	expression [above](#cat), which covered only the four fixed user categories.
89	If we bring the individual user capabilities into it, the full hierarchy
90	of user power in Fossil is:
91
92	> setup ≥ admin ≥ moderator ≥ developer ≥ reader ≥ subscriber ≥ anonymous ≥ nobody
93
94	The two additions at the top are clear: [setup is all-powerful](#apsu),
95	and admin users are [subordinate to the setup user(s)](#a).
96
97	The moderator insertion could go anywhere from where it’s shown now down
98	to above the “anonymous” level, depending on what other caps you give to
99	your moderators. Also, there is not just one type of moderator: Fossil
100	has [wiki](#l), [ticket](#q), and [forum](#5) moderators, each
101	independent of the others. Usually your moderators are fairly
102	high-status users, with developer capabilities or higher.
103
104	The placement of “subscriber” in that hierarchy is shorthand for the
105	sort of subscriber who has registered an account on the repository
106	purely to [receive email alerts and announcements](#7). Users higher up
107	the hierarchy can also be subscribers.
108
109
110	## <a name="new"></a>New Repository Defaults
111
112	When you create a new repository, Fossil creates only one user account
113

Fossil SCM

Keyboard Shortcuts