Jump to content

Wikipedia:Village pump (idea lab)

From Wikipedia, the free encyclopedia
 Policy Technical Proposals Idea lab WMF Miscellaneous 
Shortcuts
The idea lab section of the village pump is a place where new ideas or suggestions on general Wikipedia issues can be incubated, for later submission for consensus discussion at Village pump (proposals). Try to be creative and positive when commenting on ideas.
Before creating a new section, note:

Before commenting, note:

  • This page is not for consensus polling. Stalwart "Oppose" and "Support" comments generally have no place here. Instead, discuss ideas and suggest variations on them.
  • Wondering whether someone already had this idea? Search the archives below, and look through Wikipedia:Perennial proposals.

Discussions are automatically archived after remaining inactive for two weeks.

« Archives, 41, 42, 43, 44, 45, 46, 47, 48, 49, 50, 51, 52, 53, 54, 55, 56, 57, 58, 59, 60, 61

Fix Draftification with a new template

[edit]

Draftification has long been criticized as a backdoor to deletion. In New Pages Patrol (NPP), it is common to move new articles that are not ready for mainspace to draftspace. This way, articles that could potentially be suitable for Wikipedia, but are not yet, are preserved. The article creator then gets a chance to improve their article without NPPers breathing down their necks or having it taken to Articles for Deletion. If anyone, including the article creator, objects to draftification, the article should be moved back to mainspace (draftification should be reversed). This is explained by DRAFTNO #6 and #7. No reason is required for the objection.

Problem: However, we also have a rule that drafts that haven't been edited for six months get automatically deleted, under Criterion for Speedy Deletion G13. So, well-meaning New Page Patrollers will unilaterally draftify new articles that are not yet ready for the encyclopedia. The new editors who created the article may disagree with the move, without knowing that they can object. The new users can get discouraged and leave Wikipedia altogether, and after six months the draft is deleted under CSD G13. As this process happens without community discussions, it results in draftification being called a "backdoor to deletion".

Solution: This problem can be solved without changing policy or current practice. We just need to make it very obvious to new users that they can object to draftification. We can also make it easy to reverse the draftication (assuming the new user is autoconfirmed). I suggest we do this by adding a template to all draftified articles. The template would include a big blue button, similar to the "Submit the draft for review!" button at Template:AfC submission/draft, which says "Object to this move". Clicking this button either: 1. Leaves a message on the talk page of the editor who draftified, notifying them that there has been an objection to the move and requesting that it be immediately reversed. 2. Moves the page back to mainspace automatically, or if the editor's account is unable to perform this task, creates an entry at Requested moves/Technical moves to that effect. The latter is better, but also more technically complex. Adding a similar button to Template:Uw-articletodraft, the warning typically given upon draftification, would also be helpful.

Implementation: Once the new template is ready, it can be added to MPGuy's MoveToDraft userscript, which is the most common way for NPPers to draftify articles. It should be placed above the AfC template on all draftified articles.

I would appreciate comments from technically skilled editors, who could create this template (or tell me that it's impossible), from NPPers who draftify articles, and from uninvolved editors who have opinions on the draftification process. Toadspike [Talk] 10:37, 26 September 2024 (UTC)[reply]

This idea isn't really my own, it was obviously sparked by the most recent RfA. A similar idea was previously discussed here, but that discussion proposed a requirement that all editors have to follow (policy), not a technical solution, and turned into a trainwreck. To prevent something similar, I ask all participants to please focus on improving the current situation instead of debating the morality of draftification as a whole. Toadspike [Talk] 11:03, 26 September 2024 (UTC)[reply]
Notifying the users who commented most directly on this topic at the RfA: @Alalch E.@User:Onel5969@User:Hobit@User:Fangz@User:Nsk92. I have also notified the NPP Talk page and posted a message on Discord. I am not sure how to notifying all participants of the previous discussion (aside from doing it manually) and I am not sure that is productive considering how many people were involved and how offtopic it got, so I won't do that for now. Toadspike [Talk] 11:07, 26 September 2024 (UTC)[reply]
Are you sure you want to make this an RfC? Is there a BEFORE somewhere? Aaron Liu (talk) 11:32, 26 September 2024 (UTC)[reply]
Good point, I am not sure if the RfC label applies, so I'll remove the templates. I was looking for ways to notify people and misread RFCBEFORE. Toadspike [Talk] 11:34, 26 September 2024 (UTC)[reply]
  • Oppose: The draftification message could be tweaked, but a big button to reverse the move will lead to more AfDs, higher strain on NPP, more BITEY behaviour, and worse editor retention. Draft space is incredibly valuable, and people have some incredibly warped views about the space. If we did something like this then we'd end up chasing away new editors because learning how to make your article meet our complicated guidelines in under 7 days (AfD tag) is not easy for a lot of folks. Draft space gives them the opportunity to work on the content, to receive advise, and to make articles that will actually survive at AfD and allow them to stick around. Really we need to draftify more, and I've taken it upon myself to begin to do so again and encourage others to do. I'm big on editor retention. This is not the way to do it. Hey man im josh (talk) 12:15, 26 September 2024 (UTC)[reply]
    The problem with unilateral draftification is that it can also be incredibly bitey, especially when done for arbitrary reasons that have nothing to do with any of the reasons why something might be deleted at AfD (although this is less prevalent than the trivial reasons things are rejected at AfC). We should be draftifying fewer articles and not sending them to AfD either but rather leaving them in the mainspace (With appropriate tags where justified) so that they can be found and improved rather than pretending that they don't exist for six months and then deleting them. Thryduulf (talk) 12:34, 26 September 2024 (UTC)[reply]
    I'm not really convinced draftification is any worse than the alternatives - tagging is *also* bitey as well, and one user tagging an article and leaving it in mainspace could lead to another user seeing it and deciding to AfD. Draftification could be a way to protect an article until it enters a better state. But I think the other part I have an issue with is the lack of clear guidelines. Clearly some people have an issue with draftification and others do not, and people have different ideas what it is for. That needs to be made more concrete. Otherwise just saying "we should use draftification less" isn't going to lead to any positive changes. Fangz (talk) 12:43, 26 September 2024 (UTC)[reply]
    I agree with the general sentiment – arguing for more or less draftification does not solve the problem that new users basically can't object to it. Toadspike [Talk] 12:47, 26 September 2024 (UTC)[reply]
    I envision a template (possibly one specific for relatively new users?) being something like:
    1. Hi, this article has been moved to a draft form because another user thinks it has potential but is not ready for the encyclopedia just yet. REASON:
    2. You can continue to work on it while it's not published, though note that if not editted for 6 months it will be deleted. Here are some useful resources.
    3. When you think the article is ready you can submit the article to a review, which can give useful feedback. []
    4. Alternatively you may return the article to the main encyclopedia at any time and have it be editted while part of the main encyclopedia. See WP: Draft Object. Note however that if other users think there are unfixable issues with the article it may be put forward as a candidate for deletion. Fangz (talk) 12:54, 26 September 2024 (UTC)[reply]
    I like the idea for the user warning. Aaron Liu (talk) 12:59, 26 September 2024 (UTC)[reply]
    Tagging never leads to an article being automatically deleted. – Joe (talk) 18:43, 26 September 2024 (UTC)[reply]
    In my view draftified articles should (semi?) automatically return to the mainspace after timeout instead of be deleted. Or at least be re-evaluated for notability. I do not really see the reason for automatic speedy deletion, except as backdoor deletion. Fangz (talk) 18:59, 26 September 2024 (UTC)[reply]
    I like that idea. They don't, though, so it's a bit of a moot point in terms of current policy. – Joe (talk) 06:16, 27 September 2024 (UTC)[reply]
    Why can't they just improve it in mainspace, without the sting on of an initial rejection and a six month deletion countdown hanging over them? I don't get why you keep presenting this as a choice between draftspace and AfD. – Joe (talk) 18:46, 26 September 2024 (UTC)[reply]
    The reason is that "improving it in mainspace" has its own issues. An article in mainspace has to juggle being of service to the reader to being of service to the editor. This implies formal processes and wikijargon for consistency, unified templates for issues in the article, clear and ruthless labelling of problems and so on. There's a strong tendency for the first experience of an editor to be a very public and humiliating fight against established editors who have a better understanding of wikipedia processes, quickly driving the editor away or getting them blocked. It is also very difficult to improve on this experience as it would imply fundamental changes affecting all sorts of things. Meanwhile improving an article in draft mode allows for a more informal process of communication to shepherd an article towards an acceptable state. Fangz (talk) 19:10, 26 September 2024 (UTC)[reply]
    I did a little work on page view statistics recently. The median article gets about one page view per week. So if the new article is typical, then it doesn't have to "be of service to the reader", because there aren't really any readers. Editors (especially NPP and RecentChanges folks) may look at a brand-new article a few dozen times on the first day, but once the reviewers leave it alone, most articles just don't have much traffic.
    I think the reason we are unwilling to "improve it in mainspace" is because we're scared that we'll forget that it was there, and years later, someone will be embarrassed to discover that an WP:UGLY article has been neglected ever since. We are using draftification and other threats as a way to make other WP:VOLUNTEERS improve the article to our idea of acceptable quality. WhatamIdoing (talk) 20:40, 26 September 2024 (UTC)[reply]
    I don't know if we're looking at different draft namespaces, but an "informal process of communication to shepherd an article towards an acceptable state" sounds like the precise opposite of our current AfC process. – Joe (talk) 06:19, 27 September 2024 (UTC)[reply]
I don't like the idea of a button but I do think the template should be changed. I think having a button suggests it's a default option, but I think a link is okay. Fangz (talk) 12:37, 26 September 2024 (UTC)[reply]
  • This is the idea lab so no bolded comment from me, but I have mixed feelings. I am in favour of softening the experience for newcomers, but I'm opposed to the concept of draftification being automatically reversible. If a new page patroller reviews a new article and moves it to draft because it's clearly unsuitable for mainspace, the creator should need to do more than just say "I object" in order to move their clearly unsuitable article back again. I've recently proposed that all of draftspace should be move-protected at the semi level (the proposal was not well received - fair enough). This is probably the rule I ignore more than any other on Wikipedia, mostly dealing with spam sockfarms that try to abuse the rule to promote their garbage. Besides, a new user whose submission is quarantined to draft space and they're left with instructions and a list of suggestions with helpful links is already getting better treatment than most editors ever have or will, and if their reaction to that is to rage-quit then they're probably not a good fit for the collaborative environment of Wikipedia anyway. Ivanvector (Talk/Edits) 12:57, 26 September 2024 (UTC)[reply]
    @Ivanvector, you know the joke about "If you ask three people, you'll get four opinions"? I wonder if we ask three NPPers what "ready for mainspace" means, if we'd get four opinions. AFAICT, "ready for mainspace" most often means "contains at least as many refs as the median article, but higher quality ones". All the children in Lake Wobegon are above average, and all the new Wikipedia articles must be, too. WhatamIdoing (talk) 20:12, 26 September 2024 (UTC)[reply]
    I feel like I might vaguely recall a discussion on that topic sometime in the not too distant past. Folly Mox (talk) 22:55, 26 September 2024 (UTC)[reply]
    176 comments from 22 editors, and I probably had 22 opinions all by myself. ;-) WhatamIdoing (talk) 22:23, 27 September 2024 (UTC)[reply]
    All pages are effectively move-protected at the semi level already. Moving requires an (auto)confirmed account. SilverLocust 💬 07:17, 5 October 2024 (UTC)[reply]
  • As far as I see it draftification should never be used for subjects which pass GNG, and it should only be standard for things like films/TV series/games which are in the works but have not yet begun production. Subjects with debatable notability should be sent to AFD to the issue can be resolved.★Trekker (talk) 13:00, 26 September 2024 (UTC)[reply]
    Subjects that pass WP:GNG should never be draftified at all, instead they should be tagged and dealt with using normal community procedures. I agree that films/TV series/games/political events probably best fit the bill for draftifications, but so do potentially notable but underdeveloped articles. Sohom (talk) 13:33, 26 September 2024 (UTC)[reply]
    This is out of step with the present form of Wikipedia:DRAFTIFY, and I don't think it makes sense anyway. Articles that fail GNG should not be draftified, they should be AfDed. Films etc that are in the works should not be draftified merely because they aren't in production, and it's not really a great use for draft space because there's no guarantee that there would be a change of situation to establish notability within 6 months. Articles should be draftified only if the reviewer believes the article can be editted into an acceptable state within the time window. This implies a pass of GNG - i.e. a belief that reliable sources are potentially out there. Remember that GNG is about the *subject*, not about the state of the article. Fangz (talk) 14:09, 26 September 2024 (UTC)[reply]
    In my view the correct use of draftification is sort of as an alternative version of the WIP template. An acknowledgement that the article is not ready and should be being worked on and will likely have multiple issues, but in a protected sandboxed environment to avoid overly zealous moderation and promotion of misunderstanding for casual readers, and without implying the original editor is the one working on it. For new users it should offer a less formal and jargony process to learning how to improve an article than tagging based methods, because the latter has to balance the need to inform *readers* as well as editors. Fangz (talk) 14:23, 26 September 2024 (UTC)[reply]
    If you evaluate that a article passes WP:GNG, then there is not point in draftifying it, you could just add a {{sources exist}} template, patrol and move on. Alternatively, if you evaluate that a article fails WP:GNG, there is no point in wasting the article creator's time and you should WP:AFD/PROD it.
    The only case where you would draftify a article is if you saw a article that a) had a credible claim to significance/notability b) does not meet/prove notability in it's current state c) has been created in the last week or so by a inexperienced article creator. Sohom (talk) 14:43, 26 September 2024 (UTC)[reply]
    Not sure if we're disagreeing or we're having some semantics thing about what "passes GNG" means.
    But anyway there's issues beyond notability, in my view that's probably more useful. Fangz (talk) 15:08, 26 September 2024 (UTC)[reply]
    If an article has a credible chance of being kept or merged at AfD then it should not be draftified.
    If an article would definitely fail AfD and there is no editing that can fix that it should be sent to AfD. Thryduulf (talk) 15:57, 26 September 2024 (UTC)[reply]
    I think then you're pretty much arguing that the draftification process should be removed entirely, and I don't agree with that. It has its advantages. It should not be made a mandatory process by any means but just as some users prefer to work on articles as a draft and then push to the public wiki, it can be a better resolution to certain issues than the alternatives. Fangz (talk) 17:44, 26 September 2024 (UTC)[reply]
    I'm not sure that the Draft: namespace has any advantages over a user sandbox, and m:Research:Wikipedia article creation and m:Research:AfC processes and productivity says that the Draft: namespace is where articles go to die.
    I do think that we've fallen into a false binary here. The options are not "garbage in the mainspace" vs "auto-deleted as in the draftspace". There are other options (e.g., sticky prods for uncited articles, userification, bold stubbification, bold merging, developing a more consistent and predictable standard for evaluating articles, etc.). WhatamIdoing (talk) 20:20, 26 September 2024 (UTC)[reply]
    I think there is a argument to be made that this landscape might have changed a fair bit since this research was done. The latest data that these projects consider is from 2014-2017. WP:ACTRIAL happened after that research was done, and Wikipedia's policies have changed since those times. Sohom (talk) 20:48, 26 September 2024 (UTC)[reply]
    It's possible that things have changed, and I'm never one to turn down a new research project if you happen to be volunteering to do it (I believe that all the necessary data is public), but looking at the overall deletion rate in that namespace, it seems unlikely that the result will be materially different. WhatamIdoing (talk) 20:31, 27 September 2024 (UTC)[reply]
    I think then you're pretty much arguing that the draftification process should be removed entirely, and I don't agree with that. I'm sorry to pick on you but this is the clearest example yet of the circular reasoning that has got us into this mess: draftification must be good because we do it, so we must keep doing it because it's good. From literally the moment draftspace was created and people started doing this (before that, the equivalent process of userfication was expressly forbidden without prior discussion), others have been pointing out that the underlying logic makes no sense. Draftification is only for articles that shouldn't be deleted, but it's also only for articles that can't be in mainspace. But since fix good content in place is a part of the editing policy and almost all the community accepted reasons for deletion involve the potential of the article, not it's current state, the intersection of those two sets is functionally zero (apart from some consensus-established edge cases like paid creations or upcoming films).
    This is why attempts to clarify and improve policy around draftification—and I've been closely involved in many of them—keep failing. You try to find a solid basis for guidelines and there just isn't one. We really need to stop trying to square the circle of justifying draftification as it is practiced now, and start asking what we the community actually wants to achieve with it and whether what we're doing now fulfils that aim. So far it's not looking good for the send-them-all-to-draftspace-and-the-god-of-notability-will-recognise-his-own camp, because there's not a shred of evidence that it helps improve content, retain editors or manage the NPP workload, and as WAID says above the empirical studies we do have concluded the precise opposite. But that picture could change with more research – somebody just needs to step up and do it! – Joe (talk) 07:01, 27 September 2024 (UTC)[reply]
    @Joe Roe Draftification is only for articles that shouldn't be deleted, but it's also only for articles that can't be in mainspace. That is the exact reason why draftspace exists in the first place. Imagine you see a article with the following content: Nicholas Carlini is an amazing researcher at Google working on adversarial machine learning. created in the last week or so and sourced to a person's personal web-page. On doing a quick google search, you see that the person exists and is a researcher at said company, however, due to your unfamiliarity with adversarial machine learning topic-area you are not able to immediately identify the person's impact on the field. Do you 1) WP:BITEly nominate the article for deletion 2) leave the content up for somebody to deal with it (and hope that the other somebody will not choose option 1) or 3) draftify the article with a note that more sources are required to prove notability? Sohom (talk) 11:25, 27 September 2024 (UTC)[reply]
    @Sohom Datta None of them. What you do is add a template to the article noting the lack of sources, leave a friendly message on the creator's talk page explaining the issues in plain English, and leave a note about it at Wikipedia talk:WikiProject Computer science. Depending on what your research found you could add more information, add some sources that might or might not demonstrate notability, remove the peacock terms, etc. Yes, this is more effort than blinding draftifying or AfDing but it is far more important that things get done well than things get done quickly. Thryduulf (talk) 12:37, 27 September 2024 (UTC)[reply]
    @Sohom Datta, thanks for creating Nicholas Carlini, whose first version does not contain the hypothetical sentence you gave in your comment above. In your example above, why can't that stay in the mainspace? I frankly don't love it, and I'd immediately pull the word "amazing" out, but what's the policy basis for saying "that article truly can't be in mainspace"? WhatamIdoing (talk) 21:10, 27 September 2024 (UTC)[reply]
    @Fangz I'm not arguing for the elimination of draftspace, it has it's uses as an optional space where articles can be developed over time so they don't have to meet all the relevant content policies from the very first edit. I'm also not arguing for the elimination of all draftifcation, just the majority of unilateral draftification because, as Joe has put better than I can, it is not a net benefit to the project as currently practised. Thryduulf (talk) 12:46, 27 September 2024 (UTC)[reply]
    There's a middle ground between meets-GNG-mark-as-reviewed and fails-GNG-send-to-AfD: recently created articles where the sources in the article do not validate GNG, but where the new page reviewer hasn't done a BEFORE search. I think it's perfectly fair (and permissioned within the current draftification process) to say "this recently created article doesn't demonstrate GNG yet, but I'll kick it back to the creator in draft form to put in some more sources." Dclemens1971 (talk) 04:43, 29 September 2024 (UTC)[reply]
    Punting it to draftspace without doing a BEFORE is definitely not something we should be tolerating. Thryduulf (talk) 10:21, 29 September 2024 (UTC)[reply]
    This would mean we're either leaving these articles unpatrolled (which is obviously undesirable), or giving new page patrollers the job of finding sources on every article where the original author hasn't, which would be ideal in, well, ideal conditions, but puts the burden of actually sourcing the encyclopedia on a very small group of editors. In my opinion, there should be a way to ask the original author to add sources to show it meets GNG, beyond just putting a "notability" tag and being done with it. Chaotic Enby (talk · contribs) 19:53, 1 October 2024 (UTC)[reply]
    I agree with Chaotic Enby. Drafification is a good solution because it strongly encourages the author to improve the article, and, most importantly, gets it out of mainspace so that it isn't a problem for innocent readers – without forcing NPPers to clean up other peoples' messes. Cremastra (talk) 20:06, 1 October 2024 (UTC)[reply]
    Drafticiation [...] strongly encourages the author to improve the article. That's the theory but the evidence is that in practice it very rarely does this. There is also little to no evidence that most pages moved to draftspace are actually a problem for innocent readers rather than being a problem for those who want immediate perfection. Thryduulf (talk) 20:47, 1 October 2024 (UTC)[reply]
    About wanting to ask the original author to add sources to show it meets GNG, beyond just putting a "notability" tag and being done with it, I wonder if it's actually possible to do this in a non-coercive way. The options right now are:
    • Just ask (what the {{notability}} tag does).
    • Ask under threat of deletion (WP:BLPPROD and WP:PROD).
    • Move article to Draft: space (essentially holding the article hostage, to be deleted if you give up or can't figure out how to do it).
    • Send to AFD today.
    AFAICT a method for "force another WP:VOLUNTEER to improve the article to my standards" option has proven pretty elusive. But if you want to reach that point, I suggest that you take a baby step towards it in the form of getting a policy (any policy, really) to actually, directly, unambiguously say that every article must cite at least one source. Until the community agrees that this actually is a requirement, then we have no hope of getting them to increase the requirement all the way up to "show it meets GNG". WhatamIdoing (talk) 00:20, 2 October 2024 (UTC)[reply]
If a new editor thinks their article is ready for mainspace, they will put it there. They will also happily revert the move. If a new editor is unsure, they will probably ask for help first or use draftspace. Cremastra (talk) 19:35, 26 September 2024 (UTC)[reply]
I think the concern expressed by Joe and others who support the "backdoor" theory is that new users do not know how to revert the move to draftspace. Do you disagree with that assumption? Toadspike [Talk] 19:53, 26 September 2024 (UTC)[reply]
I think most users do not know how to revert the move, yes. I also think we shouldn't hand it to them on a silver platter, because that likely largely annuls the whole point of draftification. What is the solution to this? I couldn't tell you. Cremastra (talk) 20:09, 26 September 2024 (UTC)[reply]
Is "the whole point of draftification" to make my view of the subject's value more powerful than the newbies' view? Security through obscurity kind of works for that, but not reliably. WhatamIdoing (talk) 20:22, 26 September 2024 (UTC)[reply]
They don't know how, maybe, but more importantly that they don't know that they're allowed to. We have to remember how very unusual our collaborative process is. If an inexperienced editor contributes an article to Wikipedia and then it is swiftly unpublished with a message that there's something wrong with it, they won't think, hmm, I'm not sure if I agree with that, I'm going to revert and/or discuss this with my peer-editors to find a consensus. They'll think that with someone the authority to decide what happens to articles has rejected my contribution, and I'm a mere newbie. At that point they will either give up (the majority) or they'll persevere and get into cycle of trying to satisfy first the NPP reviewer and then a succession of AfC reviewers until they finally give up or manage to write a GA, which seems to be roughly the standard AfC is applying these days Even very experience editors fall into this trap because even though the templated messages try to communicate the full range of options the user has (now at least, after I and others have spent several years fighting for it), it's really hard to communicate that we're all equal and all have a say here within a draft–review structure that implicitly elevates the opinions of reviewers over others. – Joe (talk) 07:31, 27 September 2024 (UTC)[reply]
I've pulled the most recent 10 articles moved to mainspace with the AFCH script. They are:
That's an average of 372.5 words and 12.6 refs. The median article has 338 words and 4 refs. Compared to existing articles, 53% of our existing articles have fewer than 372.5 words, and 83% have fewer fewer than 12.6 refs. One in six articles has fewer words than the shortest in this list. One of three articles is shorter than the second-shortest in this list.
I think it is clear from these numbers that AFC is expecting more refs than existing community practice, and that they are trying to accept only articles that are already as long as ones that editors have been working on in the mainspace for years.
BTW, during the same span of time, more than 100 pages were deleted from the Draft: namespace. You shouldn't assume this means that more than 90% of drafts get deleted, because deletions are bursty and this is a relatively small sample size, but that's about what I expected. WhatamIdoing (talk) 20:56, 27 September 2024 (UTC)[reply]
  • A Conclusion: I am sadly not surprised at the current state of this discussion. Some of the heated off-topic arguments verge on NOTHERE behavior. I am very disappointed to see this from experienced editors. To those of you who simply commented on the proposal: I appreciate you a lot.
Since the default NPP draft template was changed to Template:Draft article a day before this discussion began, I think my proposal is moot. I don't see how we could improve that template much, but I may raise some minor wording changes on the Template Talk. If someone wants to close this discussion, that's fine; if others wish to continue discussing other things here, I wish you the all best. Toadspike [Talk] 21:16, 27 September 2024 (UTC)[reply]
Worth also talking about the usertalk notification MTD leaves, which only provides one option: submit for review. Agree in principle we shouldn't trick people into thinking draftification/AfC is mandatory for a typical article creator. — Rhododendrites talk \\ 13:29, 28 September 2024 (UTC)[reply]
  • Strong Oppose All it will do is destroy the draft system as it stands and eventualy destroy Wikipedia. This almost happened between 2008 and 2012, before the draft process was available, when Wikipedia was flooded with paid/coi editors and there was no effective system to deal with them. Do folk not understand what draftification is. Every publisher has draft process. It is NOT a route to deletion. That is what the detractors of the system say, many of them who are paid to oppose it and destroy it. It is the one of the core safeguards we have against the complete destruction of Wikipedia. scope_creepTalk 11:46, 29 September 2024 (UTC)[reply]
    That comment is almost entirely evidence free assumptions of bad faith. Please try engaging with the discussion rather than just knee-jerking oppose to changing the status quo because it would change the status quo. Thryduulf (talk) 12:56, 29 September 2024 (UTC)[reply]
    Its not evidence free and I resent the fact that you have said my comment bad faith. Why would I make the comment if I didn't know what I was talking about. I've worked in NPP/AFC since it was created and was involved in some of the early discussions. I now how exactly how UPE/paid editors behave. It would lead to an exodus of editors after the place gets flooded with adverts. It would be free-for-all. The reality is that the editor who posted hasn't thought it through and hasn't looked in the archives to see what the situation was like then. scope_creepTalk 16:05, 29 September 2024 (UTC)[reply]
    "Trust me, I was there" is not evidence. Your comment assumes bad faith from those disagreeing with you, and of everybody submitting new articles. Not every editor is paid (and disclosed paid editing is explicitly allowed), not every paid edit (disclosed or otherwise) is bad, not every paid editor (disclosed or otherwise) is attempting to harm the encyclopaedia, not every paid edit (even undisclosed ones) does harm the encyclopaedia. Thryduulf (talk) 16:19, 29 September 2024 (UTC)[reply]
    That is true to certain extent, but the majority of editors who create modern biographical, organisational and product articles which make up the majority are undeclared paid editors. They do not have our best interests at heart and never have done. scope_creepTalk 16:53, 29 September 2024 (UTC)[reply]
    Even if that is true (and you haven't provided any evidence, of either your assertion or the implications of it that these articles harm Wikipedia and/or that draftification as currently implemented and practice prevents that harm), that doesn't mean that draftification as implemented currently can't be improved and that any changes to the status quo will mean the death of Wikipedia. Thryduulf (talk) 17:02, 29 September 2024 (UTC)[reply]
    @Scope creep, what percentage of articles in the draft space do you think get deleted? WhatamIdoing (talk) 18:51, 29 September 2024 (UTC)[reply]
    If drafts get deleted, that's because their creators have abandoned them. That's what G13 is. Perhaps more effort should be spent encouraging article writers to improve their articles after they got moved to draft (where they can be improved without interference), but draftification is not deliberate, malicious backdoor deletion, and I resent it being characterized as such. Cremastra (talk) 19:47, 29 September 2024 (UTC)[reply]
    Is this a Double-barreled question? The comment you're replying to said only "route to deletion", and you've turned it into four separate parts:
    • deliberate
    • malicious
    • backdoor
    • deletion.
    I wouldn't personally characterize any of them as malicious, but I think a fraction of them are deliberate. IMO claiming that nobody ever sent a borderline subject to AFC instead of AFD (which has lower standards in practice) would be rather extraordinary. I frankly don't think we're all so stupid that we can't figure out which route is most likely to end up with the result we prefer.
    If we characterize AFD as the "front door" for deletion, then it seems fair to describe letting articles expire in the Draft: space as the "back door".
    But the original comment is merely that it's not a route to deletion. But if 90–95% all of the articles put on that path actually do end up getting deleted, then is it not basically fair to say that it is one of our routes to deletion? WhatamIdoing (talk) 20:22, 29 September 2024 (UTC)[reply]
  • Oppose. The current verbiage of the tag makes it clear to anyone with a lick of common sense, that the article has potential, but in its current form it is not ready for mainspace. Some of the comments here from folks clearly indicate a lack of understanding of what the draftification process is for. If an article, in its current form, passes GNG, then there are only certain circumstances where it should be draftified (e.g. paid editing), but if an article probably would pass GNG, but does not in its current form (e.g. there are not enough in-depth sources from independent, reliable sources to meet the standard), than that is a poster child for draftification. When I was more active in reviewing articles, I created several custom responses, which took the standard message and massaged it a bit depending on the reason for draftification (e.g. UPE, lack of GNG) or a specific topic (e.g. NFOOTY, Populated places). In some instances those messages contained an offer to ping me directly when they felt the article was ready for mainspace. I am all for article creation, but I also care about the quality and reputation of Wikipedia, which is often seen as the punchline for jokes regarding garbage information on the internet. And I would completely disagree with those who say that draftification is not a net benefit. In fact, I think it is one of the most useful tools to helping improve the quality on WP. Is it always used correctly? No. But that's an education problem with individual users, not an overriding issue with the process itself.Onel5969 TT me 14:34, 29 September 2024 (UTC)[reply]
    I agree with Onel5969. (But also remember to not leave !votes as this is the idea lab, not a formal proposal). Cremastra (talk) 14:36, 29 September 2024 (UTC)[reply]
    Apologies, Cremastra. Onel5969 TT me 19:38, 29 September 2024 (UTC)[reply]
    That might be fine in theory, but it doesn't match the what is happening in practice. Especially given that articles are being moved to draftspace for not being of sufficient quality that are C or even B class. If an article is neutrally written and meets the GNG then there is no justification for moving it to draftspace just because someone might (or might not) have been paid to edit it. Thryduulf (talk) 15:21, 29 September 2024 (UTC)[reply]
    @Thryduulf: Do you have a specific example in mind when you mention C or B class articles? scope_creepTalk 16:13, 29 September 2024 (UTC)[reply]
    See @WhatamIdoing's comment in this discussion. Thryduulf (talk) 16:15, 29 September 2024 (UTC)[reply]
    This list is the state of articles when they come out of the Draft: space. For articles going in to the Draft: space, here's a current list:
    I have skipped redirects, some round-robin page swaps, and a couple of editors moving AFC submissions from User: space to the Draft: space, and tried to include only articles being moved from the mainspace to the Draft: space. I can't get the ORES ratings for these articles, but at a glance, I think that Start and C-class is not an unreasonable description. WhatamIdoing (talk) 19:31, 29 September 2024 (UTC)[reply]
    First, thanks for providing the list. The issue is, in reviewing those drafts, most are solid drafts, and not " Especially given that articles are being moved to draftspace for not being of sufficient quality that are C or even B class." Although I think a more careful explanation could have been made. For example, the first one would have been better with a "more in-depth references from independent, reliable sources" needed, rather than simply saying "more sources needed", as there isn't a single, in-depth reference from an independent, reliable source in the draft. The second and third examples are the exact same issue. The 4th and 5th examples are properly labeled as covert advertising (both editors have been blocked for it - in addition, the 4th one didn't have a single in-depth reference from an independent source, either). The 6th example, while having 3 sources, none are in-depth, and while it might be a spelling difference on the translations of the 2nd and 3rd refs, it does not appear that the article's subject is mentioned in any of them. The 7th article is not a true example of draftification, as it was moved by the author. The 8th and 9th article have zero independent reliable sources (for the 9th, the newspaper referenced does not have a page number, and the link does not appear to bring up anything in depth about the hack lab). Not sure about the 10th, for the history is a bit wacky, but again, does not look like an example of draftification.
I think this illustrates some of the misunderstanding that folks who don't like draftification make. You look at the list provided, and you go, wow, lots of references, most not stubs or micro-stubs, why in the hell were they draftified? Hell, I did that myself, wondering if all 10 were done by a single editor, who perhaps did not have a firm grasp of draftification. But then you dive into the merits of the sourcing, or the upe issues, and it appears all 8 of the draftifications appear justified.Onel5969 TT me 20:32, 29 September 2024 (UTC)[reply]
@Onel5969, I wonder if you could explain "the newspaper" in the 9th article a little better. You say that the article has "zero independent reliable sources", but traditional print newspapers are independent reliable sources. Then you say it doesn't have a page number, but the link takes you directly to a scanned copy of the correct page; the cited article [title given in the citation] is in the last two columns. None of that makes the newspaper less independent. Is your concern that the article appears to predate the use of the name in the article title ("De Zanbak" means "The Sandbox")? WhatamIdoing (talk) 20:51, 29 September 2024 (UTC)[reply]
Could be the translation, but there does not appear to be anything connecting the group mentioned in that article, with De Zanbak. But even if there is, agf, that still is the only in-depth independent source. Onel5969 TT me 01:15, 30 September 2024 (UTC)[reply]
I'm glad we agree that a newspaper is an independent source. WhatamIdoing (talk) 01:20, 30 September 2024 (UTC)[reply]
If a new editor includes 5 sources in their submission and it gets moved to [somewhere I didn't put it] because "more sources needed" or "no sources" how many of them are going to take the time to learn that the experienced editor actually meant none of these sources contain what I think is significant, in-depth coverage in independent reliable sources and then have the confidence to say "actually, this experienced person with the power to remove my article from Wikipedia is wrong and I'm right, I'll learn how to challenge them and how and where to express my view in a way that the powerful people will listen to me" rather than just give up at some point along that path? And before anyone says it, no, just because a few bad faith editors might be among the dissuaded does not justify the loss of good faith editors. Thryduulf (talk) 21:29, 29 September 2024 (UTC)[reply]
I guess that's the difference between editors who care about quality on WP, and those who care about quantity. But that's why I said that the rationale given could have been better. Onel5969 TT me 01:17, 30 September 2024 (UTC)[reply]
Is it really a quality vs quantity question?
Or is this the difference between editors who would rather see a page run through Wikipedia:Articles for deletion or Wikipedia:Proposed article mergers instead of being unilaterally hidden until it gets deleted without the level of community oversight that we expect from AFD? For example, I'm not convinced that "De Zanbak" is a viable subject for an article, but I think there are several ways that we could address that concern, and I don't see the Draft: space helping. In fact, the only thing that moving that page to the Draft: space does that's different from moving that page to the User: space is: It's far more likely to get deleted during the next year if it's in Draft: space than if it's in User: space. WhatamIdoing (talk) 01:26, 30 September 2024 (UTC)[reply]
Well, since draftification isn't a "backdoor to deletion", nor is it "hiding an article", it's definitely a question of quality vs. quantity. Draftification, in short, is a quality control measure. These are articles that might be notable enough for mainspace, but simply aren't in good enough shape to be there. But, like other vehicles in WP, good faith editors might disagree on an article's notability, so for example in the De Zandbak articlem, Jay8g (who tagged it for notability), and Jonathan Deamer (who draftified it) might deem it potentially notable, while you, WhatamIdoing, might have simply sent it to AfD, because you do not feel it notable. But that doesn't mean the system isn't working. Perhaps we can tweak the current verbiage in the template to include where resources about where an editor can reach out for help might be added (e.g. AFC or Teahouse)?Onel5969 TT me 09:20, 30 September 2024 (UTC)[reply]
Well, since draftification isn't a "backdoor to deletion", nor is it "hiding an article", you say that as if there is no possible way good faith editors could disagree, but that simply isn't true. Whether either of those things is true is a matter of opinion (and, in my opinion, one that is consistent with the evidence presented). Thryduulf (talk) 10:07, 30 September 2024 (UTC)[reply]
Hi. No, editors can certainly have different interpretations and disagree on issues. However, in this instance, it is not a matter of disagreement. In order to hold those views indicates a lack of understanding of what the draftification process is. That's not what draftification is, it is, as I've said, simply a quality control measure. It would be like saying, it's a matter of opinion whether or not this person wrote an article about themselves, that can be interpreted as not being COI editing. Of if a an article simply cut and paste the info from Encyclopedia Brittanica, you cannot say it's your opinion that that isn't a copyvio. I mean, I have the utmost respect for you, Thryduulf, and you do a great job on WP. There are things on WP which are subjective (e.g. exactly what constitutes SIGCOV), while others are objective, (e.g. UPE/COI editing, copyvio). What draftification is falls into the latter category. All that being said, we can disagree on whether or not an individual article should or should not have been draftified. You say the evidence presented shows that it was not warranted that those articles be sent to draft. Going through the sources, however, it looks like draftification was justified. That is a difference of opinion. Onel5969 TT me 14:20, 30 September 2024 (UTC)[reply]
It's your opinion that moving an article to the Draft: space is simply a quality control measure.
It's my opinion that moving an article to the Draft: space is also simply a quality control measure that, compared to the available alternatives of leaving it in the mainspace, sending it to AFD, or moving it to User: space, substantially decreases the likelihood of the quality being improved and substantially increases the likelihood of the article being deleted.
Oh, right: Those last two points ("substantially decreases the likelihood of the quality being improved" and "substantially increases the likelihood of the article being deleted") aren't "opinions". They're objective facts. WhatamIdoing (talk) 22:17, 30 September 2024 (UTC)[reply]
Rhodesia Railways 19th class is not a list; it's a train that was in operation for multiple ranges of time. Even if it were a list, the empty headings and only content being a table is nowhere near start-class, maybe even substub. Aaron Liu (talk) 20:47, 29 September 2024 (UTC)[reply]
The existing content in the article is an infobox and a table. Tables are the format preferred by Wikipedia:Featured lists. Empty sections aren't banned, and ratings are based on what is already there. I'd rate it as |class=List today. WhatamIdoing (talk) 20:53, 29 September 2024 (UTC)[reply]
only content being a table have you actually read the page? That infobox is full of content, there are two apparently reliable sources and the table itself has about 20 rows of content. Thryduulf (talk) 21:33, 29 September 2024 (UTC)[reply]
Sorry, yes the infobox as well. I still wouldn't call it a start, though. Aaron Liu (talk) 22:03, 29 September 2024 (UTC)[reply]

Can we consider EC level pending changes?

[edit]

This is just an idea, and I want to workshop this a bit more, but I think it would be helpful to have pending changes at the extended confirmed level. This could be called "PC2" again (not to be confused with the original PC2) or "PCECP". The idea would be to help enforce WP:ARBECR and similar restrictions where non-extended confirmed users are prohibited from certain topic areas. Under this level, edits by non-extended-confirmed editors would be held for review, while extended confirmed users can approve these edits and thus take responsibility under WP:PROXYING.

I think it would be helpful for pages where (1) parts of the article intersect with a contentious topic, or (2) the article in its entirety intersects with a contentious topic, but not edited frequently. Awesome Aasim 16:54, 27 September 2024 (UTC)[reply]

This seems like it could be useful. It would have to be restricted to infrequently edited pages (likely excluding all current events articles) so as not to overwhelm Pending Changes every time Reuters publishes a new story or an edit war erupts. The big question is: what problem are you trying to solve? Toadspike [Talk] 20:39, 27 September 2024 (UTC)[reply]
There are some contentious topics designated either by ArbCom or the community where only extended confirmed users are allowed to participate. However, admins refuse to protect pages where there isn't enough disruption to justify protection. Although, it should be considered that the XCON restriction applies regardless of whether a page is protected or not.
What PCECP would do is essentially remove fears that there "isn't enough disruption to justify protection" while buffering all non-extended-confirmed contributions so they have to be approved, in line with "non-extended-confirmed can only make edit requests". Templates that are specifically for this case like {{edit protected}} break when the page is not protected. Awesome Aasim 22:00, 27 September 2024 (UTC)[reply]
The problem with that is that the 500/30 rule is specifically designed to keep newer editors out due to extreme amounts of disruption as a rule. There's a good reason why both of the world's main hot wars (the Arab-Israeli conflict and the Russo-Ukrainian war) are under 500/30. And, as has been brought up repeatedly and bears repeating again, high volumes of edits on a given article contraindicate CRASHlock.
But the biggest stumbling block here is that no consensus exists yet for an extended-confirmed CRASHlock. The last discussion about expanding CRASHlock to higher protection levels predates XCP entirely. There would need to be a formal RfC for this, not VP spitballing. —Jéské Couriano v^_^v threads critiques 15:37, 28 September 2024 (UTC)[reply]
XCON protection makes sense for high traffic articles, but low traffic articles? If the edit is minor such as fixing spelling mistakes or grammatical errors, there should be no problem. Fixing spelling and grammar is generally outside of contentious topic areas anyway. From WP:ARBECR: On any page where the restriction is not enforced through extended confirmed protection, this restriction may be enforced by other methods, including ... the use of pending changes.
I probably would set up abuse filters as well to see if a page is in a category that primarily deals with a contentious topic, and then warn and tag the edit in question. Awesome Aasim 16:22, 28 September 2024 (UTC)[reply]
Most low-traffic CT articles don't have any protection since they never saw amounts of vandalism necessitating protection. Protection requests that solely rely on arb enforcement and little to no evidence of vandalism get declined. Aaron Liu (talk) 23:26, 28 September 2024 (UTC)[reply]
Yeah I see that, but the problem is that a non-XCON edit will get approved on pages that not many people are watching. Pending changes still allows non-XCON users to make these edits, but their edits will need to be approved and they can be reverted if in violation of WP:ARBECR. This is also in line with how pending changes is used on low-traffic articles to monitor (not prevent) disruption. Awesome Aasim 18:26, 29 September 2024 (UTC)[reply]
@Aaron Liu Most low-traffic CT articles don't have any protection since they never saw amounts of vandalism necessitating protection. Protection requests that solely rely on arb enforcement and little to no evidence of vandalism get declined. Untrue, articles in ECR topics can and are pre-emptively locked. What actually happens is that articles with minimal disruption are usually not brought to WP:RFPP or noticed by a wayward admin. Mach61 19:53, 29 September 2024 (UTC)[reply]

Untrue, articles in ECR topics can and are pre-emptively locked.

Could you add an example? There is a long list of declined RFPP requests for arbitration enforcement. Aaron Liu (talk) 20:42, 29 September 2024 (UTC)[reply]
See this exchange between an admin who refused to protect based on ECR due to a lack of disruption and a (former) admin who explained to them otherwise. Mach61 19:46, 1 October 2024 (UTC)[reply]
Thanks, I get the "can" now. Aaron Liu (talk) 20:59, 1 October 2024 (UTC)[reply]
Seems reasonable. I've always wondered why pending changes isn't deployed more often. It seems a useful tool, and there are lots of pending changes reviewers so very little backlog Cremastra (talk) 14:18, 28 September 2024 (UTC)[reply]
Because there are enough people who dislike or distrust pending changes that it's hard to get a consensus to use it. See, for example, Wikipedia:Village pump (proposals)/Archive 183#RFC: Pending-changes protection of Today's featured article. Anomie⚔ 14:41, 28 September 2024 (UTC)[reply]
Well, gee, I fucking wonder why? —Jéské Couriano v^_^v threads critiques 15:39, 28 September 2024 (UTC)[reply]
Would you care to elaborate on your point? I'm not seeing it. Anomie⚔ 17:04, 28 September 2024 (UTC)[reply]
@Anomie: Read the "Proposal" section on the linked page. The fact that RfC even exists should give you a clue as to why CRASHlock is so mistrusted by a significant minority of editors. —Jéské Couriano v^_^v threads critiques 18:01, 9 October 2024 (UTC)[reply]
Still not seeing it. People supposedly mistrust it because there was a trial 14 years ago and enwiki admins didn't immediately stop using it after the trial period pending a consensus on the future of the feature? Anomie⚔ 18:43, 9 October 2024 (UTC)[reply]
You familiar with the idiom of the Camel's nose? —Jéské Couriano v^_^v threads critiques 18:47, 9 October 2024 (UTC)[reply]
The TL;DR I'm taking away from this discussion is that you're still butthurt over consensus not going your way 12 or 13 years ago, and assuming that anyone opposed to PC shares that reason and no other. I think it's unlikely continuing this conversation is going to go anywhere useful. Anomie⚔ 18:59, 9 October 2024 (UTC)[reply]
That isn't how consensus works, either. Consensus can be determined by an RfC, yes. But it can also develop just by the way that things are done already, regardless of whether it has formally discussed.
I think about the example given by Technology Connections about "the danger of but sometimes". The LED traffic light is superior in energy savings and much more, but sometimes snow and ice builds up on them, so they are bad. Likewise, XCON pending changes will help with enforcement of WP:ARBECR but sometimes admins might apply this to pages out of policy, so it shouldn't be used again. The correct response would be to place in policy guardrails so that admins don't do that. Awesome Aasim 19:00, 9 October 2024 (UTC)[reply]
How is an RfC from over 13 years ago still reflective of consensus today? I am pretty certain that while some opinions might not have changed, others definitely will have. No one is saying there should be full pending changes. Awesome Aasim 18:16, 9 October 2024 (UTC)[reply]
@Awesome Aasim: The RfC was linked specifically to point out one of the reasons for the mistrust in the PC system. The most recent RfC on CRASHlock, as I said, predates XCP as a concept. —Jéské Couriano v^_^v threads critiques 18:20, 9 October 2024 (UTC)[reply]
Also, please explain what you mean by "crashlock". I cannot find any discussion or glossary entry on "crashlock". Awesome Aasim 18:21, 9 October 2024 (UTC)[reply]
@Awesome Aasim: It should be VERY obvious from context. —Jéské Couriano v^_^v threads critiques 18:26, 9 October 2024 (UTC)[reply]
I guess you might be the only one using this terminology; as it is not in WP:GLOSSARY or anywhere else.
Nonetheless, this is the Idea Lab; it is the place to develop ideas, not to show stark opposition to ideas. That is what the other discussion boards are for; consensus polling. It should be noted that WP:ECP was created originally for the purpose of enforcing arbitration decisions and community sanctions. It was never intended for anything else; it just got used for other stuff de facto. Awesome Aasim 18:40, 9 October 2024 (UTC)[reply]
(edit conflict) All these things you think are obvious really are not. You should try explaining yourself better instead of emphatically waving your hands at something random. Anomie⚔ 18:43, 9 October 2024 (UTC)[reply]
Obvious perhaps, but it still doesn't make much sense. I'm not sure how using your own special terms of unclear implications to disparage things you dislike is helping communication or community understanding here. Cremastra (talk) 19:37, 9 October 2024 (UTC)[reply]
I don't understand. People mistrust PC because of a bureaucratic misimplementation of an experiment over 10 years ago? (In a noncentralized bureaucracy where dumb shit happens all the time?) The RfC is explicit that it makes no normative judgement on PC, and it seems the !voters are not doing so either. SamuelRiv (talk) 18:37, 9 October 2024 (UTC)[reply]
It's one reason, and probably the biggest for some (who viewed the trial's mishandling as trying to force CRASHlock/FlaggedRevisions down our throats). Another reason is that, from 2010 to 2014, CRASHlock RfCs were called at least once a year, with most of them being written by pro-CRASHlock editors. —Jéské Couriano v^_^v threads critiques 18:42, 9 October 2024 (UTC)[reply]
Ok for those not into WP politics, there's an overview opinion piece from the August 2011 WSP that seems to capture the attitude and aftermath. It appears the closure results of the RfCs left admins in an indeterminate state as to whether PC can ever be applied or removed. SamuelRiv (talk) 18:47, 9 October 2024 (UTC)[reply]
as to whether PC can ever be applied or removed True in 2011 when that was written, but later RFCs resolved that. Anomie⚔ 19:02, 9 October 2024 (UTC)[reply]
Could you link to said RfCs? All else that's linked previously regards the main page. SamuelRiv (talk) 19:56, 9 October 2024 (UTC)[reply]
Wikipedia:Pending changes/Request for Comment 2012 established basic consensus to use PC, with Wikipedia:PC2012/RfC 2 and Wikipedia:PC2012/RfC 3 clearing up some details. PC level 2, on the other hand, never got consensus for use and eventually in 2017 there was consensus to remove it from the configuration. Template:Pending changes discussions has a lot of links. Anomie⚔ 22:14, 9 October 2024 (UTC)[reply]
It's worth noting that the 2017 RfC is the last one about any aspect of CRASHlock, to my knowledge. As I said above, there would need to be a new RfC in order to get consensus for extended-confirmed CRASHlock, as PC2 was originally full-protection level and no ECP!CRASHlock question was asked in the 2016 RfCs, none of which were particularly comprehensive. (The last comprehensive RfC was the 2014 clusterfuck.) —Jéské Couriano v^_^v threads critiques 06:47, 10 October 2024 (UTC)[reply]
I think the main reasons editors don't want to expand the use of pending changes are practical: no technical support for fixes (or additional feature development) is on the horizon, in spite of documented bugs; and uncertainty in the community's ability to manage expanded use. There are certainly vocal editors who are wary due to past history, but this has already been a factor in other decisions, and they have accordingly been influenced to be more definitive about how any trials will proceed. isaacl (talk) 18:55, 9 October 2024 (UTC)[reply]
Ok so there's a lot of history here as you are already seeing above, and no one's even gotten to discussing Phillipe's little misadventure yet. Despite all that I actually think the general idea here is sound. And since we are discussing history its worth pointing out that as a practical matter this is actually closer to what the EC restriction was intended to do in its earliest incarnation where it functioned as a softer version of 1RR originally enforced as a bespoke AE remedy on one specific article reverts of non-qualifying accounts did not count towards 1RR.
Times have changed, ECR now tends to be enforced in mainspace with ECP and is applied far more broadly than anyone from then would have envisioned, for better and for worse.
The best use case here is for quiet pages where the history of non-EC editing is largely one of minor non-contentious fixes and improvements, but have caught attention due to sporadic contentious edits, where it can offer a middle way between leaving enforcement to post-edit reverts and preventing all non-EC editing.
As a practical matter the limitations of the extension mean that it really only works-well on low-traffic pages and realistically improvements to the extension aren't coming anytime soon. So use case (2) makes sense, but (1) is a harder sell. Might not be enough of a use case to justify the hassle. Personally I'd have to do some research and think about this a little but the basic idea is sound.
Apologies for the hastily typed response, I'm a little pressed for time; hopefully there was something useful in there. 184.152.68.190 (talk) 16:06, 22 October 2024 (UTC)[reply]

Maybe what is needed is this...

[edit]

A multi-part RfC asking how ECR should be enforced for existing pages, including based on activity. High traffic pages will need extended protection retroactively as those tend to get the most disruption from ECR violations. Low-traffic pages, not so much, but we can use abuse filters and workshop ECP pending changes for this. Spelling and grammar fixes as far as I am aware are excluded from WP:ARBECR. Awesome Aasim 19:52, 1 October 2024 (UTC)[reply]

I view the ECR in the PIA area to be absolute (no editing full stop by those who do not meet 500/30), so CRASHlock would be off the table there in any event. I'm not sure if this also applies to WP:GS/RUSUKR (which falls into the EE area). —Jéské Couriano v^_^v threads critiques 18:57, 9 October 2024 (UTC)[reply]

Can we build the proposal here?

[edit]

Here is some starter text maybe to get the ball rolling:

  • What is the best way to enforce WP:ARBECR on articles?
    • Option 1: Preemptive XCON protection
    • Option 2: Preemptive XCON pending changes
    • Option 3: Edit filters
    • anything else?

This probably is incomplete, anyone else have ideas for this proposal? Awesome Aasim 19:41, 16 October 2024 (UTC)[reply]

I'd say remove "preemptive", as it is sometimes placed only in response to disruptive activity from non-ECs. Aaron Liu (talk) 11:31, 17 October 2024 (UTC)[reply]
So should reactive also be an option? Awesome Aasim 17:32, 17 October 2024 (UTC)[reply]
I think so. That's what I support. Cremastra — talk — c 19:29, 17 October 2024 (UTC)[reply]
So we should have it like this?:
  • What is the best way to enforce WP:ARBECR on articles? Please rate whether these options should be preemptive, reactive, or not used.
    • Option 1: XCON protection
    • Option 2: XCON pending changes
    • Option 3: Edit filters/Revert filters
    • anything else?
Awesome Aasim 19:39, 17 October 2024 (UTC)[reply]
sure. Cremastra — talk — c 19:42, 17 October 2024 (UTC)[reply]
Sounds good - but bear in mind we are discussing CRASHlock (which would require developer buy-in to make XC happen) and an Arbitration policy (which ArbCom may short-circuit). Also note that there would likely need to be a separate RfC consensus to allow XC CRASHlock in the first place; like I said above we haven't had a comprehensive discussion about it since 2014. —Jéské Couriano v^_^v threads critiques 16:26, 26 October 2024 (UTC)[reply]
@Jéské Couriano, I do wish you would quit using that made-up word. WP:PC is shorter to type, and when editors use the same words for the same thing, then we're less likely to end up with avoidable confusion ("CRASHlock sounds really bad, but I'm just asking for WP:PC"). WhatamIdoing (talk) 00:26, 27 October 2024 (UTC)[reply]
My point still stands - a new RfC, developer buy-in, and ArbCom not interdicting the RfC would be required for this to become a reality. —Jéské Couriano v^_^v threads critiques 17:34, 27 October 2024 (UTC)[reply]
No, we're discussing "pending changes protection". Crashlock is a type of cardboard box. --Ahecht (TALK
PAGE) 21:18, 28 October 2024 (UTC)[reply]
WP:ARBECR can first just be XCON PC. After extensive edits by non-EC, piling on to PC backlog, then it can just be upgraded to normal XCON. If the disruption is already severe before being brought to RFPP or other venue, then XCON protection can just be the first action. ~/Bunnypranav:<ping> 13:05, 28 October 2024 (UTC)[reply]
Read what I wrote above in re an RfC. EC!CRASHlock does not exist, and would need a consensus to use it and the devs being willing to work on it for it to be a thing. Spitballing anything about this is a waste of time until that happens, especially as the current consensus is that (1) anything beyond standard CRASHlock is deprecated and (2) ECP renders EC!CRASHlock pointless. —Jéské Couriano v^_^v threads critiques 17:17, 28 October 2024 (UTC)[reply]
Please, stop calling it "CRASHLOCK" it's confusing and pointless. At least explain why pending changes = crashing. Cremastra (u — c) 19:59, 28 October 2024 (UTC)[reply]
@Jéské Couriano the discussions that you linked are from 2016, so we cannot assume the consensus has not changed. Also, I believe that this is a platform for building ideas and new proposals, hoping to bring them to reality while abiding by consensus. ~/Bunnypranav:<ping> 15:28, 30 October 2024 (UTC)[reply]

On another thought I am actually wondering if we can just have a two-part RfC as to whether to turn on this feature I discuss. Part 1 would just be about PCECP and part 2 would be just about replacing ECP with PCECP on low-traffic WP:ARBECR and related articles. Awesome Aasim 16:41, 30 October 2024 (UTC)[reply]

That makes sense, but the second RfC might fail, as it one would have to discuss page wise about the change in protection. Also proving that PCECP is enough for said pages will be complicated, and also have to think about the storming of backlog in PC if it is not enough. ~/Bunnypranav:<ping> 16:45, 30 October 2024 (UTC)[reply]

Wikipedia Main Page Proposal

[edit]
Moved from WP:VPT

I think that the Wikipedia main page would be more educative and with a section riddles, proverbs, idioms, wise saying. You know, a collection from many languages around, their origins, past meanings, reforms, present meanings, examples of their usage in history (past & present), their literal meanings, word for word rendering in english, etc. I don't know, who has better ideas? Let Wikipedia be a fun place too for visitors and readers to always learn more. I'm looking forward to seeing this by the start of next year and in other language wikis. Any and all contributions are accepted. elias_fdafs (talk) 20:02, 13 October 2024 (UTC)[reply]

@Elías Fortaleza de la Fuerza Sánchez: I moved your idea to the idea lab here, it was not a technical issue. — xaosflux Talk 20:09, 13 October 2024 (UTC)[reply]
While this does sound more like a Wiktionary or Wikiquote thing, I feel like there might be fruitful discussion to be had about showcasing featured content from sister projects in the general case. Folly Mox (talk) 20:32, 13 October 2024 (UTC)[reply]
Oh dear, another Main Page redesign suggestion. Good luck with that. --Redrose64 🌹 (talk) 20:51, 13 October 2024 (UTC)[reply]
The thing is, one person's "wise saying" is another person's "deepity". I don't think having these on the Main Page, especially in a dedicated section, would actually be very encyclopedic. However, like Folly Mox says, a more general concept of showcasing sister project content (a word etymology, a quote, etc.) could be interesting! Chaotic Enby (talk · contribs) 21:03, 13 October 2024 (UTC)[reply]
How about a small section with whatever the sister project featured thingy is? It could cycle daily. Cremastra (talk) 22:57, 13 October 2024 (UTC)[reply]
That could very well work! Chaotic Enby (talk · contribs) 17:22, 14 October 2024 (UTC)[reply]
The tricky thing is actually transcluding something from another project, which I don't think is possible without mw:Scary transclusion. Cremastra (talk) 17:25, 14 October 2024 (UTC)[reply]
I assume you mean without scary transclusion? jlwoodwa (talk) 18:54, 14 October 2024 (UTC)[reply]
Fixed. Thanks, Cremastra (talk) 18:58, 14 October 2024 (UTC)[reply]
The problem with idioms and proverbs is that, usually, they are regional. They are widely used at some area, but hardly mentioned or even unknown in others. For each user that see such a section and says "oh, that's the origin of that proverb" we'll have several who will say "what, was that a proverb? Never heard about it". Besides, explaining their background is just impossible with the limited text in main page boxes. Perhaps DYK may be a better venue to show those articles in the main page. Cambalachero (talk) 13:18, 15 October 2024 (UTC)[reply]
Articles on idioms would be helpful, especially if they mentioned pitfalls when translating between languages. However, I don't believe that the main page is an appropriate venue. -- Shmuel (Seymour J.) Metz Username:Chatul (talk) 13:58, 15 October 2024 (UTC)[reply]
As I discussed at Wikipedia:Village pump (proposals)/Archive 213 § Proposal: Create quizzes on Wikipedia, I suggest finding people interested in creating that type of content, creating a project page, and producing the content regularly on whatever schedule you can manage. From that experience, you can try to figure out how to make the process sustainable. isaacl (talk) 15:59, 15 October 2024 (UTC)[reply]
I think that it could be put in Portal:Current events, on the side under the "2024 at Wikipedia's sister projects" box. There's plenty of room, and a "____ of the Day" could be fun. WhatamIdoing (talk) 00:03, 17 October 2024 (UTC)[reply]
The main page is already overcrowded. Tinynanorobots (talk) 11:21, 29 October 2024 (UTC)[reply]
I agree with that 41.114.177.180 (talk) 11:14, 31 October 2024 (UTC)[reply]

Consensus Required Restriction and NPOV tags

[edit]

I know that editors should seek to remain unbiased, but it seems on divisive topics we can end up with one side who manages to tilt the article toward their POV. We can then end up with half of the editors saying "This article is perfectly fine" and the other half of the editors saying "There are big POV issues, here they are..."

The side who are happy with the bias can actively work to prevent any fixes to the page to address the bias, while simultaneously blocking the addition of a NPOV tag to the page.

It seems that if half of the editors are saying "it's fine" and the other half are saying "there are big issues" this is extremely indicative of a POV problem even if there is not consensus that one exists.

So I'm wondering if there should be an exemption to the Consensus Required Restriction and if some sort of critical mass short of consensus should be enough to allow for NPOV tag.

Thoughts? Bob drobbs (talk) 18:48, 22 October 2024 (UTC)[reply]

Putting the {{POV}} should never be an end goal. The goal should be to fix the problem, and adding the banner frequently provides no practical benefit at all. Imagine a wildly non-neutral article about an article under the Wikipedia:Consensus required restriction. Maybe it's an article called 2+2. The article says that 2+2 is generally understood to equal four, but there is a significant minority of respectable mathematicians says that 2+2=5. Here's the story you seem to want:
  • Alice adds a {{POV}} tag.
  • Eve removes it because she disagrees.
  • The discussion on the talk page about the tag ends in a stalemate. Because of the 'consensus required' rules, the tag would normally not be added, but because of the newly carved-out exception, the tag can be added.
  • End result: The article is tagged, but it's still wildly unbalanced.
Here's the story we need:
  • Alice adds a {{POV}} tag.
  • Eve removes it because she disagrees.
  • The discussion on the talk page about the tag ends in a stalemate. Because of the 'consensus required' rules, the tag is not added.
  • Alice decides to quit worrying about the tag and start worrying about the content of the article. The regulars on the talk page can't reach a satisfactory agreement, so she takes the dispute to a relevant noticeboard or starts an RFC.
Remember: Maintenance tags are not badges of shame. They do not exist to 'warn the reader' or to formally express your disagreement with the article. They exist in a (mostly vain) hope that editors will fix the article's content. If you can fix the article's content without a tag, then everyone wins. If you can't fix an article (tagged or otherwise), then read up on Wikipedia:Dispute resolution. WhatamIdoing (talk) 19:05, 22 October 2024 (UTC)[reply]
Depends… how many are on each “side” of the debate?
If there are multiple editors on each “side”, then I don’t think we can say that a consensus actually exists (in either direction). However, if it’s just one or two disgruntled editors against many, then we can say there is consensus, and that consensus does not require unanimity. Blueboar (talk) 19:08, 22 October 2024 (UTC)[reply]

Describing Notability in plain English

[edit]

The name we use for Wikipedia:Notability has long been a source of confusion. People can guess the basic concept of many policies and guidelines from the plain-English meaning of the title (e.g., Wikipedia:Reliable sources are sources you rely on; Wikipedia:Copyright violations is about violations of copyright etc.), but this one has quite a different meaning. You can have several sources that directly say ____ is a notable musician, and we'll reply that he's not WP:Notable.

I'd like to brainstorm some alternative phrases that could be used instead of "notability", or as a supplement to it, that would be less confusing to people unfamiliar with our internal jargon.

Background

[edit]

From Wikipedia:Glossary:

NN, non-notable
Abbreviation found in comments at Wikipedia:Articles for deletion and in edit summaries, indicating that the article's subject is not notable enough for a Wikipedia entry. A subject is non-notable if editors agree not to have an article about this subject. Their decision is usually based on things like not finding enough reliable sources to write a decent encyclopedia article, but it can also be based on things like a desire to present a small subject as part of a larger one.
Notability, Notable
A characteristic held by article subjects that qualify for separate, stand-alone articles. A notable topic is one that "is suitable for a stand-alone article or list when it has received significant coverage in reliable sources that are independent of the subject." Note that "notability" is a property of a topic, and has nothing to do with the quality of an article, or whether an article exists for the topic.

From a recent discussion:

  • Words for the concept: criteria, concept, test, quality, qualities, requirements, notedness, guideline, threshold, when to create an article
  • Words for the result: separate article, stand-alone article, separate page, stand-alone topic, new topic, own page, article creation, article suitability, inclusion
  • Some specific ideas:
Collapsed list of prior ideas
The following discussion has been closed. Please do not modify it.
  • Article concept guideline
  • Article creation criteria
  • Article creation guideline
  • Article sourcing test
  • Article suitability criteria
  • Article test guideline
  • Article threshold
  • Criteria for article creation
  • Guide to which topics should be included as articles on Wikipedia
  • Guideline for when a topic should have its own article
  • Inclusion criteria
  • Is the subject written about in reliable sources?
  • New topic test
  • Notedness
  • Own page threshold test
  • Page sourcing guide
  • Primary notability criterion
  • Qualifying for a separate article
  • Separate article criteria
  • Source availability
  • Source depth
  • Stand-alone concept
  • Stand-alone article criteria
  • Stand-alone topic criteria
  • Stand-alone topic criterion #1 (#2, #3, etc.)
  • When to create an article

Feel free to expand the box if you want to see some of the prior ideas. It's collapsed because some research on brainstorming ideas suggests that looking at other people's ideas can reduce the total number of ideas shared. Duplicates are fine!

Your ideas (“notability”)

[edit]

Please share your ideas here. Even a 'bad' idea might inspire the next person to think of another option. WhatamIdoing (talk) 21:04, 22 October 2024 (UTC)[reply]

I had also been thinking about this. The core issue, in my opinion, is that we're trying to describe as "notability" something that is closer to "for someone/something to have an article, they should be well-documented in reliable sources". At its core, the term "notability" carries more of a connotation of relative importance, leading to a lot of newcomers, and sometimes even other users, being misled as to what makes a topic notable. On the other hand, the actual guidelines describing it focus on the existence of reliable sources about the topic, with importance only being used by some guidelines as a proxy for these sources being likely to exist.
A word like well-sourced or well-documented would carry this idea better, without the a priori of "importance/fame is what matters" that "notability" carries. Chaotic Enby (talk · contribs) 21:13, 22 October 2024 (UTC)[reply]
Lots of topics are documented by primarily primary sources (eg like many news event), but we require coverage by secondary sources, so those would worsen the situation. — Masem (t) 21:20, 22 October 2024 (UTC)[reply]
Good point, although it could still be a first start, and no word can fully convey our notability guidelines either. Maybe encyclopedically sourced could help convey the fact that not any source works? Or, as you employ the term "coverage", we could make the difference between (primary) documentation and (secondary) coverage and call it well-covered? Chaotic Enby (talk · contribs) 21:27, 22 October 2024 (UTC)[reply]
Chaotic Enby: I am still chewing over all this. I fear that encyclopedically sourced could be easily misunderstood and potentially lead to more newbies trying to cite Wikipedia itself. I really don't have a sense of how well people outside Wikipedia and academia understand the distinctions between primary, secondary, and tertiary sources. I think well-covered does capture the essence of what we're trying to convey without causing more confusion. — ClaudineChionh (she/her · talk · contribs · email) 23:42, 22 October 2024 (UTC)[reply]
I'd say that people outside the wiki-verse and academia understand primary/secondary/tertiary "not at all", and I'd say that people in the wiki-verse understand the distinction "poorly". Editors struggle with WP:PRIMARYNEWS, especially when it comes to the question of notability ("But event is obviously important, so obviously this breaking news article is secondary"), and most of them could not explain why Wikipedia:Secondary does not mean independent. WhatamIdoing (talk) 00:17, 23 October 2024 (UTC)[reply]
Masem, the GNG requires secondary sources, but NPROF does not. Both are still wiki-notable. We therefore need a handle for this concept that does not assume the GNG approach. WhatamIdoing (talk) 00:13, 23 October 2024 (UTC)[reply]
I like “When to create an article”. SmokeyJoe (talk) 21:22, 22 October 2024 (UTC)[reply]
I caution against this because as it is used now, notability is not used as a check at new page review, and primarily is a method used for evaluating whether to delete an article at AFD. We should have an advice page with that title about how to make sure you have a good topic and reviewing the notability of the topic is a good starting point as part of it. — Masem (t) 21:35, 22 October 2024 (UTC)[reply]
So "When to have an article"? WhatamIdoing (talk) 00:18, 23 October 2024 (UTC)[reply]
“When to have a separate article”?
A nod to WP:Structurism as an existing concept. Also a hint that newcomers should add content to existing article, and no be trying to add a new orphan topic as their first contribution.
- SmokeyJoe (talk) 02:12, 23 October 2024 (UTC)[reply]
  • I'm inclined to something like "stand-alone topic criteria" (to clarify that the point is determining whether a topic warrants a stand-alone article) or, in a similar vein, "when to create an article" (or possibly "when it can be appropriate to create an article", since in occasional cases it can be appropriate to cover a small number of closely related topics that could be notable in the same article rather than separately). I do agree with the notion that notability isn't the best name for this guideline and that having a term that's more like plain English. Hydrangeans (she/her | talk | edits) 21:26, 22 October 2024 (UTC)[reply]
  • I like "stand-alone article criteria" as it is focused on when to create an article. --Enos733 (talk) 21:28, 22 October 2024 (UTC)[reply]
  • Maybe something like suitable topics or suitable article topics would work. That implies the existence of editorial judgement and that some topics simply aren't suitable. User:Chaotic Enby, this was inspired by your idea of "well-sourced", which has the potential to be confused with well-cited (i.e., the number of refs in the article right now, rather than the number of sources in the real world). WhatamIdoing (talk) 00:21, 23 October 2024 (UTC)[reply]
    From all the suggestions so far, this seems the most understandable so far. It's short, it communicates that some things are excluded and that there is 'judgement' involved. —TheDJ (talk • contribs) 09:46, 23 October 2024 (UTC)[reply]
    I really like this, because (1) it removes the emotional pain of being deemed "not notable", and (2) it avoids the confusion we currently have of subjects that are notable but about which we cannot have a meaningful article. To clarify: (1) AfD and Teahouse waste a lot of time trying to explain to upset people that Wikipedian notability has nothing to do with importance, creativity, or future value to humanity. We could save a lot of trouble by focusing on the objective need for sources rather than the subjective view of importance. (2) Notability is currently only half of the two tests we need to pass: We can't have an article unless the subject is notable and someone's written something about it for us to summarise. We have a lot of guidelines that say "XXX is generally considered notable", which result in unexpandable stubs because although it can be demonstrated from primary sources that two old ladies and a chicken once lived near a railway siding in Ohio (making it a genuine inhabited settlement), there is now nothing there, and no one has ever written anything about it, or ever will. Focusing on what is necessary to create an article would cut to what actually matters, practically, rather than getting tied up in legalistic debates about what constitutes a notable thing. Elemimele (talk) 16:14, 23 October 2024 (UTC)[reply]
    But all too often, we get the argument that we should have an article on XXX because sources exist, even though no one has demonstrated the existence of such sources. Attempts to add the requirement that reliable sources must be cited to create or keep an article have been repeatedly rejected. I would support replacing "notability" with something like "specific topics are suitable for articles if they are well-sourced, NPOV, and meet certain broad topic requirements (i.e., replacements for SNGs)". Donald Albury 17:32, 23 October 2024 (UTC)[reply]
    @Donald Albury, do you mean that topics are suitable/notable if they're neutral, or do you mean that articles are suitable/notable if they're neutral? I'm not sure if you mean that you want to repeal WP:NRVE and expand the deletion policy to say that a (deserved) {{POV}} tag is grounds for deletion, or if you mean that citing sources in a neutrally written article must be possible, even if it hasn't happened yet (including for many years). WhatamIdoing (talk) 17:44, 23 October 2024 (UTC)[reply]
    I was just trying to express that availability of reliable sources is required, but not sufficient, and that other policies and guidelines also must be met for an article to be suitable for inclusion in WP. Donald Albury 18:30, 23 October 2024 (UTC)[reply]
    I do like suitable much better than notable (and came here to suggest it). It's more accurate, but still gives some flexibility in definition, where something like well documented might be open to misinterpretation / lawyering. Folly Mox (talk) 17:50, 23 October 2024 (UTC)[reply]
    Suitable / Suitability is the first suggest I like, it helps show that this is a Wikipedia stand not a general idea. -- LCU ActivelyDisinterested «@» °∆t° 20:23, 23 October 2024 (UTC)[reply]
    Thanks a lot! I do very much like suitable topics (suitability?) too, as it is broad and flexible enough to cover our various policies on the topic. Chaotic Enby (talk · contribs) 19:26, 23 October 2024 (UTC)[reply]
    @Seraphimblade also deserves credit for this idea, since a comment from him is the source of "article suitability" in the list above.
    I'm leaning a bit towards "topics" (or "subjects"?), because "articles" could be argued to exclude lists, and because of the endless problem of "it's not notable because the article's quality is currently too low". WhatamIdoing (talk) 02:13, 24 October 2024 (UTC)[reply]
    I like that a lot. On Wikipedia, a suitable topic for an article is one where either sufficient reliable, independent sources can be found or which meets the criteria outlined in a subject-specific suitability guideline (SSG)... – sounds both more understandable and closer to how we actually decide whether or not to keep articles, in practice. – Joe (talk) 08:02, 25 October 2024 (UTC)[reply]
  • Just to throw out an idea that I think can minimize disruption, is to consider a comparable situation to the relatively recent rename of of the old Naming Convention page to WP:Article Titles while specific advice of naming for various fields are still at "Naming Convention". In that same vein, if the GNG was moved to its own page (thus sitting alongside the sepearate SNG pages) and what's left at WP:N left there, then renaming that leftover to some of the suggestions above would still allow us to keep the principle of notability via the GNG and SNG while having a better landing page at a more familiar term and to explain the GNG and SNG functions within that. It would minimize a mass edit on p&g pages. The GNG and SNGs can be described as tests used on Wikipedia to measure how notable (real world definition) a topic is within the suitability on an encyclopedia. Masem (t) 18:11, 23 October 2024 (UTC)[reply]
    There might be some advantages to splitting the GNG out onto its own page, but I think that might need to be a separate discussion. WhatamIdoing (talk) 18:36, 23 October 2024 (UTC)[reply]
    Well, in terms of providing g a word that is closer to the real definition for our practice related to when a topic is suitable for it's own article, treating the existing idea of notability through the GNG and SNGs as is and focusing on a clear word for the broad concept is a clean solution. Masem (t) 19:39, 23 October 2024 (UTC)[reply]
    The issue is that GNG is about how well-documented the topic is in independent secondary sources, which doesn't necessarily map to real-world notability, and using the latter word for it has been just as much source of confusion. Chaotic Enby (talk · contribs) 19:45, 23 October 2024 (UTC)[reply]
    We can frame the GNG and SNGs as semi objective, source based tests to evaluate real-world notability, and establih in the top level guideline that one reason to allow a topic to have an article is via demonstrating real world notability using the GNG and SNGs tests. That moves us away from having notability take the wiki definition. We still need a clear understandable title for the top level guideline, and that would also discuss more that the GNG and SNGs, such as the current NLIST advice. — Masem (t) 16:55, 24 October 2024 (UTC)[reply]
    The issue is, basing article suitability on real-world notability is a very iffy definition. GNG (and to a lesser extent the SNGs) provide us with a better foundation for defining what is suitable for our encyclopedia, which is quality of independent secondary sourcing. "This person is important" is ultimately a less relevant criterion than "this person has enough secondary sources to write an article about them", if our goal is to write an encyclopedia (tertiary source, i.e. relying on secondary sourcing). Chaotic Enby (talk · contribs) 17:02, 24 October 2024 (UTC)[reply]
    Consider that several of the SNG do give measure of real world notability based on claims of importance which can be given by a single reliable primary source, the expectation they can be expanded. The key is that with a tiny bit of rewording of the GNG and SNGs are set as the evaluation of real world notability with the expectation of sourcing and coverage required for an encyclopedia, either which establishes one way a topic is suitable for a stand alone article. Masem (t) 17:35, 24 October 2024 (UTC)[reply]

The reality is that wp:notability is the operative word for "allowed to have a separate article" and the talisman for the fuzzy ecosystem/process which decides that. It incorporates with wp:notability guidelines, degree of compliance with WP:not (a measure of the degree of enclyclopedicness of the article) and a bit of influences from real world notability/importance. Any term needs to acknowledge this. If one tries to base it on summarizing just what the wp:notability guidelines say, IMO it won't work. Sincerely, North8000 (talk) 02:00, 24 October 2024 (UTC)[reply]

So WP:What topics are allowed to have a separate article? WhatamIdoing (talk) 02:10, 24 October 2024 (UTC)[reply]
Yes. And the strongest consideration in it would be wp:notability per the notability guidelines, but the above other factors described above are also a part of that consideration. North8000 (talk) 15:31, 24 October 2024 (UTC)[reply]


I prefer to see a more obvious name for the guideline for article creation. Something such as like "Guideline for article creation" would be more obvious. TFD (talk) 16:21, 24 October 2024 (UTC)[reply]

Agree. My point was agreeing with the structure/content. If we want this to have legs, we'll need something with an even shorter with a good acronym for it. North8000 (talk) 17:08, 24 October 2024 (UTC)[reply]
My concern about WP:Guideline for article creation is that I would expect the advice on a page with that name to overlap considerably with Help:Your first article. There's more to article creation than identifying whether this is a suitable/acceptable/appropriate/notable topic for an article. WhatamIdoing (talk) 17:17, 24 October 2024 (UTC)[reply]
  • Procedural request I don't mean to gum up the process. But there's a risk of having 100 different ideas from 99 different editors, which can make it difficult to reach a consensus. Whenever this brainstorming step is over, I want to recommend compiling them into a list, sorted by some type of subcategory. That way we can slowly funnel our way towards something that can earn a consensus. I believe you'd probably find (at least) three or four types of names:
  • Non-descriptive (compare WP:NOT or WP:SIZE): inclusion criteria, inclusion test, article creation threshold, etc.
  • Type of outcome (compare WP:DISAMBIG or WP:STANDALONELIST): separate article, stand-alone article, separate page
  • Standard of sources (compare WP:RELIABLE or WP:VERIFIABLE): independent sources, third party sources
  • Standard of coverage (compare WP:OR or WP:COPYRIGHT): significant coverage, minimum coverage, coverage threshold
I lean towards something more descriptive, because "inclusion criteria" just shifts the complaints from "Wikipedia has an arbitrary definition of notability!" to "Wikipedia has an arbitrary list of inclusion criteria!" Newcomers and outsiders notoriously don't read passed the headline, or even twist ambiguity in bad faith to attack Wikipedia with misinformation campaigns. It would help the project much more if the guideline title summarized an uncontroversial standard for our encyclopedia. (Currently: if no reliable, independent sources can be found on a topic, then it should not have a separate article. or A topic is presumed to be suitable for a stand-alone article or list when it has received significant coverage in reliable sources that are independent of the subject.) Shooterwalker (talk) 17:24, 24 October 2024 (UTC)[reply]
I agree that "inclusion criteria" could shift the complaints from "Wikipedia has an arbitrary definition of notability!" to "Wikipedia has an arbitrary list of inclusion criteria!" However, the current name has an additional problem, namely "I have three Wikipedia:Reliable sources that WP:Directly support a claim that this subject is 'notable', so why are you claiming that it's non-notable?" That problem would go away with a name like "inclusion criteria". WhatamIdoing (talk) 19:57, 24 October 2024 (UTC)[reply]
We do have arbitrary criteria, though. All the WP:SNGs are arbitrary. The WP:GNG is arbitrary in what it considers "significant", "reliable", and "independent". Individual decisions on articles are arbitrary in how these guidelines are interpreted and how strictly they are applied. It's better to be open about that than pretend, like too many 'notability theorists' do, that we've come up with a 350 word rubric that objectively divides all of human knowledge into worthy and unworthy. I think most people can understand that to make a large project like this manageable, you have to agree on some boundaries – and respect them, even if they don't agree with them. – Joe (talk) 08:18, 25 October 2024 (UTC)[reply]
Except we do also have rubrics, and we also have to work together, so we have found it necessary to define together. There's boundaries, you say? What are they? We have to go about answering that question together. -- Alanscottwalker (talk) 11:20, 25 October 2024 (UTC)[reply]
Yes, that's what I'm saying. WP:GNG and the WP:SNGs are the boundaries we've arrived upon. They aren't objective, they're arbitrary and subjective, but that's okay. – Joe (talk) 11:31, 25 October 2024 (UTC)[reply]
Perhaps it would be more precise to say that there is an element of arbitrariness and subjectivity to decisions, especially for borderline subjects. WhatamIdoing (talk) 16:35, 25 October 2024 (UTC)[reply]
But, they are not just arbitrary. They describe real world things (sources) and using them for coming to decision (measure), and even more importantly, the rationale for doing so (writing based on what reliable others do). Arbitrary would be no definition, no rubric at all among us. We may suck, but we don't usually just rely on throwing darts or dice to delete articles. Alanscottwalker (talk) 18:39, 25 October 2024 (UTC)[reply]
Do they really describe real-world sources? Consider "The person has had a substantial impact outside academia in their academic capacity." The basis for deciding this is: Wikipedia editors say so.
Or "The person's academic work has made a significant impact in the area of higher education, affecting a substantial number of academic institutions." I tried adding a requirement for Wikipedia:Independent sources to that, and it got reverted 75 minutes later. WhatamIdoing (talk) 19:21, 25 October 2024 (UTC)[reply]
Yes, they do, those impacts are sourced, somehow -- you actually do have to prove it to each other. (Besides, you already know, this "independence" is a both matter of degree, and not strictly necessary to be in the definition for all real world sources -- and as a matter of various qualities a real world source might have, we are generally more concerned with trustworthy). Alanscottwalker (talk) 20:56, 25 October 2024 (UTC)[reply]
I've been told that the usual way of qualifying under the second one ("significant impact") is to write a book that is used in (undergraduate?) classes at multiple universities. But some classes, and some universities, appear to be more equal than others for this determination, which is arbitrary, using the definition as a decision made according to individual personal preference rather than by its intrinsic qualities.
I agree with you that supporters of these two criteria use sources whose independence can often be most politely described as a "matter of degree", and they appear to agree with you that independent sources are "not strictly necessary". (For example, I have seen sources accepted by other editors that were just a few links to class syllabi, saying that the text for the class would be Big Textbook by Alice Expert. In GNG terms, these are mere passing mentions in self-published sources, and would not be accepted for any other subject at all.) WhatamIdoing (talk) 21:36, 25 October 2024 (UTC)[reply]
I strongly disagree with the statement that the WP:GNG is arbitrary. (Or even the additional requirements of the WP:SNGs.) At worst, the application of WP:N requires some level of judgment, based on a consensus of editors applying the principle. But the evidentiary standard for writing an article is based on real, practical, and empirical experience. And it helps our project when the world understands that we write articles based on evidence. Shooterwalker (talk) 01:41, 29 October 2024 (UTC)[reply]
It's not completely random, but it is arbitrary, in the sense that nobody on the face of the earth except for English Wikipedia editors uses this definition of "notable". For example, I think virtually all people would agree that a YouTube celebrity with twenty million fans was "a famous or important person" -- it is only Wikipedians who have a secret alternate definition where it means "has had three newspaper articles written about them". jp×g🗯️ 12:11, 29 October 2024 (UTC)[reply]
That's a different point, and the real point of this brainstorm. Asking for sources isn't an arbitrary standard, but in hindsight, the word "notability" is an odd choice of words to describe it. Shooterwalker (talk) 22:04, 29 October 2024 (UTC)[reply]
  • Frankly, I think that it is an obvious error that we incorrectly refer to our guideline as "notability", and that we call things that meet this guideline "notable". It is not arbitrary -- there are rules -- but they aren't about notability. No normal speaker of the English language, when they say "notability", means what that guideline says.
If I'm going to be totally honest, it feels like -- whether designed intentionally or not -- the guideline's name is designed to make sure that newbies give invalid arguments during deletion debates, thus ensuring that their autobiographies/advertisements/etc are deleted and they are dismissed, because they stupidly assume that the word means the thing it means in 99.999% of its usage in the English language. For example, the obvious direct interpretation of "Smith is not notable" is:
  • The speaker's subjective opinion, which you can argue against by saying "Yes he is".
  • A claim that he is not very famous, which you can argue against by saying X million people listen to his podcast
  • A claim that he is not very successful, which you can argue against by saying he made X million dollars or has Y thousand clients or employs Z hundred people.
  • A claim that he is not very unique, which you can argue against by saying that he's the first X to ever Y, or the only Z who's ever Qd while Zing.
We do not accept any of these arguments. If you make any of these arguments, we sneer and ridicule you for being an idiot.
I would propose that the "notability" guideline be called something that does not, in any way, create "two-tier" sentences (e.g. ones where there's an obvious plain English interpretation, and then a second Wikipedian English interpretation where it means something else). For this reason I think stuff like "impactfulness topic criteria" might be helpful, but would not fully solve the issue, as people still know what the word "impactful" means, and would argue that things were impactful, when what we actually meant was impactful, and only a moron would think that meant impactful. It should be something that nobody would ever think to define in terms other than looking up the Wikipedia policy for it. For example: "includability" or "florfbap". jp×g🗯️ 12:07, 29 October 2024 (UTC)[reply]
Maybe "sourceability"? It brings the idea of having quality sources, while not being an already existing word, to make it clear that it's a unique Wikipedia concept. Chaotic Enby (talk · contribs) 16:01, 29 October 2024 (UTC)[reply]
I was about to suggest this, one advantage is "sourcable" and "sourcability" having the same grammatical categories as "notable" and "notability", easing rewrites.--LaukkuTheGreit (Talk•Contribs) 10:39, 1 November 2024 (UTC)[reply]
How do you apply that to WP:NPROF, which doesn't really care about sources? WhatamIdoing (talk) 15:42, 1 November 2024 (UTC)[reply]
Honest answer, you deprecate NPROF. I don't know why this one guideline has been repeatedly giving exemptions to sourcing requirements in an encyclopedia that should rely on secondary sources. Chaotic Enby (talk · contribs) 15:53, 1 November 2024 (UTC)[reply]
Until that magical future appears, I think we need a name that encompasses SNG criteria that are not directly dependent on sourcing. WhatamIdoing (talk) 16:57, 1 November 2024 (UTC)[reply]
"Sourcability" is far too close in meaning to WP:Verifiability and implies a weaker aspect when in fact what notability currently is is more complex than just WP:V itself. (that's one reason why notability remains a guideline rather than a policy, because of how complex it is) Masem (t) 17:08, 1 November 2024 (UTC)[reply]
  • Binominal expression or complete sentence This is a great discussion and thank you to OP for starting it. I think all the suggestions presented so far are great, though, they each introduce some of the ambiguity that already exists with Notability. I guess my comment is that we seem to be caught up on coining an all-encapsulating single word that could replace Notability. Maybe this is a case where a binominal expression ("Nice and Plenty") or even a complete sentence would be more appropriate to communicate the complexity that WP:NOTABILITY houses? Chetsford (talk) 18:10, 1 November 2024 (UTC)[reply]

Timeline of significant figures

[edit]

While many people have made contributions to history (many more than could fit in one timeline), it's undoubtable that some people's influence far exceeds that of others. 

Therefore, I think we should have a timeline of the significant figures in history. 

I completely understand that determining how significant some people are is a difficult task. It's expected to take struggle and effort to make this work. However, people deserve to know who made the greatest contributions to the advancement of humanity.

Also, many scholars themselves have written about who they believe are to be the most significant people.

I have created a sketch of this idea at User:Wikieditor662/sandbox. It's far from perfect, but you get the main idea. The people are colored based on the era they were in. The most significant people make it to the overview and those who are not as important but still nonetheless significant (as well as people born earlier so the overview doesn't get clumped) go to the individual timelines (below the overview) along with those in the overview.

I would again like to reiterate that this is something that is going to take effort, dedication, and much debate, but if we do this, then I think it could be worth it. What do you all think?

Wikieditor662 (talk) 20:34, 23 October 2024 (UTC)[reply]

Kindly, I'm experiencing philosophical opposition to this project. History has been a team effort, and further elevation of the already elevated is not likely to improve genuine understanding of historical processes. The Great man theory correctly fell out of fashion early last century.
Having said that, I don't mean to dissuade you from undertaking a project you're clearly interested in, and this seems like it could serve as some kind of subpage of WikiProject Vital Articles. Using the inclusion criterion "listed at WP:VA" is probably the only way you'd ever develop any kind of agreement as to which historical figures to include. That WikiProject has already done a lot of debating over which topics are more important than others.
The periodisation scheme is pretty parochial and Eurocentric, and would have to be converted to numeric year spans or whatever schema WP:VA uses (and the section headings would have to be delinked per MOS:NOSECTIONLINKS). You'll also want to consider how to handle cases where vital dates are approximate, unknown, disputed, etc. Folly Mox (talk) 00:12, 24 October 2024 (UTC)[reply]
I would tend to agree with Folly Mox on this. I'll add that it might be pretty much impossible to find an actual inclusion criteria, that is, any kind of consensus in reliable sources as to who is a significant enough figure – or even if we can compare the significance of historical figures across times, cultures, and domains. If anything, that page will inform more about our own selection than about any historical truth behind it.
However, having it as part of WP:VA, rather than as an encyclopedic article, could make it a pretty useful reference for articles about famous figures needing improvement, without claiming that these are necessarily the most significant ever. Chaotic Enby (talk · contribs) 01:07, 24 October 2024 (UTC)[reply]
Hey @Folly Mox@Chaotic Enby I posted to Wikipedia talk:WikiProject Vital Articles and a week later there's still no response... Is there anything else I could do?
Thanks,
Wikieditor662 (talk) 20:25, 1 November 2024 (UTC)[reply]
That sounds like a giant pile of WP:OR – Joe (talk) 12:26, 24 October 2024 (UTC)[reply]

Auto-amending bare URL tags

[edit]

Is there any reason we aren't or can't scrape and extract basic cite template information (webpage title, domain, visited datetime) at submit-time from bare URL <ref>s? Personally, I use bare URLs all the time as I consider filling out the cite template the most emphatically tedious part of editing WP (as it is when writing scholarly manuscripts) and know that some robot editor will just come along and fix it for me anyway. Since the code already exists and could be done more efficiently server-side, why don't we just pull it into the WP core? Just a small and probably extant idea I had while feeling a little guilty for adding a bare <ref> to a nicely-formatted article with proper tag attributes and template use. Cheers, fellows. Elliott-AtomicInfinity (talk) 01:38, 24 October 2024 (UTC)[reply]

This is what mw:Edit check is getting to AFAIK. Aaron Liu (talk) 02:18, 24 October 2024 (UTC)[reply]
@Trizek (WMF) will know if they're going beyond "prompt to add a ref" to "try to format the ref". WhatamIdoing (talk) 20:03, 24 October 2024 (UTC)[reply]
Not quite what you are looking for, but there is reFill for bare URLs, and Wikipedia:Citation expander for when the URL is within <ref> ... /ref>. You can save your edit, and then immediately run those tools. As always, the output of any such tool must be reviewed and verified. Donald Albury 14:32, 24 October 2024 (UTC)[reply]
You might be looking for this.
Or use the visual editor, or use the ref filler in the 2010 wikitext editor's toolbar. Or maybe even embrace the idea that everyone contributes in different ways, and that WP:CITE means what it says about doing your best to accurately communicate what your source is, and that editors can, do, and should work together on the formatting. WhatamIdoing (talk) 20:01, 24 October 2024 (UTC)[reply]
It took me far to long to realise you can auto-fill citations from the toolbar, I fear I'm not the only one as it's not well advertised. -- LCU ActivelyDisinterested «@» °∆t° 20:12, 24 October 2024 (UTC)[reply]
Nice, but it doesn't always work. It is particularly annoying when I'm trying to cite something that I have accessed through the Wikilibrary (with a long list of authors) and it doesn't work, and I am unable to go to the non-Wikilibrary page for the article. Donald Albury 20:26, 24 October 2024 (UTC)[reply]
It is indeed unfortunate that many websites do not properly mark up their pages so that the automated tools and Zotero etc are unable to extract the appropriate information from webpages. But that is a problem that we cannot really solve. —TheDJ (talk • contribs) 20:48, 24 October 2024 (UTC)[reply]
Recently (1-2 months back?) I saw a project to improve the automated tools (or maybe just one tool), iirc by adding local code for specific commonly cited websites it consistently gets wrong. Unfortunately I can't find the discussion now, but if someone remembers it (user:WhatamIdoing?) you may be interested. Thryduulf (talk) 22:48, 24 October 2024 (UTC)[reply]
Thryduulf, are you thinking of Wikipedia:Village pump (proposals)/Archive 213 § Deploying Edit Check on this wiki (August 2024)? Folly Mox (talk) 23:35, 24 October 2024 (UTC)[reply]
No, this was about better (more complete, more correct) automated filling of source metadata (author, publisher, title, etc) when a reference is added. Thryduulf (talk) 00:01, 25 October 2024 (UTC)[reply]
m:Web2cit? * Pppery * it has begun... 00:41, 25 October 2024 (UTC)[reply]
I think that was the tool, but I'm sure the discussion was on en rather than meta (the canonical capitalisation btw is Web2Cit). Thryduulf (talk) 01:25, 25 October 2024 (UTC)[reply]
I really need to be better at checking my links. * Pppery * it has begun... 03:09, 25 October 2024 (UTC)[reply]
The other main enwiki tool that formats citations is User:Citation bot. * Pppery * it has begun... 03:09, 25 October 2024 (UTC)[reply]
What about Wikipedia talk:Citing sources § citation generator? (September 2024)? Folly Mox (talk) 11:51, 25 October 2024 (UTC)[reply]
Oh right, and the "Edit Check" thread I guessed first had a tangential subthread about better metadata, including adding a local translation layer to Citoid as invoked from the Visual Editor interface, but no one gave the subthread a heading for me to link. I think it starts around here. Folly Mox (talk) 11:57, 25 October 2024 (UTC)[reply]
It wasn't the citing sources discussion. Might have been the subthread but I'm not certain. Thryduulf (talk) 12:24, 25 October 2024 (UTC)[reply]
Or they do mark them up, but they block our servers. That's probably happening with The New York Times. Properly formatted refs are in their interest, too, but it's likely that all they see is some automated thing or another and automatically block it. WhatamIdoing (talk) 23:41, 24 October 2024 (UTC)[reply]
Server side automation would have the same issues, and I'd rather editors checked what the automated tools outputted as they sometimes produce nonsense. -- LCU ActivelyDisinterested «@» °∆t° 20:50, 24 October 2024 (UTC)[reply]
@Donald Albury, I've had some success with using a DOI in such cases, assuming it has one. WhatamIdoing (talk) 23:42, 24 October 2024 (UTC)[reply]
I think I've also had the problem using DOI. It looks like WikiLibrary sets cookies on my device (when I go back to a source a day or two after I looked it up with WL, WL immediately jumps in. I saw this happening even when I was logged in with my alternate account, which is not eligible for WL.), so any attempt to reach a link outside of WL gets diverted back to WL. Donald Albury 18:15, 25 October 2024 (UTC)[reply]

WP:BITE rewrite 2

[edit]

Previous discussions

How do you feel about this updated rewrite? Ca talk to me! 14:27, 25 October 2024 (UTC)[reply]

@Ca, without looking at your rewrite, I often feel like baby steps are the best way to get changes made. WhatamIdoing (talk) 16:37, 25 October 2024 (UTC)[reply]

Determining who should be an electionadmin

[edit]

Following Wikipedia:Village pump (proposals) § Enabling SecurePoll elections with the electionadmin right (permalink), I am starting a discussion on who should actually get the electionadmin permission. (The permission is necessary for scrutineering the results.) I see a couple of potential options:

  1. Bundling the permission with CheckUser
  2. Creating a separate user group which simply contains the electionadmin permission, which is assignable...
    1. ...by the Arbitration Committee, or
    2. ...by community consensus at (either a new WP:Requests for election administrator or some existing page, such as WP:AN)

I would lean towards option 1, with option 2a as a second choice. The less bureaucracy the better, and CUs are trusted enough to use the permission responsibly. They have also already signed the NDA. If we are going to create a separate right, ArbCom is the body which is best equipped to assign (and importantly, monitor the use of) tools which give access to non-public information. Are there other options I am not thinking of? Reasons to pick a particular option? Other comments? HouseBlaster (talk • he/they) 02:47, 28 October 2024 (UTC)[reply]

Pinging participants at the VPR discussion: @ActivelyDisinterested, Bluerasberry, Bunnypranav, Chaotic Enby, EggRoll97, Isaacl, JSutherland (WMF), Just Step Sideways, Levivich, Novem Linguae, Pinguinn, Pppery, SD0001, Sdkb, Sohom Datta, Thryduulf, and Xaosflux. Thanks, HouseBlaster (talk • he/they) 02:47, 28 October 2024 (UTC)[reply]
Option 1. At least until T377531 is done, in which case I would give securepoll-edit-poll to admin (or maybe crat) while leaving securepoll-view-voter-pii only for checkusers. * Pppery * it has begun... 02:51, 28 October 2024 (UTC)[reply]
Option 1. If scruntinising for socks, then going with CUs group – robertsky (talk) 02:55, 28 October 2024 (UTC)[reply]
Option 2a with the right being given initially to any current CU or former CU in good standing who asks for it. That way it can be added/removed independently of the CU rights if there is any reason to do so, and allows for any changes in the future. Thryduulf (talk) 03:34, 28 October 2024 (UTC)[reply]
Given that ACE scrutineers are routinely granted local CU for the purpose of properly scrutinizing the election, I do not think an electionadmin without CU makes any sense. (I can see the argument for having CUs without electionadmin, however.) In other words, I do not think it should be added independently of the CU right, but removing it would be acceptable. HouseBlaster (talk • he/they) 03:40, 28 October 2024 (UTC)[reply]
I think the ability to assign/remove it independently of CU is more important than whether it ever is given to a non-CU or removed from someone without removing CU. Thryduulf (talk) 03:45, 28 October 2024 (UTC)[reply]
Option 2a and personally, I don't think it necessarily needs to be restricted to CheckUsers. As long as the appointment comes with a vote of ArbCom and has community consultation, it satisfies the WMF's criteria for access, assuming the recipient is identified as well. I see no reason to lock it behind the CheckUser right, though I do think ArbCom is the right choice for who should be assigning it. EggRoll97 (talk) 04:38, 28 October 2024 (UTC)[reply]
We should postpone considering this until phab:T377531 is resolved. Communication from WMF regarding SecurePoll related groups/rights has not been technically accurate. In particular I want to note the following points:
  • electionadmin group gives access to sensitive data as of today, but this is actually because of a bug. If/when the bug fix is merged (gerrit:1083337), no PII would be leaked – and the ability to setup and configure polls becomes quite low-risk and can be bundled into the sysop toolkit.
  • The user right which actually does expose PII, securepoll-view-voter-pii, is extremely sensitive! It allows viewing the IPs and UAs of all the voters in a single page. This is a much higher level of access than CheckUser which only allows viewing the data for a user individually, and the use of such access along with the given reason go into logs which are audited by ArbCom/Ombuds for compliance with local and global CheckUser policy. Compare that with securepoll-view-voter-pii which allows viewing PII en masse without any audit trail (phab:T356442).
– SD0001 (talk) 07:25, 28 October 2024 (UTC)[reply]
This idea starts with the presupposition that PII must be collected on these. That is something that can be discussed. Perhaps it doesn't need to be, especially if we are going to keep using manual whitelists for the electoral rolls. — xaosflux Talk 09:48, 28 October 2024 (UTC)[reply]
Per SD, I think that all admins should have electionadmin right, since scheduling elections seems like great mop work. However, I disagree that the right to view voter private information shouldn’t be given to all CheckUsers. I think that it should, since the users that have accessed the information are already logged (T271276), so there is an audit trail. CheckUsers are also the ones who know about socks, so they seem like a great fit.
Also, guys, this is the idea lab, not VPR. Don’t pile on! Aaron Liu (talk) 11:28, 28 October 2024 (UTC)[reply]
  • Unless we start doing an election a week we'll ever need more than a handful of election admins, so I'm not sure giving it to every admin is necessary. It sounds more like interfaceadmin (of which we have 10) or bureaucrat in that regard (15, and they aren't busy). – Joe (talk) 11:32, 28 October 2024 (UTC)[reply]
    We don't "need" it, but I see only benefits in having all admins able to do it. Aaron Liu (talk) 12:55, 28 October 2024 (UTC)[reply]
    What benefits would there be in having way (as in perhaps 100x) more people than needed? The drawbacks I can see immediately are: increased risk/attack surface (we generally follow the principle of least privilege for even the most minor rights); increased chance of misunderstandings arising from the lack of clarity over who's responsible for elections (look at what's happened already); increased chance of conflicts when too many people are trying to coordinate one election; increased expectations for new admins from adding yet another bundled responsibility. – Joe (talk) 18:01, 28 October 2024 (UTC)[reply]
    The arbitration committee election is run by volunteers who co-ordinate to avoid overlapping work. I'm confident that Wikipedia's collaborative community will continue in this tradition with administrator elections.
    Bundling privileges together is a tradeoff: sure, election admins could be a separate user group, with the overhead cost of the processes to add or remove members. That has to be weighed against the risk of someone setting up votes without community approval. I think I agree with SD0001 that it's not a high-risk scenario. There are much better ways for someone who obtained access to an admin's account to disrupt Wikipedia than trying to setup clandestine polls. isaacl (talk) 18:34, 28 October 2024 (UTC)[reply]
    That's what I'm basing my numbers off. The ArbCom election is run by three coordinators, three scrutineers, and a couple of people setting up the pre-RfC. So eight people, and none of them seem particularly run off their feet. We have over eight hundred admins.
    I imagine the potential for abuse would not be in setting up bogus elections but in manipulating or sabotaging real ones or (if CU ends up being included in this) doxxing voters en masse. Admin accounts are scarce and valuable enough commodity for it to be worth the effort for some people. But again, we apply the principle of least privilege to rollback and page mover. Why wouldn't we do it here? – Joe (talk) 19:54, 28 October 2024 (UTC)[reply]
    Regarding the arbitration committee election: anyone is eligible to co-ordinate the election RfC and the non-votewiki portion of the election itself. They don't all rush in and try to perform tasks without co-ordinating with each other.
    SD0001 suggested that the electionadmin right be bundled with the admin toolset since, after the bug is fixed, it does not require CheckUser privileges. I appreciate that, in your view, the risk is sufficiently high to warrant the overhead of managing the electionadmin right with a separate process.
    Regarding the page mover and rollback rights, they remain bundled with the sysop group, though. Since those rights are granted separately, if the principle of least privilege were followed, admins should have to apply for them separately rather than getting them bundled. I've previously stated my support for tailoring permissions with matching roles (see this comment thread on protection for Did You Know queues for example). But I recognize that there is an overhead cost, and there have to be willing volunteers to pay it. isaacl (talk) 22:09, 28 October 2024 (UTC)[reply]
Who will have access to the vote details? Unrelated to the other private details who voted, and how they voted should be encrypted and access extremely limited. If that's not the case these won't be 'secure' elections, and voters need to be very visibly warned that their votes aren't private -- LCU ActivelyDisinterested «@» °∆t° 12:51, 28 October 2024 (UTC)[reply]
The creation and setup can be done by 'crats as Joe mentioned. For the PII exposing rights, I do agree with SD's views, I also have another option, this right can be asked only by existing Check Users, and the ArbCom can grant it to the ones who have a respectable experience using CU tools. ~/Bunnypranav:<ping> 12:55, 28 October 2024 (UTC)[reply]
One thing to keep in mind, to see SP PII you have to be listed on the specific poll (and you have to be in the electionadmin group to be eligible to be listed on the specific poll). So if we decide to collect the enhanced PII in SP, then it is still limited to only the users registered to the specific poll. — xaosflux Talk 13:21, 28 October 2024 (UTC)[reply]
Regarding the attack vector for users with the electionadmin, a compromised account could add more scrutineers to the poll. Thus the risk would be that everyone in the group with the securepoll-view-voter-pii right could gain access. So for simplicity, I think we should be prepared to accept that everyone with the securepoll-view-voter-pii right might have access. If want to be able to move users in and out of this group on a per-poll basis, then there should be a separate user group for it. isaacl (talk) 18:45, 28 October 2024 (UTC)[reply]
Note: It is certainly possible we could have multiple, overlapping secure polls at the same time on different topics with different admins, etc. — xaosflux Talk 18:52, 28 October 2024 (UTC)[reply]
Sure. Everyone who has the securepoll-view-voter-pii right should be trusted for all polls currently in progress. isaacl (talk) 18:59, 28 October 2024 (UTC)[reply]
  • Community consensus, as we do for scrutineers. I really don't like the idea that arbcom would be involved in any way in the admin election process, and they don't need more workload anyway. Just Step Sideways from this world ..... today 17:24, 28 October 2024 (UTC)[reply]
    So one thing that needs to be considered is, first assuming we collect the PII in SP, is that if a scrutineer wants to be able to further investigate a voter using other on-wiki data, they will also need to be a local checkuser to be able to check those logs. So it needs to be established that those checks are appropriate, and additionally we currently give arbcom exclusive decision making authority on who may be a local checkuser. — xaosflux Talk 18:50, 28 October 2024 (UTC)[reply]
  • Echoing Xaosflux above, I believe electionadmin / securepoll-view-voter-pii does not grant every electionadmin the ability to see every voter's data ever. I think it just grants the ability to be added to a poll during setup. There is compartmentalization. So how this would work in practice if we gave the right to all the checkusers is that when we have an election, we'd probably want to pre-pick 3 checkusers to scrutineer the election, add them to the poll, then only those 3 would have access to the data.
    Right now the way I am asking WMF to set up SecurePoll for us is to let any admin create a poll, and then only that poll's designated electionadmins can edit a poll or scrutineer. phab:T378287.
    There's 3 pending patches related to phab:T377531 that may change some details of how SecurePoll permissions work. We may have some additional clarity after those patches are merged and have been in production for a few weeks. –Novem Linguae (talk) 19:08, 28 October 2024 (UTC)[reply]
    @Novem Linguae: Where is the consensus for giving all admins the ability to create a poll? It seems contrary to Levivich's close of Wikipedia:Village_pump_(proposals)#Enabling_SecurePoll_elections_with_the_electionadmin_right: An RFC to determine how the new right should be distributed can be launched at any time; it may be advisable to advertise that RFC on WP:CENT. – Joe (talk) 22:05, 28 October 2024 (UTC)[reply]
    It's the suggested setting in the extension documentation at mw:Extension:SecurePoll, and exposes no PII. However if folks object we can change the ticket. –Novem Linguae (talk) 22:29, 28 October 2024 (UTC)[reply]
    I think we need a discussion of who should have it. The RfC linked above gave this meta page as an explanation of what an 'electionadmin' is, and it says (perhaps contrary to the default in the documentation) that it's a right that allows users to set up elections with SecurePoll. – Joe (talk) 07:38, 29 October 2024 (UTC)[reply]
    Roger. Will move it to electionadmin for now. –Novem Linguae (talk) 08:45, 29 October 2024 (UTC)[reply]
  • I'm opposed to local CUs doing scrutineering. For electionadmin (excl PII), I don't see why we don't give it to the Electoral Commission only? They're elected to manage the ACE process. This is distinct to option 2 in my eyes; it would be assumed consensus upon election of an Electoral Commission (perhaps the crats could action the userrights changes). For AELECT, it's trickier but could be discussed in post-trial discussions. For PII scrutineering, I think we should continue using stewards for ACE; for AELECT it's up in the air (and subject to them willing to do it, and the frequency of admin elections being reasonable for them, I'd prefer stewards handling it). ProcrastinatingReader (talk) 22:11, 29 October 2024 (UTC)[reply]
    The stewards have already indicated that they are not willing to continue handling enwiki admin elections. Thryduulf (talk) 22:20, 29 October 2024 (UTC)[reply]
    Looks opposite to me? See: [1] and [2] - seems like their initial comment was misinterpreted? ProcrastinatingReader (talk) 22:21, 29 October 2024 (UTC)[reply]
    But is it really good to require relying on Stewards for local stuff? It just seems more logical to me that we make it all an on-wiki process. I just don't see why not local CU. Aaron Liu (talk) 22:22, 29 October 2024 (UTC)[reply]
    I think so, at least for scrutineering. Stewards are happy to deal with it AFAICT and it's been the way it's done historically. Aside from independence reasons, I'd be concerned with local CUs doing election scrutineering with PII because that would give local CUs a dual-purpose. Their purpose atm is tackling abuse, and they're restricted by the Wikipedia:CheckUser policy. In particular, they need cause, and their checks are logged. But scrutineers see all voters', which is a large portion of the active editor userbase, and their checks aren't logged. I find it hard to reconcile this in my head with the restrictions placed upon CUs in our local policy, which become meaningless to my mind if CUs can see most active editors' IPs come ACE/AELECT anyway. ProcrastinatingReader (talk) 22:29, 29 October 2024 (UTC)[reply]
    Not exactly sure what @Xaosflux meant above, but the task he mentioned only said that it was a bit too easy (as in friction, not permission) to access the PII, not that it's not logged; in fact, the task links to phab:T271276, which made access logged.
    Correct me if I'm wrong, but don't the list of users who can access PII have to be whitelisted by the electionadmin for every election? Aaron Liu (talk) 23:42, 29 October 2024 (UTC)[reply]
    Yes, to see securepoll data you have to be an explicitly listed admin for the specific poll you want to view; to be eligible to be listed you have to currently be in the electionadmin group. Viewing the securepoll data is logged in securepoll. It is also possible to configure a poll to not collect personal data at all, so just the public list of usernames would be available. — xaosflux Talk 23:53, 29 October 2024 (UTC)[reply]
    Oops, I pinged the wrong person, sorry. I meant @SD0001 lol Aaron Liu (talk) 01:30, 30 October 2024 (UTC)[reply]
    I didn't know about the feature mentioned in phab:T271276 and didn't see it in localhost, probably because of some missing setup. It does seem to be logged after all. Nevertheless, it just records that someone saw the full list – there's obviously no way of logging whose PII they happened to look at or take note of. That's more of what I meant. – SD0001 (talk) 22:19, 30 October 2024 (UTC)[reply]
    Since scrutinners need to be whitelisted, I don't really see a problem. Aaron Liu (talk) 23:23, 30 October 2024 (UTC)[reply]
    Maybe $wgSecurePollUseLogging = true; and then visiting Special:SecurePollLog will turn it on. –Novem Linguae (talk) 23:35, 30 October 2024 (UTC)[reply]
    A possible solution CUs having a lot of instant access, if a CU wants to become a PII scurtineer, they would have to apply to it, and a group of trusted users (crats/ArbCom/anyone else that the community deems trusted) can approve it. This perm can be granted/requested per election, and they would be added into the securepoll view PII whitelist. ~/Bunnypranav:<ping> 10:35, 30 October 2024 (UTC)[reply]
    In summary, you're proposing we ask bureaucrats to give people the electadmin right. Honestly, since we (probs. justifiably) don't appear to want SecurePoll to be frictionless, I think that's a good-enough idea. Aaron Liu (talk) 22:21, 29 October 2024 (UTC)[reply]
    The original purpose of the arbitration committee election commission was to be able to decide on questions that needed to be settled quickly to be effective, and thus a community RfC discussion wouldn't be feasible. Community expectations has shifted the role to include more management of community comments. Most of the election management continues to be done by other volunteers. Personally, I don't like continuing the trend of making the commission more central to the arbitration committee election process as I'd prefer that it remain a largely hands-off role. I like how the arbitration committee elections are run through a grassroots effort. isaacl (talk) 22:38, 29 October 2024 (UTC)[reply]
    How are election admins on votewiki currently decided? It looks like Cyberpower and Xaosflux have had electionadmin for various periods.[3][4] Is consensus needed, or do WMF just appoint people who express interest in helping manage the process? ProcrastinatingReader (talk) 22:46, 29 October 2024 (UTC)[reply]
    When an election is being configured on votewiki the coordinators have accounts made and are added to the group, then are added to the election, as are the scrutineers. In elections such as ACE, the coordinators are removed when voting begins so they can't access the PII that gets collected. — xaosflux Talk 23:55, 29 October 2024 (UTC)[reply]
    When there are non-technical coordinators, they may not get added as they wouldn't have anything to do - in which case the WMF resource generally does all the work. — xaosflux Talk 23:56, 29 October 2024 (UTC)[reply]
    Can something similar to this be continued, then? Coordinators are added to electionadmin, and either local crats or admins flip the bits each ACE? ProcrastinatingReader (talk) 07:10, 30 October 2024 (UTC)[reply]
  • I'm going to split a couple of ideas out in to subsections below. There are a few complicated things that need to be considered. Let's assume this isn't for ACE right now, but for any other use case we decide to use securepoll for. — Preceding unsigned comment added by Xaosflux (talk • contribs)
  • create new separate userright Setting up elections is a specialized, new, sensitive, very social process. Although elections require checkuser services and support, there is little overlap in the roles. I presume how this is going to work is that we have a noticeboard for requesting elections, a form to complete in that noticeboard, and then the electionadmin will use the tool which generates the election instance. When the election is complete, then I think the electionadmin should turn the results over to a checkuser for scrutiny. The major English Wikipedia election is Wikipedia:Arbitration Committee Elections December 2023/Coordination, but I think that whomever is in this role for English Wikipedia should be open and eager to collaborate across wikis with elections including Picture of the Year, WMF board elections, special elections like the Movement Charter, and Community Wishlist. All of these elections have had very serious social challenges which are beyond the role of technical functionary. It may not fall to the role of electionadmin to resolve all social issues, but the electionadmin certainly should not create election instances carelessly or without confirming that community support for an election is in place. The results of Wikimedia elections direct investments at least in the tens of millions of dollars. This election committee should consider the possibility of requesting a budget from the Wikimedia Foundation to communicate the elections, train election coordinators, discuss election policy and best practices across languages and wikiprojects, and try to establish some social and ethical norms that apply through Wikimedia projects. I would like for people to trust our elections and believe that Wikipedia is democratic. Activities like "promoting democracy" are not in the scope of checkuser duties. If we assign this userright to checkusers, then I think that will restrict elections to what checkusers currently do, rather than allow us to design elections to meet community needs. And yes of course - people with electionadmin rights should not get checkuser access to personal data. Bluerasberry (talk) 21:11, 1 November 2024 (UTC)[reply]
    While I have many words to say against your argument on electionadmins, this is a workshop, so at this point I think we should accept "create new electionadmin user group" and "add electionadmin to all admins" as separate options.

    If we assign this userright to checkusers, then I think that will restrict elections to what checkusers currently do, rather than allow us to design elections to meet community needs.

    What else would scrutineers need to do besides inspecting election PII and checkusering to ensure democracy? Aaron Liu (talk) 22:20, 1 November 2024 (UTC)[reply]
@Aaron Liu: Scrutineering and election administration are non-overlapping workflows. Part of scrutineering is checkusering. Another part of scrutineering could include confirming that someone is eligible to vote by non-standard, non-machine readable criteria, which Wikimedia elections often include. For example, elections over off-wiki processes often give voting rights to people who contribute to Wikipedia outside the Wikimedia platform, such as by processing Wikimedia Commons content for upload or similar. Bluerasberry (talk) 00:31, 2 November 2024 (UTC)[reply]
I'm fairly sure election administrators configure the list of eligible voters, not scrutineers. I have trust in administrators to conduct diplomacy and even more trust in a potential group of "specialized, sensitive, and very social" users. Aaron Liu (talk) 00:39, 2 November 2024 (UTC)[reply]
Scrutineering and election administration are non-overlapping workflows. I agee. I envision splitting electionadmin into a user right that adds and edits polls, and a user right that scrutineers polls. They are currently kind of combined. phab:T377531. –Novem Linguae (talk) 05:55, 2 November 2024 (UTC)[reply]
You lost me a bit in the second half of your post, because you switched to talking about global elections and WMF budgets. I think that would be unrelated to what we're talking about here, which is developing the ability for enwiki to host its own non-global elections, with the goal of 1) not depending on and using the resources of global partners such as stewards and WMF Trust & Safety, 2) developing the technical and social ability to hold many more elections than we do currently, and 3) increasing autonomy. Our use cases are things like WP:ACE and WP:AELECT. By the way, global elections are their own special beast, and are much more technically challenging than local elections (phab:T355594, wikitech:SecurePoll#How to run a board election), and basically require WMF Trust & Safety and WMF software engineer support no matter what, unlike local elections which will run completely self-sufficiently once we have a system in place. –Novem Linguae (talk) 05:53, 2 November 2024 (UTC)[reply]

Do we need PII in SP for local elections?

[edit]

So this is something that is going to be important as to who is going to be allowed to do what, and how they will be allowed to do that. Polls don't have to collect PII. If they don't, they will still collect usernames. PRO's are that if we don't collect PII in the vote action, then the bar of who can administer elections is much lower. The con is that checkuser data of the vote-action isn't collected. Keep in mind the username is still collected - and checkuser investigations of everything that person has done on-wiki can continue as per normal. This is very close to how it is in RFA now, if the only edit/action that wasn't checkuser recorded for someone was their "vote". — xaosflux Talk 14:26, 30 October 2024 (UTC)[reply]

That is actually is pretty good option. As there is a suffrage requirement, the chances of abuse are a lot lower. ~/Bunnypranav:<ping> 15:25, 30 October 2024 (UTC)[reply]
I like the idea of collecting the PII from the voting data, as it's a good way of excluding some socks and catching others. However that's not the really the purpose of having a poll, so I don't see why its collected. Maybe I'm missing something, is there some other reason to collect the data? -- LCU ActivelyDisinterested «@» °∆t° 15:33, 30 October 2024 (UTC)[reply]
The purpose of collecting the PII is to detect attempts to circumvent the one person, one vote requirement by one person voting from multiple accounts. This is done by analysing the public and non-public information in the same way that checkusers at SPI do. At arbcom elections struck votes fall into five categories:
  • Editors in good standing voting twice from the same account. This is permitted and should just automatically invalidate the older vote but occasionally it doesn't happen. Scrutineers strike the earlier vote.
  • Editors in good standing voting twice with different accounts in good faith. e.g. someone with a valid alt account wanting to change their vote but forgetting which account they used first time, or forgetting that they'd already voted. Scrutineers strike the earlier vote.
  • Editors discovered to be sockpuppetteers by normal means after they have cast votes. If only one account has been used to vote the most recent vote by that account is allowed to stand, if multiple accounts have been used to cast votes then all the votes are struck.
  • Known sockpuppetteers voting with one or more accounts discovered to be sockpuppets by the scrutineers. Scrutineers strike all votes.
  • Editors, not previously known to be sockpuppetteers, discovered by scrutineers to be voting with multiple accounts in bad faith. Scrutineers strike all votes.
Without PII being collected I believe that the first three types of multiple voting would still be detectable, the rest would not. Sockpuppetteers who vote using only one account will not be detected by scrutineers regardless of whether PII is collected or not. Thryduulf (talk) 16:43, 30 October 2024 (UTC)[reply]
The last two fall into the using the poll to catch editors who are socking that I mentioned, but should this be something that's part of the poll? I guess the main issues would be a sockpuppetiers setting up accounts that allow for voting, and then never using them again. That would be near impossible to catch unless they slipped up before hand.
Say the was a EC requirement to vote, a malicious actor could setup multiple accounts, use them to make good edits in completely separate areas to avoid scrutiny, and only bring them together within a vote in an attempt to sway the outcome. The normal methods for catching sockpuppets would be ineffectual in stopping that.
I was thinking this might be overkill, but now I'm starting to think I was wrong. -- LCU ActivelyDisinterested «@» °∆t° 17:14, 30 October 2024 (UTC)[reply]
At least the CUs can detect same IPs/same ballot + proxy. Aaron Liu (talk) 20:13, 30 October 2024 (UTC)[reply]
CUs who aren't election admins can't see anything more about the vote/voter that a normal admin can, even if they have a reason to look. Thryduulf (talk) 20:20, 30 October 2024 (UTC)[reply]
Sorry, I meant the scrutineers, not either of the above. I know that this is somewhat CU procedure and typed my thoughts out wrong :) thanks for the correction Aaron Liu (talk) 20:32, 30 October 2024 (UTC)[reply]
I think scrutineers can see the IP address associated with a ballot only if the poll is set to collect PII? Thryduulf (talk) 20:39, 30 October 2024 (UTC)[reply]
Looking back on the discussion, I read Disint's comment wrong. Aaron Liu (talk) 21:01, 30 October 2024 (UTC)[reply]
only if the poll is set to collect PII. I don't see any option to turn off PII collection on the page Special:SecurePoll/create. One way to turn that off would be to not grant the user right securepoll-view-voter-pii to anyone. Unless I am missing an option somewhere. –Novem Linguae (talk) 21:13, 30 October 2024 (UTC)[reply]
I'm not sure if creating a poll works on enwiki yet. Aaron Liu (talk) 23:24, 30 October 2024 (UTC)[reply]
This was in my localhost testing environment. –Novem Linguae (talk) 23:36, 30 October 2024 (UTC)[reply]
Hmmm, seems like this feature didn't get off the ground (only hide the voter list from other voters did). Sort of why we are in idea lab though -- if this is useful we could put in a feature request do "disable PII collection". — xaosflux Talk 22:02, 30 October 2024 (UTC)[reply]
  • Electionadmins do not need access to personally identifying information Someone should be able to scrutineer election data. Right now checkusers do that. I do not think electionadmins should have access to personally identifying information, but they should be able to consult with checkusers or have some way to confirm election validity. Bluerasberry (talk) 21:15, 1 November 2024 (UTC)[reply]
    This is about whether scrutineers should have access to PII, not about electionadmins. Scrutineers are the people whitelisted for each election to view a list of the browser-used and IP-used for every vote. Aaron Liu (talk) 22:21, 1 November 2024 (UTC)[reply]
    ?? I must be misunderstanding. Who gets whitelisted to scrutineer, and on what basis? As I understood, checkusers can already do this, and the discussion is about whether users with the electionadmin right could additionally scrutineer. Is "whitelist to scrutineer" an additional class of users? Bluerasberry (talk) 00:36, 2 November 2024 (UTC)[reply]
    No, this subheading is about whether scrutineers should be able to access PII, not electamins.
    For each election, highly trusted users (so far, with the votewiki elections, those users have been stewards) are asked if any of them would like to volunteer to scrutinize the election (and just that election, though they can also volunteer to scrutinize futre elections separately).
    After that, when setting up the election, two lists have to be added by an electamin: 1. a list of all users who may vote; and 2. a list of users who may view the PII-containing logs of voting.A list from which a software may "bouncer" to deny everybody not on the list is called a whitelist. Aaron Liu (talk) 00:49, 2 November 2024 (UTC)[reply]
    Who gets whitelisted to scrutineer, and on what basis? Depends on the election. One common format is to pick 3 stewards to scrutineer an election. Then WMF T&S gives them electionadmin permissions on votewiki, and they are added to just the election they'll be scrutineering. As I understood, checkusers can already [scrutineer]. I don't think this is correct. The checkuser group does not have any SecurePoll related permissions by default. We would have to change the #Wikimedia-site-config via a Phabricator ticket. However giving checkusers these permissions is a logical idea since checkusers have already signed the NDA and are already trusted to handle the kind of voter data that SecurePoll collects. –Novem Linguae (talk) 06:03, 2 November 2024 (UTC)[reply]
  • No PII means no scrutineering. Are we comfortable with having 600 vote WP:AELECTs or 1,600 vote WP:ACEs without anyone double checking IPs and user agents for obvious socks? I'm leaning towards yes collect PII. Also SecurePoll does not currently appear to have an option to turn off PII collection. –Novem Linguae (talk) 06:22, 2 November 2024 (UTC)[reply]

Do we need to encrypt the backend poll data?

[edit]

How people voted isn't available through the securepoll system, but when setting up a poll you can optionally choose the configure encryption. This will prevent vote data from being able to be accessed by system administrators who read the datastores. This provides quite strong voter secrecy. The downside is that cryptography is hard, and will require election administrators to understand these aspects, develop and strictly adhere to secure processes for key management. As this larger idea is about who can be an election admin, if we need this component we will need a way to ensure that such admins are not only trustworthy, but that they are also technically competent. — xaosflux Talk 14:26, 30 October 2024 (UTC)[reply]

I'm confused, you say How people voted isn't available through the securepoll system and encryption will prevent vote data from being able to be accessed by system administrators. So to clarify without encryption can system admins see how people voted, or is that information store elsewhere? -- LCU ActivelyDisinterested «@» °∆t° 14:35, 30 October 2024 (UTC)[reply]
My understanding is they can't unless election admins give them the key (basically a very strong password) Aaron Liu (talk) 14:48, 30 October 2024 (UTC)[reply]
If encryption prevents them from accessing the datastore, can they access the unencrypted datastore without need of a key? -- LCU ActivelyDisinterested «@» °∆t° 14:55, 30 October 2024 (UTC)[reply]
No, that's the core concept of encryption. Aaron Liu (talk) 14:58, 30 October 2024 (UTC)[reply]
When you create a poll, you can choose to optionally encrypt the poll data. This can be done with SSL or GPG keys. If you encrypt the poll, the stored data can't be read by system admins (note, this is not a wikipedia admin, or 'election admin', but the back-end server administrators). Finalizing the poll requires loading the decryption key in to the tallying mechanism. If the poll isn't encrypted it is possible the vote data could be accessed by system admins accessing the raw stored data. In either case, the software doesn't ever produce a voter:choice output. — xaosflux Talk 15:01, 30 October 2024 (UTC)[reply]
Ok so the choice that voters make isn't accessible even without encryption, which would suggest encryption isn't needed. What general type of information about the vote data is accessible without encryption? -- LCU ActivelyDisinterested «@» °∆t° 15:05, 30 October 2024 (UTC)[reply]
It's not available through the poll system (the confidentially risk is only of stored raw data for server admins). The public data is what you can already see on all elections: date of vote, name of voter, and if the vote has been replaced or stuck. — xaosflux Talk 15:19, 30 October 2024 (UTC)[reply]
Sorry this doesn't make it clearer. Yes or no, can a sysadmin see how people have voted by accessing the database if it's not encrypted? -- LCU ActivelyDisinterested «@» °∆t° 15:27, 30 October 2024 (UTC)[reply]
Yes. Aaron Liu (talk) 15:30, 30 October 2024 (UTC)[reply]
Thanks, and sorry for being slow. -- LCU ActivelyDisinterested «@» °∆t° 15:34, 30 October 2024 (UTC)[reply]
Note that the current poll encryption feature still doesn't entirely prevent an actively malicious sysadmin from, say, modifying the software to do something with the unencrypted data either before it's encrypted or after it's been decrypted to be counted. Of course that's much harder to pull off than just reading the unencrypted database (especially if you don't want to leave any traces) and requires a bit more server-side access, but not impossible. Taavi (talk!) 15:14, 30 October 2024 (UTC)[reply]
Yes this is true of all safety measures, but not an argument against them. -- LCU ActivelyDisinterested «@» °∆t° 15:27, 30 October 2024 (UTC)[reply]
I don't think we need to safeguard anything from the WMF. Aaron Liu (talk) 14:58, 30 October 2024 (UTC)[reply]
(no opinion in whether it should be encrypted, just stating some facts) Not all sysadmins are WMF staff. And there are a total of 192 sysadmins, which is much more than you might expect. * Pppery * it has begun... 17:34, 30 October 2024 (UTC)[reply]
Out of curiosity, where's the 192 number coming from? Folks in the ops LDAP group would definitely have enough database access to modify votes in the SQL database, but that's only 65 people I think. Who'm I missing? –Novem Linguae (talk) 21:26, 30 October 2024 (UTC)[reply]
deployment and restricted also have those permissions as I understand it. * Pppery * it has begun... 22:52, 30 October 2024 (UTC)[reply]
Yes. The first two can modify the running code, and analytics-privatedata-users can also read things from the database (in addition to the restricted group). Taavi (talk!) 04:20, 31 October 2024 (UTC)[reply]
analytics-privatedata-users contains 270 people, 128 of whom are already in one of the other groups, making 334 people total. No, I don't expect any of them to go snooping, but it is what it is ... * Pppery * it has begun... 21:53, 31 October 2024 (UTC)[reply]
Hmm, do they know they're operating WMF services? Aaron Liu (talk) 23:25, 30 October 2024 (UTC)[reply]
Obviously I can't read the minds of all of them, but probably, given that one of the requirements is signing L3. * Pppery * it has begun... 01:09, 31 October 2024 (UTC)[reply]
Yes. Taavi (talk!) 04:34, 31 October 2024 (UTC)[reply]
Given that voting choices could be accessed I would say it needs to be encrypted. Obviously this only makes it harder to access the information not impossible, but that is true of all such measures. Account passwords are required even though as a security measure they can be overcome.
Voters would expect that their votes are secure, or if not they need to be well informed that their votes are not. -- LCU ActivelyDisinterested «@» °∆t° 15:41, 30 October 2024 (UTC)[reply]
This should be decided on a case-by-case basis. If a WikiProject is using SecurePoll to elect its coordinators, using encryption seems like overkill. For ArbCom elections, on the other hand, I see no reason not to encrypt. For such significant elections, there would be no shortage of volunteers who can handle OpenSSL keys. – SD0001 (talk) 17:59, 30 October 2024 (UTC)[reply]
Leaning no to encryption. Seems like overkill. "Make the workflow more complicated for every electionadmin in every election" vs "make it harder for a rogue sysadmin to tamper with an election one time or a couple times until they get caught/fired/access removed" seems to be the tradeoff to weigh here. –Novem Linguae (talk) 21:28, 30 October 2024 (UTC)[reply]
It's not tampering with the result that is the problem, and reading the vote choices is unlikely to get caught. I wouldn't vote if I knew my vote was so easily accessible. -- LCU ActivelyDisinterested «@» °∆t° 22:01, 30 October 2024 (UTC)[reply]
"... in every election" Encryption can be configured differently for each election. – SD0001 (talk) 22:02, 30 October 2024 (UTC)[reply]
I'll have to try out encryption in a SecurePoll test wiki sometime. I should probably also take a peek at the database and see exactly what it encrypts. But my impression is it increases complexity for the electionadmin, who has to do stuff like generate encryption keys, then make sure the encryption key doesn't get lost else the entire election's results are lost. This will reduce the pool of folks that can easily administrate an election, limiting it to a small pool of technical users who are familiar with this encryption workflow. –Novem Linguae (talk) 06:08, 2 November 2024 (UTC)[reply]

Avoiding a long month of drama

[edit]

Well. WP:RECALL is upon us now, and, while clearly an improvement for community accountability, the first petition is already showing that the system has its limits. To be fair, that is to be expected – we can't really brainstorm a perfect system without any real-life testing, and such a new system should be open to community inputs for tweaking it into a more functional state.

Namely, the issue is with recall proposals that are, from the start, overwhelmingly likely not to succeed. In a case such like this one, where the number of (informal) opposes far outweighs the number of signatories, prolonging the long drawn-out process (the petition being open for a month, and then potentially seven days of RRfA) isn't desirable if the outcome is already pretty much known. I figure there should be a way to cut short petitions where it is clear that most editors are not behind it, a sort of WP:SNOW close, to avoid dragging the admin and the community through a month-long slog.

Of course, the petition itself shouldn't be the final !vote on admin accountability, but only a means to bring up the issue. So, if we go through an opposes/signatories ratio to close it early, for instance, it should be pretty high (maybe 3 to 1?), but still allow a way to cut short petitions with no chances of succeeding. Chaotic Enby (talk · contribs) 13:55, 28 October 2024 (UTC)[reply]

Agreed. If each person were allowed to write a single short statement (absolute maximum 2 sentences) about why they support/oppose and no discussion or replies were allowed then a month would be reasonable. A month of what's currently happening at the first petition is completely unreasonable - a week of that plus a week of RFA hell is not reasonable even for someone whose conduct is beyond the pale (and they should be at Arbcom anyway) let alone a month for someone who has just made a few minor mistakes or pissed off a few people.
The Crats should be empowered to close petitions early if the result is clear (either way). Arbcom still exists as a venue should people think that a petition that was going to succeed was closed too early. Thryduulf (talk) 14:15, 28 October 2024 (UTC)[reply]
Isn't the primary point of the petition process to ensure that we don't have frivolous RRFAs? It seems that most of the participants are already trying to skip to a future RRFA discussion that may not even materialize. — xaosflux Talk 14:23, 28 October 2024 (UTC)[reply]
That is indeed an issue, the petition is itself getting a RfA-like amount of discussion before the RRfA even started. Thryduulf's proposal of limiting the conversation to a single short statement per person could make it much more manageable, and cut short the problem by making 30 days long petitions less awful. Chaotic Enby (talk · contribs) 14:59, 28 October 2024 (UTC)[reply]
Opposes don't formally affect the outcome of the petition, that's what the RRfA is for. From my own thought process (and from what I read from that discussion), opposes can only dissuade potential petition signers to NOT sign the petition. fanfanboy (block) 14:39, 28 October 2024 (UTC)[reply]
I know, that's why I was referring to them as informal opposes above. But there should still be a way for the community to formally state that the vast majority is not in support of a petition. At least to shut down frivolous petitions in advance. Chaotic Enby (talk · contribs) 14:57, 28 October 2024 (UTC)[reply]
I feel like if a petition is unnecessary, then no one would sign it. fanfanboy (block) 15:02, 28 October 2024 (UTC)[reply]
The Lizardman's Constant means that pretty much all views will be supported by some people, so no, I don't think we can rely on that. It's a complete waste of everyone's time if we only pay attention to the support votes and force a WP:SNOWBALL petition to go to RRfA. Theknightwho (talk) 18:34, 30 October 2024 (UTC)[reply]
There is no drama except what some editors are creating. I don't think an admin is going to quit because they discover that five people think they shouldn't be an admin. Those that oppose the petition can just... not sign it. It'll be over in 30 days. I'm not opposed to shortening the 30 days but I'd rather wait at least one full cycle before deciding. Preferably more than one full cycle. Levivich (talk) 14:47, 28 October 2024 (UTC)[reply]
As I have said elsewhere, we need to reduce the drama surrounding these. I agree that people opposing the petition should just leave it alone. There should be no discussion section and no threaded responses to endorsement; a week of discussion (which is plenty) happens once the petition is successful. Additional discussion only makes the signal to noise level worse and cranks up the heat. —Kusma (talk) 22:54, 29 October 2024 (UTC)[reply]
Noting I've withdrawn the petition. Sincerely, Dilettante 15:41, 28 October 2024 (UTC)[reply]
Agree with some of the others that shortening the time makes sense, though I don't think we should be cutting it to shorter than 2 weeks if we started at 30 days. 25 signatures in 30 days does seem really out of wack - less than one signature a day, in a community this large, where RFAs have some 200 votes in a week and we've already got more than 400 votes in the admin elections? Seems very off. -- asilvering (talk) 16:12, 28 October 2024 (UTC)[reply]
Two weeks as a baseline sounds like a more reasonable time, that could very much work. Chaotic Enby (talk · contribs) 16:15, 28 October 2024 (UTC)[reply]
Thing is that many editors (including myself) voted for the 30 days. Now seeing what has happened, I agree it should be shortened. 2 weeks seems like a good number. fanfanboy (block) 16:21, 28 October 2024 (UTC)[reply]

I suppose, we'll have to be mindful of the potential for editors to seek an administrator's recall, who blocked/banned them, in the past. Grudges are always possible as being a core of recall attempts. GoodDay (talk) 14:46, 28 October 2024 (UTC)[reply]

  • I think shortening the time period for the petition to 10 or 14 days makes sense. I would oppose allowing snow closes regardless of how unlikely it appears that a petition will pass. ~~ Jessintime (talk) 15:18, 28 October 2024 (UTC)[reply]
    That's exactly what I suggested a few months back Mach61 16:44, 28 October 2024 (UTC)[reply]
  • I'm inclined to believe that, instead of tinkering with this on an ad hoc basis with every new petition, we modify the terms of the recall process to be a six-months trial and then -- at the end of that -- evaluate everything that worked and didn't and make whatever modifications are needed in one fell and final swoop. Chetsford (talk) 16:25, 28 October 2024 (UTC)[reply]
    @Chetsford The close of the final RfC establishing recall instructed that any outstanding issues may be resolved through normal editing. (emphasis mine), and personally, I am very burnt out by all the multi-step trials and ratification RfCs that sprung out of RFA2024. Mach61 16:47, 28 October 2024 (UTC)[reply]
    I have no idea what that means. Any single editor can just change the process by WP:BOLD editing it? If that's the case, why are we having this discussion? Chetsford (talk) 16:52, 28 October 2024 (UTC)[reply]
    To be fair, this is a discussion on the idea lab, so the goal is first to figure out what to change before figuring out how to change it. And also because, even if a user could technically make a WP:BOLD edit, having a consensus behind it is always good. Chaotic Enby (talk · contribs) 17:00, 28 October 2024 (UTC)[reply]
  • I looked at the petition before it closed, and realised multiple editors opposing it despite it not having any effect. I think it should be possible to run a petition in a closer timeframe to an RfA or AfD. To summarise, petitions could be changed as follows :
  • Each petition runs for exactly a week.
  • Any extended confirmed editor can support or oppose the petition
  • If consensus is reached to desysop after a week (ie: support / support + oppose = 70% per current RfA thresholds) then the admin is desysopped
I think holding an admin to the threat of being desysopped for over a month is worse than what happens at Arbcom. Conversely, if the community is in obvious agreement than an admin has outstayed their welcome and must go, it gets the job done far more quickly without people getting frustrated about when it's going to happen. And furthermore, if somebody starts a petition in retaliation ("Desysop this admin, he blocked me for no reason!") it'll get short shrift and SNOW opposed by the community.
Any views on that? Ritchie333 (talk) (cont) 16:51, 28 October 2024 (UTC)[reply]
The only issue I have with that is theoretical. Ostensibly, the petition is supposed to create a turnstile sparing an Admin from having to go through the back-and-forth of an entire RfA unless there's some minimum support for that. In other words, ideally, the Admin simply ignores the petition until or if the threshold is met. Only then do they need to ramp up to start compiling, potentially, years of diffs, etc. to defend themselves at RfA. Going straight to RfA means any single, aggrieved editor can encumber an Admin with the significant angst of a full RfA.
Of course, that's all theoretical. As we've seen from the current example, the mere act of petitioning creates the angst it was designed to mitigate. So, if we're going to introduce a Reign of Terror anyway, we may as well make it the most efficient Reign of Terror we can come up with, on which basis I'd support this suggestion. Chetsford (talk) 17:01, 28 October 2024 (UTC)[reply]
The other option would be to make it so that the petition doesn't turn into a Reign of Terror to begin with. Which is easier said than done, but a good first step would be to limit back-and-forth conversation and just have it be, well, a petition. Chaotic Enby (talk · contribs) 17:05, 28 October 2024 (UTC)[reply]
I do have a few concerns on that. In this situation the Admin is being recalled for reasons no one is allowed to articulate to them, but maybe they'll learn them during sentencing (RfA)? I liked The Trial as much as anyone, but I'm not sure how I feel about recreating it IRL. But I'm open to whatever. Chetsford (talk) 17:13, 28 October 2024 (UTC)[reply]
No it wouldn't prevent reasons being given, it would just restrict discussion of those reasons. So everybody supporting or opposing the petition would be able to (arguably should be required to) give a single short statement (50 words or 2 sentences have been suggested) about why they are supporting/opposing. However there would be no discussion unless and until an RRFA was opened. There would be no restriction on clarification being sought on user talk pages, e.g. if user:Example wrote "Support because of their actions at the recent AfD" anyone would be allowed to go to user talk:Example and ask which AfD(s) they were referring to if it wasn't clear. Thryduulf (talk) 17:20, 28 October 2024 (UTC)[reply]
I would say no. If the petition can get 25 people to agree (despite all the issues of the discussion section), then the RFA should run. Y'all are Streisanding the current petition and bringing people in. If it was as sterile and clinical as the process laid out was supposed to be, it would more than likely died in a month. spryde | talk 20:52, 28 October 2024 (UTC)[reply]
I think any petition is going to get significant amounts of attention, maybe not quite this much if they become routine, but certainly enough that it's never going to be "sterile and clinical" under the current setup. Thryduulf (talk) 21:14, 28 October 2024 (UTC)[reply]
If the time is reduced to a week, then the number of signatures needed should be reduced. I also don't understand the point of opposition statements. If it is a petition, then there should just be people signing it, maybe proposing changes to the petition statement. It seemed like a lot of the opposition was based on people not likely the process. There is already a problem with accountability for admins in Wikipedia, because admins are not only well known, but have power to block people, and probably have more knowledge of how Wikipedia works than the poor editors who try to recall them. Admins are pretty safe. Term limits would have been a better solution, as well as temporary blocks for admins. Tinynanorobots (talk) 11:35, 29 October 2024 (UTC)[reply]
For now, we have a sample set of one incomplete case. Ten editors have signed the petition in the first 40 hours. A linear projection would predict that 25 signatures would be reached in less than five days. Some commenters have assumed that the level of opposition expressed to this petition indicates that Graham87 would retain the admin bit in an RRFA. If a case that appears this weak does reach 25 signatures in less than a week, why should we have to wait a month for cases where there is less enthusiasm for signing a petition. I will note that the rate of new signatures likely will decline, prolonging the end, and that some commenters are claiming that many potential signers will wait to the last minute to sign to avoid social pressure, but that is not an argument for waiting a month, as they can sign the petition at the last minute whether the duration is for a week, two weeks, or a month. But, as I said, this is the first case, and my crystal ball is very murky. Donald Albury 13:39, 29 October 2024 (UTC)[reply]


I think that that first recall petition showed some of the warts of the process in a really stark way. Floating 4 significant changes for the community to think about here, either separately or in combination:

  • 1) - The petition process is too long. If these are going to turn into mini-RfAs, then the petition needs to be significantly shorter than a RFA. 24-72 hours is plenty of time to see whether the petition has legs, anything more is cruel.
  • 2) - The petition is too easy to initiate. I know that people will complain about cabals, but I really think it should take an admin to initiate one of these. Alternatively a small group (3 ish) of extended confirmed users works.
  • 3) - We should move from number of supports to number of net supports. If a petition has 1 net support at closing time, it can go through as prima facie evidence that the petition has legs. If the ratio of opposes to supports gets over 2-3 to 1, we can close early without losing many petitions that would wind up successful.
  • 4) - The commentary is too much. Restrict people, both support and oppose, to something very short, like 10 words and 1 link.

Obviously this is idea lab, so please discuss which of these have merit fluidly either alone or in any combination. tweak numbers, break things. Tazerdadog (talk) 17:07, 28 October 2024 (UTC)[reply]

I'd agree with shortening the petition process (although 72 hours might be too drastic), but I think turning them into mini-RfAs is not the goal. The point of the petition is to see if there is a substantial number of editors wanting a recall election to begin with, not to replace the recall election entirely. And, if you need to get 3 people on board to start the petition, you're functionally making a petition for the petition.
For the same reason, net supports shouldn't really be what is measured (as it isn't about whether the admin has majority support, but only about whether some people are questioning it). A large oppose ratio, however, would indicate the petition will likely not be successful, so the early close you suggest could work. Also agree with your idea of restricting commentary, as said above. Chaotic Enby (talk · contribs) 17:11, 28 October 2024 (UTC)[reply]
The old RFC/U process required two editors to sign within 48 hours, or the page would get deleted. These two editors had to show evidence(!) of having attempted to resolve the same(!) dispute with the targeted editor. This was fairly effective at preventing RFC/Us over disputes that just needed a Wikipedia:Third opinion. WhatamIdoing (talk) 18:43, 29 October 2024 (UTC)[reply]
That could work, in a way. Every editor can start a petition, but two editors have to sign within 48 hours or it gets closed without further ado. Chaotic Enby (talk · contribs) 18:50, 29 October 2024 (UTC)[reply]
  • It's impossible to constrain the discussion when the petition has started and for the petition page not to turn into a quasi-RfA. That's why the petition signatures and comments should be understood as RRfA !votes. The signatures would begin counting as !votes when 25 of them are collected, and prior to that, the signatures would be null !votes, and only valid as fulfilling a precondition to their collective validity as !votes. A signature is actually a latent 'oppose adminship' RRfA !vote. An "oppose petition" comment is actually a 'support adminship' RRfA !vote. At any point, if the admin does not like the protraction and feels secure about passing, the admin can cut the petition stage short and start the RRfA with their statement, answers and all, without a need to wait for signatories to reach 25. That imbues all signatures with the power of a !vote immediately, regardless of how many there are, whereas the "oppose petition" comments have had the power of a 'support adminship' !vote all along. If the admin doesn't feel secure, they can wait it out, and are protected by the fact that the opposition to their adminship is ineffective until it reaches the critical mass of 25 signatories. It isn't reasonable to think that the admin is unfairly treated by the fact that opposition to their adminship is rendered ineffective until a difficult procedural barrier is overcome; that's obviously a mechanism that protects their status. If they don't feel like they need that protection, if the climate seems friendly to their adminship, they can relinquish it and start the RRfA.—Alalch E. 17:32, 28 October 2024 (UTC)[reply]
    I'm not sure we should understand them as quasi-votes, since it would be perfectly reasonable for someone to sign the petition because they think a re-RFA ought to be initiated, not because they think the admin should step down. That is, I can easily see someone putting their name on the petition because they believe a re-RFA is the right thing to do, not because they desire for the admin in question to be de-sysopped. But it's true that nothing is stopping an admin from "calling the bluff" and standing for re-RFA before the petition reaches 25 signatories. At this point, frankly, that doesn't look like it would be a bad move for our unfortunate first candidate. -- asilvering (talk) 19:27, 28 October 2024 (UTC)[reply]
    The way the process is currently set up, you're right. But I would argue that it should be different (that's the idea I'm presenting): If you do not think that the admin should cease being admin, you should not sign the petition. On the material side, the petition should be presented as: "By signing you are stating that the administrator has lost your confidence"; and on the procedural side: "By signing you are stating that (because the administrator has lost your confidence and provided that he has also lost the confidence of many other editors) the administrator should undergo a RRfA". —Alalch E. 11:09, 29 October 2024 (UTC)[reply]
    It isn't impossible to constrain discussion. We are capable of setting and enforcing a rule that says "Signatures only. No diffs, no explanations, no discussion, no opposes". This might be fairer, since even a few words or a single diff could prompt "me too" votes from people who had no concerns of their own, and a diff or a brief comment could be taken unfair or out of context. It would probably be stressful for the admin, as people would be publicly expressing dislike without any reason.
    Editors generally oppose efforts to prevent them from talking about other editors, though, so I doubt we'll end up there. More realistically, we could insist that any discussion happen on the talk page. WhatamIdoing (talk) 20:00, 29 October 2024 (UTC)[reply]
    ArbCom manages to have strict rules about constraining discussion, and it does lead to more productive cases (read: not a shiftest). I would support a "Signatures only" rule, especially considering the opening comment should already be expected to have the needed context.
    A talk page discussion would be already lower profile and likely more calm, and ultimately look less like a !vote or like its own mini-RfA. Chaotic Enby (talk · contribs) 20:21, 29 October 2024 (UTC)[reply]
    Any rule restricting what can and can't be said on the page needs to come with explicit instructions to this on the page and a clear statement of who is allowed to remove things that objectively break the rules (I'd favour "anybody"). Perhaps accompanied with a "you will be partially blocked from this page if you reinsert, without explicit advanced consensus, something removed." Thryduulf (talk) 20:46, 29 October 2024 (UTC)[reply]
    That could definitely work. WP:RECALL doesn't need a set of clerks like the (much more complex) ArbCom cases do, if the only rule is "just leave a signature" or close to that. Also agree with the disclaimer, and good of you to be thinking of the implementation details already!
    I'm thinking of having a formal proposal with both the restriction on discussion and the shortened timeframe as independent options. Given how the WP:RECALL RfCs have been criticized for not being well-advertised, it might be good to bring this one up on WP:CENT. Chaotic Enby (talk · contribs) 21:55, 29 October 2024 (UTC)[reply]
    I think that's a good course of action. Aaron Liu (talk) 22:25, 29 October 2024 (UTC)[reply]
    We can start workshopping the RfC right now, but it's probably best to hold off opening the RfC itself for the moment given how heated emotions are. Chaotic Enby (talk · contribs) 22:48, 29 October 2024 (UTC)[reply]
    Discussion will migrate elsewhere. ArbCom is mentioned as a counterexample, but discussion there is quite free-flowing, only formatted differently to avoid long non-constructive threads... but the stated problem here is not non-constructive threads, the stated problem is comments. That is completely different. "Discuss calmly and with measure" and "don't talk" is different. It will be possible to have an adjacent discussion on some other page or pages. And if you are blocked from the page, so what, what you added to the page, diffs and all, stays in history and can be viewed by anyone. —Alalch E. 23:36, 29 October 2024 (UTC)[reply]

    And if you are blocked from the page, so what, what you added to the page, diffs and all, stays in history and can be viewed by anyone.

    Nobody inspects every nook and cranny in history for bad things people have said to agree with it. Aaron Liu (talk) 01:29, 30 October 2024 (UTC)[reply]
    I agree that a complete ban on discussion will result in the discussion happening elsewhere, but that's not necessarily a bad thing. Wherever there are humans, there will be gossip mongers, but gossip whispered between a few people (e.g., via Special:EmailUser) for a few days, or even for 30 days, is not as widely and as permanently destructive as accusations posted on the internet forever. WhatamIdoing (talk) 18:04, 30 October 2024 (UTC)[reply]
    That elsewhere could just be the talk page, and it appears that it might just be that. Edit: All in all, "discussion elsewhere" + word limits + RfA monitor function preserved + "five uninvolved signatories first" latch mechanism could all add up to something good. I'm for trying. —Alalch E. 22:32, 30 October 2024 (UTC)[reply]
  • It all depends on who you want to sign up to a petition. If it is only "editors who have independently decided that an admin's conduct should be examined", the only way is to disallow comments from both signatories and opponents. Otherwise many signatories will sign because they are convinced by the arguments, even if they never heard of the admin before. In that case, allowing only signatories to comment will dramatically skew the results and be quite unfair. In summary, allow everyone to comment or allow nobody to comment. Zerotalk 02:10, 30 October 2024 (UTC)[reply]
    Very good point, and why I would favor "allow nobody to comment" as a general rule. Chaotic Enby (talk · contribs) 02:22, 30 October 2024 (UTC)[reply]
  • I'd also like to raise another issue. We have created a risk-free way for editors to get back at an admin who has sanctioned them. I think that editors who have received a recent (definition?) personal sanction from an the admin should not be a signatory. Zerotalk 02:10, 30 October 2024 (UTC)[reply]
    On the other hand, editors victims of administrator misconduct should definitely be able to support the administrator being brought to recall. Chaotic Enby (talk · contribs) 02:26, 30 October 2024 (UTC)[reply]
    I can see both sides of this. Perhaps a reasonable way forwards is to disallow someone from initiating a petition if they have received a recent (within the last 3 months?) personal sanction from the admin. They can still support a petition initiated by someone else, but perhaps only if 5 uninvolved editors have already supported. If there is a genuine issue this should be an easy bar to clear but it would make retaliatory petitions much harder to initiate and harder for them to succeed. Thryduulf (talk) 02:35, 30 October 2024 (UTC)[reply]
    Maybe we could make it so that the first five signatures (other than the initiator) must not have been involved with any dispute in which the admin concerned acted in their capacity as an administrator within the last (1? 2? 3?) months. If five uninvolved editors are prepared to sign a petition that suggests it's more likely to have some merit than if no such group of five are? Thryduulf (talk) 02:39, 30 October 2024 (UTC)[reply]
    That makes sense. Zerotalk 02:42, 30 October 2024 (UTC)[reply]
    Let's say it's day three and there are fifteen signatures. The first five signatories have not been involved in the discussed sense, followed by ten signatures from people who have been involved (they were the greater cohort that was waiting for the special signatures to add up so that they can add theirs; imagine ANI participants). One among the first five withdraws their signature ("I changed my mind after reading the talk page"). There are no longer five signatures from uninvolved signatories. What then? All's good? (Probably not.) Petition has failed? (Probably not.) Monitor halts signature collection only allowing signatures from uninvolved signatories, until one such additional signature is collected? (Probably not.) Monitor notes that the petition will be invalid unless at least one more special signature is supplied during the entire remaining period? (Maybe.) Monitor notes that the petition will be invalid unless at least one more special signature is supplied during a set period, for example three days? (Maybe.) —Alalch E. 17:00, 30 October 2024 (UTC)[reply]
    I hadn't thought of that scenario. The simplest option would just be a latch - once five uninvolved people have signed the petition is unlocked and remains that way for the duration. Thryduulf (talk) 19:03, 30 October 2024 (UTC)[reply]
    I agree. Anything more complicated would be too complicated. —Alalch E. 22:30, 30 October 2024 (UTC)[reply]

Workshopping the RfC

[edit]

As the two main proposals that editors seem to converge on (limiting discussion and shortening the petition timeframe) are essentially independent, I'm thinking it can be best to go for a two-part RfC, with the following questions:

  • Should input to WP:RECALL petitions be limited to signatures only?
  • Should the petition duration be limited to X amount of days?

There is also the possibility of having multiple options for each question. For the first one, an alternate proposal of limiting input to to a short statement per person was also suggested, while multiple timeframes for the petition could also be proposed. Chaotic Enby (talk · contribs) 22:59, 29 October 2024 (UTC)[reply]

I think a RFC like this needs to happen. I think the second bullet point is fairly self-explanatory, but the first needs more thought. On a recall petition, is there value in having a statement from the initiator? A statement from the admin being recalled? Statements from people bringing up new evidence? Statements/signatures from supporters? Which belong on the main page, and which belong on the talk page? If we impose a length limit, can anyone truncate statements to fit in it? Do we need clerks, arb style?
For example, I favor the initiator getting a short statement, the admin having unlimited length to respond optionally (hidden comment in the template that makes a section if they choose to respond), all recallers signature only on the main page, with limited commentary on the talk page, and any list of supporters with limited commentary on the talk page, no threaded discussion anywhere. Any editor except the initiator and the admin being recalled can move comments to enforce length/threading/talk page. This is not about my preference, but more saying that this bullet point can get really complex really fast, and we should think about that now in workshopping. Tazerdadog (talk) 02:04, 30 October 2024 (UTC)[reply]
Thanks a lot for the feedback! You're right that the first bullet point should definitely be clarified before the actual RfC.
In my mind, the initiator would be able to make a short statement, with the rest being only signatures (as the point of the petition isn't to be its own RRfA, but only to gauge whether it has enough support). Regarding the admin responding, I think it (and other replies) should be reserved to the talk page, to avoid it becoming a RfA-lite where the admin has to respond to the claims to not be seen as suspicious. Chaotic Enby (talk · contribs) 02:20, 30 October 2024 (UTC)[reply]
If the admin is allowed a right of reply, but only on the talk page, it should be possible to see from just the main page whether they have chosen to respond or not. Regardless of where, everybody who has the right to comment (including the responding admin) should be subject to a word limit, although not necessarily the same limit. Thryduulf (talk) 02:30, 30 October 2024 (UTC)[reply]
In my mind, the initiator is no more or less important than anyone else who prefers to recall that admin, I prefer not creating a "first mover" advantage. So I'd rather just be strictly signatures only, or strictly "Short statement on main page without replies" for everyone.
The talk page will be open anyway, so people who want to elaborate on why can do it as they prefer Soni (talk) 05:14, 30 October 2024 (UTC)[reply]
I can get behind a word limit for the responding admin. I do think it's important that the admin have the ability to present their case in the same location that the initiator does. Tazerdadog (talk) 06:55, 30 October 2024 (UTC)[reply]
I agree with that as well, I just end up at "Initiator and all future signatures should be given same weightage" and "Maybe both should be on talk" as my preferences. Soni (talk) 05:20, 30 October 2024 (UTC)[reply]
I start with "someone should say why we're all here" and "I don't want everyone piling on with extensive commentary. I will concede that I create a first mover advantage as a consequence of those, but I think that's the best we can do. Either way, I think we can craft a RFC that presents all this fairly without too much difficulty. Tazerdadog (talk) 06:52, 30 October 2024 (UTC)[reply]
Ultimately, a "first mover" advantage makes sense in that, since they're starting the petition, they are responsible for explaining it. We don't need 25 redundant explanations, but we don't need an unexplained petition either, so it is logical that the creator of the petition be the one to state the case for it. Chaotic Enby (talk · contribs) 08:10, 30 October 2024 (UTC)[reply]
"The talk page will be open anyway", will that result in all the "pre-RRFA RRFA" stuff just happening there instead of on the petition itself? Anomie⚔ 07:49, 30 October 2024 (UTC)[reply]
Moving the discussion to a less prominent place behind the petition, plus a word limit as Thryduulf suggested, would definitely limit the "pre-RRFA RFA" stuff. Not everyone will go through long talk pages, making it less critical to respond than with the "in-your-face" discussion that currently runs in the middle of the signatures. Chaotic Enby (talk · contribs) 08:07, 30 October 2024 (UTC)[reply]
Will this: Any ... comment may be struck based on the same criteria used during requests for adminship (from WP:RECALL) hold true on the talk page? —Alalch E. 16:33, 30 October 2024 (UTC)[reply]
I think that is something that will need to actively decided. Thryduulf (talk) 16:45, 30 October 2024 (UTC)[reply]
If it's mandated that no discussion happen on the petition page, I'm not so sure the petition's talk page would remain very much "less prominent". Sure, not everyone will bother to check the talk page, but knowing that's where discussion is I suspect anyone who would have pre-RRFA RFFA-ed as things are now would. Anomie⚔ 07:51, 31 October 2024 (UTC)[reply]
I don't think it's a good idea to start a two-part RFC so soon after we just ended a three-part RFC. Take note of the backlash to the third RFC; a fourth RFC will get even more backlash; a fifth even more. Levivich (talk) 16:45, 30 October 2024 (UTC)[reply]
By two-part, I mean asking two questions simultaneously, not running one RfC and then another. The second RfC had more then ten simultaneous questions, so two should be manageable. Chaotic Enby (talk · contribs) 17:28, 30 October 2024 (UTC)[reply]
But you really think, three days into the first petition, you've learned enough about this process to know how to change it for the better? There's no part of you that's thinking "it's too soon to draw any conclusions"? Levivich (talk) 17:33, 30 October 2024 (UTC)[reply]
I share Levivich's concerns here. Now's a fine time to take some notes, but we're 10% of the way through the first use of a process. We might learn something in the coming days, or in a second petition. We might also discover that the RFC question needs to be "Well, that was a disaster. All in favor of canning the idea completely?" WhatamIdoing (talk) 18:12, 30 October 2024 (UTC)[reply]
And this is why I said, above, We can start workshopping the RfC right now, but it's probably best to hold off opening the RfC itself for the moment given how heated emotions are. I do not claim to personally know exactly how to change the process, but we can already start discussing the shortcomings we can see, even if we are not going to open the RfC right now. Chaotic Enby (talk · contribs) 18:21, 30 October 2024 (UTC)[reply]
People have been proposing changes all over the place. Why not have a discussion that will hopefully bring up possible problems with proposed changes, even if it will be a while before any RfC should start? Donald Albury 19:42, 30 October 2024 (UTC)[reply]
@Chaotic Enby: I've been thinking about how to format this RfC for a fair while. If someone has a better idea than yet another dedicated subpage, I'm all ears, because I'm not sure how else to deal with the number of proposals and changes people are asking for. theleekycauldron (talk • she/her) 18:44, 31 October 2024 (UTC)[reply]
I think subpages is fine, but we probably should try to limit the number of options to be voted on, in some way. Either by number or some other ways.
Say if a proposal is something like "For 2 future RECALL petition, the petition will not have any discussion. After this trial, you need consensus to make it permanent" - that's self contained and gives place to start off from. Much better than just trying to push through every change at once. Soni (talk) 20:56, 31 October 2024 (UTC)[reply]
That's the point of starting this discussion now. We're at the ideas stage, at some point after the first petition ends (and, if one happens, after the subsequent RRFA ends) this will move into the stage of collating those ideas that both could work and got some indication they might be supported and refining them into draft proposals. Once we have a rough idea of what and how many proposals there are is the time to work out the best structure for an RFC, as until we know those things we can't know what will and won't work. Thryduulf (talk) 00:39, 1 November 2024 (UTC)[reply]

Notification: Admin recall has an RfC

[edit]

Wikipedia:Administrator recall has an RfC for possible consensus. A discussion is taking place. If you would like to participate in the discussion, you are invited to add your comments on the discussion page. Thank you. CNC (talk) 21:59, 1 November 2024 (UTC)[reply]

Author Profile Page

[edit]

One should exist for Authors to personally fill out a profile. Many book readers would like to know the "about" information about writers that have books published. 91.242.149.121 (talk) 09:15, 29 October 2024 (UTC)[reply]

If you're referring to the authors/editors of an article, editors already have their own user pages, which are accessible from an article edit history. If you're referring to the authors of books that merit Wikipedia articles, this isn't a place for people to tell about themselves(see WP:AUTO). 331dot (talk) 09:18, 29 October 2024 (UTC)[reply]

Allow IP editors to set preferences

[edit]

IP editors now have the ability to turn on dark mode, which previously was limited to logged in users setting a preference. We should extend this concept to allow IP editors to set other prefernces such as disabling fundraising banners or whatever other preference they prefer. RudolfRed (talk) 23:33, 1 November 2024 (UTC)[reply]

I believe that would require changes to the software. Thryduulf (talk) 00:46, 2 November 2024 (UTC)[reply]
I mean, temporary accounts are already on. I doubt that the WMF isn't already planning this. Aaron Liu (talk) 00:49, 2 November 2024 (UTC)[reply]
Supporting preferences in general would mean the caching infrastructure could no longer be used for non-logged in users, which would have a big impact on the amount of computing resources required to handle Wikipedia's traffic. So I don't believe that general support is in the works. isaacl (talk) 05:40, 2 November 2024 (UTC)[reply]
They could 1. restrict preferences to a subset that won't interfere with caching; or 2. figure out a way to serve cache to everyone who didn't touch certain preferences. Aaron Liu (talk) 18:28, 2 November 2024 (UTC)[reply]
I've discussed this before so don't really want to get into the details again, beyond saying that making the servers do anything is more expensive than reading ready-to-go HTML content and sending it back. Please feel free to discuss your ideas with the WMF engineering team. isaacl (talk) 21:33, 2 November 2024 (UTC)[reply]

Comparison shopping with data from factboxes

[edit]

As more information is put in Wikidata and is presented in Wikipedia's fact boxes, I think this opens a possible new feature or gadget similar to the comparison shopping offered by many e-commerce websites. As I visit the article Thailand, the factbox should have a little tick box to add this article to my personal comparison basket, and when I tick that box on another comparable object (using the same factbox template), say Chile, I should be able to view my current comparson set, presenting a table with two columns for Thailand and Chile, and rows for their attributes: capital city, main language, population, area, GDP, etc. LA2 (talk) 11:45, 2 November 2024 (UTC)[reply]

Retrieved from "https://en.wikipedia.org/w/index.php?title=Wikipedia:Village_pump_(idea_lab)&oldid=1255047271"
pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy