Wikitech-l October 2017

wikitech-l@lists.wikimedia.org

53 participants
70 discussions

Discovery Weekly Update for the week starting 2017-10-16
by Deborah Tankersley 24 Oct '17

24 Oct '17

This is the weekly update for the week starting '''2017-10-16''' ==Highlights== * Wikidata Query Service had a partial outage on 18 Oct 2017: a single client started to run an unusually high number of queries on WDQS and the overload was not prevented by our current throttling nor was it automatically detected and isolated—detailed information is on the mailing list. [0] * Discovery and Legal chatted on Oct 18 about supporting only CC0 data in the .map data namespace on Commons, in response to a community conversation; a detailed response will be prepared and released next week. [1] [2] ==Discussions== === Search === * We added more namespaces to the search results for Bengali Wikisource (Special:Search—add) [3] * David fixed an issue where users couldn't click on svwikisource search results when running a crosswiki search on svwiki; this will be in production during the week of Oct 24th [4] * David was also working on finishing up deployment-prep elasticsearch cluster to 5.5.x [5] * David launched the A/B test for testing the relaxing of the retrieval query filter using two different configurations (the test is expected to last a week) [6] * We wrapped up a series of adding content namespaces to wikis that were accidentally excluded from the default results of Special:Search (thanks to TheDJ for discovering this bug and to David for his quick fixing of the issues once the community consultation was completed by Chris K) [7] * Erik deployed a fix for when the rebuildtextindex fails when searchindex on InnoDB (no support for MyISAM) and it went into production on Oct 19 [8] === Analysis === * Mikhail finished up tasks related to establishing the baseline of metrics for SDoC—looking at querying databases [9] === Portal === * The Wikipedia.org portal page stats and translations were updated on Oct 19, 2017 [10] [11] === Maps === * MaxSem and Gehel fixed a weird bug where tileshell wasn't exiting after after being notified of updates, effectively stopping the OSM data in production from being regenerated; data updates are now back and running once a day [12] [0] https://lists.wikimedia.org/pipermail/wikidata/2017-October/011280.html [1] https://commons.wikimedia.org/wiki/Commons:Village_pump/Proposals#Proposal_… [2] https://phabricator.wikimedia.org/T154071 [3] https://phabricator.wikimedia.org/T178041 [4] https://phabricator.wikimedia.org/T177913 [5] https://phabricator.wikimedia.org/T178413 [6] https://phabricator.wikimedia.org/T177502 [7] https://phabricator.wikimedia.org/T170473 [8] https://phabricator.wikimedia.org/T177477 [9] https://phabricator.wikimedia.org/T177356 [10] https://phabricator.wikimedia.org/T128546 [11] https://phabricator.wikimedia.org/T142582 [12] https://phabricator.wikimedia.org/T177389 --- Subscribe to receive on-wiki (or opt-in email) notifications of the Discovery weekly update. https://www.mediawiki.org/wiki/Newsletter:Discovery_Weekly The archive of all past updates can be found on MediaWiki.org: https://www.mediawiki.org/wiki/Discovery/Status_updates Interested in getting involved? See tasks marked as "Easy" or "Volunteer needed" in Phabricator. [1] https://phabricator.wikimedia.org/maniphest/query/qW51XhCCd8.7/#R [2] https://phabricator.wikimedia.org/maniphest/query/5KEPuEJh9TPS/#R -- deb tankersley Product Manager, Discovery Wikimedia Foundation

1 0

Tomorrow: Weekly Technical Advice IRC Meeting
by Michael Schönitzer 24 Oct '17

24 Oct '17

Sorry for cross-posting! Reminder: Technical Advice IRC meeting again **tomorrow 3-4 pm UTC** on #wikimedia-tech. The Technical Advice IRC meeting is open for all volunteer developers, topics and questions. This can be anything from "how to get started" over "who would be the best contact for X" to specific questions on your project. If you know already what you would like to discuss or ask, please add your topic to the next meeting: https://www.mediawiki.org/ wiki/Technical_Advice_IRC_Meeting This meeting is an offer by WMDE’s tech team. Hosts of tomorrows meeting are: @addshore & @CFisch_WMDE. Hope to see you there! Michi (for WMDE’s tech team) -- Michael F. Schönitzer Wikimedia Deutschland e.V. | Tempelhofer Ufer 23-24 | 10963 Berlin Tel. (030) 219 158 26-0 http://wikimedia.de Stellen Sie sich eine Welt vor, in der jeder Mensch an der Menge allen Wissens frei teilhaben kann. Helfen Sie uns dabei! http://spenden.wikimedia.de/ Wikimedia Deutschland - Gesellschaft zur Förderung Freien Wissens e.V. Eingetragen im Vereinsregister des Amtsgerichts Berlin-Charlottenburg unter der Nummer 23855 B. Als gemeinnützig anerkannt durch das Finanzamt für Körperschaften I Berlin, Steuernummer 27/681/51985.

1 0

MediaWiki-CodeSniffer 14.1.0 released
by Kunal Mehta 24 Oct '17

24 Oct '17

Hello! MediaWiki-CodeSniffer 14.1.0 is now available for use in your MediaWiki extensions and other projects. This release features improves to the documentation-related sniffs and new upstream releases. 14.0.0 was tagged, but 14.1.0 should be used as it includes a newer upstream version. Here's the changelog since 13.0.0 * Update PHP_CodeSniffer to 3.1.1 (Paladox) * Add sniff for @params instead of @param (Umherirrender) * Better distinguish "one space before brace" and "brace on same line" (Florian Schmidt) * Typo fix in docs (MarcoAurelio) * Unwrap types in function docs from {} (Umherirrender) * Update PHP_CodeSniffer to 3.1.0 from 3.0.2 (Paladox) * Validate doc syntax (Umherirrender) Libraryupgrader and Umherirrender submitted patches for most Gerrit repositories :) Thanks, -- Legoktm

1 0

New Developers Quarterly Report's first edition
by Srishti Sethi 22 Oct '17

22 Oct '17

Hello everyone, I would like to share the first edition of the New Developers Quarterly Report <https://www.mediawiki.org/wiki/New_Developers/Quarterly/2017-10> that the Developer Relations team has produced. This report covers metrics, survey analysis and lessons learned from new developers focused activities in the previous quarter (July-September 2017). If you have questions and feedback that you would like to share with us, please add them on the discussion <https://www.mediawiki.org/wiki/Talk:New_Developers/Quarterly/2017-10> page. To receive a notification when a new report is published, subscribe here <https://www.mediawiki.org/wiki/Special:Newsletter/11/subscribe>. We plan to release a report every quarter and take action items identified from the key findings for improving our existing methods and processes. The next release will be in January 2018. If you have any questions, comments, and concerns, we will be more than happy to hear them! Thanks, Srishti -- Srishti Sethi Developer Advocate Technical Collaboration team Wikimedia Foundation https://www.mediawiki.org/wiki/User:SSethi_(WMF)

5 4

need a URL encoding expert
by Ryan Kaldari 21 Oct '17

21 Oct '17

Could someone knowledgeable about URL encoding take a look at this pull request? Thanks! https://github.com/wikimedia/DeadlinkChecker/pull/26/files

4 4

Tech Debt SIG IRC meeting...
by Jean-Rene Branaa 20 Oct '17

20 Oct '17

Hello All, For those of you that had shown interest in attending the IRC Tech Debt SIG kickoff meeting, my apologies for having to cancel it last minute. I had a minor family emergency to attend to. Unfortunately, the email I sent out only went to the internal email distribution lists. I've not yet reschedule the meeting as I was actually thinking of having the Tech Debt SIG kickoff be a topic during the first, yet to be scheduled, Code Health office hours. If you'd prefer that I set up a separate time for the IRC Tech Debt SIG kickoff, please let me know. Otherwise, please hold tight as I will be scheduling the Code Health office hours by Tuesday of next week. Cheers, JR

1 0

TechCom Radar, 2017-10-18
by Daniel Kinzler 20 Oct '17

20 Oct '17

Hello all! Here are the minutes from this week's meeting: * Last Call: Bump PHP requirement to 5.6 in 1.31. <https://phabricator.wikimedia.org/T178538>. RFC discussion minutes: <https://tools.wmflabs.org/meetbot/wikimedia-office/2017/wikimedia-office.20…>. If no pertinent concerns remain unaddressed by November 1st, this RFC will be approved fro implementation. * Next week’s IRC discussion: Don’t use FauxRequest in production code. <https://phabricator.wikimedia.org/T169266> As always, the discussion will take place in the IRC channel #wikimedia-office on Wednesday 21:00 UTC (2pm PDT, 23:00 CEST). * CommTech is looking for input on allowing extensions more control over user preferences, so they can implement global preferences. RFC discussion upcoming. <https://phabricator.wikimedia.org/T178449> * We are seeing a big JobQueue backlog again from Commons. <https://phabricator.wikimedia.org/T173710> * PDF generation: OCG has been turned off. Electron is still available, but has stability problems. ChromeDriver is being considered as an alternative. You can also find our meeting minutes at <https://www.mediawiki.org/wiki/Wikimedia_Technical_Committee/Minutes> See also the TechCom RFC board <https://phabricator.wikimedia.org/tag/mediawiki-rfcs/>. -- Daniel Kinzler Principal Platform Engineer Wikimedia Deutschland Gesellschaft zur Förderung Freien Wissens e.V.

1 0

Roadmap for continued compatibility with MySQL
by Hogan, Michael C 20 Oct '17

20 Oct '17

How many years into the future is it reasonable to expect that MySQL will remain a recommended database server for "production use" along with MariaDB now that the Foundation has switched to using MariaDB internally? I know that MariaDB claims to be drop in compatible with MySQL, but the list of variances seems to be slowly growing. References... * Compatibility - [[mw:Compatibility]] * MariaDB support? - [[mw:Topic:R1hqki3kaytylml4]] * https://mariadb.com/kb/en/library/mariadb-vs-mysql-compatibility/ Other than [[mw:Compatibility]] on mediawiki.org is there anywhere else (wiki pages, Phabricator tasks/tags, etc.) that I should check for technical roadmap information before emailing wikitech-l? Thank you! Michael

4 3

Fwd: OOjs UI 0.24.0 release (breaking change)
by Volker E. 19 Oct '17

19 Oct '17

---------- Forwarded message ---------- From: Volker Eckl <volker(a)wikimedia.org> Date: Tue, Oct 17, 2017 at 6:41 PM Subject: OOjs UI 0.24.0 release (breaking change) To: Wikimedia developers <wikitech-l(a)lists.wikimedia.org> Hello everyone, We've released OOjs UI 0.24.0, today. It will be in MediaWiki core from 1.31.0-wmf.4, which will be deployed to Wikimedia production in the regular train, starting on Tuesday 24 October. As there are five breaking changes in this release, at least nominally, please carefully consider if they affect your code. Breaking changes since last release: * Drop 'MediaWiki' backwards-compatibility theme (James D. Forrester) To better indicate usage focus, 'MediaWiki' theme got renamed to WikimediaUI' in v0.22.0. The remaining backwards-compatible alias has been dropped in this release. * icons: Drop 'stripeSideMenu' (James D. Forrester) 'stripeSideMenu' was renamed to 'draggable' and moved to 'movement' pack in v0.22.2. It's now completely dropped. Use it with it's new name from 'movement' instead. * icons: Remove 'eye'/'eyeClosed' icons (Volker E.) We want to use 'alerts' pack more deliberately in major products and moved 'eye'/'eyeClosed' out. They were deprecated in v0.23.0 in 'alerts'. Use icons from 'accessibility' pack instead. * icons: Remove 'signature' icon (Volker E.) Similar to above, we deprecated 'signature' in v0.23.0 in 'alerts'. Use icon from 'editing-advanced' pack instead. * icons: Remove 'sun' (James D. Forrester) 'sun' icon isn't in use in any of our products or products known to us, nor is it planned to be used. In order to keep things small, the icon, deprecated in v0.23.0, now has been removed. Please update your icon pack references accordingly in case you're using one of those icons. Additional details on the 4 new features, 29 code-level and accessibility changes, 24 styling and interaction design amendments, and all improvements since v0.23.0 are in the full changelog[0]. If you have any further queries or need help dealing with breaking changes, please let me know. As always, library documentation is available on mediawiki.org[1], and there is some comprehensive generated code-level documentation and interactive demos hosted on doc.wikimedia.org[2]. [0] - https://phabricator.wikimedia.org/diffusion/GOJU/browse/ master/History.md [1] - https://www.mediawiki.org/wiki/OOjs_UI [2] - https://doc.wikimedia.org/oojs-ui/master/ Best, Volker -- Senior UX Engineer, Contributors Wikimedia Foundation volker.e(a)wikimedia.org | @Volker_E

1 0

Last call: Bump PHP requirement to 5.6 in MW 1.31
by Tim Starling 19 Oct '17

19 Oct '17

Today's RFC discussion was T172165, a proposal for MediaWiki 1.31 to require PHP 7.0. There was no consensus on that proposal, due to the opinion from Ops that it is not feasible to migrate all application servers to Debian Stretch and PHP 7.0 by the expected release date of June 2018. However, there was consensus on the lesser goal of requiring PHP 5.6. So, we have created a new RFC for PHP 5.6 (T178538) and are hereby placing it into Last Call. The proposal is: MediaWiki should bump its PHP requirement to 5.6 as soon as possible, and at the latest in time for the 1.31 branch point (i.e. April 2018). "As soon as possible" means as soon as the few remaining uses of PHP 5.5 in the WMF cluster have been migrated to PHP 5.6 or later, or to HHVM. We'd like to see this migration work be given a high priority. If you have any objection to this proposal, please raise it on Phabricator before the end of the Last Call period, which will be October 31. https://phabricator.wikimedia.org/T178538 -- Tim Starling

2 1

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

Wikitech-l October 2017