128:, with "project" (content-work) leadership being a totally informal meritocracy of who is getting the work done sanely, i.e. the most active and intelligent editors, often the effective leaders of wikiprojects, and it operates rather like leadership in hunter-gatherer societies, by suasion and assent based on results, not by post-agricultural-style hierarchy and vested authority. The "human resources department" function of #3A is also distributed, with the whole community deciding who to "hire" as an admin or 'crat, and who to "fire" as an editor (via
205:
of losing the bit and possibly other sanctions). More broadly and more obviously, WP's entire operation is one in which the power to edit could be used to blank or make senseless or misleading any random article on the system, yet this does not actually happen systemically at all (individual abuses are usually detected quickly and dealt with, and done by newly arrived and usually anonymous outsiders, or by
24:
225:, since their primary present function (whether we like to admit it or not) is dispute mediation and disruption lock-down, the only thing out of administrative work types #1, #2, #3A, and #3B that may intrinsically require a higher level of maturity and trust, and thus naturally lend itself to an admin class of type #3B.
231:
The community is never going to unbundle those functions, because they are the ones – the only ones – that actually sometimes require better-than-average, and not just editorial, judgment. WMF has also made it clear that they're never going to get rid of the administrative class, for legal reasons.
204:
thing, out of process and willy-nilly, simply because it's technically possible. This actually makes no sense at all, and WP's present operation proves it doesn't. File-movers, template-editors, and now page-movers do not go around wreaking havoc, but stay within what they're allowed to do (on pain
174:
we're very, very processy. Unbundling in this area is not likely to be successful any time soon, only in areas #1 and #2 (see template-editor, file-mover, page-mover, account-creator, etc.) Where the unbundlings we already have do cross slightly into #3B's "laying down the law" territory at all,
209:). There is no actual reason to believe that unbundled admin abilities, limited by rules regarding their use, would be used inappropriately more than some tiny fraction of 1% of the time. Our community values and enforcement processes will actually ensure that they aren't.
189:
leadership. The impediments are entirely incidental (e.g., cleaning up the CfD backlog requires some presently admin-only powers, simply because they have not yet been delegated like template-editor and page-mover have).
101:– rote functionary and support work that needs to be out of the way of those doing the central work of the organization, or inefficiency results (examples: secretaries, bookkeepers, quartermasters);
95:– fiddly work others are not competent to perform but upon which their ability to work depends, directly or indirectly (examples: systems & network administrators, attorneys, flight-line crew);
196:, are what make the power to move or delete something not particularly dangerous. Because we started with "admin or not admin" with no middle ground, the community suffers under the
185:
because there's no intrinsic reason to not approach these from the same egalitarian "are you going to get it done, correctly?" viewpoint as we treat topical, content-development
232:
Part of being a US-based nonprofit is having some kind of election, and a meaningful process for determining competence for the authority to take actions that affect people.
256:
241:
81:
219:
All of our unbundlings have proven quite effective at reducing backlogs of tedious administrative work, and have raised no consequential problems of any kind.
223:
Making some particular technical- or rote-work function no longer the pointlessly exclusive realm of admins does not magically make admins obsolete
266:
39:
It contains the advice or opinions of one or more
Knowledge (XXG) contributors. This page is not an encyclopedia article, nor is it one of
159:
40:
194:
The principal impediment to further unbundling is the failure to recognize that behavioral constraints, rather than technical limitations
261:
113:
direct labor to the organizational goals (examples: project leaders, HR, division managers, organizational officers), or
175:
there are strict rules regarding their application (and they tend to become tighter over time); this is even true of
119:
manage human foibles (examples: labor dispute adjudicators, and again division managers and organizational officers).
76:
206:
155:
44:
151:
54:
167:
163:
147:
133:
32:
179:, a largely informal variety of unbundling in this area without permission bits being involved.
215:
in form of editors abusing the user-rights, and collapse of adminship as suddenly irrelevant.
88:
In organizational management in the real world, there are three kinds of administrative work:
79:
has become more and more dysfunctional, various abilities that were once admin-only have been
176:
129:
213:
Every single unbundling to date has been opposed by doomsayers predicting disruptive chaos
200:
that the ability to delete or move something at all will always be used to delete or move
137:
250:
229:
The most frequent reason for doomed unbundling proposals is overreach, into area #3B.
85:
from the admin toolset and provided to a broader class of editors in good standing.
47:. Some essays represent widespread norms; others only represent minority viewpoints.
144:
For #3B – "bossing people around" – Knowledge (XXG) is very hierarchical and formal
126:
The
Knowledge (XXG) editorial community itself already forks #3A and #3B sharply
158:, and admins, plus "bodies" like ArbCom, plus a division of "rules" into
140:
have taken and formalized some that distributed community authority).
18:
62:
242:Knowledge (XXG):Unbundling administrators' powers
8:
257:Knowledge (XXG) essays about administration
207:banned bad apples returning as sockpuppets
170:. For better or worse, when it comes to
41:Knowledge (XXG)'s policies or guidelines
150:lawyers and other WMF officers, then
7:
172:being able to tell people what to do
183:Unbundling works well for #1 and #2
45:thoroughly vetted by the community
14:
22:
16:Essay on editing Knowledge (XXG)
107:– top-down decision-making to:
77:Knowledge (XXG) administrators
1:
267:Requests for adminship reform
75:Over time, as the system of
283:
52:
262:Knowledge (XXG) politics
217:It's just not happening.
168:processes and procedures
43:, as it has not been
160:policies, guidelines
177:non-admin closure
73:
72:
274:
65:
26:
25:
19:
282:
281:
277:
276:
275:
273:
272:
271:
247:
246:
238:
105:#3. managerial
93:#1. specialist
69:
68:
61:
57:
49:
48:
23:
17:
12:
11:
5:
280:
278:
270:
269:
264:
259:
249:
248:
245:
244:
237:
234:
203:
199:
173:
123:
122:
121:
120:
114:
102:
96:
71:
70:
67:
66:
58:
53:
50:
38:
37:
29:
27:
15:
13:
10:
9:
6:
4:
3:
2:
279:
268:
265:
263:
260:
258:
255:
254:
252:
243:
240:
239:
235:
233:
230:
226:
224:
220:
218:
214:
210:
208:
201:
197:
195:
191:
188:
184:
180:
178:
171:
169:
165:
161:
157:
153:
149:
145:
141:
139:
135:
131:
127:
118:
115:
112:
109:
108:
106:
103:
100:
99:#2. clerical
97:
94:
91:
90:
89:
86:
84:
83:
78:
64:
63:WP:UNBUNDLING
60:
59:
56:
51:
46:
42:
36:
34:
28:
21:
20:
228:
227:
222:
221:
216:
212:
211:
193:
192:
186:
182:
181:
143:
142:
125:
124:
116:
110:
104:
98:
92:
87:
80:
74:
30:
31:This is an
251:Categories
148:WP:OFFICE
134:WP:ARBCOM
82:unbundled
236:See also
198:illusion
187:de facto
152:stewards
132:(though
55:Shortcut
146:, with
166:, and
164:essays
156:'crats
130:WP:ANI
138:WP:AE
117:#3B.
111:#3A.
33:essay
136:and
202:any
253::
162:,
154:,
35:.
Text is available under the Creative Commons Attribution-ShareAlike License. Additional terms may apply.