Jump to content

Wikipedia:Village pump (proposals)

From Wikipedia, the free encyclopedia

This is an old revision of this page, as edited by Lowercase sigmabot III (talk | contribs) at 02:21, 29 March 2017 (Archiving 2 discussion(s) to Wikipedia:Village pump (proposals)/Archive 138) (bot). The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.

 Policy Technical Proposals Idea lab WMF Miscellaneous 
Shortcuts

New ideas and proposals are discussed here. Before submitting:


Renaming Category:WikiProject Infoboxes

I just want to alert people that there is currently a proposal at CFD for renaming Category:WikiProject Infoboxes to Category:Wikipedia infoboxes [1]. Personally, I have opposed this, as this is obviously a maintenance category. I don't understand the rationale behind the proposal. ---Steve Quinn (talk) 18:04, 15 January 2017‎ (UTC)[reply]

Proposal to submit blockers on replacing our wikitext editor

There is a strong consensus among the participants of the discussion to support both the proposals.Winged Blades Godric 12:30, 21 March 2017 (UTC)[reply]

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

Tracked in Phabricator
Task T154843
Tracked in Phabricator
Task T154844

The Wikimeda Foundation is working on a new software project called New Wikitext Editor (also known as NWE, or 2017 Wikitext Editor). The "new editor" is being built as a new wikitext mode within the Visual Editor extension. This allows the WMF to consolidate on a single editor with both Visual and wikitext modes. The plan is for this to become the default wikitext editor in a few months. The current wikitext editor would be temporarily retained as an opt-in in preferences, but eventually the current wikitext editor would be removed completely. Please view mw:2017_wikitext_editor for a more thorough explanation of the project, as well as the WMF's reasons for it. The new editor is available for opt-in testing under the Beta features section of Preferences.

The WMF is still working on a number of issues with the new software, however over the last few months several editors have raised a pair of issues which (in my opinion) they have not constructively addressed. Both of these issues appear to be a direct consequence of designing the "new wikitext editor" as a mode within Visual editor. The issues are:

  1. Slow load time, primarily on larger articles. Different people may experience different load times, but I will report my experience. With the current wikitext editor I am able to start editing the article United States within 3 seconds after clicking edit. (The toolbar at top took a moment longer to finish loading, but that does not obstruct editing.) The new editor took 30 seconds to load before I could begin editing. With the current wikitext editor it took 5 seconds until I could edit our largest article (List of named minor planets (numerical)). With the new editor my load time was 127 seconds.
  2. Faulty previews. The new editor does not provide genuine article-view previews. Instead it uses the Visual Editor rendering engine for previews. This results in a large assortment of things that render incorrectly in preview, or fail to render at all. The WMF has been working to address these issues for years as part of the Visual Editor work, and they plan to continue hunting down and fixing many of these rendering problems. However the WMF has indicated that some of these rendering problems are CANTFIX or WONTFIX. They hope to address the common cases, and their goal is to eventually get 99+% correct previews.

The WMF has been developing a Technical Collaboration Guideline. According to the guideline, the community is invited to submit "actionable blockers" on any software project. These are issues that block deployment unless/until the issues are adequately resolved. This RFC is seeking consensus to formally submit the one or both issues as actionable blockers. You may support one issue as a proposed blocker while opposing the other.

EDIT FOR CLARIFICATION: The WMF has been developing a Technical Collaboration Guideline. It is currently a draft. At least one WMF staff member has been actively seeking to test the guideline in action (Qgil-WMF) and another WMF staff member subsequently requested removal of any mention of the guideline (Keegan (WMF)). Editors are reminded that it is merely a draft. This RFC could be interpreted by the WMF as a test of their draft best practices for collaboration with us, or it could be interpreted as some generic consensus on the New Editor's prospects for successful deployment if specific issues are or are not addressed, or it could be interpreted in some other manner. In any case, our goal is to work with each other as partners in a positive and constructive manner, seeking to serve our shared mission to the best of our ability. Added: Alsee (talk) 20:27, 19 January 2017 (UTC)[reply]

Proposals:

  1. Actionable Blocker: Load time. Load time is a priority concern for both new editors and experienced editors. Possible resolutions:
    • We could happily retain our current wikitext editor; or
    • if possible, drastically reduce New Editor load times, particularly on large pages.
  2. Actionable Blocker: Article previews. Previews are a critical part of the learning process for new editors, as well as a critical tool for experienced editors. Inaccurate previews will confuse, disrupt, and frustrate. Possible resolutions:
    • We could happily retain our current wikitext editor; or
    • previews must use the article-view rendering engine (this is called the PHP parser), as well as any other relevant parts of the article-view software stack. This fixes the assorted rendering errors all at once, and it ensures that previews remain synchronized with article views when any changes are made to the software.

Alsee (talk) 00:04, 17 January 2017 (UTC)[reply]

Responses

  • Support both. The load time on large articles is gross, and using an entirely different rendering engine for previews was a bizarre design decision. Unless both of these issues are adequately resolved, our current wikitext editor is clearly superior to the proposed replacement. If it ain't broke, DON'T BREAK IT! Alsee (talk) 23:52, 16 January 2017 (UTC)[reply]
  • Support both Loading time is a problem with VisualEditor, I am guessing that it's a problem with Parsoid. And the preview engine should use the parser, not it's own software, otherwise it's just reinventing a wheel. A square one most likely. Jo-Jo Eumerus (talk, contributions) 00:08, 17 January 2017 (UTC)[reply]
  • Strongly oppose removal. To clarify, strongly support both (03:58, 17 January 2017 (UTC)). On some very large pages the text editor takes a bit to load, let alone the JavaScript-heavy visual editor. The visual editor has its uses and I support keeping/improving it, but making it the sole option would definitely make it harder for me to edit. Daß Wölf 01:34, 17 January 2017 (UTC)[reply]
    It is a mischaracterization to say that the WMF is making the VE the sole option--it is that both the VE and the 2017 WTE use the same root software. --Izno (talk) 13:43, 17 January 2017 (UTC)[reply]
    Thanks for your reply, I wasn't aware that VE and 2017 WTE were different things. Still, new WTE also has bad loading times. For example, the minor planets list referenced by Yodin below takes about 20 seconds to render in reading mode, 5 seconds in normal edit source (less than reading mode!), 114 seconds in new edit source and at least 5 minutes and 12 timeouts in VE (I gave up). This page takes around 2.5 seconds in both reading mode and old edit source and 21 seconds in the new edit source. In both cases loading the new edit source caused prolonged browser freezing and delayed keyboard and mouse response as long as the minor planets page was opened in a background tab. I'm going with "don't fix what ain't broke" here. Daß Wölf 01:10, 18 January 2017 (UTC)[reply]
  • Support both. I'd rephrase the first one as "loading times must be less than or equal to the current wikitext editor". Previewing using Parsoid is a mind-bogglingly stupid decision, especially when proper previewing is just an API call away. MER-C 02:59, 17 January 2017 (UTC)[reply]
  • Support load time as a blocker. Do not support previews as a blocker. Previews are pretty gosh-darn close. --Izno (talk) 13:43, 17 January 2017 (UTC)[reply]
    Dear Izno, would you submit an edit when you can't preview it? --NaBUru38 (talk) 00:13, 24 January 2017 (UTC)[reply]
    @NaBUru38: You can preview your edits in WTE2017, though the workflow is a little wonky: Click "Save Changes", and in the box that pops up is an option "Show preview". There's a task open to pull the "preview" button onto the main editing screen at phab:T153306. The original poster of this discussion is making the distinction that previews are not 100% equivalent to the PHP parser (which is a fact, but lacking the context that something like 99%+ renders using Parsoid are correct), not that they don't exist. --Izno (talk) 00:27, 24 January 2017 (UTC)[reply]
  • Support both as I will any other reasonable measures that may achieve allowing us to "happily retain our current wikitext editor". — Godsy (TALKCONT) 13:46, 17 January 2017 (UTC)[reply]
  • Weak support 2, wary about 1. Load times are going to vary from computer to computer and browser to browser, and I think it's hard if not impossible to explicitly say that a specific measured load time applies to everyone. I support the idea of 1, that load times should be at worst comparable to the current editor, but I'm not sure that in practice this is something that could be a certain result. As for 2, I'm fine with the current previewer (I assume there's a good reason for using it), provided it reaches parity with the old one and is consistent with the saved contents of the page. For the record I very much support the new text editor, and apart from the unintuitive copy/paste behaviour (being debated elsewhere I believe), will be happy to use it. Sam Walton (talk) 15:48, 17 January 2017 (UTC)[reply]
  • Support both noting that 2 is particularly egregious. Also comment that I do not want the current wikitext editor to be dropped for a very long time. BethNaught (talk) 15:51, 17 January 2017 (UTC)[reply]
  • Support both Having a resource heavy GUI as the only option would prevent a lot of contributions from editors who don't have the hardware or bandwidth to handle it, which defeats the object of wikimedia encouraging grassroots participation. Not everywhere is wikisilicon valley. In addition inaccurate rendering of previews can cause countless problems, direct and indirect.Cesdeva (talk) 22:41, 17 January 2017 (UTC)[reply]
  • Oppose I've been using the new source editor since the beta was announced and haven't run into anything like the load times you describe. I'm also not sure the "preview" issue is nearly as serious as you present it; many of the cases in which the preview is substantively inaccurate are pathological in the first place (i.e. you shouldn't be doing whatever it is that's causing the renderer to barf). There are definitely some irritating usability issues, but neither of the items on your list seems worth throwing a wrench in the works over. Opabinia regalis (talk) 23:25, 17 January 2017 (UTC)[reply]
  • Support both. I have a decent computer, but don't have broadband, and decided to try both of the examples given above. United States: in the current editor took 4 seconds before I could start typing, and 6 seconds before the full page loaded; in the new Visual Editor text mode, it took 35 seconds! Then List of named minor planets (numerical): in the current text mode it took me 8 seconds before I could start typing, and 14 seconds for the entire page to load; in the new editor, it took 90 seconds before timing out, then timed out again at 120 seconds, and took about 122 seconds in total to load. As pointed out above, these figures are just anecdotal, but now that the issue has been raised, please provide reliable stats on a range of modern and old devices, at various internet speeds and in various countries – we don't want to become "Wikipedia, the encyclopedia that anyone with a fast enough connection can edit"! I'm genuinely pleased for people who enjoy using the Visual Editor, and wouldn't want to take it away from them, but likewise please at least provide an option that will allow me and others in a similar position to keep editing. ‑‑YodinT 00:29, 18 January 2017 (UTC)[reply]
    • The best answer to the problem with List of named minor planets (numerical) is that 1.12MB is just too big for one article. I hope the people responsible for the 26 views per day via mobile aren't actually using their mobile data for that. Opabinia regalis (talk) 01:28, 18 January 2017 (UTC)[reply]
    • Speed varies considerably per account, browser, device, and location. For example, it took me just six seconds in Safari 10 and nine seconds in Firefox 50 to open United States in the wikitext mode of VisualEditor – much less than the time it took your computer. In Safari, VisualEditor's wikitext mode is slightly faster than reading the page; in Firefox, loading the page in read mode is one second faster than opening it to edit.
      The team has a standardized system for testing this. In general, the results are that short pages take faster than long pages; that VisualEditor is faster in Europe and Africa than in North America; that any method of editing wikitext is faster than anything that shows a lot of images (e.g., reading a page); that newer computers are faster than older computers; and that IPs and new editors have faster load times than experienced editors (who tend to have a lot of performance-harming scripts in their accounts). For a reasonable sample of pages (i.e., not just the longest ones), when editing as an IP (e.g., with no scripts or gadgets), with nothing else running (e.g., no other scripts running or tabs refreshing in the background), in a highly standardized setting, the time-to-open speeds are approximately the same for VisualEditor's built-in wikitext mode vs the 2010 wikitext editor.
      And then you impose all of the real-world, non-standardized conditions that affect each of us, and the answer becomes: Who knows? Your experience is your real experience, and whether your experience is fast or slow, it's not safe to assume that the next editor will have the same experience. Whatamidoing (WMF) (talk) 19:33, 19 January 2017 (UTC)[reply]
  • Oppose (edit conflict) both procedurally and on the merits. Firstly, the technical guide is still a draft, it's not a guideline like the proposer states. I think it's far too premature to start implementing things from it. Secondly, the draft says that "Development teams participate in the discussion focusing on the proposed blockers (whether they are sensible, consistent with the project, actionable, realistic…)" so I am hesitant to make any decisions until the proposer shows they've discussed this with the devs or until the devs actually participate in this discussion. Thirdly, the purspose of "actionable blockers" is that they be actionable, they, in my mind, need to have clearly defined criteria for when they have successfully been actioned. Neither the proposal nor the draft technical guide adequately lay out how it is determined that an actionable blocker has been overcome. The draft says: "If the development team solves the blockers, the community will be asked for a new review. If no surprises are found, the deployment will proceed." What constitutes "surprises"? What is the threshhold for these proposed actionable blockers? Load times are highly variable, how will we determine an adequate level of load time? What if we just happen to have a discussion full of people contributing via Windows 95 who oppose the re-review? More likely, what if we just keep inflating our standards saying it's not fast enough or the preview isn't good enough in order to filibuster implementation? Wugapodes [thɔk] [ˈkan.ˌʧɻɪbz] 01:37, 18 January 2017 (UTC)[reply]
  • Support both. Both have long been known as serious VE problems, to introduce these (and other VE problems) into normal editing would be a very bad idea. Fram (talk) 09:32, 18 January 2017 (UTC). To be sure these are still problems, I switched on the new Wikitext mode again, and edited Leuchtenberg Gallery. Not only does it take too long (15 seconds!) before I can start editing, the preview doesn't give ma good idea of how the page will look eventually (e.g. by eliminating the left sidebar, increasing the width of the page). On a second try, I first did "review changes" and from that window "preview", with the result "Error loading data from server: Failed to connect." This happened three times in a row. I could still edit the page and review my changes, so connection wasn't really lost... On preview, I don't get to see redlinks. This is one of the essential elements of preview for me, as it allows the correction of bad links before saving. Opening Exposition des primitifs flamands à Bruges first returns the standard editor for some reason, a second try gives me the new wikitext editor, but only after 50 seconds, which is way too long. I added an image, asked for a preview, and again got "Error loading data from server: Failed to connect.". In standard editing mode (I at this point switched back, quite relieved that that option still existed) opening the page took a few seconds, previewing went without any problem and showed the page as it would look after saving, including redlinks and the like. Fram (talk) 10:00, 18 January 2017 (UTC)[reply]
  • Oppose. I use primarily use the Visual Editor for content work and find the Parsoid preview adequate 99% of the time. In the few instances where it's troublesome (e.g. not seeing references), there's a very easy workaround: save the page. Excessive load times are a concern, but the proposed "blocker" is too vaguely worded to achieve anything. It seems to me that submitting a phabricator ticket asking for it to be profiled and reduced would suffice (if one doesn't already exist). – Joe (talk) 10:12, 18 January 2017 (UTC)[reply]
    • A. It seems a bit rude for someone not affected by this change (since you are a VE user) to oppose those who are affected by this change. B. "Saving" is no workaround for previewing, previewing is also meant for testing, but the mainspace is no place to test things. Of course, one can copy a page to a sandbox, comment out the categories, and then start testing, but this is no longer an "easy workaround" but a lot of haasle. C. Excessive load times of VE have been noted from the very start of VE, and numerous times since then[2], but have four (five, whatever) years later not been corrected. Yet another phabricator ticket won't solve this. (the "redlinks should be red" issue has been a ticket for more than a month now[3], no activity as far as I can see; other issues also are already phab tickets). Note that the new editor also seems to break some well-used gadgets and tools like Twinkle, apparently (I haven't tested this). Fram (talk) 11:00, 18 January 2017 (UTC)[reply]
      • Fram, the new editor is an entirely new system. Gadgets and scripts will need to be rebuilt from scratch. That adds a one-time cost to switching, but I think it's fair to primarily focus on long-term pros and cons. (Although I'm not really seeing a long-term pro to the new editor.) Alsee (talk) 22:32, 18 January 2017 (UTC)[reply]
      • @Fram: I said primarily; I also use the wikitext editor so I'm as "affected" as anyone else. After seeing this I opted into the NWE beta and haven't experienced any appreciable slowness, making me think that this, like the very few edge cases where Parsoid previews aren't sufficient, isn't a hugely critical issue. We can't keep obstructing the WMF's efforts at improving our antiquated interface because the new versions have a few bugs. All new software has bugs. – Joe (talk) 09:23, 19 January 2017 (UTC)[reply]
  • Support both, On point one, as a regular editor from developing countries the last thing I need is even slower download times. On point two, I'm mystified at the idea of a preview function that doesn't render the page as it would if you saved it. -- Euryalus (talk) 11:14, 18 January 2017 (UTC)[reply]
  • Support both. Slower loading times are an issue for developing countries and mobile users who don't like the mobile interface (I know I'm not the only one). But having a preview that doesn't render the page exactly like it appears when saved (even if it is just a missing sidebar) is daft. As Alsee said, if it ain't broke, don't break it. There's no reason to eliminate the plain text editor; far from simplifying things, the proposal to ultimately eliminate it is a switch to a more resource hungry process for no real benefit. oknazevad (talk) 23:00, 18 January 2017 (UTC)[reply]
  • Support both The optimism that allows programmers to ply their trade often leads them down strange paths, but none stranger than thinking these features should be imposed on everyone, with performance details on the todo list. Just save your edits for a true preview! That must be what was behind the fuss a couple of months back when someone dropped into WP:VPT to tell template/module writers they should not show extra error messages during preview. Johnuniq (talk) 23:04, 18 January 2017 (UTC)[reply]
  • Support both per every single support listed here. I tried the new editor and did not enjoy it. If they do go ahead and bring the new wikitext editor out of beta, they must keep the old editor. — Gestrid (talk) 05:46, 19 January 2017 (UTC)[reply]
  • Support both These sound like serious issues that need to be addressed. Change always makes me a bit uncomfortable, especially when there are problems. Also Support keeping old editor, as I think many editors would consider leaving if it was taken away, and we already have editor retention problems. Tamwin (talk) 05:50, 19 January 2017 (UTC)[reply]
  • Support both per Euryalus. Ealdgyth - Talk 15:36, 19 January 2017 (UTC)[reply]
  • Support both Don't fix what isn't broken: current editor working perfectly on my end. Psychotic Spartan 123 18:43, 19 January 2017 (UTC)[reply]
  • Support both. Just tried it, clearly noticeable speed difference and the "preview" is unacceptable. Echoing BethNaught in that I do not want to see the current source editor (which is actually functional) to be removed. In what ways is the new source editor superior, other than "easy switching" (which is negated by the long load times of VE to start with) and the toolbar (whether that is even superior to the current setup is debatable)? This is a sham referendum, not that I expect any better from the WMF. feminist 09:38, 31 January 2017 (UTC)[reply]
  • Support both. And under no circumstances should the existing source editor be removed. Peter coxhead (talk) 09:53, 31 January 2017 (UTC)[reply]
  • Support both. Offer it as an option, but don't try to impose it on everyone, especially not with increased load times and preview that doesn't preview. SarahSV (talk) 15:58, 31 January 2017 (UTC)[reply]
  • Support both and do not remove the existing editor. ThePlatypusofDoom (talk) 18:20, 31 January 2017 (UTC)[reply]
  • Support both I support anything that obstructs WMF. Chris Troutman (talk) 20:19, 31 January 2017 (UTC)[reply]
  • Support both per above. The current wikitext editor is not broken. -FASTILY 22:16, 31 January 2017 (UTC)[reply]
  • Support both for all the reasons given, plus.
    • Previews are necessary: Opabinia regalis said
      I'm also not sure the "preview" issue is nearly as serious as you present it; many of the cases in which the preview is substantively inaccurate are pathological in the first place (i.e. you shouldn't be doing whatever it is that's causing the renderer to barf).
      I don't know what you use previews for, O. regalis, but a large part of their value for me is spotting errors of execution as well as errors of intention. For example, last night on my mobile I added a rather complex "cite" ref, incorporating a template call as the last item. When I tapped Next for the preview, I got an "unclosed reference" error (or whatever the wording is). It turned out that in the steps of constructing the ref, which involves a good bit more moving around on a smartphone than on a computer, instead of inserting the double double curly closing braces at the end (}}}}) I'd lost track and only inserted one pair (}}), and as a result the "</ref>" and everything after it got swallowed up as part of the citation. This is not "doing something pathological that caused the renderer to barf" in the apparently snarky way you used it. This is called "checking your work", and we all should be doing it regularly.
    • Loading time. If you think it's slow on a computer, be glad you're not using a mobile. I get fairly frequent browser crashes, and I'm sure some of them are due to timeouts.
    --Thnidu (talk) 00:10, 2 February 2017 (UTC)[reply]
  • Support both. If WMF really does adopt the concept of project-by-project blockers, I would welcome that improvement. Here, I think both issues are meaningful, and I see no reason to implement anything that has significant problems. Most of us are here to edit an encyclopedia, not to beta-test software that does not even address the issues that we care about. --Tryptofish (talk) 00:03, 3 February 2017 (UTC)[reply]
  • Support both – It is supposed to be an upgrade, not a downgrade. And what is going to happen to WikEd? The Transhumanist 19:53, 6 February 2017 (UTC)[reply]
  • Support load time as a blocker. I can live with the bad previews, but the slow load times will actually limit my editing activity. I frequently edit from countries where internet access is quite slow and having to wait more than a minute to edit a page isn't workable for me. I'm sure other people with slow internet access feel similarly. Kaldari (talk) 01:57, 12 February 2017 (UTC)[reply]
  • Strong oppose, we should keep ONE editing mode and ONE reading mode. On other Wikipedias have I noticed that it's possible to wright directly in to the text. This
  1. causes confusion
  2. the "direkt wrighting" will attract pure vandals
  3. there is no obvious benefit, with a new way of editing Wikipedia

Boeing720 (talk) 02:21, 14 February 2017 (UTC)[reply]

Note: Boeing720 explained[4] that they were attempting to oppose VisualEditor on EnWiki. Visual Editor is already here. This proposal is about a change to the wikicode editor. Boeing720, you may want to strike or revise your !vote here. Alsee (talk) 09:52, 21 February 2017 (UTC)[reply]
Alsee is 100% correct, like anyone who reads my explanation will understand. I made a huge mistake by turning the proposal. I Strongly support both. Sorry for the confusion I may have caused. Boeing720 (talk) 10:11, 21 February 2017 (UTC)[reply]
  • Strongest possible support on the load time. Long load times make editing a chore, so quick fixes of simple errors are likely to be left alone. Editing in general will be discouraged. Support on the rendering. VisEd still can't render links properly? After all this time, that is totally sad. SpinningSpark 19:42, 18 February 2017 (UTC)[reply]
  • Support on load times. I have just come back from the Phillipines. It was nearly impossible to edit even with the faster load times of the wikitext editor. If the only option becomes an even longer load times less of the world is going to be able to contribute. Also there is no "color coding". The color coding of WikEd is essential. The cite tool still adds unneeded urls when the pmid is give (this too needs fixing) Doc James (talk · contribs · email) 16:12, 20 February 2017 (UTC)[reply]
  • The New Visual Editor =should replace the old Visual Editor, not the old wikicode editor. --NaBUru38 (talk) 13:04, 19 March 2017 (UTC)[reply]

Discussion

  • Does anyone else think the current pasting behavior is weird, too? Whenever I copy a part of a page title and paste it, I want to get the text that I copied, not some empty bulleted lists and other wikitext cruft. Enterprisey (talk!) 03:03, 17 January 2017 (UTC)[reply]
    There's at least one currently open task for that. --Izno (talk) 13:50, 17 January 2017 (UTC)[reply]
    Enterprisey, the WMF is aware of the copy-paste issue. They'll address it. The ability to paste something like a fully formatted table could be really nice in some rare cases, but plaintext is what we want in nearly 100% of cases. Right now they are leaning towards the idea that a single line copy would be plaintext paste, and a multi-line copy would be markup-code paste. (I think that's probably the wrong fix, but I didn't comment on that.) Another idea is that ctrl-V would always paste plaintext, and ctrl-shift-V would always paste markup-code. (That's probably the better fix, but it would be hard to discover that ctrl-shift-V even exists.) The WMF will happily give us whatever we want. Alsee (talk) 14:52, 17 January 2017 (UTC)[reply]
  • Once again, Alsee, you refer to a "large assortment" of rendering failures in the Parsoid previews, without providing a link or reference to help editors understand what you are talking about. With the exception of the fact that red links do not appear red (an obviously severe flaw that needs to be fixed), it seems to me that most of the issues that you are referring to are in fact obscure and rarely encountered. It would be helpful if you could link to or provide some examples of wikitext that does not preview as you expect. That way, editors can judge for themselves whether the problem is indeed as serious as you make it out to be. — This, that and the other (talk) 14:02, 17 January 2017 (UTC)[reply]
    This, that, I considered putting various examples in the RFC, but (1) I didn't want to bloat it up with a huge list, (2) the list that *I* happen to have compiled is an clearly an insignificant fraction of the issues that exist, and (3) I think the fundamental issue is broken previews, even if some of the cases are rare. I said in the RFC that the WMF is hoping to fix the common issues, and is aiming for 99+% accurate previews. If you think the exact list is important, then perhaps the WMF should compile a list. I'll happily contribute my pile of examples. Table of contents is missing. Redlinks, black links, external links, PDF links all show as plain blue links. Some links in the preview point to the wrong place... clicking them or opening-in-new-tab takes you to the wrong page. Markup on a link can completely break the link. Images can display in a completely wrong section (I haven't investigated why). Audio and video aren't included in the preview at all (they are replaced by a speaker-image). Oddly placed comments can break the preview. Some things that should be on one line are split onto multiple lines. Some elements - even entire paragraphs - can display in the wrong order. REFs can be missing from the reflist. I have multiple cases where it fails to render section-titles. Templating a template-name is is broken. Definition lists can render wrong. Some uses of elements like <code> <tt> and <s> can completely trash the preview. It can badly mangle table structure. Cases where stuff like <sub> doesn't get applied. Markup like #if can badly break if Parsiod doesn't like how it's arranged. And more. Some issues are related to Tidy, and the WMF is planning to remove Tidy, but so long as Tidy is part of the article view then Tidy must be part of the preview. And again, I'm sure the WMF can come up with far more examples than I have. And I'm sure that new examples will keep popping up. So let's consider the issue here as fix the endless render bugs that no one has listed yet, anywhere. In which case any particular list is irrelevant. Alsee (talk) 15:32, 17 January 2017 (UTC)[reply]
  • I would also add that I forgot to switch off the VE before editing the above section... and for some reason was given the entire html of the page instead of the wikitext of just the section, <!DOCTYPE html><html prefix="dc: http://purl.org/dc/terms/ and all. I didn't dare click preview... ‑‑YodinT 00:34, 18 January 2017 (UTC)[reply]
    It's a problem I've been experiencing since the last software deploy. I believe that Parsoid is showing us the internals of the page (incorrectly). I would guess there's a phabricator task for this problem at this time but I haven't gone looking (nor have I reported one). It is well you did not save; I find that bypassing your cache fixes the problem. --Izno (talk) 01:10, 18 January 2017 (UTC)[reply]
    @Yodin: And I didn't see another task in Phabricator, so I've added one; tracked at phab:T155632. --Izno (talk) 15:26, 18 January 2017 (UTC)[reply]
  • I tried the beta for this just now. I noticed the formatting issue when pasting text. That wasn't too bad but there was a major hiccup when I was using it to post an entry in a big RfC. There was an edit conflict and I chose the option to handle this manually. The resulting edit took an 86K bite out of the discussion. That was quite alarming so I reverted my edit immediately. I have stopped using the beta now as it's taking me too far out of my comfort zone when I want to get things done. Andrew D. (talk) 14:05, 18 January 2017 (UTC)[reply]
    @Andrew Davidson: This is tracked at phab:T154217. --Izno (talk) 15:14, 18 January 2017 (UTC)[reply]
  • The Technical Collaboration Guideline is a document of guidance in communications that is in mid-draft and has nothing to do with this. It does not call for actionable blockers as framed here. Remove its mention, please. Keegan (WMF) (talk) 07:41, 19 January 2017 (UTC)[reply]
  • Specifically, the very first line says "This is a recommendation for software projects following the Technical Collaboration Guideline (TCG)". No project is following the TCG since the thing is still being written. More importantly, the guideline is not a guideline in the sense of the word that the English Wikipedia knows, a form of directive. It's help, that's all. To the point: you can't put something under rules it doesn't qualify for, and that aren't rules to begin with. Remove its mention in the proposal. Keegan (WMF) (talk) 07:49, 19 January 2017 (UTC)[reply]
Keegan (WMF), I have added a clarification on this issue. I hope you find it constructive and satisfactory. Alsee (talk) 20:29, 19 January 2017 (UTC)[reply]
I think the entire mention could have been taken out and the intent of the request is clear - I still think that's the better way to go, but meh. What I do not want is to see this as any sort of test or use of the TCG aside from "as an example." If that is your intent, that's fine. I'm working on building collaborative frameworks for the future years, and great harm can come from using them before everyone agrees and we're all ready. I hope you can appreciate that perspective. Keegan (WMF) (talk) 21:02, 19 January 2017 (UTC)[reply]
  • This seems like a pretty pointless discussion, from a developer's perspective. Not sure what it is trying to accomplish. This feature is not being released yet, the feature is not bothering any of the people who are voting here, the previews will be aligned at some point in the next 1-2 years (mostly because maintaining 2 parsers is gonna be problematic), there is no plan to remove the current editor. If someone wants to be useful and constructive however, they could assist in some prototyping work, testing, design feedback etc etc. instead of nurturing your inner Statler and Waldorf. —TheDJ (talk • contribs) 01:49, 20 January 2017 (UTC)[reply]
    • "probably in mid-2017, we'll begin to provide it by default in place of the current wikitext editor"[5] If the WMF plans to roll out a new default editor in mid-2017, then early 2017 seems like the perfect time to discuss whether this really is fit to be the default editor, and which things surely need correcting before this can happen. The result of making this the default editor would be that new editors would encounter three editing environments instead of two (luckily we don't have Flow), as it has been shown here that there are circumstances where you always get the old wikitext editor, even if the new one would be the default. Sending out the message to the WMF that this is not acceptable is best done in time and not at the last minute (or even worse but rather typical, the WMF implements this, then a consensus emerges that we don't want it, the WMF refuses to roll it back because that would be too complicated or "confusing for new editors" or some similar excuse, and only after a long and bitter dispute does the WMF relent). This is a Beta, no one is arguing to end the availability as beta feature, but the stated plans by the WMF to roll out this out as the default in a few months time are simply premature. To dismiss this as "unconstructive" and "nurturing your inner grumpy old men" and adding the rather disingenious "this feature is not being released yet" (no, but it would be very stupid to wait with this discussion until it is released, wouldn't it?) is typical "shut up" behaviour of WMF supporters and not helpful, constructive, or open-minded at all. You could instead take the comments made in this very discussion as "testing and design feedback" and be happy that people care and voice their opinions. Fram (talk) 08:29, 20 January 2017 (UTC)[reply]
    • This is design feedback. An editor with broken previews and atrocious load times is clearly inferior to what we have, and should not be deployed unless the issues are resolved. Your suggestion that no issues should be addressed until deploy phase is silly. A primary reason the WMF has been developing the Collaboration guideline is to avoid having these sorts of issues (and RFCs) pop up at the last minute, during deploy. The best time to address issues is as early as possible, preferably during concept and design phase. Unfortunately there was no project page or information available until after it was built. Alsee (talk) 13:11, 30 January 2017 (UTC)[reply]
  • Comment - (sigh) I don't understand why there always seems to be so much effort going on in this project to create alternatives to things that already work fine. I hope this isn't where the money goes that is donated to Wikipedia, which I'm sure that the donators assume is used for maintaining servers and organizing the development of the encyclopedia. That said, load times of software under development are often high, because of bloat left in for testing purposes and emphasis on functionality over speed in early phases. We can only hope that sincere efforts at optimization take place before the deployment.—Anne Delong (talk) 12:40, 7 February 2017 (UTC)[reply]

Third blocker: undo no longer works?

  • Apparently from every page, if I am at "View History" (instead of "read") and then press "edit", I get the old editor instead of the new one. Apparently a page must be completely loaded in read mode before the new wikitext editor can be used. This would also mean that something like UNDO would no longer work when the new wikitext editor would be the only available editor. This seems to me to be a major blocker as well. Can others reproduce this and confirm this technically? Fram (talk) 11:18, 18 January 2017 (UTC)[reply]
    You're mischaracterizing the WMF's plans re the new editor, so far as I'm aware. It is not that there will be no other way to do it, but that the wikitext editor which will be available when e.g. Javascript fails to load will be a simple and plain text field (rather than include the editor bar and other such items). That said, I have reproduced that error multiple times, though no discrete steps for it (I think it's just clicking the 'undo' button, but I could be wrong). --Izno (talk) 13:04, 18 January 2017 (UTC)[reply]
    As long as the old wikitext editor remains, undo should keep on working, if they start it by default anytime the new editor fails (instead of e.g. only allowing it for people who have turned off the new editor explicitly). What their promises to keep the wikitext editor around are worth is anyone's guess of course. And obviously that "read - edit" gives a different result than "view history - edit" is perhaps not a technical blocker, but is it indicative of the total lack of adequate testing at the WMF, the thing that already sinked so many of their pet projects. The things that get discussed here are not exceptional occurrences or edge cases, these are basic functionality and actions. Fram (talk) 13:49, 18 January 2017 (UTC)[reply]
    I agree that undo is a regression--and I think their intent to keep a basic text box form is pretty sound because we do need to provide some support for Javascript-less users. --Izno (talk) 15:08, 18 January 2017 (UTC)[reply]
    Having activated and desactivated the new wikitext editor beta a few times, I now have all kinds of problems. At the moment, the beta (new editor) is activated: on most articles, I only get the old editor, and on some pages (e.g. Sumathi Murthy) I can,'t edit at all. This page has now opened in the new editor though (I thought it only worked in mainspace and user space?). Further testing confirms that I now can edit pages in the Wikipedia space with the new editor, but not in main namespace. I think I can safely conclude that this thing is far from ready to become a non-beta feature, never mind the default wikitext editor. Fram (talk) 14:28, 18 January 2017 (UTC)[reply]
    That sounds more like your cache is wonky. You should consider clearing it. --Izno (talk) 15:08, 18 January 2017 (UTC)[reply]
    Izno, Fram, I've also had issues where it seems random which editor starts up, and where turning the new editor on or off in preferences doesn't seem to take effect, among other problems. Bypassing local cache with shift-reload does not fix the issue. If it's a cache issue, it seems to be the server cache. I've also had cases preview fail to work at all, returning server errors. I suspect it's related to Parsoid, as I was trying to preview an article which the WMF had listed as generating a Parsoid roundtrip semantic error in their automated testing. Alsee (talk) 23:21, 18 January 2017 (UTC) On second thought, it might have been an article that generated Parsoid timeout in the automated testing. Alsee (talk) 23:45, 18 January 2017 (UTC)[reply]
    @Alsee: Yes, there's a handful of tasks documenting issues related to the 'wrong editor' in Phabricator. With Fram however "activating and deactivating a few times", that's not going to go well, I should think, and I'm pretty sure I've seen advice regarding other "Beta"-tab projects to the effect of "try to avoid turning things off and on multiple times". --Izno (talk) 23:54, 18 January 2017 (UTC)[reply]

My biggest failure mode with VE is undo failing. If there is any cut & paste in my undo buffer, trying to undo that step often fails in an odd way, and I have to reconstruct my edits piecemeal. If that's what Fram is talking about, and it would apply to NWE editing, that seems like a major issue to me as well. Not as big a blocker as performance, but significant for complex edits. – SJ + 22:28, 19 March 2017 (UTC)[reply]

There is no plan to remove the old wikitext editor

I have seen comments now on multiple pages that say something like, "eventually the current wikitext editor would be removed completely" – with the implication that this is definitely planned and will happen soon.

If we use a typical definition of "plan" like a "list of steps with timing and resources, used to achieve an objective" (to quote the article), then there is no plan to remove any of the wikitext editors from any WMF site. It would be far more accurate to say that the Editing department (and anyone who's been around computing for more than a few years) has a reasonable expectation that none of the current software will be used a hundred years from now, or even a few decades from now. So, sure, it's technically true that "eventually the current wikitext editor would be removed completely": someday, it presumably will be. However, it's also technically true that "eventually" I'm going to die (as will all of us) – and AFAICT it's still an open question as to which of those events will happen first.

On the other hand, I believe that we are all going to outlive the old parsing system, which is what the second proposed blocker concerns. They are planning to remove the old (HTML4-based) parser and to use (HTML5-based) Parsoid for saving all pages, no matter which of the many editing tools you're using. This epic project will certainly not be finished during 2017, but when it is finally completed, the odd differences between the two parsers will simply disappear. (One example: should [<!-- Invisible -->[Text]] produce a normal wikilink or should it display all the characters on the page or should it display the brackets but not the invisible HTML comment?) 

If you are interested in this project, then I recommend that you join WP:WikiProject Check Wikipedia. The first major step in replacing the old parsing system is described at mw:Parsing/Replacing Tidy; basically, some typos in HTML codes (e.g., someone typing </br> rather than the correct <br>) will no longer be silently fixed. (NB: This initial set of disruptive changes would have to happen even if Parsoid didn't exist; the library is unmaintained and outdated.) Whatamidoing (WMF) (talk) 07:25, 19 January 2017 (UTC)[reply]

@Whatamidoing (WMF): When you say that Parsoid will be used to save all pages, do you mean that pages will be saved in Wikitext but rendered with Parsoid, or saved in Parsoid HTML and round-tripped to Wikitext for source editing? I hope the former, as the latter will inevitably cause dirty diffs, and if made retroactive will change historical Wikitext revisions. BethNaught (talk) 09:00, 19 January 2017 (UTC)[reply]
I mean that what we've called "the parser" for years (Parser.php and a string of other supporting pieces in that system) will be completely removed – gone, not used, completely unavailable, deleted from the servers, given a death certificate that lists bitrot as the primary cause of death, etc. If you use (for example) the oldest, Javascript-free wikitext editor to save a change today, the resulting wikitext revision is currently turned into HTML by the old parser so that a reader can read it. When (2018? 2020?) the switch to Parsoid-based rendering is completed, even if you use exactly the same editor, the resulting revision will be turned into HTML by Parsoid instead. This change should have no practical effect on most Wikipedians, although I suppose that people may someday wonder why "obvious typos" like </br> were overlooked in articles for years. The change will be retroactive in the specific sense that it will no longer be possible to use the old parsing system to render any pages, so if you go look at a revision from 2003, then you will see how Parsoid turns it into HTML5, rather than how the old parser turned it into HTML4. (This is not very different from what we have now, since "the old parser" has changed quite a lot during its existence, and there's currently no way for you to see the 2003 revision with the 2003 parser, either.)
Whether revisions should be saved in wikitext alone or simultaneously saved in both wikitext and HTML+RDFa was an open question the last time I heard anyone mention it, but not one that affects the editing experience. (The idea seemed to be that dual-format saving would increase disk use but might be faster to read.) A few years ago, the devs discussed someday saving pages in HTML+RDFa alone and then turning them back into wikitext whenever someone wanted to edit, but interest in that option was limited. Maybe it's something they should consider again in future decades, but I don't expect it to happen in the foreseeable future. Whatamidoing (WMF) (talk) 17:13, 19 January 2017 (UTC)[reply]
@Whatamidoing (WMF): If we switch both editors to use Parsoid, issue #2 will be moot (as you explained above), but it isn't clear to me that that is actually going to happen. Can you provide any clarification on that issue? i.e. is the Editing Team planning on switching the old Wikitext editor to use Parsoid? Personally, I haven't heard of any such plans. On issue #1, my understanding is that there is little possibility of further improving the load time of the new WikiText editor due to its architecture (since it has to load most of the VisualEditor code in order to function). Is that also your understanding? Has the Editing Team considered re-architecting it to address the load time concerns or is that not a realistic option? Kaldari (talk) 02:23, 12 February 2017 (UTC)[reply]
Hi, Kaldari: Replacing the old parser with a modern one (i.e., some modern one/not necessarily Parsoid) has been expected for some time (software is not eternal, bitrot is real, etc.), but I believe that the decision to replace it with Parsoid (i.e., a modern replacement that happens to be Parsoid) was officially taken last quarter. (That decision belongs to ArchCom and Parsing, not to the VisualEditor team.) There is some information on the plans at on mediawiki.org; IMO the more interesting and informative page is the one about the two-systems problem itself.
The VisualEditor team is not currently working on performance issues. It's being considered for the coming year, but I don't know what they'll decide yet. There are some resource constraints that make it a difficult choice (e.g., inability to instantly clone certain members of Ops.  ;-) Whatamidoing (WMF) (talk) 18:40, 20 February 2017 (UTC)[reply]
Even if maintaining our "old" editor, have I experienced troubles at other Wikis, which uses more than one. All developments are not necessary good ones Boeing720 (talk) 00:52, 24 February 2017 (UTC)[reply]
A dozen different editing environments are officially supported on WMF wikis, and there are others that aren't officially supported (such as WP:WikEd). Whatamidoing (WMF) (talk) 21:44, 2 March 2017 (UTC)[reply]
The discussion above is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.
There is consensus to replace the magic links with corresponding templates, and to do this replacement via bot. The consensus for the bot extends only to the conversion of magic links, not any other ISBN/ISSN/etc tasks like linking things that currently aren't linked at all. ~ Rob13Talk 18:14, 19 March 2017 (UTC)[reply]

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

Moved from WP:VPT

Magic links are being removed per the outcome of a Mediawiki RFC. What should we replace them with?

  • Nothing
  • Links ([[Special:BookSources/$1|$1]])
  • Templates ({{ISBN|$1}})
  • Parser functions ({{#ISBN:$1}}) [Requires Mediawiki changes]
  • Interwiki links ([[ISBN:$1|$1]]) [Requires Mediawiki changes]

21:49, 5 February 2017 (UTC)

Um the widely unadvertised RFC. All the best: Rich Farmbrough, 23:54, 13 February 2017 (UTC).[reply]

Background

In the RfC meeting for the Future of magic links RfC, it was agreed upon to disable magic links for the MW 1.28 release by default and begin the deprecation for Wikimedia sites. MW 1.28 was released 2016-11-28. I proposed a bot to replace the magic link to templates. See: Wikipedia:Bots/Requests for approval/Yobot 27 -- Magioladitis (talk) 09:10, 3 February 2017 (UTC)[reply]

What meeting? All the best: Rich Farmbrough, 23:55, 13 February 2017 (UTC).[reply]
phab:E287. Anomie⚔ 13:53, 14 February 2017 (UTC)[reply]

@Xaosflux: to comment. -- Magioladitis (talk) 15:22, 3 February 2017 (UTC)[reply]

I'm not seeing where the English Wikipedia had this "RfC meeting for the Future of magic links RfC" please provide a link to the RfC closure here, if there was not a community discussion here then spin one up. — xaosflux Talk 15:35, 3 February 2017 (UTC)[reply]

@Xaosflux: This is a Mediawiki issue. It will affect all Wikipedias. See mw:Talk:Requests_for_comment/Future_of_magic_links. -- Magioladitis (talk) 15:44, 3 February 2017 (UTC)[reply]

And for the record, Wikipedia:Village pump (technical)/Archive 151#Tech News: 2016-46 said:
The linked post links the RfC. PrimeHunter (talk) 16:59, 3 February 2017 (UTC)[reply]
@PrimeHunter: mw:Requests_for_comment/Future_of_magic_links#Problem links to the discussion to turn this off on the software, it does not show support for which (or even IF) local communities replace it with something else. — xaosflux Talk 17:06, 3 February 2017 (UTC)[reply]
Sure, I just pointed out we had been informed about the discussion to turn it off. mw:Requests for comment/Future of magic links links to phab:T145604 where the RfC meeting is mentioned. What local communities do (if anything) is something to be discussed locally. I assume Special:BookSources will still be there if we want to add a link to it. Wikipedia:Bots/Requests for approval/Yobot 27 was denied so this section is currently the only open discussion I know. If another exists or is opened then please post a link here. PrimeHunter (talk) 17:35, 3 February 2017 (UTC)[reply]

@MZMcBride: to comment on this. -- Magioladitis (talk) 15:49, 3 February 2017 (UTC)[reply]

I understand that if the magic link gets disabled it will just revert these to plan text. I'm also in general support that having these be linkable text is a good thing, and that mass conversions would need to be handled by a bot. What I'm not see is community support for which mechanism should the new enwiki standard for presenting ISBN values. It could be a template, or a parser function to be, or a combination - a pseudonamespace, etc. It could be one of thees, supported by another one a is traditional for a module in a template. I don't have any strong preference for which one to use - just that it has widespread support. — xaosflux Talk 15:51, 3 February 2017 (UTC)[reply]
I'd agree with this. Replacement of the magic links in general with something else is probably not something we get to decide on, what the "something else" is on the other hand... Jo-Jo Eumerus (talk, contributions) 16:18, 3 February 2017 (UTC)[reply]
My vote is using a template. It's consistent with how we treat other citations already and it allows page-level tracking of usage. We now have Template:ISBN and it's been working fine in live articles. Assuming that MediaWiki will no longer support magic links, does anyone object to using templates for their replacement? --MZMcBride (talk) 21:43, 4 February 2017 (UTC)[reply]
I don't. -- Magioladitis (talk) 23:27, 4 February 2017 (UTC)[reply]
Agree with replacing with templates. Keith D (talk) 23:52, 4 February 2017 (UTC)[reply]
Ditto, for each magic link. Jo-Jo Eumerus (talk, contributions) 16:16, 5 February 2017 (UTC)[reply]
The discussion above is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.

Backlog of unpatrolled files

Request an autopatrolled group specific to files

MAKE IT SO
Consensus is that a file-autopatrol userright ought to be created that makes one's uploads automatically patrolled. There was also a suggestion that regular autopatrol should not patrol files but I am not certain there is consensus for that yet - a few users supported this proposal and others did not comment. Criteria for the file autopatrol to consider are understanding in file patrolling, copyright and fair use. Potential future projects that don't have consensus support yet (also per the following section) are to grant the file-autopatrol status by default to file movers. Jo-Jo Eumerus (talk, contributions) 10:11, 19 March 2017 (UTC)[reply]

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

File patrolling was technically introduced almost a year ago (phab:T11501). The backlog of unpatrolled files, visible at Special:NewFiles, is very significant. Autopatrolled users have their files automatically patrolled, but there are many users who are trusted to upload files that do not meet the requirements for autopatrol (which is concerned with new articles, not files). Thus I suggest we request a new usergroup, "File autopatrolled", with a single userrright (to be created): autopatrol-upload that autopatrols upload of the user. This way, we'll cut down a lot on the new files to patrol. Cenarium (talk) 18:36, 10 February 2017 (UTC)[reply]

  • Support. Seems like a good idea. I don't think (article-)autopatrolled users should necessarily have their files autopatrolled either, since WP:PERM/A doesn't do anything to check that the editor is au fait with licensing policies etc. – Joe (talk) 15:52, 11 February 2017 (UTC)[reply]
Indeed these are very separate areas, in fact one would need separate userrights for patrolling uploads too, which should probably be bundled with the file mover usergroup. Cenarium (talk) 17:29, 11 February 2017 (UTC)[reply]
I can see the benefit of this in principle but there may be a difficulty in assessing a user's uploading experience. Files uploaded here may be transferred to Commons (sometimes wrongly leading to deletion there). Also, files uploaded here with a NFUR or with copyright outside the US are transferred to Commons when they fall out of copyright. Can an admin see the files I uploaded which were transferred to Commons on 14 January 2017? For example File:Boating in St Kilda, J Norman Heathcote, 1900.jpg. Thincat (talk) 18:17, 11 February 2017 (UTC)[reply]
Yes, admins can see it - both the 2 image versions and all the versions of the text from the page. עוד מישהו Od Mishehu 18:28, 11 February 2017 (UTC)[reply]
Oh, well, in that case I am in favour, supposing the standard of approval is appropriate. (BTW I think the article autopatrolled criterion is too high I see the level has sensibly been reduced.). Thincat (talk) 18:32, 11 February 2017 (UTC)[reply]
  • Support and remove file auto patrolled from the normal auto patrolled per Joe Roe. -- Iazyges Consermonor Opus meum 13:08, 13 February 2017 (UTC)[reply]
  • Support - Nifty idea and potentially good in practice. Criteria to obtain this permission may be needed, nevertheless. I don't know what the standards should be, but the criteria would be related to copyright and fair use. I don't know how many people would meet the criteria; the number would be the same as that of template editors or as high as the number of PC reviewers. George Ho (talk) 06:24, 14 February 2017 (UTC)[reply]
@Cenarium: May I add this discussion to "Centralized discussion" list? George Ho (talk) 19:49, 14 February 2017 (UTC)[reply]
The discussion above is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.
@Jo-Jo Eumerus: Did you create a ticket for this? — Train2104 (t • c) 18:49, 22 March 2017 (UTC)[reply]
No. Jo-Jo Eumerus (talk, contributions) 19:08, 22 March 2017 (UTC)[reply]
Tracked in Phabricator
Task T161215
@Jo-Jo Eumerus: Done. First time I've done this, so hope I didn't screw up somewhere. — Train2104 (t • c) 13:37, 23 March 2017 (UTC)[reply]

Rename "File mover" usergroup to "File handler" and grant ability to patrol files (only)

Also to deal with the backlog of unpatrolled files. Patrolling files and patrolling new articles requires completely different abilities, editors with the file mover usergroup are knowledgeable about files and should be allowed to patrol files even if they aren't new page patrollers, and vice versa new page patrollers weren't vetted to patrol files. Hence I suggest to Nikkimariarename the file mover usergroup to file handler and grant them the ability to patrol files, while new pages patrollers would no longer be able to patrol files. Cenarium (talk) 21:18, 11 February 2017 (UTC)[reply]

I think this is getting too complicated - if someone just wants to patrol files, let them? The existing group can be used for that - if they are making bad patrols, it can be removed. — xaosflux Talk 13:05, 13 February 2017 (UTC)[reply]
I suppose this may make sense, but would users be given a newsletter and asked if they wish to get the new rights immediately, much like the grandfathering of the NPP rights? Because if not a massive backlog could ensue. -- Iazyges Consermonor Opus meum 13:10, 13 February 2017 (UTC)[reply]
Why not having two separate rights? Renaming a file is enough. Changing to "handler" would make things more complicated. Also, "file handler" is a little too new and needs to be practiced more. George Ho (talk) 21:07, 13 February 2017 (UTC)[reply]
We don't bundle page mover and new page patrol, so there's precedent for making them separate. But part of me says we're unbundling a bit too much. The suggested "file patrol" and the above "file autopatrolled" should be one right. Unlike article patrol where one can be good at identifying good articles/cleanup tagging but not that good at writing content from scratch, someone familiar with the file licensing polices should be easily able to apply them to their own uploads. — Train2104 (t • c) 06:08, 16 February 2017 (UTC)[reply]
Echoing Xaosflux: Users who wish to patrol pages and demonstrate and understanding of what constitutes an appropriate page should be granted the new page reviewer user right. The right can be removed if they demonstrate a pattern of marking inappropriate pages as patrolled. — Godsy (TALKCONT) 05:56, 25 February 2017 (UTC)[reply]
  • Oppose rename, simply for the reason that this seems to be a Mediawiki thing, so the developers might have to do a bit of work just to do the renaming. I see no reason to disagree with the idea of allowing filemovers the ability to patrol files. Nyttend (talk) 00:20, 11 March 2017 (UTC)[reply]

RfC: Deprecate terms "edit history" and "revision history"

 Not done--The proposal failed to gain consensus.Many editors have expressed a lack of any meaningful benefit/purpose ariving out of the change.Winged Blades Godric 06:42, 24 March 2017 (UTC)[reply]

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

Should the terms "edit history" and "revision history" be deprecated in favor of "page history"? ―Mandruss ☎ 22:37, 28 February 2017 (UTC)[reply]

If a Yes consensus is reached, occurrences of "edit history" and "revision history" would be replaced by "page history". This would begin with what are arguably the most visible occurrences, the links "revision history statistics" and "revision history search" on the page history page itself, and the "Revision history" in its heading. At Help:Page history, the sentence "A page history is sometimes called revision history or edit history." would change to "(The alternative terms 'revision history' and 'edit history' are deprecated.)" Other occurrences would be replaced as editors run across them, citing this consensus. ―Mandruss ☎ 22:37, 28 February 2017 (UTC)[reply]

Survey: Deprecate "edit history" and "revision history"

  • Yes - I see absolutely no benefit to having multiple names for the same thing. Meanwhile, there is a downside in that new editors have to learn that the various names refer to the same thing. This is a good example of widepsread unjustifiable complexity that, collectively, serves as a barrier to entry. ―Mandruss ☎ 22:37, 28 February 2017 (UTC)[reply]
  • request clarification Are we talking about changing links in policies and so forth or are we talking about what editors choose to call it, because those are two very different conversations. Beeblebrox (talk) 22:48, 28 February 2017 (UTC)[reply]
    Request clarification of your request for clarification. If you're asking whether it's about changing existing or future occurrences within editor comments in talk spaces, the answer is no. Communication is improved when we agree on the names of things, but we don't go around changing editor comments from "edit comment" to "edit summary", "intro" to "lead" or "lede", and so on. Rather, it's about non-talk occurrences in the WP and Help spaces, etc., and infrastructure software such as the page history display. We can't make the horses drink, but we can lead them to the water. ―Mandruss ☎ 22:52, 28 February 2017 (UTC)[reply]
  • Yes makes sense. -- Iazyges Consermonor Opus meum 01:43, 1 March 2017 (UTC)[reply]
  • No, because the different terms are used in different contexts. When we're talking largely about the page itself, editors tend to say "page history". When we're talking about specific diffs, editors tend to say "edit history". When we're talking about specific revisions (but not necessarily which individual edit led to them), editors tend to say "revision history". The terms "page", "edit", and "revision" are distinct and editors have to learn them anyway. Any editor who struggles to understand what "page history", "edit history", and "revision history" means after knowing those three terms must not know what a "history" is, and that's something we're not going to be able to fix. This is a solution in search of a problem, and it actually has a small chance of causing harm. Removing the alternative terms that have different contexts from all documentation will just make discussions held in those different contexts more difficult to understand. ~ Rob13Talk 08:27, 1 March 2017 (UTC)[reply]

Yes. As the OP poinyted out, we won't erase the terms from Help:Page history, and this will keep all current discussions consistant with the way major features of the software are refered to - this will make things easier for newcomers. Note that no automation should be used to fix anything here - each change needs to be reviewed by a human being (an admin inthe case of MediaWiki: namespace pages). עוד מישהו Od Mishehu 09:18, 1 March 2017 (UTC)[reply]

@Od Mishehu: "Current discussion" will be unaffected, just documentation pages. We obviously cannot ban editors from using the alternative phrases which are more descriptive in specific contexts. ~ Rob13Talk 09:20, 1 March 2017 (UTC)[reply]
Yes, but as we move towards the new terminology, the depricated ones will gradually fade out of use in discussions. We son;t ban editors from talking about the "Abuse Filter", yet I haven't seen anyone calling itby that name. עוד מישהו Od Mishehu 09:21, 1 March 2017 (UTC)[reply]
  • No Outside technical and emergency contexts, there is no need for perfect consistency in language, especially in English. If I ask you for a pop from your ice chest, and you go and grab a soda from your fridge, we both know what I was asking for and effective communication happened. I see no evidence that effective communication is hampered by these terms. There isn't any real problem in referring to page history versus edit history versus revision history. They all refer to the record of past edits that revised the way a page displayed, and they all communicate effectively. We shouldn't try too hard to impose order on a usage area that will likely defy order. Eggishorn (talk) (contrib) 16:48, 1 March 2017 (UTC)[reply]
  • No per there being no real reason to change. Not confusing and it doesn't hurt anything. Eggishorn also has a great explanation for why it doesn't matter. Just because it doesn't appear to hurt anything to change it doesn't mean we should do it. There should be a positive reason for the change, which I don't see here. TonyBallioni (talk) 14:37, 2 March 2017 (UTC)[reply]
  • no. I too can see no reason for this, no benefit it will bring to the encyclopaedia, just a bunch of unnecessary edits and potentially a number of disputes as editors unaware or disagreeing with this proposal revert the changes.--JohnBlackburnewordsdeeds 15:39, 2 March 2017 (UTC)[reply]
  • No English has multiple different terms that mean essentially the same thing. Since the terms aren't confusing or misleading there's no real benefit to standardising on one, and trying to enforce a single term would only antagonise people. Hut 8.5 18:46, 2 March 2017 (UTC)[reply]
    There is no proposal to "enforce" anything. Also see today's further discussion in the following section. ―Mandruss ☎ 04:12, 3 March 2017 (UTC)[reply]
  • No Per WP:CREEP, we should always have a real problem that is solved by any changes, and I'm just not convinced there is a real problem here that would require a new rule to solve it. Beeblebrox (talk) 05:06, 3 March 2017 (UTC)[reply]
    There is no proposal for a new rule. CREEP does not apply since the proposal is to replace two words, revision history or edit history, with a different two words, page history, in contexts referring to the tool described at Help:Page history. Also see today's further discussion in the following section. Per WP:BLUDGEON, this will be my last attempt to get participants to expend a bit of effort to understand the relatively simple question presented in this RfC, as well as the rationale for support. ―Mandruss ☎ 05:10, 3 March 2017 (UTC)[reply]
  • No a waste of time RFC. The terms edit history and revision history are much more explanatory, esp. when it comes to external usage - by non-wikipedians. "Page history" is too vague. 103.6.159.75 (talk) 16:11, 16 March 2017 (UTC)[reply]

Discussion: Deprecate "edit history" and "revision history"

I don't want to vote yet, but I mean it sounds reasonable. Is there any any "against" argument? Herostratus (talk) 23:18, 28 February 2017 (UTC)[reply]

@Herostratus: Well, page history could refer to the history of things like deletion logs and such. I would value a single term for edit history/revision history, possibly just use one or the other? RileyBugzYell at me | Edits 23:50, 28 February 2017 (UTC)[reply]
If I see significant support for a "choose the term or leave status quo" RfC, I will withdraw this and restart, pinging any prior participants. ―Mandruss ☎ 23:56, 28 February 2017 (UTC)[reply]
I have generated a list of likely pages to look over for the term "revision history" - see here. The similar search for "edit history" has too many false positives to use this way. עוד מישהו Od Mishehu 09:24, 1 March 2017 (UTC)[reply]

A lot of the opposition is that there is no confusion. I fully understand that there is no confusion to us, after we have learned that they refer to the same thing. In my opinion experienced editors should put ourselves in the position of the newbie; this is about entry after all. Does anyone dispute that it does take longer to learn three synonyms than a single term? It doesn't take a lot longer, but combined with the numerous other such situations the learning curve is significantly longer than necessary. Does anyone not find it intuitively obvious that many newbies, especially those not coming from technical backgrounds, must be overwhelmed by the complexity of this environment?
The only way to address this is one nit at a time. The principle is that simpler is better, and the proper question is: What harm would be done by this small simplification?
The effort required to implement is miniscule; except for the trivial software changes (you don't have to do elaborate regression testing of a change to a few words on a generated page), I would do most of it myself. ―Mandruss ☎ 03:41, 3 March 2017 (UTC)[reply]

Counter-argument: Od Mishehu's comment above about "too many" false positives for a simple search on "edit history". In truth, it is not likely simple on a technical level, and certainly not simple on a behavioral level. Editors will continue to call and name these pages whatever they wish and banging them over the head with yet another stylistic preference is policy creep. Eggishorn (talk) (contrib) 04:00, 3 March 2017 (UTC)[reply]
(edit conflict) The question also shouldn't be What harm would be done by this small simplification? but Why should we do this? I haven't heard a good case for why we should do it. TonyBallioni (talk) 04:03, 3 March 2017 (UTC)[reply]
Changing the words used by Wikipedia is hardly banging anybody over any heads. I'm not proposing a warning template here. Hyperbole is not helpful to the debate or one's own thinking.
I think it's abundantly clear that editors would not be forced to use the "official" term any more than they are forced to use any other "official" terms. I merely assert that it makes sense to have one "official" term for each "thing". Some editors call the lead/lede the "intro", but does that mean we should rename Wikipedia:Manual of Style/Lead section to Wikipedia:Manual of Style/Lead or intro section? I think not. Does it mean we should call it lead/lede in some places and "intro" in others? I think not. Communication would be enhanced if everybody called it lead/lede, but we don't actively correct the editors who call it "intro". We simply hope that, at some point in their development as an editor, it will occur to them that Wikipedia calls it lead/lede and they will start calling it that instead. No head-banging.
I've made the best case I know how, but if I fail to convince a majority, I certainly know how to lose. I do ask that participants refrain from misconstruing the proposal, as that undermines any decision-making process. I've seen little evidence that closers take the time necessary to discount such !votes. ―Mandruss ☎ 04:09, 3 March 2017 (UTC)[reply]
Yes, yes. Disagree with your case, but wasn't trying to suggest you don't know how to lose. Sorry if the tone came off that way. Text being an imperfect means of communication :) TonyBallioni (talk) 04:12, 3 March 2017 (UTC)[reply]
The discussion above is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.

Wikipedia:WikiProject Council/Proposals/Wiki Brain

Moved to Wikipedia:Village pump (idea lab) § Wikipedia:WikiProject Council/Proposals/Wiki Brain
 – Way too vague for this page. Needs incubation. ―Mandruss ☎ 09:52, 23 March 2017 (UTC)[reply]

Proposal - non-requested automated messages on talk pages must be short

As more bots edit Wikipedia more often, I think we should be mindful of the ways that interacting with bots can take time away from human engagement in Wikipedia. As a general rule, messages from bots, especially if they are routine and posted 100,000+ times, should be short so as to minimize the amount of human time and attention that they capture. The time of Wikipedia editors is valuable and any small grab for time multiplied by 100,000 has a big impact. I wish to propose a general rule that could be expanded if there is community support.

  • Non-requested, mass-posted, automated messages on talk pages must be short.

Details can be sorted, but I mean that a message written by a bot and designed to capture the attention of thousands of users should be not more than about a sentence long.

Example case

InternetArchiveBot is operated by Cyberpower678 place dead external links with links to backup copies of the source at the Internet Archive. The bot and project are funded by a partnership between the Wikimedia Foundation and the Internet Archive to do tasks as described at meta:Community Tech/Migrate dead external links to archives. The project was the top-ranked request in the meta:2015 Community Wishlist Survey. Everyone likes the project and I like it too.

The part that I think is excessive is posting comments like this on talk pages:

Hello fellow Wikipedians,

I have just modified 2 external links on Gorham's Cave. Please take a moment to review my edit. If you have any questions, or need the bot to ignore the links, or the page altogether, please visit this simple FaQ for additional information. I made the following changes:

When you have finished reviewing my changes, you may follow the instructions on the template below to fix any issues with the URLs.

This message was posted before February 2018. After February 2018, "External links modified" talk page sections are no longer generated or monitored by InternetArchiveBot. No special action is required regarding these talk page notices, other than regular verification using the archive tool instructions below. Editors have permission to delete these "External links modified" talk page sections if they want to de-clutter talk pages, but see the RfC before doing mass systematic removals. This message is updated dynamically through the template {{source check}} (last update: 5 June 2024).

  • If you have discovered URLs which were erroneously considered dead by the bot, you can report them with this tool.
  • If you found an error with any archives or the URLs themselves, you can fix them with this tool.

Cheers.—InternetArchiveBot (Report bug) 09:56, 23 March 2017 (UTC)[reply]

Here are some problems with this post:

  1. It is long and capturing too much volunteer attention. Research in eye tracking is raising awareness of how much time arbitrary decisions in online diversions take away from meaningful ways for people to spend their time. If someone reads or even sees this post that could take 15 seconds to a minute of time. Multiple visitors to a talk page might read the post, as it is persistent indefinitely and at current archiving rates probably has an average life of ~5 years.
  2. The post asks for "source checking", where a human manually checks what the bot does. If a human does this task, that could take 2-3 minutes.
  3. This is my own estimate, but my guess is that the average time consumed per talk page post is 1 minute. I think every talk page post will be viewed at least once for 15 seconds, many will be viewed multiple times by multiple users over a period of years, and in some cases some users will complete the sourcecheck task. Overall, I think guessing that each post consumes 1 minute is a fair place to start the conversation. Arguably the average time cost is higher.
  4. This bot has made 700,000+ edits and is going to make millions more. If it edits 100,000 talk pages, then it consumes 100,000 minutes of time, or 1600 hours or 66 days. Also, the time it is consuming is time from the kind of person who would visit a Wikipedia article talk page, so this is the time of Wikipedia users who are among the 1% most engaged and whose time is most valuable.
  5. 100,000 minutes of time is too much time to give to this talk page post, when typically, the post needs no response at all. These posts represent one of the biggest content publishing pushes from a single project in Wikimedia history. Practically all Wikipedia editors who read talk pages are going to spend time reading these posts repeatedly for years, giving some amount of attention to them.
  6. In 95% of cases there is no reason for anyone to interact with any of these posts. They do not contain information which is of interest to most talk page readers.
  7. There is no plan in place to expire or remove these posts. Even if they are checked, they will continue to be read for years in the current plan design.
  8. I am not aware of any discussion demonstrating mindfulness about how much editor time this bot is designed to consume.

To lessen the impact of the bot, I propose that its posts to talk pages be restricted. Perhaps restriction to one sentence is sufficient. Either it can say everything it needs to in one sentence, or otherwise, the one sentence can link to a more detailed log somewhere else for users to follow and read if they really want to spend their time engaging with this bot.

In the future, as a general rule, talk pages on Wikipedia should emphasize human to human interaction and work tasks posted to talk pages by bots should be minimally invasive.

I discussed this with Cyberpower678 at T161108 and they told me they wanted Wikipedia community consensus for change. I am asking now for support to reduce the bot's posting to one short sentence, like one of these -

  1. "A link went down and the Internet Archive Wikipedia Link Archiving Project fixed it by replacing it with an archived copy. - Internet Archive Bot"
  2. "A link went down and the Internet Archive Wikipedia Link Archiving Project fixed it as described on the archive log, which anyone may see. - Internet Archive Bot"

I do not want to detract from the archiving project, which is important, but this is a big enough issue on a well-funded enough project that I think we can cut back to a sentence as an immediately measure then have longer discussions about whether more should be added back, if there is any dispute about exactly what should be cut and what is necessary.

Thoughts from others?

Operator comment: The settings for the talk page messages are controlled here, and it's documentation can be seen here. As a side note, the one sentence proposal of Bluerasberry is not feasible with current design considering that there are more than one links being fixed in most edits. This is in regards to sentence 1. In regards to proposed sentence 2, there is no archive log.

Also, talk page messages are only left when archives have been added or modified, and they're there for users to quickly be able to click on and verify their functionality.—CYBERPOWER (Chat) 15:38, 23 March 2017 (UTC)[reply]

Cyberpower678 Can you comment on how feasible it seems to you that your current design process is likely to attract about 100,000 minutes of editor attention for every 100,000 talk page posts? Do you have a better guess for how much time your project is designed to consume? Blue Rasberry (talk) 16:07, 23 March 2017 (UTC)[reply]
A user does not have to read the notifications if they do not want to. The notifications simply is there as a means to quickly verify the bot's edit if they choose to. The talk page messages provides tools for user to appropriately correct any errors found. Users would typically only read it once, and would be able to quickly identify any new message and act accordingly. So your estimate is likely smaller than that. The talk page messages can be shut off entirely too. It's all controllable on the config page I linked to.
There are a lot of organizations which post messages to twitter and Facebook to collect something called an Impression (online media). This is a contemporary advertising theory, and there is research describing how much thought people put into the messages to which they are exposed. I expect that posts on Wikipedia get read at least as much as something in a typical person's subscribed feeds elsewhere. If a message on a talk page lasts for ~3 years and gets read by 10 people for 6 seconds each over that 3 year period, then that adds up to one minute. Which of my numbers seem off to you? Does 6 seconds each by 10 users over 3 years per post seem excessive? What number would you tweak? Did your project do any calculation or put any thought into this yourselves, to present your own time cost estimate? Suppose that I am off by 50% - does a cost of 50,000 minutes per 100,000 posts seem reasonable to you? Blue Rasberry (talk) 16:40, 23 March 2017 (UTC)[reply]
Mandruss I just moved this from policy to "proposals". Blue Rasberry (talk) 15:13, 23 March 2017 (UTC)[reply]
xaosflux Thanks for early feedback. I changed this to only refer to non-opt in posts which are targeted to at least thousands of readers and written by a bot. Blue Rasberry (talk) 15:13, 23 March 2017 (UTC)[reply]
  • Weak Support Losing the many "walls of words" would be a relief, but I usually skip them anyway. That right there tells you the impact it has on me - I have trained myself to ignore these post whenevr possible. GenQuest "Talk to Me" 15:24, 23 March 2017 (UTC)[reply]
  • Oppose as effectively unenforceable. How long is too long? are we going to set a hard byte limit on bot talkpage notices? There are other problems, as well. There is already a mechanism in place for bot best practices, the BAG. The idea that a new, permanent, policy is needed because of notices posted by one bot that the community and the WMF agree is doing necessary work is policy creep. Lastly, and most importantly, talkpage reading is not mandatory and easily ignored. If this is really considered a problem, then institute archiving on the page and let Cluebot or lowercase sigmabot take care of it. There's a certin elegance in letting a bot clean up after a bot, afer all. Eggishorn (talk) (contrib) 16:59, 23 March 2017 (UTC)[reply]
  • Oppose - if some specific bot is giving messages which are too long, discuss it as you would any other issue related to a bot's behavior not being up to your standards. This would mean starting with a discussion with the operator, and if you can't agree, moving on to more public discussion. No need to make this an explicit rule. עוד מישהו Od Mishehu 18:47, 23 March 2017 (UTC)[reply]
  • Oppose - A good suggestion, but a poor requirement. Sometimes longer messages may be due. Also, "short" is vague. — Godsy (TALKCONT) 20:25, 23 March 2017 (UTC)[reply]
@Xaosflux, Eggishorn, Od Mishehu, and Godsy: Can you say more about why you oppose? Would any of you feel comfortable saying that you disagree with any or all of these premises?
  1. If 100,000 long messages are posted to 100,000 articles, then over the life of the message, about 100,000 volunteer minutes will be consumed in the process. This is a significant amount of time and volunteer attention.
  2. Volunteer attention, measured in time, is poorly spent engaging with automated messages of the sort presented by Internet Archive Bot as compared to other Wikipedia activities which the Wikipedia community encourages by placing into focus on this scale.
  3. Assuming that the messages are consuming large amounts of time, and assuming that the time consumption is a problem to address, then shortening the messages is a viable way to address the issue.
Which of these, if any, do you doubt? If you doubt all of them, then it would be useful feedback for me to hear that you think that what the IABot is doing is practice that the Wikimedia community should permit or encourage. Blue Rasberry (talk) 20:47, 23 March 2017 (UTC)[reply]
@Bluerasberry: My oppose was prior to the proposal being changed, I've stricken it for now - reason was that we should not restrict opt-in automated messages like in my exampled above to only be "small". — xaosflux Talk 22:28, 23 March 2017 (UTC)][reply]
"Premise" #1 is a free-floating assertion with no evidence to back it up and supported by nothing more than assumed reading resources and back-of-the-envelope calculations. How are you deriving any of those numbers. Where is the data to believe that each message "consumes" volunteer minutes in anything like this amount? Premise #2 is a mere personal belief, again with no empirical data. Premise #3 is nothing more than a tautology. There is nothing in these premises to justify creating new rules. Here's a simpler solution: don't read the messages. Eggishorn (talk) (contrib) 23:04, 23 March 2017 (UTC)[reply]
I don't insist that all premises be "proven"; I think reason and intuition are enough in many cases. But reason and intuition tell me that most editors actually read the whole message once, if that. After that they recognize it at a glance and they already know what it says and what its purpose is. ―Mandruss ☎ 03:10, 24 March 2017 (UTC)[reply]
Personally, I usually don't either. If an editor tries to lay out their argument in terms of hypotheses and premises and suchlike, however, it is only natural for other editors to evaluate their arguments in similar terms. What I see in this set of premises is an editor raising their personal distaste to universal commonality, which is a really big leap in logic. Eggishorn (talk) (contrib) 15:36, 24 March 2017 (UTC)[reply]
Eggishorn You are correct - I used poor word choices and I did not communicate effectively. I wish that I could step outside this conversation and ask you somehow if you understood my intent, because I feel like I presented arguments that you are parsing as equations when actually I was trying to raise concern about a recurring social issue. Do you do video or phone chat? I will email you and ask. If you really are interested in this conversation, one point that you raise which I can address is a better calculation. The most solid number that I have is that 100,000+ messages are posted to talk pages. I hope that I could get you to agree with an assumption that these messages are viewed on average for not less than 1 second each, which is less than the 60 seconds which I imagined people like you would take as conservative. If the number is 1, and not 60, then the time cost is still 100,000 seconds or 27 hours. I would argue that this is not time well spent, and that we should not permit or encourage processes which are designed to consume time in this way even if it is in small pieces from many people. User experience is not enhanced by subjecting them to messages which are designed to not be read, and if these messages are designed to be read and actually are being read, then they are consuming even more time and for no apparent reason. The novelty in this case is that whatever the effect, it is multiplied by 100,000 and planned for 1,000,000+ messages. Despite my inability to articulate the cause and effect as a matter of logic, does any part of this strike you as unusual and worth examining as a matter of policy? Blue Rasberry (talk) 14:08, 28 March 2017 (UTC)[reply]
  • Oppose Saying this is a must is excessive. The postings shouild be as short as is clear, sets the right tone, and motivates people in a suitable way. I don't see that there is much time wasted, as on most pages I see them, the messages are ignored by others. Not only that, talk pages get only a few reads. Perhaps some talk messages could be hatted or closed once dealt with, so that others don't repeat any effort requested. Graeme Bartlett (talk) 10:19, 24 March 2017 (UTC)[reply]

Linking from Wikipedia to other wikis

Transferred from WP:AN. Nyttend (talk) 05:06, 24 March 2017 (UTC)[reply]

As a follow up to Wikipedia:Village_pump_(proposals)#Future_of_magic_links, the following BRFAs have been made

On some of those at least, is the idea of converting non-magic word identifier instances either

  • Only do magic word conversion (e.g. doi:10.1234/whatever, PMID 0123465 → doi:10.1234/whatever, PMID 123465)
  • Alongside the magic word conversion (e.g. doi:10.1234/whatever, PMID 0123465 → doi:10.1234/whatever, PMID 123465)
  • On their own (e.g. doi:10.1234/whatever → doi:10.1234/whatever)

As well as doing some standardization and cleanup (doi 10.1234/whatever → doi:10.1234/whatever)

This is not, however, a proposal to convert bare citations to templated citations, e.g.

  • Smith, J. (2016), "Article", ''Journal of Foo'' '''23'''(3):1–23 doi:10.1234/whatever
    → {{cite journal |last=Smith |first=J. |year=2016 |title=Article |journal=Journal of Foo |volume=23 |issue=3 |pages=1–23 |doi=10.1234/whatever}}

only bare identifiers to templated identifiers, e.g.

  • Smith, J. (2016), "Article", ''Journal of Foo'' '''23'''(3):1–23 doi:10.1234/whatever
    → Smith, J. (2016), "Article", ''Journal of Foo'' '''23'''(3):1–23 {{doi|10.1234/whatever}}

I can't think of any reason why the unlinked/untemplated version would be preferred over the linked/templated versions, but I figured I'd at least advertise these BRFAS. Headbomb {talk / contribs / physics / books} 14:09, 25 March 2017 (UTC)[reply]

This is a great task. -- Magioladitis (talk) 14:21, 25 March 2017 (UTC)[reply]

There needs to be a way for editors to opt-out of this if a particular circumstance requires it. The easiest way would be to put the content in "nowiki" tags, which should be enough to tell the bot that it is not intended to be linked. Can the bot recognize and respect that? — Carl (CBM · talk) 18:40, 26 March 2017 (UTC)[reply]

AWB has the option to "Ignore external/interwiki links, images, nowiki, math, and <!-- -->". I can't see why that wouldn't be enabled during such a run. Headbomb {t · c · p · b} 19:11, 26 March 2017 (UTC)[reply]

A proposed template for the draftspace

Hi,

Following early RfCs, I have made a proposal for the template that can be used to sort and classify pages in the draftspace (but not drafts in the user pages.) More participations are welcome and, well, needed at Wikipedia_talk:Drafts#RfC:_Draft_classifier_template. -- Taku (talk) 23:10, 25 March 2017 (UTC)[reply]

Ijabcd redirects for IJabcd articles

As you can see from IJ (digraph), many Dutch words are written with "IJ", both capitalised, as their initial letters. This looks odd to English-reading eyes, and if you remember how such a world is spelled (e.g. IJlst), you may forget to capitalise the J.

With this in mind, creation of "Ij" redirects seems like a good idea. Would it be desirable to request that a bot create an "Ij" redirect for every "IL" article? Nyttend (talk) 02:45, 26 March 2017 (UTC)[reply]

Is there some idea of how many there are? If there are only a few dozen programming a bot might not be worth it. A few hundred? Then yeah, a bot might be useful. --Majora (talk) 02:47, 26 March 2017 (UTC)[reply]
Once we scrap acronyms and the like (e.g. IJA 145th Division and IJCAI Award for Research Excellence), we're left with 70 titles, out of which 38 are articles, 30 are redirects, and 2 are irrelevant, IJustWantToBeCool and IJustine. So I guess you're right about doing these some other way. By the way, is there some custom way to cause Special:Allpages to exclude redirects, or is there some other special page that does the same thing as Allpages except without the redirects? If we'd had hundreds of pages, it would have taken an excessive amount of time to count all of them. Nyttend (talk) 03:11, 26 March 2017 (UTC)[reply]
How did you come up with 70? I just did a search for prefix:ij and then did a normal ctrl + f search for the word "Dutch" and came up with 29 articles. I don't think there is a way to eliminate redirects in Special:Allpages and the manual on searching is coming up empty as well. --Majora (talk) 03:22, 26 March 2017 (UTC)[reply]
Even better, search for Dutch in the entire article. Search for "Dutch prefix:ij" returns 37 articles. --Majora (talk) 03:27, 26 March 2017 (UTC)[reply]
I searched for titles beginning with IJ at Special:Allpages, deleted the ones that were acronyms and the like, and I was left with 70 titles. Probably 1 of the 38 is unrelated to Dutch and I made a mistake by including it. Nyttend (talk) 03:34, 26 March 2017 (UTC)[reply]
Whether it is 37 or 38 it would probably just be easier to do these manually. That isn't really enough to warrant making a bot, getting it approved, and running it. --Majora (talk) 04:00, 26 March 2017 (UTC)[reply]
I made an AWB request before leaving my last note here, and Certes fulfilled it a couple of hours ago. Nyttend (talk) 21:09, 26 March 2017 (UTC)[reply]
Should we also include titles with the word IJ rather than IJabcd (e.g. IJ (Amsterdam)) or containing IJabcd as a later word (Hoge vuurtoren van IJmuiden) or both (Brouwerij 't IJ)? Certes (talk) 23:12, 26 March 2017 (UTC)[reply]
Good point. The problem is that I don't know how to search for such pages; you won't find them easily with Special:Allpages of course, and if it's possible to get Special:Search to be case-sensitive (i.e. counting "Hoge vuurtoren van IJmuiden" but ignoring "Hoge vuurtoren van ijmuiden" if it existed), I don't know how. Judging by Help:Searching, if I searched for intitle:IJ and intitle:IJ*, I suppose it would give me all pages with "IJ" as a separate word and all pages beginning with IJ, but those might still have to be sorted by capitalisation status. Nyttend (talk) 23:31, 26 March 2017 (UTC)[reply]
Those articles are now done too, so that's probably the end of this job. Certes (talk) 12:28, 27 March 2017 (UTC)[reply]

Make the title of each column follow the scrolling in tables

Hi, I like to read statistics and I often find that with a large table with many columns and rows, I get lost while scrolling down. I think the first row of a table should 'magnetize' to the top of your screen and follow along as you read entries of the table that are lower. Often, the tables are incomplete and so, it is hard to follow along, remembering which row is which. It can be especially hard when the subject is a new one for the reader. Of course, this idea should be implemented in beta first to see if it works.

--Ṗḯƥỡȵẘẩ (talk) 00:56, 28 March 2017 (UTC)[reply]

I believe there is a phabricator task for this request. --Izno (talk) 02:14, 28 March 2017 (UTC)[reply]
I've been testing this lately in my personal CSS. It works quite well on sortable tables. For wiki tables, it's harder, since you need to guess where headers start and end, which is basically impossible (the JS of wiki tables has some pretty complicated logic to do that, which cannot be easily copied). It also only works on rather recent browsers. I'll turn it into a gadget. —TheDJ (talk • contribs) 11:18, 28 March 2017 (UTC)[reply]
@Piponwa:, @Izno: see the last gadget in the Testing and development section of Special:Preferences#mw-prefsection-gadgets. —TheDJ (talk • contribs) 11:24, 28 March 2017 (UTC)[reply]
@TheDJ: Doesn't appear to work on Fx 51.0.1 (32-bit--why do I have 32 bit? D:), though it does successfully remove the bottom border on the headers at List of multiplayer online battle arena games. Do you have a page where it works for you? --Izno (talk) 11:43, 28 March 2017 (UTC)[reply]
Works on Safari. On Chrome it seems that it only works halfway (no sticky support for thead elements...) and on Firefox it should be working but apparently it doesn't work at all. —TheDJ (talk • contribs) 12:30, 28 March 2017 (UTC)[reply]
Wow! Thanks! i added the gadget and it's great! --Ṗḯƥỡȵẘẩ (talk) 21:19, 28 March 2017 (UTC)[reply]

RfC on the new "Protector" permission

There is currently an RfC regarding this permission on Wikipedia talk:Protection policy#RfC on the new "Protector" permission. If you are willing to, could you please give feedback? Thank you --Cheers, FriyMan talk 09:13, 28 March 2017 (UTC)[reply]

Fritz Angst

That's a one line article of an author of one book, which in turn is an eight line article. I'd say, ether delete both or merge them.

(Please forward if this is not the best location for this kind of proposal.)

bye217.248.40.182 (talk) 20:41, 28 March 2017 (UTC)[reply]

Wikipedia does have Wikipedia: Articles for deletion and you may have more joy there for this type of proposal. Carltonio (talk) 20:52, 28 March 2017 (UTC)[reply]

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