38:
492:
The goal here is to not add to admin's work, but to give the moderator that ability to assess consensus, to handle content-related issues, without needing to run to an admin, because the moderator, in these situations, will be as trusted as an admin to perform them. Why? Because the mod went through
484:
And note: to not have the ability to delete and to see deleted, would leave the editor with this user-right package without the ability to perform the majority of the tasks noted at the top: XfD, RM, CSD, editprotected, etc. You can't close an XfD without the deletion tools to implement. That's been
173:
is essentially: "if you don't have the tools to implement a close, you shouldn't be closing the discussion". And also that non-admins shouldn't close "close" or "contentious" discussions. (This latter point is sometimes complained about by some experienced editors – who feel that they should be able
508:(which is what the admin package actually is) is pretty much a dumping ground for most new tools made. And what's left (mostly) deal with the ability of an individual to edit, and assessing an individual's edits, rather than handling content. Besides what I've already noted, I left out editing the
292:
Though of course, anyone doing this while under a cloud may still have this package removed, just as adminship can be removed, though restoration would likely require a community request. (In other words, switching to this package should in no way be considered a way to avoid or bypass anything,
321:
Forcing an editor to carry tools related to assessing editor behaviour, when they may merely want to help out on the content side of things, just seems wrong. Some editors just don't want to carry such tools or to have any of the potential responsibilities that go with it.
331:
may think they can be trusted with all of them, we shouldn't be "forcing" people to accept certain tools which they feel uncomfortable with, and/or clearly do not want, in order to receive tools with which they could clearly help with the encyclopedia project.
512:
namespace (which is broader than just content), and user-rights dealing with offsite things like importing. (I only added the user-right dealing with commons to grant the ability to implement that type of close at FFD, and other image/file-related things.)
394:
Part of the problem with picking a name for this is that for others' purposes elsewhere (bureaucracies/websites/governments/etc.), content and behaviour is usually lumped together. So most terms are going to have been used for both at some place or other.
339:
tool group includes a LOT of tools. And arbitrarily keeping trusted individuals from certain other tools because they refuse to carry "the whole admin package" seems foolish (counter-productive) on our part as a volunteer project.
181:
In broad terms, this means that those with this user-right package should have the ability to: delete/undelete pages (and related abilities); move most pages (and related abilities); deal with files; and edit protected pages.
111:
A new user-right package (aka user group) designed primarily to allow editors the option to help with content-related admin tasks (for which there is often a backlog), if they wish to not have the rest of the sysop package of
177:
So this user-right package would be helpful/useful by allowing the editor the opportunity to retain the tools to implement the close of such discussions, without requiring them to carry all of the tools of adminship.
516:
So with all that in mind, this is designed to be a rather clear definition of what types of work the moderator will do. One thing we don't want is a confusion about what a mod is able to do now (or in the future).
343:
And with that in mind, the tools in this package were not arbitrarily selected, they were particularly chosen due to their interdependent usage for various content-related tasks and responsibilities.
318:) who are happy to help with content, but really don't want anything to do with the block/protect tools, or being expected to deal with behavioural issues. For them, this would be a perfect fit.
202:-related tools. Semi-related to this, no tools which grant user-rights to editors. I also did not include a couple rarely used "mass-action" tools (mass message / mass delete etc.)
216:
is a user-right package which essentially deals with marking certain edits as patrolled/reviewed/viewable. All of these (and other such) tools are handed out by admins through the
224:
have these abilities. Though the editor is of course welcome to request such tools (through the standard processes), with the standard rules and restrictions applicable as normal.
166:
group. User-rights which do not deal with content issues, and in particular user-rights which are related to the assessing of user behaviour are specifically not included.
76:
523:
433:
If anyone has a better name, I'm all ears. But for now, that name seems to be understandable for the primary intent of this group: Someone who can respond to
237:
the adminship-related
Knowledge policies and guidelines, and so would also be subject to all the rules and restrictions which are also expected of adminship.
520:
So this is about as "condensed" a package as we should do. The idea was to make the tools as useful as possible with as small a package as possible.
170:
158:, and other such content-related tasks which would be related to the tools granted in this user-rights package. But which does not include
298:
this all falls under all the various currently-existing policies and processes, and should not be considered any sort of exception to them
489:
and links to a now moved or deleted page, or they may need to adjust a categorisation due to a renamed or a merged category, and so on.
303:
246:
55:
for its implementation was not established within a reasonable period of time. If you want to revive discussion, please use
45:
84:
716:
264:
361:
90:
60:
56:
27:
379:
398:
So, after a lot of thinking and researching names/titles, I'm calling the recipient of this user-right package a
174:
to close such discussions – however, as far as I know, it has been repeatedly upheld in community discussion.)
454:
The tools in this package were specifically selected due to their interdependency in application and usage.
389:
373:
seems unclear, please ask, I'm more than happy to clarify. I look forward to everyone's thoughts on this. –
445:(I did not call it "closer" because many non-admins close discussions, including clerks, CUs, and so on.)
311:
Believe it or not, such a user-right group has actually been requested repeatedly for a very long time.
470:
Besides the deletion tools, there are only a few tools in this package which aren't already given to
346:
We have a tradition on
Knowledge that people contribute at whatever level they are comfortable with.
449:
702:
Note: Indented items are currently available to most users, but may be needed for technical reasons
461:, by my count, there are currently 81 (plus two more to add and remove certain user-rights) in the
458:
406:
277:
And just like adminship, anyone with this user-right package may request its removal. Removal of
155:
384:
355:
114:– For example, to allow for implementing the close of certain content-related discussions like:
360:
Thank you for bearing with this and reading this all. I welcome your thoughts on this proposal
441:
in content-related discussions and has the ability to subsequently implement that consensus.
256:
420:
It's a universally known term online as someone who deals with discussions/text/"substance".
315:
240:
17:
485:
the standard for a long time. Someone may need to edit protected pages in order to adjust
352:
And wouldn't it be great if this helped nudge a few former admins back into activity? : )
227:
To be clear, though this user-right group does not grant the user all of the tools in the
8:
52:
194:: Any tools which directly deal with the assessing of editor behaviour. In particular:
188:– Only those tools which are directly related to the intended usage explained above.
486:
289:
was not "under a cloud", it may be restored by any bureaucrat per the normal rules.
217:
169:
While non-admins do help with some of this, our current policy/guideline regarding
102:
151:
263:(RfM), similar to how adminship is requested there. (Note: Per past requests,
710:
474:, and we shouldn't give those to someone who couldn't view deleted material.
438:
260:
147:
143:
139:
135:
131:
127:
123:
119:
115:
481:, the 22 user-rights below appear to meet the criteria established above.
405:(The technical name of this user-right package (user group) as listed in
537:- Edit pages protected as "Require autoconfirmed or confirmed access"
375:
270:
The editor may also request one or more admin-granted tools (such as
267:- that the granting be similar to how adminship tools are granted.)
437:
implement editorial requests concerning content, and who assesses
426:
It's easily abbreviated to "mod" (compare to administrator/admin)
26:
This page is about the 2016 proposal. For the 2013 proposal, see
75:
590:– View deleted history entries, without their associated text
543:- Edit pages protected as "Require extended confirmed access"
649:– Not create redirects from source pages when moving pages
596:– View deleted text and changes between deleted revisions
504:, but there's a lot more in the admin package than that.
493:
the same trust-assessing process that current admins do.
247:
Knowledge:Administrator § Review and removal of adminship
553:- Edit pages protected as "Require administrator access"
696:– Override files on the shared media repository locally
285:. And so, just like adminship, as long as removal of
429:As far as I know it should translate fairly easily
584:– Delete and undelete specific revisions of pages
265:this has been said to be a requirement by the WMF
231:user-rights package, moderator still falls under
708:
349:This is merely an extension of that tradition.
524:List of user-rights included in the user group
220:process, and there is no need for a closer to
186:What this user group may include in the future
416:Moderator has a couple things going for it:
314:For one thing, there are Wikipedians (like
661:- Override the title or username blacklist
142:/ etc.; various talk page and noticeboard
304:So why would anyone want to request this?
212:are specific separate user-right groups.
192:What this user group should NEVER include
14:
709:
477:So out of 81 user-rights listed for
146:; and so on. In addition, assessing
32:
496:What I didn't add were (of course)
23:
621:– Move pages under pending changes
28:Knowledge:Moderators/Proposal/2013
24:
728:
643:– Move pages with their subpages
74:
36:
281:falls under the same rules as
13:
1:
655:- Merge the history of pages
259:as a result of a successful
7:
385:Moderator user-rights group
10:
733:
717:Knowledge failed proposals
686:– Overwrite existing files
667:- View title blacklist log
559:- Edit protected templates
423:It's a fairly neutral term
244:
25:
367:Again, thank you. And if
380:20:31, 8 July 2016 (UTC)
274:) as part of their RfM.
59:or initiate a thread at
529:Editing protected pages
459:Special:ListGroupRights
407:Special:ListGroupRights
162:the user-rights in the
156:edit-protected requests
627:– Move root user pages
602:– Search deleted pages
362:on the discussion page
293:including sanction.)
261:request for the tools
296:Again, to be clear,
241:Granting and removal
18:Knowledge:Moderators
390:Moderator as a name
625:move-rootuserpages
171:non-admin closures
100:
94:of this proposal.
91:ongoing discussion
704:
665:titleblacklistlog
578:– Undelete a page
541:extendedconfirmed
535:editsemiprotected
446:
308:Several reasons.
99:
98:
69:
68:
67:
724:
700:
647:suppressredirect
564:Handle deletions
444:
78:
71:
70:
61:the village pump
40:
39:
33:
732:
731:
727:
726:
725:
723:
722:
721:
707:
706:
694:reupload-shared
526:
452:
450:Interdependency
411:moderator-admin
392:
387:
358:
306:
249:
243:
105:
64:
37:
31:
22:
21:
20:
12:
11:
5:
730:
720:
719:
698:
697:
690:
689:
688:
687:
681:
680:– Upload files
673:
669:
668:
662:
656:
650:
644:
638:
631:
630:
629:
628:
622:
616:
608:
604:
603:
597:
591:
588:deletedhistory
585:
582:deleterevision
579:
573:
572:– Delete pages
566:
565:
561:
560:
557:templateeditor
554:
547:
546:
545:
544:
538:
530:
525:
522:
451:
448:
431:
430:
427:
424:
421:
391:
388:
386:
383:
357:
354:
305:
302:
242:
239:
104:
101:
97:
96:
85:the straw poll
79:
66:
65:
51:
50:
41:
15:
9:
6:
4:
3:
2:
729:
718:
715:
714:
712:
705:
703:
695:
692:
691:
685:
682:
679:
676:
675:
674:
671:
670:
666:
663:
660:
657:
654:
651:
648:
645:
642:
641:move-subpages
639:
636:
633:
632:
626:
623:
620:
617:
614:
611:
610:
609:
606:
605:
601:
600:browsearchive
598:
595:
592:
589:
586:
583:
580:
577:
574:
571:
568:
567:
563:
562:
558:
555:
552:
551:editprotected
549:
548:
542:
539:
536:
533:
532:
531:
528:
527:
521:
518:
514:
511:
507:
503:
499:
494:
490:
488:
482:
480:
479:administrator
475:
473:
472:autoconfirmed
468:
467:
464:
463:administrator
460:
455:
447:
442:
440:
436:
428:
425:
422:
419:
418:
417:
414:
412:
408:
403:
401:
396:
382:
381:
378:
377:
372:
371:
365:
363:
353:
350:
347:
344:
341:
338:
337:administrator
333:
330:
329:
323:
319:
317:
312:
309:
301:
299:
294:
290:
288:
284:
283:administrator
280:
275:
273:
268:
266:
262:
258:
254:
248:
238:
236:
235:
230:
229:administrator
225:
223:
219:
215:
211:
210:autopatrolled
207:
203:
201:
197:
193:
189:
187:
183:
179:
175:
172:
167:
165:
161:
157:
153:
149:
145:
141:
137:
133:
129:
125:
121:
117:
113:
110:
95:
93:
92:
87:
86:
80:
77:
73:
72:
62:
58:
57:the talk page
54:
49:
47:
42:
35:
34:
29:
19:
701:
699:
693:
683:
677:
672:Handle files
664:
658:
653:mergehistory
652:
646:
640:
637:– Move files
634:
624:
618:
615:– Move pages
612:
607:Handle moves
599:
593:
587:
581:
575:
569:
556:
550:
540:
534:
519:
515:
509:
505:
501:
497:
495:
491:
483:
478:
476:
471:
469:
466:
462:
456:
453:
443:
434:
432:
415:
410:
404:
399:
397:
393:
374:
369:
368:
366:
359:
351:
348:
345:
342:
336:
335:The current
334:
327:
326:
325:Even though
324:
320:
313:
310:
307:
297:
295:
291:
286:
282:
278:
276:
271:
269:
252:
251:Granting of
250:
233:
232:
228:
226:
221:
213:
209:
205:
204:
199:
195:
191:
190:
185:
184:
180:
176:
168:
163:
159:
112:user-rights.
108:
107:
106:
89:
83:
81:
43:
594:deletedtext
465:user group.
257:Bureaucrats
255:is done by
659:tboverride
619:movestable
356:In closing
316:Wikignomes
245:See also:
206:Rollbacker
44:This is a
510:mediawiki
439:consensus
409:would be
400:moderator
287:moderator
279:moderator
253:moderator
218:WP:RFPERM
109:Proposal:
82:See also
53:Consensus
48:proposal.
711:Category
684:reupload
635:movefile
576:undelete
487:hatnotes
370:anything
272:rollback
222:directly
214:Reviewer
103:Proposal
502:protect
196:protect
678:upload
570:delete
506:+sysop
154:, and
150:, and
46:failed
498:block
200:block
164:sysop
16:<
613:move
500:and
457:Per
376:jc37
208:and
152:PROD
144:RfCs
88:and
435:and
413:.)
234:all
198:or
160:all
148:CSD
140:MfD
136:TfD
132:FfD
128:CfD
124:AfD
120:DRV
713::
402:.
364:.
328:we
300:.
138:/
134:/
130:/
126:/
122:;
118:;
116:RM
63:.
30:.
Text is available under the Creative Commons Attribution-ShareAlike License. Additional terms may apply.
