Knowledge talk:WikiProject Conflict Resolution

2297:

authority. We do lose a great number of editors due to conflicts that are not so much about content as one editor feels like someone else is dismissing them or simply being rude. This project has no authority to offer ultimatums, it could simply provide neutral ground. An article talk page isn't appropriate since these problems are often bigger than one article. The talk page of either editor isn't appropriate, as there should't be a "home team". Often, I've talked with editors on my talk page in the same manner, just discussed, get them to agree or simply calm down. Often, just talking it out works. Sometimes, no amount of talking will do and you just want to get them to agree to avoid each other. It shouldn't be seen as a board, but as a way to AVOID the boards, as fellow editors helping each other. There is a risk of drama, like with any venue you discuss personality conflict, which is why the system needs to develop. Realistically, if there is a risk of drama here, that drama would just be playing out on someone's talk page, so you aren't creating it. Maybe it will work, maybe it won't, I have no idea and no dog in this hunt, but I think the concept is worth exploring. WQA didn't work, but neither does ANI for minor personality clashes. THAT is a place that tends to make small problems bigger. We should encourage novel ideas and solutions, and be open minded, and try to be part of the solution. Just saying "it won't work" is easy but not exactly brave or bold.

724:

and conduct (see below). IMHO, as much as anything the real problem is that the DR policy page is itself a dog's dinner. There's no vested community standing behind it to keep it up to date and coordinated with the changes at the various DR projects — which on the Knowledge geological time scale are fairly continuous — and it's often out of sync both in general philosophy and in detail with them. Moreover, it's really more of a general guidance page (unfortunately, since it doesn't do a very good job of it) than it is a policy page and does not do much (if any?) of the kind of things or take the kinds of positions that policy pages ordinarily do. The fact is that in my own head I don't much think of the conduct-DR processes you list as being part of DR and I've become unconsciously lax in just saying "DR processes" when what I really mean is "conduct DR processes". Thanks for the trout and I'll be more careful in that regard in the future, but I stand by the substance of what I said above, i.e. that I don't think that anyone

568:@Amadscientist - It sounds like you are contemplating a new dispute resolution process ... apparently aimed at resolving large-scale conduct-oriented conflicts between editors. S. Zhang spent a lot of time studying the DR process and - after a lot of work - was successful in streamlining the overall DR process by eliminating MedCab and Wiketiquette. Creating a new process so soon after eliminating two is a bad idea. To go forward with this, we need to make the proposal within an RfC and publicize the RfC at the Village Pump and Centralized Discussions. Creating a new conduct-oriented process is a big deal, with lots of ramifications (e.g. Will admins be involved? Will they issue blocks? Will this process be added to the DisputeResolution sidebar? How will this process differ from the processes that were eliminated? How will this process differ from AN or ANI? Will this new process dilute the DR effort by spreading volunteers thinner over more forums?) -- 533:

content. If the main issue is a content dispute it would be defered to another DR process like DR/N or RFC etc. This project is for helping the community deal with severe conduct and conflict, not just any random fight when two editors can't get along. We still have 3.0 for that and we still have all the other DR processes. Project DR itself is simply not about conduct and this project is. Many disputes are not actual conflicts. They just don't agree on content. That is a normal part of the Knowledge structure. "Conflict" is when editors cannot resolve a dispute and conduct becaomes a bigger issue than the original dispute. This is just one area that has not been sufficiantly covered by the DR process without going all the way to arbitration and there should be something before editors need to take that route.--

588:

does not require an RFC process to begin. Just like articles can be created using the AFC process, WikiProjects can be proposed first at the Project council page, but this is not a requirement. WP:WER was a bold creation as I believe was WP:DRP. Yes, this project and subprojects will differ from other "processes" that were eliminated like the cabal that didn't exist and exists even less now, as well as the defunct Wiketiquette board, which, by the way, was a civility enforcement page...and I think we all agree civility is not an issue that can be enforced in that manner. But this is not a civility project. It is a conflict resolution project and is designed to help eliminate old and new conflict issues through resolutions everyone can live with in a non binding way for issues that go beyond simple incivility.--

663:"minor conduct issues." Current DR processes, by which I mean 3O, DRN, MEDCOM, and the content flavor of RFC (that is, vs RFC/U) do not handle, and will ordinarily reject consideration of, disputes which are wholly or primarily conduct disputes. If cases are accepted which have an incidental conduct component, that component is ordinarily not addressed other than to tell the disputants to avoid continuing it as part of the DR process. I don't think that Amad or anyone else is saying that current DR processes are "only" for content disputes. And if the newcomers listening here have taken the idea that current DR processes will not accept disputes which have 1749:. I don't exactly understand what the project is trying to accomplish that WPDR cannot do, or indeed isn't doing already. In an ideal world, it'd always be ideal for us to prevent disputes/conflict from happening in the first place, but with the nature of Knowledge and it's openness to editing, this is difficult to achieve. Arming our editors with ways they can resolve disputes themselves I think is the best result we can hope for. Some have suggested this could be a forum for directing disputes to the correct forum, however this is something that the 1393:"Hello. I am a dispute resolution volunteer here at the Knowledge Dispute Resolution Noticeboard. This does not imply that I have any special authority or that my opinions should carry any extra weight; it just means that I have not been previously involved in this dispute and that I have some experience helping other people to resolve their disputes. Right now I am waiting for everyone to make their statements before opening this up for discussion. in the meantime, I encourage everyone involved to read the 1240:

disputes to the correct venues, a place for like-minded editors to discuss conflict resolution strategies, a neutral forum for grievances to be debated under pre-agreed conditions, a Wikiquette Teahouse, a "non-content only" DRN - there are lots of avenues this project could take, and if it does them well, it could be a balm to the fractured Knowledge community. If it crashes and burns, well, I'll happily dust myself off and apply Savlon to the affected areas; on balance I think the ride might be worth it.

321:

who have been involved in long standing disputes. For them going to ArbCom would lead to a (topic) ban. DR won't work well if the conflict has festered for too long, so we need something that can address behavioral issues but not in the way we do this at ArbCom or AN/I. An example could be the climate change case that was poorly handled by ArbCom. One could argue that topic banning the most prominent editors from both sides did work, but that's like amputating a limb to cure an infection.

2500:

examples from the editing history of a talk page where one can see how a discussion that is in principle ok. to have, strays off course. Then at Arbitration these are used as evidence against some of editors, so it is used in a passive way to passs judgement on people. I suggest making active use of this. Just go back at the time when everything was still ok. and then ask the involved people to start arguing from that point onward, but now they should do their best to stay on topic.

148: 130: 1816:"...the purpose of this project is to pick up where the DR project leaves off. Mainly with editor conflict and conduct. This is not a civility enforcement taskgroup. We are not attempting to make people act nice to each other or take on issues of simple name calling and incivility. Our goal is to provide tools and venues where editors can help mediate over conflicts that may not even be over content with the goal of improving the quality of experiance for everyone." 1473: 2150:(as happens in DRN) great progress is made. Forcing editors into a 100% content venue like DRN can be a transformative experience for combative editors. Conversely, giving them a venue to continue venting about behavior just enables their bad conduct. Forums that address behavior issues (like WQA) end up promoting drama and accomplishing ... nothing. But for some reason everyone wants to create behavior-oriented forums. Not sure why. -- 913:

that. I agree wholeheartedly that all this should have been discussed beforehand, but that did not happen. I don't mean to imply that this was done in anything but good faith and an honest attempt to help, but I think some folks are being a bit naive if they think resolving behavioral disputes is so easy that all you have to do is say "here we are, bring us your dispute" and somehow they will be able to resolve it.

2576: 99: 2249:

others; everyone (myself included) wants to rebuild things from scratch "my way". But that is not best for the overall WP community. We don't have an employer who can tell us "knock off that duplication: consolidate!". We have to tell that to ourselves. I would support keeping this project (as a brainstorming effort) if it were moved to be a subproject (subpage) under the existing DR project. --

2215:

discussion with volunteers encouraging ways to avoid continuing a fight. This would not be a location to discuss content however as we are not concerned with content here and would simply direct editors to the proper content venue. Lets se...how many content venues are there? How many conflict venues do we have? Seems to me that we can at least take a good look at things and see what needs to be done.--

2485:

wound? I still like this idea in some form though. A conflict incubation page perhaps, where editors have an opportunity to take their conduct and conflict discussions away from the article that it began at to keep the talk pages flowing and uninterrupted. Thanks Iblis. There is some potential even if I don't necessarily agree entirely on the concept I think there is something there to consider.--

1641:

content dispute and conflicts between editors where topics are heated and conduct has become an issue between multiple editors even before or just after a dispute has arisen. There have been a number of ANI conflict discussions pertaining to a number of editors, situations and topics where editors are engaged in long term conflict over a number of pages and articles for many different reasons.--

994: 835:

re-inventing the wheel: instead it should explicitly start with Zhang's research & statistics gathered over the past year, and with the recent process eliminations (as TM lists above), and build on that background. And (3) Creating a new process is a big deal. The first thing that should be done is create an RfC and a place prominent notice at WP:Centralized Discussions. --

2469:

relevant pages to some conflict resolution workshop area, and then ask the disputants to start editing from there. This allows one to start over from e.g. a time before the conflict started. One can also re-run heated disputes, try to give the involved editors instructions on how to avoid problems and see if re-running an old argument leads to a better outcome etc. etc.

792:

disputes that don't require admins to be involved. As in two people are arguing about conduct, they can come here and get some impartial mediation on the dispute with, perhaps, voluntary sanctions (too strong a word?) on both parties. If that works, great, if not then it gets kicked up the DR chain. I would see this as being on a similar level to 3O/DRN in that respect.

1863:

another project due to simple confusion and the idea that this "should have been started under the other project". I believe there are inadequate ways to deal with an issue that is certainly plaguing Knowledge. I believe we should be given the chance and opportunity to prove ourselves. If this works then great, if not, as Yunshui stated:

1756:

have been busy with my duties on the Wikimedia Australia chapter, but I think I have some sort of balance now so I will be returning shortly and getting back to work on dispute resolution. Please don't take what I say as criticism, I just feel we can accomplish more by centralising all our efforts into one place. Regards,

638:

there are two other editors on this page, relative newcomers apparently, that are now repeating that "dispute resolution" is for content only. Is it your intention to limit the scope of "dispute resolution" to content-only disputes? Or when you wrote "dispute resolution" did you mean "dispute resolution noticeboard"? --

2036:

for people to get along. This is no different than many of us do already, but it provides a neutral ground to do it in. I'm not sure what the exact end game will be, but there is room (and a need) for a place for fellow editors to discuss conflicts before they rise to the level that requires admin intervention.

1120:

authority beyond that of a regular editor. Likewise the project's decisions should only be binding within its own space. If participants want to be voluntarily be bound by outcomes elsewhere, that is probably ok. Anything beyond that would be a major new process and require a great deal of community scrutiny.

2542:

Hello there! As you may already know, most WikiProjects here on Knowledge struggle to stay active after they've been founded. I believe there is a lot of potential for WikiProjects to facilitate collaboration across subject areas, so I have submitted a grant proposal with the Wikimedia Foundation for

2035:

the admin boards if possible, then it is not only a good idea, but it would be 100% in line with the goals of administrating at Knowledge, that is to handle the problem at the lowest possible level. This would be 100% community level, with no authority or sanctions, but instead a way to explore ways

1847:

article which appears to be an after thought and has a single reference. Is it possible the WP:DRP should be renamed if there truly are no venues to deal with groups of editors in a conflict not involving content directly? If indeed there is only the huge gap between individual conduct with RFC/U and

1669:

No, I am not saying a I can't. I am saying I am not comfortable discussing individual editors or using them as examples in a general discussion of this type to hold them up and identified for ridicule or embarrassment. Now, if you would like, I can ask specific editors permission but cannot guarantee

961:

new projects of any kind to suck at first. The answer, however, is not a merge or an RfC. The answer is either fixing the problems yourself or alerting Amadscientist about specific wording that needs to be fixed. He tends to take that sort of constructive criticism very well and usually comes up with

912:

on a project that just started yesterday. So, yeah, I opened an RFC because I think it is a dangerous thing for one person to just create a new area for dispute resolution, declare what its goals are, and claim it is ready to start resolving disputes without even giving us a clue how it intends to do

320:

Yes, but then things have gradually changed here in recent years, the ArbCom system we have is not an ideal venue for disruptive problem editors to raise their grievances. That's a good thing w.r.t. the problems posed by such editors, but there are always editors who don't fit into that category, but

2080:

Noleander makes a very good point with his "Report from the Future!", especially the "Editors choose CRN instead of DRN because CRN will permit discussion of the other editors' wicked behavior." bit. Take a look at the Adolph Hitler case. Progress is being made on article content, but only because I

1797:

I simply used your opening at the DR project as an example to start this project with modifications, that is why the goals look similar but that alone does not mean the projects cover the same thing. They don't. Conflict and dispute are not the same thing. One thing I must ask, if you decline I will

1588:

There seems to be an assumtion that I opened this RFC in an attempt to destry this project before it gets started. While it is possible that some users feel that way that was not my intent at all, if my goal was deletion of this project I am fully aware of how to file an MFD and would have done so.

1139:

I recommend that we back off and let this project grow. There are two things I know about Amadscientist. First, he is comfortable with trying something new even if it goes against conventional wisdom. Second, he is comfortable with killing it if it becomes obvious that it isn't working, Sort of like

939:

The way you talk about the doors being thrown open by one user and the project being declared open for business without any prior discussion, you make it sound as if that is a bad thing. It isn't. If you think that creating a WikiProject requires any sort of prior activity or any particular quality

757:

that proposal and the matter died, leaving us with a gap where WQA once stood and a bad entry, it appears, in the Conduct section of the sidebar. Whether that gap needs to be filled, and whether it is possible without creating a new dramafest, is a matter which is worthy of some discussion. I'm just

723:

includes some conduct processes. In light of the purpose of that sidebar (as opposed to the DR policy page itself), that's probably a good thing as a general guide to where to go to find things (and it does break them down, correctly, into content vs conduct, except for listing 3O under both content

587:

you mean an actual process in the same manner as DR/N. Right now we have not advanced that far, but I am very familiar with the route Zhang took and have been involved with some of those discussions and consensus. I am using Steven Zhang's example here by beginning with a WikiProject, something that

499:

The principle applies to all of Knowledge. It starts somewhere. This isn't a process or even a proposal for a process. We already have processs in place, but what we lack are some venues for this issue. This isn't a noticeboard, although a proposal for one isn't a bad idea and may be made. This is a

422:

processes ... which include both content and behavior issues. They key point here is that WP has too many things to do and too few editors. The existing DR project is already gathering dust ... does WP really need a second similar project? Resources are spread thin already. Better is to take our

2248:

of the DR project is that it dilutes WP's limited resources. Say there is a new editor that wants to help out: they flip a coin between DR project and CP project, and choose the CP project. That is one less editor working under the DR umbrella. It is human nature to overlook efforts created by

2229:

There is always the possibility that this project will not need to add any additional major subpages and this can be a simple discussion page of ideas, suggestions and encouragement to resolve conflicts quickly. Possibilities seem to make a lot of people nervous. I don't know why that is, but there

2195:

Yep, I agree. Sort out conduct issues between yourselves on a talk page. Many conduct issues are a result of a content dispute that's gotten out of hand. If it's just editors causing trouble for the sake of causing trouble, it should either be addressed by an RFC/U or AN. I don't see how having the

1740:

redirects to. It does fall under the banner of dispute resolution, they are really one and the same thing. While the dispute resolution wikiproject has indeed been inactive (as have I), I think that the efforts to reform Knowledge's dispute resolution processes best be served by expanding the scope

880:

the first thing that should be done. Brainstorming, discussing, deciding whether to proceed, and deciding what questions the RfC should ask come before any RfC. You should not take the square peg of a WikiProject that was created to talk about what to do and pounding it into the round hole of a RfC

849:

If we want to create new policies then we need community wide discussions. But if we try to formalize things too much before actually trying out something, chances are that after a lot of effort things won't work. It's better to try out things informally (we should, of course, study the experiences

637:

All of those pages embrace all disputes: conduct & content. None of those are limited to content only. I think you are confusing the umbrella term "dispute resolution" (DR - for all conduct & content disputes) with the "Dispute Resolution Noticeboard" (DRN - for content only). In fact,

2519:

The dispute resolution system, AN/I and ArbCom system we have, tend to simply accept that certain people are not suitable to be active in certain areas, and then we impose topic bans, or interaction bans. But then these people never learn how to change themselves, they are simply told to stay away

1832:

I think it important to mention that the redirect that was brought up has nothing to do with either projects. It was created in 2007 and was in regards to clarification due to the existing article's title which was started in 2004. However when you look at what the Dispute Resolution page began as

1755:

would accomplish (that's a prototype, I still need to do some work on it but you get the idea.) I really do appreciate the effort to move forward with reform, but I do think we would serve the community better by consolidating our efforts into one location (the DR project). In regards to myself, I

1735:

I've thought about this project for a while, and I do applaud innovation and new ideas. The dispute resolution community is an important one and anything we can do to make it a more pleasant experience for editors, I think we should consider doing. However, I don't think it wise for us to reinvent

1465:

I don't understand the comment about "pushed for radical ideas". In the past, I have proposed and implemented an assortment of ideas that have garnered the support and implementation by a number of editors, including the WP:WER User statement (that was copied by numerous, established and respected

1442:

came from) I'd like to hear a concise explanation as to what this project expects to achieve that is not already covered by WPDR? If editors wish to form a task force inside WPDR for the express purpose of dealing with conduct disputes, that's one thing, but to do it in this way almost feels like

1239:

Nice image, Guy. I agree; it's worth hanging onto this to see how it develops. I too was a bit skeptical at first, and checked out what Amadscientist's aims were before being sufficiently enthused to sign on. I'm of the opinion that this could develop into something worthwhile: a hub for directing

2386:

I don't see how anyone is being forced to oppose anything, the purpose of this RFC is to clarify how this is intended to work, not to make people oppose it altogether. Every time I open an RFC I seem to end up being accused of being able to practice mind control. I wish, it sure would make things

2085:

suppressing them making accusations against each other (some of them far worse than others, of course). I was sort of assuming that if there was a forum where they could do that it would reduce it at DRN, but it did not occur to me that they might just abandon DRN if another noticeboard gave them

2014:

I'm assuming the purpose of the project is to deal with personality disputes. Any content disputes would go to DRN. Right now, WP:WQA is defunct and many long time disputes are not appropriate for ANI (unless we are trying to cause more drama) nor are they so cut and dry as to justify a RFC/U.

1640:

That would be a matter of consensus of editors to determine here once we get started. I don't feel comfortable discussing editors outside of any particular mediation attempt, but in general: conflicts that have not been resolved after a dispute resolution, conflicts that have nothing to do with a

437:

I find dispute resolution to be overbearing. And not many editors want to take care of things like this. This wikiproject may have similar goals, but the process is completely different. For example, this wikiproject can help approve guidelines, policies, and essays that could help conduct issues

2509:

We then don't care primarily if that discussion is useful for editing Knowledge, instead we should teach people how they can have very strong disagreements, and still avoid such disagreements from becoming personal. We just observe everyone and give them feedback on what they are doing right and

2499:

I think (both from real world experience and my experience here on Knowledge), that the reason why some people tend to get into conflicts, is because they are not good at keeping a legitimate discussion from straying off course and degenerating into exchange of insults etc.. There are often many

2214:

The project will sort out a number of these issues, such as the best venue for any real discussion between conflicted editors, whether that be here, on another subpage or their own talk page. Below we have started discussing ideas such as a conflict incubation page where editors can continue the

1862:

My point is just this. I believe there is a difference between the two projects. I believe they can exist simultaneously. I believe they have differing goals and scopes and can be separated even further by consensus but the basic concept is appropriate and need not be merged or incorporated into

1299:

Just like Project Dispute Resolution, no experience is needed and no authority is granted or implied, as we are a simple collaboration and not a noticeboard. Even at DR/N and Knowledge in general, no experience is needed, no special powers of authority are granted or suggested. We learn and grow

532:

Like Project DR, which was designed as a collaboration for editors to help resolve small content disputes with only minor conduct issues, this project focuses of the conduct and conflict between editors that may or may not involve content, but as with DR/N, we will allow some small discussion of

2591:

is now live! In our first phase, we are focusing on research. At this time, we are looking for people to share their experiences with WikiProjects: good, bad, or neutral. We are also looking for WikiProjects that may be interested in trying out new tools and layouts that will make participating

2484:

Would that not make the editors feel as if they have to rehash old disputes? If the issue is strictly a content dispute we would want to encourage the use of the DR/N-RFC process. If this is about a continuing conflict after a content resolution, would this not encourage re-opening the original

2296:

I want to add one more note: this isn't a noticeboard. Noticeboards require community authorization. This is a Wikiproject. I don't think there is a clearly defined structure yet, and Amadscientist has set this up as a project to coordinate with WP:WER. The key is simply to not overstep the

1350:

As a Wikiproject this in itself has no effect on the established process of RFC/U. The RFC/U process is to comment on an individual. This project is not aimed at individuals but the community as a whole. It is neither a prerequisite nor a substitute for any current process. This is not civility

1119:

Baring a large scale discussion, and strong consensus to the contrary, members have no special authority outside the project's own space. With a few very small exceptions, no one but Arbcom, and permissions holders to the extent the act cannot be carried out without the permission, have special

810:

This is something we really need. As Cabe points out, conduct disputes are treated at the Admin level and can end up at ArbCom. The problem here is that often there is little room to look also at content (because Admins must stay uninvolved). Consider e.g. how a sort of general sanctions regime

699:

has an entire subsection on "conduct disputes". The suggestion (made earlier) that "current DR processes are only for content disputes" is not accurate: what we tell users is "RFC/DRN/3O/Mediation are for issues that are primarily content disputes; if you have a conduct issue, go to RFCU,

582:

Nothing has been proposed as yet. This is a collaboration of editors interested in conflict resolution, a WikiProject similar to WP:DRP, WP:TH and WP:WER. The question about admin is answered as simply, they may be involved at whatever level they wish just like at the DR project. Creating a new

2265:

This isn't the best argument to make. Knowledge is not a paper encyclopedia and our resources are not so limited to make that even close to being a concern. Your argument against this project is noted but has had no effect on my firm belief that it is an appropriate use of project space and is

1607:

I do not believe your intent is to destroy the project. However I do believe the RFC has possibly confused some editors. To answer your concern, this project is designed to discuss ways to resolve conflicts between editors that may not even regard content at all, have gone past a resolution to

1527:

The purpose of this project is to address concerns of conflict between editors that may or may not relate to a specific content dispute or has gone beyond a resolution of the original content dispute. This project pertains to the needs of the community to resolve issues between editors causing

791:

I'm also somewhat supportive of this project. I'm interested to see how it fits and will happily be involved with it. From my perspective it seems that the conduct dispute avenues go straight to admin level intervention and up (ANI, RfC/U ArbCom) while this could fill a gap for smaller conduct

2468:

I mentioned this possibility a long time ago during the climate change ArbCom case. Suppose that you have a number of editors who frequently are in conflict with each other on a limited number of pages. Then because we preserve the entire history of the pages, one can copy old versions of the

2105:

I should have a Google Hangout call with Amadscientist later, but if I understand that this project is intended to be some sort of WQA replacement, then I am very worried and would strongly oppose the idea. I don't think that's what it's intended to be (I am still not clear on the aims of the

834:

object to is: (1) the phraseology used in this new Conflict Resolution project is contradictory to phraseology used in all other DR pages, where "dispute resolution" is clearly an umbrella term that includes conduct/behavior issues. (2) This project appears to be starting from scratch,

283:

Perhaps one could focus more on content and the other (this one, due to the difference in names — dispute vs conflict) more on conduct. But the bigger problem, I think is that those who don't care about DR don't care about it and those of us who do care about DR spend our available time

1160:. If we can develop a way to resolve conflicts relating to user behavior without resorting to the torches-and-pitchforks route or kicking it upo to ArbCom I am all for it, but what we have here so far is just vagueries, it doesn't seem like anyone would know what to actually 2178:

I think Noleander is basing his arguments on a number of false premises. The main one is that the project will enable bad conduct. I disagree with that but mainly because its a non argument. Ever venue seems to attract bad behavior in just giving people a venue to express

260:

Reading the project page, I get the impression that what is meant by "conflict" is something more serious than just a severe editing dispute. But such severe problems do end up at DR, or at AN/I or at ArbCom while it may be dealt with using a different sort of DR process.

1730:

Before I go on, I want to make something clear: I don't want my opinion to be weighed more heavily solely because of my activities with dispute resolution over the last year as a Wikimedia Fellow. That said, do look at the research I undertook and consider how it applies

484:

As a general rule, boldness is a fine quality when it comes to editing content, but the same principles do not apply to WP processes, which normally should not just be made from whole cloth by one user who just decided one day that we needed yet another noticeboard.

1155:

If this were a content project I would agree 100% and we probably would not be having this discussion at all. But this project deals with user behavior, a very contentious area of WP dispute resolution, without providing any real specifics of how it would actually

728:

saying that "current DR processes are only for content disputes". As for your final point about creating more processes & projects, I may very well agree with you and that's the reason I began my last post about perhaps not being on board with this new project.

1164:

if and when a dispute is brought here other than draw attention to it. Maybe that is all it will do, I don't know but the fact that it is structured as a project means it is by definition a collaboration that should be inviting rather than resisting outside input.

2510:

wrong, give instructions on how to avoid problems and then we start again. If they do better, we can take another starting point (this doesn't necessarily have to be a historic one, we can invent something) and then see if they can stay out of trouble there too.

1493:

I don't believe "radical" is accurate. About projects, Knowledge WikiProjects are not authorized or given official charter. Any editor may create a WikiProject. This was touched on last year (and several other times elsewhere) this month in the thread:

1589:

I just think it makes more sense to have broad participation in the development of any project/process/wahtever it is that aims to resolve interpersonal disputes, and I think a bit more specificity regarding exactly what this project would actually

2520:

from the problem areas. Of course, we do have to keep problem editors away from the areas where they cause problems, but that doesn't mean that while they are under some (topic) ban, they can't on a voluntary basis engage in conflict resolution.

1179:

I would know what to do if and when a dispute is brought here. I would respond be explaining that this is a WikiProject that works on improving how Knowledge resolves disputes, not a place to bring individual disputes. Then I would refer them to

1045:

Note from opener of RFC: Just to be clear, all that is being looked for here is a greater degree of community involvement in the development of this project, which up until now has been mostly the creation of one user. I have listed this RFC at

1558:

My opposition to this RFC is partly because the questions asked in the RFC seem to presume that this is something more than just another editor-interest project and partly because it's a less than desirable process, the favored process being a

2543:

the "WikiProject X" project. WikiProject X will study what makes WikiProjects succeed in retaining editors and then design a prototype WikiProject system that will recruit contributors to WikiProjects and help them run effectively. Please

1081:

The phraseology used in this new Conflict Resolution project is contradictory to phraseology used in all other DR pages. Throughout DR pages, the phrase "dispute resolution" is clearly an umbrella term that includes conduct/behavior

1085:

This project appears to be starting from scratch, re-inventing the wheel: instead it should explicitly start with Zhang's research & statistics gathered over the past year, and with a survey of the recently eliminated processes

907:

Trouble is, the doors were just thrown open by one user and the project was declared open for business, apparently without any discussion whatsoever. I mean, look at the main page. It indicates that the project's goals are

1001:

This new WikiProject was just opened with the goal of "addressing the ever changing needs of the general community, and provide a positive environment to discuss ways to resolve conduct/conflict issues between editors."

224:

project is a bit dormant: only a few posts have been made on its talk page in the past 6 months. Maybe the community's limited resoruces would be better spent reviving that other project, rather than starting a new one?

2266:

supported by enough editors to satisfy a standard for community support. I can't help wondering if now some are just nervous that this might become more used than the other project. I don't even wish to reply to that.--

1836:, you can clearly see that it was actually meant as conflict resolution and not the more specific term of dispute resolution. WP:DRP was started 1 year and 4 months ago. Even after three days into it's creation it had 1563:

nomination. If I felt more strongly about this project being undesirable, I might file such a MfD, but I don't. I might (or might not) at some point in the future, but I don't feel the need at this point. Best regards,

2196:

same discussion on a noticeboard between two editors is any better than having it on their user talk page. Conduct noticeboards just create drama, and most discussions (like at WQA) turn into poo-flinging matches.

1798:

understand, but you said: "that WPDR cannot do, or indeed isn't doing already" other than arbitration and RFC/U is there another venue that deals primarily with conduct and conflict outside of content disputes?--

500:

collboration of editors interested in conflict resolution between editors and ways to overcome them and move past them to improve the encyclopedia, the experiance of editors and the retention of contributers.--

1528:

conflicts related to conduct and in some small amount to content. While the projects main purpose is not content, some content may be discussed in possible relation to the lasting conflict between editors.--

39: 1655:

Are you saying you cannot give a single example of an actual conflict that would fall within the scope of this project (and outside WP:DR or ANI or RFCU)? Feel free go back several years if needed. --

1622:

AMS: I would help others understand your intention if you could provide concrete examples of actual conflicts that are within the scope you envision for this project (and are outside the scope of

815:

look at conduct (and there was plenty of bad conduct to deal with), that can be exploited by editors, and the whole thing degenerates into a game where some editors try to get other editors banned.

351:. That hypothetical process is probably not a great idea, given the simplifications that the DR process-system recently gained thanks to S. Zhang's research (namely, eliminating the underutilized 2086:

what at least some of them so desperately crave. We can discuss the idea of a behavior noticeboard, but we really need to think about Noleander's argument before we actually turn anything on. --

1962:

2026: A new editor perceives that there is a void in the dispute resolution field, and - rather than enhance the existing Dispute Resolution project - creates a new project to fill the void.

881:

that is designed to gather wide community input after you have a pretty good idea about what you want to do. Frankly, I don't need an RfC or anyone's permission to start or join a WikiProject.

1332:

This is a collaboration of editors with a shared interest. Consensus will determine such things as "Suggestions to avoid conflict", and other possible ideas as mentioned above by User:Yunshui.

2244:

I, too, am supportive of brainstorming. If this effort had been created as a subproject of the existing DR project, I would be supportive of it. The problem with a new project that is a

1684:

How can this project define its scope if actual conflicts cannot be discussed? Are you suggesting that all project discussions will revolve around hypothetical, abstract conflicts? --

159:, a collaborative effort to improve the coverage of efforts to improve editor retention on Knowledge. If you would like to participate, please visit the project page, where you can join 2063:

Yes, content dispute would be referred to DR/N. This project focuses on editor behavior with each other. It is not a forum to continue a fight, create drama, or continue the conflict.--

1893:

April 2013: the CRP creates the Conflict Resolution Noticeboard (CRN) - The CRN is for disputes that primarily involve user conduct. The CRN's layout & processes are copied from

1698:

I am sorry, but I will not discuss actual editors to satisfy your questions. This projects scope does not require a discussion of actual conflicts between real editors to be defined.--

1068:- I have no objection to starting a discussion about whether or not WP needs a new process/forum/venue for handling conduct disputes. But there are a few problems with this project: 749:, not because I thought much was settled at that dramafest but because it provided a place for people to vent. At the same time, I wasn't utterly against it, and it was closed with 239:

That's exactly the thought that I had when I saw this. It's great that Amadscientist is doing this, but it does seem redundant with WPDR. Perhaps some sort of merge is in order? —

741:

DR processes is one worth talking about — I'm not saying that we ought to add any, just that we ought to talk about it — but I'm not sure we need a new project for that purpose

656:

on board with the creation of this project, I do think that Amad is correct in the quote, though I would suggest that "incidental conduct issues" might be a better phrase

1950:

2018 to 2022: Dispute resolution evolves into a mish-mash of confusing, overlapping forums. Some editors recognize this, but don't have the time or authority to fix it.

452:

Lucia: I cannot understand the points you are trying to make. When you say you find DR to be "overbearing" which DR processes are you referring to? Do you consider

2596:! Note that this is an opt-in program; no WikiProject will be required to change anything against its wishes. Please let me know if you have any questions. Thank you! 1140:*cough* a Mad Scientist. This is closer to the way Knowledge started out. I say let it grow and see what the harvest is rather than setting fire to the seedlings. -- 2669: 1285:

Yes, the community seems to desire this project based on the number of participants in just the initial phase of development with membership and interest growing.

464:

both shut down recently due to lack of participation? Are you aware that the effort to shut them down took a large amount of resources and time? When you say

1495: 1212:

That was more intended as a response to the above comment than an accusation, obviously it is far too soon to make any such broad statements about the project.

423:

efforts and focus on the existing DR project. For instance, if you want to do some page layout work, perhaps you could visit the DR project and work on it. --

2100:

Speculation with misinterpreted information is not an argument. This project seems to have hit a nerve of what if it replaces ____________(fill in the blank).

1373:

Re: "Even at DR/N and Knowledge in general, no experience is needed, no special powers of authority are granted or suggested", when I help out with a case at

2637:. If your WikiProject and its taskforces have newsletters (even inactive ones), or if you know of a missing newsletter (including from sister projects like 160: 74: 2126:

Just got back, and haven't had time to look into the video portion of the idea. But I should note that I have stated this isn't a replacement for WQA.--

1940:

2017: Lots of drama and discussion at CRN. No enforcement of improper editor behavior, though, because admin actions continue to be managed within

1742: 700:

ARBCOM, AN, or ANI". It is all under the DR umbrella. Creating more processes & projects will just dilute the limited resources we have. --

24: 2424: 2364: 2028: 1894: 1623: 1521: 1517: 1101: 1075: 620: 221: 202: 195: 850:

they have at DR). If the community thinks positively about what we've actually achieved they will want to include what we have in the policies.

2311: 2050: 2019:

offers a light weight way for the community to help resolve problems, this seems to have the same potential for individual conflicts where the

155: 135: 335:

Can you clarify your point? Are you saying that WP should create a new DR process? To supplement the existing processes already outlined in

830:

I have no objection to starting a discussion about whether or not WP needs a new process/forum/venue for handling conduct disputes. What I

630: 557: 80: 891:

Groups of like-minded editors may start new WikiProjects at any time and are encouraged, but not obligated, to propose them before doing so.

1078:

which is intended to include conduct disputes (as well as content disputes). Creating a second project spreads limited resources too thin.

2401:

I wasn't directly referring to you. In fact, at the time I made that comment, I'm not sure that I even knew that you had opened the RfC.

2555:(Also, sorry about the posting mistake earlier. If someone already moved my message to the talk page, feel free to remove this posting.) 2603: 2307: 2046: 348: 1100:

I recommend that this project be deleted; and that this discussion about a possible new process/forum for conduct issues be moved to

344: 607:

Project DR, which was designed as a collaboration for editors to help resolve small content disputes with only minor conduct issues

1091: 746: 461: 356: 2641:), please include it in the directory! The template can be a bit tricky, so if you need help, just post the newsletter on the 1917:

July to Dec 2013: Editors choose CRN instead of DRN because CRN will permit discussion of the other editors' wicked behavior.

1444: 1434:. I observe that the project's founder has, in the past, tried to push radical ideas a specific DR venue talk pages (such as 799: 20: 1292:

Do "members" of this project have any special authority and are they expected to have any experience in dispute resolution?

1011:

Do "members" of this project have any special authority and are they expected to have any experience in dispute resolution?

2585:

You may have received a message from me earlier asking you to comment on my WikiProject X proposal. The good news is that

1737: 1250: 69: 548:

Indeed, conflicts are when editors cannot resolve a dispute and conduct becomes a major issue than the original dispute.

2416: 2356: 2320:

I really like this idea. WP has been obsessed with DR process for years now, and nobody is filling in the blanks on its

1848:

formal arbitration.....is it not possible that this project indeed does cover a topic and issue not covered by WP:DRP?--

1513: 1198:

There is no resistance to outside input. The membership area is clear that no one need be a member to help in any way.--

1181: 811:

imposed before the climate change ArbCom case started, failed (which led to that ArbCom case). It failed because if you

754: 692: 625: 419: 364: 336: 110: 1901: 1626:). Could you provide links to a couple of recent conflicts (within talk pages, AN, etc) that are representative? -- 1512:

When editors refer to WPDR it is often difficult to know exactly what they are referring to. There is the policy page:

696: 615: 60: 1953:

2023: Wikimedia Foundation decides to hire someone for a year restore some sanity to the chaos. They hire S. Z., Jr.

940:

level at the start, go ahead and propose that in the appropriate place, but right now there are no such requirements.

1935: 1934:

2016: CRP creates a new noticeboard for handling etiquete violations, and also a lightweight mediation forum called

876:

a potential new process that may at some time in the future become an actual new process is not. Creating an RfC is

1905: 1751: 753:

proposed to replace it. That idea was then dropped in favor of making 3O serve that purpose. Then the 3O community

2642: 1087: 457: 352: 2031:) As long as the Project stays within the expected norms of any Project, and the goal is to help fellow editors 1999: 1573: 767: 676: 297: 395:

focus on content. In other matters: Who will design the page? I am very good making fancy WProject pages :) —

2545: 2027:

are concerned, I'm not aware that any Project requires the approval of any committee in order to exist. (See

2593: 2587: 2575: 2490: 2447: 2404: 2344: 2271: 2235: 2220: 2184: 2131: 2068: 2016: 1872: 1853: 1823: 1803: 1703: 1675: 1646: 1613: 1533: 1503: 1356: 1203: 750: 593: 538: 505: 453: 2654: 2617: 2565: 2529: 2494: 2478: 2451: 2437: 2396: 2377: 2333: 2315: 2275: 2258: 2239: 2224: 2209: 2188: 2173: 2159: 2135: 2119: 2072: 2054: 2005: 1978: 1876: 1857: 1827: 1807: 1791: 1769: 1707: 1693: 1679: 1664: 1650: 1635: 1617: 1602: 1579: 1537: 1507: 1456: 1360: 1255: 1221: 1207: 1193: 1174: 1149: 1133: 1113: 1059: 971: 922: 902: 859: 844: 824: 805: 773: 709: 682: 647: 597: 577: 561: 542: 509: 494: 477: 447: 432: 409: 376: 330: 303: 270: 249: 234: 214: 2304: 2203: 2113: 2043: 1785: 1763: 745:

there is some considerable sentiment that we do need them. I was not altogether in favor of shutting down

2549:

and leave feedback. If you have any questions, you can ask on the proposal page or leave a message on my

2525: 2474: 1438:). Before being an officially chartered wiki project (and I'd like to see where the authorization from 882: 855: 820: 443: 326: 266: 242: 116: 1314:

This is a WikiProject and no decisions are binding to any individual or the overall general community.

391:

My belief is that WPDR focuses on content, while WPCR focuses on conduct. Isn't that so? Even, CR can

2629: 2392: 1987: 1598: 1430:

I observe that there is very little that differentiates this project from the more broadly supported

1217: 1170: 1055: 918: 490: 1865:"If it crashes and burns, well, I'll happily dust myself off and apply Savlon to the affected areas" 2602:

To receive additional notifications about WikiProject X on this talk page, please add this page to

2329: 2254: 2169: 2155: 2091: 1991: 1974: 1689: 1660: 1631: 1565: 1480: 1418: 1189: 1145: 1109: 967: 898: 840: 759: 705: 668: 643: 573: 473: 428: 372: 289: 230: 210: 50: 2486: 2443: 2267: 2231: 2216: 2180: 2127: 2064: 1868: 1849: 1844: 1819: 1799: 1699: 1671: 1642: 1609: 1529: 1499: 1435: 1352: 1266: 1234: 1199: 1126: 589: 553: 534: 501: 65: 1956:

2024: S. Z., Jr. collects statistics, performs studies, and collects input from WP community.

1472: 147: 129: 1959:

2025: S. Z., Jr. recommends that the CRN be eliminated and that DRN be revived. It is done.

2298: 2198: 2108: 2037: 1780: 1758: 1741:

of the WPDR project rather than segregating tasks into a new project. I also noticed that the

1452: 1439: 1244: 887:

A WikiProject is a group of editors that want to work together as a team to improve Knowledge.

46: 1843:. While the terms can sometimes be interchangeable, the article on CR is far superior to the 2521: 2470: 851: 816: 439: 403: 322: 262: 2464:

Resolving conflicts by making use of the fact that on Knowledge you can travel back in time

2613: 2561: 2550: 2388: 1594: 1340: 1213: 1166: 1051: 1025: 914: 486: 2341:

I don't understand why we have to oppose every new idea without even giving it a chance.

1496:

Knowledge talk:WikiProject Council/Archive 17#When Was The Change Authorized And By Whom?

1524:. While related in one way or another, they are separate and deal with different things. 957:

I am not disagreeing about the wording having problems that need to be fixed. I sort of

2430: 2370: 2325: 2250: 2165: 2151: 2146:

is the greatest thing since sliced bread. When editors are prohibted from discussing

2087: 1970: 1685: 1656: 1627: 1431: 1414: 1185: 1141: 1105: 1047: 963: 894: 836: 701: 639: 569: 469: 424: 368: 363:, which is what this talk page is discussing. Any new DR process would fall under the 226: 206: 2663: 2650: 2143: 1945: 1928: 1775: 1746: 1560: 1374: 1121: 794: 549: 340: 1886:- I have a time machine, and I just travelled into the future. Here is what I saw: 2592:

easier and projects easier to maintain. If you or your WikiProject are interested,

1941: 1448: 1241: 720: 688: 1776:

work on the disputes that are open (and close them if they've resolved themselves)

456:

process to be overbearing? What do you think of the fact that processes such as

367:

umbrella anyway, and there is already an (underutilized) project to cover that. --

2082: 1351:

enforcement and is not a cabal (which never existed and exists even less now).--

396: 1910:

June 2013: Editors get confused trying to choose between DRN and CRN because

2609: 2557: 2442:*Zombie voice* "Beeblebrox commands me...." *slaps own face-snaps out of it*-- 1325:

a noticeboard or a process. What is it? What does the community want it to be?

1021:

a noticeboard or a process. What is it? What does the community want it to be?

1343:? Is it intended as a prerequisite, substitute, or something else altogether? 1271:

Both Guy and Yunshui put it well. I will address the Bullet listed questions:

1028:? Is it intended as a prerequisite, substitute, or something else altogether? 288:

it, rather than talking about it. Still, I applaud the effort. Best regards,

687:

TM: When you list "DR processes" why do you exclude RFCU and ARBCOM? The

1969:… at least, I think I have a time machine. Maybe it was all a dream? . -- 2606:. Otherwise, this will be the last notification sent about WikiProject X. 359:). Even if a new DR process were formed, that would be distinct from a 1321:

It has been stated by the primary architect of this project that this is

1017:

It has been stated by the primary architect of this project that this is

1924:

talking about their opponents, and CRN permits it, but DRN prohibits it.

1050:

in the hopes of drawing in broad input from the wider community.

1413:

Several other DRN volunteers use similar opening statements. --

987: 92: 15: 2574: 1546:

While I'm not necessarily in favor of the retention of this

1471: 2638: 1339:

How does this project relate to the established process of

1024:

How does this project relate to the established process of

1774:

FWIW, I think the best way we can help the problems is to

962:

a greatly improved rewrite of the section in question. --

1486:

This editor is willing to lend a helping hand. Just ask.

667:

conduct component then they are mistaken. Best regards,

466:"not many editors want to take care of things like this" 339:? If so, that is a major undertaking that requires an 2634: 1920:

2014: DRN cases dwindle to a trickle, because editors

1841: 1834: 1890:

March 2013: Conflict Resolution Project (CRP) created

1608:

content or concern conduct between multiple editors.--

1278:

Does the community desire to have this project at all?

1008:

Does the community desire to have this project at all?

2106:

project, so that's what I will be finding out later.

1377:

I always start by cutting and pasting the following:

758:not sure this is the place to do it. Best regards, 1743:goals and scope of Wikiproject Conflict Resolution 910:already being addressed and progress is being made 1931:guideline is rewritten to be "Focus On Behavior". 1747:goals and scope of Wikiproject Dispute Resolution 1736:the wheel. A few examples: have a look at where 1397:at the top of this page. Thanks! (my signature)" 528:Yes, this project is for editor conduct/conflict 2023:boards are not the proper solution. As far as 605: 583:process can be duanting, but is not impossible 27:and anything related to its purposes and tasks. 1066:Merge with existing Dispute Resolution project 8: 1914:dispute involves both content & conduct. 1554:, so I suppose that on balance I must !vote 719:Nol, I certainly concur that the sidebar at 468:what specifically do you mean by "this"? -- 1436:the Dispute Resolution Noticebard talk page 693:entire section on handling conduct disputes 612:That is not correct. Look at these pages: 124: 1752:universal dispute resolution request form 109:does not require a rating on Knowledge's 1522:Knowledge:Dispute resolution noticeboard 1518:Knowledge:WikiProject Dispute Resolution 621:Knowledge:WikiProject Dispute Resolution 222:Knowledge:WikiProject_Dispute_Resolution 203:Knowledge:WikiProject_Dispute_Resolution 1624:the existing Dispute Resolution project 1102:the existing Dispute Resolution project 1004:Possible issues needing clarification: 126: 169:Knowledge:WikiProject Editor Retention 2670:WikiProject Editor Retention articles 2538:Comment on the WikiProject X proposal 631:Knowledge:Dispute resolution requests 172:Template:WikiProject Editor Retention 7: 1307:How binding are decisions made here? 1014:How binding are decisions made here? 98: 96: 201:How is this project different from 194:How is this project different from 115:It is of interest to the following 2623:A new newsletter directory is out! 2604:Knowledge:WikiProject X/Newsletter 349:Knowledge:Village pump (proposals) 14: 2645:and someone will add it for you. 2029:WP:Knowledge is not a bureaucracy 1965:2027 to 2040 - The cycle repeats. 1895:WP:Dispute Resolution Noticeboard 737:think the issue about additional 153:This page is within the scope of 2633:has been created to replace the 2324:. That's actually kind of huge. 1094:), and build on that background. 992: 146: 128: 97: 40:Click here to start a new topic. 1900:May 2013: the CRN is added to 1092:Knowledge:Wikiquette assistance 462:Knowledge:Wikiquette assistance 357:Knowledge:Wikiquette assistance 25:WikiProject Conflict Resolution 2164:I think Noleander is right. -- 1556:in favor of project retention. 1432:WikiProject Dispute Resolution 1074:Duplication: WP already has a 418:No, the DR project covers the 1: 1738:Knowledge:Conflict resolution 868:a new process is a big deal. 220:It looks like the 2-year old 163:and see a list of open tasks. 37:Put new text under old text. 2618:16:57, 14 January 2015 (UTC) 1812:As I sated on your talkpage: 1514:Knowledge:Dispute resolution 1182:Knowledge:Dispute resolution 652:While I'm not sure that I'm 626:Knowledge:Dispute resolution 343:and should be publicized in 156:WikiProject Editor Retention 2566:22:47, 1 October 2014 (UTC) 2553:. Thank you for your time! 1902:Template:Dispute-resolution 1778:. I'll do some too myself. 747:Wikiquette assistance (WQA) 616:Template:Dispute-resolution 45:New to Knowledge? Welcome! 2686: 2655:03:11, 11 April 2019 (UTC) 2530:13:36, 15 March 2013 (UTC) 2495:23:55, 14 March 2013 (UTC) 2479:23:41, 14 March 2013 (UTC) 2452:23:21, 26 March 2013 (UTC) 2438:23:12, 26 March 2013 (UTC) 2397:18:24, 26 March 2013 (UTC) 2378:16:39, 26 March 2013 (UTC) 2334:07:09, 17 March 2013 (UTC) 2316:01:24, 17 March 2013 (UTC) 2276:01:09, 17 March 2013 (UTC) 2259:00:58, 17 March 2013 (UTC) 2240:23:44, 15 March 2013 (UTC) 2225:23:41, 15 March 2013 (UTC) 2210:20:51, 15 March 2013 (UTC) 2189:23:41, 15 March 2013 (UTC) 2174:20:35, 15 March 2013 (UTC) 2160:20:21, 15 March 2013 (UTC) 2136:23:41, 15 March 2013 (UTC) 2120:20:08, 15 March 2013 (UTC) 2073:23:41, 15 March 2013 (UTC) 2055:18:56, 15 March 2013 (UTC) 2006:15:05, 15 March 2013 (UTC) 1986:Please do not disrupt the 1979:14:44, 15 March 2013 (UTC) 1906:Template:Noticeboard_links 1877:07:31, 15 March 2013 (UTC) 1858:07:18, 15 March 2013 (UTC) 1828:06:51, 15 March 2013 (UTC) 1808:06:48, 15 March 2013 (UTC) 1792:06:28, 15 March 2013 (UTC) 1770:06:22, 15 March 2013 (UTC) 1708:02:14, 15 March 2013 (UTC) 1694:01:48, 15 March 2013 (UTC) 1680:23:37, 14 March 2013 (UTC) 1670:they would be accepting.-- 1665:23:32, 14 March 2013 (UTC) 1651:23:22, 14 March 2013 (UTC) 1636:23:02, 14 March 2013 (UTC) 1618:22:57, 14 March 2013 (UTC) 1603:22:35, 14 March 2013 (UTC) 1580:21:51, 14 March 2013 (UTC) 1538:22:29, 14 March 2013 (UTC) 1508:22:17, 14 March 2013 (UTC) 1457:21:44, 14 March 2013 (UTC) 1361:20:12, 14 March 2013 (UTC) 1256:20:03, 14 March 2013 (UTC) 1222:22:28, 14 March 2013 (UTC) 1208:20:15, 14 March 2013 (UTC) 1194:04:27, 15 March 2013 (UTC) 1175:19:58, 14 March 2013 (UTC) 1150:19:36, 14 March 2013 (UTC) 1134:17:30, 14 March 2013 (UTC) 1114:17:22, 14 March 2013 (UTC) 1076:Dispute Resolution project 1060:17:20, 14 March 2013 (UTC) 1034:17:15, 14 March 2013 (UTC) 972:18:04, 15 March 2013 (UTC) 923:17:00, 15 March 2013 (UTC) 903:15:16, 15 March 2013 (UTC) 860:16:51, 14 March 2013 (UTC) 845:16:35, 14 March 2013 (UTC) 825:16:20, 14 March 2013 (UTC) 806:15:59, 14 March 2013 (UTC) 774:15:52, 14 March 2013 (UTC) 710:14:58, 14 March 2013 (UTC) 683:14:10, 14 March 2013 (UTC) 648:13:51, 14 March 2013 (UTC) 598:01:23, 14 March 2013 (UTC) 578:00:12, 14 March 2013 (UTC) 562:23:30, 13 March 2013 (UTC) 543:22:21, 13 March 2013 (UTC) 510:23:56, 13 March 2013 (UTC) 495:23:02, 13 March 2013 (UTC) 478:19:06, 13 March 2013 (UTC) 448:18:08, 13 March 2013 (UTC) 433:16:49, 13 March 2013 (UTC) 410:16:25, 13 March 2013 (UTC) 377:16:53, 13 March 2013 (UTC) 345:WP:Centralized discussions 331:15:01, 13 March 2013 (UTC) 304:14:09, 13 March 2013 (UTC) 271:14:01, 13 March 2013 (UTC) 250:13:15, 13 March 2013 (UTC) 235:11:43, 13 March 2013 (UTC) 215:11:03, 13 March 2013 (UTC) 196:Dispute Resolution project 1341:user requests for comment 1026:user requests for comment 175:Editor Retention articles 141: 123: 75:Be welcoming to newcomers 2546:review the proposal here 1745:are very similar to the 1466:editors as a good idea): 731:Moving on to that issue: 1990:to make a point. ;-) — 1936:WP:Mediation Caballeros 1884:Report from the Future! 1561:Miscellany for deletion 1516:, The WikiProject page: 751:Knowledge:Sanity checks 2579: 2571:WikiProject X is live! 1550:, I'm opposed to this 1476: 1395:Guide for participants 609: 70:avoid personal attacks 2578: 1475: 883:Knowledge:WikiProject 420:WP:Dispute resolution 365:WP:Dispute resolution 337:WP:Dispute resolution 2649:– Sent on behalf of 2643:template's talk page 2635:old, out-of-date one 2630:Newsletter directory 2387:easier around here. 1988:space-time continuum 1929:The Focus On Content 984:Request for comment 2580: 1845:Dispute resolution 1520:and a noticeboard 1477: 1088:WP:Mediation cabal 689:Dispute resoluiton 458:WP:Mediation cabal 438:before they arise. 353:WP:Mediation cabal 111:content assessment 81:dispute resolution 42: 2556: 2436: 2376: 2338: 2314: 2053: 1270: 1238: 1131: 1039: 1038: 717:Response, per se: 191: 190: 187: 186: 183: 182: 91: 90: 61:Assume good faith 38: 2677: 2582:Hello everyone! 2554: 2433: 2427: 2421: 2414: 2410: 2407: 2373: 2367: 2361: 2354: 2350: 2347: 2336: 2310: 2208: 2206: 2201: 2144:Focus On Content 2118: 2116: 2111: 2049: 2017:WP:Third opinion 2002: 1996: 1790: 1788: 1783: 1768: 1766: 1761: 1576: 1570: 1264: 1253: 1247: 1232: 1158:resolve anything 1127: 1124: 996: 995: 988: 804: 802: 797: 770: 764: 679: 673: 602:AMS: You wrote: 454:WP:Third opinion 407: 401: 300: 294: 245: 244:Mr. Stradivarius 177: 176: 173: 170: 167: 166:Editor Retention 150: 143: 142: 136:Editor Retention 132: 125: 102: 101: 100: 93: 16: 2685: 2684: 2680: 2679: 2678: 2676: 2675: 2674: 2660: 2659: 2625: 2573: 2540: 2466: 2431: 2425: 2417: 2408: 2405: 2371: 2365: 2357: 2348: 2345: 2337:Don't knock it! 2204: 2199: 2197: 2114: 2109: 2107: 2000: 1992: 1840:scope or goals. 1786: 1781: 1779: 1764: 1759: 1757: 1574: 1566: 1251: 1245: 1130: 1122: 1035: 997: 993: 986: 800: 795: 793: 768: 760: 677: 669: 530: 404: 397: 298: 290: 243: 199: 174: 171: 168: 165: 164: 87: 86: 56: 23:for discussing 12: 11: 5: 2683: 2681: 2673: 2672: 2662: 2661: 2658: 2657: 2624: 2621: 2572: 2569: 2539: 2536: 2535: 2534: 2533: 2532: 2514: 2513: 2512: 2511: 2504: 2503: 2502: 2501: 2465: 2462: 2461: 2460: 2459: 2458: 2457: 2456: 2455: 2454: 2381: 2380: 2339: 2318: 2293: 2292: 2291: 2290: 2289: 2288: 2287: 2286: 2285: 2284: 2283: 2282: 2281: 2280: 2279: 2278: 2193: 2192: 2191: 2140: 2139: 2138: 2103: 2102: 2101: 2078: 2077: 2076: 2075: 2058: 2057: 2011: 2010: 2009: 2008: 1994:TransporterMan 1967: 1966: 1963: 1960: 1957: 1954: 1951: 1948: 1938: 1932: 1925: 1918: 1915: 1908: 1898: 1891: 1882: 1880: 1879: 1860: 1830: 1813: 1810: 1727: 1726: 1725: 1724: 1723: 1722: 1721: 1720: 1719: 1718: 1717: 1716: 1715: 1714: 1713: 1712: 1711: 1710: 1583: 1582: 1568:TransporterMan 1543: 1542: 1541: 1540: 1525: 1510: 1470: 1469: 1468: 1467: 1460: 1459: 1427: 1426: 1425: 1424: 1423: 1422: 1406: 1405: 1404: 1403: 1402: 1401: 1400: 1399: 1383: 1382: 1381: 1380: 1379: 1378: 1366: 1365: 1364: 1363: 1345: 1344: 1336: 1335: 1334: 1333: 1327: 1326: 1318: 1317: 1316: 1315: 1309: 1308: 1304: 1303: 1302: 1301: 1294: 1293: 1289: 1288: 1287: 1286: 1280: 1279: 1275: 1274: 1273: 1272: 1259: 1258: 1230: 1229: 1228: 1227: 1226: 1225: 1224: 1137: 1136: 1128: 1098: 1097: 1096: 1095: 1083: 1079: 1063: 1062: 1041: 1037: 1036: 1032: 1030: 1029: 1022: 1015: 1012: 1009: 1000: 998: 991: 985: 982: 981: 980: 979: 978: 977: 976: 975: 974: 948: 947: 946: 945: 944: 943: 942: 941: 930: 929: 928: 927: 926: 925: 864: 862: 789: 788: 787: 786: 785: 784: 783: 782: 781: 780: 779: 778: 777: 776: 762:TransporterMan 671:TransporterMan 635: 634: 633: 628: 623: 618: 610: 603: 565: 564: 529: 526: 525: 524: 523: 522: 521: 520: 519: 518: 517: 516: 515: 514: 513: 512: 413: 412: 388: 387: 386: 385: 384: 383: 382: 381: 380: 379: 311: 310: 309: 308: 307: 306: 292:TransporterMan 276: 275: 274: 273: 255: 254: 253: 252: 198: 192: 189: 188: 185: 184: 181: 180: 178: 161:the discussion 151: 139: 138: 133: 121: 120: 114: 103: 89: 88: 85: 84: 77: 72: 63: 57: 55: 54: 43: 34: 33: 30: 29: 28: 13: 10: 9: 6: 4: 3: 2: 2682: 2671: 2668: 2667: 2665: 2656: 2652: 2648: 2647: 2646: 2644: 2640: 2636: 2632: 2631: 2622: 2620: 2619: 2615: 2611: 2607: 2605: 2601: 2597: 2595: 2590: 2589: 2588:WikiProject X 2583: 2577: 2570: 2568: 2567: 2563: 2559: 2552: 2548: 2547: 2537: 2531: 2527: 2523: 2518: 2517: 2516: 2515: 2508: 2507: 2506: 2505: 2498: 2497: 2496: 2492: 2488: 2487:Amadscientist 2483: 2482: 2481: 2480: 2476: 2472: 2463: 2453: 2449: 2445: 2444:Amadscientist 2441: 2440: 2439: 2434: 2428: 2422: 2420: 2413: 2412: 2411: 2400: 2399: 2398: 2394: 2390: 2385: 2384: 2383: 2382: 2379: 2374: 2368: 2362: 2360: 2353: 2352: 2351: 2340: 2335: 2331: 2327: 2323: 2319: 2317: 2313: 2309: 2306: 2302: 2301: 2295: 2294: 2277: 2273: 2269: 2268:Amadscientist 2264: 2263: 2262: 2261: 2260: 2256: 2252: 2247: 2243: 2242: 2241: 2237: 2233: 2232:Amadscientist 2228: 2227: 2226: 2222: 2218: 2217:Amadscientist 2213: 2212: 2211: 2207: 2202: 2194: 2190: 2186: 2182: 2181:Amadscientist 2179:themselves.-- 2177: 2176: 2175: 2171: 2167: 2163: 2162: 2161: 2157: 2153: 2149: 2145: 2141: 2137: 2133: 2129: 2128:Amadscientist 2125: 2124: 2123: 2122: 2121: 2117: 2112: 2104: 2099: 2098: 2097: 2096: 2095: 2093: 2089: 2084: 2074: 2070: 2066: 2065:Amadscientist 2062: 2061: 2060: 2059: 2056: 2052: 2048: 2045: 2041: 2040: 2034: 2030: 2026: 2022: 2018: 2013: 2012: 2007: 2003: 1997: 1995: 1989: 1985: 1984: 1983: 1982: 1981: 1980: 1976: 1972: 1964: 1961: 1958: 1955: 1952: 1949: 1947: 1943: 1939: 1937: 1933: 1930: 1926: 1923: 1919: 1916: 1913: 1909: 1907: 1903: 1899: 1896: 1892: 1889: 1888: 1887: 1885: 1878: 1874: 1870: 1869:Amadscientist 1866: 1861: 1859: 1855: 1851: 1850:Amadscientist 1846: 1842: 1839: 1835: 1831: 1829: 1825: 1821: 1820:Amadscientist 1817: 1814: 1811: 1809: 1805: 1801: 1800:Amadscientist 1796: 1795: 1794: 1793: 1789: 1784: 1777: 1772: 1771: 1767: 1762: 1754: 1753: 1748: 1744: 1739: 1733: 1732: 1709: 1705: 1701: 1700:Amadscientist 1697: 1696: 1695: 1691: 1687: 1683: 1682: 1681: 1677: 1673: 1672:Amadscientist 1668: 1667: 1666: 1662: 1658: 1654: 1653: 1652: 1648: 1644: 1643:Amadscientist 1639: 1638: 1637: 1633: 1629: 1625: 1621: 1620: 1619: 1615: 1611: 1610:Amadscientist 1606: 1605: 1604: 1600: 1596: 1593:is in order. 1592: 1587: 1586: 1585: 1584: 1581: 1577: 1571: 1569: 1562: 1557: 1553: 1549: 1545: 1544: 1539: 1535: 1531: 1530:Amadscientist 1526: 1523: 1519: 1515: 1511: 1509: 1505: 1501: 1500:Amadscientist 1497: 1492: 1491: 1490: 1489: 1488: 1487: 1483: 1482: 1474: 1464: 1463: 1462: 1461: 1458: 1454: 1450: 1446: 1441: 1437: 1433: 1429: 1428: 1420: 1416: 1412: 1411: 1410: 1409: 1408: 1407: 1398: 1396: 1391: 1390: 1389: 1388: 1387: 1386: 1385: 1384: 1376: 1372: 1371: 1370: 1369: 1368: 1367: 1362: 1358: 1354: 1353:Amadscientist 1349: 1348: 1347: 1346: 1342: 1338: 1337: 1331: 1330: 1329: 1328: 1324: 1320: 1319: 1313: 1312: 1311: 1310: 1306: 1305: 1298: 1297: 1296: 1295: 1291: 1290: 1284: 1283: 1282: 1281: 1277: 1276: 1268: 1267:edit conflict 1263: 1262: 1261: 1260: 1257: 1254: 1248: 1243: 1236: 1235:edit conflict 1231: 1223: 1219: 1215: 1211: 1210: 1209: 1205: 1201: 1200:Amadscientist 1197: 1196: 1195: 1191: 1187: 1183: 1178: 1177: 1176: 1172: 1168: 1163: 1159: 1154: 1153: 1152: 1151: 1147: 1143: 1135: 1132: 1125: 1118: 1117: 1116: 1115: 1111: 1107: 1103: 1093: 1089: 1084: 1080: 1077: 1073: 1072: 1071: 1070: 1069: 1067: 1061: 1057: 1053: 1049: 1044: 1043: 1042: 1033: 1027: 1023: 1020: 1016: 1013: 1010: 1007: 1006: 1005: 999: 990: 989: 983: 973: 969: 965: 960: 956: 955: 954: 953: 952: 951: 950: 949: 938: 937: 936: 935: 934: 933: 932: 931: 924: 920: 916: 911: 906: 905: 904: 900: 896: 892: 888: 884: 879: 875: 871: 867: 863: 861: 857: 853: 848: 847: 846: 842: 838: 833: 829: 828: 827: 826: 822: 818: 814: 808: 807: 803: 798: 775: 771: 765: 763: 756: 752: 748: 744: 740: 736: 732: 727: 722: 718: 715: 714: 713: 712: 711: 707: 703: 698: 694: 691:page has an 690: 686: 685: 684: 680: 674: 672: 666: 662: 659: 655: 651: 650: 649: 645: 641: 636: 632: 629: 627: 624: 622: 619: 617: 614: 613: 611: 608: 604: 601: 600: 599: 595: 591: 590:Amadscientist 586: 581: 580: 579: 575: 571: 567: 566: 563: 559: 558:contributions 555: 551: 550:Lord Sjones23 547: 546: 545: 544: 540: 536: 535:Amadscientist 527: 511: 507: 503: 502:Amadscientist 498: 497: 496: 492: 488: 483: 482: 481: 480: 479: 475: 471: 467: 463: 459: 455: 451: 450: 449: 445: 441: 436: 435: 434: 430: 426: 421: 417: 416: 415: 414: 411: 408: 406: 402: 400: 394: 390: 389: 378: 374: 370: 366: 362: 358: 354: 350: 346: 342: 338: 334: 333: 332: 328: 324: 319: 318: 317: 316: 315: 314: 313: 312: 305: 301: 295: 293: 287: 282: 281: 280: 279: 278: 277: 272: 268: 264: 259: 258: 257: 256: 251: 248: 247: 246: 238: 237: 236: 232: 228: 223: 219: 218: 217: 216: 212: 208: 204: 197: 193: 179: 162: 158: 157: 152: 149: 145: 144: 140: 137: 134: 131: 127: 122: 118: 112: 108: 104: 95: 94: 82: 78: 76: 73: 71: 67: 64: 62: 59: 58: 52: 48: 47:Learn to edit 44: 41: 36: 35: 32: 31: 26: 22: 18: 17: 2628: 2626: 2608: 2599: 2598: 2594:check us out 2586: 2584: 2581: 2544: 2541: 2467: 2418: 2403: 2402: 2358: 2343: 2342: 2321: 2300:Dennis Brown 2299: 2245: 2147: 2079: 2039:Dennis Brown 2038: 2032: 2024: 2020: 1993: 1968: 1921: 1911: 1883: 1881: 1864: 1837: 1815: 1773: 1750: 1734: 1729: 1728: 1590: 1567: 1555: 1551: 1547: 1485: 1481:WP:RETENTION 1479: 1478: 1445:bikeshedding 1394: 1392: 1322: 1161: 1157: 1138: 1099: 1065: 1064: 1040: 1031: 1018: 1003: 958: 909: 890: 886: 877: 873: 869: 865: 831: 812: 809: 790: 761: 742: 738: 734: 730: 725: 716: 670: 664: 660: 657: 653: 606: 584: 531: 465: 405: 398: 392: 360: 291: 285: 241: 240: 200: 154: 117:WikiProjects 107:project page 106: 19:This is the 2639:WikiSpecies 2522:Count Iblis 2471:Count Iblis 2083:Whac-A-Mole 2081:am playing 852:Count Iblis 817:Count Iblis 440:Lucia Black 323:Count Iblis 263:Count Iblis 2389:Beeblebrox 1595:Beeblebrox 1440:WP:COUNCIL 1214:Beeblebrox 1167:Beeblebrox 1052:Beeblebrox 915:Beeblebrox 870:Discussing 697:DR sidebar 487:Beeblebrox 2551:talk page 2409:Strikeout 2406:Automatic 2349:Strikeout 2346:Automatic 2326:Xavexgoem 2251:Noleander 2166:Guy Macon 2152:Noleander 2142:I think 2088:Guy Macon 1971:Noleander 1686:Noleander 1657:Noleander 1628:Noleander 1415:Guy Macon 1300:together. 1186:Guy Macon 1142:Guy Macon 1106:Noleander 964:Guy Macon 895:Guy Macon 874:Designing 837:Noleander 702:Noleander 695:. The 640:Noleander 570:Noleander 470:Noleander 425:Noleander 369:Noleander 227:Noleander 207:Noleander 83:if needed 66:Be polite 21:talk page 2664:Category 2651:Headbomb 2322:practice 2312:Join WER 2230:ya go.-- 2148:behavior 2051:Join WER 2025:charters 2015:Just as 866:Creating 755:rejected 654:entirely 51:get help 1548:project 1449:Hasteur 1242:Yunshui 1082:issues. 1048:WP:CENT 889:" and " 739:conduct 361:project 2627:A new 2200:Steven 2110:Steven 1946:WP:ANI 1927:2015: 1897:(DRN). 1782:Steven 1760:Steven 1375:WP:DRN 959:expect 885:says " 743:unless 113:scale. 2610:Harej 2600:Note: 2558:Harej 2205:Zhang 2115:Zhang 2033:avoid 2021:admin 1942:WP:AN 1912:every 1787:Zhang 1765:Zhang 1731:here. 1123:Monty 721:WP:DR 286:doing 105:This 79:Seek 2614:talk 2562:talk 2526:talk 2491:talk 2475:talk 2448:talk 2432:AAPT 2393:talk 2372:AAPT 2330:talk 2272:talk 2255:talk 2246:peer 2236:talk 2221:talk 2185:talk 2170:talk 2156:talk 2132:talk 2092:talk 2069:talk 2001:TALK 1975:talk 1944:and 1922:love 1904:and 1873:talk 1854:talk 1824:talk 1804:talk 1704:talk 1690:talk 1676:talk 1661:talk 1647:talk 1632:talk 1614:talk 1599:talk 1575:TALK 1534:talk 1504:talk 1453:talk 1419:talk 1357:talk 1218:talk 1204:talk 1190:talk 1184:. -- 1171:talk 1146:talk 1110:talk 1104:. -- 1056:talk 968:talk 919:talk 899:talk 893:" -- 872:and 856:talk 841:talk 821:talk 813:only 801:6403 796:Cabe 769:TALK 706:talk 678:TALK 661:than 658:that 644:talk 594:talk 574:talk 554:talk 539:talk 506:talk 491:talk 474:talk 460:and 444:talk 429:talk 393:also 373:talk 355:and 347:and 327:talk 299:TALK 267:talk 231:talk 211:talk 205:? -- 68:and 1867:.-- 1552:RFC 1323:not 1129:845 1090:and 1019:not 878:not 665:any 399:ΛΧΣ 341:RfC 2666:: 2653:. 2616:) 2564:) 2528:) 2493:) 2477:) 2450:) 2429:• 2423:• 2395:) 2369:• 2363:• 2332:) 2305:2¢ 2303:- 2274:) 2257:) 2238:) 2223:) 2187:) 2172:) 2158:) 2134:) 2094:) 2071:) 2044:2¢ 2042:- 2004:) 1977:) 1875:) 1856:) 1838:no 1826:) 1818:-- 1806:) 1706:) 1692:) 1678:) 1663:) 1649:) 1634:) 1616:) 1601:) 1591:do 1578:) 1536:) 1506:) 1498:-- 1484:: 1455:) 1447:. 1359:) 1220:) 1206:) 1192:) 1173:) 1162:do 1148:) 1112:) 1058:) 970:) 921:) 901:) 858:) 843:) 832:do 823:) 772:) 735:do 733:I 726:is 708:) 681:) 646:) 596:) 585:if 576:) 560:) 556:- 541:) 508:) 493:) 476:) 446:) 431:) 375:) 329:) 302:) 269:) 233:) 225:-- 213:) 49:; 2612:( 2560:( 2524:( 2489:( 2473:( 2446:( 2435:) 2426:C 2419:T 2415:( 2391:( 2375:) 2366:C 2359:T 2355:( 2328:( 2308:© 2270:( 2253:( 2234:( 2219:( 2183:( 2168:( 2154:( 2130:( 2090:( 2067:( 2047:© 1998:( 1973:( 1871:( 1852:( 1822:( 1802:( 1702:( 1688:( 1674:( 1659:( 1645:( 1630:( 1612:( 1597:( 1572:( 1532:( 1502:( 1451:( 1421:) 1417:( 1355:( 1269:) 1265:( 1252:水 1249:‍ 1246:雲 1237:) 1233:( 1216:( 1202:( 1188:( 1169:( 1144:( 1108:( 1086:( 1054:( 966:( 917:( 897:( 854:( 839:( 819:( 766:( 704:( 675:( 642:( 592:( 572:( 552:( 537:( 504:( 489:( 472:( 442:( 427:( 371:( 325:( 296:( 265:( 229:( 209:( 119:: 53:.

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

Knowledge

talk:WikiProject Conflict Resolution - Knowledge

Index