244:
contribute their thoughts and feelings without the process becoming bogged down in debate. Besides, the process of compiling the report is much the same as crafting an article - it's quite common for an article to be researched or compiled offline or in a sandbox, before being moved into the mainspace (or projectspace) in this case, once it's in a fit state for wider examination. The process is community driven - the structure of the review, the questions and the responses have all been from the community. All that's happening is that the report is being prepared for upload in one block, so that the community can then analyse it, discuss it and so on in one contiguous piece. The methodology being used is quite similar to that used for corporations and businesses to analyse internal processes. I hope that clarifies things for you.
296:...and so forth. I would also expect that, once we have this list of responses and how widely held each is, that the community (or Gazimoff, or whomever) would provide some analysis, such as "Examples of admins as policy enforcers included , provided by ]...", where the (admittedly few) diffs would be incorporated. Most of the questions are intended to gauge where RFA and adminship is currently, and I think the specific question I use as an example is intended to give us a target - where is adminship now, and how should that impact how we choose admins? So long as we can edit the report - which we will - I don't have a problem with Gazimoff doing the initiall analysis and tally - though, if he were to provide his reporting format and a block of responses, I'd be happy to pitch in.
1290:
1618:
point was around the risk the project faces from having a small number of highly active editors and to raise questions from it. Do we feel that the risk has a low impact or low probability, or do we feel that it has a high impact or probability and requires reasonable mitigation. It's only prudent to ensure that you manage risk effectively, which includes analysing workload distribution and levelling in order to mitigate or lower overall risk to the project. The examples were to try and illustrate the examples that contribute to this risk. Admittedly, I should have qualified my statement somewhat, but the question on overall risk level and what constitutes an acceptable level remains. Many thanks,
1302:
1278:
1055:
382:, except that it will be in alphabetical order. Then I'll break the list into 20-25 names apiece, and each of us can read through the responses and tally the comments. I don't think we need to go too in depth, as that's what Gazimoff is doing with his logical analysis. This read will be to determine, for example, how many people oppose Self-Noms? I'll plug the tallys into a spreadsheet and graph the results. Maybe I'll do a trial run tonight, just to see if it's feasible, but I don't anticipate many problems.
973:
1522:
again. Secondly, by placing a large amount of work on a small team of admins you begin to increase the levels of stress and risk of burnout. In order to reduce these risks, it makes sense to recruit more admins who are prepared to carry out admin tasks and reduce the burden placed on any one individual. Lucklily being a voluntary organisation, we are only limited by those who wish to take on the role and who the community feels are suitable. Hope this helps,
1427:
1070:
graph canvassing responses, that person is counted twice - they held both sentiments. So percentages are dicey, and will be for most questions. The exceptions will be the next to last two, "Ever vote in an RfA?" and "Ever a candidate?", where we have a sharp divide between yes and no. For those, I'll add the responses where the editor didn't offer an answer as a third choice, "No response", and give a percentage of the total. I
91:
1574:
of the project - then I'm not concerned about the number of inactive admins. I do want to know what leads them to be inactive, and whether some of the inactive admins still edit - remember, inactive is counted as an admin who has performed no administrative tasks in 30 days. Is it an aspect of the culture surrounding adminship? Or perhaps it is natural that more admins would be inactive over time.
273:<- I think, if we had a bigger team and could parcel out the responses 10 or 20 per editor, then a group draft would be workable - and maybe it is. My understanding is that the report from Gazimoff will basically collate the responses and find common threads. For example, on the question "How do you view the role of an administrator?", the report will likely say that, of 200 responses,
819:
672:
614:. What I'd like to do, if this format works, is to set up a page for each set of remaining responses, 5 at a time, and get others to assist in tallying the responses. If there's a comment that doesn't fit a current field, no problem - a new row can easily be added. Once we have them all, I'll combine them and make up nice pretty graphs of the results.
1362:
uses data from the List of
Administrators and other sources to show the proportion of active administrators to total administrators." which uses "proportions". It may seem a small point, yet it is highly important in the field of interpretation of data, of which others have stated elswhere I have some expert knowledge.
1601:
Admins, like all editors, choose what they want to contribute. No individual has a defined minimum or maximum remit. Is there evidence to show that the most active admins have a higher rate of burnout? I expect that the most active admins have a specific personality type that drives them to make more
1521:
Axl, I think I disagree. The problem is that by having a small nexus of highly active admins, you do two things. Firstly, you place a high level of reliance on those admins for keeping backlogs low. This can lead to problems when a highly active admin leaves the project, as backlogs start to creep up
1361:
It is good work, but if I can impose here just for a small, yet important point (given that I haven't contributed before here), the labelling as given in the description for the thord graph does not correspond to what is shown. The graph shows numbers of people, and the description states "This chart
606:
OK, there are two phases of the
Reflect process. One is the Qualitative analysis, which Gazimoff and others are working on - what was said in the responses? The other is the Quantitative analysis, which I am working on - how many people said X, Y, or Z? I stress that this doesn't dimish the responses
137:
Fair point, and I need to get a page up explaining what this stage is all about. Essentially, I'm currently compiling a report on all responses to the question phase (circa 200), before submitting it for review for depth of content, balance and neutrality. This report will then form the basis for the
1573:
Agreed; I was using a hypothetical to tie the discussion into the survey, I see no evidence from the source to support that. So long as the growth of admins, active and total, is consistent with the growth of the userbase, the article count, and the daily volume of edits - in effect, with the growth
1400:
Yep, you're completely right about the third chart and I'd add to it that not starting the axis at zero makes it even harder to judge. Mind you, the second one covers the proportion of active to inactive easily enough, while the first one shows total trends easily enough. I'm not sure if any log-lin
1372:
If one were really intent on exploring this, and it may be too much to realistically do, one might consider doing some log-linear modelling to assess any statistical significance to such data, though the information would have to be re-jigged to do that (issues to do with satisfying various crietria
997:
I think the 3D on some of the graphs isn't necessary, but it's not a very big issue. So far I like what you've been doing. A pie graph for C4 between "limited canvassing OK"/"link from userpage OK", "unlimited canvassing OK", "no canvassing OK", and "bot generated list OK" might be useful. On the
565:
I'm working my way through a tally of how many times common responses were given. Once I have fifty or so, I'll post something and group the remaining responses, so others can tally as well. I'm basically adding unique responses to the list as I go, but those are getting fewer and farther between as
1617:
Stress and burnout can happen in voluntary organisations as well as in the workplace. But the consequences are the same as a highly active editor who decides to move on to other projects, or who loses interest or enthusiasm, or who has a life changing event that requires them to contribute less. My
1364:
The two (the graph and its description) need to be brought into agreement: Either (a) change the description to use "numbers" instead of "proportions", or (b) recast the graph so that it plots the proportion of active admins against time, there being no need to have the proportion of admins in this
888:
responses. I'm going to see if there's a way to get this spreadsheet (which includes over 440 distinct responses and statements) into some sort of format to distribute, if only to ensure that this review is open and public. Maybe I can post the CSV as code, perhaps? We'll figure it out, but for now
1503:
active. If the top 10 most active admins, say, were a group or acted as a bloc at rfa or elsewhere, it'd certainly fuel concerns over clique-ishness (as were raised under question 1). I'd be curious to see a breakdown of how that chart would look for, say, the past year, rather than the history of
1433:
This was the chart I was thinking of. The data behind it (you can read it off the chart) shows that roughly 80 admins are responsible for 50% of admin actions (deletes, blocks, protects, granting rollback/acc, etc). Slicing it a different way, roughly two thirds of the admins have performed 10% of
1336:
That's some fantastic work. So essentially, for the previous twelve months, although the total admin count has increased the number of active admins has flattened? I think in order to round this work off, I need to take a copy of the data table that lists the admin actions undertaken by each admin
1069:
Yeah, that's total responses, which I should indicate somewhere. I'm mainly trying to show which statements popped up more than others, but there are a few snags. For example, we had a few people who said that "RfAs don't get enough attention" AND "Limited
Canvassing is OK, if neutral", so when we
476:
After some discussion, I'm opening this work up. i was wrong to think I could complete it by myself, and I need help piecing it all together. currently I have handwritten notes on some 60 submissions, which I'm using to create the article structure before filling them out with information from the
422:
I agree, except that I would like to leave the chart open until we're done. If I have three different responses for
Question 1, and the next survey has a response that fits none of those, then I can just add it to the list; subsequent items that match it can be added to that tally. I think I moved
1455:
I've updated the third graph, above, with a clearer description that substitutes numbers for proportions - and remind me never to upload images when I'm in a hurry, as that's what I get for copy-pasting. My intent was to illustrate the trends in both total and active admins, and didn't think that
794:
Thanks again for the assistance, we're making good progress. One note, though - if you find a questionnaire that's blank, just take the "1" out of the "Total
Responses" line at the top of the page, and leave a note at the bottom or in your edit summary; I'll remove it from the total, and from the
980:
OK, so now that we have our numbers, I'm starting to see what graphs would be worth including. Are there any comparisons you see that might be interesting? I have a few in mind already. I'd also like to know if it's worthwhile to put graphs in the
Reflect page itself, or if an appendix (or Graph
397:
That's great. I'd like to make a judgement call on completed response sheets that were not added to the responses list but are still in the cat, as there is a lot of feedback in some of them. Personally, I'd like to include all apart from the blanks and non-response-related submissions. Also, if
402:, which I'm using to tag responses once I've processed them. You might want to look at a similar cat to track tally processing. You might also want to define your tally chart before counting, so that we can get an idea of the granularity. Hope this helps, bit of a rush of blood to the head :)
312:
That's a goods point, and one that I'm keen on sharing the workload on. My analysis is centred on examining the statements from each editor in order to build up an overall picture, and is time consuming. If you can perform a statistical analysis on the feedback, the report can contain both a
243:
It's a good question, and a valid one at that. Essentially, I offered to perform this review, as previous wiki-centric processes had failed to reach any meaningful consensus. Because editors hold a wide range of disparate views, it was felt that a survey-based approach would allow editors to
914:
chose to make comments outside of the questions. I'm not quite sure how to handle this, though my first blush idea would be to look at what he said and just put it in the question-blocks where it fits. Just trying to get a little advice first, though. Cheers, everyone, and thanks.
1638:
Okay, I see what you mean. However
Knowledge is no ordinary voluntary organization. As I said above, individuals determine their own workloads. Are you (or someone else) able to find out who (say) the top ten active admins are, and ask them specific questions on their talk pages?
1152:
I was thinking that there's a bot that parses a list of active admins (currently around the 1000 mark). I'd like if possible to get some recent trend graphs to show how the number of total admins and number of active admins vs total registered user count. What do you think?
1135:
OK, we have stats for every section, as well as some prose to explain what the numbers are. I'd like to get some input on what else to add to the report. Are there RfA statistics that would be worthwhile? I think we're closing in on the next phase, which should be exciting.
496:, or help to clarify meanings. If they include refs to examples, add those refs to the reflect article. Once that's done, tag it as processed and move on to the next one. Once all are processed, we can develop conclusions and summary bullet points. One of the things that
932:
Range 28 had someone do the same, and I just plugged in the answers where they fit. I've also been doing that for the last question, if they offer a suggestion that I know I've seen in a previous question - statements about NOTNOW falling under voting, for
1365:
case, as it would always be at 100% or 1.0 (depending on whether one uses percentages or fractional depictions of proportions), or (c) change the wording in this graph to use "numbers" and plot a small additional graph which directly plots the proportion.
1252:
I'll have a look. I've got the graph for the past year, though - I'll upload it momentarily. It looks like adminship has trended up (from 1307 last august to 1584 now), while active admins have stayed relatively flat. Let me see what I can come up with.
1434:
the total admin actions, while one third are responsible for 90% of the total number of actions. I think this chart shows that not only do we need more admins, but we need more active admins willing to perform janitorial duties.
1456:
starting at 600 would cause a problem (as neither figure dipped below 800 during the sample period). I can correct that bit, as well, but I concur with
Gazimoff that the first two graphs accomplish our purposes well enough.
1208:. Near as I can tell, automatic updates started on 20 August (!), so we have a year of data. I'll run the inactive numbers and compare the trend for the past year, unless someone has stats for more than a year ago... maybe?
1105:
For my own preference, I'd avoid 3D graphs as they can introduce a perspective distortion in the representation. Other than that, it's some fantastic work and given me a bit of a kick up the ass to get my side finished :)
1504:
the project. A trendline on that would be fascinating. On point, we had two responses that said that there were too many inactive admins, so I don't know that we can tie a recommendation to it... let's think about it.
1368:
It depends on whether one wants to interpret the figures as indicating that "the total number of admins has risen, whilst the number of active admins has flattened", or whether "the proportion of active admins has
398:
possible I'd like some stats on the responders, such as admin/non-admin, time since registered etc as a form of demographic analysis, although I suspect this would be best suited to bot-work. I also have a cat,
176:
Ish. Why do you ask? If you could give me some further information or background to your question, I'd probably be able to give you a more complete answer. The structure of the report, however, is based on the
1483:
I disagree. This chart shows that there is a wide variation in the degree of admin-type activity between different admins. It does not demonstrate a need for more admins, or a need for more active admins.
1602:
contributions. I am not convinced that increasing the number of admins (or increasing the number of "active" admins) will actually reduce the workload of the most active, or reduce their risk of burnout.
1401:
analysis would help here - the dataset doesn't feel as if it would show anything from it and I'm not sure if it would highlight anything that would be of use. I'm happy to listen to suggestions though.
213:
Because I had been under the mistaken impression that this was a community-driven review, not one person running a survey. Why, on a wiki, are you avoiding a communal writing process for the report?
1558:". These data don't demonstrate that. Regarding "too many inactive admins", which Gazimoff also alludes to, the relevant question is: Are backlogs increasing due to inadequate admin-type activity?
739:
Life intervened, I'm afraid - but I've now posted the remaining 15 lists, so all responses are accounted for. I'll work a list later today; with enough help, we should bang this out in no time.
477:
remainder. Problem is, at this rate it's going to be about 3 months before I manage to process the remaining three quarters of the submissions. That's why I need help in finishing this article.
607:
into sheer numbers, or a popular vote - rather, it's intended to highlight numerical trends in the responses to help find common threads, and to determine how common those threads were.
500:
was looking at was adding tally information to give an idea of the level of responses for each section of the report. If you'd like to help out in this area as well, that would be great.
1320:, which is exactly what I need - but it doesn't have April - July 2007, which I'm missing. If I can track those numbers down, or extrapolate them, we'll have a 6 year trend to review.
348:
I'm game, assuming you guys have any use for relatively unskilled !labor. I've also got access to a dumb station to run things on I won't need for the rest of this week. Cheers. --
998:
bar graphs, noting total responses to each of the questions would be useful for interpreting the data; this could be included in the footnote, though. Just some thoughts. Cheers.
795:
category for responses. That'll help when we do totals, such as finding out how many responses favored self-noms vs the total, or what have you. Thanks again for the assistance!
524:
I'll be throwing some time at this, to see what we can extract from it and some pointers as to where we are headed, and we will be pleased to assist in whatever way I can.
138:
recommendation section. It's going to be approximately 2 weeks before the report is up for peer review here, as there's a lot of study to complete. Hope this makes sense.
545:
If you'd be interested in helping me process responses and build the report, that would be a huge hlp. It's time consuming work, but hopefully worthwhile. Many thanks!
1337:
and do some analysis there for another graph in order to examine the admin workload breakdown. I'll let you know once I have more on that. Great work so far though!
492:. What needs to happen is for each response that has not been processed, responses to each section need to be analysed to see if they add anything to the report at
610:
Here's where I am. I've taken the first 55 or so responses (alphabetically) and tallyed the comments. The different comments I found are broken out by question at
1330:
1218:
489:
371:
259:
222:
196:
171:
153:
1466:
1449:
1352:
1263:
1243:
1187:
1168:
1121:
1009:
959:
943:
749:
663:
591:
576:
453:
433:
417:
392:
365:
343:
328:
899:
763:
1289:
1044:
1028:
1416:
1386:
1611:
1584:
1567:
1514:
1493:
858:
730:
713:
Dunno' what's goin' on with this right now (nothing since the 25th, looks like), but I'll be doin' at least one a day 'til they're all done. Cheers.
560:
540:
680:
64:
1648:
1633:
1537:
1146:
1084:
991:
1544:"If the top 10 most active admins, say, were a group or acted as a bloc at rfa or elsewhere, it'd certainly fuel concerns over clique-ishness."
789:
1195:
102:
1301:
805:
693:
627:
1033:
Ehm, I believe it's number of users, not percent of users. So, 126 is a reasonable number out of 209. A bit low, if anything. Cheers.
481:
375:
843:
707:
518:
485:
399:
131:
878:
306:
1473:"I think this chart shows that not only do we need more admins, but we need more active admins willing to perform janitorial duties."
566:
I proceed. One thing I can say with certainty, though - almost everyone agrees that candidates should be able to withdraw at will.
379:
926:
1014:
Side note, I can't tell the color scheme for 1% and 30% they are too close to each other. Also, how do we end up with 126%?---
1591:"By placing a large amount of work on a small team of admins you begin to increase the levels of stress and risk of burnout."
1177:, which would be fun to graph. Still looking for the active list, though - but I agree, we should include it as background.
1580:
1510:
1462:
1326:
1259:
1214:
1183:
1142:
1080:
987:
939:
895:
864:
801:
745:
689:
623:
587:
572:
429:
388:
339:
302:
683:, and will complete the list later today. It should be pretty straightforward - and thanks to everyone who helps out!
21:
1277:
656:
438:
Fair enough, works for me. If I come across any blanks myself, I'll shift them into your cat as well. Many thanks,
35:
1499:
I think it does demonstrate that the most active administrators over the history of the project have been really,
1228:
for further background information, particularly the part on total admin actions. Hope it's of interest to you.
725:
555:
513:
448:
412:
360:
323:
254:
191:
148:
70:
1313:
967:
617:
Is this a process that can work? Or is there a better way I'm missing? Thanks in advance for the assistance,
611:
313:
mathematical and logical analysis of the survey results. It's a great idea, and I'm all for it. Many thanks!
55:
75:
60:
1174:
423:
two unsubmitted responses, mainly to populate the category - but, I agree, only blanks should go there.
698:
I'll take a stab at some of the "groups of 5". Can statistics really be fun? I'll report back. :)
776:
While the plural of
Majorly might be Majorlys, I'm pretty sure that the plural of tally is tallies.
50:
17:
1224:
I dont have one myself. But I think it'd be great to see that graph. You might also want to look at
905:
1317:
601:
1200:
OK, so I've got the numbers for active admins, based on trolling the update history of the master
650:
471:
218:
167:
127:
911:
1023:
45:
8:
1381:
777:
754:
I did one of the ranges. Wow, was it tedious. I mean fun. It was fun. Join in, everyone!
1626:
1530:
1442:
1409:
1345:
1236:
1161:
1114:
1039:
1004:
954:
921:
838:
721:
641:
553:
511:
446:
410:
356:
321:
252:
214:
189:
163:
146:
123:
117:
1575:
1505:
1457:
1321:
1254:
1225:
1209:
1178:
1137:
1075:
1054:
982:
934:
890:
874:
854:
829:
796:
759:
740:
703:
684:
618:
582:
567:
497:
424:
383:
334:
297:
972:
493:
178:
1016:
533:
378:
to the unsubmitted category. Then, the responses category will match the list at
503:
Many thanks for any help and support you can provide in completing this report.
1374:
889:
I'll be posting some of the highlights. Again, thanks to everyone for helping!
581:
Breaking for lunch, I'm up to 36; I expect I'll have 50 by the end of the day.
1644:
1621:
1607:
1563:
1525:
1489:
1437:
1404:
1340:
1231:
1201:
1156:
1109:
1034:
999:
949:
916:
833:
714:
636:
547:
505:
440:
404:
349:
315:
246:
183:
140:
1205:
870:
850:
810:
755:
699:
849:
Nice job, guys. That was some tedious and time consuming work. Well done.
162:
So this is a solo project, at least in terms of basic report composition?
1426:
374:, and my first task will be to move the unsubmitted items from the main
832:
still has three to record, though. Cheers, everyone, and great work.
527:
181:
of the review, encompassing all responses provided. Hope this helps.
1640:
1603:
1559:
1485:
884:
Thanks to everyone who helped out - we now have statistics on all
333:
OK, let me work up a method, then. Anyone else want to pitch in?
869:
And... I'm spent. Turns out statistics can, indeed, be fun. :)
90:
679:
I have posted the first 100 responses in ranges of 5 each at
490:
Category:Unsubmitted
Wikipedian responses to RfA Review
372:
Category:Unsubmitted Wikipedian responses to RfA Review
370:
I've created a category for the unsubmitted responses,
633:
It looks reasonable enough to me. No problems here.
1373:to make the applied log-linear models valid, etc)
681:Knowledge:RfA Review/Reflect/Statistical Analysis
122:Where, exactly, is this reflection taking place?
1074:already did one already for "Ever voted?".
482:Category:Wikipedian responses to RfA Review
376:Category:Wikipedian responses to RfA Review
488:. Blank or meaningless forms should be in
486:Category:Processed responses to RfA Review
400:Category:Processed responses to RfA Review
948:Gotcha'. I'll go do it, then. Cheers.
1425:
1053:
971:
484:. Processed responses should also be in
380:Knowledge:RfA Review/Question/Responses
14:
1271:Here's what I have for the past year:
1196:Admin statistics, Inactive and Active
480:All submitted responses should be in
981:gallery) would be better. Thoughts?
813:'s doing the last one, then we are
27:
976:Quick and dirty, graph number one.
292:view admins as enforcers of policy
28:
1662:
1173:Total admin counts are listed at
1300:
1295:Proportion of Active to Inactive
1288:
1276:
817:
670:
280:view admins as authority figures
89:
1312:There are also some charts at
84:
13:
1:
1314:User:NoSeptember/admin graphs
612:User:Ultraexactzz/RREV Tallys
7:
1649:08:16, 30 August 2008 (UTC)
1634:21:53, 29 August 2008 (UTC)
1612:15:46, 29 August 2008 (UTC)
1585:17:42, 29 August 2008 (UTC)
1568:15:37, 29 August 2008 (UTC)
1538:12:44, 29 August 2008 (UTC)
1515:12:21, 29 August 2008 (UTC)
1494:15:29, 28 August 2008 (UTC)
1467:16:43, 21 August 2008 (UTC)
1450:15:50, 21 August 2008 (UTC)
1417:16:05, 21 August 2008 (UTC)
1387:15:01, 21 August 2008 (UTC)
1353:14:46, 21 August 2008 (UTC)
1331:14:04, 21 August 2008 (UTC)
1307:Active vs Total, Trendlines
1264:13:02, 21 August 2008 (UTC)
1244:12:29, 21 August 2008 (UTC)
1219:12:21, 21 August 2008 (UTC)
1188:15:20, 20 August 2008 (UTC)
1175:User:NoSeptember/admincount
1169:15:07, 20 August 2008 (UTC)
1147:15:03, 20 August 2008 (UTC)
1122:10:19, 14 August 2008 (UTC)
1085:01:52, 14 August 2008 (UTC)
1045:21:37, 13 August 2008 (UTC)
1029:21:32, 13 August 2008 (UTC)
1010:18:25, 13 August 2008 (UTC)
992:16:48, 13 August 2008 (UTC)
960:14:57, 12 August 2008 (UTC)
944:14:55, 12 August 2008 (UTC)
927:14:42, 12 August 2008 (UTC)
900:15:33, 13 August 2008 (UTC)
879:13:33, 13 August 2008 (UTC)
859:14:46, 13 August 2008 (UTC)
844:13:11, 13 August 2008 (UTC)
10:
1667:
806:14:59, 4 August 2008 (UTC)
1318:Image:En-admin-growth.png
790:21:23, 31 July 2008 (UTC)
764:18:46, 31 July 2008 (UTC)
750:12:43, 31 July 2008 (UTC)
731:04:07, 31 July 2008 (UTC)
708:15:52, 25 July 2008 (UTC)
694:14:54, 25 July 2008 (UTC)
664:18:24, 24 July 2008 (UTC)
628:18:14, 24 July 2008 (UTC)
592:15:28, 18 July 2008 (UTC)
577:15:19, 18 July 2008 (UTC)
561:08:32, 18 July 2008 (UTC)
541:07:42, 18 July 2008 (UTC)
519:00:46, 18 July 2008 (UTC)
18:Knowledge talk:RfA Review
454:22:06, 8 July 2008 (UTC)
434:21:49, 8 July 2008 (UTC)
418:21:35, 8 July 2008 (UTC)
393:20:51, 8 July 2008 (UTC)
366:20:28, 8 July 2008 (UTC)
344:12:40, 8 July 2008 (UTC)
329:10:22, 8 July 2008 (UTC)
307:15:01, 7 July 2008 (UTC)
260:20:17, 6 July 2008 (UTC)
223:19:04, 6 July 2008 (UTC)
197:18:50, 6 July 2008 (UTC)
172:18:28, 6 July 2008 (UTC)
154:18:45, 5 July 2008 (UTC)
132:06:14, 5 July 2008 (UTC)
286:view admins as janitors
1599:
1552:
1481:
1430:
1059:
977:
36:Requests for Adminship
1589:
1542:
1471:
1429:
1057:
975:
968:Tinkering with Graphs
1058:Participation at RfA
1431:
1060:
978:
1583:
1513:
1465:
1329:
1262:
1226:User:E/AdminStats
1217:
1186:
1145:
1083:
990:
942:
898:
804:
786:
782:
748:
729:
692:
626:
590:
575:
539:
432:
391:
364:
342:
305:
115:
114:
83:
82:
1658:
1629:
1624:
1597:
1579:
1550:
1533:
1528:
1509:
1479:
1461:
1445:
1440:
1412:
1407:
1384:
1379:
1378:
1348:
1343:
1325:
1304:
1292:
1280:
1258:
1239:
1234:
1213:
1204:updated list at
1182:
1164:
1159:
1141:
1117:
1112:
1079:
1019:
986:
938:
894:
828:with analysis.
825:
821:
820:
800:
787:
784:
780:
744:
719:
688:
678:
674:
673:
659:
653:
644:
639:
622:
602:Tally Assistance
586:
571:
538:
536:
525:
428:
387:
354:
338:
301:
93:
85:
30:
29:
1666:
1665:
1661:
1660:
1659:
1657:
1656:
1655:
1627:
1622:
1598:
1595:
1551:
1548:
1531:
1526:
1480:
1477:
1443:
1438:
1410:
1405:
1382:
1376:
1375:
1346:
1341:
1308:
1305:
1296:
1293:
1284:
1281:
1237:
1232:
1198:
1162:
1157:
1115:
1110:
1017:
970:
908:
867:
865:We're finished!
827:
826:
818:
816:
778:
671:
669:
662:
657:
651:
642:
637:
604:
558:
534:
526:
516:
474:
472:Opening this up
451:
415:
326:
257:
194:
151:
120:
98:
33:A Review of the
26:
25:
24:
12:
11:
5:
1664:
1654:
1653:
1652:
1651:
1593:
1588:
1587:
1554:That's a big "
1546:
1541:
1540:
1518:
1517:
1475:
1470:
1469:
1424:
1423:
1422:
1421:
1420:
1419:
1393:
1392:
1391:
1390:
1356:
1355:
1310:
1309:
1306:
1299:
1297:
1294:
1287:
1285:
1282:
1275:
1269:
1268:
1267:
1266:
1247:
1246:
1197:
1194:
1193:
1192:
1191:
1190:
1133:
1132:
1131:
1130:
1129:
1128:
1127:
1126:
1125:
1124:
1094:
1093:
1092:
1091:
1090:
1089:
1088:
1087:
1052:
1051:
1050:
1049:
1048:
1047:
969:
966:
965:
964:
963:
962:
907:
904:
903:
902:
866:
863:
862:
861:
815:
814:
771:
770:
769:
768:
767:
766:
734:
733:
667:
666:
648:
603:
600:
599:
598:
597:
596:
595:
594:
579:
556:
514:
473:
470:
469:
468:
467:
466:
465:
464:
463:
462:
461:
460:
459:
458:
457:
456:
449:
413:
324:
294:
293:
287:
281:
271:
270:
269:
268:
267:
266:
265:
264:
263:
262:
255:
232:
231:
230:
229:
228:
227:
226:
225:
204:
203:
202:
201:
200:
199:
192:
179:Question phase
157:
156:
149:
119:
116:
113:
112:
111:
110:
105:
99:
94:
88:
81:
80:
79:
78:
73:
68:
58:
53:
48:
40:
39:
34:
15:
9:
6:
4:
3:
2:
1663:
1650:
1646:
1642:
1637:
1636:
1635:
1632:
1631:
1630:
1625:
1616:
1615:
1614:
1613:
1609:
1605:
1592:
1586:
1582:
1577:
1572:
1571:
1570:
1569:
1565:
1561:
1557:
1545:
1539:
1536:
1535:
1534:
1529:
1520:
1519:
1516:
1512:
1507:
1502:
1498:
1497:
1496:
1495:
1491:
1487:
1474:
1468:
1464:
1459:
1454:
1453:
1452:
1451:
1448:
1447:
1446:
1441:
1428:
1418:
1415:
1414:
1413:
1408:
1399:
1398:
1397:
1396:
1395:
1394:
1389:
1388:
1385:
1380:
1370:
1366:
1360:
1359:
1358:
1357:
1354:
1351:
1350:
1349:
1344:
1335:
1334:
1333:
1332:
1328:
1323:
1319:
1315:
1303:
1298:
1291:
1286:
1279:
1274:
1273:
1272:
1265:
1261:
1256:
1251:
1250:
1249:
1248:
1245:
1242:
1241:
1240:
1235:
1227:
1223:
1222:
1221:
1220:
1216:
1211:
1207:
1203:
1202:User:Rick Bot
1189:
1185:
1180:
1176:
1172:
1171:
1170:
1167:
1166:
1165:
1160:
1151:
1150:
1149:
1148:
1144:
1139:
1123:
1120:
1119:
1118:
1113:
1104:
1103:
1102:
1101:
1100:
1099:
1098:
1097:
1096:
1095:
1086:
1082:
1077:
1073:
1068:
1067:
1066:
1065:
1064:
1063:
1062:
1061:
1056:
1046:
1043:
1042:
1038:
1037:
1032:
1031:
1030:
1027:
1026:
1025:
1021:
1020:
1013:
1012:
1011:
1008:
1007:
1003:
1002:
996:
995:
994:
993:
989:
984:
974:
961:
958:
957:
953:
952:
947:
946:
945:
941:
936:
931:
930:
929:
928:
925:
924:
920:
919:
913:
910:On range 30,
901:
897:
892:
887:
883:
882:
881:
880:
876:
872:
860:
856:
852:
848:
847:
846:
845:
842:
841:
837:
836:
831:
824:
812:
808:
807:
803:
798:
792:
791:
788:
775:
765:
761:
757:
753:
752:
751:
747:
742:
738:
737:
736:
735:
732:
727:
723:
718:
717:
712:
711:
710:
709:
705:
701:
696:
695:
691:
686:
682:
677:
665:
660:
654:
647:
646:
645:
640:
632:
631:
630:
629:
625:
620:
615:
613:
608:
593:
589:
584:
580:
578:
574:
569:
564:
563:
562:
559:
554:
552:
551:
550:
544:
543:
542:
537:
531:
530:
523:
522:
521:
520:
517:
512:
510:
509:
508:
501:
499:
495:
491:
487:
483:
478:
455:
452:
447:
445:
444:
443:
437:
436:
435:
431:
426:
421:
420:
419:
416:
411:
409:
408:
407:
401:
396:
395:
394:
390:
385:
381:
377:
373:
369:
368:
367:
362:
358:
353:
352:
347:
346:
345:
341:
336:
332:
331:
330:
327:
322:
320:
319:
318:
311:
310:
309:
308:
304:
299:
291:
288:
285:
282:
279:
276:
275:
274:
261:
258:
253:
251:
250:
249:
242:
241:
240:
239:
238:
237:
236:
235:
234:
233:
224:
220:
216:
215:Phil Sandifer
212:
211:
210:
209:
208:
207:
206:
205:
198:
195:
190:
188:
187:
186:
180:
175:
174:
173:
169:
165:
164:Phil Sandifer
161:
160:
159:
158:
155:
152:
147:
145:
144:
143:
136:
135:
134:
133:
129:
125:
124:Phil Sandifer
109:
106:
104:
101:
100:
97:
92:
87:
86:
77:
74:
72:
69:
66:
62:
59:
57:
54:
52:
49:
47:
44:
43:
42:
41:
37:
32:
31:
23:
19:
1620:
1619:
1600:
1590:
1576:UltraExactZZ
1555:
1553:
1549:UltraExactZZ
1543:
1524:
1523:
1506:UltraExactZZ
1500:
1482:
1472:
1458:UltraExactZZ
1436:
1435:
1432:
1403:
1402:
1371:
1367:
1363:
1339:
1338:
1322:UltraExactZZ
1316:, including
1311:
1283:Total Admins
1270:
1255:UltraExactZZ
1230:
1229:
1210:UltraExactZZ
1199:
1179:UltraExactZZ
1155:
1154:
1138:UltraExactZZ
1134:
1108:
1107:
1076:UltraExactZZ
1071:
1040:
1035:
1024:
1022:
1015:
1005:
1000:
983:UltraExactZZ
979:
955:
950:
935:UltraExactZZ
922:
917:
909:
891:UltraExactZZ
885:
868:
839:
834:
830:UltraExactZZ
822:
809:
797:UltraExactZZ
793:
773:
772:
741:UltraExactZZ
715:
697:
685:UltraExactZZ
675:
668:
635:
634:
619:UltraExactZZ
616:
609:
605:
583:UltraExactZZ
568:UltraExactZZ
548:
546:
528:
506:
504:
502:
498:UltraExactZZ
479:
475:
441:
439:
425:UltraExactZZ
405:
403:
384:UltraExactZZ
350:
335:UltraExactZZ
316:
314:
298:UltraExactZZ
295:
289:
283:
277:
272:
247:
245:
184:
182:
141:
139:
121:
107:
95:
103:Pre-reflect
1377:DDStretch
1369:decreased"
1018:Balloonman
290:34 editors
284:56 editors
278:77 editors
118:Reflection
51:Discussion
494:WP:RREV/R
71:Recommend
1596:Gazimoff
1581:Evidence
1511:Evidence
1478:Gazimoff
1463:Evidence
1327:Evidence
1260:Evidence
1215:Evidence
1184:Evidence
1143:Evidence
1081:Evidence
1036:lifebaka
1001:lifebaka
988:Evidence
951:lifebaka
940:Evidence
933:example.
918:lifebaka
906:Range 30
896:Evidence
835:lifebaka
802:Evidence
781:HEFFIELD
746:Evidence
726:contribs
716:lifebaka
690:Evidence
624:Evidence
588:Evidence
573:Evidence
549:Gazimoff
507:Gazimoff
442:Gazimoff
430:Evidence
406:Gazimoff
389:Evidence
361:Contribs
351:lifebaka
340:Evidence
317:Gazimoff
303:Evidence
248:Gazimoff
185:Gazimoff
142:Gazimoff
56:Question
46:Overview
20: |
1072:think I
871:Livitup
851:Useight
811:Livitup
756:Useight
700:Livitup
108:Reflect
96:Archive
76:Collate
61:Reflect
38:Process
22:Archive
1501:really
1383:(talk)
658:review
652:mentor
1206:WP:LA
912:Tony1
535:Chat
529:Pedro
65:stats
16:<
1645:talk
1628:moff
1623:Gazi
1608:talk
1564:talk
1532:moff
1527:Gazi
1490:talk
1444:moff
1439:Gazi
1411:moff
1406:Gazi
1347:moff
1342:Gazi
1238:moff
1233:Gazi
1163:moff
1158:Gazi
1116:moff
1111:Gazi
875:talk
855:talk
823:Done
785:TEEL
760:talk
722:talk
704:talk
676:Done
643:moff
638:Gazi
557:Read
515:Read
450:Read
414:Read
357:Talk
325:Read
256:Read
219:talk
193:Read
168:talk
150:Read
128:talk
1641:Axl
1604:Axl
1560:Axl
1486:Axl
886:209
1647:)
1610:)
1594:—
1566:)
1556:If
1547:—
1492:)
1476:—
1041:++
1006:++
956:++
923:++
877:)
857:)
840:++
762:)
724:-
706:)
532::
359:-
221:)
170:)
130:)
1643:(
1606:(
1578:~
1562:(
1508:~
1488:(
1460:~
1324:~
1257:~
1212:~
1181:~
1140:~
1078:~
985:~
937:~
893:~
873:(
853:(
799:~
783:S
779:S
774:m
758:(
743:~
728:)
720:(
702:(
687:~
661:)
655:/
649:(
621:~
585:~
570:~
427:~
386:~
363:)
355:(
337:~
300:~
217:(
166:(
126:(
67:)
63:(
Text is available under the Creative Commons Attribution-ShareAlike License. Additional terms may apply.
