32:
284:) and just asks me what I would do, and to explain myself. If my responses are within the guidelines of the policy, I'll be told so - if I was to ever make a "mistake", my coach would point me to the policy section and get me to re-read it, and then re-answer. My coach hasn't given me any "answers" or "fed me" any policy meanings (if you want, you can look at the
85:
648:
541:
My point though, is not really about the ideals or goals of the project but rather the fact that it is obviously inactive. Rightly or wrongly this process has acquired a bad reputation and it isn't helping anyone, rather it is wasting their time with false hopes that somebody might actually give them
246:
That's an interesting idea (and I mean that!) - but I'm not sure if it's technically feasible on enwiki. It might be possible to have a new wikipedia set up for this (although you'd need the WMF to agree with this, plus community approval for it) - it could be something like admintest.wikipedia.org I
131:
I believe it might be time to tag this as historical. Many administrators don't believe in coaching, and it has been months since any new coachees have been taken. I believe it is time to put this to rest. I am listed here, I know, but after thinking this matter, I think it is hopeless. So I propse:
209:
The proposal I was thinking about, about is was a somewhat complicated one, was to set up an "admin sandbox," but that would need to be checked with developers. By "admin sandbox," I mean to set up a namespace were selected users could use the admin tools freely, without the possibility of damaging
360:
There are many editors who could do with assistance to help them get the most out of Wiki but who may not ever be candidates for admin. I believe there are also admins who would sacrifice a little time to assist so maybe this project would be better renamed to show that editors should come here to
167:
I do not feel that "all interest in it is lost". I know that I started admin coaching as a result of visiting this page. However, if you were to provide some more details about what you would envisage for a "similar project, with a different approach", then I would be happy to comment on that. How
462:
the above conversation ran out of steam two years ago and not one single edit has been made to this talk page in all that time. there has been no actual discussion at the project's main talk page since late 2009, and the only edits to the main project page have been a slo-mo edit war on this very
429:
I think the "Admin coaching" name is fine. Mentoring is more general and coaching is more targeted. THere is a new admin training school, but there could also be a yearly diff of the important policies that admins need to know so that rusty admins can get up to date. Somewhere there is a test
281:
AfD is an important part of
Knowledge's maintenance, and is critical for keeping out non-notable and problematic pages. As an admin, you'll likely end up closing some AfDs here and there. A crucial part of closing discussions properly is being able to correctly evaluate a debate and interpret
288:
page - I don't look at others' coaching pages in case they might have questions which my coach will give me later! You'll see that my coach isn't going into detail about the policies, and isn't "feeding" me anything! I'm assuming that other coaches follow the same kind of pattern. --
171:
Having this here as an active project does no harm, and even if only a few people per year receive admin coaching (although I prefer the term "mentoring" myself), then it's worthwhile being here. If we had a while when no one was either adding themselves to the list, or where the
356:
From this discussion and what
PhantomSteve said to me further up the page I think that there is interest enough in the idea admins helping non admins to better use Knowledge but that many are put off by the notion that it is a fast track approach to becoming an
630:
I don't think this decision needs an RFC, we are just talking about marking an inactive project as historical. If a week or so goes by with no serious objections being raised we can just do that. Staring an alternative program would be a separate discussion.
278:
Oh, and in response to your comment about coachees being "fed" with what policy means, I don't feel that that is how coaching works (which is why I think "Admin mentoring" would be a better name). For example, my coach gives me scenarios (e.g.
494:
there is a strong perception in the community at large and among RFA regulars in particular that Admin coaching is actually a bad thing as it is seen as "teaching to the test," that is, preparing a user for RFA, not for actually being an
282:
consensus. However, as you probably know, not all "votes" should be taken with the same amount of consideration. Here are a few examples of hypothetical posts, and I want you to identify the weaknesses and strengths of each argument
387:. As such, there are venues where either problematic or newish editors can receive the kind of learning you suggest, Weakopedia. If an editor is more established, and wants feedback (and advice on how to improve), there is
430:
wikipedia where it is really easy to become an admin just by asking. But the actual use of admin tools is not that hard. The difficult part is knowing when to use them and how to deal with the humans involved.
324:. In any case, I think we could structure better that proposal above. Another benefit would be that users willing to be admin would get a taste of what being an admin is like, a better way to understand what
502:
So, for all those reasons I would again like to broach the subject of admitting that this project is effectively dead and should be marked as historical so that admin hopefuls don't waste their time here.
53:
48:
219:
As opposed to coaching, the user would be able to exercise and practice his own judgement, rather than being "fed" with what policy means. I'm talking, in essence, about field training.
655:
I think it's clear at this point that here is no interest in keeping the facade up any longer, I've marked the projects pages as historical and removed all requests for coaching.
176:
was not updated, then I'd agree with you - but the latter page has been updated recently (I think 3 coachees have been added in the last 3 months, if I remember correctly). --
394:
The purpose of this project is specifically for those who would like to consider running for adminship sometime. I'd have no issues with these pages being renamed to
143:
To fund a similar project, with a different approach. Mentorship can lead to positive results. A different method may bring new, responsible administrators.
472:
it's unclear when the last time was that this project actually paired a coach with a student, and even less clear when such a student actually passed RFA
99:
Either the page is no longer relevant or consensus on its purpose has become unclear. To revive discussion, seek broader input via a forum such as the
213:
Users with admin access in said namespace would have the opportunity not only to test the tools, but also to learn when, and how to use them.
517:
I think that the problem is not in the idea itself, but the execution of it. You don't major in something to pass a test. You major in it
418:
309:
267:
196:
100:
380:
689:
173:
676:
Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.
17:
338:
234:
168:
would a different project work? How would it attract more interest in this area? What method would you suggest we use?
153:
361:
ask for help in learning how to best use Wiki without them thinking they are on the road to adminhood because of it?
590:
or marking it historical and starting a new project based on teaching interested editors important Wiki policies. --
285:
664:
640:
623:
608:
572:
551:
528:
512:
439:
424:
370:
345:
315:
273:
241:
202:
160:
435:
379:(mainly for editors who have had problems, so they can get help in being a more productive editor - we also have
321:
224:
Of course, such proposal would need to be very well structured. I'm probably just making up castles in the sky.
65:
395:
388:
412:
384:
303:
261:
190:
69:
620:
569:
525:
660:
636:
547:
508:
431:
376:
366:
137:
542:
some admin coaching. That's not a good thing, and marking this thing as historical will fix that.
92:
84:
71:
247:
suppose. As I say, I'm not sure how feasible it would be. Let's see what others think here! --
401:
292:
250:
179:
617:
566:
522:
325:
67:
31:
656:
632:
543:
504:
362:
485:
in the "current requests" list, I'd hate to think what is in the "older requests" lists
210:
or disrupting in any way the encyclopedia. This would prove very useful for 3 reasons:
683:
591:
587:
565:
then. Let's actually start from scratch on this, so we can be more successful.
332:
228:
147:
79:
72:
25:
586:
to pass an RFA. I suggest merger of this project with
616:
I think we'll get more responses if we open an RfC.
120:
Subsequent comments should be made in a new section.
91:
This page is currently inactive and is retained for
582:I agree with Beeblebrox, one should not be trained
216:It would add an extra level of evaluation at RfA.
8:
320:Oh, sorry for that. Guess I haven't read
7:
114:The following discussion is closed.
24:
672:The discussion above is closed.
646:
381:Knowledge:WikiProject User Rehab
140:, as all interest in it is lost.
83:
30:
174:Knowledge:Admin coaching/Status
1:
18:Knowledge talk:Admin coaching
665:19:58, 3 February 2012 (UTC)
641:19:30, 29 January 2012 (UTC)
624:19:14, 29 January 2012 (UTC)
609:09:53, 29 January 2012 (UTC)
573:05:13, 29 January 2012 (UTC)
552:05:12, 29 January 2012 (UTC)
529:05:08, 29 January 2012 (UTC)
513:04:56, 29 January 2012 (UTC)
440:12:18, 20 January 2010 (UTC)
425:12:42, 19 January 2010 (UTC)
371:12:25, 19 January 2010 (UTC)
346:13:07, 19 January 2010 (UTC)
316:13:02, 19 January 2010 (UTC)
274:12:54, 19 January 2010 (UTC)
242:12:50, 19 January 2010 (UTC)
203:12:09, 19 January 2010 (UTC)
161:10:28, 19 January 2010 (UTC)
136:To close this offspring of
706:
375:We already have the essay
286:User:Phantomsteve/Coaching
396:Knowledge:Admin mentoring
674:Please do not modify it.
481:there are requests from
456:Consider the following:
117:Please do not modify it.
389:Knowledge:Editor review
690:Inactive project pages
385:Knowledge:Adopt-a-User
328:and the rest mean...
588:Adopt-a-user program
519:to learn the content
377:Knowledge:Mentorship
322:WP:WHATCOACHINGISNOT
342:
238:
157:
108:
107:
78:
77:
59:
58:
697:
654:
650:
649:
606:
601:
596:
421:
415:
407:
404:
344:
335:
312:
306:
298:
295:
270:
264:
256:
253:
240:
231:
199:
193:
185:
182:
159:
150:
119:
104:
87:
80:
73:
45:
44:
34:
26:
705:
704:
700:
699:
698:
696:
695:
694:
680:
679:
678:
677:
647:
645:
602:
597:
592:
454:
432:Graeme Bartlett
419:
413:
405:
402:
383:) and there is
341:
329:
310:
304:
296:
293:
268:
262:
254:
251:
237:
225:
197:
191:
183:
180:
156:
144:
129:
127:{{historical}}?
124:
115:
98:
74:
68:
39:
22:
21:
20:
12:
11:
5:
703:
701:
693:
692:
682:
681:
671:
670:
669:
668:
667:
627:
626:
611:
576:
575:
559:
558:
557:
556:
555:
554:
534:
533:
532:
531:
499:
498:
497:
496:
489:
488:
487:
486:
476:
475:
474:
473:
467:
466:
465:
464:
453:
450:
449:
448:
447:
446:
445:
444:
443:
442:
392:
358:
354:
353:
352:
351:
350:
349:
348:
336:
318:
232:
222:
221:
220:
217:
214:
169:
164:
163:
151:
141:
128:
125:
123:
122:
110:
109:
106:
105:
97:
88:
76:
75:
70:
66:
64:
61:
60:
57:
56:
51:
41:
40:
35:
29:
23:
15:
14:
13:
10:
9:
6:
4:
3:
2:
702:
691:
688:
687:
685:
675:
666:
662:
658:
653:
644:
643:
642:
638:
634:
629:
628:
625:
622:
619:
615:
612:
610:
607:
605:
600:
595:
589:
585:
581:
578:
577:
574:
571:
568:
564:
561:
560:
553:
549:
545:
540:
539:
538:
537:
536:
535:
530:
527:
524:
520:
516:
515:
514:
510:
506:
501:
500:
493:
492:
491:
490:
484:
480:
479:
478:
477:
471:
470:
469:
468:
461:
460:
459:
458:
457:
451:
441:
437:
433:
428:
427:
426:
422:
416:
410:
409:
408:
397:
393:
390:
386:
382:
378:
374:
373:
372:
368:
364:
359:
355:
347:
343:
340:
334:
327:
323:
319:
317:
313:
307:
301:
300:
299:
287:
283:
277:
276:
275:
271:
265:
259:
258:
257:
245:
244:
243:
239:
236:
230:
223:
218:
215:
212:
211:
208:
207:
206:
205:
204:
200:
194:
188:
187:
186:
175:
170:
166:
165:
162:
158:
155:
149:
142:
139:
135:
134:
133:
126:
121:
118:
112:
111:
102:
96:
94:
89:
86:
82:
81:
63:
62:
55:
52:
50:
47:
46:
43:
42:
38:
33:
28:
27:
19:
673:
651:
613:
603:
598:
593:
583:
579:
562:
518:
482:
455:
400:
399:
330:
291:
290:
280:
249:
248:
226:
178:
177:
145:
138:WP:ESPERANZA
130:
116:
113:
101:village pump
90:
36:
618:Jasper Deng
567:Jasper Deng
523:Jasper Deng
657:Beeblebrox
633:Beeblebrox
544:Beeblebrox
505:Beeblebrox
452:2012 redux
363:Weakopedia
95:reference.
93:historical
339:vandalism
326:WP:TROPHY
235:vandalism
154:vandalism
54:Archive 2
49:Archive 1
684:Category
614:Comment:
420:contribs
311:contribs
269:contribs
198:contribs
37:Archives
580:Support
563:Support
463:subject
403:Phantom
294:Phantom
252:Phantom
181:Phantom
621:(talk)
570:(talk)
526:(talk)
357:admin.
495:admin
406:Steve
398:. --
337:: -->
333:RUL3R
331:: -->
297:Steve
255:Steve
233:: -->
229:RUL3R
227:: -->
184:Steve
152:: -->
148:RUL3R
146:: -->
16:<
661:talk
652:Done
637:talk
584:just
548:talk
509:talk
483:2008
436:talk
414:talk
367:talk
305:talk
263:talk
192:talk
686::
663:)
639:)
550:)
521:.
511:)
438:)
423:\
369:)
314:\
272:\
201:\
659:(
635:(
604:S
599:M
594:S
546:(
507:(
434:(
417:|
411:/
391:.
365:(
308:|
302:/
266:|
260:/
195:|
189:/
103:.
Text is available under the Creative Commons Attribution-ShareAlike License. Additional terms may apply.
