Wikitech-l October 2018

wikitech-l@lists.wikimedia.org

71 participants
69 discussions

2018-10-24 Scrum of Scrums meeting notes
by Grace Gellerman 25 Oct '18

25 Oct '18

https://www.mediawiki.org/wiki/Scrum_of_scrums/2018-20-24 =2018-10-24= == Callouts == * Technical Engagement ** Google Code In <https://www.mediawiki.org/wiki/Google_Code-in> starts on Tuesday 2018-10-23 and runs until 2018-12-13. GCI is a contest to encourage and inspire pre-university students to begin participating in open source development. More mentors and tasks are needed! Read mentor instructions on mediawiki.org <https://www.mediawiki.org/wiki/Google_Code-in/Mentors> or contact Andre Klapper to get involved. * Release Engineering ** revision-create event date format has changed (we think) -- new format example "2018-10-24T00:28:24.162300+00:00" -- if you know anything chime in on task please https://phabricator.wikimedia.org/T207817 ** https://gerrit.wikimedia.org/r/c/mediawiki/extensions/EventBus/+/468482 is likely the culprit == Audiences == === Contributors === ==== Community Tech ==== * Blocked by: * Blocking: * Updates: - TemplateWizard was released as a beta feature to all wikis ** ==== Anti-Harassment Tools ==== * Blocked by: * Blocking: * Updates: - Releasing Partial Blocks to beta. Some tests failed on gate-and-submit CI process (specifically with postgres), we're dealing with those. - Discovered an inconsistency with the database layer, patch pending on that: https://gerrit.wikimedia.org/r/#/c/mediawiki/core/+/469324/ ** ==== Editing ==== * Blocked by: * Blocking: Growth team on cross collaboration instrumentation ** Updates: ** Added VisualEditorFeatureUse schema ==== Growth ==== * Blocked by: **We need security review of the GrowthExperiments extension https://phabricator.wikimedia.org/T207798 **RelEng figuring out how to unblock and merge https://gerrit.wikimedia.org/r/c/integration/config/+/468171 **Editing on cross collaboration instrumentation * Blocking: * Updates: **Copyvio bot logging trial concluded on enwiki should be live on Thursday https://en.wikipedia.org/wiki/Wikipedia:Bots/Requests_for_approval/EranBot_3 **PageViews schema is on meta wiki https://meta.wikimedia.org/wiki/Schema:PageViews and we will start testing in beta this week or early next week https://gerrit.wikimedia.org/r/c/mediawiki/extensions/WikimediaEvents/+/464… ==== Language ==== * Blocked by: None * Blocking: None * Updates: ** ContentTranslation v2 work continue. ** Work on mediawiki-html-sanitizer library: https://github.com/wikimedia/mediawiki-html-sanitizer === Readers === ==== iOS native app ==== * Blocked by: * Blocking: * Updates: ** 6.1 with wikidata description editing & revert notifications in beta ( https://phabricator.wikimedia.org/tag/ios-app-v6.1-narwhal-on-a-bumper-car/) ** 6.1.1 ( https://phabricator.wikimedia.org/tag/ios-app-v6.1.1-narwhal-on-a-magic-pum…) will be a bug fix & tech debt release ** mobile editing research ==== Android native app ==== * Blocked by: * Blocking: * Updates: ** ==== Readers Web ==== * Blocked by: * Blocking: * Updates: ** Mobile website (MinervaNeue / MobileFrontend): *** Invest in the MobileFrontend & MinervaNeue frontend architecture https://www.mediawiki.org/wiki/Reading/Web/Projects/Invest_in_the_MobileFro… **** Complete webpack migration of mobile.startup T206169 **** Collapse mobile.search.util into mobile.startup T206027 **** Migrate PageGateway tests to node-qunit T206226 **** Use NPM for Hogan v2.0.0 T205128 *** Page issues https://www.mediawiki.org/wiki/Reading/Web/Projects/Mobile_Page_Issues **** A/B test will conclude soon T200792 *** Maintenance and bug fixes T207423 T207480 *** Advanced mobile contributions https://www.mediawiki.org/wiki/Reading/Web/Advanced_mobile_contributions **** Design and product continuing special pages work in Minerva ** PDF rendering (Proton) https://www.mediawiki.org/wiki/Reading/Web/PDF_Functionality *** Remaining work tracked in T186748 *** Rewrite Queue to Promises T204055 *** Upgrade Puppeteer to v1.9.0 T207416 ** SEO: *** Add Schema.org Article JSON-LD to main namespace pages T198946 *** Server side split test T206868 ** Product and management in Portland. ==== Readers Infrastructure ==== * Blocked by: * Blocking: * Updates: ** ==== Multimedia ==== * Updates ** Hiring continues ** SDoC - some progress on beta cluster deployment ** SDoC - discussion on data modelling continues ** SDoC - usability study on multi-lingual captions ** SDoC - 'depicts' upload wizard ==== Parsing ==== * Blocked by: No one * Blocking: Hopefully no one :-) * Updates: **"Untidy" parser output is being deprecated **Most system messages are being tidied in this week's train (and next week) **If you see unexpected UI changes (probably extra whitespace) let us know **HTML DOM structure might change as well (if you are doing screen scraping) ***https://gerrit.wikimedia.org/r/#/q/topic:deprecate-wgtidy ==== UI Standardization ==== * Blocked by: * Blocking: * Updates: ** == Technology == === Analytics === * Blocked by: * Blocking: * Updates: ** === Cloud Services === * Blocked by: * Blocking: * Updates: ** === Fundraising Tech === * Blocked by: * Blocking: * Updates: ** Dealing with some odd PayPal behavior regarding legacy subscriptions ** Working out county-specific issues with card processor in Latin America campaign ** Deployed new batch-mode payment spreadsheet importer ** Preparing 3 proposals for contractor work on CentralNotice - live banner previews, campaign fallback and sub-national targeting, and calendar display. === MediaWiki Core Platform === * Blocked by: * Blocking: * Updates: ** === Performance === * Blocked by: ** * Blocking: ** * Updates: ** === Release Engineering === * Blocked by: ** Train is blocked on group0 *** [https://phabricator.wikimedia.org/T207817 WDQS] problems *** revision-create event date format has changed (we think) -- new format example "2018-10-24T00:28:24.162300+00:00" -- if you know anything chime in on task please *** https://gerrit.wikimedia.org/r/c/mediawiki/extensions/EventBus/+/468482 is likely the culprit * Blocking: **Growth needs support on how to unblock and merge https://gerrit.wikimedia.org/r/c/integration/config/+/468171 * Updates: ** === Research === * Blocked by: None * Blocking: None * Updates: ** Writing a paper that researches Wikipedia section alignments across languages: https://meta.wikimedia.org/wiki/Research:Expanding_Wikipedia_articles_acros… ** Working on taking the Recommendation API to production: https://gerrit.wikimedia.org/r/#/c/mediawiki/services/recommendation-api/+/… ** Stopping data collection for citation usage schemas on 10/25: https://gerrit.wikimedia.org/r/#/c/operations/mediawiki-config/+/465418/ === Scoring Platform === * Blocked by: None * Blocking: None * Updates: ** Redis task tracker is live now, ores responses is now cut to half ** More work on upgrading to celery 4 is ongoing === Search Platform === * Blocked by: breakage in the updater ( https://phabricator.wikimedia.org/T207817) being handled * Blocking: * Updates: ** ** WDQS Updater incident: https://wikitech.wikimedia.org/wiki/Incident_documentation/20181024-WDQS - working on it ** Fixed issue with Lexeme data not being properly updated in WDQS: https://phabricator.wikimedia.org/T207673 ** Fixed search satisfaction browser tests: https://phabricator.wikimedia.org/T206232 ** Working on “wrong keyboard layout” detection: https://phabricator.wikimedia.org/T138958 ** Working on ES 6 upgrade: https://phabricator.wikimedia.org/T183282 ** Working on running multiple Elastic instances on the same hardware: https://phabricator.wikimedia.org/T193654 ** Working on query parsing refactoring: https://phabricator.wikimedia.org/T185108 === Security === * Blocked by: * Blocking: T207798 Security review for GrowthExperiments extension opened 10/23 * Updates: ** === Services === * Blocked by: * Blocking: * Updates: ** === Site Reliability Engineering === * Blocked by: * Blocking: * Updates: ** == Wikidata == * Blocked by: * Blocking: * Updates: ** == German Technical Wishlist == * Blocked by: * Blocking: * Updates: ** == Multi-Content Revisions == * Blocked by: * Blocking: * Updates: ** == SoS Meeting Bookkeeping == * Updates: **

1 0

(no subject)
by Liza Rustanto 25 Oct '18

25 Oct '18

-- *FUSION ENTREPRISES GROUPS PTY LTD* 2/14 Bloomfield Avenue MARIBYRNONG VIC 3032 Phone: (+61) 448 86 96 46 Fax: (+61)3 8679 0330 Email: info(a)fusionentreprises.com.co

1 0

flake8 python linter updated
by Antoine Musso 24 Oct '18

24 Oct '18

Hello, If you are using the python linter "flake8", a new version has been released today. If your dependency is unbound, CI will pick up the new version (3.6.0) which will most probably report new errors and breaks the build. You can either fix the lint issues, or set an upper bound to the version with: flake8<=3.6.0 Ref: https://pypi.org/project/flake8/#history -- Antoine Musso

1 0

WM Technical Conference 2018 update
by Deb Tankersley 24 Oct '18

24 Oct '18

1 0

Google Code-in 2018 just started (and will take place for the next seven weeks)
by Andre Klapper 23 Oct '18

23 Oct '18

Google Code-in 2018 just started: https://www.mediawiki.org/wiki/Google_Code-in/2018 You might remember the announcement email from a few weeks ago.[1] In the next seven weeks, many young people are going to make their first contributions to Wikimedia. Expect many questions on IRC and on mailing lists by newcomers who have never used IRC or lists before. Your help and patience is welcome to provide a helping hand! Thanks to all mentors who have already registered & provided tasks! You have not become a mentor yet? Please consider it! For the full info, please check out https://www.mediawiki.org/wiki/Google_Code-in/Mentors and ask if something is unclear. Thank you again for giving young contributors the opportunity to learn about and work on all aspects of Free & Open Source Software projects. Now bring your tasks! :) Cheers, andre [1] https://lists.wikimedia.org/pipermail/wikitech-l/2018-September/090799.html -- -- Andre Klapper | Bugwrangler / Developer Advocate https://blogs.gnome.org/aklapper/

1 0

Wednesday: Technical Advice IRC Meeting
by Michael Schönitzer 23 Oct '18

23 Oct '18

Reminder: Technical Advice IRC meeting again **Wednesday 3-4 pm UTC** on #wikimedia-tech. Question can be asked in English & German. The Technical Advice IRC Meeting is a weekly support event for volunteer developers. Every Wednesday, two full-time developers are available to help you with all your questions about Mediawiki, gadgets, tools and more! 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 Hope to see you there! Michi (for the Technical Advice IRC Meeting crew) -- 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

Re: [Wikitech-l] [Wikimedia-l] Proposal regarding norms for meeting/deadline announcements
by Pine W 21 Oct '18

21 Oct '18

Hi Lodewijk, I want to encourage people to feel comfortable with posting in-scope and civil emails to WMF mailing lists, but my personal opinion is that the number of reminders is sometimes excessive and the related costs are non-trivial. My view is that excessive reminders about meetings have recently been especially afflicting Wikitech-l, but have also taken place on Wikimedia-l periodically. If we multiply the quantity of seconds that the average person spends clicking or scanning through a reminder email by (1) the number of recipients and (2) the average hourly value of recipients' time, I don't know what the total costs (in money and time) would be but I think that they would be non-trivial. I think that I'm being reasonable in requesting that people make announcements about most one-time meetings 14 days in advance. However, I seem to be a minority of one. And speaking of time management, my guess is that there are hundreds or thousands of other busy people on these mailing lists who might not appreciate my continuing to press this subject, so I'm moving on. Pine ( https://meta.wikimedia.org/wiki/User:Pine ) On Sun, Oct 21, 2018 at 11:34 PM effe iets anders <effeietsanders(a)gmail.com> wrote: > Hi Pine, > > I would also suggest not to get overly bureaucratic with this :) If the > public meeting you refer to requires a large attendance, the 14 days makes > sense for example - but I cannot recall many meetings of that style. > Rather, most meetings are either scheduled taking the availability of > participants in mind, or it is to get input (where it is more important to > have a bunch of people show up, than to have everyone participate). > > Whether more than one reminder is excessive, is imho quite subjective. I > appreciate most reminders, especially if they stick to the same thread. > > On a side note: are there any weekly meetings being announced on this list? > Again, it highly depends on the topic, and whether the reminder may also > contain more information. > > My point? Don't worry about it so much :) Be flexible with this, and go > with the flow. People can figure this out quite well if they use their > common sense without added bureaucracy. > > Lodewijk > >

1 0

Discovery Weekly Update for the week starting 2018-10-15
by Chris Koerner 21 Oct '18

21 Oct '18

This is the weekly update from the Search Platform team for the week starting 2018-10-15. As always, feedback and questions welcome. == Discussions == === Search === * Trey completed his analysis of the Nori language analyzer for Korean. [0] With appropriate customizations, it should improve search on Korean-language wikis, though we won't be able to use it until we upgrade to Elasticsearch 6.4.2. Thanks to Baha and Revi for their help reviewing the output of the language analyzer. [1] * Mathew and Gehel worked on reconfigure=ing Icinga alert for elasticsearch_shard_size to reduce false positive alerts [2], as well as working on refactoring to 'use_git_deploy' in wdqs puppet module to cater for scap3 and autodeployment modes [3] * Erik worked on repairing some search satisfaction browser tests that were no longer automagically running [4] === WIkidata Query Service === * Query Lexemes are now in production for the Wikidata Query Service that entailed a large amount of work and dedication from Stas [5] * Mathew and Gehel created an auto-deployment test server for WDQS [6] == Did you know? == * The writing system for Korean, called Hangeul or Hangul, [7] consists of 24 characters (14 consonants and 10 vowels), which can be combined into 11,172 modern syllable blocks. Each of the modern syllable blocks has its own Unicode character, while obsolete syllable blocks can be composed of individual characters (if you have a font that is smart enough to know what to do [8]). Hangeul thus combines the features of an alphabet and a syllabary, and has been called a "syllabic alphabet" and an "alphabetic syllabary". [0] https://www.mediawiki.org/wiki/User:TJones_(WMF)/Notes/Nori_Analyzer_Analys… [1] https://phabricator.wikimedia.org/T178925 [2] https://phabricator.wikimedia.org/T206187 [3] https://phabricator.wikimedia.org/T206597 [4] https://phabricator.wikimedia.org/T206232 [5] https://lists.wikimedia.org/pipermail/wikidata//2018-October/012545.html [6] https://phabricator.wikimedia.org/T197187 [7] https://en.wikipedia.org/wiki/Hangul [8] https://commons.wikimedia.org/wiki/File:Korean_Composition_Example.png ---- 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 Yours, Chris Koerner Community Relations Specialist Wikimedia Foundation

1 0

Re: [Wikitech-l] [Wikimedia-l] Proposal regarding norms for meeting/deadline announcements
by Pine W 20 Oct '18

20 Oct '18

I've heard little support for new norms regarding reminders and announcements of deadlines on Wikimedia-l and Wikitech-l, so I withdraw my proposal. I may revisit this subject in the future. Pine ( https://meta.wikimedia.org/wiki/User:Pine )

1 0

$wgVisualEditorParsoidForwardCookies
by Aran 19 Oct '18

19 Oct '18

Hi, just wondering what the situation is with $wgVisualEditorParsoidForwardCookies these days. The documentation for visual editor says that it's needed if you have a wiki that's not editable by the public. But I've just set it up on such a wiki and editing/saving an article through visual editor works fine without me having set this or allowed anonymous edits by localhost. Is there no longer any need to worry about settings specifically for locked down wikis? Thanks, Aran

2 2

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 2018