Support request with team editing experiment project
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.
Hello Daniel, thank you for your interest in the Erasmusprijs 2015. We have started a mail-list for information exchange and discussions. If you want, you can subscribe to this list. --FrankTMeijer (talk) 12:56, 3 June 2015 (UTC)
Italian Wikipedia and all remaining Wikisource projects now have arbitrary access. The rollout will continue. The schedule for the next projects is at d:Wikidata:Arbitrary access.
The Content Translation tool now automatically connects translated articles to Wikidata. (Thanks Content Translation developers!) Previously translated but unconnected articles have been connected by a bot. (Thanks Amir!)
Code review of the extensions written by a team of students to improve the constraint reports and make it possible to automatically check our data against other databases. A first version will go live soon pending further codereview and fixes.
When you click on a link to an article, you now see more information:
The link tool has been re-designed:
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 and fixed many bugs and changed 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.
Auto-fill featuresfor 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 appropriate icons for disambiguation pages, redirect pages and empty pages (where applicable). 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.
The weekly task triage meetings continue to be open to volunteers, usually on Wednesday 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 Q4 blocker, though. Instead, go to Phabricator and "associate" the VisualEditor 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.
The team is planning the second VisualEditor-related "translathon" for July. Please follow this task on Phabricator for details and updates! Announcements will follow in due course.
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!
A challenge was raised to calculate the degrees of separation to Kevin Bacon. Already one routine has been produced, the next step is to use live data so that we can work on reducing the number of intermediary steps.
Hello friends! We have been hard at work these past two months. For this report:
The directory is live!
For the first time, we are happy to bring you an exhaustive, comprehensive WikiProject Directory. This directory endeavors to list every single WikiProject on the English Wikipedia, including those that don't participate in article assessment. In constructing the broadest possible definition, we have come up with a list of approximately 2,600 WikiProjects. The directory tracks activity statistics on the WikiProject's pages, and, for where it's available, statistics on the number of articles tracked by the WikiProject and the number of editors active on those articles. Complementing the directory are description pages for each project, listing usernames of people active on the WikiProject pages and the articles in the WikiProject's scope. This will help Wikipedians interested in a subject find each other, whether to seek feedback on an article or to revive an old project. (There is an opt-out option.) We have also come up with listings of related WikiProjects, listing the ten most relevant WikiProjects based on what articles they have in common. We would like to promote WikiProjects as interconnected systems, rather than isolated silos.
A tremendous amount of work went into preparing this directory. WikiProjects do not consistently categorize their pages, meaning we had to develop our own index to match WikiProjects with the articles in their scope. We also had to make some adjustments to how WikiProjects were categorized; indeed, I personally have racked up a few hundred edits re-categorizing WikiProjects. There remains more work to be done to make the WikiProject directory truly useful. In the meantime, take a look and feel free to leave feedback at the WikiProject X talk page.
Stuff in the works!
What have we been working on?
A new design template—This has been in the works for a while, of course. But our goal is to design something that is useful and cleanly presented on all browsers and at all screen resolutions while working within the confines of what MediaWiki has to offer. Additionally, we are working on designs for the sub-components featured on the main project page.
A new WikiProject talk page banner in Lua—Work has begun on implementing the WikiProject banner in Lua. The goal is to create a banner template that can be usable by any WikiProject in lieu of having its own template. Work has slowed down for now to focus on higher priority items, but we are interested in your thoughts on how we could go about creating a more useful project banner. We have a draft module on Test Wikipedia, with a demonstration.
New discussion reports—We have over 4.8 million articles on the English Wikipedia, and almost as many talk pages as well. But what happens when someone posts on a talk page? What if no one is watching that talk page? We are currently testing out a system for an automatically-updating new discussions list, like RFC for WikiProjects. We currently have five test pages up for the WikiProjects on cannabis, cognitive science, evolutionary biology, and Ghana.
SuggestBot for WikiProjects—We have asked the maintainer of SuggestBot to make some minor adjustments to SuggestBot that will allow it to post regular reports to those WikiProjects that ask for them. Stay tuned!
Semi-automated article assessment—Using the new revision scoring service and another system currently under development, WikiProjects will be getting a new tool to facilitate the article assessment process by providing article quality/importance predictions for articles yet to be assessed. Aside from helping WikiProjects get through their backlogs, the goal is to help WikiProjects with collecting metrics and triaging their work. Semi-automation of this process will help achieve consistent results and keep the process running smoothly, as automation does on other parts of Wikipedia.
Want us to work on any other tools? Interested in volunteering? Leave a note on our talk page.
More work on getting the Wikibase Quality extensions ready for deployment. They'll improve constraint checking and provide checks against 3rd party databases.
Special:UnconnectedPages had to be reworked (thanks Amir!) because of huge performance issues. Because of this it loses some functionality (being able to specify where the list starts and limiting the list to pages that have local interwiki links). We're working on bringing functionality back without the performance penalty.
Enabled arbitrary access on arwiki, cawiki, eswiki, huwiki, kowiki, rowiki, ukwiki, viwiki, and usage tracking on dewiki, ruwiki, cswiki and all s3 wikis. (ruwiki and cswiki get arbitrary access on June 23)
Finishing work on improved handling “invalid” values and statements with deleted properties.
Small breaking DOM change: Wikibase no longer adds its own h1 tag but uses MediaWiki's default .firstHeading element. (phabricator:T93534)
More work on getting the Wikibase Quality extensions ready for release. The part doing constraint violation checks should go to test.wikidata.org next week. The part doing checks against 3rd party databases will still take a bit longer but is also shaping up nicely.
Made it possible to create items even when another user is mass-creating items (phabricator:T103796)
Bene* worked more on making Wikidata work nicely on mobile
When you read a page on the mobile site, you can now see a link to go to its talk page. 
The code coloring tool has changed. You can now use many more languages. It now also works on mobile. 
You can look at a new site to learn how to reuse data from Wikimedia sites. 
Changes this week
The new version of MediaWiki will be on test wikis and MediaWiki.org from June 30. It will be on non-Wikipedia wikis from July 1. It will be on all Wikipedias from July 2 (calendar).
You can now use a tool in VisualEditor to add and edit code in color. 
When you edit a sentence in the Translate tool, it can show you older translations. They help you save time if they look alike. The older translations should now work better. If you see problems, you should report them. 
If you are an admin or have other special rights, you now need a strong password. 
You can join the next meeting with the Editing team. During the meeting, you can tell developers which bugs are the most important. The meeting will be on June 30 at 19:00 (UTC). See how to join.
When you create a new account, it will also create one on Meta-Wiki and mediawiki.org.