Jump to content

Wikipedia:Arbitration/Requests/Clarification and Amendment/Archive 123

Add links
From Wikipedia, the free encyclopedia
< Wikipedia:Arbitration | Requests | Clarification and Amendment
This is an old revision of this page, as edited by Dreamy Jazz (talk | contribs) at 13:08, 10 January 2023 (archive one). The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.
Archive 120Archive 121Archive 122Archive 123Archive 124Archive 125→Archive 130
Clarification and Amendment archives
123456789101112131415161718
192021222324252627282930313233343536
373839404142434445464748495051525354
555657585960616263646566676869707172
737475767778798081828384858687888990
919293949596979899100101102103104105106107108
109110111112113114115116117118119120121122123124125126
127128129130131132


Amendment request: Iranian politics (November 2022)

Original discussion

The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.

Initiated by Stefka Bulgaria at 09:34, 12 October 2022 (UTC)

Case or decision affected
Iranian politics arbitration case (t) (ev / t) (w / t) (pd / t)
Clauses to which an amendment is requested
  1. Wikipedia:Arbitration/Requests/Case/Iranian politics § Stefka Bulgaria topic-banned
List of any users involved or directly affected, and confirmation that all are aware of the request
Information about amendment request
  • Appeal of topic ban

Statement by Stefka Bulgaria

I'm not familiar with these appeals; sorry if I didn't fill this correctly. It's been a year since I was topic-banned from editing articles relating to Iranian politics. My edits in other areas (since I was topic-banned) have been constructive, and I've had a good chance to reflect and learn from the issues I had with other editors back then. With everything that's been happening in Iran these last weeks, I think I could be a useful contributor in this area once again. Also, editors I had issues prior to being topic-banned have mostly been topic-banned themselves or blocked for socking, so I don't believe that I would have problems working collaboratively in this area again. Anyways, thank you for your consideration.

Addressing comments below, last year's experience had an effect on my desire to participate in other talk/pages as a whole (and it still does); which is why I've been mainly reviewing new pages. I'm aware that if I were allowed to participate in Iranian-politics again, a misstep of any kind on my behalf would likely lead to me being indef'ed from this area. This request is for making occasional corrections in this area; nothing more. Stefka Bulgaria (talk) 09:42, 13 October 2022 (UTC)

Statement by Thryduulf (Iranian politics)

They were topic banned because they engaged in bludgeoning, stonewalling, and degrading of discussions. and filed verbose RfCs in an attempt to railroad preferred changes. They've done none of that since the topic ban was imposed, but they've done almost nothing else in talk spaces either. Since the case closed they've only made 9 edits to the talk: namespace that were not just page moves or wikiproject tagging (and one of them was a copyedit to their own comment) and 0 edits to the Wikipedia talk:, Template talk:, Category talk: and File talk: namespaces. Almost all their edits in user talk: have been speedy deletion notices (most of their work has been new page patrolling). Their four edits to Draft talk: came today and all are related to moving their personal sandbox to draftspace. Thryduulf (talk) 18:09, 12 October 2022 (UTC)

Statement by HistoryofIran

Considering the majority of Stefka Bulgaria's edits were in this topic, I don't find it surprising that their editing activity has decreased. It's hard to find another niche. The Iranian Politics area is a cesspool which suffers from POV editing (including dirty tactics such as WP:GAMING), and a lack of monitoring admins (I don't blame them), which makes it a lot more difficult to adhere to our guidelines (which is mainly why I left that area). While Stefka Bulgaria's hands may not be completely clean (then again, whose are?), I think they did a lot more good in that area than many others, and thus deserves another chance. --HistoryofIran (talk) 13:07, 27 October 2022 (UTC)

Statement by {other-editor}

Other editors are free to make relevant comments on this request as necessary. Comments here should address why or why not the Committee should accept the amendment request or provide additional information.

Iranian politics: Clerk notes

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

Iranian politics: Arbitrator views and discussion

  • I find myself somewhat on the fence. On the one hand, the issues that led to the levied sanctions have not been repeated in other venues. On the other hand, as Thryduulf mentions, there have not really been that many edits or "opportunities" (for lack of a better word) for that behaviour to show. It makes me think of an unsuccessful RfA candidate who then spends the next twelve months carefully avoiding anything that could be seen as controversial in an attempt at a second successful bid for adminship. In the interest of good faith, I do not necessarily think this is what happened; when an editor goes from averaging about 2000 edits per year to less than a tenth of that it does demonstrate that the topic area in question certainly was their primary focus, and they might not have found a new niche. I would like to hear from other editors, though. Primefac (talk) 08:42, 13 October 2022 (UTC)
  • I find myself largely agreeing with Primefac that we don't know if behavior has improved. I have noticed in several noticeboard discussions there still doesn't appear to be much admin work in this topic and so I worry if misbehavior were to happen again it would not be addressed. Barkeep49 (talk) 13:32, 27 October 2022 (UTC)
  • I think I am a decline here. Please demonstrate good work in the talk space in other areas and I expect an appeal would be successful. --Izno (talk) 21:17, 2 November 2022 (UTC)
  • I agree with Izno here. Maxim(talk) 12:23, 3 November 2022 (UTC)
  • I am also inclined to decline. I think you have some good feedback here, and the signs are encouraging for your next appeal if you follow it. --BDD (talk) 21:00, 3 November 2022 (UTC)
  • I concur with Izno. Best, KevinL (aka L235 · t · c) 09:08, 10 November 2022 (UTC)
  • I'm not seeing the evidence of good collaboration, so I also decline. WormTT(talk) 13:54, 10 November 2022 (UTC)
The discussion above is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.

Clarification request: Appeal restrictions as part of discretionary sanctions (November 2022)

Original discussion

The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.

Initiated by ToBeFree at 20:09, 2 November 2022 (UTC)

Case or decision affected
WP:AC/DS

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

Enforcing administrators:

Affected users:

Confirmation that all parties are aware of the request

Statement by ToBeFree

Wikipedia:Arbitration_enforcement_log/2022#Horn_of_Africa currently contains two entries saying "with an appeal possible in six months". There may be other, similar restrictions elsewhere; I didn't search for more. I'd like to know if such restrictions on appeals are compatible with the WP:AC/DS procedures. ~ ToBeFree (talk) 20:09, 2 November 2022 (UTC)

If it had been a single entry, I'd have asked the administrator who has placed it; I was looking at multiple entries and wanted to avoid starting multiple individual discussions with possibly varying results. ~ ToBeFree (talk) 20:46, 2 November 2022 (UTC)
I've looked for more from 2022 alone and feel confirmed in my decision to raise this centrally. I'm adding two parties for [1] and [2]. ~ ToBeFree (talk) 21:00, 2 November 2022 (UTC)

Statement by Ymblanter

I absolutely can not recollect the case, but reading the AE discussion I closed I see that the proposal was indeed "TB which can be appealed in 6 months". I guess what I meant was that the TB is best appealed after 6 months and has very little chances to lead to a successful appeal before that, but I see indeed that this is not what I logged. My apologies.--Ymblanter (talk) 20:29, 2 November 2022 (UTC)

May I please also notice that TBF did not attempt to discuss the issue with me prior to filing this request. Ymblanter (talk) 20:35, 2 November 2022 (UTC)

Statement by Doug Weller

Apologies. Of course we shouldn't deny the right of appeal at any time. I thought I'd seen this before and hadn't considered the implications. Doug Weller talk 16:47, 3 November 2022 (UTC)

Mind you the editor I topic banned just blocked his page and blew through the TB. Doug Weller talk 16:24, 4 November 2022 (UTC)

Statement by The Blade of the Northern Lights

Statement by RegentsPark

Agreed that an appeal can be filed immediately so, yes, mea culpa. In the particular case pointed to above, there was some discussion among the commenting admins about a timed t-ban, and that's part of the reason why the 6 months showed up there but I should have timed it to "exactly six months" to make it appealable. The current appeal system, imo, is a good one and I have no problems with it. Also, thanks to ToBeFree for bringing this up because, although on first glance this appears to be merely procedural, it is actually important for ensuring that our messaging be clear and not confusing. --RegentsPark (comment) 16:32, 3 November 2022 (UTC)

Statement by Shirshore

Statement by Onengsevia

Statement by Stix1776

Statement by Bookku

Took note of this helpful discussion. After overwhelming discussions small time gap can be helpful break for users too for study and reflection about what all went wrong. Bookku (talk) 13:10, 4 November 2022 (UTC)

Statement by Abecedare

My 2c: appeals by sanctioned editors fall essentially into two categories:

  1. "This sanction is unjustified"
  2. "This sanction may have been justified when placed but is no longer needed"
No administrator/venue should be able to place a limit of when the first kind of appeal can be placed since that would remove an essential check on their authority. However, it should be permissible for the sanction notice to specify when the second kind of appeal can be placed (as long as the time period is reasonable) both to prevent too-early appeals that are almost certain to be rejected and as a carrot to improve conduct.

As an example of what I mean, see this DS I had placed with a note appended that said, I have kept the topic area of the ban narrow in the hope that you can learn to edit productively in other areas and even ask for this ban to be rescinded say 3 months from now. I hope that the committee will not disallow that kind of "limit/encouragement" even while clarifying that I couldn't have (hypothetically) prohibited the editor from appealing the sanction to AN/AE/ARCA at any point they wished. Abecedare (talk) 15:33, 3 November 2022 (UTC)

Statement by Vanamonde

I agree with my colleagues above and below that individual admins obviously cannot obviate all rights of appeal, and that's wording we need to be careful about. However, if memory serves, admins at AE sometimes decline an appeal and simultaneously prohibit AE appeals for a given period of time. And this actually makes sense to me, because it's not about obviating the right of appeal, but rather saying "any appeal at this venue will be unsuccessful for this period of time". Sometimes want to avoid repeated appeals, and the sanctioned user would always have the option of coming to ARCA (I'm assuming this is non-controversial; if diffs are needed, I can dig them up later). It seems logical to say that individual admins may also state that they will not personally consider appeals for a given period, with the user still having the option of appealing to AE, AN, or ARCA. Vanamonde (Talk) 16:50, 3 November 2022 (UTC)

Statement from Harry

I came to make largely the same observation as Abecedare. I assume that these time limits on "appeals" were intended to mean that the sanction can be reviewed after that length of time, which is how I've used them in the past. They should not be taken, and I doubt the sanctioning admins intended them to be taken, as preventing the first kind of appeal, which asks other admins/the community/ArbCom to review the sanction because the sanctioned editor feels it is unjust. I would suggest using the term "review" or coming up with another ArbCom/WP policy neologism to distinguish appeals on the grounds that a sanction is no longer necessary. HJ Mitchell | Penny for your thoughts? 19:35, 3 November 2022 (UTC)

Statement by El_C

Hello. I'm not sure where Worm That Turned's quote of me is from, but it sounds about right. I believe the prevailing understanding is that outright moratoriums on appeals, as opposed to recommendations, are the sole domain of ArbCom (for WP:ACDS; the community for WP:GS). The argument that a consensus of AE admins on the WP:AE board, which obviously is a level higher than a single sanctioning admin, could also do that, is not something I have a strong opinion on. I have a vague recollection of a consensus of AE admins placing ~year'ish moratoriums on certain appellants who appeal, say, every 6 months over the span of years and years. And I've also a vague memory of it sticking without objections. But maybe it was a dream, whose to say?

But even at that event, if an admin were to remove such an appeal, from either AE or AN, the option to still appeal here at ARCA, as Barkeep49 notes below, nonetheless would remain open. At which point the Committee may be prompted to comment on AE board-derived moratoriums. But that has yet to happen as far as I'm able to recall, and overall has not been an issue of note. So this might mostly be theory. By contrast, I have a clear memory of ArbCom itself imposing moratoriums on appeals, I believe very recently even, though, I'm too lazy to look it up. BTW, a while back, Barkeep was wary of having too many AE appeals end up at ARCA, but to that I say: it's probably 80 percent AN, 20 percent AE, and negligible at ARCA, so I wouldn't really worry about it.

Anyway, I rambled for a while, but to reiterate as per the ping: take for example the last TBAN I imposed, currently being appealed (←live, permalink), to unanimous opposition I might add. Consider how I phrased it on that user's talk page: Now, while I strongly recommend you wait 6 months before appealing this sanction, you could technically do so immediately. But my sense is that it'll go about as well as your p-block appeals above [...] (diff). So that's been my MO, overall. At the least, a single sanctioning admin doesn't have the authority to override the right of appeal. El_C 17:58, 10 November 2022 (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.

Appeal restrictions as part of discretionary sanctions: Clerk notes

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

Appeal restrictions as part of discretionary sanctions: Arbitrator views and discussion

  • I'd love to understand the intent of Ymblanter and Doug Weller. If the intent is to ban all appeals I would say that is outside of DS power - at minimum they could appeal to us at ARCA. If the intent is "the appeal can be handled without needing to meet the DS criteria by third parties", that feels in line with the changes proposed to DS. Barkeep49 (talk) 20:12, 2 November 2022 (UTC)
    So in terms of resolving this particular issue is the answer a direction to clerks to strike those phrases and to otherwise proceed with the documentation of this consensus we've been doing for ARCAs? Barkeep49 (talk) 17:05, 4 November 2022 (UTC)
  • The appeals procedure described at Wikipedia:Arbitration Committee/Discretionary sanctions § Appeals and modifications is immediately available upon imposition of a restriction under the DS procedure. Best, KevinL (aka L235 · t · c) 20:20, 2 November 2022 (UTC)
    @Barkeep49: That sounds like the best way to resolve this ARCA, and seems to be consistent with the Committee's consensus. If there is no objection, I will ask the clerks to do so. Best, KevinL (aka L235 · t · c) 09:08, 10 November 2022 (UTC)
  • I don't think an AE sanction can be made unappealable for a certain time period, particularly at the time it is imposed. That said, an appeal of a reasonably placed sanction will almost certainly fail within the first six months, which is true not only for AE actions, but also for community imposed sanctions and a lot of types of indefinite blocks. Maxim(talk) 12:22, 3 November 2022 (UTC)
  • While I agree that current policy prohibits a prohibition on appeals, I would venture that it would be valuable to prevent specious appeals. But perhaps that can be handled without an AE consensus or isn't a common issue from restrictions levied at AE. Anyway, I'd probably only allow such a use for appealing to AE, if it were desirable to change the policy on the point, allowing the other two locations to remain a location for appeal. (Need to review what the new version of the DS procedures says.) --Izno (talk) 19:54, 3 November 2022 (UTC)
  • I can see a moratorium on appeals if they become disruptive, but otherwise I agree with my colleagues above. Primefac (talk) 13:18, 4 November 2022 (UTC)
  • This sort of turned from El_C saying quite reasonably, that "if a user edited productively for 6 months, it would be likely that their appeal would be upheld" into "don't appeal for 6 months" and then it got repeated over and over. The former is fine, the latter isn't. Otherwise, I agree with my colleagues above. WormTT(talk) 13:58, 10 November 2022 (UTC)
The discussion above is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.

Clarification request: Iranian politics (November 2022)

Original discussion

The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.

Initiated by Stefka Bulgaria at 09:30, 24 November 2022 (UTC)

Case or decision affected
Iranian politics arbitration case (t) (ev / t) (w / t) (pd / t)
Wikipedia:Arbitration/Requests/Case/Iranian politics § Stefka Bulgaria topic-banned

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 Stefka Bulgaria

Could you advice if I am able to make corrections to articles that aren't specifically about Iranian politics, but involve companies controlled by the Iranian government? For example, I see that in my absence, sourced information about an Iranian company has been removed from the article with no apparent justification. Would I be able to restore information of that nature?

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.

Iranian politics: Clerk notes

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

Iranian politics: Arbitrator views and discussion

The discussion above is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.

Clarification request: Should disputed content be left in a BLP while discussion is ongoing?

Original discussion

The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.

Initiated by IntrepidContributor at 16:13, 22 December 2022 (UTC)

Case or decision affected
If your request does not concern a case, provide a link to the arbitration decision affected.

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 IntrepidContributor

There is a dispute on whether it is due to put the claim that Elon Musk is a "polarizing figure" in Wikivoice in the lead of his BLP, and editors in discussions on the TP and BLPN have highlighted WP:BLP and MOS:LEAD as pertinent policies. I don't have a strong opinion on the matter, but I don't think we should put the claim in Wikipedia's voice when it is only based on a few articles that mention the term in passing, and I don't really think its due in the lead given that only one of these sources is cited in the article's main body.

When I twice restored Anythingyouwant's attempt to attribute the claim [3] [4], and explained my position on the talk page [5] [6], HAL333 replied "yeah that's just your opinion man" [7], twice reverted me [8] [9] and posted an edit warring warning on my talk page threatening to also post on this noticeboard [10]. I take HAL333's warning serious since they have reported me there before [11], so I decided not to revert it a third time and request policy guidance from administrators. When I posted my guidance on WP:AN (a noticeboard for "posting information and issues of interest to administrators"), administrators Black Kite said it was the wrong venue and warned me against edit warring, while administrator Black Kite seems to have accused me of noticeboard spamming [12].

As was noted by Anythingyouwant on the TP [13] and BLPN [14], WP:BLPUNDEL indicates that the content should not have been restored till a consensus was formed. I would appreciate some policy guidance from arbitrators on whether disputed unattributed claims should remain in the lead of BLP articles while the discussions in TP and BLPN are ongoing, and may still be escalated to an RFC. I hope this is the right venue to gain a clear clarification on BLP policy (and the proper enforcement of the policy by administrators). IntrepidContributor (talk) 14:15, 22 December 2022 (UTC)

  • @Barkeep49: my request very clearly asks about conduct, and not content. Perhaps I could have worded my request more succinctly, but I am asking if, as WP:BLPUNDEL indicates, disputed content should be removed from BLPs while discussions and consensus building is ongoing. By extension, I ask if administrators should enforce this policy. IntrepidContributor (talk) 16:24, 22 December 2022 (UTC)

Statement by Anythingyouwant

Statement by HAL333

Statement by Black Kite

I think you may find it was Doug Weller, not myself, that warned you about edit-warring, whilst I merely pointed out that your behaviour could be seen as noticeboard-spamming, which ironically this filing appears to have proved. Black Kite (talk) 16:30, 22 December 2022 (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.

Should disputed content be left in a BLP while discussion is ongoing?: Clerk notes

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

Should disputed content be left in a BLP while discussion is ongoing?: Arbitrator views and discussion

  • @IntrepidContributor:, Wikipedia has two kinds of noticeboards: conduct noticeboards and content noticeboards. Conduct noticeboards deal with editor conduct, while content noticeboards handle content issues. This question seems to me to pretty clearly be a content issue. However, WP:AN and this board (WP:ARCA) are both conduct noticeboards. This is why these are the wrong place for your question. On the otherhand, WP:BLPN is a content noticeboard and has had discussion about this topic. That is the right place to gain further input. Barkeep49 (talk) 16:21, 22 December 2022 (UTC)
    @IntrepidContributor your question to us is I would appreciate some policy guidance from arbitrators on whether disputed unattributed claims should remain in the lead of BLP articles while the discussions in TP and BLPN are ongoing, and may still be escalated to an RFC. which is a content not conduct question. You seem to be wondering if others (or you) have edit warred. That would be conduct but this is the wrong place for it, and frankly so is AN. You might have more like at the teahouse getting some guidance like that. Barkeep49 (talk) 21:36, 22 December 2022 (UTC)
  • I am inclined to agree with the administrators at WP:AN. Questions should be answered either at the locations to which you have been pointed and for the reasons you have been pointed to those places, or potentially WT:BLP if you believe there is an issue with the policy (I do not think you think there is). Izno (talk) 17:30, 22 December 2022 (UTC)
  • Yep, this is not a proper ARCA request. If you have nothing to put in the section marked "Case or decision affected", you are not in the right place. Beeblebrox (talk) 19:52, 22 December 2022 (UTC)
  • Concur with the above. As much as I am loathe to send people on a series of "ask the other parent" missions, this does not fall into our remit. Primefac (talk) 16:25, 24 December 2022 (UTC)
  • I would decline the clarification request, and absent objection I will ask the clerks to close this request in 24 hours. Best, KevinL (aka L235 · t · c) 18:04, 1 January 2023 (UTC)
The discussion above is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.

Amendment request: Community ECR request

Original discussion
Much of this discussion has been made moot by the community formally adopting these restrictions at AN. There is a rough consensus of arbs that the restrictions proposed and now passed fall with-in the community's remit and powers. Barkeep49 (talk) 21:18, 9 January 2023 (UTC)

The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.

Initiated by El C at 22:44, 23 November 2022 (UTC)

Case or decision affected
Armenia-Azerbaijan_2 arbitration case (t) (ev / t) (w / t) (pd / t)
Kurds and Kurdistan arbitration case (t) (ev / t) (w / t) (pd / t)
Clauses to which an amendment is requested
  1. Extended confirmed restriction: The extended confirmed restriction is imposed on the area of conflict (from Wikipedia:Arbitration/Requests/Case/Palestine-Israel_articles_4#ARBPIA_General_Sanctions)
  2. Extended confirmed restriction: The extended confirmed restriction is imposed on the area of conflict (from Wikipedia:Arbitration/Requests/Case/Palestine-Israel_articles_4#ARBPIA_General_Sanctions)
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
Information about amendment request

Statement by El C

I realize I'm a broken record, but how record broken is this template? Anyway, there was a proposal at AN (live, permalink) which read:

Proposal: WP:ARBECR (which includes a 500edits/30days restriction) over WP:AA2 and WP:KURDS articles.

That proposal has seen a unanimous 17/17 support, but the proposer (HistoryofIran) and others weren't sure how to affect that resolution. Arb L235 recommended to wait for a WP:CLOSE to do the WP:ARBEE → WP:GS/RUSUKR thing. I said that it'd be better to amend AA2 and KURDS by motion rather than create a new GS with separate logs, alerts, page notices, etc., which is what should have happened with RUSUKR (→ ARBEE).

I think most participants don't really care either way, they just want to see that community consensus affected. Personally, I'm for streamlining rather than adding further to the maze of DS/GS pages, so I'm bringing it here. Needless to say, ARCA is intimidating and has a very high access ceiling (one of the least accessible areas of the project). And I still fucked up that impossible template, but that was always a given (but it sort of displays, so there you go). Thank you for your time and attention. El_C 22:44, 23 November 2022 (UTC)

Barkeep49, yes. As stated, the proposal reads: over WP:AA2 and WP:KURDS articles. El_C 22:56, 23 November 2022 (UTC)
Sorry, writing in haste, but a few quick notes. First, I actually have no firm opinion if the mentioned (17/17) community consensus is an appropriate re/action to whatever influx it represents (long term, etc.). It probably is, but I've not reviewed the material closely, so ultimately can't say that I'm certain about it. Here, I'm mostly just serving as an informal clerk (but also the best clerk!). That said, note that the last ARCA I filed here was also about issues that concern this general region of West Asia and these two associated DSs, in particular (in 2021, I believe; I'll see if I can find it later, now that ARCAs are separately archived thanks to me and to real best clerk, Dreamy Jazz). But as I recall, there was a warning there, a forewarning, even.
But no one remembers, not even me. And, I mean, say this resolution becomes WP:GS/AAKURDS, a split GS like WP:GS/RUSUKR — in a couple of years, when ArbCom subsumes it, no one will remember, either! On a separate note: I hesitated on filing this ARCA because the ACE adds a layer to this that I (best clerk) am a bit uncomfortable with. But the ACE just takes so fuckin' long, it really can't be helped (unless whatever is being discussed coincides with the ACE concluding in, like, a week or mere days). El_C 20:21, 26 November 2022 (UTC)
Wugapodes, no, I'm not calling to abolish all GSs. I'm calling to end parallel GSs for existing DSs (i.e. splits). Not sure what logs have to do with anything, as one is required to log at WP:GS/RUSUKR just as they would if the existing WP:ARBEE would have been amended per community consensus there.
Again, the overarching trend has been to subsume, so for example WP:GS/IPAK no longer runs in parallel to WP:ARBPAK, and so on and so forth (example example). But it doesn't really matter, I've hit a bureaucracy wall here, with reasoning I'm not really able to meaningfully understand; unless it just means 'ArbCom is too busy, do it yourself,' which I'm getting the sense is largely what's behind Izno's stance (i.e. not wanting to spare the time to examine the matter at hand substantively, which in some sense is understandable, busy-busy).
Anyway, I'm not gonna try again, at least not for a long while, so, see you all (?) again at my next ARCA in, like, a year per usual — I'd probably had forgotten by then the extent of the bureaucracy wall, only to be reminded yet again (that, subsume/split, ultimately it's a cycle with not much rhyme or reason). El_C 21:26, 28 November 2022 (UTC)
Izno, in one breath you reject my you're-on-your-own interpretation of your stance, but then in the same breath, you go on to detail basically that very thing: 'the community should own it, not our thing, etc.' Not only that, you then try to impose additional barriers to even have the Committee look into acting on this matter (full RfARs, plural). Honestly, your original terse response, that read dismissive, was better. Better than trying to crank up the inaccessibility even further.
Thanks, though, Wugapodes, for at least trying to think outside the box, and for communicating clearly. So, not all bad; it evens out, I suppose. Maybe the Committee will be able to help after all, if not with the fundamentals (i.e. unrefined ECR), at least with the organization and presentation. Which does count for a lot. El_C 12:13, 29 November 2022 (UTC)
Barkeep49, I call em like I see em. And I don't need anything done, but I'm against some of you seemingly working to make the process even less accessible, when the rest of us are working towards more access. Here, and overall. The way forward is not for you to shelter yourselves from the rest of the project. El_C 16:31, 29 November 2022 (UTC)
Barkeep49, whatever you say, I'll leave you to it. El_C 17:36, 29 November 2022 (UTC)

Statement by HistoryofIran

Statement by Guerillero

These are big topic areas to place under ECP. Is there a more narrow topic area that might work better? --Guerillero Parlez Moi 20:40, 25 November 2022 (UTC)

Statement by ProcrastinatingReader

ECR is pretty draconian and an extreme measure to prevent disruption.

The problem is not inherently with ECR, as I accept it may sometimes–very, very rarely–be appropriate. My concern is: no other lesser restrictions have been considered in that discussion (e.g. a topic-wide semi or ECR on a narrower topic area), no assessment of how many high-quality non-ECP user contributions the topic will lose, and no assessment of the size of administrative burden if a GS is not imposed (which should be a key factor in imposing GS, as otherwise ANI/admins can handle topic disruption as usual). I'm also unsure how this is distinct to other sockpuppeteers who are single-topic focused, we don't fight these with topic-wide ECR. Some of the comments are literally politician's fallacy (e.g. Surely something must need to be done about this disruption.)

If ArbCom is to make a motion, it should be due to substantive agreement and not just rubber-stamping. And ArbCom doesn't need to act here, the community can under the auspices of consensus. If the community wants to motion this, they should do so themselves, but I do wish these GS discussions had some more guidance to, well, guide them. With few exceptions, the fate of almost all community-authorised sanctions is that they were not necessary (see their logs for instance). The only other time the community authorised 500/30 was India-Pakistan I think, which turned out to be unnecessary and was repealed last year after several years of being nominally in force. My overarching point in this paragraph is that the community doesn't have too many tools in its toolbox to deal with this kind of disruption, which I accept is a problem, but it tends to use a hammer when it comes to GS authorisation requests. It's relatively surprising, given how conservative the community is with topical actions otherwise.

I would suggest ArbCom substantively review the issue which caused community concern, in line with WP:AA2/WP:KURDS and Wikipedia:Arbitration/Policy#Jurisdiction (The Committee retains jurisdiction over all matters heard by it, including associated enforcement processes, and may, at its sole discretion, revisit any proceeding at any time.). Not to overrule the community, but to see if ArbCom can identify the locus of problem and form a better tool to deal with these kinds of issues. I think ArbCom is best placed to do this.

Barkeep49 reasons:
  1. I think an ArbCom ECR has a greater chance of being enforced as-written or less chance of being forgotten. In the case of India-Pakistan's 500/30, I'm glad it wasn't enforced as-written, because it was never necessary in the first place, and it would've been detrimental to the encyclopaedia's content if it were enforced. Letting administrators maintain discretion is key, and I think that's more likely with a community GS. And IMO, remedies being forgotten is a decent signs they're no longer (if ever) necessary.
  2. IMO it falls out of ArbCom's scope unless you consider the issue substantively, as the community can and did 'resolve' this. I don't feel it's WP:NOTBURO because WP:ECR prescribes no requirements, not even logging, so there is no bureaucratic overhead or procedural differences, unlike DS. Both community and ArbCom non-DS GS are listed on WP:General sanctions in the same manner. I see no blocker to a new table row being added to WP:GS and am unsure why the Committee is needed here.
  3. I'm not a fan of ArbCom rubber-stamping community motions and implementing them as arbitration decisions, at least if ArbCom wouldn't have made the same decision itself. (Would you have motioned this if the AN discussion never happened and an ARCA was filed detailing the socking problem? Or would you do something else?) In paragraph 1 I outline some issues/omissions in that discussion. I dunno if you agree with any of the points I made, but if you do, I feel like you should be wary of authorising a remedy that may not be tightly fitted to the problem. The numerical vote may be there, but this is a strong restriction, and there is no equally strong discussion. I accept it'll probably be implemented anyway, but it's a community decision, the community should own it and have the ability to directly revoke it.
  4. If you wished, this could be an opportunity for ArbCom to figure out how we can address these issues without ECR. I'm personally sceptical of ECR's proliferation. While I appreciate it stops some bad behaviour, I don't think it stops as much bad behaviour as it does good in most cases, and I'm concerned of you setting a precedent where we turn to properly-enforced ArbCom-authorised broad topic-wide ECR implementations in the face of (potentially transient) sockpuppetry and canvassing. I'd maybe go as far as saying ArbCom should conduct a review of the effectiveness of ECR, in particular does it remain the best tool at our disposal for this problem, and when is it actually appropriate?
ProcrastinatingReader (talk) 22:13, 26 November 2022 (UTC)

Statement by Newyorkbrad

I am not familiar enough with the editing in these topic-areas to opine whether ECR, or any other restriction, is warranted, and I defer to the arbitrators, administrators, and other community members who have commented above for knowledge of the recent editing histories on the topics. I do have two short, more general observations to offer, though, paralleling ones I have made before about other geographical topic-areas:

(1) There is an enormous difference between (for example) requiring 500 edits' experience to edit "all articles about disputes between Azerbaijan and Armenia" and requiring 500 edits to edit "all articles about Azerbaijan and all articles about Armenia." The former is limited to the area of conflict; the latter takes in every article, however non-contentious, between the two countries that happen to be in conflict, and unless the situation has deteriorated to the point where most Armenian editors are unable to edit anything without mentioning Azerbaijan and vice versa, is too broad.

(2) There is also an enormous difference between "administrators, in their discretion, may impose ECR on any article in such-and-such topic-area where problems arise" as opposed to "all articles in such-and-such topic-area are now automatically subject to ECR (whether there have been any problems or not). If the Committee decides to proceed with any motions, please consider these thoughts for what they might be worth. Newyorkbrad (talk) 23:56, 28 November 2022 (UTC)

Statement by Andrew D.

There was recent discussion at ITN about applying such restrictions to discussion of news items such as the recent missile strike in Poland or a fire in Gaza. This seemed to be technically difficult because such discussions are bundled in dated sections rather than on separate topical pages. And establishing the scope of "broadly construed" didn't seem clear either. So, my impression is that the EC restriction already doesn't work well and so further proliferation should be resisted.— Preceding unsigned comment added by Andrew Davidson (talk • contribs) 10:20, 29 November 2022 (UTC)

Statement by Nosebagbear

Over on the VP, I've just given a mixed oppose/support on the issue (I'm also not the only oppose, though certainly still close to). ECR is a very severe restriction, and AA2 is a huge scope unless you don't have much of a link to either country. In terms of the general ECR question, I'd support a restriction on the conflict, but not the individual countries (and just accept that a certain amount of gaming will have to be handled by the standard DS regime).

In terms of "should it be DS at all" - I have made abundantly clear that I oppose DS subsumption of GS without community agreement, but likewise don't really mind if the community itself would like it all under one banner. Though with all that, Izno's position is not unreasonable and has a lot to say for it. Nosebagbear (talk) 10:35, 29 November 2022 (UTC)

Statement by Rosguill

I'm undecided on the merits of the proposal itself, but I want to push back against CaptainEek's characterization of the Arab-Israeli conflict as uniquely thorny or that it goes back thousands of years (case in point: the only way to construe the A-I conflict as thousands of years old is if we include the Roman-Judaean conflict or the early Muslim conquests as part of its scope; we do not apply PIA protection to such articles). Pretty much any ethnic conflict has the propensity to motivate extremely disruptive editing: the question to be answered is whether the level of disruption on Wikipedia merits a given sanction. This should be an assessment of the quality and quantity of edits on Wikipedia alone, not an evaluation of how intractable we believe the actual nationalist conflicts to be. signed, Rosguill talk 16:08, 1 December 2022 (UTC)

Statement by Nil Einne

I don't have an opinion on the need or wisdom of imposing ECP in the area at the time, nor on whether arbcom should take over the community proposal or really anything in the area at this time. But an obvious question if the alts pass, does Wikipedia:Arbitration Committee/Discretionary sanctions#Appeals and modifications apply in entirety? I'm particularly thinking of the ARCA aspect. It seems a little weird that people can appeal to arbcom, or for admins to try and get agreement from abcom before modifying sanctions when arbcom is basically saying they're not taking over this it's still only a community decision; and arbcom stopped considering appeals for community sanctions long ago. Nil Einne (talk) 15:30, 4 December 2022 (UTC)

I see this proposal is maybe somewhat dead given DS/contentious topics motion. Having skimmed through that it maybe does imply that ARCA cannot be used as I guess a community-imposed remedies where discussion is designated to take place on the AE noticeboard is still not a "contentious topic restrictions", and perhaps somewhat clearer, a community restriction even taking place on the AE noticeboard is still not "an arbitration enforcement request". However although again I only skimmed and I'm also fairly tired, it's surprisingly less explicit than I would have though. (I'm mentioning this here since I couldn't figure out any place to comment on the motion.) Nil Einne (talk) 15:57, 4 December 2022 (UTC)

Statement by Paradise Chronicle

In the Kurdish-Turkish conflict area I'd expect for years to come some IP or seldomly also an editor claiming (Turkish, Syrian) Kurdistan does not exist or that some Kurdish organization is terrorist. Usually those IPs/editors don't last for long and are reverted rather quickly. Then a 17/17 support vote for the amendment from also experienced editors in the field should be seen as an alert to a problem that needs to be addressed. Maybe they aren't as experienced in ArbCom policy as the Arbs (I've noticed some hesitation in approving the amendments), but they have very likely a point. If you (the Arbs) could find a feasible amendment/measure to the problem, it would bring some calmness to the areas (also the Armenian-Turkish, in which I have less experience) in question.Paradise Chronicle (talk) 20:15, 16 December 2022 (UTC)

Statement by EvergreenFir

I saw the AN post and then this. I've been mulling this for a while, but I'd like to propose a community or arb DS for Turkey, broadly construed.

The post about the Discord server and subreddit come as no shock as even I have noticed tons of nationalist-oriented SPAs on articles related to Turkey. This spills over into Armenia, Iran, Kurds, Eastern Europe, and Uyghurs. I once asked here if WP:ARBEE applied to Turkey in hopes of finding some tool to help with these editors. I want to go to AN and propose the community sanctions, but worry that might be out of turn if it ends up with the ARBCOM.— Preceding unsigned comment added by EvergreenFir (talk • contribs) 22:23, 16 December 2022 (UTC)

Statement by SilentResident

The nationalist-oriented SPAs are now spilling to articles Aegean dispute, Cyprus and Cyprus–Turkey maritime zones dispute resulting in their indefinite blocks and to article protection level increase. It is a matter of time before SPA pressure for these border topic areas in Turkey's South West and West (Cuprus and Greece) increases, from the moment the border topic areas in Turkey's East and South East (Armenia, Azerbaijan and Kurds respectively) get stricter. It came to my notice that the SPAs are appearing at a time where a growing number of international media is reporting [15][16][17][18][19] an extremely hostile domestic political rhetoric against these neighboring countries. For these reasons, Wikipedia should consider EvergreenFir's proposal to have whole of Turkey covered, or at least include Greece and Cyprus to them. --- ❖ SilentResident ❖ (talk ✉ | contribs ✎) 02:30, 2 January 2023 (UTC)

Statement by TonyBallioni

Noting I've closed the AN proposals as consensus for the sanctions. TonyBallioni (talk) 03:55, 3 January 2023 (UTC)

Statement by {other-editor}

Other editors are free to make relevant comments on this request as necessary. Comments here should address why or why not the Committee should accept the amendment request or provide additional information.

Community ECR request: Clerk notes

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

Community ECR request: Arbitrator views and discussion

  • El C the ask here is to add ECR to Kurds and Kurdistan and also to Armenia-Azerbijan? Just want to make sure I understand this correctly before investigating the substance. Barkeep49 (talk) 22:51, 23 November 2022 (UTC)
    I've thrown up a couple motions below. I'm weakly in support of both but also think the community could just enact based on the consensus of the AN thread, no action from us needed. Alternatively if the intent was always to ask us my wish would be for that to have been noted - as is it's not clear if the editors participating want this to be a community sanction, an arb sanction, or don't care. I post this more in hopes that other community members will weigh in but if nothing happens I'm inclined to support. Barkeep49 (talk) 19:13, 25 November 2022 (UTC)
    ProcrastinatingReader broadly I agree with you on ECR and the role of arbcom and the community. But I am a bit puzzled with how you apply it in this case. The feedback you and Guerillero have given is why I didn't support the motions after proposing them - I wanted to hear from more voices. When you say If the community wants to motion this, they should do so themselves isn't that what happened at AN? So why should ArbCom spend a lot of time making its own determination rather than acknowledging that having parallel ArbCom and Community restrictions is messy and respecting community consensus by incorporating it into ours? Neither of you are opposing the community motion and so absent ArbCom passing these motions these restrictions will still come into effect at some point when someone gets around to closing it and opening the pages, so why not have the simpler method of doing it? Barkeep49 (talk) 17:49, 26 November 2022 (UTC)
    @ProcrastinatingReader if El C had filed a request an ARCA request without that community discussion I would absolutely be taking it seriously given that these remain contentious topic areas and El C actively works them. The argument that having two different sets of places to record issues is to be celebrated as evidence that the community can handle so no need for ArbCom it is not an argument that resonates with me. I'm glad you and Guillero have now opposed at the community discussion. I will continue to wait to see what others in the community have to say. Barkeep49 (talk) 22:33, 26 November 2022 (UTC)
    El C it feels like you're frustrated at the committee for not doing what you want when the overwhelming agreement of the people giving feedback on "should ArbCom do this" (vs people giving feedback in the !vote on "Should the community do this") is no. I get why you're frustrated with this but also do want to call out that it's not like the Arbs are getting caught up in bureaucracy here and not listening to what people want. Barkeep49 (talk) 16:02, 29 November 2022 (UTC)
    Listening to the feedback of the community telling us not to do something feels like the opposite of sheltering ourselves from the rest of the project. Barkeep49 (talk) 17:26, 29 November 2022 (UTC)
  • My read of the discussion is that users don't care but that El C thinks it would be administratively simpler if we did it ourselves. I'm happy to support the motions; I will be copyediting them to be in line with existing ECR remedies shortly. Best KevinL (aka L235 · t · c) 20:17, 25 November 2022 (UTC)
    ProcReader and Guerillero's points here are great, and I will further consider the best path forward. Best, KevinL (aka L235 · t · c) 22:26, 26 November 2022 (UTC)
  • I was going to follow up my below votes with something much shorter and simplistic but much along the same lines as ProcrastinatingReader has this afternoon, but I think his points are better framed anyway. ECR doesn't have any overhead and no fundamental complexity in implementation. Pages get protected and wherever else an unregistered or 'new' editor is editing in the topic area they can be reverted with enforcement at 3RRN. Izno (talk) 22:32, 26 November 2022 (UTC)
    ArbCom is too busy, do it yourself Decidedly not. It is resolutely "the community wants it, so they should own it", as I have said already.
    We could examine it, but if that's what you want, what you actually want are AA3 and KURDS2 cases given the draconian nature of the restriction you are attempting to add committee authorization to and the lack of evidence of disruption the community cannot handle even with existing restrictions under our name (or even attempts to do so), at least as presented here. I'd be willing to entertain such cases, but certainly not in parallel with the community discussion. That discussion could serve as evidence of community discontent making a basis for a case, but I don't think it sufficiently indicates by itself (and by itself I mean in the text of the discussion, not just its existence) the necessity either for arbitration-committee-backed-ECR or any other addition to the discretionary sanctions already available here and maybe isn't even sufficient to take a case. That would be something for WP:ARC either way.
    As for the splitting of documentation and such, it looks like I'm not going to get what I personally want on the matter and arbitration and community documentation is going to fall under the new contentious topics nomenclature with its requirement for summarizing subpages and allowance for use of AE if requested by the community. (Mind you, the new subpages I liked, so I'm quipping mostly about the name and use of AE.) I imagine such subpages could or even should directly display community additions to arbitration remedies or link to the community additions elsewhere.
    So, if this amendment request had shown up literally a week or two later, I would just have said "that looks like sufficient community direction to use the same enforcement/summary mechanisms, go ahead and add it over there as a community restriction in the same area". Maybe I should have said that earlier, but I didn't know if the associated proposals were likely to pass. Izno (talk) 22:30, 28 November 2022 (UTC)
  • @El C: I agree with Izno's reading that a community-imposed ECR restriction doesn't require logging under the cited procedures. Is your goal to eliminate the need for a GS page at all or just logging? I agree with streamlining and harmonizing these processes, but it's not clear to me how us implementing the restriction resolves that. — Wug·a·po·des​ 20:38, 28 November 2022 (UTC)
  • Rosguill Thanks for pointing that out. I'm not sure my analogy landed in the way I wanted it to. So let me say I agree: we should be making decisions based on how disruptive something is being to Wikipedia, and so far we only have evidence that this is disruption based on a short to medium range harassment campaign. I point out the real world dimension because I simply question whether this is actually a long term problem for Wikipedia. It would be a massive waste of admin time to go through the labor of ECP'ing thousands or tens of thousands of pages...for the harassment to die down in a few months or a year, and then we've just neutered a topic area for no reason. CaptainEek Edits Ho Cap'n!⚓ 18:52, 1 December 2022 (UTC)
  • As this has now been implemented by the community, can we finish up here? WormTT(talk) 11:15, 3 January 2023 (UTC)

Kurds and Kurdistan ECR request

The following remedy is added to the Kurds and Kurdistan case:

Extended confirmed restriction

11) The extended confirmed restriction is imposed on all edits and pages related to Kurds and Kurdistan, broadly construed.

Support
Oppose
  1. The original ECR placed on PIA was noted as draconian. If that's what the community wants in this topic area, I think the community should own these accordingly. Izno (talk) 21:53, 25 November 2022 (UTC)
  2. I am sharply opposed to the proliferation of ECR. This is the encyclopedia that anyone can edit. ECR is almost universally so high a burden (to would be editors, and to our administrators) that it has not been implemented even in highly acrid areas. The exception that proves the rule is WP:PIA. PIA represents a simply different paradigm. The conflict between Israel and Palestine is the single most intractable political problem of the last century. It sharply divides dozens of countries and entire populations. It encapsulates an ethnic and religious dispute that goes back thousands of years. It was attracting editors from the entire world that made the topic an unapproachable editing wasteland. I understand that issues with Kurds and AA2 are bad, but they simply pale in comparison to PIA. I might support a narrowly targeted scope, but there isn't evidence to support such a broad scope.
    I understand the idea that if the Community wants this, ArbCom should implement it. But I think a rigid formulation of that rule is unhelpful. Also, the latest five comments at AN all oppose the idea, so I suspect we may seeing a sampling error given that this is a rather stale discussion on AN. I would also caution that the proposal in the AN thread came out of an off-Wiki harassment campaign. The users in question were blocked. We have had harassment campaigns in the past (think Muhammed images, or the vast harassment campaign against Ahmadiyya that plagued VRT a few years ago). But they passed. I do not think implementing long-term ECR across a topic area is warranted in response to a short or medium term problem. I understand the frustration with the topic area, but ArbCom (or the community) should not implement a fundamentally flawed solution just because of frustration. CaptainEek Edits Ho Cap'n!⚓ 08:12, 1 December 2022 (UTC)
Arbitrator discussion (Kurds and Kurdistan ECR request)

Armenia-Azerbaijan ECR request

The following remedy is added to the Armenia-Azerbaijan 2 case:

Extended confirmed restriction

3) The extended confirmed restriction is imposed on all edits and pages related to Armenia, Azerbaijan, or related ethnic conflicts, broadly construed.

For administrative simplicity, the section titled "Standard discretionary sanctions" is redesignated as Remedy 4 of the Armenia-Azerbaijan 2 case.

Support
Oppose
  1. The original ECR placed on PIA was noted as draconian. If that's what the community wants in this topic area, I think the community should own these accordingly. Izno (talk) 21:53, 25 November 2022 (UTC)
  2. Refer to my vote on the first motion. CaptainEek Edits Ho Cap'n!⚓ 08:13, 1 December 2022 (UTC)
Arbitrator discussion (Armenia-Azerbaijan ECR request)
Copyedited both motions. This second one is a bit messy because the case page is a bit messy and this motion redesignates the currently un-numbered remedy "Standard discretionary sanctions" with a remedy number for future ease of reference. When enacting this motion, it would be great if the clerks would also collapse all rescinded or superseded text on the case page. Best, KevinL (aka L235 · t · c) 20:26, 25 November 2022 (UTC)

Kurds and Kurdistan ECR request (alt)

The following remedy is added to the Kurds and Kurdistan case:

Extended confirmed restriction

11) The committee authorizes using the procedures of remedy 1 to administer a community-imposed extended confirmed restriction in the topic area or any sub-topic. For administrative simplicity, alerts, warnings, and sanctions regarding a community-imposed extended confirmed restriction may be given as if the Arbitration Committee had authorized an extended confirmed restriction. If the community repeals its extended confirmed restriction on this topic area, this remedy will be automatically revoked.

Support
Oppose
Arbitrator discussion (Kurds and Kurdistan ECR request alt)


Armenia-Azerbaijan ECR request (alt)

For administrative simplicity, the section titled "Standard discretionary sanctions" is redesignated as Remedy 3 of the Armenia-Azerbaijan 2 case.

The following remedy is added to the Armenia-Azerbaijan 2 case:

Community-maintained extended confirmed restriction

4) The committee authorizes using the procedures of remedy 3 to administer a community-imposed extended confirmed restriction in the topic area or any sub-topic. For administrative simplicity, alerts, warnings, and sanctions regarding a community-imposed extended confirmed restriction may be given as if the Arbitration Committee had authorized an extended confirmed restriction. If the community repeals its extended confirmed restriction on this topic area, this remedy will be automatically revoked.

Support
Oppose
Arbitrator discussion (Armenia-Azerbaijan ECR request alt)
  • So I'm going to think outside the box here, and try to hash out a compromise. I'm incredibly sympathetic to the idea that we should reduce the maze of templates, logs, and pages required for what are essentially parallel ArbCom and community sanctions; it's bad from a maintenance perspective, from an administrative perspective, and from an editorial perspective. We should avoid duplicating work where possible. That said, I'm also sympathetic to the idea that the community should ultimately be the one to own these restrictions, and ArbCom shouldn't subsume sanctions that the community is capable of administering itself.
    The issue I see is that the community (or at least El_C who does his fair share of the DS/GS work) would like to use our infrastructure for it's sanctions, but we have no mechanism for that other than subsuming the sanctions which (like this situation) isn't always the ideal choice. We need some (new) way of allowing the community to use our infrastructure, but leave the actual maintenance of the sanction (including its repeal) up to them.
    So the two alternative motions I'm proposing are a little rough, I'd welcome copyedits, but I think the gist is there. We make clear that these are community-imposed sanctions, but we authorize the use of our (soon to be renamed) DS infrastructure for administrative simplicity; don't worry about the GS/DS distinction, if you act like the ECP is a DS no one will yell at you. The community maintains control over when to terminate the sanction, and if they do so, this whole thing becomes null without us having to do anything; we can revoke this authorization early by motion if it turns out to be a horrible idea in practice. — Wug·a·po·des​ 22:28, 28 November 2022 (UTC)
    This was also the direction that I've been thinking – if I can get past my current questions about whether ECR would be a Bad Thing here. Best, KevinL (aka L235 · t · c) 22:59, 28 November 2022 (UTC)
    I think these are basically (American) mooted by the DS rework as I noted above that we posted almost simultaneously. Izno (talk) 23:27, 28 November 2022 (UTC)
    I think so too. But this is also why I've asked for clear sample language for the community to use in such instances. One of the hang-ups for me is that there is a clear understanding by the community, when participating in the discussion and voting, what they're voting for. Given the idea of merging with ArbCom came after discussion had (at that point) died down is part of my overall reluctance in this instance. Barkeep49 (talk) 23:43, 28 November 2022 (UTC)
The discussion above is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.
Retrieved from "https://en.wikipedia.org/w/index.php?title=Wikipedia:Arbitration/Requests/Clarification_and_Amendment/Archive_123&oldid=1132765144"