This is an archive of past discussions with User:Davidbuddy9. Do not edit the contents of this page. If you wish to start a new discussion or revive an old one, please do so on the current talk page.
The next Weekly Summary (February 19th) will be the 300th edition of the newsletter! To help making it special, you can share your favorite Wikidata tool, so the other readers discover nice tools
Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.
Recent changes
TemplateStyles has been deployed to the Swedish Wikipedia. TemplateStyles is a feature to make it easy to add CSS to templates without administrator privileges. This allows for better adaptability to screen sizes, especially on mobile where are half our total page views. If your community would like to be the next to have the feature, please submit a task on Phabricator. [1][2][3]
You can opt in to a new beta feature that lets you use visual diffs on history pages. [4]
The visual editor shows and lets you edit templates in one way, and reference lists in another. This meant that templates that only contain a fake reference list, like {{reflist}}, would not get updated as you edited. Now they will update as you edit, but you will no longer be able to visually edit them as templates. [5]
The abuse filter extension has a new feature contains_all that you may use to check if one or more strings are all contained in another given string. [6]
The new version of MediaWiki will be on test wikis and MediaWiki.org from 13 February. It will be on non-Wikipedia wikis and some Wikipedias from 14 February. It will be on all wikis from 15 February (calendar).
Meetings
You can join the next meeting with the Editing team. During the meeting, you can tell developers which bugs you think are the most important. The meeting will be on 13 February at 18:30 (UTC). See how to join.
You can join the technical advice meeting on IRC. During the meeting, volunteer developers can ask for advice. The meeting will be on 14 February at 16:00 (UTC). See how to join.
Here's your quick overview of what has been happening around Wikidata over the last week.
Welcome to the 300th Weekly Summary!
The weekly newsletter was started by Lydia at the very beginning of the Wikidata project, even before the first deployment, to keep the community informed about the developments, the new projects and tools. More than five years later, the newsletter is still there, its content powered by the community, and sent every week all along the years. I wanted to say a warm "thank you!" to each person who helped filling the Weekly Summary <3
Over the past years, as you know, Wikidata has grown a lot. More data, more tools, more editors and reusers, more exciting projects led by the community. The Weekly Summary has evolved with us, and the 300th edition seems a good moment to ask you all your suggestions about the newsletter, how it could continue evolving, and how you would like to improve it.
On that purpose, you can find a feedback page to express all your ideas about the Weekly Summary. We're very interested to know more about your reading habits, the parts you're more or less interested in, the new topics you would like to share with the community. Thanks in advance for filling it.
I stay available anytime to discuss with you, feel free to contact me if you have any question or concern! Cheers, Léa
A selection of cool tools on Wikidata
Here are a few tools that are recommended by some Wikidata community members. External websites, gadgets or scripts, they are very useful for Wikidata editors or users!
QuickStatements is a powerful tool that can edit or add Wikidata item en masse, via a text editor or importing a spreadsheet. (Éder Porto via Facebook)
Mix'n'match (manual), which helps us to interlink Wikidata with the rest of the web and the world :-) (Spinster, Siobhan via Twitter)
WikiShootMe! allows you to see Wikidata items plotted out on a map and shows you whether they have images or not. (Ham II)
Yair Rand's WikidataInfo script adds the QID of the equivalent Wikidata item to the page being viewed (on sister projects), along with its Wikidata label and description. (Andy Mabbett)
Recoin measures the degree of completeness of relevant properties of a Wikidata item and suggests any relevant statements that can be added to the item. (Rachmat04)
DuplicateReferences gadget adds a link to copy references and add them to other statements on the same item. (PKM)
checkConstraints gadget adds notifications on the interface to easily notice the violation of constraints and help people fixing them (Léa)
Resolve authors lists scientific articles with the property author name string (P2093) and groups them on the basis of co-authors and topic, which helps to distinguish people referred to by identical name strings. (Daniel Mietchen)
The Wiki Loves Monuments map is powered by Wikidata. You can look for a city and find the monuments around. (Stefano Sabatini via Facebook)
Fixed incomplete "Label:", "Description:" and "Statement:" entity usage messages in various places (phab:T178090). Thanks, Matěj!
Improved violation messages for ranges involving the current date (e. g. “should not be in the future”).
Continued work on caching constraint check results.
Enabled Lua fine-grained usage tracking for better performance on several more wikis: hywiki, frwiki, svwiki, itwiki, zhwiki, bewiki, nlwiki, glwiki, and Wikimedia Commons (phab:T187265phab:T186714)
Representation and grammatical features of the form can be changed using the UI (WikibaseLexeme) (phab:T173743, phab:T160525)
Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.
Recent changes
The explanation of the abbreviations on the recent changes page could overlap with the list of changes. This has been fixed. [8][9]
You can now see statistics for pageviews per wiki per country. You can see this on maps or in a table. [10]
Problems
Linter is reporting estimated counts instead of actual counts for some wikis. This is because of performance problems. You might notice a false higher number in linter counts for some categories. This will be fixed as soon as the performance problem has been fixed. [11]
Last week the way that Visual Editor displays references lists was changed. As a result, the references generated by specific templates like {{sfn}} are not visible in the references list whilst editing. [12][13]
Changes later this week
The new version of MediaWiki will be on test wikis and MediaWiki.org from 20 February. It will be on non-Wikipedia wikis and some Wikipedias from 21 February. It will be on all wikis from 22 February (calendar).
Meetings
You can join the next meeting with the Editing team. During the meeting, you can tell developers which bugs you think are the most important. The meeting will be on 20 February at 19:30 (UTC). See how to join.
You can join the technical advice meeting on IRC. During the meeting, volunteer developers can ask for advice. The meeting will be on 21 February at 16:00 (UTC). See how to join.
Future changes
The way edit summaries and log comments are stored in the database is being changed. In the future this will make longer comments possible. [14]
Edit conflicts could be solved in a different way in the future. You can test a new prototype.
Welcome to the February 2018 GOCE newsletter in which you will find Guild updates since the December edition. We got to a great start for the year, holding the backlog at nine months. 100 requests were submitted in the first 6 weeks of the year and were swiftly handled with an average completion time of 9 days.
Coordinator elections: In December, coordinators for the first half of 2018 were elected. Jonesey95 remained as lead coordinator and Corrine, Miniapolis and Tdslk as assistant coordinators. Keira1996 stepped down as assistant coordinator and was replaced by Reidgreg. Thanks to all who participated!
End of year reports were prepared for 2016 and 2017, providing a detailed look at the Guild's long-term progress.
January drive: We set out to remove April, May, and June 2017 from our backlog and all December 2017 Requests (a total of 275 articles). As with previous years, the January drive was an outstanding success and by the end of the month all but 57 of these articles were cleared. Officially, of the 38 who signed up, 21 editors recorded 259 copy edits (490,256 words).
February blitz: This one-week copy-editing blitz ran from 11 through 17 February, focusing on Requests and the last articles tagged in May 2017. At the end of the week there were only 14 pending requests, with none older than 20 days. Of the 11 who signed up, 10 editors completed 35 copy edits (98,538 words).
Thank you all again for your participation; we wouldn't be able to achieve what we have without you! Cheers from your GOCE coordinators: Jonesey95, Miniapolis, Corinne, Tdslk, and Reidgreg.
Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.
Recent changes
Checkusers and stewards can now view private data such as the IP address in the abuse log. This data is removed regularly. [15]
Problems
Last week's MediaWiki version was rolled back because of a bug. [16][17]
Since the deployment train last week until late evening on 20 February UTC, when you thanked someone for an edit, the thank went to the latest unthanked edit to that page. It didn't matter which edit you tried to give thanks for. This has been fixed. [18]
Special:Statistics did not take newly created pages into account since 13 February 2018. Because of this the statistics are recreated. [19][20][21]
Changes later this week
Users with version 10 of the Internet Explorer browser will no longer get JavaScript on Wikimedia wikis. If you use this browser on your computer, you can try upgrading to a newer version. [22]
The Wikinews wikis will switch to use the Remex parsing library. This is to replace Tidy. It will happen on 27 February. Other wikis will be recommended to switch soon when they have fixed the errors that must be fixed. Tidy will be removed in the middle of 2018. [23][24]
The new version of MediaWiki will be on test wikis and MediaWiki.org from 27 February. It will be on non-Wikipedia wikis and some Wikipedias from 28 February. It will be on all wikis from 1 March (calendar).
Meetings
You can join the next meeting with the Editing team. During the meeting, you can tell developers which bugs you think are the most important. The meeting will be on 27 February at 19:30 (UTC). See how to join.
You can join the technical advice meeting on IRC. During the meeting, volunteer developers can ask for advice. The meeting will be on 28 February at 16:00 (UTC). See how to join.
Did you know that you can now use the visual diff tool on any page?
Sometimes, it is hard to see important changes in a wikitext diff. This screenshot of a wikitext diff (click to enlarge) shows that the paragraphs have been rearranged, but it does not highlight the removal of a word or the addition of a new sentence.
If you enable the Beta Feature for "⧼visualeditor-preference-visualdiffpage-label⧽", you will have a new option. It will give you a new box at the top of every diff page. This box will let you choose either diff system on any edit.
Click the toggle button to switch between visual and wikitext diffs.
In the visual diff, additions, removals, new links, and formatting changes will be highlighted. Other changes, such as changing the size of an image, are described in notes on the side.
This screenshot shows the same edit as the wikitext diff. The visual diff highlights the removal of one word and the addition of a new sentence. An arrow indicates that the paragraph changed location.
You can read and help translate the user guide, which has more information about how to use the visual editor.
The 2017 wikitext editor is available as a Beta Feature on desktop devices. It has the same toolbar as the visual editor and can use the citoid service and other modern tools. The team have been comparing the performance of different editing environments. They have studied how long it takes to open the page and start typing. The study uses data for more than one million edits during December and January. Some changes have been made to improve the speed of the 2017 wikitext editor and the visual editor. Recently, the 2017 wikitext editor opened fastest for most edits, and the 2010 WikiEditor was fastest for some edits. More information will be posted at mw:Contributors/Projects/Editing performance.
The visual diff tool was developed for the visual editor. It is now available to all users of the visual editor and the 2017 wikitext editor. When you review your changes, you can toggle between wikitext and visual diffs. You can also enable the new Beta Feature for "Visual diffs". The Beta Feature lets you use the visual diff tool to view other people's edits on page histories and Special:RecentChanges. [25]
The citoid service automatically translates URLs, DOIs, ISBNs, and PubMed id numbers into wikitext citation templates. This tool has been used at the English Wikipedia for a long time. It is very popular and useful to editors, although it can be tricky for admins to set up. Other wikis can have this service, too. Please read the instructions. You can ask the team to help you enable citoid at your wiki.
Wikibooks, Wikiversity, and other communities may have the visual editor made available by default to contributors. If your community wants this, then please contact Dan Garry.
The <references /> block can automatically display long lists of references in columns on wide screens. This makes footnotes easier to read. This has already been enabled at the English Wikipedia. If you want columns for a long list of footnotes on this wiki, you can use either <references /> or the plain (no parameters) {{reflist}} template. If you edit a different wiki, you can request multi-column support for your wiki. [27]
If you aren't reading this in your preferred language, then please help us with translations! Subscribe to the Translators mailing list or contact us directly. We will notify you when the next issue is ready for translation. Thank you!
And so ends the first round of the competition, with 4 points required to qualify for round 2. With 53 contestants qualifying, the groups for round 2 are slightly smaller than usual, with the two leaders from each group due to qualify for round 3 as well as the top sixteen remaining users.
Our top scorers in round 1 were:
Aoba47 led the field with a featured article, 8 good articles and 42 GARs, giving a total of 666 points.
FrB.TG , a WikiCup newcomer, came next with 600 points, gained from a featured article and masses of bonus points.
Ssven2, another WikiCup newcomer, was in third place with 403 points, garnered from a featured article, a featured list, a good article and twelve GARs.
Ceranthor, Numerounovedant, Carbrera, Farang Rak Tham and Cartoon network freak all had over 200 points, but like all the other contestants, now have to start again from scratch. A good achievement was the 193 GARs performed by WikiCup contestants, comparing very favourably with the 54 GAs they achieved.
Remember that any content promoted after the end of round 1 but before the start of round 2 can be claimed in round 2. Invitations for collaborative writing efforts or any other discussion of potentially interesting work is always welcome on the WikiCup talk page. Remember, if two or more WikiCup competitors have done significant work on an article, all can claim points. If you are concerned that your nomination—whether it is at good article candidates, a featured process, or anywhere else—will not receive the necessary reviews, please list it on Wikipedia:WikiCup/Reviews.
Collaboration and Language are now going their way separately. Updates about Content Translation are not included in this newsletter anymore. Please refer to the Language report.
The wording when you send a thanks message has changed. Instead of Yes or No it says Thank and Cancel. It is also now easier to understand that all thanks are public. [36]
A notification is now sent to account owner on multiple unsuccessful login attempts. [37]
Problems
Between week 7 and 20 February, when you thanked someone for an edit, the thank went to the latest unthanked edit to that page. It didn't matter which edit you tried to give thanks for. This has been fixed. [38]
Long page titles on Special:Notifications were not truncated. This is now fixed. [39]
You can now press CTRL + ENTER to post a new message. [40]
It wasn't possible to create a description of a Structured discussions board. This has been fixed. [41]
Problems
On wikis using the Beta feature, it is not possible to enable or disable Structured discussion from the Beta page. However, admins can create and move the pages.
Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.
On Special:AbuseLog you can now choose to list only actions that actually made an edit. Other actions are when the filter warned the editor or blocked the edit from being made. There are also more search options. [44][45]
Wikis can enable Citoid to provide automatic reference look-up in the visual editor and the 2017 wikitext editor, but it is complex. The tool will now warn in the JavaScript console if the configuration isn't correct. Soon Citoid will disable itself if the configuration isn't correct. Check that your wiki is configured correctly. You can ask for help if you need it. [46]
The new version of MediaWiki will be on test wikis and MediaWiki.org from 6 March. It will be on non-Wikipedia wikis and some Wikipedias from 7 March. It will be on all wikis from 8 March (calendar).
Meetings
You can join the next meeting with the Editing team. During the meeting, you can tell developers which bugs you think are the most important. The meeting will be on 6 March at 19:30 (UTC). See how to join.
You can join the technical advice meeting on IRC. During the meeting, volunteer developers can ask for advice. The meeting will be on 7 March at 16:00 (UTC). See how to join.
Future changes
In the future you will be able to use global preferences. This means you could change a preference for all wikis instead of having to change it every time for each wiki. You can now test global preferences and give feedback.
