1, 2, 3, 4, 5, 6, 7, 8, 9, 10 |
ArbCom 2020 Elections voter message
A barnstar for you!
The Tireless Contributor Barnstar | |
Thank you for closing the RfC on People's Mujahedin of Iran. I suspect it wasn't easy to go through all the material, so I just wanted to show my appreciation for your thorough evaluation. Stefka Bulgaria (talk) 19:18, 29 November 2020 (UTC) |
Hi, if you are able to view a Newspapers.com clipping, you should clip it and post it as open access. Considering that you are quoting those bombshell allegations against President Johnson and Congressmen keeping mistresses in their hideaways, you can assume that most readers would want to see the source. I clipped and formatted the Newspapers.com reference for you. Please do this in future. Thanks, Yoninah (talk) 21:13, 29 November 2020 (UTC)
- Thanks for handling the clipping, Yoninah, but I'm not sure what's "bombshell" about a 30 year old story that repeats the historical consensus of Johnson's personal life. Chetsford (talk) 23:07, 29 November 2020 (UTC)
- Well, it was news to me. BTW this is a really fun subject. There are a lot of books written on it, though most are only available in snippet view. I added a bunch of references. Thanks for coming up with these U.S. government themes. Yoninah (talk) 23:31, 29 November 2020 (UTC)
- Gracias, Yoninah! I'll make a note to more consistently clip newspapers.com references. Chetsford (talk) 15:35, 30 November 2020 (UTC)
- Well, it was news to me. BTW this is a really fun subject. There are a lot of books written on it, though most are only available in snippet view. I added a bunch of references. Thanks for coming up with these U.S. government themes. Yoninah (talk) 23:31, 29 November 2020 (UTC)
Closing at Talk:Territorial evolution of Russia#RFC about the spelling of a specific place name to use here
Hi. Thanks for closing the RFC.
Why is “longstanding usage” privileged, and which guideline does this follow? The guidelines and normal practice afford primacy to the main article title, Kyiv, as is stated, for example, in MOS:CAPS#Place names, “In general, other articles should refer to places by the names which are used in the articles on those places, according to the rules described at Wikipedia:Naming conventions (geographic names). If a different name is appropriate in a given historical or other context, then . . .” (my emphasis). Historical usage is an exception.
And your comment about this being “consistent with the close of a related RfC” seems backwards. That other RFC is recommending an exception to the normal usage of the main-article title. Since the RFC showed no consensus favouring the exception, then the normal rule applies. Any privilege of “longstanding usage” was overturned by the consensus move to Kyiv, which led directly to that RFC and this one.
(Additionally, the article in question arguably does not meet the criteria of the other RFC, as it is in its terms neither an “unambiguously historical” nor “an edge case” since its scope explicitly includes the period after both 1991 and 1995, as stated in the introduction. It is a survey article that includes previous history to the present, like, e.g., History of Kyiv) —Michael Z. 03:58, 30 November 2020 (UTC)
- Sorry, that should have read "we should privilege" (I accidentally dropped "should") and, as noted in the close, is not "part of the closing decision". The closing decision was no consensus and the rest a suggestion that editors can action or ignore at their discretion. I apologize if I imperfectly expressed that and will edit it to more clearly communicate the point.
Insofar as WP:NCGN is concerned, it also sets out that "when a widely accepted English name, in a modern context, exists for a place, we should use it" which was the argument of the "Kiev" !voters. Your objections to that position should be made to them in the RfC. The closer's only role is to determine the strength of the arguments presented during the RfC, he is not an interlocutor in the discussion. - "It is a survey article that includes previous history to the present" That is, to me, inconsistent with the idea of something that is "unambiguously current" and is the very definition of an edge case. Chetsford (talk) 15:26, 30 November 2020 (UTC)
- Okay, thanks again.
- FYI, in the Kyiv article move, both move and keep arguments cited common name, and the decision explicitly stated there are two common names, but Kyiv better met our guidelines and is favoured by a 2-to-1 majority of participants.
- The “historical article” RFC gives one specific example of “unambiguously current / ongoing topics (e.g. Kyiv Metro),” an article that begins with the largest section, a “History” survey going back to Russian-empire times. The RFC question is vague in some ways, but in this we have the very definition of current. —Michael Z. 16:20, 30 November 2020 (UTC)
- Those sound like compelling arguments to make in an RfC. Chetsford (talk) 16:29, 30 November 2020 (UTC)
- The “historical article” RFC gives one specific example of “unambiguously current / ongoing topics (e.g. Kyiv Metro),” an article that begins with the largest section, a “History” survey going back to Russian-empire times. The RFC question is vague in some ways, but in this we have the very definition of current. —Michael Z. 16:20, 30 November 2020 (UTC)
RfC closure
Thanks for taking the time to go through the RfC and closing it here. You said that only "three are opposed" to the proposal, but I count 6: Mhhossein,[1]Pahlevun,[2] Ali Ahwazi[3], Jushyosaha604,[4] Sa.vakilian,[5] and myself[6][7].
Secondly, I feel the RfC was closed in the middle of a discussion (even though I know it was well past the 30 days). For example, on 27 November I argued that the original proposal's wording was contrary to MOS:WEASEL. I was hoping to get some responses to that, yet you closed the RfC on November 29. Would you please re-open the RfC and let that discussion conclude?VR talk 11:12, 30 November 2020 (UTC)
- This sort of pressure cast on the closing admin to either revert the decision or re-open the RfC happens each time a decision doesn't go their way. This RfC was reviewed by an experienced admin who gave a thorough closing remark on their decision, so it was closed properly and there is no need to re-open it. I'll spare the pinging of other voters from that RfC (which would turn this talk page into a horrid mess) and just point out to what Chestford suggested in the closing remarks: VR, if you want to propose a modification to the current consensus, then start a new talk page discussion (like the rest of us have been doing). Stefka Bulgaria (talk) 12:35, 30 November 2020 (UTC)
- Without going through these one by one, the additional !votes you cited are ambiguously opposed to the proposal. For instance, Jushyosaha604 only clearly registered a !vote in favor of your alternate version without actually objecting to adoption of Stefka Bulgaria's proposal (in that case, they did critique Stefka Bulgaria's version by saying it "removed too much information" but many !votes, both in favor and against, contain extended narratives qualifying their !votes; the onus is ultimately the editor's to present their opinion in an unambiguous way, not the closer's to interpret !votes when their construction is so inscrutable as to conceal their gist). Because consensus is not a vote, but a means of incorporating all legitimate concerns, an editor who expresses nothing more than a glancing style note to the proposal may be unsatisfied with the outcome of the RfC if their actual intent was absolute objection. The RfC ran 30 days and, while that is not a hard stop, it's sufficient time if discussion has come to a natural conclusion. At the time of close, there had not been an original !vote for five days. You can appeal the close per WP:CLOSE. Chetsford (talk) 15:05, 30 November 2020 (UTC)