User talk:John Broughton

From Wikipedia, the free encyclopedia
Jump to: navigation, search

Click here to start a new section. (The edit summary will be created automatically; it will be the same as the heading of the new section.)


Contents

Books and Bytes - Issue 9[edit]

Wikipedia Library owl.svg The Wikipedia Library

Bookshelf.jpg

Books & Bytes
Issue 9, November-December 2014
by The Interior (talk · contribs), Ocaasi (talk · contribs), Sadads (talk · contribs)

  • New donations, including real-paper-and-everything books, e-books, science journal databases, and more
  • New TWL coordinators, conference news, a new open-access journal database, summary of library-related WMF grants, and more
  • Spotlight: "Global Impact: The Wikipedia Library and Persian Wikipedia" - a Persian Wikipedia editor talks about their experiences with database access in Iran, writing on the Persian project and the JSTOR partnership

Read the full newsletter

MediaWiki message delivery (talk) 23:36, 8 January 2015 (UTC)

Tech News: 2015-03[edit]

16:47, 12 January 2015 (UTC)

Tech News: 2015-04[edit]

18:13, 19 January 2015 (UTC)

There is a new WikiProject you may be interested in[edit]

Lede Improvement Team.JPG This is a form letter sent out to members of WikiProject Lead section cleanup.

I am contacting you because you are listed as a participant of the now defunct WikiProject Lead section cleanup. I have created a new WikiProject, WikiProject Lede Improvement Team (name subject to change), that likely has the same goals as the project that you signed up for was supposed to have. If improving the lede sections of articles is something you are still interested in, please stop by and add yourself as a participant. As well, if you have any thoughts regarding your previous experience with lede section cleanup, please stop by and share them. Thank you,  DiscantX 08:39, 20 January 2015 (UTC)

Tech News: 2015-05[edit]

16:08, 26 January 2015 (UTC)

RfC - Helper Script access[edit]

An RfC has been opened at RfC to physically restrict access to the Helper Script. You are invited to comment. --Kudpung กุดผึ้ง (talk) 16:33, 1 February 2015 (UTC)

Tech News: 2015-06[edit]

16:31, 2 February 2015 (UTC)

VisualEditor News 2015—#1[edit]

VisualEditor-logo.svg

Since the last newsletter, the Editing Team has fixed many bugs and worked on VisualEditor's appearance, the coming Citoid reference service, and support for languages with complex input requirements. Status reports are posted on Mediawiki.org. Upcoming plans are posted at the VisualEditor roadmap.

The Wikimedia Foundation has named its top priorities for this quarter (January to March). The first priority is making VisualEditor ready for deployment by default to all new users and logged-out users at the remaining large Wikipedias. You can help identify these requirements. There will be weekly triage meetings which will be open to volunteers beginning Wednesday, 11 February 2015 at 12:00 (noon) PST (20:00 UTC). Tell Vice President of Engineering Damon Sicore, Product Manager James Forrester and other team members which bugs and features are most important to you. The decisions made at these meetings will determine what work is necessary for this quarter's goal of making VisualEditor ready for deployment to new users. The presence of volunteers who enjoy contributing MediaWiki code is particularly appreciated. Information about how to join the meeting will be posted at mw:Talk:VisualEditor/Portal shortly before the meeting begins. 

Due to some breaking changes in MobileFrontend and VisualEditor, VisualEditor was not working correctly on the mobile site for a couple of days in early January. The teams apologize for the problem.

Recent improvements[edit]

The new design for VisualEditor aligns with MediaWiki's Front-End Standards as led by the Design team. Several new versions of the OOjs UI library have also been released, and these also affect the appearance of VisualEditor and other MediaWiki software extensions. Most changes were minor, like changing the text size and the amount of white space in some windows. Buttons are consistently color-coded to indicate whether the action:

  • starts a new task, like opening the Save page dialog:  blue ,
  • takes a constructive action, like inserting a citation:  green ,
  • might remove or lose your work, like removing a link:  red , or
  • is neutral, like opening a link in a new browser window:  gray.

The TemplateData editor has been completely re-written to use a different design (T67815) based on the same OOjs UI system as VisualEditor (T73746). This change fixed a couple of existing bugs (T73077 and T73078) and improved usability.

Search and replace in long documents is now faster. It does not highlight every occurrence if there are more than 100 on-screen at once (T78234).

Editors at the Hebrew and Russian Wikipedias requested the ability to use VisualEditor in the "Article Incubator" or drafts namespace (T86688, T87027). If your community would like VisualEditor enabled on another namespace on your wiki, then you can file a request in Phabricator. Please include a link to a community discussion about the requested change.

Looking ahead[edit]

The Editing team will soon add auto-fill features for citations. The Citoid service takes a URL or DOI for a reliable source, and returns a pre-filled, pre-formatted bibliographic citation. After creating it, you will be able to change or add information to the citation, in the same way that you edit any other pre-existing citation in VisualEditor. Support for ISBNs, PMIDs, and other identifiers is planned. Later, editors will be able to contribute to the Citoid service's definitions for each website, to improve precision and reduce the need for manual corrections.

We will need editors to help test the new design of the special character inserter, especially if you speak Welsh, Breton, or another language that uses diacritics or special characters extensively. The new version should be available for testing next week. Please contact User:Whatamidoing (WMF) if you would like to be notified when the new version is available. After the special character tool is completed, VisualEditor will be deployed to all users at Phase 5 Wikipedias. This will affect about 50 mid-size and smaller Wikipedias, including Afrikaans, Azerbaijani, Breton, Kyrgyz, Macedonian, Mongolian, Tatar, and Welsh. The date for this change has not been determined.

Let's work together[edit]

Subscribe or unsubscribe at Wikipedia:VisualEditor/Newsletter. Translations are available through Meta. Thank you! Whatamidoing (WMF) 20:23, 2 February 2015 (UTC)

Tech News: 2015-07[edit]

16:27, 9 February 2015 (UTC)

Add your own[edit]

Phab:'s a wiki (sort of). You can add the "§ VisualEditor Q3 Blockers" project to any bug or feature request that you think needs to be considered for blocker status. Tasks nominated after the meeting (which starts in 78 minutes) will be considered at the next meeting. Whatamidoing (WMF) (talk) 18:41, 11 February 2015 (UTC)

@Whatamidoing (WMF): Thanks; very helpful. While we're discussing Phab, a question: Is there a protocol/norm for responding to what I think is a premature closing of a task? [As in, "Here's my opinion, and I'm in charge, so I'm closing the task without waiting for your response."] If not, I'll just muck around in Phab, or complain at a Feedback page, but I'd prefer to keep discussions to one place, which seems to be Phab, if I can have a constructive discussion there. -- John Broughton (♫♫) 19:09, 11 February 2015 (UTC)
mw:Bug management/Phabricator etiquette is the only written advice that I'm aware of. The practice, to the best of my possibly-not-very-good knowledge depends on whether your objection is more "reasoning" or "technical facts". If the former, people usually seem to send e-mail to the person who closed it ("I see you closed this as unimportant, but I think it's really important because..."); if the latter ("This was closed as fixed, but I'm still experiencing this problem"), then they post directly in the ticket.
The overall trend seems to be that technical decisions are made at Phabricator, so the most efficacious option is probably to keep as much of the conversation at Phab as you can. Whatamidoing (WMF) (talk) 19:34, 11 February 2015 (UTC)

Tech News: 2015-08[edit]

17:57, 16 February 2015 (UTC)

Please comment on WP:AN#Closure review: Wikipedia:WikiProject Articles for creation/RfC to physically restrict access to the Helper Script[edit]

Hello! You have been selected to receive an invitation to participate in the closure review for the recent RfC regarding the AfC Helper script. You've been chosen because you participated in the original RfC. Should you wish to respond, your contribution to this discussion will be appreciated. This message is automated. Replies will not be noticed. --QEDKTC 14:23, 18 February 2015 (UTC)

Heather Bresch[edit]

I was wondering if you might have some advice on how to handle this. I was thinking I might need to start an RFC on the article's Talk page and ping the editors that participated here to get more editors involved? The problem is, I'd end up doing about 3-4 RFCs for every... little... change... which isn't practical, but I know of no better way. CorporateM (Talk) 15:21, 18 February 2015 (UTC)

To John Broughton: CorporateM has approached a significant number of other editors with this message on the topic of Heather Bresch. No worries if you do actually want to get involved. But I'm growing somewhat frustrated by the tactic: instead of being satisfied with posting to a noticeboard, approach editors one by one until he chances across someone who agrees with him. It's an obvious variant of canvassing. (And just in case you're not aware of the context: CorporateM is being paid by Bresch's employer, Mylan, to fluff up her biography.) Nomoskedasticity (talk) 15:37, 18 February 2015 (UTC)
It was archived without discussion at BLPN, but ANI could be another option, as it tends to have more participation and the drama boards is probably appropriate. I was thinking that by asking those that participated in the AfD to participate in the article, that is a random selection of editors that have shown an interest in a related subject and have some familiarity with the situation. Naturally I would have to provide an utterly neutral RFC and notification if I go that route. CorporateM (Talk) 17:00, 18 February 2015 (UTC)
@Nomoskedasticity: Perhaps you can help me understand the situation better. You said that CorporateM wasn't "satisfied with posting to a noticeboard"; CorporateM said the posting was archived without any discussion. If that's the case, are you saying that CorporateM should have stopped looking for other input when his first try got none? More generally, what do you suggest is the best thing that he could do to get others involved, or should he do nothing at all, now, other than possibly continue to post at the article talk page? -- John Broughton (♫♫) 17:14, 18 February 2015 (UTC)
CorporateM has posted at BLPN several times in the last few weeks about Bresch. Some of those posts have led to discussion at BLPN itself ([43]); others have brought additional people to the article talk page. That's all well and good. But what's going on with the repeated posting to the talk pages of individual editors isn't an attempt to get "more" input -- it's an attempt to get input agreeing with CorporateM's attempts to do what his client wants. If the BLPN posts had accomplished that (instead of gaining involvement from some people who didn't agree with those attempts), he wouldn't have wanted "more" input. Again, I have no objection to your taking a look at the article and then being as involved as you want to be. But I think it's appropriate for me to point out some of the context here: this is a paid editor trying to accomplish his goals using a specific tactic in doing so. Nomoskedasticity (talk) 17:50, 18 February 2015 (UTC)
The BLPN post Nomo linked to shows general support for reducing the weight of the controversy, which previously dominated the article. It's not as if they disagreed with me so I went looking elsewhere for someone to take my side. They supported that there was a problem (as did quite a few editors) but didn't take any action besides a passing comment. After an editor from IRC trimmed the controversy, they were merely reverted by Nomo, who alleged there was no consensus, since editors had only stated their objections to the UNDUE and BLP problem on BLPN and user Talk pages, rather than the article Talk page. Consensus was not clearly established and carried out until a large number of editors got involved. CorporateM (Talk) 21:55, 18 February 2015 (UTC)

Tech News: 2015-09[edit]

16:28, 23 February 2015 (UTC)

Tech News: 2015-10[edit]

16:41, 2 March 2015 (UTC)

Books and Bytes - Issue 10[edit]

Wikipedia Library owl.svg The Wikipedia Library

Bookshelf.jpg

Books & Bytes
Issue 10, January-February 2015
by The Interior (talk · contribs), Ocaasi (talk · contribs), Sadads (talk · contribs)

  • New donations - ProjectMUSE, Dynamed, Royal Pharmaceutical Society, and Women Writers Online
  • New TWL coordinator, conference news, and a new guide and template for archivists
  • TWL moves into the new Community Engagement department at the WMF, quarterly review

Read the full newsletter

MediaWiki message delivery (talk) 17:40, 4 March 2015 (UTC)

Sorry if ...[edit]

... my sarcasm didn't come through. That point was that there is so much paid editing going on, but "at least 5" paid editors have disclosed since June. Actually I did look around for quite some time, and I think I did find up to about 5 declarations. I'll see what I can remember and maybe update this over the next few days.

  • @CorporateM: - tries to do it the right way and declares at every opportunity. Still, it seems a bit forced (hard to explain) at times. I assume everybody knows CorpM, pretty much a good guy. I've pinged him in case he knows others who have declared.
  • @BlackCab: see Talk:A2_milk/Archive_1#Arbitrary_break:_BCM7, his declaration was on his user page, but apparently he's quit the paid editing business and taken it off his user page. My feeling - while I watched it - was that while he was likely working in good faith, he did not come in with an informed neutral outlook. Thus he was causing a bit of a mess, that took others awhile to cleanup.
  • There was a huge mess at Banc de Binary right as the ToU were changed. At least one of BdB's paid edits did declare, but I don't think (IMHO) BdB had the least idea how to conduct ethical business on Wikipedia. The extremely serious legal problems they had with the SEC and the CFTC suggests a general problem as well.

(i'll remember more later)

Smallbones(smalltalk) 19:48, 7 March 2015 (UTC)

@Smallbones: - Thanks, that's helpful. I'm actually surprised how few editors openly declare they are paid editors. I understand that to some extent - they have to limit their edits, mostly, to article talk pages, and have to know how to ask for help when talk posts languish or they run into (what they think is) unreasonable opposition, and there are certainly other editors who are quite willing to harass paid editors, regardless of what they do. Still, it seems to me that there are advantages of being on the right side of the law, so to speak - the ability to ask for help, the ability to show clients exactly what your work looks like, and the ability to build reputation without risking being blocked (or, alternatively, to use throwaway accounts, which again doesn't allow reputation to be built.)
So yes, if you do remember others, or come across others, I'd like to know. (One more that I do know of is User:I'm Tony Ahn.) -- John Broughton (♫♫) 20:09, 7 March 2015 (UTC)
Forced? Maybe, not sure what that means. "Pretty much" a nice guy, I suppose implies "sometimes a jerk" - I'll cop to that ;-)
Regarding Banc de Binary, that page has at least 30 primary sources cited for contentious material, which is to say almost all of them. If it were a BLP, I would be allowed to delete almost the entire page regardless of consensus or edit-warring. I'm not sure if that page reflects more poorly on the paid editor, or on the Wikipedia community. Both sides seem so eager to point fingers at the others' deficiencies.
From what I've seen on-and-off by chance, Bell Pottinger is doing pretty decent work these days. I helped @HOgilvy: with Dany Bahar a while back and it was a good piece - a rare find for COI-produced pages. Plus they assumed good faith even with a tad of badgering - I was impressed.
The Request Edit queue will give you dozens of disclosed COIs, but mostly for people who work directly for the org or person. PRSA's survey found that only 1% of PR respondents out-sourced to a paid editing firm, so that seems representative.
The problem with disclosure is that doing something evil in the open is even more frustrating than doing it in secret, so in actuality it all boils down to the edits.CorporateM (Talk) 22:05, 7 March 2015 (UTC)

Tech News: 2015-11[edit]

15:18, 9 March 2015 (UTC)

The Signpost: 11 March 2015[edit]

Tech News: 2015-12[edit]

15:15, 16 March 2015 (UTC)

Tech News: 2015-13[edit]

15:09, 23 March 2015 (UTC)

Invitation[edit]

A gummi bear holding a sign that says "Thank you"
Thank you for using VisualEditor and sharing your ideas with the developers.

Hello, John Broughton,

The Editing team is asking for your help with VisualEditor. I am contacting you because you posted to a feedback page for VisualEditor. Please tell them what they need to change to make VisualEditor work well for you. The team has a list of top-priority problems, but they also want to hear about small problems. These problems may make editing less fun, take too much of your time, or be as annoying as a paper cut. The Editing team wants to hear about and try to fix these small things, too. 

You can share your thoughts by clicking this link. You may respond to this quick, simple, anonymous survey in your own language. If you take the survey, then you agree your responses may be used in accordance with these terms. This survey is powered by Qualtrics and their use of your information is governed by their privacy policy.

More information (including a translateable list of the questions) is posted on wiki at mw:VisualEditor/Survey 2015. If you have questions, or prefer to respond on-wiki, then please leave a message on the survey's talk page.

Unsubscribe from this list Sign up for VisualEditor's multilingual newsletterTranslate the user guide

Thank you, Whatamidoing (WMF) (talk) 15:56, 26 March 2015 (UTC)

Tech News: 2015-14[edit]

15:18, 30 March 2015 (UTC)

VisualEditor News #2—2015[edit]

VisualEditor-logo.svg
Did you know?

With Citoid in VisualEditor, you click the 'book with bookmark' icon and paste in the URL for a reliable source:


Screenshot of Citoid's first dialog


Citoid looks up the source for you and returns the citation results. Click the green "Insert" button to accept its results and add them to the article:


Screenshot of Citoid's initial results


After inserting the citation, you can change it. Select the reference, and click the "Edit" button in the context menu to make changes.


The user guide has more information about how to use VisualEditor.

Since the last newsletter, the Editing Team has fixed many bugs and worked on VisualEditor's performance, the Citoid reference service, and support for languages with complex input requirements. Status reports are posted on Mediawiki.org. The worklist for April through June is available in Phabricator.

The weekly task triage meetings continue to be open to volunteers, each Wednesday at 11:00 (noon) PDT (18:00 UTC). You do not need to attend the meeting to nominate a bug for consideration as a Q4 blocker. Instead, go to Phabricator and "associate" the Editing team's Q4 blocker project with the bug. Learn how to join the meetings and how to nominate bugs at mw:Talk:VisualEditor/Portal.

Recent improvements[edit]

VisualEditor is now substantially faster. In many cases, opening the page in VisualEditor is now faster than opening it in the wikitext editor. The new system has improved the code speed by 37% and network speed by almost 40%.

The Editing team is slowly adding auto-fill features for citations. This is currently available only at the French, Italian, and English Wikipedias. The Citoid service takes a URL or DOI for a reliable source, and returns a pre-filled, pre-formatted bibliographic citation. After creating it, you will be able to change or add information to the citation, in the same way that you edit any other pre-existing citation in VisualEditor. Support for ISBNs, PMIDs, and other identifiers is planned. Later, editors will be able to improve precision and reduce the need for manual corrections by contributing to the Citoid service's definitions for each website.

Citoid requires good TemplateData for your citation templates. If you would like to request this feature for your wiki, please post a request in the Citoid project on Phabricator. Include links to the TemplateData for the most important citation templates on your wiki.

The special character inserter has been improved, based upon feedback from active users. After this, VisualEditor was made available to all users of Wikipedias on the Phase 5 list on 30 March. This affected 53 mid-size and smaller Wikipedias, including AfrikaansAzerbaijaniBretonKyrgyzMacedonianMongolianTatar, and Welsh.

Work continues to support languages with complex requirements, such as Korean and Japanese. These languages use input method editors ("IMEs”). Recent improvements to cursoring, backspace, and delete behavior will simplify typing in VisualEditor for these users.

The design for the image selection process is now using a "masonry fit" model. Images in the search results are displayed at the same height but at variable widths, similar to bricks of different sizes in a masonry wall, or the "packed" mode in image galleries. This style helps you find the right image by making it easier to see more details in images.

You can now drag and drop categories to re-arrange their order of appearance ​on the page.

The pop-up window that appears when you click on a reference, image, link, or other element, is called the "context menu". It now displays additional useful information, such as the destination of the link or the image's filename. The team has also added an explicit "Edit" button in the context menu, which helps new editors open the tool to change the item.

Invisible templates are marked by a puzzle piece icon so they can be interacted with. Users also will be able to see and edit HTML anchors now in section headings.

Users of the TemplateData GUI editor can now set a string as an optional text for the 'deprecated' property in addition to boolean value, which lets you tell users of the template what they should do instead (T90734).

Looking ahead[edit]

The special character inserter in VisualEditor will soon use the same special character list as the wikitext editor. Admins at each wiki will also have the option of creating a custom section for frequently used characters at the top of the list. Instructions for customizing the list will be posted at mediawiki.org.

The team is discussing a test of VisualEditor with new users, to see whether they have met their goals of making VisualEditor suitable for those editors. The timing is unknown, but might be relatively soon.

Let's work together[edit]

  • Share your ideas and ask questions at mw:VisualEditor/Feedback.
  • Can you translate from English into any other language? Please check this list to see whether more interface translations are needed for your language. Contact us to get an account if you want to help!
  • The design research team wants to see how real editors work. Please sign up for their research program.
  • File requests for language-appropriate "Bold" and "Italic" icons for the character formatting menu in Phabricator.

Subscribe, unsubscribe or change the page where this newsletter is delivered at Meta. If you aren't reading this in your favorite language, then please help us with translations! Subscribe to the Translators mailing list or contact us directly, so that we can notify you when the next issue is ready. Thank you!

-Whatamidoing (WMF) (talk), 17:50, 3 April 2015 (UTC)

Tech News: 2015-15[edit]

15:42, 6 April 2015 (UTC)

A new reference tool[edit]

Hello Books & Bytes subscribers. There is a new Visual Editor reference feature in development called Citoid. It is designed to "auto-fill" references using a URL or DOI. We would really appreciate you testing whether TWL partners' references work in Citoid. Sharing your results will help the developers fix bugs and improve the system. If you have a few minutes, please visit the testing page for simple instructions on how to try this new tool. Regards, MediaWiki message delivery (talk) 18:47, 10 April 2015 (UTC)

Tech News: 2015-16[edit]

16:40, 13 April 2015 (UTC)

Tech News: 2015-17[edit]

15:30, 20 April 2015 (UTC)

Tech News: 2015-18[edit]

15:10, 27 April 2015 (UTC)

Joining the Signpost[edit]

Hey John, you've been a frequent voice on Signpost talk pages for several years. Have you ever thought about coming on board and helping us out? Ed [talk] [majestic titan] 00:05, 30 April 2015 (UTC)

Support request with team editing experiment project[edit]

Dear tech ambassadors, instead of spamming the Village Pump of each Wikipedia about my tiny project proposal for researching team editing (see here: https://meta.wikimedia.org/wiki/Grants:IdeaLab/Research_team_editing), I have decided to leave to your own discretion if the matter is relevant enough to inform a wider audience already. I would appreciate if you could appraise if the Wikipedia community you are more familiar with could have interest in testing group editing "on their own grounds" and with their own guidance. In a nutshell: it consists in editing pages as a group instead of as an individual. This social experiment might involve redefining some aspects of the workflow we are all used to, with the hope of creating a more friendly and collaborative environment since editing under a group umbrella creates less social exposure than traditional "individual editing". I send you this message also as a proof that the Inspire Campaign is already gearing up. As said I would appreciate of *you* just a comment on the talk page/endorsement of my project noting your general perception about the idea. Nothing else. Your contribution helps to shape the future! (which I hope it will be very bright, with colors, and Wikipedia everywhere) Regards from User:Micru on meta.

Tech News: 2015-19[edit]

15:12, 4 May 2015 (UTC)

Books and Bytes - Issue 11[edit]

Wikipedia Library owl.svg The Wikipedia Library

Bookshelf.jpg

Books & Bytes
Issue 11, March-April 2015
by The Interior (talk · contribs), Ocaasi (talk · contribs), Sadads (talk · contribs), Nikkimaria (talk · contribs)

  • New donations - MIT Press Journals, Sage Stats, Hein Online and more
  • New TWL coordinators, conference news, and new reference projects
  • Spotlight: Two metadata librarians talk about how library professionals can work with Wikipedia

Read the full newsletter



MediaWiki message delivery (talk) 23:25, 4 May 2015 (UTC)

Tech News: 2015-20[edit]

15:43, 11 May 2015 (UTC)

Tech News: 2015-21[edit]

15:21, 18 May 2015 (UTC)

Tech News: 2015-22[edit]

16:16, 25 May 2015 (UTC)

Tech News: 2015-23[edit]

15:39, 1 June 2015 (UTC)

VisualEditor News #3—2015[edit]

VisualEditor-logo.svg
Did you know?

When you click on a link to an article, you now see more information:

Screenshot showing the link tool's context menu


The link tool has been re-designed:

Screenshot of the link inspector


There are separate tabs for linking to internal and external pages.

The user guide has more information about how to use VisualEditor.

Since the last newsletter, the Editing Team has created new interfaces for the link and citation tools, as well as fixing many bugs and changing some elements of the design. Some of these bugs affected users of VisualEditor on mobile devices. Status reports are posted on Mediawiki.org. The worklist for April through June is available in Phabricator.

A test of VisualEditor's effect on new editors at the English Wikipedia has just completed the first phase. During this test, half of newly registered editors had VisualEditor automatically enabled, and half did not. The main goal of the study is to learn which group was more likely to save an edit and to make productive, unreverted edits. Initial results will be posted at Meta later this month.

Recent improvements[edit]

Auto-fill features for citations are available at a few Wikipedias through the citoid service. Citoid takes a URL or DOI for a reliable source, and returns a pre-filled, pre-formatted bibliographic citation. If Citoid is enabled on your wiki, then the design of the citation workflow changed during May. All citations are now created inside a single tool. Inside that tool, choose the tab you want (<citoid-citeFromIDDialog-mode-auto>, <citoid-citeFromIDDialog-mode-manual>, or <citoid-citeFromIDDialog-mode-reuse>). The cite button is now labeled with the word "Cite" rather than a book icon, and the autofill citation dialog now has a more meaningful label, "<Citoid-citeFromIDDialog-lookup-button>", for the submit button.

The link tool has been redesigned based on feedback from Wikipedia editors and user testing. It now has two separate sections: one for links to articles and one for external links. When you select a link, its pop-up context menu shows the name of the linked page, a thumbnail image from the linked page, Wikidata's description, and/or appropriate icons for disambiguation pages, redirect pages and empty pages. Search results have been reduced to the first five pages. Several bugs were fixed, including a dark highlight that appeared over the first match in the link inspector (T98085).  

The special character inserter in VisualEditor now uses the same special character list as the wikitext editor. Admins at each wiki can also create a custom section for frequently used characters at the top of the list. Please read the instructions for customizing the list at mediawiki.org. Also, there is now a tooltip to describing each character in the special character inserter (T70425).

Several improvements have been made to templates. When you search for a template to insert, the list of results now contains descriptions of the templates. The parameter list inside the template dialog now remains open after inserting a parameter from the list, so that users don’t need to click on "Add more information" each time they want to add another parameter (T95696). The team added a new property for TemplateData, "Example", for template parameters. This optional, translatable property will show up when there is text describing how to use that parameter (T53049).

The design of the main toolbar and several other elements have changed slightly, to be consistent with the MediaWiki theme. In the Vector skin, individual items in the menu are separated visually by pale gray bars. Buttons and menus on the toolbar can now contain both an icon and a text label, rather than just one or the other. This new design feature is being used for the cite button on wikis where the Citoid service is enabled.

The team has released a long-desired improvement to the handling of non-existent images. If a non-existent image is linked in an article, then it is now visible in VisualEditor and can be selected, edited, replaced, or removed.

Let's work together[edit]

  • Share your ideas and ask questions at mw:VisualEditor/Feedback.
  • The weekly task triage meetings continue to be open to volunteers, each Wednesday at 12:00 (noon) PDT (19:00 UTC). Learn how to join the meetings and how to nominate bugs at mw:Talk:VisualEditor/Portal. You do not need to attend the meeting to nominate a bug for consideration as a Q4 blocker. Instead, go to Phabricator and "associate" the Editing team's Q4 blocker project with the bug.
  • If your Wikivoyage, Wikibooks, Wikiversity, or other community wants to have VisualEditor made available by default to contributors, then please contact James Forrester.
  • If you would like to request the Citoid automatic reference feature for your wiki, please post a request in the Citoid project on Phabricator. Include links to the TemplateData for the most important citation templates on your wiki.

Subscribe, unsubscribe or change the page where this newsletter is delivered at Meta. If you aren't reading this in your favorite language, then please help us with translations! Subscribe to the Translators mailing list or contact us directly, so that we can notify you when the next issue is ready. Thank you! Whatamidoing (WMF) (talk) 17:31, 6 June 2015 (UTC)

Ping[edit]

Hi John,

The research project about VisualEditor will be moving into the data-analysis phase this week, so I'm personally asking a few "regulars" at WP:VEF to let me know if they’d seen anything unusual during the last week or two. (You're in the top 10 all-time editors at WP:VEF.) Anyway, if you've seen anything or have any thoughts on it, then please let me know. There's a thread open at Wikipedia:VisualEditor/Feedback#Test feedback if you want, or you can always leave a note at my talk page or send me e-mail.

Also, my current "when I have some time" goal is to replace screenshots at the user guide. It's a bit of a mess; linking, tables, and citations all need to be re-done almost from scratch. I'm currently thinking that the citation section will need to be split, with a main/summary style. On the upside, we might be able to talk about how to add ==Further reading== items using citation templates. Thanks, Whatamidoing (WMF) (talk) 06:25, 7 June 2015 (UTC)

@Whatamidoing (WMF): I don't tend to pay attention to what other editors are doing; you've quite correctly asked the folks who do, at Wikipedia talk:Recent changes patrol. So I can't be helpful with the analysis, at least up-front. I do have some background in analytics, and am quite interested in (hopefully preliminary) results from the A/B testing.
On the matter of the user guide, it's quite a challenge to keep that current, agreed. I've thought about a second version of WP:TMM, based on VE rather than the wikitext editor (and with screencasts rather than step-by-step written tutorials), but that makes no sense until the UI stabilizes a great deal more. If you want help on the text of the updated user guide, please let me know.
Regarding ==Further reading==, yes, the entries in that section are in fact citations without the <ref> tag wrappers. The same situation applies to citing a source on a talk page - while this can be done as a footnote, it's better to leave the <ref> tags off. The solution might be as simple as a checkbox, visible when the cite dialog starts, that is labeled "not a footnote" - if checked, the output of the cite process would have the normal <ref> tags omitted.
Finally, I note that I'm going to be at WMF in San Francisco on Friday the 26th, in the afternoon, for an editathon in conjunction with the American Library Association annual conference. If you're around, it would be great to say "hi". -- John Broughton (♫♫) 15:36, 7 June 2015 (UTC)
Quick link for you: User:EpochFail keeps a public worklog at m:Research talk:VisualEditor's effect on newly registered editors, so if you want to drop by and see what's happening (or contribute your own, even), then you can always find the latest. Whatamidoing (WMF) (talk) 00:33, 8 June 2015 (UTC)

User guide - citations[edit]

Heads up that I've created a royal mess for you at mw:Help:VisualEditor/User guide/Citations, and that I hope you'll feel like re-structuring, re-organizing, and re-writing it. (In my defense, I'll add that splitting the page off like this means that there is currently zero translation markup on it, which means that section editing is possible once again.)

I haven't counted, but I think I need to create about another dozen screenshots. What do you think about using this for the basic order?
  1. Toolbar/basic introduction to the pieces we're using (do we need this?)
  2. Adding a basic citation via the Insert menu (assuming that the Basic citation item is supposed to be in the Insert menu; I'm confirming), including viewing the citation by selecting it to see the context menu.
  3. Inserting a references list at the end of the page.
  4. Adding citations if Citoid is enabled:
    1. Automagic version, including the insert-then-edit sequence
    2. Manual version, focused on templates but mentioning the existence of the free-form "Basic"
    3. Re-using
  5. Adding citations if Citoid is not enabled:
    1. Cite menu
    2. Using one of the citation templates
    3. Mentioning the existence of "Basic"
    4. Re-using
  6. Inserting citation templates without putting them in ref tags, e.g., for ==Further reading== or shortened citations.
"Editing an existing one" is missing here, but I'm not sure whether that should go after the "basic citation" item or in each subsection, or at the end (before the ==Further reading== section). What do you think? (I need to get back over to VPPR to answer some questions, and I'm hoping to get offline later today, but ping me whenever you want.) Whatamidoing (WMF) (talk) 19:29, 26 June 2015 (UTC)
...and the "Basic" item is being yanked from the Insert menu. So my proposed structure is now invalid. Whatamidoing (WMF) (talk) 19:35, 26 June 2015 (UTC)
@Whatamidoing (WMF): Well, you've definitely interested me. I'll start with a question: what do you mean by "Citoid is not enabled"? I started editing a page while logged out (using /veaction=edit), and still saw what looked like Citoid to me. I ask, of course, because if Citoid is always enabled, the user guide is simpler. -- John Broughton (♫♫) 20:40, 26 June 2015 (UTC)
@Whatamidoing (WMF): Okay, I can answer my own question: "enabled" is a yes/no thing for each language Wikipedia, rather than being related to whether a user is logged on or not.
To answer your question, regarding what I think, I still like the organization of the existing user manual (edit existing; reuse; create new). Suggested changes:
  • Add "The toolbar" section, as with the new page you've created, numbered section 5.1, and renumbering 5.1 through 5.3 to be 5.2 through 5.4
  • For the (renumbered) section 5.4, add a new 5.4.1, Using the automatic citation. That would include a disclaimer that some wikis may not have enabled this, in which case see 5.4.2 and 5.4.3
  • For the (renumbered) sections 5.4.2 and 5.4.3., discuss, if necessary, very briefly, the two routes by which a user might get to these citation options. [Do you have screenshots of the alternative path, for wikis that haven't enabled Citoid? I'm really, really hoping that the initial Cite dialog box is the same, but with two tabs, not three, in which case the two paths are trivially different, but it would be very nice to see this confirmed, or not. Or, alternatively, could you tell me a wiki where Citoid is not yet enabled?] -- John Broughton (♫♫) 22:50, 26 June 2015 (UTC)
I will cheerfully follow your advice about the order.
No, the design isn't the same. I can make all the screenshots for you. Without Citoid = what everyone had a couple of months ago. You can see it still at simple: (random article there). And then there's actually the minor complication of not having the citation templates enabled, which is still true at small Wikipedias (and mediawiki.org). See the Ido Wikipedia for what that looks like.
This multi-interface complication is why I split the citation page off to a sub-page. I decided that we can do a better job with a classic split-page style (summary on the main page, details on the subpage) because of this. (Also, Wikipedians in particular might only want information about how to cite stuff. I expect that some of the bigger Wikipedias will omit the entire section about "Adding citations if Citoid is not enabled", because it won't be relevant to them.) Whatamidoing (WMF) (talk) 23:11, 26 June 2015 (UTC)
@Whatamidoing (WMF): Having just tried to edit the new page using VE (that was a FAIL), and then looking at it using the wikitext editor, I'm inclined to believe that it's undesirable to ask/expect editors in any language to delete a subsection that doesn't apply to them, as you're suggesting, or to delete parts of a subsection, as I was thinking of suggesting. So, here's an alternative: create three versions of the page Help:VisualEditor/User guide/Citations, one named "Citations-Full", one named "Citations-Templates", and one named Citations-Basic". Each of the three pages would then not need any "if" statements, and while a bit more work to create, the versions would be fairly similar, so not that much more work.
The other half of this is to enable wikis to select which of the three versions would be active in the main user guide. The main user guide would have three transclusions, next to each other, with two of them commented out. [Perhaps "Citations-Basic" would be the default, not commented out, in deference to the smallest wikis.] Then all that is needed, other than the translations themselves, for wikis where the default transcluded page is the wrong one (say, for en wiki), is simply to edit the main user guide to comment out the default transclusion and uncomment the preferred alternative.
Does that make sense to you? Am I missing something? -- John Broughton (♫♫) 03:02, 28 June 2015 (UTC)
Yes. Actually, now that you suggest it, it seems perfectly obvious that the end user (the audience for the page) is best served by having exactly what s/he needs for the local wiki, rather than three sets of options.
I can open the page in VisualEditor, but I haven't sorted out how to insert an image in a table cell. It's all still wrapped in table formatting (which we can remove if you want). Whatamidoing (WMF) (talk) 18:02, 28 June 2015 (UTC)

Quick summary, so I can get things right for you:

Elitre is going to update her list of pages for translators soon, so I'd like to have the pages/page titles settled by early next week. Whatamidoing (WMF) (talk) 00:35, 2 July 2015 (UTC)

I think that mw:Help:VisualEditor/User guide/Citations-Templates is ready for you. Please let me know what other screenshots you want, or if anything's wrong. There are a couple that are out of date in minor ways, but I think I fixed all of the howlers. Whatamidoing (WMF) (talk) 20:08, 6 July 2015 (UTC)
@Whatamidoing (WMF): Okay, done. Some notes:
  • File:VisualEditor - Editing references 18.png has out-of-date text in the search box (the narrative for the image is different, and correct).
  • The value for {{Intcurrent}} is showing, in the user guide, as "Insert", but the image, File:VisualEditor - Editing references - Cite book required fields.png shows "Insert citation". (I'm guessing that the image is wrong.)
  • In the user manual, I use the phrase "general references", in plain text. That wording appears as a default in the Reference dialog; I'm guessing that it's a VE field/parameter/whatever.
  • Similarly, I've used this phrase - click on "Add template" - twice in the user guide, but almost certainly there is a VE field/parameter/whatever for this.
  • And similarly, in the "Editing an existing footnote" section, you'll find this phrase - Clicking on the "Edit" button - and this - clicking on "Edit".
  • To answer a question of yours, elsewhere, I have mixed feelings about showing a Basic footnote that isn't a citation. On the one hand, it's a bit limited to associate footnotes with nothing other than citations in the user manual. On the other hand, footnotes other than citations aren't common, and beginners really ought to focus on citations, not on other types of footnotes. Plus adding complexity to the user manual has potential costs. All in all, I'd personally rather err on the side of excess simplicity, since editors encountering non-citation footnotes presumably can puzzle them out. But if you decide differently, that's fine, and I've revised the text in the manual so that it fits better with a non-citation footnote. (As an aside, the image you provided can't be used; it's a screenshot of a basic footnote being modified, rather than being created.)
  • Finally, in revising the manual, I'm favorably impressed by how much more obvious the flow of user actions seem to be - for example, now clicking on "Edit" rather than, previously, clicking directly on the text of a template in order to start editing that template. -- John Broughton (♫♫) 01:05, 7 July 2015 (UTC)

Animated gifs[edit]

Do you think that any of these animated gifs would be desirable for the user guide? Whatamidoing (WMF) (talk) 22:36, 2 July 2015 (UTC)

@Whatamidoing (WMF):Interesting. I'm inclined to say "no" for two reasons. The lesser is because if two of these are close to one another in the user manual, that would be distracting. The more major reason is that the gifs running continually is a big negative. When you're reading the user guide, you're going to be distracted. Worse, you can't tell when the gif begins, because it's on a loop; while you can eventually puzzle it out, that takes time.
If the gifs were small video clips, where the user clicks the play icon, and the clip runs for five seconds or so, I'd definitely be in favor. (I've said a number of times that, in hindsight, the tutorials in WP:TMM should have been screencasts; I think these are really good for step-by-step procedures.) I also suggest slowing down the pace a bit (in screencasts, this is accomplished implicitly because of the voice-over narration), and typing in text, rather than pasting it, at least the first time the text is used. -- John Broughton (♫♫) 22:58, 2 July 2015 (UTC)

Terminology[edit]

Basic footnote, context menu
Basic footnote, editing dialog

What do you think about the idea in phab:T85679? Whatamidoing (WMF) (talk) 17:37, 1 July 2015 (UTC)

I think this is classic developer behavior - (a) identify a problem [correctly], (b) treat something that is non-technical (in this case, a semantical problem) as a technical matter (in this case, by not asking the community to help), and (c) assign the lowest priority to a task that has absolutely minimal programming work, almost guaranteeing that - despite the minimal programming work involved [as opposed to community discussion] - the problem will not actually be addressed. [To restate (c): not comparing the cost to the benefits]
More constructively: I'd be happy to see the user guide consistently refer to citations and references as "footnotes", and to say something along the lines of "a footnote normally contains information about a source which provides reliable information in support of the text in an article", and "footnotes are often called 'citations' or 'references'". If you agree, I'll be happy to edit the user guide accordingly. -- John Broughton (♫♫) 18:00, 1 July 2015 (UTC)
If you are happy with that, then I'm happy with it.
My next question: What do you think about using a non-bibliographic example for the basic/manual footnote? You can see my proposed screenshots above (in my sandbox, if you want to fix it or change the content). Whatamidoing (WMF) (talk) 00:27, 2 July 2015 (UTC)

Tech News: 2015-24[edit]

15:21, 8 June 2015 (UTC)

The Wikipedia Library needs you![edit]

Wikipedia Library owl.svg The Wikipedia Library

Bookshelf.jpg
Call for Volunteers

The Wikipedia Library is expanding, and we need your help! With only a couple of hours per week, you can make a big difference in helping editors get access to reliable sources and other resources. Sign up for one of the following roles:

  • Account coordinators help distribute research accounts to editors.
  • Partner coordinators seek donations from new partners.
  • Outreach coordinators reach out to the community through blog posts, social media, and newsletters or notifications.
  • Technical coordinators advise on building tools to support the library's work.
Sign up to help here :)

Delivered on behalf of The Wikipedia Library by MediaWiki message delivery (talk) 06:16, 11 June 2015 (UTC)

Franklin Center[edit]

Oops, sorry for the misunderstanding, and thanks for the clarification. --Dr. Fleischman (talk) 23:47, 12 June 2015 (UTC)

@DrFleischman: No problem - I appreciated your clear edit summary, which let me figure out what was going on. -- John Broughton (♫♫) 23:57, 12 June 2015 (UTC)

Tech News: 2015-25[edit]

15:04, 15 June 2015 (UTC)

Tech News: 2015-26[edit]

15:24, 22 June 2015 (UTC)

Requesting your cooperation[edit]

Hello,

I usually volunteer to study different communities and Wiki-projects. You can glance thru some of my blogposts here. I am also trying to study NIH-WMF collaboration and made some initial progress. But I need your cooperation as I believe you were also one of the instructors who rendered their valuable service in this direction. --Muzammil (talk) 12:09, 15 June 2015 (UTC)

@Hindustanilanguage: I'd be happy to help, if I can. Yes, I was one of the volunteers at Wikipedia:Academy/NIH 2009, though not (in my opinion) one of the more involved, or important, members of the Wikipedia group at that event.
It's probably best to send me an email, describing what sort of information you're looking for. You can do that via "Email this user" (on the tools menu at the left, as I'm sure you're aware, but I mention just in case). -- John Broughton (♫♫) 15:06, 15 June 2015 (UTC)
Hi John, the WMF blog team has changed some of its policies regarding blogposts. I've requested some clarification regarding possible new blogposts. Once I get this, I'll revert to you. Otherwise there is no point in us putting effort when the outcome is not used anywhere. --Muzammil (talk) 09:51, 27 June 2015 (UTC)

Tech News: 2015-27[edit]

15:56, 29 June 2015 (UTC)

Reference errors on 2 July[edit]

Hello, I'm ReferenceBot. I have automatically detected that an edit performed by you may have introduced errors in referencing. It is as follows:

Please check this page and fix the errors highlighted. If you think this is a false positive, you can report it to my operator. Thanks, ReferenceBot (talk) 00:17, 3 July 2015 (UTC)

Tech News: 2015-28[edit]

15:13, 6 July 2015 (UTC)

The Wikipedia Library needs you![edit]

Wikipedia Library owl.svg

We hope The Wikipedia Library has been a useful resource for your work. TWL is expanding rapidly and we need your help!

With only a couple hours per week, you can make a big difference for sharing knowledge. Please sign up and help us in one of these ways:

  • Account coordinators: help distribute free research access
  • Partner coordinators: seek new donations from partners
  • Communications coordinators: share updates in blogs, social media, newsletters and notices
  • Technical coordinators: advise on building tools to support the library's work
  • Outreach coordinators: connect to university libraries, archives, and other GLAMs
  • Research coordinators: run reference services


Sign up now


Send on behalf of The Wikipedia Library using MediaWiki message delivery (talk) 04:31, 7 July 2015 (UTC)

Tech News: 2015-29[edit]

15:06, 13 July 2015 (UTC)

Books and Bytes - Issue 12[edit]

Wikipedia Library owl.svg The Wikipedia Library

Bookshelf.jpg

Books & Bytes
Issue 12, May-June 2015
by The Interior (talk · contribs), Ocaasi (talk · contribs), Sadads (talk · contribs), Nikkimaria (talk · contribs)

  • New donations - Taylor & Francis, Science, and three new French-language resources
  • Expansion into new languages, including French, Finnish, Turkish, and Farsi
  • Spotlight: New partners for the Visiting Scholar program
  • American Library Association Annual meeting in San Francisco

Read the full newsletter

The Interior 15:23, 16 July 2015 (UTC)

Tech News: 2015-30[edit]

03:05, 21 July 2015 (UTC)

Tech News: 2015-31[edit]

15:05, 27 July 2015 (UTC)

Progress[edit]

Hi John,

With Ceyockey's help, I made some progress on a new area for the user guide: how to add content in a ref, after a citation template. You can see the results at mw:Help:VisualEditor/User guide/Citations-Full#Manually_editing_an_automatic_citation. I think that I included enough text to show you what I meant, but it needs help. Also, once you're happy with that, we should re-do it (mostly swapping in new images) for the non-Citoid system. Whatamidoing (WMF) (talk) 19:07, 28 July 2015 (UTC)

@Whatamidoing (WMF): Well, I do have to say that the first steps in that process are (technical term) ugly. I've posted a suggestion at WP:VE/F to eliminate them, though there are clearly tradeoffs; I'm hoping someone can build on my suggestion.
In the meantime, I've edited the user guide, so - it's back to you. -- John Broughton (♫♫) 22:14, 28 July 2015 (UTC)
I completely agree with you about the ugliness of the process. IMO it's less-ugly without the citoid service installed (but still not pretty). Whatamidoing (WMF) (talk) 14:24, 29 July 2015 (UTC)

Bill Niederst listed at Redirects for discussion[edit]

Information.svg

An editor has asked for a discussion to address the redirect Bill Niederst. Since you had some involvement with the Bill Niederst redirect, you might want to participate in the redirect discussion if you have not already done so. Magioladitis (talk) 12:11, 31 July 2015 (UTC)

Tech News: 2015-32[edit]

15:51, 3 August 2015 (UTC)

Lists[edit]

I have just realized that we have almost nothing about lists in the user guide, and since this is now possible:

  • Beginning
    • Three characters
      1. First pig builds a house of straw.
      2. Second pig builds a house of sticks.
      3. Third pig builds a house of bricks.
  • Middle
    • Introduce the wolf.
      • Blow down the straw house.
      • Blow down the stick house.
  • End
    • Wolf fails to blow down the brick house.
    • Kill the wolf.

it's probably time. I've created a placeholder at mw:Help:VisualEditor/User guide#Editing lists. Whenever I get good screenshots made for you, I'll let you know. Whatamidoing (WMF) (talk) 16:52, 5 August 2015 (UTC)

@Whatamidoing (WMF): Sounds good - let me know when you'd like me to jump in. And just a quibble, but the last item probably should be something like "Wolf runs away", both for political correctness and to correspond to the traditional version described in The Three Little Pigs. -- John Broughton (♫♫) 17:14, 5 August 2015 (UTC)
BTW, I'm thinking about taking a few hours to create a fake article for the purpose of making screenshots and maybe even videocasts. See mw:Topic:Smg3tzz5xft57kua for a summary. I'm thinking about using an astronomy theme, because we can use some awesome NASA photos without needing to worry about attribution. What do you think? Whatamidoing (WMF) (talk) 16:12, 10 August 2015 (UTC)

mw:Help:VisualEditor/User guide#Editing lists awaits you. I've got two screenshots for one step; one's in place and the other is linked, so you can pick whichever you like. Any screenshot can be redone, or I can add circles and arrows (but not paragraphs typed on the back) to anything that you would like. If you need more or different ones, just let me know. This is my first test run for the sample article idea. I may turn it into an article about a fictional word, but for right now, it was easier to use simple facts.

Also, in terms of overall layout, do you prefer all images on the left or right, or do you prefer having them alternate (e.g., images on the left for the citation section, and images on the right for the table section)? Whatamidoing (WMF) (talk) 18:45, 13 August 2015 (UTC)

@Whatamidoing (WMF): I've done some editing. Regarding your question of image placement, I've never considered that. Upon reflection, I suggest that when the image shows something that the user is supposed to do, the image should be on the left, as, for example, with the first image in the "Editing lists" section. (Conceptually: the user sees the image, then - looking right - sees instructions on what do.) But when the image is passive - simply showing what has happened, as, for example, "Here is the result of increased indentation", then the image should be to the right. (Conceptually: the text announces what the user is seeing.) Hopefully that makes sense to you, but if not - or where it doesn't give clear guidance - I don't see any reason why images shouldn't remain [mainly] on the left.
Also, I did a bit of editing of the next two sections. -- John Broughton (♫♫) 23:14, 14 August 2015 (UTC)

Feature[edit]

About this: It's a feature, not a bug. Bugs are unintentional.  ;-)  Whatamidoing (WMF) (talk) 23:30, 5 August 2015 (UTC)

@Whatamidoing (WMF): I wasn't aware of that subcategory of the "feature" class; thanks for pointing it out. I spent an interesting year, in 1999, coordinating the U.C. Berkeley response to an interesting feature: squeezing what ideally would have been an eight-character field (MMDDYYYY) into only six spaces (MMDDYY). That, of course, had been a necessary feature back in the days of 80-column punched cards. -- John Broughton (♫♫) 23:54, 5 August 2015 (UTC)

VisualEditor News #4—2015[edit]

Read this in another languageLocal subscription listSubscribe to the multilingual edition

VisualEditor-logo.svg
Did you know?

You can add quotations marks before and after a title or phrase with a single click.

Select the relevant text. Find the correct quotations marks in the special character inserter tool (marked as Ω in the toolbar).

Screenshot showing the special character tool, selected text, and the special character that will be inserted


Click the button. VisualEditor will add the quotation marks on either side of the text you selected.

Screenshot showing the special character tool and the same text after the special character has been inserted


You can read and help translate the user guide, which has more information about how to use VisualEditor.

Since the last newsletter, the Editing Team have been working on mobile phone support. They have fixed many bugs and improved language support. They post weekly status reports on mediawiki.org. Their workboard is available in Phabricator. Their current priorities are improving language support and functionality on mobile devices.

Wikimania[edit]

The team attended Wikimania 2015 in Mexico City. There they participated in the Hackathon and met with individuals and groups of users. They also made several presentations about VisualEditor and the future of editing.

Following Wikimania, we announced winners for the VisualEditor 2015 Translathon. Our thanks and congratulations to users Halan-tul, Renessaince, जनक राज भट्ट (Janak Bhatta), Vahe Gharakhanyan, Warrakkk, and Eduardogobi.

For interface messages (translated at translatewiki.net), we saw the initiative affecting 42 languages. The average progress in translations across all languages was 56.5% before the translathon, and 78.2% after (+21.7%). In particular, Sakha improved from 12.2% to 94.2%; Brazilian Portuguese went from 50.6% to 100%; Taraškievica went from 44.9% to 85.3%; Doteli went from 1.3% to 41.2%. Also, while 1.7% of the messages were outdated across all languages before the translathon, the percentage dropped to 0.8% afterwards (-0.9%).

For documentation messages (on mediawiki.org), we saw the initiative affecting 24 languages. The average progress in translations across all languages was 26.6% before translathon, and 46.9% after (+20.3%).  There were particularly notable achievements for three languages. Armenian improved from 1% to 99%; Swedish, from 21% to 99%, and Brazilian Portuguese, from 34% to 83%. Outdated translations across all languages were reduced from 8.4% before translathon to 4.8% afterwards (-3.6%).

We published some graphs showing the effect of the event on the Translathon page. Face-smile.svg Thank you to the translators for participating and the translatewiki.net staff for facilitating this initiative.

Recent improvements[edit]

Auto-fill features for citations can be enabled on each Wikipedia. The tool uses the citoid service to convert a URL or DOI into a pre-filled, pre-formatted bibliographic citation. You can see an animated GIF of the quick, simple process at mediawiki.org. So far, about a dozen Wikipedias have enabled the auto-citation tool. To enable it for your wiki, follow the instructions at mediawiki.org.

Your wiki can customize the first section of the special character inserter in VisualEditor. Please follow the instructions at mediawiki.org to put the characters you want at the top. 

In other changes, if you need to fill in a CAPTCHA and get it wrong, then you can click to get a new one to complete. VisualEditor can now display and edit Vega-based graphs. If you use the Monobook skin, VisualEditor's appearance is now more consistent with other software.  

Future changes[edit]

The team will be changing the appearance of selected links inside VisualEditor. The purpose is to make it easy to see whether your cursor is inside or outside the link. When you select a link, the link label (the words shown on the page) will be enclosed in a faint box. If you place your cursor inside the box, then your changes to the link label will be part of the link. If you place your cursor outside the box, then it will not. This will make it easy to know when new characters will be added to the link and when they will not.

On the English Wikipedia, 10% of newly created accounts are now offered both the visual and the wikitext editors. A recent controlled trial showed no significant difference in survival or productivity for new users in the short term. New users with access to VisualEditor were very slightly less likely to produce results that needed reverting. You can learn more about this by watching a video of the July 2015 Wikimedia Research Showcase. The proportion of new accounts with access to both editing environments will be gradually increased over time. Eventually all new users have the choice between the two editing environments.

Let's work together[edit]

  • Share your ideas and ask questions at Wikipedia:VisualEditor/Feedback.
  • Can you read and type in Korean or Japanese? Language engineer David Chan needs people who know which tools people use to type in some languages. If you speak Japanese or Korean, you can help him test support for these languages. Please see the instructions at mw:VisualEditor/IME Testing#What to test if you can help.
  • If your wiki would like VisualEditor enabled on another namespace, you can file a request in Phabricator. Please include a link to a community discussion about the requested change.
  • Please file requests for language-appropriate "Bold" and "Italic" icons for the styling menu in Phabricator.
  • The design research team wants to see how real editors work. Please sign up for their research program.
  • The weekly task triage meetings continue to be open to volunteers, usually on Tuesdays at 12:00 (noon) PDT (19:00 UTC). Learn how to join the meetings and how to nominate bugs at mw:VisualEditor/Weekly triage meetings. You do not need to attend the meeting to nominate a bug for consideration as a Q1 blocker, though. Instead, go to Phabricator and "associate" the main VisualEditor project with the bug.

If you aren't reading this in your favorite language, then please help us with translations! Subscribe to the Translators mailing list or contact Elitre directly, so that she can notify you when the next issue is ready. Thank you! Whatamidoing (WMF) (talk) 00:01, 8 August 2015 (UTC)

Public Storage[edit]

Hi John. I seem to remember (and correct me if I'm wrong) that you were sort of encouraging me not to bother you with day-to-day Request Edits for minor stuff, but you were interested in helping when things got sticky. This page has been a bit of a drama explosion, in particular due to a GA review that was picked up just hours after I nominated (usually takes months) and completed within a short time frame. The original article was written by someone that was engaged in a lawsuit with the company and I was recruited to put something more encyclopedic in place.

This discussion is where things are at right now. If you have time to participate, I think having an un-involved editor that wasn't engaged in the drama about the GA review participate for a while would help prevent people from strangling each other. CorporateM (Talk) 04:57, 8 August 2015 (UTC)

If I'm not bothering you too much this could also use a diplomatic, un-involved editor's sustained attention, but it's difficult to get anyone involved for more than a single post. I suspect on many counts other editors are correct - I'm a bit outside my element on medical pages, but once someone mocks me for being a paid editor, at that point I no longer know on which points I may legitimately be incorrect, and on which points they may just not want me contributing. Also, one of the other editors and I got in a spat on the Acupuncture page a while back that was followed by a short period of stalking and finding argument on other pages. I don't think they are still stalking me and it would be routine for us to encounter each other by chance, but it seems ripe for similar problems/drama as the PS page. I'd understand if you don't have time for both.
In other news, I just hit 40 GAs. These two are somewhat rare in being so problematic. CorporateM (Talk) 01:35, 11 August 2015 (UTC)
Congratulations on the 40 GAs! I realize that your goal isn't to demonstrate that paid editors can add lots of value to Wikipedia, but since that's a topic of interest to me, I'm glad you're providing an excellent example.
I think the PS discussion is moving in a constructive direction, so I'm happy; let's see how things progress. As for Invisalign article, it looks like there are at least two open issues: the lead paragraph(s?), and the arrangement of (some?) sections of the article. Is that correct, or are there more than those two? -- John Broughton (♫♫) 03:27, 11 August 2015 (UTC)
Paid editors can be helpful in some cases, but I always remind people that I only accept 30% of inquiries I receive, because in most cases there is no ethical way to obtain the article-subject's desired outcome without breaching Wikipedia's policies. A lot of potential clients say their article is overly critical, and I respond by saying that more criticism is actually needed, etc.. Recently I've seen a few cases where PR reps were bringing borderline attack pages to our attention - very useful. In most cases I can persuade article-subjects to abstain just through education and consulting - they aren't evil.
Yah those are the two open discussions right now. With the article-structure, for the sake of focusing on one thing at-a-time, I was trying to focus the discussion on whether there should be a separate Cost section, rather than consolidating it with a "Comparison to" or "Advantage/Disadvantages" section. Both Dental Update[1] and the other accessible source[261] mention costs in more of a pros/cons, advantages/disadvantages context, so I think we should follow suite with the sources, rather than creating a dedicated section on the product's main disadvantage and not even mentioning its primary benefit (aesthetics). CorporateM (Talk) 05:18, 11 August 2015 (UTC)
I can provide PDFs by email if you need access to some of the sources. There's literally only 3 MEDRS-compliant sources in PubMed, so it's not a lot, but I remember the Dental Update piece being very hard to get the full-text of. CorporateM (Talk) 05:22, 11 August 2015 (UTC)
  1. ^ Malik, Ovals; McMullin, Allbhe; Waring, David (April 2013). "Invisible Orthodontics Part 1: Invisalign". Dental Update. PMID 23767109. 

Tech News: 2015-33[edit]

14:57, 10 August 2015 (UTC)

IYO, What happens to pageviews count when a page is moved?[edit]

Hi John,

Just reading the section about moving a page in your Missing Manual book, and wondering whether you could advice on the following challenge:

I'm trying to use the very cool stats.grok.se to get page-views data for article.

1. One challenge is that the data in stats.grok is per URL, not per article, so when the page is moved.

2. Using the Wikipedia API I managed to get hold of all the dates and URL changes I need, The new link data is only relevant from when the change is mad, BUT I'm not sure how to treat old-link page-views after the date of the page move:

3. After the page-move - there are many times pageviews numbers for the same days on both links. For example: for this movie: - these data start 21 Aug 2008, but the Revision history shows that was a date of a link change. AND - Old link data continues after the link change date.

If New_link_data was always the maximum page-views, I could assume the old location is still getting hits just as users are being redirected from it to the new page location. but this is not he case. Also I know that redirects to the old-location don't get automatically redirected to the new location. I have two options of getting a measure of number of daily hits for an article, as far as I can see:

A. On the date of page move - start using new-location data and ignore old-location data B. From the date of page move, add the pageviews for old and new locations for each day of data.

My problem is: - Option A will be an under-estimation if some users who are interested in the article still only get to the old location (e.g. from redirects). BTW what do such users see - just a redirect message? - Option B will be an over-estimation if the redirect creates 2 hits for a user which is re-directed - one in the old location and another in the new location. I'd appreciate any advice. Again - great tool! Thanks, Michael

I'd be grateful for any advice about the issue or who I should ask! Kind Regards Michael

MichaelWhite1982 (talk) 12:41, 11 August 2015 (UTC)

@MichaelWhite1982: Interesting question. I'm not quite sure I understand "Also I know that redirects to the old-location don't get automatically redirected to the new location." That's not how redirects work - they are automatic, unless the redirect is to a page on another wiki (for example, mediawiki.org) - and that's not relevant to articles.
More to the point, I'd recommend posting this question to WP:VPT - that's where all the technical people hang out, and this is the sort of question that would interest them - and someone might be able to answer it off-the-cuff. -- John Broughton (♫♫) 16:15, 11 August 2015 (UTC)

Thanks John. I have and indeed got great answers. Apparently simply summing the page views per day on the old and new locations is the answer since there won't be cases of a duplicated hit. MichaelWhite1982 (talk) 20:32, 11 August 2015 (UTC)

Nomination for deletion of Template:House Races 2006[edit]

Ambox warning blue.svgTemplate:House Races 2006 has been nominated for deletion. You are invited to comment on the discussion at the template's entry on the Templates for discussion page. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 17:53, 13 August 2015 (UTC)

Tech News: 2015-34[edit]

16:17, 17 August 2015 (UTC)

Sample page[edit]

I think that mw:Help:Sample page is nearly done, except:

  1. adding an infobox (which one?) (and maybe some other template);
  2. maybe adding something that uses computer code or preformatted text; and
  3. simplifying the language, to make things easier on the translators (says the woman who just added a section from a John Donne poem  ;-).

The next use will be screenshots for citations. I've added three citations: one manually formatted about a book, and two using a citation template (a 2008 version of {{cite journal}}). Can you think of anything else that I should add? Whatamidoing (WMF) (talk) 23:03, 19 August 2015 (UTC)

@Whatamidoing (WMF): I agree that an infobox would be good. {{Infobox planet}} comes to mind. The article Earth uses this; if you go with that infobox, it obviously would be best to use only a few parameters. I don't see a good reason to use another template.
Code is used relatively rarely in Wikipedia articles; I don't see the need. Plus, with VE, it's not really different than bolding or making text italics.
I've done a bit of editing to simplify the language, but it seems pretty straightforward. -- John Broughton (♫♫) 00:20, 24 August 2015 (UTC)
Thanks. I added a few more things today. I've also agreed that James F can have it in British English.  :-) Whatamidoing (WMF) (talk) 19:04, 25 August 2015 (UTC)

I've reached the "test drive" stage. I've replaced most of the screenshots above mw:Help:VisualEditor/User_guide#Editing_templates. Eventually, I'm going to have to get back to figuring out the main citation section. Whatamidoing (WMF) (talk) 00:36, 29 August 2015 (UTC)

I've made some progress over the last few days. There are a handful of obvious problems, like images on the wrong side of the table or half the size they should be. But I think that everything *except* the main refs section and templates is done. I made some progress on the templates section, but it needs more. The Tables section definitely needs a complete re-write.
Feel free to request any more/different screenshots that you want. I expect to be online a lot this week, so I should be able to give you any screenshots you want. Also, I've added a hatnote at the top to discourage translation markup, to make it easier for you to get the writing done without having to fight the translation code. You may remove it whenever you are ready to have it marked for translation. Whatamidoing (WMF) (talk) 05:16, 2 September 2015 (UTC)
@Whatamidoing (WMF): I thought, while I'm at it, to play around a bit more with the sample page, since that is still marked as not for translation. If you were happy with it as it was, feel free to revert.
As for user manual, I've finished editing it, I think - but if you see sections that you'd like another review of, just let me know.
In the "Editing Templates" section, some issues:
  • I've set up one new subsection heading in the "Editing Templates" section, and put text where I suggest putting two other subsection headings.
  • You'll find excess translate sections that should be deleted; please review the translation chunking throughout this section, since I moved text between rows.
  • And a "transclusion" link that isn't behaving.
  • I'm fine with the screenshots except
  • File:VisualEditor - Template editing 1.png, which is out-of-date: the pop-up window contains an "Edit" link
  • All the images that are in what I'm suggesting be the "Template parameters" subsection have "Show options" as a button/link - but that's now been changed. Given that I'm suggesting that one image be deleted, I think the remaining four images need changing.
  • The first two images in the "Substituting templates" section (again, "Show options" is no longer what is in the dialog).
The "Editing tables" section and "Editing references" sections are done, too. -- John Broughton (♫♫) 22:20, 6 September 2015 (UTC)
I had the same problem with the "Transclusion" item and have referred it to Guillaume, who is the master of all things related to the translation extension. I can't tell from your comment whether I owe you six or nine images. However, several of those are already on my list, and my hope is to get those done late today or tomorrow. Whatamidoing (WMF) (talk) 19:09, 9 September 2015 (UTC)
@Whatamidoing (WMF): I've revised the wording of my comment, above, to make it clearer. The images I think need revision now total seven. -- John Broughton (♫♫) 19:40, 9 September 2015 (UTC)

I've made a few changes, and have left a few notes about what still needs to be done at mw:Help_talk:VisualEditor/User_guide#Updates. There will be more, but it should all be small tweaks from here. I am removing the "don't translate this yet!" tag and will let Shirayuki mark it up whenever he wants to. Whatamidoing (WMF) (talk) 19:00, 11 September 2015 (UTC)

Tech News: 2015-35[edit]

13:02, 24 August 2015 (UTC)

Tech News: 2015-36[edit]

21:36, 31 August 2015 (UTC)

Tech News: 2015-37[edit]

17:29, 7 September 2015 (UTC)

Your feedback on a short series of tutorials[edit]

Hi John,

I was told that I should speak with you about a short series of videos I'm making about how to edit Wikipedia. If you are interested, could you email me at vgrigas@wikimedia.org ? I'd love your feedback. VGrigas (WMF) (talk) 20:49, 9 September 2015 (UTC)

Tech News: 2015-38[edit]

16:17, 14 September 2015 (UTC)

Tech News: 2015-39[edit]

18:29, 21 September 2015 (UTC)

Tech News: 2015-40[edit]

15:15, 28 September 2015 (UTC)

Books and Bytes - Issue 13[edit]

Wikipedia Library owl.svg The Wikipedia Library

Bookshelf.jpg

Books & Bytes
Issue 13, August-September 2015
by The Interior (talk · contribs), Ocaasi (talk · contribs), Sadads (talk · contribs), Nikkimaria (talk · contribs)

  • New donations - EBSCO, IMF, more newspaper archives, and Arabic resources
  • Expansion into new languages, including Viet and Catalan
  • Spotlight: Elsevier partnership garners controversy, dialogue
  • Conferences: PKP, IFLA, upcoming events

Read the full newsletter

The Interior via MediaWiki message delivery (talk) 16:30, 1 October 2015 (UTC)

Tech News: 2015-41[edit]

18:32, 5 October 2015 (UTC)

VisualEditor update[edit]

VisualEditor-logo-pacifico.svg
This note is only delivered to English Wikipedia subscribers of the visual editor's newsletter.

The location of the visual editor's preference has been changed from the "Beta" tab to the "Editing" section of your preferences on this wiki. The setting now says Temporarily disable the visual editor while it is in beta. This aligns en.wiki with almost all the other WMF wikis; it doesn’t mean the visual editor is complete, or that it is no longer “in beta phase” though.

This action has not changed anything else for editors: it still honours editors’ previous choices about having it on or off; logged-out users continue to only have access to wikitext; the “Edit” tab is still after the “Edit source” one. You can learn more at the visual editor’s talk page.

We don’t expect this to cause any glitches, but in case your account no longer has the settings that you want, please accept our apologies and correct it in the Editing tab of Special:Preferences. Thank you for your attention, Elitre (WMF) -16:32, 7 October 2015 (UTC)

This ain't an alternative form of the WIP template, correct? Thanks a lot for the updates you made, --Elitre (WMF) (talk) 17:06, 7 October 2015 (UTC)
@Elitre (WMF): You're welcome. And no, I'm not planning to personally revise that page. In general, I'm sort-of waiting for VE to be less beta-ish before I'm willing to invest time in rewriting the English-language user guide. -- John Broughton (♫♫) 17:34, 7 October 2015 (UTC)

Tech News: 2015-43[edit]

16:02, 19 October 2015 (UTC)

Tech News: 2015-44[edit]

18:04, 26 October 2015 (UTC)

VisualEditor News #5—2015[edit]

Read this in another languageSubscription list for this multilingual newsletter

VisualEditor-logo.svg
Did you know?
You can use the visual editor on smartphones and tablets.

Screenshot showing the menu for switching from the wikitext editor to VisualEditor

Click the pencil icon to open the editor for a page. Inside that, use the gear menu in the upper right corner to "Switch to visual editing".

The editing button will remember which editing environment you used last time, and give you the same one next time. The desktop site will be switching to a system similar to this one in the coming months.

You can read and help translate the user guide, which has more information about how to use the visual editor.

Since the last newsletter, the VisualEditor Team has fixed many bugs, added new features, and made some small design changes. They post weekly status reports on mediawiki.org. Their workboard is available in Phabricator. Their current priorities are improving support for languages like Japanese and Arabic, making it easier to edit on mobile devices, and providing rich-media tools for formulæ, charts, galleries and uploading.

Recent improvements[edit]

Educational features: The first time you use the visual editor, it now draws your attention to the Link and Cite tools. When you click on the tools, it explains why you should use them. (T108620) Alongside this, the welcome message for new users has been simplified to make editing more welcoming. (T112354) More in-software educational features are planned.

Links:  It is now easier to understand when you are adding text to a link and when you are typing plain text next to it. (T74108T91285) The editor now fully supports ISBN, PMID or RFC numbers. (T109498, T110347, T63558)  These "magic links" use a custom link editing tool.

Uploads:  Registered editors can now upload images and other media to Commons while editing. Click the new tab in the "Insert Media" tool. You will be guided through the process without having to leave your edit. At the end, the image will be inserted. This tool is limited to one file at a time, owned by the user, and licensed under Commons's standard license. For more complex situations, the tool links to more advanced upload tools. You can also drag the image into the editor. This will be available in the wikitext editor later.

Mobile:  Previously, the visual editor was available on the mobile Wikipedia site only on tablets. Now, editors can use the visual editor on any size of device. (T85630)  Edit conflicts were previously broken on the mobile website. Edit conflicts can now be resolved in both wikitext and visual editors. (T111894) Sometimes templates and similar items could not be deleted on the mobile website. Selecting them caused the on-screen keyboard to hide with some browsers. Now there is a new "Delete" button, so that these things can be removed if the keyboard hides. (T62110) You can also edit table cells in mobile now.

Rich editing tools:  You can now add and edit sheet music in the visual editor. (T112925)  There are separate tabs for advanced options, such as MIDI and Ogg audio files. (T114227 and T113354)  When editing formulæ and other blocks, errors are shown as you edit. It is also possible to edit some types of graphs; adding new ones, and support for new types, will be coming.

On the English Wikipedia, the visual editor is now automatically available to anyone who creates an account. The preference switch was moved to the normal location, under Special:Preferences.

Future changes[edit]

You will soon be able to switch from the wikitext to the visual editor after you start editing. (T49779) Previously, you could only switch from the visual editor to the wikitext editor. Bi-directional switching will make possible a single edit tab. (T102398) This project will combine the "Edit" and "Edit source" tabs into a single "Edit" tab, similar to the system already used on the mobile website. The "Edit" tab will open whichever editing environment you used last time.

Let's work together 5[edit]

If you can't read this in your favorite language, then please help us with translations! Subscribe to the Translators mailing list or contact us directly, so that we can notify you when the next issue is ready. Thank you!

Whatamidoing (WMF) 04:16, 30 October 2015 (UTC)

Hi John,
I've added placeholders for the image uploading feature at the user guide. I think that design is stable, so I'll make screenshots soon.
If memory serves, the musical scores work the same as poems in terms of interface. I'm therefore weakly inclined to omit them, but I would be happy to follow your advice either way. If there anything else in this list that you think should be included? Whatamidoing (WMF) (talk) 17:06, 30 October 2015 (UTC)
@Whatamidoing (WMF): My inclination would be to have separate sections for poems and musical scores, because I think that people jump to the section of interest, rather than reading the manual linearly - so length isn't an issue. It is a bit more work to write, of course.
As for what else should be included, I'd recommend a separate high-level item that covers switching in mid-edit to the wikitext editor; obviously this would become switching to and from the wikitext editor, once this week's code changes take effect. -- John Broughton (♫♫) 16:37, 2 November 2015 (UTC)
I've made notes in Phab about it, and cc:d you. This way I won't forget.  ;-) Whatamidoing (WMF) (talk) 16:55, 2 November 2015 (UTC)

Tech News: 2015-45[edit]

16:43, 2 November 2015 (UTC)

Speedy deletion nomination of Wikipedia:VisualEditor/Updates/August 15, 2013[edit]

If this is the first article that you have created, you may want to read the guide to writing your first article.

You may want to consider using the Article Wizard to help you create articles.

Hello, and welcome to Wikipedia. This is a notice that the page you created was tagged as a test page under section G2 of the criteria for speedy deletion and has been or soon may be deleted. Please use the sandbox for any other tests you want to do. Take a look at the welcome page if you would like to learn more about contributing to our encyclopedia.

If you think this page should not be deleted for this reason, you may contest the nomination by visiting the page and clicking the button labelled "Contest this speedy deletion". This will give you the opportunity to explain why you believe the page should not be deleted. However, be aware that once a page is tagged for speedy deletion, it may be removed without delay. Please do not remove the speedy deletion tag from the page yourself, but do not hesitate to add information in line with Wikipedia's policies and guidelines. If the page is deleted, and you wish to retrieve the deleted material for future reference or improvement, then please contact the deleting administrator, or if you have already done so, you can place a request here. Liz Read! Talk! 13:43, 5 November 2015 (UTC)

Tech News: 2015-46[edit]

17:18, 9 November 2015 (UTC)

Tech News: 2015-47[edit]

19:39, 16 November 2015 (UTC)

ArbCom elections are now open![edit]

Hi,
You appear to be eligible to vote in the current Arbitration Committee election. The Arbitration Committee is the panel of editors responsible for conducting the Wikipedia arbitration process. It has the authority to enact binding solutions for disputes between editors, primarily related to serious behavioural issues that the community has been unable to resolve. This includes the ability to impose site bans, topic bans, editing restrictions, and other measures needed to maintain our editing environment. The arbitration policy describes the Committee's roles and responsibilities in greater detail. If you wish to participate, you are welcome to review the candidates' statements and submit your choices on the voting page. For the Election committee, MediaWiki message delivery (talk) 13:09, 23 November 2015 (UTC)

ArbCom elections are now open![edit]

Hi,
You appear to be eligible to vote in the current Arbitration Committee election. The Arbitration Committee is the panel of editors responsible for conducting the Wikipedia arbitration process. It has the authority to enact binding solutions for disputes between editors, primarily related to serious behavioural issues that the community has been unable to resolve. This includes the ability to impose site bans, topic bans, editing restrictions, and other measures needed to maintain our editing environment. The arbitration policy describes the Committee's roles and responsibilities in greater detail. If you wish to participate, you are welcome to review the candidates' statements and submit your choices on the voting page. For the Election committee, MediaWiki message delivery (talk) 13:33, 23 November 2015 (UTC)

Tech News: 2015-48[edit]

20:26, 23 November 2015 (UTC)

Tech News: 2015-49[edit]

16:16, 30 November 2015 (UTC)

Tech News: 2015-50[edit]

17:52, 7 December 2015 (UTC)

Advice on the Introduction to tables tutorial[edit]

Hi,

I've found your contributions and opinions on help pages useful previously so if you have a moment would you mind taking a look at the Introduction to tables tutorial?

It's has been partially complete for a few years. I've had a go at updating it but it would be really useful to have a few other editors have a quick look over to see what content and detail level the community think needs to be included. The centralised talk page for discussion is here

Any suggestions or advice on content and depth would be helpful. T.Shafee(Evo﹠Evo)talk 12:25, 8 December 2015 (UTC)

Books and Bytes - Issue 14[edit]

Wikipedia Library owl.svg The Wikipedia Library

Bookshelf.jpg

Books & Bytes
Issue 14, October-November 2015
by The Interior (talk · contribs), Ocaasi (talk · contribs), Sadads (talk · contribs), Nikkimaria (talk · contribs)

  • New donations - Gale, Brill, plus Finnish and Farsi resources
  • Open Access Week recap, and DOIs, Wikipedia, and scholarly citations
  • Spotlight: 1Lib1Ref - a citation drive for librarians

Read the full newsletter

The Interior, via MediaWiki message delivery (talk) 19:12, 10 December 2015 (UTC)

Tech News: 2015-51[edit]

17:42, 14 December 2015 (UTC)

Tech News: 2015-52[edit]

18:29, 21 December 2015 (UTC)

VisualEditor News #6—2015[edit]

Read this in another languageSubscription list

VisualEditor-logo.svg
Did you know?

A new, simpler system for editing will offer a single Edit button. Once the page has opened, you can switch back and forth between visual and wikitext editing.

Screenshot showing a pop-up dialog for switching from the wikitext editor to VisualEditor
If you prefer having separate edit buttons, then you can set that option in your preferences, either in a pop-up dialog the next time you open the visual editor, or by going to Special:Preferences and choosing the setting that you want:
Screenshot showing a drop-down menu in Special:Preferences

The current plan is for the default setting to have the Edit button open the editing environment you used most recently.

You can read and help translate the user guide, which has more information about how to use the visual editor.

Since the last newsletter, the VisualEditor Team has fixed many bugs and expanded the mathematics formula tool. Their workboard is available in Phabricator. Their current priorities are improving support for languages such as Japanese and Arabic, and providing rich-media tools for formulæ, charts, galleries and uploading.

Recent improvements[edit]

You can switch from the wikitext editor to the visual editor after you start editing.

The LaTeX mathematics formula editor has been significantly expanded. (T118616) You can see the formula as you change the LaTeX code. You can click buttons to insert the correct LaTeX code for many symbols.

Future changes[edit]

The single edit tab project will combine the "Edit" and "Edit source" tabs into a single "Edit" tab, like the system already used on the mobile website. (T102398) Initially, the "Edit" tab will open whichever editing environment you used last time. Your last editing choice will be stored as a cookie for logged-out users and as an account preference for logged-in editors. Logged-in editors will be able to set a default editor in the Editing tab of Special:Preferences in the drop-down menu about "Editing tabs".

The visual editor will be offered to all editors at the following Wikipedias in early 2016: Amharic, Buginese, Min Dong, Cree, Manx, Hakka, Armenian, Georgian, Pontic, Serbo-Croatian, Tigrinya, Mingrelian, Zhuang, and Min Nan. (T116523) Please post your comments and the language(s) that you tested at the feedback thread on mediawiki.org. The developers would like to know how well it works. Please tell them what kind of computer, web browser, and keyboard you are using.

In 2016, the feedback pages for the visual editor on many Wikipedias will be redirected to mediawiki.org. (T92661)

Testing opportunities[edit]

  • Please try the new system for the single edit tab on test2.wikipedia.org. You can edit while logged out to see how it works for logged-out editors, or you can create a separate account to be able to set your account's preferences. Please share your thoughts about the single edit tab system at the feedback topic on mediawiki.org or sign up for formal user research (type "single edit tab" in the question about other areas you're interested in). The new system has not been finalized, and your feedback can affect the outcome. The team particularly wants your thoughts about the options in Special:Preferences. The current choices in Special:Preferences are:
    • Remember my last editor,
    • Always give me the visual editor if possible, 
    • Always give me the wikitext editor, and 
    • Show me both editor tabs.  (This is the current state for people using the visual editor. None of these options will be visible if you have disabled the visual editor in your preferences at that wiki.)
  • Can you read and type in Korean or Japanese? Language engineer David Chan needs people who know which tools people use to type in some languages. If you speak Japanese or Korean, you can help him test support for these languages. Please see the instructions at mw:VisualEditor/IME Testing#What to test if you can help, and report it on Phabricator (Korean - Japanese) or on Wikipedia (Korean - Japanese).

If you aren't reading this in your favorite language, then please help us with translations! Subscribe to the Translators mailing list or contact us directly, so that we can notify you when the next issue is ready. Thank you!

Whatamidoing (WMF), 00:54, 24 December 2015 (UTC)

Tech News: 2016-02[edit]

16:59, 11 January 2016 (UTC)

Emeco[edit]

The article has a dedicated section called "Restoration Hardware Lawsuit". There is a discussion on the Talk page about whether an individual lawsuit should have a dedicated section like this. Was hoping you could take a look if you have a minute? David King, Ethical Wiki (CorporateM) (Talk) 20:09, 14 January 2016 (UTC)

Tech News: 2016-03[edit]

17:56, 18 January 2016 (UTC)

Tech News: 2016-04[edit]

16:39, 25 January 2016 (UTC)

Next up: Bi-directional switching[edit]

All yours. As usual, please direct any and all complaints about or desire for extra screenshots to me. Face-smile.svg Whatamidoing (WMF) (talk) 04:20, 28 January 2016 (UTC)

@Whatamidoing (WMF): Okay, back to you. -- John Broughton (♫♫) 18:57, 28 January 2016 (UTC)
I'm not getting a confirmation (from the browser) that I want to lose all my work when I switch from VE to WT. It happens WT to VE, but not the other way. Is it working for you? Whatamidoing (WMF) (talk) 23:28, 29 January 2016 (UTC)
@Whatamidoing (WMF): What you're seeing is what I saw, yesterday. That's why the VE user guide only mentions a confirmation once (WT to VE) rather than twice. I guess for some reason I thought that was the way things were supposed to be (not sure why); apologies for not mentioning it. -- John Broughton (♫♫) 23:53, 29 January 2016 (UTC)
So phab:T123960 is a one-way bug. I've added that information to the bug report.
I don't know what they're going to do about it; it'll probably get triaged next week. I suspect that this may be one of those "harder than it looks" problems. Whatamidoing (WMF) (talk) 01:21, 30 January 2016 (UTC)
Whereas the docs match reality, I'm declaring this one "done". mw:VisualEditor/Single edit tab is my next project, which means that my next User guide project is going to be delayed a bit. I was thinking that the next one should be dealing with the citation mess; does that sound best to you? Whatamidoing (WMF) (talk) 16:33, 2 February 2016 (UTC)
Sounds fine; I tend to go where you point me. (More constructively: you have a much better handle on what has changed and what needs more or better explanation.) -- John Broughton (♫♫) 01:08, 3 February 2016 (UTC)

Tech News: 2016-05[edit]

21:02, 1 February 2016 (UTC)