595:
some people from adminship. Turning down good candidates is a bad idea, and any proposal to change the system to exclude a group of candidates who currently get consensus support is logically doomed to fail. Remember that while there is an argument that you don't want so many active crats that a crat chat becomes dysfunctional, there is no equivalent way in which one could ever have too many admins. 1500 and 2000 are both figures that I and others have proposed before and got majority support though not consensus, they are of course only partial solutions to the problem - but partial solutions can be useful incremental improvements. I'm pretty sure that only one candidate has got through in the last three years with less than 2,000 edits, and he could have got a nomination if he'd asked for it. So the advantage of a 1500 or even a 2000 threshold is that it would delay a group of candidates who can currently get badly bitten by the system, whilst having a healthy safety margin to avoid excluding serious candidates. My understanding of the pattern is that by the time an editor has 1500 edits they usually know enough not to run until they have a chance of getting through, so a 1500 bar if gently applied would improve our treatment of a bunch of newbies whilst not losing any potential admins.
446:
this project to raise or lower that bar. There have, however, been suggestions to introduce a low threshold that is just enough to screen out some people who the community won't take seriously as candidates, as WSC says. The French, German, and
Italian Wikis have such a threshold. Here at en.Wiki It's very rare to see anyone passing with less than around 3,000 edits these days, and Snottywong's table shows a median of more around 11,000. Only yesterday we had a candidate trying to transclude with only 36 edits. It won't show up in any stats because it was nipped quickly in the bud. What I suggest would be a threshold of 1,500 edits/3 months, and this is still lower than that practiced by the other countries. The only exception I can think of would be the rare times a new bot would need admin access for some reason or another. It would not be difficult for the devs to write a software block for editors who try to transclude under the bar, and load a templated message such as, for example:
1400:
dropped dramatically over the last 6 months, but the time I spend on
Knowledge (XXG) doing research and participating in other WikiMedia areas has in fact increased significantly. However, edit counts are not always a true demonstration of dedication - or maturity and responsibility either. It can be assumed that anyone with upwards of 6,000 edits might have sufficient clue for admin tasks, but is a poor criterion of character. Edit count is unfortunately one of the few metrics available. I'm not convinced that all voters actually look very hard at the quality of a candidate's edits or know how to interpret the pie chart.
1206:- it's not for preventing suitably mature and experienced candidates from voting. Lack of maturity, experience, and civility, have been demonstrated enough for it to be of concern. Some other Wikis have qualifications for voters. Autoconfirmed should be enough, with a topic ban for anyone who abuses the system three times for incivility, creating drama, unreflected voting, and posing silly questions. The fact that such rules would exist would be a deterrent and once they exist, they would probably not be broken. There is more important background at
240:"Thank you for applying to be a Knowledge (XXG) administrator. You do not appear to have sufficient experience at this time, and your application has been declined. nevertheless, you may wish to read xxxx and xxxx and xxx, and try again when you feel you meet the recommended minimum criteria. In the meantime you may wish to help out at Recent Changes Patrol and New Page Patrol, and taking part in more AfD, RfA, SPI, and AN/I, which will certainly help increase your experience of admin tasks significantly. Good luck, and happy editing!"
1210:. I was once plumply told by an admin to publish a list of the names of such editors, but I refused out of decency, only to be told by the same admin that by not naming them, I was acting like a child in an elementary school playground - one wonders how mature some of our existing admins really are - one only has to examine a year's worth of RfAs to know who the drama queens and kings are.
490:
797:, who could have got a nomination I'm certain). That would take out the NOTNOWs, and by the time they have 2000 edits, they should be savvy enough to know whether they should transclude. NB since 2009, removing MGA73, there were 0 successful candidates with 0-3000 edits, but 20 with 3000-5000 - so we should really pitch the bar below 3000.
1085:
aimed at getting a consensus from the community on whether a candidate should receive the tools or not. This isn't an election per se, but more of a discussion. If we limit who can participate, the number of !voters will surely decay over time due to lack of interest in "registering" to speak one's mind.
718:
I hate the editcountitis implied by editcount based thresholds, but too few of the electorate will seriously consider a candidate with less than 2,000 edits. I suspect that most candidates with 3,000 would struggle; Though of course if they had an FA and relevant experience on other projects it would
245:
Basically, we've discussed setting a bar before, but every time we have, people have assumed us to mean either raising it or loweriing it. This is not the case here. What we are doing here is making both the time wasters not waste their or our time, and encouraging others who may not
164:
We have a whacking great big warning template on the edit notice of the transclusion page but we still get clots who just don't read it . Thre solutions that could be proposed to the commuynity right now. The scripts are easy to instal in the site software and
Twinkle. Note that the
387:
Companies that are paying people need to be picky and sometimes to be arbitrary. Admins are not paid and we have no shortage of mops, so providing we screen out a few unsuitable candidates the more admins we appoint the better. That said a low threshold for self noms would screen out some people who
147:
edits. This is an exceptionally low edit count, and was the only successful RfA with less than 4,000 edits. While it's good that we can close RfAs early, frankly, it's ridiculous that absolutely anyone can run in the first place. It would save time, effort and stress if there was an edit count level
138:
Several good ideas on this page, but the idea I'd most like to see proposed is a set of minimum requirements for RfA candidates. This year, there have been 22 NOTNOW closures, plus multiple SNOW closures due to activity level. In the last year, the successful candidate with the lowest edit count was
1399:
A huge number of 'old timers' are stolid content workers and are probably not interested in any
Knowledge (XXG) meta subjects. The irony is that many of them are just the right kind of people to be admins. Edit counts are always a contentious issue - for example, my edit count has
682:
Don't mess around with 1500. I really DO worry then that you get a lot of 2000 edit noms and you do more damage than help with an unrealistic threshold. Make it 5000. We only had a tiny fraction of people (one?) below that in the first year, and he would have qualified in a few months. 10000 is
477:
Of course, there is always the psychological danger that once such a threshold is known, there may be a stampede of candidates who meet it. That's just the collateral damage we would have to take int consideration. It always amazes me that they don't take any notice of this in-your-face
415:
I really doubt anyone is going to quit because a mechanism stopped them from transcluding. A regulation. It's more being part of the process and losing that makes them sad. I would seriously consider to put the bar reasonably high. Let special cases (if really needed and we don't) be dealt with
356:
I will take any bar. That said, I recommend setting it high. Even if there are SOME editors who will do a great job with 3900 edits, it is just more efficient to set it at 10,000. Don't WORRY about excluding a small number of good candidates. Unis and companies routinely filter candidates. You
1297:
I have long held out the theory that grizzled old timers who've been here since, say, 2008 or earlier, are good to have at RfA. They are less likely to suffer from editcountitis and more likely to focus on what makes a good admin than being swayed by weak arguments in the oppose section. Maybe I'm
1224:
We currently have an unwritten rule for this, replacing it with a written rule isn't about extra bureaucracy it is about openness. Socks created purely for a particular RFA are rarely if ever worth listening to, but I don't think we get much participation from editors who have a few hundred edits,
828:
for adminship, it's more a fence to jump over to get to the door of the interview room. It prevents those who think
Knowledge (XXG) is a club, a blog, or a web forum, and those not tall enough, from getting anywhere near the building: "Come back when you've growm a few more inches and then we can
594:
I wouldn't worry about the rush from people who just meet the quota - by the time people have 1500 edits they usually have an idea as to their chances of passing. As for TCO's suggestion. 5,000 is higher than some candidates who have recently passed, so setting it at that level would mean delaying
445:
As I have said in several places before, the actual bar 'floats'. It depends on who turns out to !vote and what their individual criteria are. There is only a very small core of regular !voter that have their own set criteria. AFAIK, there have never been any serious discussions on
1176:
I was thinking that the "RfA voter" group should be designed to stop people creating an account solely to ruin the chances of a specific candidate - anything else could be gamed. The number of edits I'm not worried about (though there should be some) but I think the time period should be 1 week.
1148:
If we were going to go with a new "RfA voter" group, it could simply be automatically added to a user's account after they've been autoconfirmed. That way, we could stop most of the vandals while still allowing input from almost everyone. Having the new group also means that someone who has been
1084:
After reading through this proposal, I believe the community will immediately reject it. !Voters should not have to be qualified to !vote at an RfA, much like users who have discussions to try to get a consensus do not have to be qualified. We have to keep in mind that a request for adminship is
194:
If the user does not check the box but tries to save the page, a simple script that will load a notice declining the transclusion: "Sorry, but as you have not read up on all that is required to become an administrator, it will not be possible to process your request this time."
1229:
editors are welcome to !vote in RFAs and RFBs, but please read the guide for voters first." would be a good way to go. The only worry is that once you formalise a criteria you risk having standards inflation and at some point you'll need as many edits and as much tenure to vote in an RFA as you
372:
We also have stats for that too - of the ones who left
Knowledge (XXG) in disgust of the way they were treated at RfA. Whether the candidates pass or not, there is a clear need to filter out the drama mongers and and incivility from the voting process.. They might not all be
924:
My thoughts exactly, and if we have a software check (is this even possible? - I know we use it for elections, but they're not actually held on WP), IAR situations can be transcluded by any user over the
Journeyman level. We could even have a category of "Users who are willing to consider RfA
740:
I think that the problems with RFA these days have a lot to do with the fact that there doesn't seem to be any 'minimum requirement' per se. Therefore, inexperienced editors seem to have the impression that it doesn't take much to become an administrator when this, in fact, is not the case.
1051:
If we get a consensus for the suggestions I extrapolated above, there won't be a need for a nominator for those who have not reached
Journeyman - we would only be excluding the candidates who clearly are not ready for RfA. If in spite of that they still think they should be
683:
too high, if 11000 is the median. The warning is a waste of time, Kud. Make a real change, not something so flimsy as another exhortation. The minimum requirements is easy. If you guys can't nail that, then I have zero hope that you are going to do anything harder in terms of reform.
1318:
Only around 2% of our active admins even come back to support the RfAs with a vote of some kind, and even some of them don't always vote in an intelligent fashion, so we"re open to all sorts of suggestions as to how we can enlarge the pool of reasonable participants.
233:
3 We simply set the bar as low as possible (e.g. 2,000/3) to ensure that the certain time wasters don't waste our time, install a
Twinkle script that deletes the RfA proposal or the RfA if it has already been transcluded, and leaves a message on the applicant's talk
1225:
and I fear they are the group who can spot that there is an unwritten rule, but are unsure if they qualify. So provided it is kept low I'm happy to support a qualification for voting, to keep things simple we should use an existing threshold. I think that "All
823:
I'm happy with anything on the lines of 1,500/3 months, 1,500/6 months, or 3,000/6 months. I don't think we need 12 months like the German do (they have their own cultural reasons for the things the do). Let's not forget that the bar we are suggesting is not a
1052:
considered, they can ask an admin for an opinion. There is in fact no real reason why our bar should be any lower than those practiced by, say, the German Wiki (One year and significant four-figure edits). More important background to all this at
793:. Essays seem to agree that you should have 2000 edits and 6 months tenure minimum, so that seems like the right sort of place to put a software bar. Especially since we've only had one candidate since the beginning of 2009 who has had less than 2000 edits (
703:
WSC: Yes it is, but I didn't put it there! What we really need is something more attractive but that really hammers the message home. I'm thinking on the lines of
Fetchcomms' excellent modern page designs at the MedaiWiki outreach project.
762:
I think we should get a local consensus here for one of the solutions I have proposed above in 'Comment from Swarm', and the template above, with it's software block, and then draft a proposal we can agree on for posting at RfC.
647:
the "STOP" sign! Don;t we have a "WAIT!" sign instead? The stop seems horribly ... errmmm .... 'heavy-handed', or some such phrase. I can;t think of the right phrase, but I guess the rest of you guys will know what I meant, anyway :o)
217:"Please note that candidates with less than 4,000 edits and/or 6 months continuous editing are most unlikely to succeed. If you wish to continue please click here, but be aware that your application is unlikely to succeed."
970:
Thank you for your interest in wanting to serve Knowledge (XXG) as an administrator. However, at this time you do not appear to have been registered long enough or have made a sufficient number of edits. Please read the
455:
Thank you for your interest in wanting to serve Knowledge (XXG) as an administrator. However, at this time you do not appear to have been registered long enough or have made a sufficient number of edits. Please read the
1126:
I don't think that's too much to ask; we require that participants in other community processes as well (i.e. ArbCom elections). It makes sense to have an experience threshold for RFA participants, albeit an easily attainable one.
225:"Sorry, but you do not appear to have sufficient experience to become an administrator at this time. Please read the pages at xxx and xxx, and xxx, and discuss your request with an administrator before applying again."
261:
I'll just add that a lot of people here probably are not aware of the number of RfAs that don't make it to tranclusion, and I don't see a way of tracking those deleted or reverted applications for the stats.
1302:
would help more RfAs pass. And if more pass, more reluctant editors will step forward. It doesn't, of course, address the main problem, which is declining numbers of editors, but hey, at my best I'm good, not brilliant.
49:
416:
by crats going around the system. Set it high. You want to eliminate the waste of time train wrecks. Set it at 5000. Or even 10,000. 1500 is insane and does nothing for us. Might as well have no bar then.
389:
1500 edit can transclude to this page, not a snarky excuse to delete RFAs without consideration. we also need the safety valve of allowing other editors to nominate candidates and make a case for an exception.
167:
One should should demonstrate at least one year of experience as a writer and collaborators in various fields of the project. Candidates with less experience have no chance of being elected to adminship.
847:
I agree, and I'd prefer to set the bar lower for that reason. However, since no one has passed with less than 3000 (nor with less than 8 months) in the past 2.5 years, and we already have a "
719:
be a different matter. The trick is to set the threshold high enough to make a useful difference, low enough that it won't delay good candidates, and to have a safety valve for exceptions..
1014:
that we require a qualified nominator only for candidates that haven't reached Journeyman editor yet (or whatever criteria we agree upon; personally I like the Journeyman requirement).
1347:
Other Wikipedias with far fewer registersed users than en.Wiki have a similar turnout of voters at thneir RfAs. Each RfA is published at their Village Pump or some such venue.
1011:
373:
posting comments here, but some people are working constantly on stats in the background. Please consider !voting on the proposals when they are ready for RfC. Thanks. --
1263:(1,000/3m) as a qualification for voting. Other Wikis have a software check to see if voters have attained the requirement - no 'right' needs to be specially accorded.
357:
can't obsess on the one that got by. Think about an efficient process. And if they really love the encyclopedia, they will keep editing, regardless of the "moderator hat".
172:
Candidates that do not have a significant four-digit number of edits are mostly rejected. The proportions of the edits in different namespaces is often critically examined.
1333:
I didn't mention admins, but all old-timers. I think they could be encouraged with some carefully considered messaging on their talk pages, supported by the Signpost. --
34:
1428:
but nobody really responded there (I think it got buried in the other conversations). On the topic of the civility problem, perhaps it would be helpful to modify
460:
and when you have been registered for at least 3 months and have made at least 1,500 manual edits you may try again. You might also wish to join our
246:
be time wasters, but have little chance of passing, to take more advice and get more experience - such as those who would pass in another six months or so.
144:
1383:
They are less likely to suffer from editcountitis and more likely to focus on what makes a good admin than being swayed by weak arguments in the oppose section.
84:
512:
280:
132:
1252:
213:
if the software detects less than 4,000 for field 1, and/or less than 6 in field 2, a simple script will load a notice declining the transclusion:
564:
622:
Is that really the message we currently put for transclusion? I thought we limited that stop sign for badfaith final warnings before we block people.
221:
if the software detects less than 2,000 for field 1, and less than 3 in field 2, a simple script will load a notice declining the transclusion:
1149:
abusing the process can be blocked from voting for a finite period of time without going to the extreme length of hitting them with the banhammer. â
794:
1425:
898:
Yes, Journeyman level seems like a good place to start, unless someone has a heap of edits-and-good-standing globally but not necessarily in -en.
90:
913:
663:
790:
1464:
388:
the community won't take seriously as candidates. But it needs to be an automated thing in terms of permissions i.e. Only editors with : -->
1053:
1369:
likes this idea and part of me is somewhat skeptical. Will the old timers really be more reasonable !voters? What makes you think that?
311:
1111:
Keep in mind that the bar can be minimal- it could be one month and 50 edits. It doesn't have to mean making an "RfA voter" group.
30:
17:
1207:
79:
1230:
originally needed to pass one - but as we've seen with RFA, unwritten standards are more prone to inflation than written ones.
1100:
1432:
that people see when they're voting on an RfA. You could add material about the length of comments, badgering, civility, etc.
1429:
70:
1237:
907:
726:
657:
629:
602:
397:
1260:
1256:
976:
848:
741:
Establishing a minimum edit count threshold is a necessary measure to prevent candidates from pursuing RFA too soon.
504:
1193:
941:
867:
813:
1226:
190:
I'am aware that my RfA can and will be reverted or closed early if it is obvious that it will not succeed.
982:
461:
1450:
1409:
1394:
1377:
1356:
1342:
1328:
1312:
1272:
1246:
1219:
1197:
1171:
1156:
1143:
1121:
1105:
1065:
1030:
945:
919:
893:
871:
842:
817:
772:
757:
735:
713:
692:
669:
638:
611:
582:
425:
406:
382:
366:
343:
325:
292:
271:
256:
158:
1232:
899:
721:
649:
624:
597:
392:
60:
1178:
926:
852:
798:
527:
489:
100:
75:
186:
Before transcluding this page, please be sure to have read all the instructions and advice pages.
1202:
I don't think the community will reject it. We are forgetting again that this bar is not a
533:
1444:
1094:
323:
558:
539:
440:
522:
you nominate yourself. Adminship is not for new or inexperienced users. You need to have made
1405:
1390:
1352:
1338:
1324:
1308:
1268:
1215:
1061:
889:
838:
789:
Well, if we're looking for local consensus on what the bar should be - I'd suggest looking at
768:
709:
578:
378:
339:
288:
267:
252:
148:
that candidates have to meet before they are allowed to run. It would also filter out trolls.
56:
972:
457:
1138:
1025:
752:
1370:
1255:. It's been suggested that we take one of the lower service awards such as for example
1153:
1439:
1087:
318:
1458:
688:
421:
362:
307:
1401:
1386:
1348:
1334:
1320:
1304:
1264:
1211:
1057:
885:
834:
764:
705:
574:
374:
335:
284:
263:
248:
1161:
That's reasonable, but I think autoconfirmation is still too easily attainable.
1128:
1015:
742:
1163:
1150:
1113:
206:
Enter these details: 1. Total number of edits to date: 2. Total number of
150:
140:
526:
edits to articles and housekeeping tasks. You also need a good knowledge of
986:
465:
684:
417:
358:
303:
925:
Nomination requests". In fact, why the hell don't we have that already?
182:
A checkbox on that transcslusion page that reads something like this:
1385:
Maybe I'm wrong, but it's a fairly simple thing to try, isn't it? --
981:
award you may try again. You might also wish to join our
319:
25:
851:" - 2000/6m - I thought that'd be a good place to put it ;)
302:
have software stop it or have buros authorize transcludes.
563:. If you are not sure that you qualify, please ask an
1095:
1088:
1433:
108:
1300:encouraging long-standing users to !vote at RfA
964:
449:
281:Knowledge (XXG) talk:RfA reform 2011/Candidates
133:Knowledge (XXG) talk:RfA reform 2011/Candidates
8:
1253:Comparison of voting on RfA other Wikipedias
1426:Knowledge (XXG) talk:RfA reform (continued)
884:Excellent - and I like the Journeyman bit.
1165:
1115:
152:
1101:
283:. Please continue the discussion there.
135:. Please continue the discussion there.
1436:an example of how it might be tweaked.
478:message when they try to transclude:
544:, and to show that you can exercise
297:
7:
1372:
18:Knowledge (XXG) talk:RfA reform 2011
1298:completely wrong, but I think that
567:or an established user for advice.
33:for discussing improvements to the
551:Applications from editors without
279:: This thread has been copied to
165:German Knowledge (XXG) requires:
131:: This thread has been copied to
35:RfA reform 2011/Possible proposals
24:
791:the summary of candidate findings
55:New to Knowledge (XXG)? Welcome!
993:has an excellent programme too.
488:
472:has an excellent programme too.
50:Click here to start a new topic.
1139:
1135:
1129:
1026:
1022:
1016:
849:Journeyman editor service award
785:Minimum requirement suggestions
753:
749:
743:
515:Guide to requests for adminship
1329:14:53, 28 September 2011 (UTC)
1313:16:05, 27 September 2011 (UTC)
1:
1465:Requests for adminship reform
557:experience are often quickly
47:Put new text under old text.
1451:02:44, 12 October 2012 (UTC)
1293:Encourage oldtimers to !vote
1180:
928:
854:
800:
298:don't let newbies transclude
1410:00:51, 4 October 2011 (UTC)
1395:20:10, 3 October 2011 (UTC)
1378:18:13, 3 October 2011 (UTC)
1357:13:30, 3 October 2011 (UTC)
1343:12:59, 3 October 2011 (UTC)
1481:
98:
1220:10:54, 29 June 2011 (UTC)
1198:06:27, 29 June 2011 (UTC)
1172:02:24, 29 June 2011 (UTC)
1157:02:21, 29 June 2011 (UTC)
1144:20:08, 28 June 2011 (UTC)
1122:19:42, 28 June 2011 (UTC)
1106:17:27, 28 June 2011 (UTC)
1080:Qualifications for voters
1066:11:03, 29 June 2011 (UTC)
1031:15:41, 28 June 2011 (UTC)
946:11:34, 28 June 2011 (UTC)
920:11:24, 28 June 2011 (UTC)
894:10:46, 28 June 2011 (UTC)
872:10:29, 28 June 2011 (UTC)
843:10:09, 28 June 2011 (UTC)
818:09:23, 28 June 2011 (UTC)
773:01:28, 28 June 2011 (UTC)
758:01:19, 28 June 2011 (UTC)
736:20:07, 27 June 2011 (UTC)
714:18:08, 26 June 2011 (UTC)
693:16:39, 26 June 2011 (UTC)
670:11:28, 28 June 2011 (UTC)
639:16:36, 26 June 2011 (UTC)
612:16:33, 26 June 2011 (UTC)
583:16:25, 26 June 2011 (UTC)
548:in awkward situations.
426:15:54, 26 June 2011 (UTC)
407:15:13, 26 June 2011 (UTC)
383:21:03, 19 June 2011 (UTC)
367:19:26, 19 June 2011 (UTC)
312:19:22, 19 June 2011 (UTC)
293:03:22, 21 June 2011 (UTC)
272:09:06, 19 June 2011 (UTC)
257:08:57, 19 June 2011 (UTC)
159:02:31, 19 June 2011 (UTC)
85:Be welcoming to newcomers
1424:I suggested this on the
1273:07:35, 1 July 2011 (UTC)
1247:06:20, 1 July 2011 (UTC)
975:and when you have your
973:guidelines for adminship
458:guidelines for adminship
344:01:51, 2 July 2011 (UTC)
326:01:40, 2 July 2011 (UTC)
995:
474:
80:avoid personal attacks
1054:WT:RFA2011/CANDIDATES
833:to talk about it." --
560:declined as premature
352:Also set the bar high
202:2 Short questionnaire
334:See next thread. --
208:recent consecutive
1010:I've suggested in
501:
210:months editing:
124:Comment from Swarm
91:dispute resolution
52:
1448:
1261:Apprentice Editor
1208:WT:RFA2011/VOTING
1142:
1029:
756:
524:several thousand
497:
444:
121:
120:
71:Assume good faith
48:
1472:
1449:
1442:
1375:
1374:
1244:
1240:
1235:
1227:wp:Autoconfirmed
1191:
1187:
1186:
1168:
1167:
1140:
1137:
1136:
1133:
1118:
1117:
1103:
1097:
1090:
1027:
1024:
1023:
1020:
939:
935:
934:
910:
904:
865:
861:
860:
811:
807:
806:
754:
751:
750:
747:
733:
729:
724:
660:
654:
636:
632:
627:
609:
605:
600:
500:
499:Wait, Jonesey95!
492:
438:
404:
400:
395:
321:
155:
154:
143:, who had about
111:
26:
1480:
1479:
1475:
1474:
1473:
1471:
1470:
1469:
1455:
1454:
1437:
1430:the edit notice
1422:
1402:Kudpung āļāļļāļāļāļķāđāļ
1371:
1349:Kudpung āļāļļāļāļāļķāđāļ
1321:Kudpung āļāļļāļāļāļķāđāļ
1295:
1265:Kudpung āļāļļāļāļāļķāđāļ
1242:
1238:
1233:
1212:Kudpung āļāļļāļāļāļķāđāļ
1189:
1179:
1164:
1114:
1082:
1058:Kudpung āļāļļāļāļāļķāđāļ
1012:this discussion
937:
927:
908:
900:
886:Kudpung āļāļļāļāļāļķāđāļ
863:
853:
835:Kudpung āļāļļāļāļāļķāđāļ
809:
799:
787:
765:Kudpung āļāļļāļāļāļķāđāļ
731:
727:
722:
706:Kudpung āļāļļāļāļāļķāđāļ
658:
650:
634:
630:
625:
607:
603:
598:
575:Kudpung āļāļļāļāļāļķāđāļ
570:
569:
498:
493:
402:
398:
393:
375:Kudpung āļāļļāļāļāļķāđāļ
354:
336:Kudpung āļāļļāļāļāļķāđāļ
300:
285:Kudpung āļāļļāļāļāļķāđāļ
264:Kudpung āļāļļāļāļāļķāđāļ
249:Kudpung āļāļļāļāļāļķāđāļ
151:
126:
117:
116:
115:
114:
107:
103:
96:
66:
22:
21:
20:
12:
11:
5:
1478:
1476:
1468:
1467:
1457:
1456:
1421:
1418:
1417:
1416:
1415:
1414:
1413:
1412:
1363:
1362:
1361:
1360:
1359:
1294:
1291:
1290:
1289:
1288:
1287:
1286:
1285:
1284:
1283:
1282:
1281:
1280:
1279:
1278:
1277:
1276:
1275:
1257:Novice Editor)
1081:
1078:
1077:
1076:
1075:
1074:
1073:
1072:
1071:
1070:
1069:
1068:
1040:
1039:
1038:
1037:
1036:
1035:
1034:
1033:
1001:
1000:
999:
998:
997:
996:
957:
956:
955:
954:
953:
952:
951:
950:
949:
948:
877:
876:
875:
874:
795:a special case
786:
783:
782:
781:
780:
779:
778:
777:
776:
775:
700:
699:
698:
697:
696:
695:
675:
674:
673:
672:
620:
619:
618:
617:
616:
615:
614:
572:
546:sound judgment
507:Administrators
495:
487:
486:
485:
484:
483:
482:
481:
480:
479:
475:
447:
431:
430:
429:
428:
410:
409:
385:
353:
350:
349:
348:
347:
346:
329:
328:
299:
296:
247:
243:
242:
236:
235:
229:
204:
203:
198:
192:
191:
184:
183:
170:
169:
125:
122:
119:
118:
113:
112:
104:
99:
97:
95:
94:
87:
82:
73:
67:
65:
64:
53:
44:
43:
40:
39:
38:
23:
15:
14:
13:
10:
9:
6:
4:
3:
2:
1477:
1466:
1463:
1462:
1460:
1453:
1452:
1446:
1441:
1435:
1431:
1427:
1419:
1411:
1407:
1403:
1398:
1397:
1396:
1392:
1388:
1384:
1381:
1380:
1379:
1376:
1368:
1364:
1358:
1354:
1350:
1346:
1345:
1344:
1340:
1336:
1332:
1331:
1330:
1326:
1322:
1317:
1316:
1315:
1314:
1310:
1306:
1301:
1292:
1274:
1270:
1266:
1262:
1259:(200/1m) or
1258:
1254:
1250:
1249:
1248:
1245:
1241:
1236:
1228:
1223:
1222:
1221:
1217:
1213:
1209:
1205:
1204:qualification
1201:
1200:
1199:
1195:
1188:
1185:
1184:
1175:
1174:
1173:
1170:
1169:
1160:
1159:
1158:
1155:
1152:
1147:
1146:
1145:
1141:
1134:
1132:
1125:
1124:
1123:
1120:
1119:
1110:
1109:
1108:
1107:
1104:
1099:
1098:
1092:
1091:
1079:
1067:
1063:
1059:
1055:
1050:
1049:
1048:
1047:
1046:
1045:
1044:
1043:
1042:
1041:
1032:
1028:
1021:
1019:
1013:
1009:
1008:
1007:
1006:
1005:
1004:
1003:
1002:
994:
992:
991:
990:
984:
983:Admin School
980:
979:
974:
969:
963:
962:
961:
960:
959:
958:
947:
943:
936:
933:
932:
923:
922:
921:
917:
916:
911:
905:
903:
897:
896:
895:
891:
887:
883:
882:
881:
880:
879:
878:
873:
869:
862:
859:
858:
850:
846:
845:
844:
840:
836:
832:
827:
826:qualification
822:
821:
820:
819:
815:
808:
805:
804:
796:
792:
784:
774:
770:
766:
761:
760:
759:
755:
748:
746:
739:
738:
737:
734:
730:
725:
717:
716:
715:
711:
707:
702:
701:
694:
690:
686:
681:
680:
679:
678:
677:
676:
671:
667:
666:
661:
655:
653:
646:
642:
641:
640:
637:
633:
628:
621:
613:
610:
606:
601:
593:
592:
591:
590:
589:
588:
587:
586:
585:
584:
580:
576:
568:
566:
562:
561:
556:
555:
549:
547:
543:
542:
537:
536:
531:
530:
525:
521:
518:
517:
516:
510:
509:
508:
496:
491:
476:
473:
471:
470:
469:
463:
462:Admin School
459:
454:
448:
442:
441:edit conflict
437:
436:
435:
434:
433:
432:
427:
423:
419:
414:
413:
412:
411:
408:
405:
401:
396:
386:
384:
380:
376:
371:
370:
369:
368:
364:
360:
351:
345:
341:
337:
333:
332:
331:
330:
327:
324:
322:
316:
315:
314:
313:
309:
305:
295:
294:
290:
286:
282:
278:
274:
273:
269:
265:
259:
258:
254:
250:
241:
238:
237:
232:
231:
230:
227:
226:
222:
220:
218:
214:
211:
209:
201:
200:
199:
196:
189:
188:
187:
181:
180:
179:
178:Suggestions:
176:
175:
168:
163:
162:
161:
160:
157:
156:
146:
142:
136:
134:
130:
123:
110:
109:WT:RFA2011/PP
106:
105:
102:
92:
88:
86:
83:
81:
77:
74:
72:
69:
68:
62:
58:
57:Learn to edit
54:
51:
46:
45:
42:
41:
36:
32:
28:
27:
19:
1423:
1382:
1366:
1299:
1296:
1231:
1203:
1182:
1181:
1162:
1130:
1112:
1093:
1086:
1083:
1017:
988:
987:
977:
967:
965:
930:
929:
914:
901:
856:
855:
830:
825:
802:
801:
788:
744:
720:
664:
651:
644:
623:
596:
571:
559:
554:considerable
553:
552:
550:
545:
540:
538:, and other
534:
528:
523:
519:
514:
513:
506:
505:
503:Please read
502:
494:
467:
466:
452:
450:
391:
355:
301:
276:
275:
260:
244:
239:
228:
224:
223:
219:
216:
215:
212:
207:
205:
197:
193:
185:
177:
173:
171:
166:
149:
137:
128:
127:
29:This is the
1420:Edit notice
1365:Part of me
989:WIKIVERSITY
468:WIKIVERSITY
978:Journeyman
968:Jonesey95!
453:Jonesey95!
1440:Adjwilley
643:Ooooh, I
535:copyright
320:My76Strat
317:I agree.
93:if needed
76:Be polite
31:talk page
1459:Category
1243:Chequers
732:Chequers
635:Chequers
608:Chequers
541:policies
529:deletion
511:and the
403:Chequers
101:Shortcut
61:get help
1387:Dweller
1335:Dweller
1305:Dweller
1434:Here's
1367:really
1154:Pyfan!
1131:Tyrol5
1089:Eagles
1018:Tyrol5
966:Hello
915:stalk!
745:Tyrol5
665:stalk!
520:before
451:Hello
1373:Swarm
1239:Spiel
1166:Swarm
1116:Swarm
902:Pesky
831:start
728:Spiel
652:Pesky
645:hated
631:Spiel
604:Spiel
565:admin
399:Spiel
234:page:
153:Swarm
145:3,900
141:RHM22
89:Seek
37:page.
16:<
1445:talk
1406:talk
1391:talk
1353:talk
1339:talk
1325:talk
1309:talk
1269:talk
1251:See:
1234:ÏĒere
1216:talk
1194:talk
1183:Worm
1096:24/7
1062:talk
985:and
942:talk
931:Worm
909:talk
890:talk
868:talk
857:Worm
839:talk
814:talk
803:Worm
769:talk
723:ÏĒere
710:talk
689:talk
659:talk
626:ÏĒere
599:ÏĒere
579:talk
464:and
422:talk
394:ÏĒere
379:talk
363:talk
340:talk
308:talk
289:talk
277:Note
268:talk
253:talk
129:Note
78:and
1151:Oli
1102:(C)
685:TCO
418:TCO
359:TCO
304:TCO
1461::
1408:)
1393:)
1355:)
1341:)
1327:)
1319:--
1311:)
1303:--
1271:)
1218:)
1196:)
1064:)
1056:.
944:)
918:)
892:)
870:)
841:)
816:)
771:)
712:)
691:)
668:)
581:)
573:--
532:,
424:)
381:)
365:)
342:)
310:)
291:)
270:)
255:)
59:;
1447:)
1443:(
1438:~
1404:(
1389:(
1351:(
1337:(
1323:(
1307:(
1267:(
1214:(
1192:(
1190:·
1060:(
940:(
938:·
912:âĶ
906:(
888:(
866:(
864:·
837:(
812:(
810:·
767:(
708:(
687:(
662:âĶ
656:(
577:(
443:)
439:(
420:(
377:(
361:(
338:(
306:(
287:(
266:(
251:(
174::
63:.
Text is available under the Creative Commons Attribution-ShareAlike License. Additional terms may apply.