Wikitech-l August 2017

wikitech-l@lists.wikimedia.org

63 participants
67 discussions

Audiences Q4 FY1617 Quarterly Check-In slides & notes
by Grace Gellerman 08 Aug '17

08 Aug '17

Hi, Wikitech-l Slide decks and notes from recent Audiences Quarterly Check-Ins are posted as follows: Audiences 1 (Comm. Tech, Comm. Health, Contributors, Design, & Business Ops): slides <https://commons.wikimedia.org/wiki/File:(PUBLIC_VERSION)_Audiences_1_(Commu…> & notes <https://meta.wikimedia.org/wiki/Wikimedia_Foundation_Annual_Plan/Quarterly_…> Audiences 2 (New Readers, Readers, Structured Data, Wikidata) slides <https://commons.wikimedia.org/wiki/File:Audiences_2_(New_Readers,_Structure…> & notes <https://meta.wikimedia.org/wiki/Wikimedia_Foundation_Annual_Plan/Quarterly_…> . These and other links are also posted on the quarterly checkin page <https://meta.wikimedia.org/w/index.php?title=Wikimedia_Foundation_Annual_Pl…> . Thanks, Grace

3 3

TechCom Radar, 2017-08-02 (was: ArchCom Radar)
by Daniel Kinzler 07 Aug '17

07 Aug '17

Hi all! Due to Wikimania coming up, the TechCom Radar email is coming very late this time. Sorry about that! Here are the minutes from this week's TechCom meeting. You can also find the minutes at <https://www.mediawiki.org/wiki/Wikimedia_Technical_Committee/2017-08-02>. See also the TechCom activity page on the RFC board <https://phabricator.wikimedia.org/tag/mediawiki-rfcs/>. Here are the minutes, for your convenience: * Discussion of talk pages and contributions for IPv6 ranges happened on August 2nd, but the RFC’s author wasn’t present. The log is linked on the ticket. <https://phabricator.wikimedia.org/T171382#3496647 > * New RFC by MaxSem: Require PHP 5.6 for MediaWiki 1.31 (target summer of 2018): <https://phabricator.wikimedia.org/T172165> * TechCom will host a session about the new charter during the Wikimania Hackathon. <https://www.mediawiki.org/wiki/Talk:Architecture_committee/Charter> * The next TechCom meeting on August 9th will be a public in-person meeting at the Wikimania hackathon, at 4pm local time (that’s 1pm PDT and 20:00 UTC). This is a TechCom planning meeting, not an RFC discussion. Remote participation will be possible (probably via Google Hangout). Watch for aqn announcement in the Hackathon unconference programme. <https://wikimania2017.wikimedia.org/wiki/Hackathon/Program> * There will be no RFC discussion on August 16th, since most TechCom members will be busy with post-Wikimania activities or travel. TechCom Will resume its regular schedule on August 23rd, the next RFC discussion will probably be on August 30th. -- Daniel Kinzler Principal Platform Engineer Wikimedia Deutschland Gesellschaft zur Förderung Freien Wissens e.V.

1 0

Discovery Weekly Update for the week starting 2017-07-31
by Chris Koerner 07 Aug '17

07 Aug '17

Hello all, Here is the Discovery weekly update for 2017-07-31. As always, feedback and questions are welcome. Programming note: We'll be spending our time and attention for the next week at Wikimania (well a sizable number of us). As such, Discovery weekly updates will return the week of 14 August. == Highlights == * 2016/17 Q4 Metrics for the Discovery Department were presented on Aug 3, 2017 * The Audiences 2 (New Readers, Structured Data on Commons, Wikidata, & Readers) Quarterly Check-in, July 2017, has been published that contains the Discovery Department's update. [0] == Discussions == === Search === * Archive search on Special:Undelete enabled everywhere by Stas. [1] * We began a search relevance test to see if we could get good feedback, based on (initial) canned queries (Erik was the key person on this test to get grading feedback from humans on search results) [2] * David fixed a bug where reusing the ScriptService was hitting a circuit breaker which prevented large featuresets to be compiled in one row [3]. This isn't complete deployed yet, due to needing a new plugin version to be added into production first. * Guillaume and Chris J helped with a big issue due to some elasticsearch servers in eqiad overheating (applied thermal paste) [4] * Trey completed another round of testing and analysis on the updated Vietnamese language plugin; we're still not able to deploy it, but it has improved. We may try again later after more updates. [5] === Analysis === * Mikhail and Chelsy worked diligently on getting metrics for the Discovery Department's Q4 2016/2017 slide deck ready for delivery [6] === Maps === * Enabled mapframe for ptwikipedia, euwikipedia and uawikimedia projects (thanks, Maxǃ) [7] [0] https://commons.wikimedia.org/wiki/File%3AAudiences_2_(New_Readers%2C_Struc… [1] https://phabricator.wikimedia.org/T163235 [2] https://phabricator.wikimedia.org/T171740 [3] https://phabricator.wikimedia.org/T17157 [4] https://phabricator.wikimedia.org/T168816 [5] https://phabricator.wikimedia.org/T170423#3502328 [6] https://phabricator.wikimedia.org/T171528 [7] https://phabricator.wikimedia.org/T171805 --- 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 Yours, Chris Koerner Community Liaison Wikimedia Foundation

1 0

Creation of a Program Committee for Wikimedia developer events
by Quim Gil 04 Aug '17

04 Aug '17

Hi, I just proposed a session for the Wikimania Hackathon next week: Creation of a Program Committee for Wikimedia developer events https://phabricator.wikimedia.org/T160996 All the details are in the task. I am mentioning this here to promote the session among those of you joining the hackathon in Montreal next week, but most importantly to encourage feedback and discussion before the session and by anyone anywhere. Preferably in the task itself, to avoid fragmentation. -- Quim Gil Engineering Community Manager @ Wikimedia Foundation http://www.mediawiki.org/wiki/User:Qgil

1 0

HTML5 sections update
by Max Semenik 03 Aug '17

03 Aug '17

Hey, yesterday the patch implementing human-readable section IDs [0] was merged (thanks, Tim!). The new feature has already been enabled on beta cluster and you can try it yourselves, e.g. on [1] - some pages might still have old HTML cached though and require a null edit to update. What's next? We can probably flip it on testwiki after Wikimania, but further deployments depend on Reading Web, Apps and Parsoid teams. We, however, can already encourage editors to check it out in staging. Unanswered question: do we really need to percent-encode the IDs? There is extensive discussion of that in the aforementioned task, concluding that percent-encoding is probably more "correct". However, not escaping it gives much better browser compatibility (close to 100%). We can change this at any time because no links will be broken due to the way browsers handle percent-encoded fragments. What's the impact for end users? When the commit above goes live, there will be no user-visible changes, and almost no HTML changes at all (only some interface IDs/classes generated from MediaWiki messages might slightly change, but no links will be broken). When we migrate we will initially enable new IDs as a fallback. After 1 month, the new IDs will become default while old ones will be used as a fallback. This way, old links will continue to work, and we have no plans to disable the fallbacks in the foreseeable future. What's the impact for developers? Sanitizer::escapeId() has been deprecated, all code should migrate to escapeIdForAttribute(), escapeIdForLink() or escapeIdForExternalInterwiki(). Warning: unlike escapeId(), these functions' output is not guaranteed to be HTML-safe so it must be escaped. Our security guidelines say that everything should be HTML-safe anyway, so even escapeId() should be properly escaped. The same deprecation happened in JavaScript, mw.util.escapeId() is also deprecated. ---- [0] https://phabricator.wikimedia.org/T152540 [1] https://ru.wikipedia.beta.wmflabs.org/wiki/%D0%92%D0%B8%D0%BA%D0%B8%D0%BF%D… -- Best regards, Max Semenik ([[User:MaxSem]])

3 4

Fwd: [Wikisource-l] An it.source gadget to manage diacritics
by Pine W 03 Aug '17

03 Aug '17

I haven't tried this, but it sounds like translators and Language Engineering folks might be interested. Pine ---------- Forwarded message ---------- From: Alex Brollo <alex.brollo(a)gmail.com> Date: Tue, Aug 1, 2017 at 12:10 AM Subject: [Wikisource-l] An it.source gadget to manage diacritics To: wikisource list <wikisource-l(a)lists.wikimedia.org> Just to let it known, some it.source contributors are using a comfortable gadget to manage diacritics - it can delete, replace or add a pretty large list of diacritical marks to any character with a single click. It uses .normalize() string method, so decomposing-recomposing (when possible) unicode characters and allowing to manage diacritics alone indipendently from base ascii character. Perhaps is this gadget "rediscovering the wheel"....? Anyway, the code is here: https://it.wikisource.org/wiki/MediaWiki:Gadget-pulsanti-diacritici.js Alex brollo _______________________________________________ Wikisource-l mailing list Wikisource-l(a)lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikisource-l

1 0

MediaWiki 1.30.0-wmf.12 deployment is blocked
by Mukunda Modell 03 Aug '17

03 Aug '17

Due to today's train deployment more than doubling the error rate seen in fatalmonitor[1], I have rolled-back group 1 wikis to wmf.11. I've submitted an UBN task T172320 [2] detailing the error, which appears to be fallout from issues in Wikibase first noticed two weeks ago. I expect that this will be easily resolved once someone familiar with the issue has had a chance to look into it and the train should be back on track in time for tomorrow's deployment. 1. https://logstash.wikimedia.org/goto/5acde54fdb7b071b5723607c9f57eb9c 2. https://phabricator.wikimedia.org/T172320

3 4

(Mostly) Normal deployment schedule next week during Wikimania
by Greg Grossmeier 03 Aug '17

03 Aug '17

Hello all, Next week is Wikimania (yay!), for those of you who weren't aware. Due to having good non-Wikimania coverage in both Release Engineering and Operations we will, however, be doing the normal MediaWiki train that week along with SWAT and (if needed) service deploys. Please don't merge risky things thinking that you have an extra week to make them less risky. Best, Greg -- Greg Grossmeier Release Team Manager

1 0

[RfC] [ORES] Do you use reverted model for wikis that have damaging ones?
by Amir Tafreshi 03 Aug '17

03 Aug '17

Hey, For patrolling work, ORES usually has two levels of support: - For basic support we usually provide a model that is called 'reverted' and has less accuracy. It also risks perpetuating editor biases due to the lack of differentiation between reasons that a change may have been reverted. - For advanced support, we require manual labeling of a large sample of edits, but then we can provide two more models: 'damaging' and 'goodfaith'. ORES review tool can only be enabled on wikis where advanced support is available and most other tools prefer the 'damaging' over the basic 'reverted' model as well. So, for performance and capacity reasons we think it makes sense to remove 'reverted' models from the ORES service when 'damaging' model is made available. However, we also want to be careful about making sure this change doesn't disrupt the work of tool developers that make use of the ORES service. If you do, please voice your concerns now. If there is no objection within the next two weeks, we'll begin the process of removing the 'reverted' model for wikis that have the 'damaging' model available. Related phabricator card: https://phabricator.wikimedia.org/T171059 Best -- Amir Sarabadani Tafreshi Software Engineer (contractor) ------------------------------------- Wikimedia Deutschland e.V. | Tempelhofer Ufer 23-24 | 10963 Berlin http://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 1

Tech News – reminder & feedback
by Johan Jönsson 02 Aug '17

02 Aug '17

Hey everyone, This is an email about Tech News. Partly to introduce or explain what it is to those who might be unfamiliar with it, or have seen it but don't know it well. Partly to ask if there's anything we could do better. If you know all there’s to know, there’s a request for feedback towards the bottom of this email. ABOUT TECH NEWS a) What is Tech News? https://meta.wikimedia.org/wiki/Tech/News Tech News is a newsletter for reaching out with technical updates to the general Wikimedia editor communities, to make sure they can keep track of what's happening. It's typically distributed in 15–20 languages, reaching roughly 90 community pages (Village Pumps etc) and some 600 individual subscribers, in addition to those who read it on Meta, see it included in the Signpost or get it in their email inbox. b) How is Tech News written? Simplification is key. Technical news for non-technical readers. Should be easy to translate as well as be written with en-1 and en-2 readers in mind. A couple of sentence per item, then a link to a Phab task, wiki page or email if they need more information. Too long and we put an unreasonable burden on the translators. c) I've done something technical. The communities should know. How do I add it? * There's a "user-notice" tag in Phabricator. Add it to the task together with a simple 1–3 sentence explanation of what this is and how it affects editors. Don't worry about polish, we'll take care of that. * You can add it yourself! https://meta.wikimedia.org/wiki/Tech/News/Next will take you to the relevant issue. Remember to link to a relevant Phab task, wiki page or email. * You can always write on https://meta.wikimedia.org/wiki/Talk:Tech/News d) When is it distributed? Weekly, each Monday afternoon/evening UTC. The deadlines for additions are several days prior to that to give the translators time to do their work. See https://meta.wikimedia.org/wiki/Tech/News/For_contributors#When_is_the_work… for when to add things to have them included in the next newsletter. e) What is Tech News not? * A general Wikimedia newsletter. Everything in the Wikimedia world is at most one step removed from being technical. This doesn't mean Tech News is the best place. Typical items are new or upcoming features or potential breaking changes. * The way to reach the Wikimedia technical community. If you want to reach Wikimedia developers, an email to wikitech-l is usually better than an item in Tech News. Tech News is a way to keep Wikimedia contributors up-to-date with technical changes. * A way to talk about all the important things that happen in the background. They're often awesome and we should talk more about them, but if they don't affect how contributors interact with the sites, then this is not the place. * A place for updates about one wiki. If it's just relevant for English or German Wikipedia, you should update English or German Wikipedia, not the entire Wikimedia community. Exceptions to this rule are Commons and Wikidata, because they're used by so many other Wikimedia wikis. More: https://meta.wikimedia.org/wiki/Tech/News/For_contributors#What_is_typicall… HOW CAN WE MAKE TECH NEWS BETTER? Are there ways we could make Tech News better at spreading information about technical updates that are relevant for Wikimedia contributors? Something we do that's unnecessary? Things we're often missing? Things we fail to explain? Anything we're particularly good at and should keep doing? Tell us – on the list, on https://meta.wikimedia.org/wiki/Talk:Tech/News, or privately (: And, specifically – are there other places (wiki pages etc) where this information should be available? Anything we could do to make this easier for you? //Johan Jönsson --

1 0

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 August 2017