Jump to content
 







Main menu
   


Navigation  



Main page
Contents
Current events
Random article
About Wikipedia
Contact us
Donate
 




Contribute  



Help
Learn to edit
Community portal
Recent changes
Upload file
 








Search  

































Create account

Log in
 









Create account
 Log in
 




Pages for logged out editors learn more  



Contributions
Talk
 



















Contents

   



(Top)
 


1 Wikipedia Hall of Fame?  
75 comments  


1.1  Hall of fame topic; section break 1  





1.2  Hall of fame topic; section break 2  





1.3  Hall of fame topic; section break 3  





1.4  section break 4; [wikilounge idea]  





1.5  Section break 5  





1.6  How about a Hall of Shame?  





1.7  An idea that might work: A Wikipedia statue  







2 Allowing Master's theses when not used to dispute more reliable sources  
29 comments  




3 Make the edit request facility optional  
33 comments  




4 Proposed revision of the COI guideline  
12 comments  


4.1  Financial Conflict of Interest  





4.2  Non-financial Conflict of Interest  





4.3  Managing Conflicts  





4.4  Exceptions  



4.4.1  General exceptions  





4.4.2  Wikipedians in residence  







4.5  Reporting suspected violations  





4.6  Discussion  







5 Ready for the mainspace  
123 comments  


5.1  Contemplation of a Proposal: Mandate edit summary linking to WP:DRAFTOBJECT in every unilateral draftification  







6 Reliable source engine  
9 comments  




7 possible idea; entry compiling overviews of multiple novels, in a single series  
5 comments  




8 Proposed edits feature  
35 comments  




9 Whales  
10 comments  




10 Add a timeline to Wikipedia pages  
7 comments  




11 Dark Mode as a Premium Feature  
5 comments  




12 Lack of Filipino folk arts  
8 comments  




13 Some kind of reminder at AN/I  
3 comments  




14 Wikipedia:MOS on Music / Song Track Listing Credits  
5 comments  




15 Re-use and edit citation  
12 comments  




16 A confusion disclaimer should be added to the top of the page for cisgender  
3 comments  




17 What to do with near-empty lists of names of obscure asteroids?  
3 comments  




18 Search engine for policy  
8 comments  













Wikipedia:Village pump (idea lab)






Deutsch

گیلکی




سنڌي
ி
 

اردو

 

Edit links
 









Project page
Talk
 

















Read
Edit
Add topic
View history
 








Tools
   


Actions  



Read
Edit
Add topic
View history
 




General  



What links here
Related changes
Upload file
Special pages
Permanent link
Page information
Get shortened URL
Download QR code
Wikidata item
 




Print/export  



Download as PDF
Printable version
 




Print/export  







In other projects  



Wikimedia Commons
 
















Appearance
   

 






From Wikipedia, the free encyclopedia
 


This is an old revision of this page, as edited by Joe Roe (talk | contribs)at09:27, 21 June 2024 (Contemplation of a Proposal: Mandate edit summary linking to WP:DRAFTOBJECT in every unilateral draftification: Reply). The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.
(diff)  Previous revision | Latest revision (diff) | Newer revision  (diff)

  • First discussion
  • End of page
  • New post
  • WP:VPIL
  • 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:

    Discussions are automatically archived after remaining inactive for two weeks.

    « Archives, 38, 39, 40, 41, 42, 43, 44, 45, 46, 47, 48, 49, 50, 51, 52, 53, 54, 55, 56, 57, 58

  • Reliability of The Telegraph on trans issues
  • 2024 RfA review, phase II
  • Propose questions to candidates in the 2024 WMF board of trustees elections
  • WMF draft annual plan available for review
  • For a listing of ongoing discussions, see the dashboard.
  • edit
  • history
  • watch
  • archive
  • talk
  • purge
  • Wikipedia Hall of Fame?

    What are your thoughts? Is it going to work? Comment down below. Wolverine XI (talk to me) 17:28, 8 April 2024 (UTC)[reply]

    i think it would be pretty cool, maybe for significant editors. Cyb3rstarzzz (talk) 10:09, 14 June 2024 (UTC)[reply]

    Hall of fame topic; section break 1

    Hall of fame topic; section break 2

    Hall of fame topic; section break 3

    I don't much like anything on Wikipedia which encourages elitism, political campaigns, cliques, inequality, etc. I can imagine that many wiki-politicians would waste a lot of time campaigning to be elected to a HOF and that the results would be divisive. "How come so-and-so got elected, and I didn't?" Smallchief (talk) 21:44, 12 April 2024 (UTC)[reply]

    section break 4; [wikilounge idea]

    Section break 5

    Many such award schemes have been previously proposed. Only two, to my knowledge, still function: WP:QAI, because of the dedication of one editor, and WP:EOTW. If you want another one, set it up and run it yourself—if people like it, you can then apply to formalize it as a Wikipedia-wide process. ~~ AirshipJungleman29 (talk) 12:13, 26 April 2024 (UTC)[reply]
    Anyway, the Service Awards are good because they are purely mechanical and entirely removed from politics. Entirely: If you're banned, you qualify. If everyone hates you, you qualify. If you drove your car up the steps and into the door of the Wikimedia Foundation offices on purpose, you qualify. Also, you continue to accrue service time -- which is measured from the date of your first edit, and does not take into account gaps -- after you're dead. So, if service time is the limiting factor for you, you will progress up the levels even after your demise, and I know of one editor who is. So... Maybe our Hall of Fame could be only for deceased editors. After all, you have to be dead five years before you're eligible for the baseball Hall of Fame. Then I think most people would be "Oh its nice to remember Smith" and not upset about the politics. My 2c. Herostratus (talk) 02:53, 28 May 2024 (UTC)[reply]

    How about a Hall of Shame?

    I know generally we are a bit negative especially when it comes to disruption, which is why we generally note previous hurdles as a cautionary tale of what not to repeat. A reminder everyone is human. A hall of fame will make editors more concerned with scoring brownie points than actually improving the project. Awesome Aasim 20:29, 7 May 2024 (UTC)[reply]

    We already have Wikipedia:STOCKS, more than this would actually be more harmful than it might help. Chaotıċ Enby (talk · contribs) 20:33, 7 May 2024 (UTC)[reply]
    Yeah I know. I was just thinking about why we have a hall of shame but not a hall of fame. Awesome Aasim 00:05, 8 May 2024 (UTC)[reply]
    The stocks aren't a hall of shame, it's a humourous list of mistakes. -- LCU ActivelyDisinterested «@» °∆t° 21:04, 9 May 2024 (UTC)[reply]
    Awesome Aasim, isn't WP:Long term abuse already kind of that? — 🌙Eclipse (talk) (contribs) 14:49, 18 May 2024 (UTC)[reply]
    That page should not really be intended to be a 'hall of shame' due to WP:DENY and WP:BEANS (none of which apply to the village stocks in comparison). Xeroctic (talk) 19:33, 20 May 2024 (UTC)[reply]

    Wealready have a hall of shame. Just Step Sideways from this world ..... today 17:40, 26 May 2024 (UTC)[reply]

    An idea that might work: A Wikipedia statue

    In place of the Hall of Fame, which doesn't seem to be going anywhere, how about this: Wikipedians can request that the Foundation agree to raise funds for and construct a Wikipedia statue featuring Jimbo Wales, Larry Sanger, and a stylized rendition of Wikipedia and Wikipedians enlarged and forever enlarging behind them (with, of course, the incomplete-globe logo somewhere in the mix). This should be a major statue, not a small standing one, and incorporate the full quality and historical significance of the encyclopedia.

    Wales and Sanger should have no veto in the idea of their inclusion in the statue but both probably should have input on the final design of their figures portrayed at the time of Wikipedia's founding. Many of the world's major sculptors should either compete for the final design or submit ideas for it. If done well, with a full mix of realism and modern art, it would be beautiful, educational, and honor the two initiators, the tens of thousands of volunteers, and the concept of knowledge itself. Randy Kryn (talk) 00:25, 10 June 2024 (UTC)[reply]

    Would sound good to me, though I fear that some may think it's spending they should focus on technical debt, which may or may not be valid. Aaron Liu (talk) 01:24, 10 June 2024 (UTC)[reply]
    Thanks Aaron. It feels like a reasonable idea, the community asking the Foundation to do something like this. As for expense, focused fundraising works. Major funders, both former and potential, often like to focus their money on specific goals. Some may delight in funding the expansion of tech, others would appreciate the chance to fund an artwok, some might be glad to fund a full evening Wikibanquet as well as add more scholarships to the regional conferences. A large well-done statue (and please also appreciate the Wikipedia Monument) dedicated to the free sharing of knowledge would catch the eye of some art loving major funders, so that shouldn't be an issue. If I was a tech giant it'd be funded already. Imagine the design proposals that would come in. Randy Kryn (talk) 03:25, 10 June 2024 (UTC)[reply]
    Simpsons did it. Just Step Sideways from this world ..... today 20:07, 10 June 2024 (UTC)[reply]
    A true Wikipedia statue should be a big framework sphere like this but with the design of the Wikipedia globe logo, and made of little shelves. The public to be encouraged to climb all over it and place (and remove) items of their choosing on the shelves. A webcam to make it a live-streaming sensation. Activate the fountains below to hose it down regularly. Barnards.tar.gz (talk) 21:10, 10 June 2024 (UTC)[reply]
    Guy brings Vitamin C effervescent tablets Aaron Liu (talk) 11:56, 11 June 2024 (UTC)[reply]
    An interesting idea, if one drops the silliness of including Sanger. The man had as much input into the founding of this as Ronald Wayne did for Apple. That is, hardly a thing. Zaathras (talk) 00:13, 11 June 2024 (UTC)[reply]

    Allowing Master's theses when not used to dispute more reliable sources

    WP:SCHOLARSHIP generally allows PhD dissertations and generally disallows Master's theses, unless they have had "significant scholarly influence." I feel that this is really locking us out from a lot of very reliable sourcing. I understand that these are often not quite as polished as something like a monograph or PhD dissertation, but often times they are the highest quality sources available about very niche subject matters. They are subject to professional review, they cite their sources, and they are published by reliable institutions. Can we really say that these are less reliable than an entry in a historical society newsletter or an online news report from an assuredly hurried local journalist?

    Just today I encountered a 2022 masters thesis, East Meets West in Cheeloo University (doi:10.7916/scmr-6237). As far as I can tell, this is the most comprehensive source available on the architecture of Cheeloo University. But I can't use it, since it's a masters thesis, and as far as Google Scholar can tell, it has yet to be cited elsewhere.

    I feel that people should be allowed to use masters theses in certain fields (I can only speak for the humanities, I'd be interested to know this from a STEM perspective) so long as A) They are not used to dispute something said in reliable sources and B) They are not used to confer notability. I feel this would strike a good balance of allowing us to use these often very useful sources, while still recognizing that a book, journal article, or PhD thesis is probably preferable if you have the choice between them. I'd love to hear other folks thoughts! Generalissima (talk) (it/she) 00:43, 7 May 2024 (UTC)[reply]

    In the stem area I would expect that important research would also be published in journals. I would discourage use of Masters theses rather than disallow. One issue is lack of accessability. Even when referenced, may not be accessible. The lack of "peer" review can also mean there are more errors included. Graeme Bartlett (talk) 02:03, 7 May 2024 (UTC)[reply]
    Is there any public information generally available about the process of publishing masters' theses for a given university? What level of scrutiny or review is generally applied, etc. I think considering whatever information is available there could lend a lot of clarity to deciding whether a given thesis is reliable. Remsense 02:09, 7 May 2024 (UTC)[reply]
    Theses are a mixed bag. Master's thesis even more so. I can say that mine went through a rigorous review process (I had a former president of the Canadian Association of Physicists as an external examiner on mine) as well as one other physics PhD, and had two physics PhD as my supervisors. The comments/feedback were substantive and relevant, and had to be addressed before acceptance.
    But go to a different department, in the same university, and the reviewing standards and requirements for a master's thesis are quite different. Headbomb {t · c · p · b} 21:34, 9 May 2024 (UTC)[reply]
    As Visviva said above, if people treat the guideline like a policy that "no masters theses can be cited for anything (or they can only be cited if lots of other people cite and repeat what they say, making it unnecessary to cite them), because we assume no masters thesis has ever been reviewed and made reliable; meanwhile, PhD theses are reliable because we're assuming every one has been reviewed by reviewers who know what they were doing", that's a problem (in fact, it's two problems separated by a semicolon). I think it would make more sense, as Visviva seems to be suggesting, to apply the same kinds of evaluative criteria as are supposed to be applied to PhD theses to both PhD and Masters theses, plus OP's suggestion that we don't use them to contradict a more reliable source; together with the fact that tighter sourcing requirements are already in effect for BLPs, medical topics, and various contentious topics, we'd in practice only cite masters theses when there was reason to think they were reliable for the uncontentious thing we were citing them for, e.g. the architecture of a particular university, which seems reasonable. (As WhatamIdoing said, if we'd accept a passing aside in blog post by the university as reliable for saying the buildings were neoclassical, it seems weird to reject a masters thesis all about the buildings being neoclassical.) Notability seems like a separate issue and it seems reasonable to say masters theses also don't impart much notability. -sche (talk) 00:48, 19 May 2024 (UTC)[reply]
    I've used and seen used master's theses in articles, and agree with a lot of the people here. I'm not sure which if any academic departments fully fact check every claim in the master's theses they go on to approve, but the same is true for most publication media. My position can be summarised as Use cautiously and replace with better source where possible.
    Also, honestly, have yall seen what's out there in the wild in mainspace? The people who frequent this board tend to be responsible editors, and take our sourcing pretty seriously, but the amount of truly garbage sources cited like they're totally unproblematic is deafening. A master's thesis, despite the potential flaws, is head and shoulders above a blog post, a self-published book, a blog post someone uploaded to academia.edu, a google books search result, ViralFinance.info's "Top 150 Most Disuptive Blockchainers of 2019", an Amazon product listing, a 1930s travellogue published by a popular printing house but cited like it's a legitimate historical source for a period centuries prior, literature that's long been superseded by newer research that's more difficult to access than one-click borrowing from Internet Archive, etc.
    Sorry I kinda lost the trail there. In most cases, a master's thesis will not be the best source. But I don't think we need to (nor, indeed, do) straitjacket ourselves with a blanket ban if no one else has bothered to publish on some obscuratum that would improve an article to include. Folly Mox (talk) 20:52, 16 June 2024 (UTC)[reply]
    Almost completely unrelated, but if we had something like a Reference: namespace, we could attach things like levels of confidence in a source, and represent that somehow to the reader, like changing the little blue clicky numbers from blue to orange for sources that are not too tier. Folly Mox (talk) 20:58, 16 June 2024 (UTC)[reply]
    @Folly Mox yes! This is something meta:WikiCite/Shared Citations could address ~ 🦝 Shushugah (he/him • talk) 22:32, 18 June 2024 (UTC)[reply]
    I see I somehow haven't registered my written support for that project, despite being aware of it for a year or so. I see the allure of wanting to make a big software architecture like that work all across the Wikimedia ecosystem, and have concerns about how it would translate technically into different spaces, ✂️ [three paragraphs of yelling at clouds trimmed and binned] Folly Mox (talk) 04:14, 19 June 2024 (UTC)[reply]
    User:SuperHamster/CiteUnseen adds icons according to RSP. Aaron Liu (talk) 02:16, 19 June 2024 (UTC)[reply]
    Oh right there is that, and WP:UPSD and User:Novem Linguae/Scripts/CiteHighlighter also provide borderline similar functionality. Folly Mox (talk) 04:04, 19 June 2024 (UTC)[reply]

    Make the edit request facility optional

    An uncontroversial, "change X to Y" request can be done just as easily using a normal discussion thread. The edit request facility exists for low-activity protected articles where there is a need to summon an editor to handle the request; otherwise the request could sit unseen or ignored for years. In my experience, edit request is used far more often for changes that are not uncontroversial, and/or are not in the required "change X to Y" format. This is because users don't take the time to read the instructions presented to them in the request path.

    It should be possible to turn off the edit request facility at articles where it isn't needed; i.e., articles that always have editors around. In such cases the edit request path could be replaced by instructions directing the user to the talk page (or saving them a step and presenting the same thing they would get by clicking "New section" at the talk page). ―Mandruss  22:31, 21 May 2024 (UTC)[reply]

    Well it is already optional and editors do make requests in text only. The template makes it formal and encourages identifying the exact change, although often not used correctly. Graeme Bartlett (talk) 22:52, 21 May 2024 (UTC)[reply]
    The use is optional; the facility is not. Again in my experience, editors are spending too much time rejecting "invalid" edit requests (which also wastes the requester's time).
    The facility summons an outside editor by placing the article in a maintenance category for that purpose. In my 10+ years at normal-activity articles, I've yet to see a request handled by such an outside editor. Rather, the request is invariably changed to answered=y by a "local" editor, removing the article from the category, before an outside editor arrives to handle it. So, for a normal-activity article, what's the point of the category or the facility? ―Mandruss  23:26, 21 May 2024 (UTC)[reply]
    Not every request-reviewer is that lazy. Quite a bit will engage in discussion. Aaron Liu (talk) 23:29, 21 May 2024 (UTC)[reply]
    And they will do so improperly, all the more reason to turn off edit requests. The edit request instructions are quite clear: "What an edit request IS NOT for: [...] making a comment or starting a discussion: go to the talk page [...]". Again, if discussion is the goal, there is already a way to do that. ―Mandruss  23:55, 21 May 2024 (UTC)[reply]
    Hmm. But should people new to a topic carry the burden of assessing whether a talk page is active? Aaron Liu (talk) 01:24, 22 May 2024 (UTC)[reply]
    I don't understand the question. If you're referring to the requesters, they wouldn't have to make that assessment. It would have already been made by the article's editors (or not). For example, the editors at Donald Trump would turn off the edit request facility and any user clicking "View source" on the article page would be directed to the talk page (or, as I said, the box would be presented to start a discussion thread). More precisely, they would be presented the option to start a discussion thread, just as they're presented the option to submit an edit request today (big blue button).
    And, again, if they don't seek discussion—if they have something clearly uncontroversial—a normal thread works equally well for that purpose. Heading: "Typo correction". Comment: "Please correct the spelling of 'envirmental' in the 'Climate change, environment, and energy' section. ~~~~". Done. The only material differences are (1) a more meaningful section heading, hopefully, (2) no need to change to answered=y, and (3) no maintenance category pointlessly involved. ―Mandruss  02:15, 22 May 2024 (UTC)[reply]
    Then just add the edit notice for articles where all edits will be controversial. I don't see why we should remove the ER facility, which is still perfectly good for uncontroversial edits. I don't see why editors already being available is a problem. Aaron Liu (talk) 11:31, 22 May 2024 (UTC)[reply]
    @Mandruss: The facility summons an outside editor by placing the article in a maintenance category for that purpose. In my 10+ years at normal-activity articles, I've yet to see a request handled by such an outside editor. Can you please clarify what you mean by this. Many volunteers watch CAT:ESP and related pages and handle requests. RudolfRed (talk) 02:45, 22 May 2024 (UTC)[reply]
    @RudolfRed: I'm sure they do, but I've never seen them handle one at an article that always has editors around to handle it. Not once in 10+ years. They simply can't get there fast enough, presumably because they are processing a FIFO queue containing a number of older requests. Even if they could, why bother them when they aren't needed? They have many requests to handle where they are needed. ―Mandruss  02:56, 22 May 2024 (UTC)[reply]
    There's a lot of high traffic articles here. In my experience handling well over 10,000 edit requests and patrolling all of the edit request queues, edit requests are often ignored by the regulars on well attended talk pages, and edit request patrollers handle requests on those articles very often. ScottishFinnishRadish (talk) 02:36, 25 May 2024 (UTC)[reply]
    Great. Then those articles would not turn off the edit request facility. Hence "optional". ―Mandruss  04:30, 25 May 2024 (UTC)[reply]
    Pages that are protected are normally of interest to many editors. So hopefully they are on watchlists. Also I expect that admins the protect, add the page to their watchlist so they can see any requests or edits. Graeme Bartlett (talk) 22:39, 23 May 2024 (UTC)[reply]
    That reads like an argument for eliminating the edit request facility entirely, which would be a step too far in my opinion. It's certainly not an argument against making the facility optional at article level. ―Mandruss  01:10, 24 May 2024 (UTC)[reply]
    And the argument is very wrong too. There are plenty of obscure protected pages. High-risk templates. MediaWiki-namespace pages. Gadgets like MediaWiki talk:Gadget-watchlist-notice-core.js, where even the edit request template itself has failed for two months. * Pppery * it has begun... 04:04, 24 May 2024 (UTC)[reply]
    I implemented this a while ago per Wikipedia:Administrators' noticeboard/Archive334#Possible new tool/technique/procedureas{{Manual edit requests}}. It never got used then because the person who was advocating for it retired due to unrelated drama shortly after that discussion. * Pppery * it has begun... 04:04, 24 May 2024 (UTC)[reply]
    I still don't see why editors being already available is a problem. Aaron Liu (talk) 11:29, 24 May 2024 (UTC)[reply]
    You're choosing to frame this in a greatly oversimplified way that ignores points already made. I hate circular/repetitive discussion, and I suggest a re-read with more effort to see a different perspective. ―Mandruss  02:27, 25 May 2024 (UTC)[reply]
    Bump. It's been said, not by me, that Idea Lab is where good ideas go to die. ―Mandruss  21:48, 5 June 2024 (UTC)[reply]
    Even if that's true, I don't think the precondition is met for this one.
    Suppressing the normal edit request mechanism IMO should only be done for pages where it makes it too easy for confused users to make completely misplaced edit requests (e.g. all the people who used to wind up at Template talk:Reflist trying to add references to some particular article, or Help talk:Edit summary trying to add a summary to their edit). If people are using it to make appropriate requests, even if malformed and even if the article always has editors around, then it's not a problem. Especially in the "always has editors around" case, those editors can handle it.
    Above you complain about Rather, the request is invariably changed to answered=y by a "local" editor, removing the article from the category, before an outside editor arrives to handle it, which IMO is the mechanism working as intended: an editor answers the request and sets answered=y. Just because that happens to be an editor who'd have seen it anyway because they watch the page is not a "problem" that needs fixing. Anomie 11:22, 6 June 2024 (UTC)[reply]
    The point is that, where there is no need to summon someone via the category, there is no need for the facility. That's it. In my nine years at the perpetually-protected Trump article, perhaps one in twenty edit requests have resulted in an edit to the article—and it could have been done using a normal thread. The other nineteen have been malformed, controversial, attempts to start discussion, or requests for permission to edit the article directly. That is a distracting waste of resources too easily avoided. ―Mandruss  12:12, 6 June 2024 (UTC)[reply]
    It's not that I don't understand your point. It's that I disagree that removing the edit request pre-fill would make things better, outside of your own personal annoyance at seeing the edit request template. You or other editors on the page are free to retitle sections and mark the "bad" request as answered when you answer them. Anomie 12:46, 6 June 2024 (UTC)[reply]
    Well, I think you do misunderstand my point, unless you're saying that the distracting waste of resources is acceptable. If that's the case, I invite you to come spend a few weeks at the Trump article; might change your perspective. We have more important things to do, and not enough time to do them. ―Mandruss  12:52, 6 June 2024 (UTC)[reply]
    On second thought, it's not a good time for your visit. The article talk page has been temporarily semi-protected due to vandalism related to the conviction, and I think that's preventing edit requests. ―Mandruss  13:13, 6 June 2024 (UTC)[reply]
    Sorry, I can't stand Trump. Anomie 00:49, 7 June 2024 (UTC)[reply]
    I might be misunderstanding the proposal; currently I'm interpreting it as "disable the ability to create edit requests on controversial pages/pages with lots of watchers". If that's the case: last year, I made an edit request to the List of Conspiracy Theories article, which is unsurprisingly a controversial article and has over a thousand talk page watchers. By your criteria, I'm pretty sure edit requests would have been disabled. As it was, it took 23 days for anyone to bother to respond, during which time (if my memory's correct) it became the 12th-most-stale edit request on the entire site. ...had your proposal been in place, and had my request been forced to have been opened as a normal thread, it would have vanished into the void and would still be unanswered today. Because surprise surprise, the ultimate responder found it through the Edit Request Tool, not from watching the talk page. 2603:8001:4542:28FB:BC84:B937:5E69:2838 (talk) 14:42, 7 June 2024 (UTC) (Send talk messages here)[reply]
    That's the general gist I saw when I was I patrolled edit requests. ScottishFinnishRadish (talk) 14:45, 7 June 2024 (UTC)[reply]
    The proposal is to give an article's editors the power to turn off the edit request facility if they judge that it's doing more harm than good at that article. The test is not an arbitrary one based on # of watchers or anything else. Are you suggesting that decision would be made at List of conspiracy theories? Made on what basis?
    Regardless, it's not like the decision is irreversible. If your normal thread sat unanswered for a long time, would that not be a clear reason to turn the facility back on? If your edit request went unanswered for 23 days, how is that an argument against this proposal? ―Mandruss  18:27, 7 June 2024 (UTC)[reply]
    I'm just not seeing what it really does. The template attracts the patrollers. If they close an edit request it doesn't mean that the watchers of that particular article can't action or respond to the request in any way they see fit. ScottishFinnishRadish (talk) 18:30, 7 June 2024 (UTC)[reply]
    If I've failed to make the point about "distracting waste of resources", I guess there's nothing else I can say. ―Mandruss  18:40, 7 June 2024 (UTC)[reply]
    What you call waste, we call extremely effective redundancy. Aaron Liu (talk) 18:48, 7 June 2024 (UTC)[reply]
    Perhaps I'm misreading, but it is unclear what resources are being wasted (server kittens?) or that anyone is distracted. One of two things is true. Either the request is answered by someone who is patrolling the categories for edit requests, in which case the system functioned as expected. Or the request is answered by a talk page watcher, in which case the proposed change would make no difference except perhaps cosmetically due to a different template. I suppose there is the tiniest chance that a patroller inspects a request at the precise instant a talk page watcher answers it and edit conflicts, but the benefit of eliminating an extremely rare occurrence is more than outweighed by the extra complications entailed by the proposed change. 184.152.68.190 (talk) 04:49, 10 June 2024 (UTC)[reply]
    I doubt that new users would be able to know how to request turning the facility back on, nor if there were a facility because it was turned off. Aaron Liu (talk) 18:49, 7 June 2024 (UTC)[reply]

    Proposed revision of the COI guideline

    Our current Conflict of Interest guideline is 6000 words - or 0.2 tomats - long, and often ambiguous and confusing. To address this we have recently been discussing at WP:COI a replacement, and I'm opening a discussion here to get further input on it now that it has gone through a few rounds of revisions.

    It is considerably shorter than the current guideline, at just 1000 words, and is intended to be clearer about what restrictions apply to which editors. The intention is that it would replace the current COI guideline; the current text would be moved to an explanatory supplement where it could be edited and pruned as appropriate. BilledMammal (talk) 18:06, 23 May 2024 (UTC)[reply]

    Draft of the proposed guideline

    To preserve the integrity, neutrality, and public trust in Wikipedia, it is crucial to effectively manage conflicts of interest among editors. A conflict of interest arises when an editor's personal, professional, or financial connections might compromise the objectivity of their contributions. This guideline outlines the types of conflicts and specifies the conduct required for editors who may be affected by them.

    Financial Conflict of Interest

    An editor has a financial conflict of interest when they stand to gain, or can reasonably be expected to gain, financial benefits from the coverage of a topic on Wikipedia. This conflict arises in various forms:

    • Direct Financial Benefits: These include receiving direct payment for editing Wikipedia articles.
    • Indirect Financial Benefits: Such benefits are not as overt as direct payments but are significant. Examples include:
      • Business Exposure: Gaining from increased visibility when a product, service, or company is featured in an article. For example, an editor who is a major shareholder or partner in a business could materially benefit from increased sales due to enhanced visibility of their product on Wikipedia. Conversely, an individual who holds a inconsequential stake, such as a small fraction of a percent of shares in a publicly traded company, would not be positioned to experience noticeable financial gains from such coverage.
      • Reputation Enhancement: Benefiting indirectly from an enhanced reputation due to having a personal article on Wikipedia or being prominently featured as an expert. This can lead to increased professional opportunities, such as book sales, speaking engagements, or consultancy work.

    Non-financial Conflict of Interest

    An editor has a non-financial conflict of interest when their personal or professional connections may compromise their ability to present a subject objectively. This type of conflict arises in various forms:

    • Personal Relationships: Editing articles about friends, colleagues, family members, romantic partners, or personal adversaries can lead to biased content, whether overly favorable or unduly negative.
    • Professional Connections: Editing articles related to one's employer or competitors in the industry can introduce biases that may either unfairly promote one’s own organization or undermine others. Similarly, citing oneself or ones close acquaintances as sources can introduce bias, influencing the content to unduly favor personal or professional interests.
    • Significant Roles: Editing articles related to organizations in which an individual holds a significant role, or recently held a significant role, may introduce biases and a lack of objectivity in content related to the organization's interests. This is a spectrum, with whether an editor has a conflict of interest depending both on the level of authority or influence their role granted them, and the recency of the role. For example:
      • A general volunteer for the Democratic Party would have no conflict of interest.
      • Aprecinct captain for the Democratic Party would have a conflict of interest for a few years after they hold the role.
      • Apresidential elector for the Democratic Party would permanently have a conflict of interest.

    Managing Conflicts

    • Editors with a Financial Conflict: Must not directly edit affected articles. Instead, they should propose changes using the Edit COI template, disclosing the nature of their conflict on their user page and in any location they discuss the topic.
    • Editors with Non-financial Conflicts: While not strictly forbidden from directly editing affected articles, transparency is required; they must disclose their conflict in the edit summary and in any location they discuss the topic.

    Exceptions

    Aside from those explicitly listed here, no exceptions exist to this guideline; edits must abide by it regardless of their perceived harmlessness or quality. Editors who wish to avoid disclosing their conflict of interest may do so only be avoiding topics affected by it.

    General exceptions

    1. Reverting obvious vandalism—edits that any well-intentioned user would agree constitute vandalism, such as page blanking and adding offensive language.
    2. Removal of clear copyright violations or content that unquestionably violates the non-free content policy (NFCC). What counts as exempt under NFCC can be controversial, and should be established as a violation first. Consider opening a deletion discussion at Wikipedia:Files for discussion instead of relying on this exemption.
    3. Removal of content that is clearly illegal under U.S. law, such as child pornography and links to pirated software.
    4. Removing contentious material that is libelous, biased, unsourced, or poorly sourced according to Wikipedia's biographies of living persons (BLP) policy. What counts as exempt under BLP can be controversial. Consider reporting to the BLP noticeboard instead of relying on this exemption.
    5. Reverting unambiguous spam, where the content would be eligible for page deletion under criterion G11 if it were a standalone page.

    Wikipedians in residence

    A Wikimedian in Residence (WIR) is a professional role in communications for an organization to share its knowledge within the Wikimedia platform, measure the impact of the same, and promote Wikipedia through training, education, and edit-a-thons. While WIRs can greatly benefit Wikipedia, there is a risk of edits that could unduly benefit their employers. To manage this risk, the following guidelines apply:

    • Scope of Editing: WIRs may edit articles related to but not directly involving their institution. They must not edit articles where their institution is the primary subject or could reasonably be seen as directly benefiting from the article's content; if they wish to make changes to such articles they must follow the instructions at #Managing Conflicts for Editors with a Financial Conflict.
    • Disclosure Requirements: WIRs must clearly disclose their role and association with their institution on their user page, as well as in any discussions or edits related to their role as a WIR

    Reporting suspected violations

    When violations of this policy are suspected or identified it is crucial to address them with transparency and caution, balancing protecting the encyclopedia with respect for the editors involved. Always adhere strictly to our no-outing policy; only post personal information if the editor has disclosed it on Wikipedia.

    • User talk page: Non-urgent issues can be raised on the editor's talk page, using the COI warning template as appropriate.
    • COI noticeboard: If issues remain unresolved after user talk page discussions, or if the user talk page is an unsuitable venue, escalate the matter to the Conflict of Interest Noticeboard. This noticeboard also provides guidance for editors dealing with their own conflicts.
    • Private communication: For issues requiring confidentiality, including where posting the information on Wikipedia would violate our policies on the posting of personal information, email evidence to the appropriate channels: for general COI issues, contact functionaries-en@lists.wikimedia.org, and for paid editing concerns, reach out to paid-en-wp@wikipedia.org. Always consult these channels for advice before sending private information.

    Discussion

    Any way to internationalise the bit under Significant roles? A "precinct captain for the Democratic Party" doesn't really map intuitively onto anything in my experience, and others may feel similarly. Folly Mox (talk) 20:41, 23 May 2024 (UTC)[reply]
    I tried to think of a few as I didn't consider it ideal either, but I couldn't think of anything more recognizable. If you have any ideas I would be glad to change them. BilledMammal (talk) 00:08, 24 May 2024 (UTC)[reply]
    Having a conflict of interest should NOT bar anyone from editing as long as their edits are in accordance with our content policies and guidelines. Even a paid editor is not problematic UNLESS they are editing in a way that is contrary to our p&g.
    I agree that it IS all too easy to (even unintentionally) edit in a way that is contrary to p&g when you have a tie to the topic… and so I agree with requiring disclosure. After all, when you disclose, others can better guide you when you unintentionally edit in a problematic way. BUT… those with a conflict CAN edit properly with such guidance.
    The flaw isn’t in having a conflict of interest… the flaw is in allowing that conflict to impact one’s editing. And THAT is resolved by addressing the edits, not the editor. Blueboar (talk) 22:36, 23 May 2024 (UTC)[reply]
    I agree that the flaw is in allowing the conflict to impact one's editing. However, I don't believe it's useful to focus on the edits within the conflict of interest guideline. All edits are held to the same standard: they are proper if they align with our content policies and guidelines, and improper if they don't.
    Instead, we should recognize that editors with a conflict of interest can make significant positive contributions but also face an increased risk of making problematic edits - especially ones that are difficult to detect and address. Our goal should be to minimize this risk without hindering those positive contributions, and we can achieve this through two complementary processes: providing additional guidance to editors with a conflict of interest and subjecting their edits to greater scrutiny.
    A conflict of interest guideline that focuses on the editor, promoting transparency and disclosure, supports these processes, and allows us to better manage the risk. BilledMammal (talk) 00:08, 24 May 2024 (UTC)[reply]
    I agree with Blueboar, the only thing that matters is the edits. Everything that isn't directly supporting the inclusion of good edits and the exclusion of bad edits, regardless of source, is irrelevant. The significant majority of this proposal is focusing on completely the wrong thing. Thryduulf (talk) 21:34, 24 May 2024 (UTC)[reply]
    @Blueboar and @Thryduulf, can't the same thing be said about the existing COI guideline? Is this really "taking us" somewhere new, or is it "keeping us exactly where we have been since 2012"?
    Related to the comment from @Curbon7, I think the most recent major change was when Gigs and SlimVirgin largely re-wrote COI in 2012. If memory serves, the goal was to make COI focus on the editor instead of the edit, because real-world definitions (e.g., for corporate board malfeasance) focus on the individual actors instead of the actions. For example, if a non-profit board member owns an office building, and offers to rent badly needed office space to the non-profit at a massive discount, he can theoretically get in COI trouble for voting to accept his offer, even if that's clearly the best possible thing for the organization. WhatamIdoing (talk) 06:17, 25 May 2024 (UTC)[reply]
    Wikipedia's COI policies don't ban those with a COI from editing. However, they do require you to:
    1. Disclose that COI
    2. Keep any bias in check
    3. Involve other editors to verify all edits are unbiased
    4. Avoid letting your voice "dominate" any articles on the topic.
    The editor matters because we don't have perfect information. If a rando gives a citation for "Bob the scientist says X", it's reasonable to include this in an article, and I won't give it much thought. However, it's possible Bob's view falls outside the mainstream; to determine that, I'd need to learn all about X. I can't do this for every possible X, so I take a shortcut: if a COI editor who would benefit from X writes this edit, I make sure to be extra-careful when reviewing the edit. –Sincerely, A Lime 20:17, 9 June 2024 (UTC)[reply]

    Worth the effort; there are many problems caused by the current guideline. North8000 (talk) 13:43, 4 June 2024 (UTC)[reply]

    Ready for the mainspace

    I'm here to solicit opinions about what it means for an article to be "ready for the mainspace". This phrase has turned up in hundreds of AFDs during recent years. Here's the story:

    You are looking at an article. You have determined that the subject is notable, and that none of the Wikipedia:Criteria for speedy deletion apply to the article. Another editor says to you: "I don't think that article is ready for the mainspace".

    What would you guess that the editor means? Is that consistent with our rules, such as the WP:NEXIST guideline or the WP:IMPERFECT policy? WhatamIdoing (talk) 19:32, 28 May 2024 (UTC)[reply]

    Personally, and this is just my own opinion here, I find this "ready for the mainspace" thing a little ambiguous. As you said, as long as WP:GNG is met, an article that is properly sourced (or at least whose topic does) deserves to be in the mainspace. Not all articles are perfect, and by having an article in the mainspace, more people will see it and improve it, which is exactly the purpose of Wikipedia. It's a work in progress!Cocobb8 (💬 talk • ✏️ contribs) 19:45, 28 May 2024 (UTC)[reply]
    I think it's a little ambiguous, too, which is why I'm asking. ;-) WhatamIdoing (talk) 20:14, 28 May 2024 (UTC)[reply]
    However, WP:DRAFTIFY clearly states that the aim of moving an article to draft is to allow time and space for the draft's improvement until it is ready for mainspace, so maybe a change to that guideline could be required to make it clearer? Cocobb8 (💬 talk • ✏️ contribs) 20:17, 28 May 2024 (UTC)[reply]
    If we can figure out what it means, that might be helpful. WhatamIdoing (talk) 20:32, 28 May 2024 (UTC)[reply]
    I would generally interpret it as "WP:N has not been shown." Gråbergs Gråa Sång (talk) 19:53, 28 May 2024 (UTC)[reply]
    Then what about you have determined that the subject is notable per @WhatamIdoing's original comment? Cocobb8 (💬 talk • ✏️ contribs) 20:02, 28 May 2024 (UTC)[reply]
    If I couldn't see for myself why the other editor would say that, I'd ask. For myself, I could see saying "not ready for mainspace" for something so poorly or inappropriately written that it does a disservice to the topic and the reader (although I'd probably say specifically what my concern was). Schazjmd (talk) 20:12, 28 May 2024 (UTC)[reply]
    Wikipedia:Drafts#During new page review says that it's enough that the topic is plausibly notable to draftify. An unsourced article with a claim of significance (or notability) could fit this description, not being eligible for WP:A7 but still not meeting the referencing standards for mainspace. Chaotic Enby (talk · contribs) 20:34, 28 May 2024 (UTC)[reply]
    In my opinion, if the article draft meets all of the following it's ready for mainspace:
    • Is not being discussed at XfD
    • Would not meet a speedy deletion criterion in article space
    • Has no identified copyright, BLP, etc issues
    • Has sufficient sources to demonstrate notability
    • Has been at least minimally proof-read (perfection is not required, basic readability is).
    • Has no in-line editing notes ("need to reword this", "add more info here", etc) (excluding templates and hidden comments).
    • Has no obviously broken templates (if you don't know how to fix it, ask for help before moving). Thryduulf (talk) 21:22, 28 May 2024 (UTC) ("article" changed to "draft" for clarity Thryduulf (talk) 23:20, 28 May 2024 (UTC))[reply]
    I'm not sure why you're asking in this venue. The only way to know is to ask the editor making the statement what they meant. Even if it could be done, I don't think it will be helpful to try to establish a common interpretation. Editors should be specific about their concerns. isaacl (talk) 22:15, 28 May 2024 (UTC)[reply]
    It's difficult to ask hundreds of editors. Also, if everyone has their own ideas, then the phrase becomes useless. We might as well just say WP:IDONTLIKEIT in that case. WhatamIdoing (talk) 22:29, 28 May 2024 (UTC)[reply]
    The phrase is useless on its own, as it's not specific. It sounds more like you want to revisit the criteria for deleting an article, to examine what should be considered showstopping shortcomings. Commenters in deletion discussions should be encouraged to list those shortcomings. They can optionally add that as a result, the article isn't ready for the mainspace. isaacl (talk) 22:48, 28 May 2024 (UTC)[reply]
    I do not want to revisit the criteria for deleting an article. Also, if you take a look, this phrase frequently is given as a reason for not deleting the articles (but instead moving them to Draft: or User: space).
    Consider Wikipedia:Deletion policy#Deletion of drafts: "If an article isn't ready for the main namespace, it can be moved to the draft namespace". Commenters in deletion discussions can listed specific shortcomings, but the deletion policy itself can't. Is this a matter of pure consensus, in which case it's nearly indistinguishable from IDONTLIKEIT (which sounds worse than it probably would be in practice)? Does it mean, e.g., what @Thryduulf said about "Has sufficient sources to demonstrate notability", in which case WP:NEXIST is no longer valid? Would a visibly broken template count as the sort of IMPERFECT thing that the deletion policy won't countenance? WhatamIdoing (talk) 23:09, 28 May 2024 (UTC)[reply]
    To be clear, my criteria are for moving a page from draft space to article space, not for moving a page in the other direction (where such issues as broken templates should simply be fixed). Thryduulf (talk) 23:18, 28 May 2024 (UTC)[reply]
    Articles don't avoid deletion to be moved to draftspace simply because they're not ready for mainspace by someone's measure, but because someone thinks there's promise to demonstrate that the topic meets English Wikipedia's standard for having an article. There's no point in trying to retroactively figure out what others have meant by a non-specific phrase they used in the past. Moving forward, users should be asked to provide specific details, assuming that it's not already clear from context what shortcomings are being considered.
    Regarding the quote from the deletion policy, I agree that ideally it wouldn't use a vague phrase. I appreciate, though, that the sentence is trying to be a placeholder to cover any scenario where the participants in a deletion discussion agreed that the best course of action was to move the article to the draft namespace. It's essentially tautological. isaacl (talk) 00:05, 29 May 2024 (UTC)[reply]
    If it means "by consensus at AFD", then it should say that. We could change the deletion policy to say that.
    In re no point in trying to retroactively figure out what others have meant by a non-specific phrase they used in the past, I don't agree. This phrase seems to mean something to people. You are the only editor who thinks that understanding what we want to communicate (in about a thousand AFDs, in the deletion policy, twice in Wikipedia:Drafts, in more than forty thousand pages all told). When a bit of wiki-jargon has been used tens of thousands(!) of times, I don't think that figuring out what we mean, and whether we all mean the same thing, is pointless. If it doesn't interest you, then that's fine, but please don't tell other editors that what they've been saying is meaningless.
    Also, I suspect that in a substantial fraction of cases, "not ready for mainspace by someone's personal standards" is exactly what is meant. WhatamIdoing (talk) 02:10, 29 May 2024 (UTC)[reply]
    To clarify, I mean from my view, there's no point in trying to guess at the meaning in a village pump thread. If we're serious about trying to figure it out, we should be systematic: take a sampling and ask the editors in question if they're still around. We can also analyze the discussion threads to see if there is enough context to understand. isaacl (talk) 05:05, 29 May 2024 (UTC)[reply]
    This phrase is used in WP:DELPOL and WP:DRAFTIFY. The village pump is the normal place to discuss confusion that affects multiple policy/guideline/help/etc. pages.
    But I'm no longer hopeful that we can have that discussion. If you look at this thread, five editors thought they had something useful to contribute. Then you started posting that you thought it was not helpful to figure out what editors mean, that it's useless, that there's no point – and nobody else has shared their thoughts since. I think you have effectively discouraged editors from sharing their their views. WhatamIdoing (talk) 18:54, 31 May 2024 (UTC)[reply]
    The main thing that it means to me is that most claims in the article are sourced, and that they're sourced to enough separate reliable sources to establish notability by just reading the references. Many topics are notable in the sense that sources exist out there somewhere, but implicit in the notability guideline is that the reason we're looking to establish there exist such-and-such many reliable sources about a topic is to use those sources to write the article. Any article that does not actually do this is half-baked. Loki (talk) 04:30, 1 June 2024 (UTC)[reply]
    @LokiTheLiar, how many existing articles do you think meet the standard of "most claims in the article are sourced"? WhatamIdoing (talk) 21:56, 1 June 2024 (UTC)[reply]
    I'm aware that there's lots of bad articles out there, if that's what you're asking. I'd still say that the majority of articles meet that standard, and that the overwhelming majority of traffic to Wikipedia is to articles that meet that standard.
    Like, compare naked butler, which doesn't meet the standard I've set here, to complaint tablet to Ea-nasir, which does. They're both small articles on obscure subjects but the complaint tablet one is totally fine. Loki (talk) 22:12, 1 June 2024 (UTC)[reply]
    I believe that the complaint tablet has about five times as many sentences as the median article and about ten times as many sources. So if that's the standard, we'd probably be deleting about 90% of current articles. WhatamIdoing (talk) 22:19, 1 June 2024 (UTC)[reply]
    To put it another way: The median article is a stub. You have given a C-class article as an example that should be considered a "small article". A quick look at Wikipedia:Version 1.0 Editorial Team#Statistics suggests that my off-the-cuff 90% estimate is correct. Only about 10% of articles (excluding lists, dab pages, etc.) rate as C-class or higher. WhatamIdoing (talk) 22:25, 1 June 2024 (UTC)[reply]
    Stub class articles don't necessarily violate this standard. So for instance, I just found a list of stubs and clicked randomly and found Ty Barnett, which clearly meets my standard. Or have Fred BaxterorWilliam Beavers, literally the next two articles I clicked on. All stubs of obscure people, all definitely meet the standard I laid out. Loki (talk) 04:31, 2 June 2024 (UTC)[reply]
    • ORES says the first is Start-class. I think editors might have different opinions about whether it's a long stub vs a short Start, but at 200 words/10 sentences long, it is at minimum on the long side for a stub.
    • The second is a four-sentence, four-source stub, which might put it around the median article for length, but I think it is above average for sourcing.
    • The third is also Start-class. It has 2750 bytes of readable prose and 450 words. This is about twice the length of the maximum described in Wikipedia:Stub#How big is too big? The stub tag was removed from the article during an expansion in 2006. I have corrected the WP:1.0 rating on its talk page.
    Looking at Fred Baxter (the second one), would you feel the same way if it had only three sentences and three sources? WhatamIdoing (talk) 06:16, 2 June 2024 (UTC)[reply]
    Yes. I don't care about length at all. Loki (talk) 13:44, 2 June 2024 (UTC)[reply]
    Are you interested in the number of sources, or the percentage of sentences with inline citations? WhatamIdoing (talk) 18:05, 2 June 2024 (UTC)[reply]
    Number of sources only has to be enough to meet the notability guideline. Otherwise it's fraction of claims that need to be sourced that aren't. Loki (talk) 23:39, 2 June 2024 (UTC)[reply]
    WP:NEXIST says that the number of citations required to meet the notability guideline is zero. (Per that long-standing guideline, the sources have to exist in the real world, but they don't have to be cited in the article.) There are no claims in User:WhatamIdoing/Christmas candy that need to be sourced (nothing about BLPs, nothing WP:LIKELY, etc.). Is that "ready for the mainspace" in your opinion? WhatamIdoing (talk) 23:51, 2 June 2024 (UTC)[reply]
    In my opinion, that article isn't 'ready for mainspace' because it is unreferenced. Cremastra (talk) 00:51, 3 June 2024 (UTC)[reply]
    I realize that the notability guideline itself says that the sources just have to exist somewhere, and not be actually present in the article. However, it's pretty clear that the reason the notability guideline says the sources have to exist somewhere is so they can be used to write the article.
    My big problem with the example article you linked is that it's not clear that "Christmas candy" is a notable subject separate from specific types of Christmas candy. I also think some of the list of examples is more WP:LIKELY to be challenged than you think. I think that for instance someone who did not know what a szaloncukor was is very likely to start out doubtful that it is Christmas candy. Loki (talk) 02:33, 3 June 2024 (UTC)[reply]
    Do you really think I needed to consult sources to write that "Christmas candyiscandy associated with the Christmas holiday season. Candy canes are one type of Christmas candy"? WhatamIdoing (talk) 05:25, 3 June 2024 (UTC)[reply]
    No, but someone who doesn't celebrate Christmas and has lived in a Hindu/Buddhist/Muslim-majority country all their life might need to. WP:V still stands, whether you like or not. Cremastra (talk) 12:05, 3 June 2024 (UTC)[reply]
    WP:V says that it must be possible to find sources (e.g., at a library). It does not say that sources must be cited in the article, except four types of material, none of which are in this article. WP:V is not violated by having those two sentences uncited. WhatamIdoing (talk) 19:31, 3 June 2024 (UTC)[reply]
    I would guess the editor means:
    • The article is completely unreferenced, and/or many of the claims are factually dubious
    • The article is written in English, but is barely coherent. It can be understood, so isn't gibberish, but is an embarrassment and not very helpful.
    • The article is blatantly and overtly promotional
    Cremastra (talk) 20:30, 1 June 2024 (UTC)[reply]
    I could also interpret "not ready for mainspace" to include glaring MOS or technical issues, like:
    • templates outputting nothing but error messages
    • external links peppering article prose
    • infobox with default values for parameters
    • entirely empty sections
    • no subheadings whatsoever, just a giant chunk of text
    • unintentional blockquotes from starting a paragraph with whitespace
    • other Wikipedia pages incorrectly formatted as references instead of internal links
    • etc
    Folly Mox (talk) 14:22, 2 June 2024 (UTC)[reply]

    First, to emphasize the obvious, "ready for mainspace" is a vague subjective term. Probably the only more objective term that could fall under that is "allowed to exist in mainspace" and the most universal standard for that is "likely to survive a reasonably well run AFD". And for an article (NOT article content) NPP and AFC passage ostensibly follow that. Which in turn (presuming no eggregious speedy or wp:not violations) the main criteria ends up being passing wp:notability. Many people (e.g. at AFC, during mentoring, and in this thread) set a higher standard for "ready for mainspace" which is that the content of the article and the article does not have any significant problems or shortcomings. Yes, this is a double standard, and can make AFC a somewhat rough and arbitrary path. But we need to recognize that it is only human by the person reviewing it. If somebody took an article to you that was allowed to exist in mainspace (usually a wp:notability decision on the topic) but which was in really bad or undeveloped shape, would you be willing to bless putting it into mainspace? Most people would want it to meet a higher quality standard before they would personally say "ready for mainspace". North8000 (talk) 19:21, 31 May 2024 (UTC)[reply]

    I agree with WAID that there is a real problem here. If you read the subpoints of WP:DRAFTIFY#During new page review, then it's clear that obviously unready for mainspace is intended to refer to a fairly narrow set of seriously problematic articles: something less than a stub, deletion almost certain, etc. But divorced from that context, "not ready for mainspace" admits a much wider range of understandings, as we've seen above. For example, the draftify script leaves the canned edit summary Not ready for mainspace, incubate in draftspace followed by a selection of prespecified reasons why the article is not ready, which include things like it needs more sources to establish notability and it has too many problems of language or grammar – a far cry from very little chance of survival at AfD. A similar message is given to the creator the explain what happened to the article. If you look at the logs, the vast majority of moves to draft use one of these canned reasons: people take their cues on what they should and shouldn't do from the UI in front of them, not the guideline. Taken out of the guideline and into scripts and other pages, the phrase "not ready for mainspace" itself has taken on a life of its own and is used to systematically circumvent the deletion policy on a daily basis. – Joe (talk) 08:12, 10 June 2024 (UTC)[reply]

    Who are these draftifiers? Are they sufficiently qualified/experienced? My biggest concern about NPR approvals was insufficient expectation of experience at AfD, draftifiers are t performing AfD-like decisions, but unilaterally.
    The wording of the script, was there any discussion or consensus behind it.
    “Not ready for mainspace”. They are very simple word. I think it might be worth an essay, WP:Not ready for mainspace.
    While trying not to embarrass individuals, is it possible to show me a list of bad draftifications? SmokeyJoe (talk) 12:37, 10 June 2024 (UTC)[reply]
    I wouldn't know where to start. I've been reviewing draftifications through WP:PERM/NPP requests, CSD R2 nominations and from the logs for years now and I'd say I come across an egregious example just about every time I look. To be clear, by 'bad', I mean something that clearly exceeds the boundaries set by WP:DRAFTIFY and/or what I understand community expectations to be, not my own. I don't want to unfairly single anyone out, but you could check my contributions to the draft namespace for a representative sample. – Joe (talk) 13:44, 10 June 2024 (UTC)[reply]
    Egregious?
    Some brainstorming questions, not having looked at your contribution history yet:
    Are reviewers systematically applying a higher standard to new articles than would be applied at AfD? I’ve seen that AfC reviewers do this. Could this be explained by an increased expectation of article standard, and AfD voting lagging this change? I know that some people complain about how hard it is to get article deleted at AfD.
    Are bad draftifications being done by editors who are not NPRs? And are they doing bad things randomly?
    Is there any sense that draftifications are being done to endorse a reviewers POV bias on what content should be in Wikipedia?
    Is the problem with this page’s asserted boundaries, or with poor training of NPReviewers? Or with bias from the draftification script(s) due to them proving an easily option for difficult cases? I don’t think that anything in the fairly heavy NPR and AfC training pages instructions to read WP:Drafts. SmokeyJoe (talk) 13:59, 10 June 2024 (UTC)[reply]
    Egregious meaning systematic enough that I feel I have to discuss it with the user and, if they don't stop, pull their NPR right. I think the rest of your questions are good ones and, although I give my anecdotal conclusion on them, I don't have any data to hand (and unfortunately I don't think anyone does, which is why this issue has been festering for years now). I do think the lack of clarity in the phrase "not ready for mainspace"—taken out of context, as discussed above—has contributed to the problem and that's why I think WAID's original question (what is ready for mainspace?) is a good one.
    To suggest a concrete next step, there is a list of specific, consensus-backed things that make a page "not ready for mainspace" at WP:DRAFTYES. We could brainstorm what could be added to those, and/or consider making a separate list of things that don't disqualify a page from mainspace. – Joe (talk) 14:13, 10 June 2024 (UTC)[reply]
    My impression:
    • Are reviewers systematically applying a higher standard to new articles than would be applied at AfD? – Yes. And it's not just one "rogue" editor; it's anyone who doesn't want to be seen "endorsing" or "accepting" an WP:UGLY article. You have to be willing to expend a lot of social capital to follow the written rules. This is one reason I recently suggested a "three strikes and you're out" approach to AFC: On the third time AFC rejects a submission, a bot should do a procedural nomination at AFD. There is no more reliable method of figuring out whether it will be kept at AFD than to send it to AFD.
    • Could this be explained by an increased expectation of article standard, and AfD voting lagging this change? – Yes, but I don't think that "increased" is the right word. AFD still operates on the written rules (e.g., sources must WP:NEXIST in the real world, but don't have to be cited in the article). NPP and AFC functionally reject this rule and want notability "demonstrated".
    • Are bad draftifications being done by editors who are not NPRs? And are they doing bad things randomly? – Yes, overly aggressive draftifications sometimes are done by anyone who believes they are defending Wikipedia against ugly articles, but it's not really random. It is an effort to "raise Wikipedia's quality" by forcing other editors to choose between improving the article or having it hidden from readers.
    • Is there any sense that draftifications are being done to endorse a reviewers POV bias on what content should be in Wikipedia? – I have not seen evidence of, e.g., editors draftifying articles related to geopolitical disputes. There have been times in which we see editors draftifying articles about, e.g., Bollywood actors or African politicians. This could be due to cultural differences (the normal, everyday ways of describing powerful people in some cultures looks like "pure promotional garbage!" in others) and is probably often due to WP:NEVERHEARDOFIT (with that bias applying both the subject and to the newspapers/standard sources in that country).
    • Is the problem with this page’s asserted boundaries, or with poor training of NPReviewers? Or with bias from the draftification script(s) due to them proving an easily option for difficult cases? – I don't think that training is the problem, because part of Wikipedia's notion of "training" is to watch what others are doing and follow their lead. The problem that I want to deal with is the problem of nobody knowing/agreeing on what those words mean. If we agree that ugly articles should be accepted, then the script should reinforce that. If we agree that ugly articles should be hidden, then the script should reinforce that (and WP:UGLY should be updated to say that ugly articles can be hidden in draftspace).
    Joe, I like your idea of having "a separate list of things that don't disqualify a page from mainspace". WhatamIdoing (talk) 17:44, 10 June 2024 (UTC)[reply]
    Me too. SmokeyJoe (talk) 11:44, 11 June 2024 (UTC)[reply]

    Contemplation of a Proposal: Mandate edit summary linking to WP:DRAFTOBJECT in every unilateral draftification

    Proposal: Mandate edit summary linking to WP:DRAFTOBJECT in every unilateral draftification.

    The more I think on this years old idea the more I think it should be done. In practical terms, it is a simple thing to write into draftification scripts. For manual draftifications, these draftifiers are probably not experience and the rule is even more important. For consensus based draftifications, via AfD or informal discussion, they should link the discussion.

    I suspect the rule should also strongly encourage including WP:DRAFTOBJECT in the usertalk explanation (automatic by the scripts), but not mandated due to occasional complications such as the first page author being an IP or banned user. SmokeyJoe (talk) 00:33, 16 June 2024 (UTC)[reply]

    I think we could realistically make this happen in the scripts, but not in manual edit summaries. WhatamIdoing (talk) 16:52, 16 June 2024 (UTC)[reply]
    I agree, but but would it be a good idea, to make it happen in the scripts, and to encourage it in manual edit summaries? It seems to me to be an easy fix to some of the problems you’ve noted (eg newcomers being intimidated). Would it have downsides? It would not fix everything. Would you support this proposal? SmokeyJoe (talk) 11:37, 18 June 2024 (UTC)[reply]

    This is the wrong place for proposals, and I would oppose it anyway, as mandating a link to an essay is a bad idea, as it gives the impression that DRAFTOBJECT is a policy without going through the policy validation process. E.g. the "you can't draftify again" part is being misused by some people to object to redraftification a priori, pretending that it isn't allowed. Often the same people who then object to an AfD because AfD is not cleanup, leaving not much room for other options to deal with very poor articles which, yes, aren't ready for the mainspace. Yes, the drafter could in theory do a complete cleanup of the article, providing coherent prose, sources, ... for a subject they know nothing about, where the sources are in a language they don't speak. Realistically speaking though, the best solution is to move the page to draft again and again until the creator or someone else with the time and knowledge to deal with it turns it into an acceptable article. Fram (talk) 10:03, 19 June 2024 (UTC)[reply]

    HiFram.
    Wrong place? Yes, I know, actually I meant it as contemplation for formally proposing this. I have learned to not propose something without at least one person agreeing with me. If supported, I would start a new page tagged {{Proposal}}. SmokeyJoe (talk) 11:26, 19 June 2024 (UTC)[reply]
    DRAFTOBJECT *is*, already, pseudopolicy, and the proposal would be defacto ratification.
    Redraftification, excepting for WP:COI, is not allowed. It is move warring. Two people disagreeing should not move war, but should discuss, and the perfect forum is AfD.
    AfD is not cleanup? No, it is not. Neither is draftification. Draftification is not for cleanup.
    What do you mean by a very poor article that is not “ready for mainspace”, to ask the central question of this thread?
    If there is any disagreement, it should go to AfD. I firmly disagree with you if you if you think it is ok for one editor to have the authority over another to send their work to draftspace until it meets the first editors undefined standard. —SmokeyJoe (talk) 11:37, 19 June 2024 (UTC)[reply]
    "Pseudopolicy" doesn't exist. Draftofject isn't only about "one editor to have the authority over another to send their work to draftspace until it meets the first editors undefined standard.", it also means that a second editor may not send a page back to draftspace. And the essay gives the right to "one editor to have the authority over other editors to send their own work to main space", no matter how poor. I see no problem with this nor a reason to burden AfD with it. I moved Draft:2025 Rugby Europe Championship to draft twice because it had no sources about the topic but about different topics, but if it could be sourced to good sources it would be a notable subject. An article with such poor sourcing is "not ready for the mainspace". Jesus Calls was draftified, recreated, speedy deleted, and then recreated as Jesus calls. I draftified that one, is that a redractification? And if so, is it for some reason problematic? I redraftified Air 1 (airline) (another editor did the original draftification), why not? Same for Mangkunegara III.
    As for "not ready for mainspace", things like Draft:Sahajanya (unsourced microstub), Draft:Azad Samaj Party (Kanshi Ram), Uttar Pradesh and Draft:Azad Samaj Party (Kanshi Ram), Madhya Pradesh (barely above speedy deletion), Draft:2025 in Belgium (explanation for the "not ready" statement: "So far, this contains 1 sure event only, plus speculative claims about who will be PM, links to unrelated articles, and the holidays for 2024."), Draft:San Sanana (not ready as in "No evidence of notability at the moment, chart performance section is not for this song" but being an Indian song not easy for me or many others to check for actual notability), ... Fram (talk) 13:09, 19 June 2024 (UTC)[reply]
    Taking Draft:2025 in Belgium as the example: Why did you decide that we shouldn't have that page in the mainspace?
    There is no question about the notability. It would easily pass AFD, and AFC's mandate is to accept pages that will pass AFD. If Thief-River-Faller submits it to AFC, they ought to accept it immediately (assuming they follow their own rules, about which there has been some doubt).
    It would also be more likely to get corrected if it were in the mainspace. So why hide it in Draft: space? WhatamIdoing (talk) 17:05, 19 June 2024 (UTC)[reply]
    Whoever would accept that page as is would need their reviewer rights removed. "AFC's mandate is to accept pages that will pass AFD." Among many other things. Accepting pages with almost exclusively blatantly incorrect information just because the topic is notable is making Wikipedia worse, not better. The page at the moment has one correct entry, "7 – 17 August: Belgium at the 2025 World Games"; everything else is either speculation or just factually wrong for the topic. I would urge you to reread Wikipedia:WikiProject Articles for creation/Reviewing instructions, which contains a lot more than "notable = accept". Fram (talk) 21:28, 19 June 2024 (UTC)[reply]
    Sure, I've read that page. I even helped write it. In particular, see Wikipedia:WikiProject Articles for creation/Reviewing instructions#Core purpose, which says (second sentence): "Articles that will probably survive a listing at Wikipedia:Articles for deletion should be accepted."
    See also the second sentence of the next section: "Article submissions that are likely to survive an AfD nomination should be accepted and moved to mainspace" (bold in the original). WhatamIdoing (talk) 21:57, 19 June 2024 (UTC)[reply]
    All the while ignoring the detailed checklist and workflow, which give further, more detailed instructions than the (by definition) simplified summary. I see no good arguments why this page should be in the mainspace as it is now, and putting it in the mainspace while knowing about the issues (which is what you claim a reviewer should do now, if asked by the creator) is basically vandalism, deliberately and knowingly putting incorrect information in the mainspace. Fram (talk) 07:43, 20 June 2024 (UTC)[reply]
    I believe it would be best to blank the obviously wrong information. WhatamIdoing (talk) 20:24, 20 June 2024 (UTC)[reply]
    Taking Draft:San Sanana as an example, why did you choose to hide it in Draft: space instead of blanking the apparently incorrect information (KjjjKjjj, that song isn't "Falling Behind", like it says in Draft:San Sanana#Charts, right?) and tagging it with {{notability}}?WhatamIdoing (talk) 18:14, 19 June 2024 (UTC)[reply]
    So, if it is notable, I should keep it in mainspace. If it is not notable, I should nominate it for deletion. And if notability is unclear I should tag it with "notability", even if there are (like here) clearly other problems as well. Is there any scenario where you believe draftifications is an acceptable course? Fram (talk) 21:30, 19 June 2024 (UTC)[reply]
    Yes, there are a couple of scenarios for which I would accept and even recommend draftification. The first and most obvious is when the editor(s) working on it want to take that route. The second obvious case IMO is when the subject is not currently notable but is reasonably likely to become notable within the next couple of months. For example, we know that certain events, such as the US State of the Union speech or the United States census, will continue to happen on a predictable schedule, but future events frequently fail Wikipedia:Notability (events) until shortly before they happen. If an article is created a bit too early, when we don't have enough sources/attention from the world at large, but when we also believe such sources will be forthcoming in short order (e.g., a press conference has been scheduled for an announcement), then I think draftification is better than either deletion or keeping it. WhatamIdoing (talk) 22:15, 19 June 2024 (UTC)[reply]
    I don't think that extremely minimal approach to draftification is shared by many, and would leave many very poor new articles in the mainspace. Something like Draft:Science Centre, Patan has now been draftified twice, which is a good thing. Would the subject survive an AfD? No idea, and as discussed elsewhere, it isn't the job of reviewers to do a WP:BEFORE check. Fram (talk) 07:43, 20 June 2024 (UTC)[reply]
    I think your extremely maximal approach to draftification, openly ignoring the only written guidance on the subject because it's "just an essay", is shared by even fewer. – Joe (talk) 11:16, 20 June 2024 (UTC)[reply]
    See below, we actually have policy about this, which is what I follow. Fram (talk) 11:43, 20 June 2024 (UTC)[reply]
    the proposal would be defacto ratification if in effect the idea is to make DRAFTOBJECT policy then that should be the proposal, rather than discussing edit summaries. -- LCU ActivelyDisinterested «@» °∆t° 19:13, 19 June 2024 (UTC)[reply]
    Something doesn't have to be a policy (or even a guideline) to be linked in a tool-generated edit summary. WhatamIdoing (talk) 21:51, 19 June 2024 (UTC)[reply]
    ...which should be obvious given that the current edit summary used by scripts is a paraphrase of the very same essay (Not ready for mainspace, incubate in draftspace). Apparently it's okay to use a non-policy to justify moving tens or hundreds of thousands of articles out of mainspace, but not to remind the creators that they're entitled to move it back? – Joe (talk) 11:21, 20 June 2024 (UTC)[reply]
    My point had nothing to do with adding anything to the summary of automated edits. It was that if editors wanted to make suggestions for new policy they should do so. The comment I was replying to was suggesting that policy should be made via discussion on another topic. -- LCU ActivelyDisinterested «@» °∆t° 14:35, 20 June 2024 (UTC)[reply]
    I don't use that edit summary either, and if you both want a policy about draftification; WP:ATD-I: Recently created articles that have potential, but do not yet meet Wikipedia's quality standards, may be moved to the draft namespace ("draftified") for improvement. Fram (talk) 11:43, 20 June 2024 (UTC)[reply]
    Where are those quality standards defined? Thryduulf (talk) 11:45, 20 June 2024 (UTC)[reply]
    Nowhere probably, just like many things around here. Having reliable sources and intelligible prose, being factually correct, and actually being about the topic as suggested by the title, is what I (and in my experience most others who do new page checking) apply. I don't think any of these can be considered really controversial. Fram (talk) 12:01, 20 June 2024 (UTC)[reply]
    This discussion demonstrates that every one of those is controversial:
    • The only requirement for sources is that they exist - if they don't exist the article should be prodded or sent to AfD, if they do exist add them to the article, if you don't know then look.
    • If there is no intelligible prose then the article should be deleted (speedy deletion criteria G1, G2, A1, A2 and/or A3 almost certainly apply)
    • If the article is factually incorrect then it should be corrected or nominated at prod or AfD (unless it's a blatant hoax, in which case it should be speedily deleted under criterion G3).
    • If it isn't about the topic as suggested by the title, then either rename the article or nominate it for prod/AfD. Thryduulf (talk) 12:14, 20 June 2024 (UTC)[reply]
    Nobody would disagree that those are desirable qualities in an article, but whether they constitute a required standard for mainspace is indeed controversial. As just one data point, the existence of {{unreliable sources}}, {{incomprehensible}}, {{disputed}}, and {{off topic}} would suggest that all of the problems you list have been tolerated in mainspace in the past. The lack of a definition of "Wikipedia's quality standards"—AKA being "ready for mainspace"—is the problem that motivated this discussion and, as the discussion shows, it leaves room for a wide range of understandings. – Joe (talk) 12:17, 20 June 2024 (UTC)[reply]
    Feel free to ping me when a policy proposal is put up for a vote. Until then, I don't think anything useful will come from continuing this discussion with you three. The requirements put up here, basically requesting the reviewers needing to do all the work the creator should have done and can do much easier, are mainly based on misreadings of policy ("The only requirement for sources is that they exist", well, no: "Any material lacking an inline citation to a reliable source that directly supports[b] the material may be removed and should not be restored without an inline citation to a reliable source. " and "The burden to demonstrate verifiability lies with the editor who adds or restores material" (bold in original). A completely unsourced article may thus be blanked (which would make it eligible for speedy deletion, not really preferable), or by draftifying it "removed" from the mainspace; and the burden to add sources lies with whoever wants it back in the mainspace, the one who "restores material". Putting that burden on new page reviewers is not acceptable (of course they may do so if they wish, but it should never be a requirement). Similarly, "If the article is factually incorrect then it should be corrected or nominated at prod or AfD (unless it's a blatant hoax, in which case it should be speedily deleted under criterion G3)" yes, it should be corrected by the creator or whoever wants the material in the mainspace. Otherwise it will be deleted. It shouldn't be brought to Prod or AfD as these are not for cleanup. "If it isn't about the topic as suggested by the title, then either rename the article or nominate it for prod/AfD." No, if you actually do new page patrol then you will encounter many cases where someone has created an article for topic X by copying their own previous creation about topic Y, and forgot to change all or most of the text. Topic X is notable, the creator is probably knowledgeable and interested in correcting this, but until then we have a completely wrong article in the mainspace (not incomplete, poorly sourced, just wrong). Speedy deleting this as a hoax is very WP:BITEy and draftifying the much more friendly, gentle solution, the middle ground between keeping the mainspace factual and the editor encouraged to continue working on it.
    The approach taken by you three seems to be "we need a policy or you can not do this" (even though we have a policy encouraging draftification in such cases), and "you are not allowed to do things which go against this essay here". Oh, and "all the work should be done by the reviewers, not the creators" or (judging from their contributions) people who never patrol new pages, edit draft space, or nominate pages for deletion (like Whatamidoing and Thryduulf) I'll continue to ignore this until you get a policy that actually supports your positions, or until you get a consensus at ANI or so that I should change my approach. Fram (talk) 12:49, 20 June 2024 (UTC)[reply]
    Most of that is not opposing DRAFTOBJECT, which is about empowering the newcomer to get their week at AfD if they want it. Opposing part of DRAFTOBJECT are a few example of something draftified twice, where WP:ATD-I rolled with DRAFTOBJECT would mean that Fram is supposed to send the bad article to AfD with a nomination to Draftify. Maybe “do not Draftify twice” is a soft rule, maybe newcomers mainspacing a draftified article do not actually mean that they want to debate it at AfD. SmokeyJoe (talk) 13:15, 20 June 2024 (UTC)[reply]
    I find your (Fram's) response interesting, because underneath it, it feels like there is a question about whether Wikipedia is a collegial, collaborative project. Several of the examples you give sound like a Wikipedia-as-a-game model: Any sentence could be required to have an inline citation, so if "you" don't have "enough" (or any) inline citations, then "my" move is to capture your article. If you make the right moves, you can get your article promoted back to the mainspace, but I see my role as fundamentally adversarial: I will prevent you from sharing information until you do so in a way that I believe is appropriate, and I will not help you fix any problems you encounter. WhatamIdoing (talk) 21:06, 20 June 2024 (UTC)[reply]
    And here I thought the singular purpose of Wikipedia is to be a factual, verifiable encyclopedia that anyone can edit. But all this time it has actually been a social platform where the real goal is to get more precious users by zealously protecting their right to publish whatever they want to the first page of Google. Editor retention above all else. JoelleJay (talk) 09:11, 21 June 2024 (UTC)[reply]
    How the fuck are we going to maintain a "factual, verifiable encyclopedia" if we don't retain editors? – Joe (talk) 09:27, 21 June 2024 (UTC)[reply]
    What is this "pseudopolicy" and why is it exempt from actual policies, like Policy and guideline pages are seldom established without precedent[3] and require strong community support. Policies and guidelines may be established through new proposals, promotion of essays or guidelines, and reorganization of existing policies and guidelines through splitting and merging. [...] Proposals for new guidelines and policies require discussion and a high level of consensus from the entire community for promotion to guideline or policy status. Adding the {{policy}} template to a page without the required consensus does not mean the page is policy, even if the page summarizes or copies policy. and Wikipedia has a standard of participation and consensus for changes to policies and guidelines. and The burden to demonstrate verifiability lies with the editor who adds or restores material and Because a lack of content is better than misleading or false content, unsourced content may be challenged and removed.?JoelleJay (talk) 08:39, 21 June 2024 (UTC)[reply]

    Reliable source engine

    Created a prototype 'reliable source engine' (you can try it here) to simplify finding reliable sources. Is this something that already exists? That others might use? (if so, maybe Wikimedia can partner with Google to make the search engine ad-free?) Superb Owl (talk) 20:11, 4 June 2024 (UTC)[reply]

    I just tried it and liked the results. Thanks! Schazjmd (talk) 20:23, 4 June 2024 (UTC)[reply]
    See WP:WRS. --Talky Muser (talk) 20:37, 4 June 2024 (UTC)[reply]
    Love it! Maybe that's something to implement to the Find sources link present in most citation needed templates? But, it already seems to exist as above. Cocobb8 (💬 talk • ✏️ contribs) 21:53, 4 June 2024 (UTC)[reply]
    Thanks all! I pinged User_talk:Syced/Wikipedia_Reference_Search#Relationship_with_WP:RSP? for feedback and to see if they think it'd be helpful to have more versions and added a second version narrowed down to reliable sources without paywalls. Superb Owl (talk) 09:14, 5 June 2024 (UTC)[reply]
    WP:RSSE is another. Levivich (talk) 02:29, 6 June 2024 (UTC)[reply]
    Oh awesome! I added all of these to the esssay Wikipedia:Advanced source searching#Niche search engines so they are all in one place Superb Owl (talk) 22:20, 8 June 2024 (UTC)[reply]
    Awesome! I'm definitely bookmarking it for later use. Relativity ⚡️ 18:57, 8 June 2024 (UTC)[reply]
    Would love your thoughts when you've tried it!
    I also just filtered-out opinion pieces when possible.
    And also confirmed that all of the other existing search engines include at least some sources where there is no consensus on reliability. Superb Owl (talk) 22:19, 10 June 2024 (UTC)[reply]

    possible idea; entry compiling overviews of multiple novels, in a single series

    hi all. i made the article below in my own userspace, to compile plot summaries for all novels in a series, namely the Aubrey-Maturin series, by Patrick O'Brian. what do folks here think of this, as a possible model for a type of article?

    as far as I know, there is no rule currently against this type of article, but I wanted to get a little feedback here, just to see what reactions or comments on this type of article people might wish to express.

    appreciate any feedback. thanks! Sm8900 (talk) 14:05, 7 June 2024 (UTC)[reply]

    I like the idea, but I don't really think Wikipedia would be the best project for it, as this is mostly based on summarizing primary sources. However, it would be great to envision this as a separate Wikimedia project, if that can be possible! Chaotic Enby (talk · contribs) 14:17, 7 June 2024 (UTC)[reply]
    WP:NOTPLOT seems like the relevant guideline here. While an encyclopedia article on a series of books can be appropriate (and indeed we do have Aubrey-Maturin series) an article which does nothing but summarise the series, as this seems to be, would not be. Caeciliusinhorto-public (talk) 14:20, 7 June 2024 (UTC)[reply]
    TV Tropes has recap pages for series {example} Mach61 16:52, 8 June 2024 (UTC)[reply]
    That is very long. Maybe incorporating condensed synopses of each entry just like List of Black Mirror episodes vs longer summaries on each individual article into Aubrey–Maturin series#Series would be more appropriate. Aaron Liu (talk) 14:20, 7 June 2024 (UTC)[reply]

    Proposed edits feature

    I was thinking that there could be a new feature where someone makes an edit but instead of applying it, ticks a box so that it has to gain approval from one other editor to be applied (and can’t outright be refused). This is a much less time consuming method that would replace talk page spam and be more of a proposal. It would also be ideal for contentious topics, to stop incorrect or uncertain content from being applied. Alexanderkowal (talk) 12:03, 9 June 2024 (UTC)[reply]

    Something like Wikipedia:Pending changes?Anomie 12:59, 9 June 2024 (UTC)[reply]
    Yes but as an option per edit for an editor, or give the edit a timer of a few hours until it’s automatically applied, during which someone can revert it preemptively Alexanderkowal (talk) 13:07, 9 June 2024 (UTC)[reply]
    Is it worth the effort to distrust an editor so much that we need a giant conservatorship scheme? Aaron Liu (talk) 13:12, 9 June 2024 (UTC)[reply]
    It is not to distrust the editor, it’s for edits where the editor is unsure Alexanderkowal (talk) 13:21, 9 June 2024 (UTC)[reply]
    @Aaron Liu My reading of the OP is that it's partly intended for editors to apply a "please check this" flag to their edits. This would only be used by editors who are editing in good faith but are unsure of Wikipedia's norms, etc (the vast majority of whom will be newcomers) so this might be a good way reducing entry barriers for some but I don't think it would be at all effective at reducing spam, deliberate misinformation, other bad-faith editing or those who are confidently wrong in good faith. Thryduulf (talk) 13:24, 9 June 2024 (UTC)[reply]
    Yes correct, and it could be a less inflammatory way of doing WP:BRD on contentious topics or controversial edits Alexanderkowal (talk) 13:27, 9 June 2024 (UTC)[reply]
    Only when the editor is not confident they are right. To catch the bad faith and confidently wrong it would have to apply to all editors (or all (extended-)confirmed editors), which is what pending changes is. Thryduulf (talk) 13:40, 9 June 2024 (UTC)[reply]
    Yes Alexanderkowal (talk) 13:42, 9 June 2024 (UTC)[reply]
    Editing already effectively works this way, especially if a "proposed edit" has a timer after which the edit is automatically accepted. Any edit can be reverted, so in effect every edit already is what a "proposed edit" would be under this scheme. I wonder if there's some value in making this into a technical restriction we could apply to problematic editors? Right now, if we identify that an editor's work is problematic, all we can really do is talk to them or else ban or block them. A sanction where we could impose pending changes on just their edits might be a decent lower-level enforcement mechanism. Then again our technical options for less-than-total blocks are already getting kind of complicated. Ivanvector (Talk/Edits) 13:54, 9 June 2024 (UTC)[reply]
    You're right that a "proposed edit" with a timer is sort of like the status quo, but the status quo means that edit is published and likely to be read by some readers, the binary between published and unpublished edits facilitates conflict Alexanderkowal (talk) 13:57, 9 June 2024 (UTC)[reply]
    (edit conflict) You still seem to be conflating things. This feature would either apply to all editors or be opt-in.
    • If opt-in it might have merit as a feature for good-faith new editors, but it would be useless at best against bad faith and confidently wrong editors so it would be a waste of time to discuss it in relation to the latter.
    • If applied to everyone it might be effective against good and bad faith errors, but it would duplicate the existing pending changes, so it would be a waste of time to discuss it.
    So forget bad faith editors, controversial topics, BRD, etc and develop this as a proposal solely to reduce barriers to entry for not-yet-confident, good faith new editors. We need more of those people so reducing barriers to entry for them is a Good Thing. Thryduulf (talk) 13:55, 9 June 2024 (UTC)[reply]
    Yes completely agree, I'm not tech literate so I would struggle to progress this but I'll try and lay out what I have in mind Alexanderkowal (talk) 13:59, 9 June 2024 (UTC)[reply]

    The idea is a checkbox next to where the editor types the edit summary, to make this edit a "proposed edit", which appears in the edit history at the time it is 'published' and the edit is automatically applied after a chosen period of time, I suggest the options being 10 mins, 30 mins, 1 hr, 2hr, 6 hr, 12hr, 24 hr. Other editors, when reading the edit history, can either 'support' or 'oppose', support applies it immediately, oppose reverts it (reasons are given for both). If the edit is reverted, you accept it or move to the talk page.

    The policy around this would have to be clear to counter spam or wasting editors' time. It would also have to counter page ownership, guardianship, and unnecessary reverting. Alexanderkowal (talk) 14:07, 9 June 2024 (UTC)[reply]

    Also anyone can revert an edit that has been supported, it is not necessarily consensus 2 v 1 Alexanderkowal (talk) 14:09, 9 June 2024 (UTC)[reply]
    It doesn't feel like you've taken Thryduulf's comments into account. A spammer doesn't have any incentive to opt into a mechanism intended to counter their work. And by design, your proposal is to ask other editors to consider proposed edits, so it's not countering additional effort from other editors. As written, it's encouraging editors to make proposed edits with the cost of additional work by others. Depending on the relative amount of good-faith edits that end up getting reverted today, versus ones that don't, in theory this could be a net gain. My instinctive feeling, though, is that the target audience isn't large enough for it to significantly reduce net effort. Thus I agree with Thryduulf that it would better to focus on encouragement as a goal. I suggest reading about Wikipedia:Article Feedback Tool, which has some similarities to your proposal. It was discontinued as the amount of useful suggestions was completely swamped by the numbers of poor suggestions, and there wasn't enough volunteer effort to handle them. isaacl (talk) 16:11, 9 June 2024 (UTC)[reply]
    This isn't anything to do with spammers or bad faith editing. It is a feature for newer editors who're generally unsure and unfamiliar with policy. To be clear it is an option, most editors will not check the box. The second paragraph there was just about writing policy around it and foreseen problems. Alexanderkowal (talk) 16:28, 9 June 2024 (UTC)[reply]
    I apologize; your second paragraph is a bit unclear to me. I suggest avoiding the word "policy" in that context, as it seems you're saying that the procedure should strive to avoid unhelpful suggestions, rather than suggesting relationships to policy. You could try discussing your proposal with WMF Growth team to see if they've considered anything along those lines. isaacl (talk) 16:50, 9 June 2024 (UTC)[reply]
    Okay, thank you, yeah I could've worded it clearer Alexanderkowal (talk) 17:04, 9 June 2024 (UTC)[reply]
    Could you clarify what 'and can’t outright be refused' means, and what problem it solves? If an editor checks the edit and see it's in error they can still just revert it, if they check the edit and don't think it's appropriate why then waste another editors time doing the check again. -- LCU ActivelyDisinterested «@» °∆t° 17:31, 9 June 2024 (UTC)[reply]
    Please ignore my first two comments, I later combined them Alexanderkowal (talk) 17:35, 9 June 2024 (UTC)[reply]
    Sorry I didn't reply properly. It encourages new people to edit wikipedia who're put off by their unfamiliarity with procedure and can facilitate master, student relationships between editors. It also means editors who're unsure about their particular edit can seek approval so that false information/edits contradicting policy are not published, even if for a short time. It can also be a less inflammatory method of doing BRD on controversial edits on contentious topics/pages. Alexanderkowal (talk) 12:58, 10 June 2024 (UTC)[reply]
    It can also be a less inflammatory method of doing BRD on controversial edits on contentious topics/pages Don't understand this, what does "doing BRD" mean? Or why is doing BRD inflammatory? Selfstudier (talk) 13:18, 10 June 2024 (UTC)[reply]
    Acting boldly on controversial topics can produce genuine conflict between editors and make it harder to work collaboratively, especially if editors are emotionally involved. This feature could provide a more measured way of going about it. Alexanderkowal (talk) 13:30, 10 June 2024 (UTC)[reply]
    To be clear, a proposed edit can be outright refused/reverted by one other editor Alexanderkowal (talk) 13:02, 10 June 2024 (UTC)[reply]
    If the edit has been made, it is not really "proposed" is it? And isn't it the case that any editor can already revert it? Selfstudier (talk) 13:20, 10 June 2024 (UTC)[reply]
    I think you’re misunderstanding, which is fair because I haven’t been clear, the proposed edit is not immediately applied or published. It appears in the edit history like a published edit but isn’t yet one. After a chosen amount of time, during which it can be prematurely reverted, it can become a published edit. Another editor can immediately apply it if they agree with it and bypass the timer. Alexanderkowal (talk) 13:28, 10 June 2024 (UTC)[reply]
    The German-language Wikipedia does this (with their version of Pending Changes), but it's applied involuntarily and per-user (e.g., all inexperienced users), rather than edit-by-edit.
    There have been times when I've wished to have someone else check an edit for me. Here's one that I would have flagged for review. Ten years later, it's still in the article (and I still think it's correct). WhatamIdoing (talk) 17:53, 10 June 2024 (UTC)[reply]
    Could do with a source though lol Alexanderkowal (talk) 18:11, 10 June 2024 (UTC)[reply]
    Its bad enough that my typos may not be corrected for years, but I only noticed this error 8 years later. Donald Albury 23:57, 10 June 2024 (UTC)[reply]
    This is an interesting idea: essentially, allowing editors to apply pending changes to their own edits on a per-edit basis. I like it. I think you'd need someone to add to MediaWiki the ability to do per-edit pending changes (not sure if that's possible with current software). It could help reduce edit wars and BLPvios and the like. Levivich (talk) 05:46, 11 June 2024 (UTC)[reply]
    Another use case would be an intuitive replacement for edit requests. Aaron Liu (talk) 11:54, 11 June 2024 (UTC)[reply]
    Yes, maybe the timer could have an option of unlimited, which would be the only option for non EC users on certain topics? Alexanderkowal (talk) 11:56, 11 June 2024 (UTC)[reply]

    Whales

    We don’t have enough content about whales. The whale content is lacking. Are kids going to be successful if they’re not skilled in whales? The answer is no. Hence, we need more whale content. First, how do they breed? Second, what do they like to eat? Third, 2603:7000:4EF0:9ED0:F9B8:A706:2018:DF70 (talk) 03:32, 10 June 2024 (UTC)[reply]

    Moot We already have sweet Jimbo Wales. Aaron Liu (talk) 11:35, 10 June 2024 (UTC)[reply]
    And {{whale}}!Chaotic Enby (talk · contribs) 12:44, 10 June 2024 (UTC)[reply]
    [cetacean needed]Jéské Couriano v^_^v threads critiques 23:16, 10 June 2024 (UTC)[reply]
    fixœd Aaron Liu (talk) 02:58, 11 June 2024 (UTC)[reply]
    Third, how often do they explode. —Cryptic 15:39, 10 June 2024 (UTC)[reply]
    We can talk about whales during lunch. --jpgordon𝄢𝄆𝄐𝄇 21:20, 10 June 2024 (UTC)[reply]
    We have a lot of content on this subject, but (per WP:ENGVAR) we use the UK spelling … without the “h”… see: Wales. Blueboar (talk) 21:31, 10 June 2024 (UTC)[reply]
    I've created a task force homepage. Aaron Liu (talk) 22:20, 10 June 2024 (UTC)[reply]
    I think you mean how often does he explode. The WordsmithTalk to me 00:37, 11 June 2024 (UTC)[reply]

    Add a timeline to Wikipedia pages

    Hi, More than 10 years ago I thought about improving Wikipedia pages, but I was convinced that Wikipedia would logically end up integrating it over time. However, I note that this was not the case even though it would certainly add value to the presentation of the information.

    In fact it involves adding a horizontally scrolling timeline in each Wikipedia page in which the topics of the page are located, accompanied by a bunch of events of all types from the period, where each event listed in the timeline would be clickable to go to the relevant Wikipedia page.

    This timeline could be enhanced with a zoom to go into more or less detail, as well as filters such as: Characters, History, Politics, Science, Sports... so that its presentation is not too busy.

    Clicking on a date or event could also refocus this timeline on the period concerned.

    For students, journalists and anyone doing research, this would provide a temporal view of information.

    And for all other WEB users another way to navigate your encyclopedia.

    In my opinion, this is interesting work which would enhance the encyclopedia by making it evolve qualitatively in terms of ergonomics.

    For any clarification if you have not understood the concept, I will be happy to clarify my suggestion with the hope that it will eventually succeed. Htordj62 (talk) 14:54, 12 June 2024 (UTC)[reply]

    This is a good idea, but I am afraid that it might not necessarily work when different timelines are considered. For instance, taking something like Dinosaur, would we show the timeline of dinosaur evolution from the Triassic onwards with events such as the Cretaceous–Paleogene extinction event, or the timeline (at a completely different scale) of dinosaur research, with the discovery and classification of fossil species and events like the dinosaur renaissance?Chaotic Enby (talk · contribs) 14:58, 12 June 2024 (UTC)[reply]
    That's right but the scale could be not linear and if you can zoom in/out you can select what you want to see, the idea is not to see complete timeline at first view but to see on page an interesting period.
    There is many things to do around this graphically for instance on mouse hover it could break the timeline in several popup timelines depending on different subjects.
    Regards Htordj62 (talk) 15:08, 12 June 2024 (UTC)[reply]
    What I see in https://en.wikipedia.org/wiki/Template:Horizontal_timeline this is a text textline not a graphic so it is limited, and the idea is not to force the page creator to manage it. I see that like a task of server which extracts dates of the page to build the graphic time line and add it on page.
    I will try to provide you a graphic view I mean. Htordj62 (talk) 09:43, 13 June 2024 (UTC)[reply]
    Here you can find a good sample of view using TimelineJS : https://timeline.knightlab.com/ Htordj62 (talk) 10:00, 14 June 2024 (UTC)[reply]

    You

    might

    want

    to

    take

    a

    look

    at

    {{Horizontal timeline}}.

    2603:8001:4542:28FB:46B:9E7E:661:108F (talk) 05:31, 13 June 2024 (UTC) (Actual talk)[reply]

    0

    1080

    2160

    3240

    4320

    5400

    For any of yall reading this thread in desktop mode, here's what the above template renders like on mobile:
    Folly Mox (talk) 23:15, 16 June 2024 (UTC)[reply]

    Dark Mode as a Premium Feature

    If dark mode was offered as a premium feature I'd be pretty likely to pay $0.99 per month for a premium "membership".

    Offering this feature would help my eyes and could be a great way to get users to support the site more consistently. 2601:644:9282:65E0:6844:BE91:592E:183F (talk) 01:22, 13 June 2024 (UTC)[reply]

    See Wikipedia:Dark mode. You can sort-of get it for free. And it would be grossly improper to charge for it. The WMF don't really need the money anyway. They are rolling in it, and a great number of contributors here consider both the way they raise funds and some of the things they spend it on to be less than optimal. AndyTheGrump (talk) 01:34, 13 June 2024 (UTC)[reply]
    Appreciate your response. Good to know they aren't hurting for funds.
    I've used Wikipedia extensively and have donated/contributed multiple times, and thought since I could be convinced to pay for this feature it was worth mentioning as a possible fundraising tactic.
    Perhaps it would be grossly improper. Admittedly, I would trust an official Wikipedia feature more than installing a browser extension. 2601:644:9282:65E0:6844:BE91:592E:183F (talk) 01:40, 13 June 2024 (UTC)[reply]
    I have been using the Dark Mode Gadget for I think a couple years. Some pictures came out wrong, but not enough to persuade me to give up the lovely darkness. Several minutes ago the notice came up that the Gadget was interfering with the new Dark Mode Feature, so I clicked the deactivate and found the correct option in Preferences. Very nice. Well, I don't notice if there's any difference. Alas, I have forgotten which pictures came out wrong with the old Dark Gadget, so don't know whether that was fixed. Anyway go, go, dark! Jim.henderson (talk) 01:44, 13 June 2024 (UTC)[reply]
    The Wikimedia Foundation is working on a night mode; see mw:Reading/Web/Accessibility for reading. You can feel free to take that amount and donate it to a charitable organization whose goals align with Wikipedia, or some other Wikimedia Foundation project. isaacl (talk) 01:57, 13 June 2024 (UTC)[reply]

    Lack of Filipino folk arts

    It has come to my attention that Wikipedia lacks info about Filipino folk arts. So far I've only seen three pages of Filipino folk songs, and in the folk section of Dance in the Phillipines a plethora of some dance's pages haven't been created. Obviously I'm not trying to say that we should add EVERY SINGLE BIT. But it would be nice to add others. Cyb3rstarzzz (talk) 14:10, 14 June 2024 (UTC)[reply]

    Try being bold and editing pages yourself to see what you can improve. – Teratix 14:36, 14 June 2024 (UTC)[reply]
    To underline what Teratix said, every page on Wikpedia was created by someone. You can be that someone. Phil Bridger (talk) 18:42, 14 June 2024 (UTC)[reply]
    I (kind of) take my word back for Filipino folk songs, I've done some more research. I don't know the exact amount but it's more than three pages. But Wikipedia is still missing some more, the absence of Filipino folk dances is still present. I'll be sure to make their Wikipedia pages as soon as I can. Cyb3rstarzzz (talk) 09:17, 15 June 2024 (UTC)[reply]
    As good old dear Liza would say, then fix it dear Henry then fix it. Davidstewartharvey (talk) 09:33, 15 June 2024 (UTC)[reply]
    Yeah, I'll make sure to make their Wikipedia pages as soon as I can. Cyb3rstarzzz (talk) 14:09, 15 June 2024 (UTC)[reply]
    Please do remember I am a new user, it'll take some time. Cyb3rstarzzz (talk) 16:58, 15 June 2024 (UTC)[reply]
    Hi Cyb3rstarzzz, if you haven't already, you should take a look at Wikipedia:Tambayan Philippines and its discussion page. It looks like it's active, so you might be able to find another editor there who has some familiarity with the topic or who would be interested in coordinating efforts. hinnk (talk) 21:18, 15 June 2024 (UTC)[reply]

    Some kind of reminder at AN/I

    This is not a joke proposal.

    I'd like to propose some kind of reminder/checker that automatically runs at AN/I, in the style of [1]. Actually reading it back to the user is good, but a given user's computer probably doesn't have the sound turned on all the time, so a pop-up dialogue box, with a five-second delay before the user can click "continue" would probably work too. Something like this:

    Here's what you just posted to AN/I:



    Yes, post this comment.Wait, go back.


    Thoughts? Cremastra (talk) 20:05, 16 June 2024 (UTC)[reply]

    Having a delay for every single reply can really make things really annoying. You also have all the different userscripts for replying (CD, Factotum, etc.) that to make that warning appear to every one of them would be really hard. Aaron Liu (talk) 22:41, 16 June 2024 (UTC)[reply]
    Forced preview was a feature(?) in the early days of the visual editor. However, it previewed the entire page, which would be a terrible experience at ANI.
    There's another Wikipedia (Korean, maybe? I can't remember) that does something like this for all posts to their village pump. I don't think it shows your comment. It's more like a message that says "This is the village pump, which is not for random chatting". I don't know for certain how they set it up, but it might be implemented with the 'warn' setting in Special:AbuseFilter. That method would probably work on (almost) all tools. WhatamIdoing (talk) 18:24, 19 June 2024 (UTC)[reply]

    Wikipedia:MOS on Music / Song Track Listing Credits

    I was reading Let_It_Be_(album) #Track_listing and perplexed to find the tracks credited to Lennon–McCartney. While this was the mythos at the time, later scholarship has done a great job distinguishing many of the Beatles tracks as predominantly or entirely written by Lennon or McCartney. I can't seem to find the style guideline on this, but I assume it's something like "song credits should be as written on the original release."

    This is unencyclopedic and ahistorical. While most song credits will line up neatly with later scholarship, some rare cases exist where listed credits were chosen for political or business reasons.

    The style guide should default to credits as printed (except in cases where artists changed their name later), but allow for those to be de-emphasized in favor of newer research. For example, Let_It_Be_(album) #Track_listing's writer credits should be almost the same as the lead vocalist credits. Anonymous-232 (talk) 20:16, 16 June 2024 (UTC)[reply]

    The MOS is a style guide that really doesn't deal with what sources are best to use in a given situation, which is why you couldn't find such guidance in it; it's possible that WikiProject Music has some sort of established norm for this, but Wikipedia policy (see WP:V) already greatly favors information in reliable, secondary sources. If such consensus in scholarship exists, and it's cited, I doubt anyone will have an issue with changing the credits of songs to fit that consensus. ~Adam (talk · contribs) 02:55, 17 June 2024 (UTC)[reply]
    [2] Rolling Stone interview with Paul about it the credits. Should we be changing what was agreed? Davidstewartharvey (talk) 08:41, 17 June 2024 (UTC)[reply]
    My gut feeling is that the track listing should match the credit listed on the actual release. Later discussion (whether scholarly research, notable speculation or something in between) is something that should be discussed in prose (maybe accompanied by a list in some cases) that explains the background, why this is a thing that has been researched/speculated about and what the basis for assigning different authorship to each track is. Thryduulf (talk) 09:07, 17 June 2024 (UTC)[reply]
    Track listing should be as published at time of release. The text of the article can cover anything else: pseudonyms, legal challenges, scholarly analysis, etc. --User:Khajidha (talk) (contributions) 12:33, 17 June 2024 (UTC)[reply]

    Re-use and edit citation

    I find the re-use citation tab to be of limited use, because it only allows using the exact same citation, pages and all. If then I try to edit just the page numbers in the new instance, it will change the page numbers in all instances of that citation, which I do not want. Instead what I'd like to see is the ability to just edit the page numbers in the new instance. I've encountered this use case hundreds of times, when I want to cite the same source but different pages in various places, thus it would greatly ease the burdensome tasks of adding citations. I have yet to encounter a case where i wanted to edit page numbers simultaneously in all instances of a citation. If the latter use case exists, then an option could be provided to change just this instance, or all instances of same citation.

    I'd like to hear what other people think Thhhommmasss (talk) 02:44, 19 June 2024 (UTC)[reply]

    I'd recommend using {{rp}} instead of the page parameter. Using the same source with a ton of different pages multiple times clogs up the reference list IMO. Or you could also use {{sfn}} if you're going to reuse the same page from a source that has multiple pages cited as well. Aaron Liu (talk) 03:09, 19 June 2024 (UTC)[reply]
    I prefer using rich-text edit to source edit, since former is more convenient and faster for me. Instead I now have to use sfn which is a pain, and to get around that very often I use multiple automatically generated citations, via link, of the same source. But that too requires me to go to Google books or a similar source to get the same link again, so again more effort, plus it generates duplicate entire citations of same source. 95%+ of my citations from the same source are for different pages, and I do not need each one of these in the reference list, instead just the last referenced page could be kept in the list Thhhommmasss (talk) 06:22, 19 June 2024 (UTC)[reply]
    Well, VE is indeed slower if you're working with templates. I find the 2010 Wikitext editor to be the best. It loads fast, has syntax-highlighting, and works with templates fast. You can use WP:ProveIt to autogen cites in source mode. Aaron Liu (talk) 19:40, 19 June 2024 (UTC)[reply]
    The issue isn't the extra second or two that it takes VE to load vs. wikitext, instead t the considerably greater time it takes to to manually type out the wikitext citation template, vs. just clicking to select a source in VE from the reference list, and as noted below, input the new page number into a dialog. Plus, new editors are much less likely to be familiar with wikitext, so this could be another hurdle to participating Thhhommmasss (talk) 22:13, 19 June 2024 (UTC)[reply]
    I do not doubt that the current workflow in VE has things to be desired. However, what I'm saying is that in the meantime, you can use the 2010 Wikitext to edit the pages faster than what you probably currently do. You can use a clipboard manager (including Windows's default, ⊞ Win+V) to copy the parts of the sfn templates right before the page number, and all you'll have to type is e.g. 41}}.
    While WMDE works on the wish, someone might be able to make a userscript. Aaron Liu (talk) 22:38, 19 June 2024 (UTC)[reply]
    When using Word or gmail, I also prefer their VE, instead of having to use Word markup or html, no matter the templates or other features they may have. I suspect the vast majority of users do too. I know some prefer different, and the proposal has no impact on current wikitext edit, it's only intended to help those who prefer VE. Believe change outlined below should be relatively easy Thhhommmasss (talk) 00:51, 20 June 2024 (UTC)[reply]
    You can file a Phabricator task if you want. Aaron Liu (talk) 02:32, 20 June 2024 (UTC)[reply]
    Thank you, I will look into thatThhhommmasss (talk) 22:25, 20 June 2024 (UTC)[reply]
    Personally I despise {{rp}}: it's ugly, confusing to anyone who doesn't already know that [1]:23 is supposed to mean "page 23 in reference 1", and separates the page number from the reference. I wish m:WMDE Technical Wishes/Reusing references / m:WMDE Technical Wishes/extending references would happen; unfortunately it seems to keep stalling because of having to support VE. Anomie 11:42, 19 June 2024 (UTC)[reply]
    I would also like to see WMDE's work become an option here (subject to all the usual WP:CITEVAR standards, of course). WhatamIdoing (talk) 18:18, 19 June 2024 (UTC)[reply]
    Another approach would be not to save the pages to the reference list, since it is much more common that one wants to reference different pages in the same source, instead of wanting to repeatedly reference the same page. Then when user selects the source from the re-use list, a dialog could pop-up to let the user input the page numbers and save. As noted, I generally use the GUI edit since it is much faster, and I find having to switch to source edit for wikitext templates, just to reference a different page, to be one of the greatest pain points in WP usage. Citing in general is the biggest, most time-consuming chore, probably one of the main reasons people are less likely to edit and why many articles lack sufficient in-line citations, The issues with re-use make this worse Thhhommmasss (talk) 18:38, 19 June 2024 (UTC)[reply]

    A confusion disclaimer should be added to the top of the page for cisgender

    [section originally titled: "A confusion disclaimer should be added to the top of the page for cisgender to avoid confusion with the Russian military pact Commonwealth of Independent States often abbreviated as (CIS)"]

    i tried searching for CIS Commonwealth of Independent States and i received the page for Cisgender. if somebody who maybe was unaware of the full name of the commonwealth of independent states attempted to search for the frequently used acronym CIS the full page maybe be hard to reach.

    full disclaimer I don't intend to degrade gender science and thus the page for cisgender I love trans people 2601:584:4400:4110:CC8A:47DD:7DBD:EA0D (talk) 14:13, 19 June 2024 (UTC)[reply]

    Indeed. I did a quick test by searching for CIS with 3 search engines:
    • Wikipedia's internal search engine:takes me directly to the disambiguation page
    • Google: First hit was the Center for Internet Security
    • DuckDuckGo: First hit was the Wikipedia page for Cisgender
    So based on that HIGHLY SCIENTIFIC test,;) the search results aren't consistent and likely vary based on the search engine's profile of the user. It also appears Google's algorithm differentiates between CIS and Cis while DuckDuckGo's does not. However, the only one we directly control lands on the disambiguation page. So I'm not convinced there's much we can or should do. Dave (talk) 15:27, 19 June 2024 (UTC)[reply]

    What to do with near-empty lists of names of obscure asteroids?

    AtWikipedia:Articles for deletion/Meanings of minor planet names: 500001–501000, it was suggested to start a broader discussion about what to do with these lists. We have now 568 (and counting) such lists (Category:Lists of meanings of minor planet names, and while the lower-numbered ones are about notable subjects where the lists are perfectly acceptable as is, the higher-numbered ones are a collection of explanations of the names of obscure asteroids, named after obscure people (e.g. the great-grandfather of the discoverer of the asteroid, Meanings of minor planet names: 623001–624000). Should these be deleted, merged, ...? Simply keeping something like Meanings of minor planet names: 618001–619000, a one-entry list sourced to a primary source, seems to go against all notability guidelines and what is accepted for other topics. And where is the cutoff between the notable ones and the non-notable ones? All ideas to help write an RfC or other proposal about this are welcome. Fram (talk) 07:51, 20 June 2024 (UTC)[reply]

    One problem here seems to be that the structure of the lists that makes sense for the first 20k or so entries is extended to 700k entries. Aggressive merging into larger lists covering 10k-100k asteroids each would already substantially improve the usefulness of these. —Kusma (talk) 09:09, 20 June 2024 (UTC)[reply]
    I looked at Meanings of minor planet names: 623001–624000. It ostensibly covers 1000 minor planets. It has ten ==Sections==, each of which is intended to cover 100 minor planets.
    The number of minor planets actually covered is: two (2). On the whole page. There are nine empty sections with nine empty tables, and one section containing a table that has information about two of them.
    I'm okay with the page only having a couple of entries; presumably some others will m:eventually get added. But I would like to consider a rule that says there should not be so many empty sections. IMO sections should be added when they're needed, not merely because the page exists. So that's one thing that could be discussed in an RFC: Should the structure be set up before there is content? WhatamIdoing (talk) 21:27, 20 June 2024 (UTC)[reply]

    Search engine for policy

    I think there should be a search engine for Wikipedia policy where you can put in key words and the relevant pages come up Alexanderkowal (talk) 22:50, 20 June 2024 (UTC)[reply]

    We have discussed putting policies in a separate hyphenated namespace as we do with the manual of style..... but to no avail yet. Pls see WP:GOVP for a whole bunch of different search boxes as seen down below..... that can be found on the namespace pages. You can also select this by the magnifying glass see Help:Searching.


    Moxy🍁 00:11, 21 June 2024 (UTC)[reply]

    But the MOS is in the project namespace? The MOS: redirects are in mainspace. Aaron Liu (talk) 00:20, 21 June 2024 (UTC)[reply]

    Because the MOS are subpages organized like Wikipedia:Manual of Style/search term you can narrow down a search to just the manual of style (as seen in the box below). If policy pages or guidelines were set up in the same manner it would be an easy search. ....like Wikipedia:Policy/search term. But one of the problems is the MOS is a guideline.... so the search parameter Wikipedia:Guideline/search term maybe confusing and give a multitude of results that aren't actually part of the MOS. It's a conundrum that has never really been solved. It is odd that it's easier to search for Wiki projects then our policy pages because of the hyphenated name setup Wikipedia:WikiProject/search for a project you're interested in Moxy🍁 02:19, 21 June 2024 (UTC)[reply]
    Don't we have searching in categories now? Aaron Liu (talk) 02:53, 21 June 2024 (UTC)[reply]
    Deepcat for policies seem to always fail for some reason. Normal incategory doesn't. Aaron Liu (talk) 02:59, 21 June 2024 (UTC)[reply]
    Those search boxes you’ve linked are really good, maybe have them on the page for beginners? Like the introduction to policy one Alexanderkowal (talk) 04:49, 21 June 2024 (UTC)[reply]
    The writing could be “Feel free to search some key words to start reading policy. Editors intimate with Wikipedia policy will usually link relevant policies in discussions.” Alexanderkowal (talk) 05:30, 21 June 2024 (UTC)[reply]

    Retrieved from "https://en.wikipedia.org/w/index.php?title=Wikipedia:Village_pump_(idea_lab)&oldid=1230199396"

    Categories: 
    Wikipedia village pump
    Wikipedia proposals
    Hidden categories: 
    Wikipedia move-protected project pages
    Non-talk pages that are automatically signed
    Pages automatically checked for incorrect links
     



    This page was last edited on 21 June 2024, at 09:27 (UTC).

    This version of the page has been revised. Besides normal editing, the reason for revision may have been that this version contains factual inaccuracies, vandalism, or material not compatible with the Creative Commons Attribution-ShareAlike License.



    Privacy policy

    About Wikipedia

    Disclaimers

    Contact Wikipedia

    Code of Conduct

    Developers

    Statistics

    Cookie statement

    Mobile view



    Wikimedia Foundation
    Powered by MediaWiki