Knowledge (XXG) talk:Pending changes/Request for Comment February 2011

1289:

its continued use determined for the future, we are taking a break from using it. Perhaps a break in the wide public discussion is a good idea and we can have some talk page discussions while developing a proposal at a somewhat less public page (though equally accessible), and I of course want in on that project. Cenarium's timeframe of a compromise proposal for August gives us a few months to work out the flaws in the system, and both supporters and opposers alike who have an interest can help develop a proposal. I would have said two months is enough, giving July, but I realize there are only a few days after two months from right now and it's August, so I do think trying to propose again in August is viable. However, whatever led to the trial not having a proper ending before (I recall it was still being newly added to articles in April, in fact) shouldn't occur again, and I would hope a clause for continuing it past September where it seems to be the best solution on a per page analysis be permitted in certain cases. perhaps including the two pages that Scott was so concerned about. Of course, if pending changes works much better this time around, it may not be necessary to do this and we can have it finally implemented fully. As for the way to do the future trial, I'm open to suggestions.

1190:

to each other in much the same way a music discography moves through albums in order via an album's infobox. We can rename pages later if we need to in order to eliminate the redundant title (it's now May, not February). As for where to go from here: if we take a break as opposers to PC above have stated, that will merely support their view that PC should not and cannot be implemented. The best thing to do now is to seek a way forward. In other words, we should take all the guidelines and evaluate them. Clearly a new page is required for this task. After we get guidelines that everyone involved can agree with (if that's even possible), we can propose it to the community. Perhaps that will give those not as invested a chance to stop thinking about it and approach it with a fresh perspective. Don't get me wrong; I will always support PC, because I have seen it work. We just need to ensure we have a better system for using it as there were things that I also found needed changing.

3455:

question. THAT I disagree with. Whether people like it or not, at some point, there will be another PC. It's one of those things that won't go away. And until it's decided how we're going to go about gathering reviewers for that new PC run, there's no point hurriedly rushing to remove the reviewer flag from those who already have it. What if we did that and PC were then turned back on on 10,000 articles tomorrow? Admins. would go crazy with no reviewers to help out. Granted, this situation is extremely unlikely, as we've been discussing on this page how to pick reviewers for the next cycle; that is, an application procedure or reviewing existing reviewers. It's easiest to pick out existing reviewers if we leave the flag in place. So while that option is on the table, is there really any harm in leaving the flag where it is?

3427:

came along and gave me the userright, I did for a second think I had been recognized for something, but on reading, no; it was merely to help test out a new feature being considered for Knowledge (XXG). I could have said no and gone about my daily life. But I didn't, I said yes. Not for the "bauble", not because I thought it gave me some sort of prestige, but because I knew it would give me a chance to do two things: try out a new feature and also do something good for the encyclopedia by joining the fight against vandals. Did I do both? Oh yeah. Do I now see this "reviewer" tag as anything more than a piece of text that means absolutely nothing? Hell no. However, without more context, I don't follow the point of your post above, so I'll just conclude that you were merely disagreeing with the candy comment.

828:, it would seem that Level 2 protection added to semi-protection would provide enough defense against similar attacks. If Bambifan were to use the same technique, he'd be free to edit, but they wouldn't be visible until a reviewer-equipped editor checked the work, increasing his chance of exposure and being blocked when his pattern is recognized. Similarly, the amount of time needed to build up confidence from an admin to add reviewer rights to his account (and thus permit unlimited carnage until he were blocked again) might be so long that he simply gets bored with waiting and decides to, basically, go and bug someone else. 2353:

responsible people. Absent that, the intent of using PC to aid our BLP policy will be made a mockery by mindless acceptance of edits. Since, as of today, the reviewer flag confers absolutely nothing, and it won't until such time as PC comes back, my advice would be to go back to being boring here. In other words, removing the flag is a solution in search of a problem (for now). But, and this is important, proposals for PC rebirth are going to have to have a clear plan as to who will or will not be able to review pending edits, and the qualifications are going to have to take into account a serious regard for BLP concerns.

583:

community has become too tired of PC for now, we need to wait for a while. The proposal was to remove PC, there was no exception, the extent of the closer's discretion does not include any line-item veto. The plan had always been for admins to use their discretion in the transition with all due regards to article and protection specifics and in accordance with the protection policy. This situation escalated because of one admin who didn't want to hear consensus. It is high time to put an end to this and get on with business as usual; and when enough time will have passed, we'll be able to reconsider the use PC.

2359:

to request to be reviewers, with the right determined by administrators (as rollback is). In this case, users who are to be made reviewers must (1) have a degree of trust as editors comparable to what we expect of rollbackers, and (2) demonstrate, further, an understanding of BLP (we will need to figure out how exactly that understanding would be demonstrated). No one should be made a reviewer unless they ask to be (a big difference from what happened before!). There also needs to be a mechanism for removal of reviewer rights when those rights are misused. --

1351:, or reviewing AfDs, and so on. I'm not saying it's right, I'm just saying that if another trial were to be proposed, it must be clear who is going to be in charge of removing it when it's over; in other words, oversee the trial. If a trial is not preferred even with such guarantees, then yes, we must seek a way to allow PC to be turned on permanently. Failing to do so lets down the community, especially when sensitive BLP articles are unable to take advantage of it. What BLP will next appear in 68: 368:

proposal will be refined and discussed and after that break/discussion/proposal tweak a final accept or reject proposal can be presented for RFC. I am also hopeful that the accept or reject RFC on usage will gain only comments as to the value or lack of value of the tool through users experience and/or usage of the tool and not users thoughts and opinions as to the trial. As in - RFC - please comment on the tool and not the trial.

31: 816:. These articles have been, in many cases, placed on indefinite semi-protection due to his activities, but this latest assault showed a new technique that semi-protection couldn't block. An anon IP (quite possibly Bambifan himself) made innocuous edits to these articles, which the new Bambifan sock (created 5 days earlier, but with no activity) would then revert, boosting his edit count to the point where he would reach 123: 2967:'lesser' right) just so there will be a 'skeleton crew' in case of reactivation. New reviewers should have to be picked based on new guidelines if ever, and anyone wishing to regain the right reapply for it (and I favor stricter rules for choosing reviewers given the sensitive nature of their responsibilities). I'm still hoping to see a workable version of PC implemented that is 3549:, let alone what standards they must follow, contributed to the last test's failure. I would say, strip the reviewer rights now, and then, if there is a future !vote that leads to some future trial, allow all the voters to have the right, unless you formally adopt more restrictive standards on who should be allowed to have it before conducting that vote. 391:

a full month, that it be commenced quite shortly. If we wait until late June, the RfC will be a bit of a flop by any standards of seeking participation. Let's get it started - it will not be over until nearly the end of June in any case. Again, I ask that you do the honours. "If 'twere done when 'tis done, 'tis well, It were done quickly." Cheers.

1955:

which came up in discussions during a period that Knowledge (XXG) sought donations. Having less on this page reduces server load on this page, and PC has taken more than its fair share of server load in three months of discussions. Let's properly archive Phase 3 like the others, then those interested in seeing further information can do so.

201:

exception, to routinely substitute PC for semiprotection. On the other hand, there still seem to be people who think that it would be better for a handful of articles to be full-protected than for them to be on a PC status. If that is consensus, so be it, but it still strikes me as odd and I would still welcome someone's explaining it.

3174:

testing cycles on it, including one in July (and sporadically over the two months if I saw something obvious), but because I was usually one of multiple editors to reach a PC edit, I often ended up being behind another editor, so it might not show as 50 for me and I would hate not being given a chance to test it again. =)

3346:

see that you aren't a reviewer (or rollbacker), so I've made you one." And this on the talk page of a user who is seriously disruptive, with warnings and such in plain view above and below, and I've seen it multiple times. I certainly don't mean to impugn everyone who was made a reviewer without asking to be one. --

180:

but I was concerned that to a certain extent it might also reflect that the RfC closure and my request for additional input was underpublicized. I am also concerned that the latter situation still has not been addressed (although I do not anticipate using this as a basis for extending the deadline another time).

1171:. OK, so there has been a little more organisation to it than that, but do you see what I mean? Perhaps if we admitted that we can't be massively organised that would also help. PC has had many attempts to structure the discussion, which have got so far before it starts to look like a bit like chaos. 1100:- any improvements welcome... actually I think there is no need for the pural as we have already got got quite close to a proposal and although we are going to discuss and tweak , there is only going to be one actual proposal. - I also removed future - do we need that - its just a proposal for usage..? 265:- There is no requirement for a break of any kind. In fact I see a six month break request as simply turning this unconditional to future use end of trial into a never for ever situation. IMO we should get this over with - lay out what there is possible consensus for and poll it in the near future - to 3194:

You know, all the worry about people "misusing" PC has me a bit mystified. I've never seen a diff of an actual, obvious problem. I've seen things that were approved (as not vandalism) and then reverted (as good-faith efforts that didn't improve the article), but that was the recommended (though not

2921:

mabdul, your comment confuses me. It sounds like you are referring to two accounts that are socks reviewing each others' edits; this would not work, they would eventually be caught. Malleus, are you saying in your comment near the start of this chain that people should not have the rollback right?

2792:

Actually, my argument makes perfect sense, though my way of stating it was a little opaque. Essentially, why take the right from responsible users (rollbackers and autoreviewers) when the program is likely to have a retrial anyway, thus creating pointless admin work to give it back. Having a skeleton

2677:

But your argument is flawed in that it is based purely on following bureaucratic procedure. Knowledge (XXG) is not an Anarchy, or a Bureaucracy. And remember, rollback is given only to trusted users, so why should we assume that their reviews would be anything less than acceptable? 00:52, 8 June 2011

1189:

in the same way the other two were created. Right now, it redirects to the project page for this talk page. When we archive this, move the whole damn thing to that location (first deleting the redirect if necessary). Then, if necessary, we could rename the two appropriately and make sure they link

616:

being used to hold another RfC. That RfC was about removing PC from current pages without prejudice against restarting it later if the consensus is to do so. Most of the comments in that RfC were about continuing a trial without consensus. A new RfC for something else entirely should have a fresh new

3511:

version of the software was put into place. I don't understand any logical reason for a person to hold a "button" that had no "function". If someone held such an ability during the "trial", and can point to being competent in it's use, then fine .. by all means feel free to mention the fact at any

3248:

Getting back to that suggestion about people who made more than a certain number of past reviews, a problem to be careful of is that there may have been people who made large numbers of reviews, but did so contrary to the guidelines (such as they were), as in accepting or rejecting indiscriminately.

2988:

If memory serves, admins don't have the reviewer userright, just like they don't have the rollbacker userright, because it's automagically part of the admin bits. (And that reminds me: I turned off rollback in Twinkle last week, but it came back to haunt me again. I've got to go figure out what's

2358:

Yaris, very sensibly, has asked here for calm suggestions about how to, in effect, formulate such a plan. My suggestion: when PC comes back, all reviewer flags get removed at the start (otherwise, there will simply be too many "children" to weed out), and we set up, as last time, a process for users

1317:

I support seeking a consensus to turn PC (possibly with modifications) back on for good. I strongly oppose any further trials. There is zero reason for anyone to believe that this or any other trial will end when promised. Nobody in authority has stepped up to the plate and announced that allowing a

1273:

Let's take a break. We'll see clearer on how to proceed after a while and the community is too tired of discussing PC at the moment. We'll also have less active editors in July/August. So I'd suggest to prepare a compromise proposal with usage policy in August-September, and a community consultation

883:

itself hasn't been one of them directly) but are not admins from editing as well, and increasing the workload on admins who would have to respond to edit requests from trusted editors. Again, this is such a narrow, easily-defined category in which to test this application of pending changes — it's a

390:

that we wait any set period of time - ndeed he noted that some might like a short break. If we do not resolve this shortly, we will enter an exceedingly quiet time historically for Knowledge (XXG) (from late June through August, many folks disappear) and so I would suggest that since an RfC runs for

3544:

the right. Additionally, there have been some people purged from having the right for reasons that I don't think should be permitted in any formal roll-out, and so I'm not sure the selection of people holding it now is truly representative. Above all, the lack of agreement (or even understanding)

3283:

I like the latter idea better. I do think it should be an admin., or someone trustworthy who is appointed by an admin., who does these reviews of current reviewers. If we do an application process, it will turn into a huge game of wonkery and, also, some good people currently flagged as reviewers

3173:

I would add one more exception: users who have been active, either for or against, in these discussions regarding PC and have an interest one way or another in what happens to it. That way, if it gets trialed again, those interested users can also keep testing. I know I spent at least three solid

2960:

Any new implementations of PC will probably be substantially different from the trial version. As such, the trial version's method of picking reviewers will not apply. The users selected were screened far less comprehensively given that expanding the experimental group (quantity over quality) still

2664:

The flaw in your argument is that you believe without proof that Rollbackers and so on did indeed do "many good reviews", just because they had some other unassociated user right(s). I could review all of you reviewers to Hell and back, but I don't want your shiny baubles. Ajraddatz is quite right.

2457:

remove it", this isn't that uncommon in the real world; some places are strewn with families who retain meaningless titles of some kind just because there's nothing to be gained by removing them, but if the titles were to be given some kind of authority they'd be thoroughly winnowed. (If the UK for

2217:

Having a reasonable group of users with the power on day one means that you can move over a reasonable number of articles to pending changes on day one without having to rush people through approval, or creating a backlog, or having to be extremely conservative about how many articles you add it to

1954:

Frankly, I'm not happy with it. I would ask rather if SlimVirgin has any reason why the discussion below should NOT be archived. If we're summarizing two phases of the RfC and linking out, then all three should be treated the same way. It also helps from a server load time perspective, something

1288:

I should further clarify my above post. I do not want to take a break from developing PC into something that the community can widely accept. I do note that an end has been brought to usage of PC, however, for the time being, thus forcing a break in usage of PC. While there is no clear method of

859:

I fight sockpuppetry as my primary activity, and think that Bambifan101's obsession with "The Fox and the Hound" constitutes an extreme corner case that would be hard to base policy on. I had taken the unusual step of long-term full-protection on the article, which was overriden and reduced to PC.

204:

9. Regarding where the discussion goes from here, I'd still welcome thoughts on whether my outline for the next wave of RfCs is helpful or not, or what might do better. I also note NuclearWarfare's suggestion that we take a break before the next round of discussion; but others seem to be saying the

179:

5. I am keenly aware that in the two weeks of input on the original closure, no one came to this page suggesting a specific BLP on which continued protection might have been warranted. To a large extent, this may reflect consensus that the current version of PC is not a good solution to BLP issues,

171:

3. Given that the task of carefully evaluating the articles that were still under PC as of Friday had obviously not been completed, I see nothing controversial in my extending the deadline by a week. The alternative would have been simply to remove the PC on all the remaining articles by pressing a

167:

2. Any implication that either my original closing or my additions to it on Friday were affected by lobbying by Jimbo Wales, the Foundation, or other arbitrators, is completely unfounded. There has been no such lobbying of any kind. In addition, my closure here has nothing to do with my arbitration

3426:

Malleus, I do not agree with your analogy. I am not a native, first off; I am a valued (more or less) contributor to this Wiki. I do not collect baubles, for I see little point in them (unless they could be converted to Canadian dollars, in which case I'd find them interesting). When Courcelles

3345:

CycloneGU, that's very reasonable, and makes me realize that I should clarify what I said, sorry. I've noticed, from time to time, that I have gone to talk pages of disruptive users and been dismayed to see a thread saying something like: "Gee, I've looked at your contributions and am surprised to

3060:

Having a somewhat experienced "skeleton" crew of past reviewers who have demonstrated competence with the previous use of the PC trial and then weeding out the "unskilled" ones — that middle line seems all fine and dandy — but then we also have to take into account the possibility that the pending

2966:

I do not support keeping the current reviewers as default to be carried over any new implementations. Though I do somewhat support the idea that reviewers who are already rollbackers (or admins perhaps? editors who are already somewhat trusted to do the right thing) retain the reviewer right (as a

2893:

Remove the rights! What happens if (and some propose) PC get a new trial, then the interface and the policy will be likely changed and maybe totally different! The (old) reviewer have to read the policy new. Maybe the bar will also be higher than it was actual in the last trial. What happens, if a

1821:

Perhaps all we need to do to address my concerns about loosing the other phases is to expand on the ambox currently summarising the RfC at the top of the page. I think that the endorsement of positions thing has a lot of valuable stuff in it that people might not realise is there if they see "The

567:

restrictive. I asked above why anyone would prefer to see a group of articles full-protected than on PC; no one responded directly, but I gather the concern is that the PC designation would be overused. But if we could all agree on criteria (such as those I embodied in my suggestion Friday night),

367:

I though there was some crossed purposes commenting there. As for the break - Perhaps, I am looking at around one month discussion to tweak and present the proposal which is not so straight away as to have a chilling effect, at least I don't think so. At the most, a six week break during which the

269:

for months would simply make all the discussion and consideration of the last months stale and wasted. The trial has been ended as requested and we have discussed and considered for months, we now know exactly how the tool works and where it is beneficial and what we expect of reviewers and who to

246:

Second that. A break will give everyone time to calm down and think about what is the best way to proceed. I would also suggest that when this comes up again a better title be chosen than "Request for Comment February 2011" and that the location of the new discussion be publicized with a notice on

3454:

I have not argued that, as of right now, the "reviewer" flag (I don't consider it a "right") is useless. I can't use it in any way to have some kind of editing privilege at this present time. However, I believe the substance of your argument is that it should be taken away from everyone without

3330:

I happen to have had a piece of candy handed to me. Is that so bad? It turns out that decision wasn't entirely disasterous, either...an admin. saw edits of mine somewhere, determined I was a competent user, and invited me to test the feature. I tested, liked it, and have supported it since. I

2352:

And to think I was just about to un-watchlist this page in the belief that it had stopped being interesting! I think, indeed, that the reviewer flag was given out far too casually last time (not to me, of course!), and any reinstatement of PC will require that the people who can make decisions be

1857:

Agree. Another thing to consider is that, at times, the discussion bounced back and forth between project and talk page, with no clear delineation between the two. Late in the game, some discussion was moved onto a talk page, but I was looking back through histories and archives the other day and

878:

While maybe not enough to create policy (just yet), that's precisely why PC2+Semi should be tried on a limited basis, to see if it does protect against such vandals. Yes, full-protection would indeed eliminate them, but it also would prevent editors who are working to improve the article (such as

634:

perhaps doesn't have the best title but it has happened in three phases, only the last of which relates to removing PC without prejudice against restarting it later. That was seen as a side issue that had to be dealt with before returning to the other issues of pending changes. I don't think we

558:

Any article can be protected from inappropriate edits by full page protection; the problem is that the article is then "protected" from good edits as well, since relatively few editors (and no new editors) will go to the trouble of making an edit request (or even know how to do it). Here's what I

509:

If there is something I am considering changing in my own proposal it is the use of the term "BLP-related". You could argue that it should be considered for any article subject to attack by sleeper accounts, which is bordering on consideration for full-protection... its just that the majority of

200:

8. On the merits of the issue, I gather the reason there is strong opposition to even a limited BLP exception to ending the trial (other than repeated chants of "the trial is over! the trial is over!") is fear that it would be overutilized. I agree that it would not be in order, under any form of

191:

7. "BLP" is not a catchphrase that, by intoning it, automatically supersedes all our policies, norms, and community decision-making. On the other hand, the group of issues that we collectively categorize as "BLP" go beyond the internal dynamics and politics of our project, because the contents of

175:

4. It appears that administrators are now in the final phase of reviewing the remaining articles under PC and evaluating whether no protection, semiprotection, or (hopefully in rare cases) full protection is appropriate for each. I trust that this can be completed by this coming Friday so that we

2925:

Meanwhile, my opinion; it's useless now. Once we're ready to move forward with PC again (where are the discussions of the trial's policies that need to be fleshed out, BTW?), we can do a review of the userright and where it should be removed. I agree reviewers should have a higher standard for

597:

Pretty much ditto with Cenarium (presuming that I'm not the "one admin" he refers to). We'll have to wait a while. I think it's a shame that this botched trial prevented a defective but promising feature that needed some revision from ever getting revised into something worthwhile. In a while, a

352:

Sithman, TelCoNaSpVe, I'm pretty sure that Newyorkbrad is talking about a break after removal of PC and before seeking consensus to reinstate it, not about keeping PC on any articles during the break. Off2riorob, if we jump right back into discussion without a cooling off period, there is a good

2155:

I don't think there's any advantage to doing this. While PC is not in use, the right is useless, but harmless. However, if you remove it now, and PC is adopted for regular use later (which seems likely to me), then you create a bunch of needless make-work for admins. I'd view it as a pointy,

1919:

Phase 3 should be permanently archived at Archive 3. The first two phases are archived at Archive 1 and Archive 2 already, and keeping Phase 3 on the main RFC page gives it more prominence than the first two phases. Closure should be the thing getting the most prominence, then the rest can be

582:

This is well known of all, but the community rejected PC nonetheless. If you want some 'exceptions' then you will need to have the whole debate started anew, which policy, which standards, which articles, etc, and get consensus for it. I estimate the chance of success at the moment to zero, the

482:

Brad said "We might want to allow a limited exception to terminating the trial" not "There will be a limited exception to terminating the trial". He has also asked for comments on the idea. If there was a fault, it was that the idea wasn't expressed in concrete-enough terms, hence most people

2328:

to review. Unless we somehow archive who were the reviewers before complete removal, we lose that information and perhaps make somebody do a lot of work to restore it, if that's the ultimate decision. So, I'm leaning towards option 2 in the long term, but option 3 might make sense for now — PC

722:

Also - I'm confused, what is happening here, NY Brad. Is the 'closure' of the RfC finished with? It doesn't seem over. In which case, surely, you shouldn't be putting forward your opinions on the actual debate (until after it is closed, and we can move on to fresh discussion, fresh proposals).

3398:

I don't think your candy analogy works. I've never been a reviewer and I never wanted to be a reviewer, largely because I saw the process as handing out baubles to win over the natives, the overwhelming majority of whom were actually having a right removed. And baubles, just like the reviewer

3249:

The more I think about this, the more I think that no one should be kept from before. Instead, better guidelines for reviewing need to be worked out first. Then would-be reviewers can apply (or re-apply), and the trial shouldn't be started until there are enough of them. First things first. --

3042:

A note of interest; I gained the rollback userright after being given the reviewer userright. I'm sure others had this order, as well. This came about during my effort to get the Australian PM's article (Julia something) semi-protected on the day she won the nomination due to an increase in

2469:

It was ill-considered and poorly implemented if that's what you mean. But we are already seeing these (in this case inactive) rights touted as a reason to trust an editor at RfA for instance. Removing this one may go a small way to restoring some sanity in that god-forsaken slough of despond.

831:

Bambifan is hardly the only persistent sockpuppeteer on the project, so perhaps this combination defense (semi-protection plus Level 2 pending) may be useful for articles that are targets of such characters but also have a cadre of diligent editors who are not admins, and thus couldn't edit a

3506:

While I can envision some sort of PC in the future, I'd have to imagine that it would be quite different than the "trial" that recently concluded. As such, anyone who would want such "rights" or rather "privileges" for any new version should be required to show an understanding of whatever

3150:

total removal from all but admins and instead recommend removing it from all but those who did more than some arbitrary number of reviews )for example 50). That should cut down on the admin workload if another trial is approved (and one probably will be approved, whether consensus based, or

183:

6. On the other hand, at least one of our administrators with an enormous amount of experience in dealing with sensitive BLP issues opined on his talkpage that there indeed are serially vandalized BLP articles on which PC should continue to be used, and where neither semiprotection nor full

1839:

That would be fine with me. My concern throughout this trial was that there were so many pages that discussions got lost, so there was no sense of continuity or progress. We all seemed to be saying the same things over and over. Providing links to it all in one place would be very helpful.

2213:

The reason I've suggested letting people with rollback keep the right is because I think that its highly likely pending changes will be implemented in some form, even if that's just for articles which would otherwise have to be indefinitely semi/fully protected. So removing it from users

459:

If you - or anyone - would like to propose it, then propose it. Seek consensus. The problem here is, 'consensus' is being invented, instead of sought. (No offence intended; of course, comments are welcome. I'm just trying to emphasize - any such proposals to use PC are...well, proposals)

188:). To my dismay, this admin opined that my closure discussion was too long to read, and he declined to come to this page to present his opinion, which therefore was not responded to by others who have strongly opposing views. I did not, however, think it made sense simply to ignore it. 223:

I agree completely with NW. We need a break with PC for some time, the community has become really tired of it. Let's just apply the arbcom injunction blindly, then see which protection level is needed for articles with all due regard to the article specifics and in accordance with

2452:

The disaster was primarily due to flaws in the software which meant it couldn't cope with the high traffic pages for which it was intended. It's entirely possible someone will come up with a version that works. Regarding "leave the right in place until it's activated again and

2793:

crew of reviewers ready also makes a retrial logistically simpler, as there is no need to hurriedly create several hundred reviewers. And why would someone need rollback? Well, it is absolutely essential for effective vandal control for starters. So please tell me how any of

2221:

Unless there is some good reason why rollback users won't be generally trusted with review powers there doesn't seem any reason to take it away from them, taking it away from other users is a simple was to allay the fear that it may have been handed out inappropriately. --

2182:

Can you guess how I view your opposition to the removal of a right that no longer exists in practice? I'll give you a clue; none of the words consist of more than four letters except for an odd "-ing" to help ease the flow. How desperately some fight to keep such "rights".

954:

Yes - PC is unable to be requested at all - the trial is over. Users that support the tool for some kind of ongoing usage can help to lay out the definitions for its usage over the next couple of weeks and get their hands out of their pockets and support its accepted use.

196:

whether there might be consensus for a narrow exception to the existing consensus to end the PC trial that my original closure had recognized. At the moment, it certainly appears that the answer will probably be no, but I make absolutely no apology for asking the question.

2771:

Ronk, I believe that Malleus was attempting to point out how your argument makes no sense and has little relevance to this discussion. For one thing, how does rollback = reviewer? If that were the case, wouldn't the reviewer rights be in the rollback group? Also, why does

3481:

PC has too much support for it to be "absolutely impossible" to suggest again, Malleus, even with the nature of the trial and Scott Mac's behavior post-trial. I suspect we'll be seeing a suggestion virtually similar with what got rejected in about a year or 18 months.

1346:

TBH, I think the reason it went on - and on, and on, and on - is because no one bothered to do the work to remove PC from everywhere on August 16. It wasn't causing any damage and there were better and more important things to do, like modifications to an article on

2288:

I can see why you might want to start with a clean sheet, but I can also see a case for evolution rather than revolution. Either way, there is potential for drama on the issue. Let's try to calmly state the reasons for and against the idea before starting an RfC.

3512:

RfA (or future request for some permission). My car has an automatic transmission, so why would I want to have a "clutch peddle" installed sort of thing. There is no use for the "rights", remove the superfluous fluff from project. It's not a degrading insult to

2541:

Ditto, Seb. I don't see any reason to remove reviewer rights from anyone when PC is (at present) only disabled, not rejected. If the last poll on it was the final word on it, so to speak, I'd support (as the userright would be deprecated) but that isn't the case.

2840:

I saw "reviewers" let edits through that should have been undone (by rollback), so I'm not really comfortable with the notion that all "rollbackers" should automatically have "reviewer" - and that's even assuming the "reviewer" right was re-enabled in some form.

2714:

I'm sorry that you feel that way, perhaps this kind of behavior explains your many blocks, and failed RfA's. There is no reason to stoop to ad homenim attacks in a discussion like this, it simply points to the weakness of your argument, and your debating skills.

3061:

changes software itself might be radically different from what it is now. Which includes, of course, possible modifications to the reviewer right itself, as well as the ability to editorially sight revisions to any particular page and access to the interface at

3065:. All the past reviewers, then, will be frozen in time believing that this would be the same as the old system, when in fact a new system of PC has been introduced, and there would no longer be any reviewers "experienced" with this hypothetically new version. 3539:

I think it makes sense to remove the right, merely to remove a purely bureaucratic temptation. If it is perceived that the people who were given the right willy-nilly are enough for the moment, there will be more pressure to make it difficult for people to

3087:

This could be fixed by pointing all the reviewers to any new policy, and keeping them on a short lead. I'm not saying revoke it for one minor mistake, but if there's a history of noncompliance or the reviewer makes an error so egregious as for it to be

1984:

gone ahead and rearchived the page, the way it should be. We have an issue, however. Whioever archived the talk page discussions has archived them such that they are connected either to a non-existant project page or, as archive 3 is now an example,

598:

properly structured trial with a software-enforced "drop dead" date may make some sense, and I think a focus on using PC level 2 as an alternative to full protection makes more sense than focusing on PC level 1 as an alternative to semi-protection.—

2120:

Personally I'd suggest removing reviewer rights from everyone who doesn't have rollback. That keeps a good stock of people with the user right and it seems highly unlikely that users with rollback won't be allowed to keep their reviewer rights. --

1699:

The third phase was only started so that we could get the short-term issue out of the way and so discuss the longer-term issues in a more calm manner. Leaving the page as it is gives the false impression that this RfC was all about the short-term

1509:

I was archiving the third phase of the RfC, as discussed above. I think all three phases of the RfC should be given equal prominence, now that they are all closed. Summarising each one, as I was trying to do, seemed like the fairest way to do

1000:

Cool. I think my using more concrete terms has had the desired effect and got the issues in the open. It looks like some people like the idea of using PC in this way but that it would require consensus in the same way as any other form of PC.

1695:

The third phase may have been decisive, but it was only decisive about the short-term issue. The RfC as a whole is about the wider issues of PC. What people said in phases one and two will have more import on the longer-term issues of

617:

page with no discussion about the trial; the old discussions would just poison the well . Besides, "Request for Comment February 2011" sucks as a title for an RfC that started many months later. A descriptive title would be far better.

1008:

However, the arguments aren’t identical and I think the idea is an interesting one and warrants attention at some point, separate from the wider PC issue. However, I don’t think now would be a good time, when everyone has PC fatigue.

2023: 2019: 106: 101: 94: 89: 84: 559:

think has been lost sight of: given the choice between no protection and pending changes, PC is more restrictive; given the choice between semiprotection and PC, there is a tradeoff in restrictiveness; but given the choice between

290:

articles; and this abomination should end. It is only after that can we ask for an RfC on BLPs, as appropriate. BLP may override consensus, but since we have the old protection system, consensus comes first before pending changes.

1880:

I have added a summary of the discussion to the top of the page, keeping Phase 3 intact on the same page. This summary includes links to the relevent talk pages at each stage. I think that will help with the issue you identify,

2458:

some reason decided to restore voting rights to the hereditary peerage, there'd certainly be some kind of mass deselection before they let the assorted "seventh son of Lady Grimley-Fiendish" chinless wonders into Parliament.) –

423:

Brad asked for comments on the idea of exceptions for some BLPs. I think part of the problem is that it hasn't been clear what this means. I would like to propose that if there are to be any exceptions it should be like this:

2645:

No sense in taking the right from Rollbackers, Autoreviewers, and other users who did many good reviews only to give it back to them when we re implement PC. Take it from all others though, that should mediate the Willy-Nilly.

1004:

My own judgement on it is that PCL2+semi could be handy but that the arguments over PCL2+semi vs full are similar to those over PCL1 vs semi. I don’t see a particular need to go through them all again in the immediate future.

1405:

Hell no on another trial. After a short break(no more than a month or two), we'll need to write up permanent guidelines on when to use and when not to use PC and get that going as an RFC. Ideally that will be the final step.

3233:

I don't believe that is the type of problem he is referring to. He means a problematic PC usage that ended in disaster, not a problem with a user trying to cling onto a perceived "power" (since this is in no way "power").

141:

considered its use in the short term. In accordance with consensus it was removed from all articles on Friday, 20 May 2011, with no prejudice against future reinstatement, in some form, based upon consensus and discussion.

2856:

That's right; @(whoever you are, where is your sig?): why should we assume that rollbackers are OK by default and everybody else has been screwing up all the time? Either remove it from everybody or have everybody keep it.

1530: 1186: 138: 1063:

Instead of "proposal for accepted usage", I would suggest "proposals for future usage" as I am sure several disparate proposals will be made, and "accepted" would be obvious for any adopted proposals. Reasonable enough?

820:

and then be free to edit at will, even with Pending Changes Level 1 and semi-protection in place. Fortunately, a number of diligent and Bambifan-aware editors were able to stop his attack until he was blocked yet again.

1655:

It was this latest RfC (or latest phase, if you prefer) that was decisive, and which led to action, so in my view we should treat it as we do any other RfC, and just leave it on the page, along with the closing admin's

3441:

You may assume whatever you like, but it would be better for you to address the substance of my argument, which is that this "right" is redundant. The only ones arguing for its retention are those who collect baubles.

1681:

One of the problems with the trial is that no one could work out what was going on because there were so many pages, and it was all very hard to follow. I'm opposed to any more refactoring in part for that reason. :)

324:. These constant reboots of the RFC and breaks are a transparent attempt to wear out, confuse, and outlast all opposition to PC. No more reboots. No more breaks. Forget about it. Run this RFC, and if there is no 921:

I disagree that PC can be requested via RfPP. If you think PC Level 2 should be used on some articles (as a trial), make a proposal for that. Let people evaluate it. Define scope. Define who may review articles.

176:

don't face the gnashing of teeth that would accompany extending the deadline again. The ArbCom injunction (which as noted I did not vote on or for) may also help draw some attention to the need to wrap this up.

3360:

Yes, to that extent I can agree with...I follow a link to someone's page and I see something similar to what you're saying, and I think, "Why is he a reviewer?" Someone who shouldn't be receiving candy. =)

2556:

Because the argument that people only want to keep reviewer rights for themselves if they think some people should keep it becomes far weaker when the person making that point doesn't have the user-right. --

971:

Shit, I was wildly unclear. I mean that if we allow Pending Changes to be used again then it could be requested through RfPP for these edge cases. I don't think another trial is needed for this edge case. --

3104:

Admins. should be assumed to read the new policy; honestly, it should be required reading, and they should not use the tool, period, until they've read it, because it cannot be easily taken away from them.

2616:

I'd completely support removing the reviewer group now, since it is useless. Its only use now is for people to have the "I'm a reviewer!" userbox on their page, which really isn't a good reason to keep it.

486:

The above is my attempt to make something more concrete, based on what Brad was talking about. I probably will propose it in an RfC, but I thought I would ask if anyone had any thoughts on the idea first.

1884:

I think the only slightly confusing issue now is that one of the archived talk pages has a discussion of a phase 3 that never happened. We decided to have the short-term-use proposal instead-of/before

442:

I hope this would make it clear we are talking about a very small number of cases and a form of protection that is different to that which people will be familiar with from the pending-changes trial.

1242: 631: 613: 503: 130: 228:, and be done with it. Of course if it were not for the unconsidered actions of some who were overzealous at wanting PC immediately, we would have by now a consensual permanent PC implementation. 1391:

Good point. If a specific person or group of people is assigned to end a trail before a specified date - with defined sanctions to be applied if they fail to do so - a trial would be acceptable.

2493:

You're making this a bureaucracy. Rights should be removed after a screw-up (but then, yeah, really remove them fast, not some other process with file, appeal, argue, re-file, and whatnot).

2894:

user stop editing and got stolen in a new trial? Okay, he has no real rights/power, but through this hoaxes can be unseen if one or two users review (with a stolen account) each other.

2062:

Sorry, I was gone all day yesterday and didn't check in until now. Kinda sucky result to the day, I now know I'm going to have to lose a tooth. But that has nothing to do with this.

719:

I agree the process could be improved, but claiming that it is impossible to new editors is a very strong assertion, with no evidence - and a cursary glance at PERs shows it is false.

3121:

True, and I should point out I'm leaning towards complete removal rather than retention at this point. If really needed, admins, as WhatamIdoing pointed out, can fill in the place of

1600:

You removed the RfC entirely and wrote over it, so I reverted. It's fine to add to the page, but the RfC and people's posts about it should remain in place. That was my only concern.

3399:"right", are worthless, as we all know. I'd hazard a guess that most of the editors who applied for the right would equally have applied for any other, baubles are so eye-catching. 2926:

accepting edits; I've seen some accepted simply because they were not vandalism, which still isn't perfect because some might have been vandalism without the user realizing it.

3092:, then it should be revoked w/o further delay. Admins using it should be held to the same standards, if not considerably higher, since the mop is far more difficult to strip. — 2004:

I think I've figured this out. The Phase 3 talk page is now at Archive 3's talk page, and 4-5 are blanked. They may be deleted once we agree they are no longer necessary.

1318:

trial to continue without consensus will no longer be allowed, so we have to assuume that voting for a "limited time trial" is actually voting for a "trial" that never ends.

37: 1550:

is used on a number of pages. If you should probably edit it directly. Was the issue that the template now points to the archived version of phase 3? That can be undone.

2571:

If you're referring to me then I'd suggest that you educate yourself. I was offered the right but refused it, as I refuse to have all other rights in the present climate.

2091:

I think that any future discussion of any form of PC will run into problems with who has the right; it was dished out willy-nilly with no specific requirements in place.

2240:

shouldn't be trusted with "review powers" when/if PC is adopted at a later date, then there doesn't seem any reason to spend our limited resources making any changes to

1703:

Summarising the RfC as a whole will make it easier to follow, not harder. We should, of course, link to archived versions of each phase, so that the detail is not lost.

1428:

Sorry for being unclear. I was speaking of trials in general. Another PC trial? No thanks, just had one. Pretty much everybody has had their fill of PC trials.. (smile)

635:

should forget about the first two phases. Having further phases seems to make sense, but if there is consensus to use a different page title then I am fine with that.

164:

1. Excessive rhetoric is unhelpful in any discussion on Knowledge (XXG). Some of the comments posted since Friday evening were excessively strident and unwarranted.

1303:

I'm against the idea of another trial. We've already tried it out and know basically how it works. We need to go all-in on something, even if its pretty limited. --

192:

these articles can have profound impacts on the articles subjects. In my comments on Friday night, I did not purport to impose a new "PC for BLPs" policy by fiat; I

3312:

True, but a review process would help us retain good reviewers who, as CycloneGU said, may ignore a new application process, thinking that their flag carried over.

1747:

You're welcome to link to the first two phrases at the top of the page if you want to. But this latest RfC ought to be left in place so it's easy to find and read.

1136:

Either name is fine. I can definitely help with proposal additions, from seeing how it has worked I have a pretty good idea of what articles could benefit from it.

2324:

handed out willy-nilly, but if PC is restarted in some form, it would be good to have a pool of reviewers available, and these are people who ostensibly actually

1167:

Are we talking about renaming all three past phases here? They wouldn't fit neatly under a heading like "proposals for future usage". What we have is a kind of

270:

give the reviewers status to and the level of usage that there may well be a consensus for and as such we should offer that to the community in the near future.

709: 1442:

Fuck your trial. You tried to fuck us over. Write the motherfucking RfC and try to get it approved, that is, if you feel like you haven't screwed the pooch. —

2753:

did by insulting my intelligence to discredit my point. I simply brought up your record in an attempt to explain your behavior, not to discredit your point.

1822:

second phase was endorsements of positions, the analysis of which is available here." But if we add a bit more info it might tempt people to click though.

3469:

It's not "extremely unlikely", it's absolutely impossible. And if anything resembling PC is ever suggested again then it will have to be very different.

2411:

I make no such assumption, in fact I assume that it was such an unmitigated disaster last time around that it won't be, at least not in the same form.

1241:

I think a break would be a good idea. Not necessarily a long one, but a break nonetheless. In the interim, we should archive the last phase and use

1031: 776:

If I'm not mistaken, PC is gone from all articles now. Agree that new editors and unregistered users seem to have no trouble making edit requests; I

428:

Exceptional pending-changes protection (EPCP) is for cases where semi-protection is insufficient. It is not a simple alternative to semi-protection.

161:

Having reviewed the input since Friday night carefully (I've been travelling with limited wiki access over the weekend), please note the following:

1862:

difficult to follow the course of the thing—and I say that as someone who followed this rather closely since February and who was responsible for

907:

The number of articles this affects should be so small that such requests should be able to be made through RfPP or another equivalent venue. --

3076: 2329:

discussion will soon be starting up again and we can talk about it then. In the meantime, it's not really hurting anything to leave it as is.

302: 824:

While researching pending changes after the attack, I discovered the Level 2 setting which, prior to that, I had never heard of. Based on the

542:

See Bambifan example below. That example is not BLP-related, which goes to confirm my thought that the exception shouldn't be BLP specific.

2247:

I'm sure Malleus can understand why I think this proposal little more than an effort to put up a needless barrier to re-starting use of PC.

1097: 3213:

Yes. People like you trying to cling on to useless "rights" against all sense or reason because you believe that it gives you some status.

1030:

As this is over - I suggest archiving all this after 24 or 48 hours and renaming the page for the final RFC and suggest as a possibility -

526:

Can you please provide examples of articles where it is impossible to alleviate the concerns by SP or FP but where PC (lvl 1 or 2) would ?

2094:

To move onwards and upwards - to have meaningful chat about who should be a 'reviewer' - I think we need to get rid of all existing ones.

884:

small number of articles, but ones that are high-profile and also at a defined high risk for attack from a known, persistent vandal. --

3298:

It was an application process last time (at least until some people started giving it out like candy). It wasn't so difficult then. --

168:

responsibilities, and I've recused myself as an arbitrator in the related arbitration case (including on the vote on the injunction).

2905:

I would imagine that if PC got a new trial - extremely unlikely at this point - it's more likely that those with the right would be

1613:

Did you read what I said about it being a multiphase thing and the third-phase (the one currently on the page) having been archived?

1571: 1547: 1417: 1352: 1168: 1147: 3558: 3532: 3489: 3476: 3464: 3449: 3436: 3421: 3406: 3370: 3355: 3340: 3325: 3307: 3293: 3278: 3258: 3243: 3220: 3204: 3183: 3168: 3141: 3114: 3099: 3081: 3052: 3029: 3015: 2998: 2983: 2947: 2935: 2916: 2900: 2882: 2850: 2810: 2787: 2766: 2744: 2728: 2709: 2672: 2659: 2628: 2601: 2587: 2578: 2566: 2549: 2534: 2516: 2497: 2477: 2464: 2440: 2418: 2406: 2388: 2368: 2338: 2300: 2268: 2256: 2231: 2208: 2190: 2165: 2142: 2130: 2114: 2071: 2057: 2035: 2013: 1998: 1964: 1949: 1929: 1914: 1896: 1875: 1848: 1833: 1798: 1755: 1714: 1690: 1630: 1608: 1583: 1561: 1524: 1500: 1463: 1449: 1437: 1423: 1400: 1364: 1341: 1327: 1312: 1298: 1283: 1267: 1233: 1219: 1199: 1180: 1153: 1131: 1109: 1091: 1073: 1058: 1043: 1020: 981: 964: 939: 916: 902: 869: 853: 789: 770: 665: 644: 626: 607: 592: 577: 551: 535: 521: 497: 477: 453: 400: 377: 362: 339: 307: 279: 256: 237: 217: 17: 2749:

An ad homenim attack is, by definition, one on the person representing the idea, in a attempt to discredit the idea, exactly what

316:

I agree with TelCo; This "short break" is a transparent attempt to keep PC in place without consensus. This needs to be settled

2583:

At least in my case, the "why?" was not "why did you have yours removed?", but rather "why should people with rollback keep it?"

896: 847: 147: 45: 568:

would there still remain an issue? (Note: I'm not necessarily meaning as an outcome of the current-stage RfC, but in general.)

3089: 2312:

Remove the reviewer right from all editors except for some group of trusted users — perhaps those with rollback or autoreview.

53: 3265:

Well, we could have all reviewers reapply, or have their status reviewed by a trusted user (a reviewer/rollbacker or admin).

1938:, I am inclined to agree with CycloneGU. But let's see if SlimVirgin has any thoughts on the issue, before we archive again. 2971:

a runaway trial and a result of discussion among much cooler heads this time, though not assuming anything at this point.--

2906: 2694: 689:

relatively few editors (and no new editors) will go to the trouble of making an edit request (or even know how to do it)

825: 134: 2530:

If you insist on removing, then remove it from everyone. But again, I don't see the point in removing it from anyone.

713: 1866:

one instance of archiving several weeks ago. In any event, the talk pages are an essential part of the puzzle here.

3473: 3446: 3403: 3217: 2944: 2741: 2706: 2669: 2575: 2525: 2474: 2415: 2385: 2265: 2204: 2187: 2139: 1127: 1054: 185: 1492:

Hi Yaris, I couldn't see why you were overwriting the RfC page, so I've reverted. Can you say what your aim is?

2940:

People can have rollback if they want it, but it's almost as useless as the reviewer right is what I'm saying.

1513:

It is a slightly confusing situation, having a multiphase RfC, but I guess we just have to make the best of it.

438:

Articles protected by EPCP shall concurrently have both level-2 pending-changes protection and semi-protection.

172:

button, without considering whether anything was necessary to replace it, which would have been irresponsible.

2196: 817: 328:

to implement, junk PC. I'm sorry if you people don't like it, but that's the honest way of handling this. ☻☻☻

3195:

mandatory) procedure for that situation. Does anyone have a concrete example of a real problem? Even one?

2702:

I'm afraid that I'm genetically unable to understand "stupid", so I'll have to leave you to your fantasies.

2018:

Okey doke. If you happy to move things around in the archives then I think there are a number of things in

2682: 649:

The title is a bit silly at this point, but it might be more confusing to change it. Maybe with redirects?

3200: 2994: 2252: 2161: 1122:

slight preference is to include "future" to stress that we are moving beyond the parameters of the trial.

804:

appeared and started wreaking havoc in his preferred targets, articles on Disney animated films, such as

801: 435:

articles subject to attack by sleeper accounts, which are bordering on consideration for full-protection.

49: 3470: 3443: 3400: 3214: 3066: 3025: 2941: 2738: 2703: 2666: 2597: 2572: 2562: 2522: 2512: 2471: 2412: 2382: 2262: 2227: 2200: 2184: 2136: 2126: 1337: 1308: 1123: 1050: 977: 912: 806: 573: 292: 213: 41: 3009:

CycloneGU, yes I had that in mind: two user/accounts (don't have to be sockets) reviewing each other.

3525: 3417: 3351: 3303: 3254: 2436: 2402: 2364: 2334: 1871: 1619:

I still think we should archive and summarise at some point, but lets give Brad's comments some time.

1105: 1087: 1039: 960: 891: 842: 785: 705:

just by way of example, and the 'fake' IP addy of 127.0.0.1) - or log out and try editing something.

661: 373: 275: 3460: 3432: 3366: 3336: 3289: 3239: 3179: 3110: 3062: 3048: 3020:

How does that make sense? If you have the reviewer right your edits don't need to get reviewed. --

2931: 2782: 2623: 2067: 2009: 1994: 1960: 1925: 1459: 1360: 1294: 1229: 1195: 1981: 3132: 2974: 2846: 2447: 2347: 2296: 2053: 2031: 1945: 1910: 1892: 1829: 1710: 1626: 1579: 1557: 1520: 1433: 1396: 1323: 1279: 1263: 1215: 1176: 1016: 640: 622: 588: 547: 531: 517: 493: 449: 358: 332: 252: 233: 1790:

Okay, I see that's already done, so that's good. People can read each phase now for themselves.

2507:, I still think its reasonable for people with rollback to generally keep reviewer status. -- 1332:

Even with such a guarantee I don't see the value in switching it on for a couple of months. --

3196: 2990: 2248: 2157: 1069: 396: 3320: 3273: 3163: 3021: 3010: 2895: 2858: 2805: 2761: 2723: 2690: 2654: 2593: 2584: 2558: 2531: 2508: 2494: 2261:

I can indeed see why you might be so reluctant to give up any of your precious user rights.

2223: 2122: 1540:. These should obviously be left there for a while, rather than archiving them immediately. 1333: 1304: 973: 908: 569: 286:

As I've suggested before, the deadline has been set; pending changes should be removed from

209: 67: 3520: 3413: 3347: 3299: 3250: 3071: 2459: 2432: 2398: 2360: 2330: 1867: 1841: 1791: 1748: 1683: 1601: 1493: 1101: 1083: 1035: 956: 886: 837: 781: 657: 506:

and have the RfC there, as the fourth phase, since it relates directly to the third phase.

369: 297: 271: 740:

One of the primary reasons for removing PC is so that we can have meaningful discussion.

697:

Have you seen the system in place for processing such requests? You can see it with e.g.

225: 2377:

Your suggestion makes no sense; leave the right in place until it's activated again and

3456: 3428: 3362: 3332: 3285: 3235: 3175: 3106: 3044: 2927: 2875: 2777: 2618: 2592:

I've already gone into quite a bit of detail above. Let me know what else you need. --

2504: 2107: 2063: 2005: 1990: 1956: 1921: 1455: 1407: 1356: 1348: 1290: 1225: 1191: 1137: 932: 763: 470: 335: 56:

exist to draw attention and ensure that more editors mediate or comment on the dispute.

3554: 2842: 2292: 2049: 2027: 1941: 1906: 1888: 1825: 1706: 1622: 1575: 1553: 1516: 1429: 1392: 1319: 1275: 1259: 1211: 1172: 1012: 865: 636: 618: 603: 584: 543: 527: 513: 489: 445: 354: 329: 248: 229: 3331:

never knew of an application process and would never have been involved otherwise.

743:

Whilst PC remains on some articles, such discussions are unlikely to be productive.

2315:

Leave it alone until a policy is in place about qualifications for reviewer rights.

1065: 392: 712:, which seems to work reasonably well. For example, today, there was a request on 688: 3313: 3266: 3156: 2798: 2754: 2716: 2686: 2647: 2024:

Knowledge (XXG) talk:Pending changes/Request for Comment February 2011/Archive 2

2020:

Knowledge (XXG) talk:Pending changes/Request for Comment February 2011/Archive 3

3412:

And those FAs are so annoying when people act like it reflects well on them. --

1818:

BTW, I like what you've done in bringing together all the closing statements.

702: 2868: 2214:

unnecessarily is just going to create extra admin work that isn't necessary.

2100: 1115: 925: 756: 463: 2863:(I just added the user name to the above comment at 00:52 - made by Ronk01 1531:

Knowledge (XXG):Pending changes/Request for Comment February 2011/Archive 3

2026:. Especially, the stuff that is about the proposed questionnaire phase. 1920:

viewed at a user's leisure (given they have some 2 days to read it all).

1034:- any ojections to this or alternative suggestions please comment, thanks. 726:

We've discussed the things you mention. At length...for a long time. Yes,

3550: 861: 599: 2088:

I'm tempted to RFC removal of the user right 'reviewer' from all users.

734:

ways, PC can be less restrictive. But, that's not the immediate issue.

3284:

might get left out because they think it's going to just carry over.

860:

When PC was removed, the full-protection should have been reinstated.—

1574:. Unless anyone has any objections, I will restore it to the page. 1114:

I don't particularly care about the name and want to resist coloring

3125:

shepherding until the numbers swell up again. Again the disclaimer:

1538:

added some important comments to the bottom of the third-phase page

812: 1905:

Archive 3 to be a redirect to phase 3 on the non-archived page.

1243:

Knowledge (XXG):Pending changes/Request for Comment February 2011

632:

Knowledge (XXG):Pending changes/Request for Comment February 2011

614:

Knowledge (XXG):Pending changes/Request for Comment February 2011

504:

Knowledge (XXG):Pending changes/Request for Comment February 2011

1078:

Sounds reasonable. Let's make sure that the archived page has a

1032:

Knowledge (XXG) talk:Pending changes/proposal for accepted usage

483:

ignoring it for a few weeks and him having to bring it up again.

30: 1210:", I am a supporter of PC and I think there should be a break. 117: 61: 25: 502:

Thinking about it, we would logically archive the content of

2236:

I'd generalize that: unless there is some good reason why

1255:

A list of things people have suggested for what to do next.

800:

This past Friday (20 May), another suspected sockpuppet of

1989:. This needs to be fixed, so I'll potter about with it. 1245:

to summarise the whole conversation. This would include:

716:(and there's another there, from a couple of weeks back). 247:

all of the previous pages that have dealt with this topic.

2218:

initially within the group - all of which seem bad to me.

1208:

if we take a break as opposers to PC above have stated...

48:. Be patient when approaching solutions to any issues. If 353:

chance that the timing will cause the proposal to fail.

3043:

vandalism and repeated visits myself to deal with it.

2864: 2045: 2041: 1986: 1935: 1902: 1616:

Anyway, think I've sorted out all the tamplating stuff.

1567: 1544: 1537: 1098:

Knowledge (XXG) talk:Pending changes/proposal for usage

777: 698: 2776:

need a collection of useless rights, rollback or not?

2135:

I don't have either, and neither should anyone else.

419:Clarifying exceptional pending-changes protection 710:Category:Knowledge (XXG) protected edit requests 2961:had precedence in a trial for testing purposes. 1224:I apologize, I did not specifically mean you. 2199:hard at work. See also RFA and Arbcom reform. 1169:Knowledge (XXG):Village pump (pending changes) 205:opposite, so we need some more views on this. 44:while commenting or presenting evidence, and 8: 2909:until such time as they misuse the right. — 2907:grandfathered into any new Reviewing policy 2309:Remove the reviewer right from all editors. 2306:Seems like it comes down to three options: 2040:I have just made that move. Specifically, 1536:However, after you restored the page, Brad 148:Final comments by the closing administrator 2737:attack is Ronk? It's what you just wrote. 737:The immediate issue is, ending the trial. 2320:I can see both side of the argument. It 2503:I've requested removal of the right for 1049:Good idea. Let's put this all behind us. 186:User talk:Scott MacDonald#Dustin Diamond 796:Defense against persistent sockpuppetry 3545:about what reviewers were supposed to 2429:see what I just said at a certain RfA. 2393:Hi, Malleus. You are assuming that it 1187:I already created the archive location 1096:Yes Collect your rename is preferable 694:Do you actually know that to be true? 563:protection and pending changes, PC is 2922:It existed before PC came into being. 7: 18:Knowledge (XXG) talk:Pending changes 746:We need to 'clear the air'. First. 651:(I always thought February was the 612:Strongly disagree with the idea of 2797:makes no sense and is irrelevant. 1529:The archive of the third phase is 1355:as being part of a legal threat? 184:protection would do as well (see, 24: 1572:Template:Pending changes May 2011 1548:Template:Pending changes May 2011 431:Specifically, EPCP is for use on 121: 66: 29: 2156:bureaucratic-minded decision. 1936:the current version of the page 1082:link to the new, renamed page. 510:such cases will be BLP-related. 3129:PC gets reactivated at all.-- 1987:to the wrong talk page archive 1: 2733:Do you actually know what an 1543:Slim, can I ask why you made 1274:on it in September-November. 778:responded to one such request 386:As I read NYB's dicta, I saw 1353:The Knowledge (XXG) Signpost 46:do not make personal attacks 2084:Reviewer user right removal 714:Talk:WWE Capitol Punishment 3575: 1249:A brief background section 135:pending-changes protection 3559:23:42, 27 June 2011 (UTC) 3533:05:40, 14 June 2011 (UTC) 3516:have said permissions. — 3490:04:15, 14 June 2011 (UTC) 3477:02:06, 14 June 2011 (UTC) 3465:01:49, 14 June 2011 (UTC) 3450:00:29, 14 June 2011 (UTC) 3437:00:20, 14 June 2011 (UTC) 3422:23:24, 13 June 2011 (UTC) 3407:22:45, 13 June 2011 (UTC) 3371:20:55, 13 June 2011 (UTC) 3356:20:44, 13 June 2011 (UTC) 3341:02:23, 13 June 2011 (UTC) 3326:00:52, 13 June 2011 (UTC) 3308:23:54, 12 June 2011 (UTC) 3294:23:31, 12 June 2011 (UTC) 3279:19:17, 12 June 2011 (UTC) 3259:18:13, 12 June 2011 (UTC) 3244:15:21, 12 June 2011 (UTC) 3221:02:35, 12 June 2011 (UTC) 3205:02:31, 12 June 2011 (UTC) 3184:15:19, 12 June 2011 (UTC) 3169:02:08, 12 June 2011 (UTC) 3142:04:27, 11 June 2011 (UTC) 3115:04:14, 11 June 2011 (UTC) 3100:02:18, 11 June 2011 (UTC) 3082:02:02, 11 June 2011 (UTC) 3053:04:14, 11 June 2011 (UTC) 2861:01:46, 8 June 2011 (UTC) 1464:03:34, 13 June 2011 (UTC) 1450:05:42, 12 June 2011 (UTC) 832:fully-protected article. 157:Comments from Newyorkbrad 3030:23:09, 8 June 2011 (UTC) 3016:16:37, 8 June 2011 (UTC) 2999:19:46, 8 June 2011 (UTC) 2984:16:13, 8 June 2011 (UTC) 2948:19:32, 8 June 2011 (UTC) 2936:14:33, 8 June 2011 (UTC) 2917:09:42, 8 June 2011 (UTC) 2901:08:33, 8 June 2011 (UTC) 2883:10:34, 8 June 2011 (UTC) 2859:Choyoołʼįįhí:Seb az86556 2851:01:39, 8 June 2011 (UTC) 2811:23:46, 8 June 2011 (UTC) 2788:22:13, 8 June 2011 (UTC) 2767:23:46, 8 June 2011 (UTC) 2745:19:30, 8 June 2011 (UTC) 2729:15:44, 8 June 2011 (UTC) 2710:00:57, 8 June 2011 (UTC) 2673:00:06, 8 June 2011 (UTC) 2660:23:49, 7 June 2011 (UTC) 2629:22:19, 7 June 2011 (UTC) 2602:23:12, 8 June 2011 (UTC) 2588:23:13, 7 June 2011 (UTC) 2585:Choyoołʼįįhí:Seb az86556 2579:22:22, 7 June 2011 (UTC) 2567:22:11, 7 June 2011 (UTC) 2550:02:02, 8 June 2011 (UTC) 2535:22:07, 7 June 2011 (UTC) 2532:Choyoołʼįįhí:Seb az86556 2517:21:57, 7 June 2011 (UTC) 2498:21:51, 7 June 2011 (UTC) 2495:Choyoołʼįįhí:Seb az86556 2478:22:02, 7 June 2011 (UTC) 2465:21:48, 7 June 2011 (UTC) 2441:21:46, 7 June 2011 (UTC) 2419:21:42, 7 June 2011 (UTC) 2407:21:39, 7 June 2011 (UTC) 2389:21:37, 7 June 2011 (UTC) 2369:21:22, 7 June 2011 (UTC) 2339:21:16, 7 June 2011 (UTC) 2301:17:06, 7 June 2011 (UTC) 2269:18:06, 7 June 2011 (UTC) 2257:18:02, 7 June 2011 (UTC) 2242:that individual editor's 2232:16:57, 7 June 2011 (UTC) 2209:05:36, 7 June 2011 (UTC) 2197:Iron Law of Institutions 2191:23:53, 6 June 2011 (UTC) 2166:23:48, 6 June 2011 (UTC) 2143:23:09, 6 June 2011 (UTC) 2131:22:55, 6 June 2011 (UTC) 2115:22:48, 6 June 2011 (UTC) 2072:19:14, 3 June 2011 (UTC) 2058:12:45, 3 June 2011 (UTC) 2036:12:40, 2 June 2011 (UTC) 2014:23:28, 1 June 2011 (UTC) 1999:23:02, 1 June 2011 (UTC) 1965:22:40, 1 June 2011 (UTC) 1950:06:36, 1 June 2011 (UTC) 1930:21:05, 31 May 2011 (UTC) 1915:18:51, 31 May 2011 (UTC) 1897:17:41, 31 May 2011 (UTC) 1876:22:58, 29 May 2011 (UTC) 1849:21:48, 29 May 2011 (UTC) 1834:19:16, 29 May 2011 (UTC) 1799:22:34, 28 May 2011 (UTC) 1756:22:32, 28 May 2011 (UTC) 1715:09:57, 28 May 2011 (UTC) 1691:23:10, 27 May 2011 (UTC) 1631:22:37, 27 May 2011 (UTC) 1609:22:33, 27 May 2011 (UTC) 1584:22:20, 27 May 2011 (UTC) 1562:22:10, 27 May 2011 (UTC) 1525:21:51, 27 May 2011 (UTC) 1501:20:59, 27 May 2011 (UTC) 1488:Recent edits to the page 1438:20:59, 25 May 2011 (UTC) 1424:20:53, 25 May 2011 (UTC) 1401:12:06, 25 May 2011 (UTC) 1365:06:11, 25 May 2011 (UTC) 1342:20:58, 24 May 2011 (UTC) 1328:20:48, 24 May 2011 (UTC) 1313:20:24, 24 May 2011 (UTC) 1299:20:17, 24 May 2011 (UTC) 1284:14:50, 24 May 2011 (UTC) 1268:09:20, 24 May 2011 (UTC) 1234:03:48, 24 May 2011 (UTC) 1220:03:43, 24 May 2011 (UTC) 1200:03:15, 24 May 2011 (UTC) 1181:19:30, 23 May 2011 (UTC) 1154:02:15, 24 May 2011 (UTC) 1132:19:12, 23 May 2011 (UTC) 1110:18:53, 23 May 2011 (UTC) 1092:18:47, 23 May 2011 (UTC) 1074:18:22, 23 May 2011 (UTC) 1059:17:56, 23 May 2011 (UTC) 1044:17:38, 23 May 2011 (UTC) 1026:Moving forward - Archive 1021:19:19, 23 May 2011 (UTC) 982:17:33, 23 May 2011 (UTC) 965:17:28, 23 May 2011 (UTC) 940:17:22, 23 May 2011 (UTC) 917:17:20, 23 May 2011 (UTC) 903:14:09, 23 May 2011 (UTC) 870:14:01, 23 May 2011 (UTC) 854:13:52, 23 May 2011 (UTC) 790:18:51, 23 May 2011 (UTC) 771:17:15, 23 May 2011 (UTC) 753:think of ways forwards. 666:16:56, 23 May 2011 (UTC) 645:16:40, 23 May 2011 (UTC) 627:16:04, 23 May 2011 (UTC) 608:13:41, 23 May 2011 (UTC) 593:13:34, 23 May 2011 (UTC) 578:13:12, 23 May 2011 (UTC) 552:14:28, 23 May 2011 (UTC) 536:12:56, 23 May 2011 (UTC) 522:12:53, 23 May 2011 (UTC) 498:12:45, 23 May 2011 (UTC) 478:12:33, 23 May 2011 (UTC) 454:12:26, 23 May 2011 (UTC) 401:16:34, 23 May 2011 (UTC) 378:09:43, 23 May 2011 (UTC) 363:09:36, 23 May 2011 (UTC) 340:09:08, 23 May 2011 (UTC) 308:08:55, 23 May 2011 (UTC) 280:08:47, 23 May 2011 (UTC) 257:05:48, 23 May 2011 (UTC) 238:01:09, 23 May 2011 (UTC) 218:00:43, 23 May 2011 (UTC) 208:I hope this is helpful. 1252:A summary of each phase 996:Clarification achieved? 687:Reply to NY Brad, re. " 2397:be activated again. -- 2238:that individual editor 1934:While I am happy with 1454:Was that necessary? 881:The Fox and the Hound 818:auto-confirmed status 807:The Fox and the Hound 131:a Request for Comment 826:description provided 701:(using prot article 3063:Special:StablePages 388:no such requirement 2022:that should be in 1419:Operation Big Bear 1149:Operation Big Bear 3531: 3153:Ex virtute Jimbo. 3146:I would advocate 2886: 2881: 2786: 2699: 2685:comment added by 2627: 2451: 2351: 2113: 1865: 1847: 1797: 1754: 1689: 1607: 1499: 938: 879:myself, although 769: 656: 476: 154: 153: 116: 115: 112: 111: 60: 59: 3566: 3530: 3528: 3517: 3488: 3323: 3318: 3276: 3271: 3166: 3161: 3139: 3136: 3098: 3079: 3074: 3069: 2981: 2978: 2915: 2880: 2878: 2872: 2866: 2862: 2808: 2803: 2780: 2764: 2759: 2726: 2721: 2698: 2679: 2657: 2652: 2621: 2548: 2462: 2445: 2345: 2201:TotientDragooned 2112: 2110: 2104: 2098: 1863: 1846: 1844: 1796: 1794: 1753: 1751: 1688: 1686: 1606: 1604: 1498: 1496: 1448: 1420: 1414: 1150: 1144: 1124:TotientDragooned 1051:TotientDragooned 937: 935: 929: 923: 899: 894: 889: 850: 845: 840: 768: 766: 760: 754: 690: 650: 475: 473: 467: 461: 305: 300: 295: 125: 124: 118: 81: 80: 70: 62: 52:is not reached, 33: 32: 26: 3574: 3573: 3569: 3568: 3567: 3565: 3564: 3563: 3526: 3518: 3483: 3321: 3314: 3274: 3267: 3164: 3157: 3134: 3131: 3093: 3077: 3072: 3067: 2976: 2973: 2910: 2876: 2870: 2867: 2806: 2799: 2762: 2755: 2724: 2717: 2680: 2655: 2648: 2543: 2460: 2425:And you should 2108: 2102: 2099: 2086: 1864:(to blame for?) 1842: 1792: 1749: 1684: 1602: 1494: 1490: 1443: 1422: 1418: 1408: 1152: 1148: 1138: 1028: 998: 933: 927: 924: 897: 892: 887: 848: 843: 838: 798: 780:earlier today. 764: 758: 755: 471: 465: 462: 421: 326:clear consensus 303: 298: 293: 159: 150: 122: 75: 54:other solutions 22: 21: 20: 12: 11: 5: 3572: 3570: 3562: 3561: 3536: 3535: 3503: 3502: 3501: 3500: 3499: 3498: 3497: 3496: 3495: 3494: 3493: 3492: 3396: 3395: 3394: 3393: 3392: 3391: 3390: 3389: 3388: 3387: 3386: 3385: 3384: 3383: 3382: 3381: 3380: 3379: 3378: 3377: 3376: 3375: 3374: 3373: 3226: 3225: 3224: 3223: 3208: 3207: 3191: 3190: 3189: 3188: 3187: 3186: 3119: 3118: 3117: 3058: 3057: 3056: 3055: 3037: 3036: 3035: 3034: 3033: 3032: 3004: 3003: 3002: 3001: 2963: 2962: 2958: 2957: 2956: 2955: 2954: 2953: 2952: 2951: 2950: 2923: 2888: 2887: 2838: 2837: 2836: 2835: 2834: 2833: 2832: 2831: 2830: 2829: 2828: 2827: 2826: 2825: 2824: 2823: 2822: 2821: 2820: 2819: 2818: 2817: 2816: 2815: 2814: 2813: 2769: 2632: 2631: 2613: 2612: 2611: 2610: 2609: 2608: 2607: 2606: 2605: 2604: 2581: 2554: 2553: 2552: 2528: 2491: 2490: 2489: 2488: 2487: 2486: 2485: 2484: 2483: 2482: 2481: 2480: 2443: 2423:Good for you! 2372: 2371: 2355: 2354: 2342: 2341: 2318: 2317: 2316: 2313: 2310: 2286: 2285: 2284: 2283: 2282: 2281: 2280: 2279: 2278: 2277: 2276: 2275: 2274: 2273: 2272: 2271: 2245: 2219: 2215: 2173: 2172: 2171: 2170: 2169: 2168: 2148: 2147: 2146: 2145: 2085: 2082: 2081: 2080: 2079: 2078: 2077: 2076: 2075: 2074: 1978: 1977: 1976: 1975: 1974: 1973: 1972: 1971: 1970: 1969: 1968: 1967: 1939: 1899: 1886: 1882: 1852: 1851: 1816: 1815: 1814: 1813: 1812: 1811: 1810: 1809: 1808: 1807: 1806: 1805: 1804: 1803: 1802: 1801: 1773: 1772: 1771: 1770: 1769: 1768: 1767: 1766: 1765: 1764: 1763: 1762: 1761: 1760: 1759: 1758: 1730: 1729: 1728: 1727: 1726: 1725: 1724: 1723: 1722: 1721: 1720: 1719: 1718: 1717: 1704: 1701: 1697: 1668: 1667: 1666: 1665: 1664: 1663: 1662: 1661: 1660: 1659: 1658: 1657: 1642: 1641: 1640: 1639: 1638: 1637: 1636: 1635: 1634: 1633: 1620: 1617: 1614: 1591: 1590: 1589: 1588: 1587: 1586: 1551: 1541: 1534: 1514: 1511: 1507: 1489: 1486: 1485: 1484: 1483: 1482: 1481: 1480: 1479: 1478: 1477: 1476: 1475: 1474: 1473: 1472: 1471: 1470: 1469: 1468: 1467: 1466: 1416: 1378: 1377: 1376: 1375: 1374: 1373: 1372: 1371: 1370: 1369: 1368: 1367: 1349:Britney Spears 1257: 1256: 1253: 1250: 1239: 1238: 1237: 1236: 1203: 1202: 1165: 1164: 1163: 1162: 1161: 1160: 1159: 1158: 1157: 1156: 1146: 1061: 1027: 1024: 997: 994: 993: 992: 991: 990: 989: 988: 987: 986: 985: 984: 947: 946: 945: 944: 943: 942: 919: 873: 872: 797: 794: 793: 792: 685: 684: 683: 682: 681: 680: 679: 678: 677: 676: 675: 674: 673: 672: 671: 670: 669: 668: 595: 556: 555: 554: 511: 507: 487: 484: 440: 439: 436: 429: 420: 417: 416: 415: 414: 413: 412: 411: 410: 409: 408: 407: 406: 405: 404: 403: 345: 344: 343: 342: 311: 310: 283: 282: 262: 261: 260: 259: 241: 240: 158: 155: 152: 151: 143: 128: 126: 114: 113: 110: 109: 104: 98: 97: 92: 87: 77: 76: 71: 65: 58: 57: 34: 23: 15: 14: 13: 10: 9: 6: 4: 3: 2: 3571: 3560: 3556: 3552: 3548: 3543: 3538: 3537: 3534: 3529: 3523: 3522: 3515: 3510: 3505: 3504: 3491: 3486: 3480: 3479: 3478: 3475: 3472: 3468: 3467: 3466: 3462: 3458: 3453: 3452: 3451: 3448: 3445: 3440: 3439: 3438: 3434: 3430: 3425: 3424: 3423: 3419: 3415: 3411: 3410: 3409: 3408: 3405: 3402: 3372: 3368: 3364: 3359: 3358: 3357: 3353: 3349: 3344: 3343: 3342: 3338: 3334: 3329: 3328: 3327: 3324: 3319: 3317: 3311: 3310: 3309: 3305: 3301: 3297: 3296: 3295: 3291: 3287: 3282: 3281: 3280: 3277: 3272: 3270: 3264: 3263: 3262: 3261: 3260: 3256: 3252: 3247: 3246: 3245: 3241: 3237: 3232: 3231: 3230: 3229: 3228: 3227: 3222: 3219: 3216: 3212: 3211: 3210: 3209: 3206: 3202: 3198: 3193: 3192: 3185: 3181: 3177: 3172: 3171: 3170: 3167: 3162: 3160: 3154: 3149: 3145: 3144: 3143: 3140: 3138: 3128: 3124: 3120: 3116: 3112: 3108: 3103: 3102: 3101: 3096: 3091: 3086: 3085: 3084: 3083: 3080: 3075: 3070: 3064: 3054: 3050: 3046: 3041: 3040: 3039: 3038: 3031: 3027: 3023: 3019: 3018: 3017: 3014: 3013: 3008: 3007: 3006: 3005: 3000: 2996: 2992: 2987: 2986: 2985: 2982: 2980: 2970: 2965: 2964: 2959: 2949: 2946: 2943: 2939: 2938: 2937: 2933: 2929: 2924: 2920: 2919: 2918: 2913: 2908: 2904: 2903: 2902: 2899: 2898: 2892: 2891: 2890: 2889: 2884: 2879: 2874: 2873: 2865: 2860: 2855: 2854: 2853: 2852: 2848: 2844: 2812: 2809: 2804: 2802: 2796: 2791: 2790: 2789: 2784: 2779: 2775: 2770: 2768: 2765: 2760: 2758: 2752: 2748: 2747: 2746: 2743: 2740: 2736: 2732: 2731: 2730: 2727: 2722: 2720: 2713: 2712: 2711: 2708: 2705: 2701: 2700: 2696: 2692: 2688: 2684: 2676: 2675: 2674: 2671: 2668: 2663: 2662: 2661: 2658: 2653: 2651: 2644: 2643: 2642: 2641: 2640: 2639: 2638: 2637: 2636: 2635: 2634: 2633: 2630: 2625: 2620: 2615: 2614: 2603: 2599: 2595: 2591: 2590: 2589: 2586: 2582: 2580: 2577: 2574: 2570: 2569: 2568: 2564: 2560: 2555: 2551: 2546: 2540: 2539: 2538: 2537: 2536: 2533: 2529: 2527: 2524: 2520: 2519: 2518: 2514: 2510: 2506: 2502: 2501: 2500: 2499: 2496: 2479: 2476: 2473: 2468: 2467: 2466: 2463: 2456: 2449: 2448:edit conflict 2444: 2442: 2438: 2434: 2430: 2428: 2422: 2421: 2420: 2417: 2414: 2410: 2409: 2408: 2404: 2400: 2396: 2392: 2391: 2390: 2387: 2384: 2380: 2376: 2375: 2374: 2373: 2370: 2366: 2362: 2357: 2356: 2349: 2348:edit conflict 2344: 2343: 2340: 2336: 2332: 2327: 2323: 2319: 2314: 2311: 2308: 2307: 2305: 2304: 2303: 2302: 2298: 2294: 2290: 2270: 2267: 2264: 2260: 2259: 2258: 2254: 2250: 2246: 2243: 2239: 2235: 2234: 2233: 2229: 2225: 2220: 2216: 2212: 2211: 2210: 2206: 2202: 2198: 2194: 2193: 2192: 2189: 2186: 2181: 2180: 2179: 2178: 2177: 2176: 2175: 2174: 2167: 2163: 2159: 2154: 2153: 2152: 2151: 2150: 2149: 2144: 2141: 2138: 2134: 2133: 2132: 2128: 2124: 2119: 2118: 2117: 2116: 2111: 2106: 2105: 2095: 2092: 2089: 2083: 2073: 2069: 2065: 2061: 2060: 2059: 2055: 2051: 2047: 2043: 2039: 2038: 2037: 2033: 2029: 2025: 2021: 2017: 2016: 2015: 2011: 2007: 2003: 2002: 2001: 2000: 1996: 1992: 1988: 1983: 1966: 1962: 1958: 1953: 1952: 1951: 1947: 1943: 1940: 1937: 1933: 1932: 1931: 1927: 1923: 1918: 1917: 1916: 1912: 1908: 1904: 1900: 1898: 1894: 1890: 1887: 1883: 1879: 1878: 1877: 1873: 1869: 1861: 1856: 1855: 1854: 1853: 1850: 1845: 1838: 1837: 1836: 1835: 1831: 1827: 1823: 1819: 1800: 1795: 1789: 1788: 1787: 1786: 1785: 1784: 1783: 1782: 1781: 1780: 1779: 1778: 1777: 1776: 1775: 1774: 1757: 1752: 1746: 1745: 1744: 1743: 1742: 1741: 1740: 1739: 1738: 1737: 1736: 1735: 1734: 1733: 1732: 1731: 1716: 1712: 1708: 1705: 1702: 1698: 1694: 1693: 1692: 1687: 1680: 1679: 1678: 1677: 1676: 1675: 1674: 1673: 1672: 1671: 1670: 1669: 1654: 1653: 1652: 1651: 1650: 1649: 1648: 1647: 1646: 1645: 1644: 1643: 1632: 1628: 1624: 1621: 1618: 1615: 1612: 1611: 1610: 1605: 1599: 1598: 1597: 1596: 1595: 1594: 1593: 1592: 1585: 1581: 1577: 1573: 1569: 1565: 1564: 1563: 1559: 1555: 1552: 1549: 1546: 1542: 1539: 1535: 1532: 1528: 1527: 1526: 1522: 1518: 1515: 1512: 1508: 1505: 1504: 1503: 1502: 1497: 1487: 1465: 1461: 1457: 1453: 1452: 1451: 1446: 1441: 1440: 1439: 1435: 1431: 1427: 1426: 1425: 1421: 1415: 1413: 1412: 1404: 1403: 1402: 1398: 1394: 1390: 1389: 1388: 1387: 1386: 1385: 1384: 1383: 1382: 1381: 1380: 1379: 1366: 1362: 1358: 1354: 1350: 1345: 1344: 1343: 1339: 1335: 1331: 1330: 1329: 1325: 1321: 1316: 1315: 1314: 1310: 1306: 1302: 1301: 1300: 1296: 1292: 1287: 1286: 1285: 1281: 1277: 1272: 1271: 1270: 1269: 1265: 1261: 1254: 1251: 1248: 1247: 1246: 1244: 1235: 1231: 1227: 1223: 1222: 1221: 1217: 1213: 1209: 1205: 1204: 1201: 1197: 1193: 1188: 1185: 1184: 1183: 1182: 1178: 1174: 1170: 1155: 1151: 1145: 1143: 1142: 1135: 1134: 1133: 1129: 1125: 1121: 1117: 1113: 1112: 1111: 1107: 1103: 1099: 1095: 1094: 1093: 1089: 1085: 1081: 1077: 1076: 1075: 1071: 1067: 1062: 1060: 1056: 1052: 1048: 1047: 1046: 1045: 1041: 1037: 1033: 1025: 1023: 1022: 1018: 1014: 1010: 1006: 1002: 995: 983: 979: 975: 970: 969: 968: 967: 966: 962: 958: 953: 952: 951: 950: 949: 948: 941: 936: 931: 930: 920: 918: 914: 910: 906: 905: 904: 901: 900: 895: 890: 882: 877: 876: 875: 874: 871: 867: 863: 858: 857: 856: 855: 852: 851: 846: 841: 833: 829: 827: 822: 819: 815: 814: 809: 808: 803: 795: 791: 787: 783: 779: 775: 774: 773: 772: 767: 762: 761: 752: 747: 744: 741: 738: 735: 733: 730:feel that in 729: 724: 720: 717: 715: 711: 706: 704: 700: 695: 692: 667: 663: 659: 654: 648: 647: 646: 642: 638: 633: 630: 629: 628: 624: 620: 615: 611: 610: 609: 605: 601: 596: 594: 590: 586: 581: 580: 579: 575: 571: 566: 562: 557: 553: 549: 545: 541: 540: 539: 538: 537: 533: 529: 525: 524: 523: 519: 515: 512: 508: 505: 501: 500: 499: 495: 491: 488: 485: 481: 480: 479: 474: 469: 468: 458: 457: 456: 455: 451: 447: 443: 437: 434: 430: 427: 426: 425: 418: 402: 398: 394: 389: 385: 384: 383: 382: 381: 380: 379: 375: 371: 366: 365: 364: 360: 356: 351: 350: 349: 348: 347: 346: 341: 337: 334: 331: 327: 323: 319: 315: 314: 313: 312: 309: 306: 301: 296: 289: 285: 284: 281: 277: 273: 268: 264: 263: 258: 254: 250: 245: 244: 243: 242: 239: 235: 231: 227: 222: 221: 220: 219: 215: 211: 206: 202: 198: 195: 189: 187: 181: 177: 173: 169: 165: 162: 156: 149: 146: 140: 136: 132: 127: 120: 119: 108: 105: 103: 100: 99: 96: 93: 91: 88: 86: 83: 82: 79: 78: 74: 69: 64: 63: 55: 51: 47: 43: 39: 35: 28: 27: 19: 3546: 3541: 3519: 3513: 3508: 3484: 3397: 3315: 3268: 3197:WhatamIdoing 3158: 3152: 3147: 3130: 3126: 3122: 3094: 3059: 3011: 2991:WhatamIdoing 2972: 2968: 2911: 2896: 2869: 2839: 2800: 2794: 2773: 2756: 2750: 2734: 2718: 2681:— Preceding 2649: 2544: 2492: 2454: 2426: 2424: 2394: 2378: 2325: 2321: 2291: 2287: 2249:WhatamIdoing 2241: 2237: 2158:WhatamIdoing 2101: 2096: 2093: 2090: 2087: 1979: 1901:I have just 1859: 1824: 1820: 1817: 1566:I have made 1545:this change? 1491: 1444: 1410: 1409: 1258: 1240: 1207: 1166: 1140: 1139: 1119: 1079: 1029: 1011: 1007: 1003: 999: 926: 885: 880: 836: 834: 830: 823: 811: 805: 799: 757: 750: 748: 745: 742: 739: 736: 731: 727: 725: 721: 718: 707: 696: 693: 686: 652: 564: 560: 464: 444: 441: 432: 422: 387: 325: 321: 317: 287: 267:take a break 266: 207: 203: 199: 193: 190: 182: 178: 174: 170: 166: 163: 160: 144: 72: 36:Please stay 3090:intentional 3022:Eraserhead1 2594:Eraserhead1 2559:Eraserhead1 2509:Eraserhead1 2381:remove it? 2224:Eraserhead1 2123:Eraserhead1 1881:Rivertorch. 1568:two changes 1334:Eraserhead1 1305:Eraserhead1 974:Eraserhead1 909:Eraserhead1 802:Bambifan101 691:" (above); 570:Newyorkbrad 433:BLP-related 210:Newyorkbrad 139:third phase 129:As part of 3414:Tryptofish 3348:Tryptofish 3300:Tryptofish 3251:Tryptofish 2989:broken.) 2735:ad hominem 2461:iridescent 2433:Tryptofish 2399:Tryptofish 2361:Tryptofish 2331:Mojoworker 2097:Comments? 1868:Rivertorch 1843:SlimVirgin 1793:SlimVirgin 1750:SlimVirgin 1685:SlimVirgin 1603:SlimVirgin 1495:SlimVirgin 1116:bike sheds 1102:Off2riorob 1084:Rivertorch 1036:Off2riorob 957:Off2riorob 782:Rivertorch 703:Anne Frank 658:Rivertorch 370:Off2riorob 272:Off2riorob 3457:CycloneGU 3429:CycloneGU 3363:CycloneGU 3333:CycloneGU 3286:CycloneGU 3236:CycloneGU 3176:CycloneGU 3123:temporary 3107:CycloneGU 3045:CycloneGU 2928:CycloneGU 2778:Ajraddatz 2619:Ajraddatz 2064:CycloneGU 2006:CycloneGU 1991:CycloneGU 1957:CycloneGU 1922:CycloneGU 1858:found it 1456:CycloneGU 1430:Guy Macon 1411:Wizardman 1393:Guy Macon 1357:CycloneGU 1320:Guy Macon 1291:CycloneGU 1226:CycloneGU 1212:Guy Macon 1192:CycloneGU 1141:Wizardman 1080:prominent 699:this link 619:Guy Macon 355:Guy Macon 249:Guy Macon 145:See also: 107:Archive 5 102:Archive 4 95:Archive 3 90:Archive 2 85:Archive 1 50:consensus 3474:Fatuorum 3447:Fatuorum 3404:Fatuorum 3218:Fatuorum 3068::| TelCo 2945:Fatuorum 2843:Gimmetoo 2742:Fatuorum 2707:Fatuorum 2695:contribs 2683:unsigned 2670:Fatuorum 2576:Fatuorum 2526:Fatuorum 2475:Fatuorum 2416:Fatuorum 2386:Fatuorum 2293:Yaris678 2266:Fatuorum 2244:account. 2188:Fatuorum 2140:Fatuorum 2050:Yaris678 2028:Yaris678 1942:Yaris678 1907:Yaris678 1889:Yaris678 1826:Yaris678 1707:Yaris678 1656:remarks. 1623:Yaris678 1576:Yaris678 1554:Yaris678 1517:Yaris678 1506:Hi Slim, 1276:Cenarium 1260:Yaris678 1173:Yaris678 1013:Yaris678 708:There's 655:month.) 653:shortest 637:Yaris678 585:Cenarium 544:Yaris678 528:Cenarium 514:Yaris678 490:Yaris678 446:Yaris678 294::| TelCo 230:Cenarium 73:Archives 3542:request 3471:Malleus 3444:Malleus 3401:Malleus 3215:Malleus 3148:against 2942:Malleus 2739:Malleus 2704:Malleus 2667:Malleus 2573:Malleus 2523:Malleus 2472:Malleus 2413:Malleus 2383:Malleus 2263:Malleus 2185:Malleus 2137:Malleus 1903:changed 1066:Collect 393:Collect 330:Sithman 3485:Jeremy 3316:Ronk01 3269:Ronk01 3159:Ronk01 3133:Obsidi 3095:Jeremy 3012:mabdul 2975:Obsidi 2912:Jeremy 2897:mabdul 2801:Ronk01 2774:anyone 2757:Ronk01 2719:Ronk01 2687:Ronk01 2678:(UTC) 2650:Ronk01 2545:Jeremy 2505:myself 2427:really 2326:wanted 1982:boldly 1700:issue. 1445:Jeremy 888:McDoob 839:McDoob 333:VIII ! 3487:v^_^v 3097:v^_^v 3078:Ve :| 3028:: --> 2914:v^_^v 2871:Chzz 2600:: --> 2565:: --> 2547:v^_^v 2521:Why? 2515:: --> 2230:: --> 2129:: --> 2103:Chzz 1980:I've 1510:that. 1447:v^_^v 1340:: --> 1311:: --> 1206:Re: " 1118:; my 980:: --> 928:Chzz 915:: --> 813:Dumbo 759:Chzz 466:Chzz 304:Ve :| 226:WP:PP 194:asked 42:civil 16:< 3555:talk 3521:Ched 3461:talk 3433:talk 3418:talk 3367:talk 3352:talk 3337:talk 3322:talk 3304:talk 3290:talk 3275:talk 3255:talk 3240:talk 3201:talk 3180:talk 3165:talk 3111:talk 3073:NaSp 3049:talk 3026:talk 3024:< 2995:talk 2932:talk 2847:talk 2807:talk 2795:that 2783:Talk 2763:talk 2725:talk 2691:talk 2656:talk 2624:Talk 2598:talk 2596:< 2563:talk 2561:< 2513:talk 2511:< 2455:then 2437:talk 2403:talk 2395:will 2379:then 2365:talk 2335:talk 2297:talk 2253:talk 2228:talk 2226:< 2205:talk 2195:The 2162:talk 2127:talk 2125:< 2068:talk 2054:talk 2046:this 2044:and 2042:this 2032:talk 2010:talk 1995:talk 1961:talk 1946:talk 1926:talk 1911:talk 1893:talk 1872:talk 1860:very 1830:talk 1711:talk 1627:talk 1580:talk 1558:talk 1521:talk 1460:talk 1434:talk 1397:talk 1361:talk 1338:talk 1336:< 1324:talk 1309:talk 1307:< 1295:talk 1280:talk 1264:talk 1230:talk 1216:talk 1196:talk 1177:talk 1128:talk 1120:very 1106:talk 1088:talk 1070:talk 1055:talk 1040:talk 1017:talk 978:talk 976:< 961:talk 913:talk 911:< 866:talk 810:and 786:talk 751:then 749:And 732:some 728:some 662:talk 641:talk 623:talk 604:talk 589:talk 574:talk 565:less 561:full 548:talk 532:talk 518:talk 494:talk 450:talk 397:talk 374:talk 359:talk 338:☻☻☻ 320:and 318:here 299:NaSp 276:talk 253:talk 234:talk 214:talk 137:, a 40:and 38:calm 3551:Wnt 3514:not 3509:new 2969:not 2751:you 2322:was 2048:. 1885:it. 1696:PC. 1570:to 862:Kww 600:Kww 322:now 288:all 133:on 3557:) 3547:do 3527:? 3524:: 3463:) 3435:) 3420:) 3369:) 3354:) 3339:) 3306:) 3292:) 3257:) 3242:) 3203:) 3182:) 3155:) 3127:if 3113:) 3051:) 2997:) 2934:) 2877:► 2849:) 2697:) 2693:• 2439:) 2431:-- 2405:) 2367:) 2337:) 2299:) 2255:) 2207:) 2164:) 2109:► 2070:) 2056:) 2034:) 2012:) 1997:) 1963:) 1948:) 1928:) 1913:) 1895:) 1874:) 1832:) 1713:) 1629:) 1582:) 1560:) 1523:) 1462:) 1436:) 1399:) 1363:) 1326:) 1297:) 1282:) 1266:) 1232:) 1218:) 1198:) 1179:) 1130:) 1108:) 1090:) 1072:) 1057:) 1042:) 1019:) 963:) 934:► 898:93 893:AU 868:) 849:93 844:AU 835:-- 788:) 765:► 664:) 643:) 625:) 606:) 591:) 576:) 550:) 534:) 520:) 496:) 472:► 452:) 399:) 376:) 361:) 278:) 255:) 236:) 216:) 3553:( 3482:— 3459:( 3431:( 3416:( 3365:( 3350:( 3335:( 3302:( 3288:( 3253:( 3238:( 3199:( 3178:( 3137:n 3135:♠ 3109:( 3047:( 2993:( 2979:n 2977:♠ 2930:( 2885:) 2845:( 2785:) 2781:( 2689:( 2626:) 2622:( 2542:— 2450:) 2446:( 2435:( 2401:( 2363:( 2350:) 2346:( 2333:( 2295:( 2251:( 2203:( 2160:( 2066:( 2052:( 2030:( 2008:( 1993:( 1959:( 1944:( 1924:( 1909:( 1891:( 1870:( 1828:( 1709:( 1625:( 1578:( 1556:( 1533:. 1519:( 1458:( 1432:( 1395:( 1359:( 1322:( 1293:( 1278:( 1262:( 1228:( 1214:( 1194:( 1175:( 1126:( 1104:( 1086:( 1068:( 1053:( 1038:( 1015:( 959:( 864:( 784:( 660:( 639:( 621:( 602:( 587:( 572:( 546:( 530:( 516:( 492:( 448:( 395:( 372:( 357:( 336:! 274:( 251:( 232:( 212:(

Text is available under the Creative Commons Attribution-ShareAlike License. Additional terms may apply.

Knowledge (XXG)

talk:Pending changes/Request for Comment February 2011 - Knowledge (XXG)

Index