Misplaced Pages

:Arbitration/Requests/Clarification and Amendment - Misplaced Pages

Article snapshot taken from Wikipedia with creative commons attribution-sharealike license. Give it a read and then ask your questions in the chat. We can research this topic together.
< Misplaced Pages:Arbitration | Requests

This is an old revision of this page, as edited by Callanecc (talk | contribs) at 01:23, 14 September 2015 (Clarification request: Abortion: Archiving closed clarification request). The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.

Revision as of 01:23, 14 September 2015 by Callanecc (talk | contribs) (Clarification request: Abortion: Archiving closed clarification request)(diff) ← Previous revision | Latest revision (diff) | Newer revision → (diff) Shortcut Arbitration Committee proceedings Case requests

Currently, there are no requests for arbitration.

Open cases
Case name Links Evidence due Prop. Dec. due
Palestine-Israel articles 5 (t) (ev / t) (ws / t) (pd / t) 21 Dec 2024 11 Jan 2025
Recently closed cases (Past cases)

No cases have recently been closed (view all closed cases).

Clarification and Amendment requests
Request name Motions  Case Posted
Amendment request: GoodDay none (orig. case) 11 September 2015
Clarification request: Kww and The Rambling Man none (orig. case) 4 August 2015
Arbitrator motions
Motion name Date posted
Arbitrator workflow motions 1 December 2024

Requests for clarification and amendment

Use this page to request clarification or amendment of a closed Arbitration Committee case or decision.

  • Requests for clarification are used to ask for further guidance or clarification about an existing completed Arbitration Committee case or decision.
  • Requests for amendment are used to ask for an amendment or extension of existing sanctions (for instance, because the sanctions are ineffective, contain a loophole, or no longer cover a sufficiently wide topic); or appeal for the removal of sanctions (including bans).

Submitting a request: (you must use this format!)

  1. Choose one of the following options and open the page in a new tab or window:
  2. Save your request and check that it looks how you think it should and says what you intended.
  3. If your request will affect or involve other users (including any users you have named as parties), you must notify these editors of your submission; you can use {{subst:Arbitration CA notice|SECTIONTITLE}} to do this.
  4. Add the diffs of the talk page notifications under the applicable header of the request.
Clarification and Amendment archives
123456789101112131415161718
192021222324252627282930313233343536
373839404142434445464748495051525354
555657585960616263646566676869707172
737475767778798081828384858687888990
919293949596979899100101102103104105106107108
109110111112113114115116117118119120121122123124125126
127128129130131

Please do not submit your request until it is ready for consideration; this is not a space for drafts, and incremental additions to a submission are disruptive.

Guidance on participation and word limits

Unlike many venues on Misplaced Pages, ArbCom imposes word limits. Please observe the below notes on complying with word limits.

  • Motivation. Word limits are imposed to promote clarity and focus on the issues at hand and to ensure that arbitrators are able to fully take in submissions. Arbitrators must read a large volume of information across many matters in the course of their service on the Committee, so submissions that exceed word limits may be disregarded. For the sake of fairness and to discourage gamesmanship (i.e., to disincentivize "asking forgiveness rather than permission"), word limits are actively enforced.
  • In general. Most submissions to the Arbitration Committee (including statements in arbitration case requests and ARCAs and evidence submissions in arbitration cases) are limited to 500 words, plus 50 diffs. During the evidence phase of an accepted case, named parties are granted an automatic extension to 1000 words plus 100 diffs.
  • Sectioned discussion. To facilitate review by arbitrators, you should edit only in your own section. Address your submission to arbitrators, not to other participants. If you wish to rebut, clarify, or otherwise refer to another submission for the benefit of arbitrators, you may do so within your own section. (More information.)
  • Requesting an extension. You may request a word limit extension in your submission itself (using the {{@ArbComClerks}} template) or by emailing clerks-l@lists.wikimedia.org. In your request, you should briefly (in 1-2 sentences) include (a) why you need additional words and (b) a broad outline of what you hope to discuss in your extended submission. The Committee endeavors to act upon extension requests promptly and aims to offer flexibility where warranted.
    • Members of the Committee may also grant extensions when they ask direct questions to facilitate answers to those questions.
  • Refactoring statements. You should write carefully and concisely from the start. It is impermissible to rewrite a statement to shorten it after a significant amount of time has passed or after anyone has responded to it (see Misplaced Pages:Talk page guidelines § Editing own comments), so it is often advisable to submit a brief initial statement to leave room to respond to other users if the need arises.
  • Sign submissions. In order for arbitrators and other participants to understand the order of submissions, sign your submission and each addition (using ~~~~).
  • Word limit violations. Submissions that exceed the word limit will generally be "hatted" (collapsed), and arbitrators may opt not to consider them.
  • Counting words. Words are counted on the rendered text (not wikitext) of the statement (i.e., the number of words that you would see by copy-pasting the page section containing your statement into a text editor or word count tool). This internal gadget may also be helpful.
  • Sanctions. Please note that members and clerks of the Committee may impose appropriate sanctions when necessary to promote the effective functioning of the arbitration process.

General guidance

Shortcuts:
Clarification and Amendment archives
123456789101112131415161718
192021222324252627282930313233343536
373839404142434445464748495051525354
555657585960616263646566676869707172
737475767778798081828384858687888990
919293949596979899100101102103104105106107108
109110111112113114115116117118119120121122123124125126
127128129130131

Amendment request: GoodDay

Initiated by GoodDay (talk) 17:11, 11 September 2015 (UTC)

Case or decision affected
GoodDay arbitration case (t) (ev / t) (w / t) (pd / t)

List of any users involved or directly affected, and confirmation that all are aware of the request:

Confirmation that all parties are aware of the request

Statement by GoodDay

May I please have my diacritics ban lifted. I believe there's no longer a reason for it to exist, as it appears that the topic itself has been settled by the general community, in favour of dios usage. GoodDay (talk) 17:11, 11 September 2015 (UTC)

Response - I'm no longer obsessed about diacritics. I merely wish the restriction removed, because it's a restriction. I wish for my slate to be clean. GoodDay (talk) 18:04, 11 September 2015 (UTC)

Response - If WP:HOCKEY has chosen to abolish the diacritics compromise & thus have chosen to include diacritics on North American hockey articles (including NHL team articles rosters), then I've no choice but to abide by it. GoodDay (talk) 18:59, 11 September 2015 (UTC)

Query from Resolute

If you believe the community has settled in favour of using diacritics, when is your position on our old compromise within WP:HOCKEY? Resolute 18:54, 11 September 2015 (UTC)

Statement by {other-editor}

GoodDay: Clerk notes

This area is used for notes by the clerks (including clerk recusals).

GoodDay: Arbitrator views and discussion

Clarification request: Kww and The Rambling Man

Initiated by Nyttend at 22:38, 4 August 2015 (UTC)

Case or decision affected
Kww and The Rambling Man arbitration case (t) (ev / t) (w / t) (pd / t)

List of any users involved or directly affected, and confirmation that all are aware of the request:

Confirmation that all parties are aware of the request

Statement by Nyttend

As noted at Misplaced Pages talk:Arbitration Committee/Noticeboard, the second remedy is rather confusing. Did you mean to say that Kww may not get the editfilter right unless he re-passes RFA, or did you not mean to address such a situation? I'm not marked Kww as a party because this isn't related to his post-case behavior: it's just a confusing element of the decision, and an authoritative interpretation would be helpful. Nyttend (talk) 22:38, 4 August 2015 (UTC)

Just a note after reading Salvio's comment — my only concern is that we get an unambiguous statement from Arbcom, because everyone loses when there's an ambiguous decision. I don't really know either editor and don't have an opinion on what Arbcom should decide here (so no point in asking my opinion); I just hope you'll decide something in place of the current wording, so that we all know what you were intending in the first place. Nyttend (talk) 20:51, 5 August 2015 (UTC)

Statement by Dragons flight

Due to his apparent lack of due care and competence in previously implementing edit filters, I am opposed to any process that would allow Kww to regain the EFM right without a community review. See my previous comments: . My understanding of remedy #2 while it was being drafted is that a desysopped Kww would be required to pass RFA before getting EFM restored, and I don't see any reason to weaken that. If this case hadn't been coming to RFAr already, I would have opened a separate community discussion about revoking Kww's EFM right. In practical terms, I assume it will be years (if ever) before Kww passes an RFA, but I don't think there ought to be a path that allows Kww to regain EFM any sooner than that (and I'm not sure he should be an EFM even if he passes RFA). Keep in mind that EFM capabilities are in some ways more powerful than the normal admin toolkit. Dragons flight (talk) 10:52, 5 August 2015 (UTC)

@Kww: It has never been clear to me that you really understood my criticisms / concerns, which is part of the problem. However, I don't want to have an argument with you about this. Should you actually want additional feedback on this issue (either now or some time in the future), I would suggest that you ask for other people at WT:EF to give you their opinions of your previous filters. Dragons flight (talk) 18:03, 5 August 2015 (UTC)

Statement by Kww

I already understood the restriction to be much as Salvio phrased it. I deeply resent Dragon flight's portraying our different opinions as to the weight that should be placed on false positives as a competence issue: I could just as reasonably claim that his insistence on consuming resources looking for rare corner cases was a competence issue. Neither one is: it's a difference in opinion as to where a reasonable balance between execution efficiency and false triggers lies.—Kww(talk) 14:34, 5 August 2015 (UTC)

Comment by Salvidrim

Since we're really getting down-and-dirty with the specifics of wording, I don't feel too bad about chiming in: in Salvio's proposed wording underneath (visibly inspired by an earlier post of mine), the removal of EFM is described first as a "restriction" that would automatically expire, and later as a "remedy" than can be appealed. The wording should probably brought in line with either term (restriction or remedy) for consistency? I really feel pedant pointing this out though.  · Salvidrim! ·  16:24, 5 August 2015 (UTC)

Statement by Francis Schonken

This may be understood in the current comment by Arbs (although I see no reference to it) but a non-admin desiring "edit filter manager user right" has to go through some procedure as described at Misplaced Pages:Edit filter#User right, second and third paragraph (starting with "The assignment of the edit filter manager user right to non-admins is highly restricted. It should only be requested by and given to highly trusted users, and only when there is a clear, demonstrated need for it...")

My point is this: if and when (within a year or whatever) a non-admin Kww would request a lifting of remedy 2 of the ArbCom case, I don't see how this could automatically result in Kww getting the edit filter manager user right back. Or would the ArbCom plan on overriding the regular procedure by ArbCom decision? Any future decision to lift that sanction should imho be formulated thus that after lifting of the sanction (if and when this is granted, in a scenario where Kww would not be an admin at that time) the regular procedure for a non-admin to be granted the right should be followed.

Seeing the analysis here: Misplaced Pages:Administrators' noticeboard/IncidentArchive890#Kww's edit filters I can imagine some reluctance by those allowed to grant the right to non-admins.

All this is a bit far ahead, and needs to be dealt with when it would occur in the future (if and when etc.), and by that time procedures might be completely different (especially when the community would take up on remedy 3 of the case), but I think it best this caveat is taken into the equasion now. --Francis Schonken (talk) 05:41, 6 August 2015 (UTC)

Statement by {other-editor}

Other editors are free to make relevant comments on this request as necessary. Comments here should opine whether and how the Committee should clarify or amend the decision or provide additional information.

Kww and The Rambling Man: Clerk notes

This area is used for notes by the clerks (including clerk recusals).

Kww and The Rambling Man: Arbitrator views and discussion

  • Nyttend, you are quite right that the remedy, as currently worded, leaves a bit to be desired and gives the impression that, short of another successful RFA, Kww may not receive the edit filter manager bit back; as far as I'm concerned, that's not satisfctory and, for that, I propose we reword the relevant remedy to Kww's edit filter manager permission is revoked. If he regains the administrator tools through a successful request for adminship, this restriction will automatically expire; in addition, he may appeal this remedy after 12 months to the Arbitration Committee. Salvio 09:42, 5 August 2015 (UTC)
  • Given that Kww has been desysopped, the only thing of relevance is how Kww may regain his EFM permission. The remedy is not brilliantly worded I agree, but the restriction it imposes is not ambiguous: He may not regain the bit while the restriction is in effect. The restriction automatically expires if he regains adminship at RfA, at which point he may regain the bit according to policy at that time (if there is no change between now and then he could assign it to himself if he desired). There is no restriction on when he can stand for adminship. I agree with Salvio that the restriction should be appealable at WP:ARCA 12 months after it's imposition (i.e. no sooner than August 2016). Thryduulf (talk) 21:02, 5 August 2015 (UTC)
  • I also agree that the EFM restriction should be appealable after some reasonable period of time has passed, 12 months would be fine for that. I don't think we need an amendment for that, though, as any arbitration remedy can be appealed at ARCA after a reasonable period, and the Committee can at that time choose to accept the appeal and lift the restriction. Seraphimblade 21:31, 5 August 2015 (UTC)
  • I'd be in favour of changing the wording of the decision, per Salvio giuliano's text above. At the time it was written (when it was unclear whether the desysop would pass or not) the current wording was arguably preferable; now that Kww has been desysopped it's overly convoluted and would benefit from being simplified. Yunshui  10:31, 6 August 2015 (UTC)
  • Out of the loop guy here. I would much rather us not have our hands in restoring permissions and have a fresh RfA be the only route of removal of the restriction. --In actu (Guerillero) | My Talk 14:07, 7 August 2015 (UTC)
    • In a hypothetical appeal to ARCA I would not be supporting any granting of the permission directly. I would consider giving permission to ask the community, taking into account the change in attitude and behaviour over the year and the level of scrutiny likely to be imparted at the relevant venue. Thryduulf (talk) 16:05, 7 August 2015 (UTC)
      • But that is disingenuous. There isn't a good WP:RFP like place to have that discussion that is in view of the community. By giving the OK for a discussion to happen at a little watched part of project space we are basically flipping the switch ourselves. I would much rather not have the committee in these matters. If anyone has a better idea for a community-centered way of signaling that the restriction is no longer needed, I am all ears. --Guerillero | Parlez Moi 20:51, 7 August 2015 (UTC)
        • Currently that is indeed the case and I would not support it. However if the proposal to split the EFM permission that was raised during the case happens, or if something else changes between now and next August that makes requesting the EFM bit something other than a barely observed blip in a backwater then I might support (depending on Kww of course). Alternatively, we could just say that the restriction may be appealed at the later of (a) when such a community process exists and (b) 12 months have passed. Of course this is academic if Kww does not wish to regain the EFM bit in advance of a successful RFA. Thryduulf (talk) 21:19, 7 August 2015 (UTC)
  • I'd prefer the community to handle this, not us. Doug Weller (talk) 17:56, 7 August 2015 (UTC)
  • The remedy was convoluted, I'm sorry for that, but the part of it was to create provisions with or without the desysop, given that usual policy is that admins may self-assign the flag. This could easily be reworded now to be clearer that the remedy expires if/when RFA is passed, but I will not support any appeal other than via RFA given the absence of any process with scruitiny to grant the EFM flag, and a belief that Arbcom should not be (re)granting permissions that have clear community processes to grant. This flag is a bit unusual, but we've given a clear community appeal here. (Had he not been desysopped, there would have been no community process of any rigor/scrutiny to regrant the flag) Courcelles (talk) 03:52, 10 August 2015 (UTC)
  • Given that we revoked the permissions, but did not ban him from re-applying by the usual means for them, I think the remedy is probably clear enough as it is. Happy to support a remedy amendment to make the existing text even clearer, if somebody wishes to move one, but otherwise I am satisfied that this is all in order. AGK 23:22, 30 August 2015 (UTC)
  • I've kept an eye on this but for absolute clarity I am of the same mind as AGK. NativeForeigner 09:44, 4 September 2015 (UTC)
  • I also agree with AGK. GorillaWarfare (talk) 01:20, 5 September 2015 (UTC)

Categories: