Tomorrow we have planned a major upgrade of the Phabricator prod server.
Starting from around 00:00 UTC (after Evening SWAT) we want to switch from
phab1001 to phab1003 as the production server.
This will involve:
- switching from jessie to stretch
- switching from mod_php to php-fpm
- switching from PHP 5 to PHP 7.2
- upgrading apache from 2.4.10 to 2.4.25
We are also hoping it will finally fix the httpd memory leaks we have been
seeing on the current server for a long time and which require periodic
service restarts.
In case we run into any unexpected issue we will simply fall back to
phab1001
and keep running as before.
https://phabricator.wikimedia.org/T221389https://phabricator.wikimedia.org/T182832https://phabricator.wikimedia.org/T190568https://phabricator.wikimedia.org/T151070
Cheers,
Daniel and Mukunda
--
Daniel Zahn <dzahn(a)wikimedia.org>
Operations Engineer
Hi,
apologies for sending meeting notes late. I was at Wikimedia Hackathon in
Prague. For HTML version see
https://www.mediawiki.org/wiki/Scrum_of_scrums/2019-05-15
Željko
--
= 2019-05-15 =
== Callouts ==
* Try the new Wikistats Time Selector -
https://wikistats-canary.wmflabs.org/time-selector/#/all-projects
* SRE DBAs asking Performance about timelines for
https://phabricator.wikimedia.org/T221577
== Audiences ==
=== Contributors ===
==== Community Tech ====
* Blocked by:
* Blocking:
* Updates:
==== Anti-Harassment Tools ====
* Blocked by:
* Blocking:
* Updates:
==== Editing ====
* Blocked by:
* Blocking:
* Updates:
** Improving mobile usability, iterating on improving editing context
workflows
** git #95da826e - Make JSON styling available on mobile by Ed Sanders
** git #ff15a2ba - Fix diffs in non-section-editing mode (task T222489) by
Bartosz Dziewoński
** git #7739b1c7 - Fix switching without changes (task T221981) by Ed
Sanders
==== Growth ====
* Blocked by:
* Blocking:
* Updates:
** Working on Mobile Homepage
==== Language ====
* Blocked by:
* Blocking:
* Updates:
=== Readers ===
==== iOS native app ====
* Blocked by:
* Blocking:
* Updates:
** v6.2.3 released 05/09
*** Send CSFR token on logout - https://phabricator.wikimedia.org/T221856
*** Keyboard editor fix - https://phabricator.wikimedia.org/T221605
** Continuing work on v6.3
*** Talk page MCS endpoint - https://phabricator.wikimedia.org/T221148
*** Talk page native work - https://phabricator.wikimedia.org/T215928
*** Link wizard in Editor - https://phabricator.wikimedia.org/T213979
==== Android native app ====
* Blocked by:
* Blocking:
* Updates:
** Proton/Chromium renderer: Improved timeout handling
https://phabricator.wikimedia.org/T217724
** Ready to roll out changes to logout behavior, pending QA:
https://phabricator.wikimedia.org/T221856
** More navigation improvements and optimizations:
https://phabricator.wikimedia.org/T222056
** Beginning work on adding image caption editing (structured Commons) in
native image gallery: https://phabricator.wikimedia.org/T223128
** Building abstraction layer of page library for clients to use in
/page/mobile-html endpoint
==== Readers Web ====
* Blocked by:
* Blocking:
* Updates:
==== Readers Infrastructure ====
* Blocked by:
* Blocking:
* Updates:
** Commons structured caption edit suggestion work (for Android's Suggested
Edits) is in progress
** MCS/PCS split in progress
** Maps: stack migrated to node 10 successfully
** Proton/Chromium PDF renderer: fixed timeout handling issues
https://phabricator.wikimedia.org/T217724
==== Multimedia ====
* Blocked by:
* Blocking:
* Updates:
** SDoC: preparing to add qualifiers to depicts statements about Files -
hope to release next week
** SDoC: working on adding other types of statements
==== Parsing ====
* Blocked by: None
* Blocking: None
* Updates:
* about 2/3rd of the porting done.
* HTML -> WT: More code ported and merged. Expect to be able to start
testing this code this week.
* WT -> HTML: Porting the parsing pipeline components - the pipeline will
have reduced complexity compared to JS because all work will happen
synchronously.
==== UI Standardization ====
* Blocked by:
* Blocking:
* Updates:
== Technology ==
=== Analytics ===
* Blocked by:
* Blocking:
* Updates:
** Upgrading superset (dashboarding tool for public and private data
sources) this week to 0.32 version
** Cool new functionality on wikistats regarding ability to select time
ranges. You can take a peek here:
https://wikistats-canary.wmflabs.org/time-selector/#/all-projects
** Reconfiguring deployments of EventGate for analytics to be able to
better deploy EventGate main, for mediawiki events.
** Many issues with latest upgrade of kafka-python in eventlogging, we had
to rollback: https://phabricator.wikimedia.org/T222941
=== Cloud Services ===
* Blocked by:
* Blocking:
* Updates:
=== Fundraising Tech ===
* Blocked by:
* Blocking:
* Updates:
** More anti-fraud work
** Fixing issues with card detail entry in main CC processor's new API
** CentralNotice monitoring work
** Thank You email updates
** Looking at CentralNotice brokenness on beta
=== Core Platform ===
* Blocked by:
* Blocking:
* Updates:
** Session storage service: Security review complete, Service checker
support merged, Code review of MW connection to service complete
** RESTBase Split: VE made so it will work with Parsoid:
https://phabricator.wikimedia.org/T222639, Parsoid simplification is
patched and waiting for review and then extensive testing on beta
** Actor Table migration is on read-new everywhere. Write-new is on Beta
Cluster
=== Performance ===
* Blocked by:
** Core Platform: CR for updated LoadBalancer logic, as requested by
DBA/Jaime. – https://gerrit.wikimedia.org/r/#/c/mediawiki/core/+/394430/
* Blocking:
* Updates:
** Various patches refactoring LoadBalancer (avoiding extra connections
when using query groups, logging, read-only logic)
** Working getting meaningful metrics out of the most common use case on
mobile: Google search, go to Wikipedia and don't scroll.
** Unseen-change notification fixes:
*** Fix for old bug with font-bolding logic for pages at Special:Watchlist;
https://gerrit.wikimedia.org/r/509176
*** Fix for client cache for action=history views;
https://gerrit.wikimedia.org/r/#/c/mediawiki/core/+/508965/
** Improvements for page startup performance in QuickSurveys, CirrusSearch,
CentralAuth, MediaViewer. – https://phabricator.wikimedia.org/T219342
** Browser tests were breaking CI, fixed as broke last week.
=== Release Engineering ===
* Blocked by:
**
* Blocking:
**
* Updates:
**
** Train Health
*** Last week: 1.34.0-wmf.4 - https://phabricator.wikimedia.org/T220729
*** This week: 1.34.0-wmf.5 - https://phabricator.wikimedia.org/T220730
*** Next week: 1.34.0-wmf.6 - https://phabricator.wikimedia.org/T220731
=== Research ===
* Blocked by:
* Blocking:
* Updates:
=== Scoring Platform ===
* Blocked by:
* Blocking:
* Updates:
=== Search Platform ===
* Blocked by:
* Blocking:
* Updates:
=== Security ===
* Blocked by:
* Blocking:
* Updates:
=== Services ===
* Blocked by:
* Blocking:
* Updates:
=== Site Reliability Engineering ===
* Blocked by:
** Performance on https://phabricator.wikimedia.org/T221577
* Blocking:
** Performance on
https://gerrit.wikimedia.org/r/#/c/operations/puppet/+/492948/. Known, it's
complicated to test it, it's going to take a while.
* Updates:
** No updates.
== TechComm ==
* Blocked by:
* Blocking:
* Updates:
** Office Hours during Hackathon will provide link for remote video
participation may also join via IRC #wikimedia-office 8:00 PT/15:00
UTC/17:00 CEST on May 17th
== Wikidata ==
* Blocked by:
** "Blocked" might be to big of a word, but we'd appreciate an input from
Security on the ongoing Production Readiness review:
https://phabricator.wikimedia.org/T216419#5178010
* Blocking:
* Updates:
** Working with SRE on deploying SSR service to kubernetes:
https://phabricator.wikimedia.org/T220402
** EntitySchema a.k.a. Shape Expressions to go live soon (planned for the
week of May, 27th)
** Test system for tool builders/users of DB replica for the new table
containing terms of items and properties (to replace existing wb_terms) a
bit delayed, and expect to be available in the week of May, 29th
== German Technical Wishlist ==
* Blocked by:
* Blocking:
* Updates:
== SoS Meeting Bookkeeping ==
* Blocked by:
* Blocking:
* Updates:
Hello,
Over the last couple months we've been working on improving the experience
of looking through the past on Wikistats2. Until now simple questions like
"who were the top editors in June 2010" or "what countries were visiting
Arabic Wikipedia the most in 2004" were difficult to answer because of our
very limited time selection options on the UI.
This week we deployed the *new time range selector* on Wikistats. As
opposed to the old one, it works for both top and time-series metrics. It
can be used to share links to specific periods in any metric of any wiki.
And we've added a toggle button to switch between monthly and daily
granularities. Please check it out, see, for example, edits for Italian
wikipedia in content spaces between December 2014 and April 2019:
https://stats.wikimedia.org/v2/#/it.wikipedia.org/contributing/edits/normal…
As always feedback welcome, handy link to report bugs:
https://phabricator.wikimedia.org/maniphest/task/edit/?title=Wikistats%20Bu…
Thanks,
Nuria
Hi,
I’ve written a post about the codehealth pipeline in Wikimedia CI, which
the code health metrics group has been working on over the last few weeks
and months:
https://phabricator.wikimedia.org/phame/post/view/160/introducing_the_codeh…
Your feedback and contributions are very welcome!
Kosta
--
--
Kosta Harlan (he/him/his)
Sr Software Engineer
Wikimedia Foundation
Hi all!
Today, TechCom will hold its second ask-us-anything office hour - not on IRC,
but at the hackathon in Prague!
If you are not at the hackathon, you can join via Google Meet (no google account
required):
<https://meet.google.com/gqn-wosn-dog>.
The office hour will start at 15:00 UTC (17:00 CEST, 8am PDT).
Ask us what you have always wanted to know, tell us what you have always wanted
to tell us, discuss the topic you have always wanted top discuss.
--
Daniel Kinzler
Principal Software Engineer, Core Platform
Wikimedia Foundation
Reminder: Technical Advice IRC meeting this week **Today 3-4 pm UTC** on
#wikimedia-tech.
Question can be asked in English, Arabic & Spanish!
Today and next week we have the special Topic "Preparing Wikidata Tools for
the wb_terms migration". If you have any tool that might be affected by
this change feel free to join and ask!
Other topics are welcome too.
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
https://wikimedia.de
Unsere Vision ist eine Welt, in der alle Menschen am Wissens der Menschheit
teilhaben, es nutzen und mehren können. Helfen Sie uns dabei!
https://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/029/42207.
I think that the mobile Suggested Edits feature and the related analysis
are interesting. I am forwarding text from that discussion.
Also, I was happy to see the recognition of two new user groups. They are
the WikiClassics User Group and the Wikimédiens du Bénin User Group.
What's making you happy this week? You are welcome to comment in any
language.
Pine
( https://meta.wikimedia.org/wiki/User:Pine )
---------- Forwarded message ---------
From: Charlotte Gauthier
Date: Tue, May 14, 2019, 08:07
Subject: Re: [WikimediaMobile] Stats & data from launch of Suggested Edits
on Wikipedia Android app
Thanks for this great info, Mikhail, and for the work that went into
producing this useful - and beautiful! - report.
We do indeed have plans to experiment with the thresholds to find the
optimum balance point between wide adoption and maintaining contribution
quality, to extend the feature with new microcontribution types, and to
begin intensive testing to find ways to encourage users to explore more of
the feature, and to inspire long-term use. Advertising new contribution
types and re-activation of editors who have previously tried the feature
will be one of the mainstays of our push messaging strategy.
If anyone is interested in our particular plans over the next year, don't
hesitate to get in touch. We've already been having wider discussions with
several teams on how we could possibly work together towards mutual goals.
Cheers,
Charlotte
On Fri, May 10, 2019 at 9:37 PM Mikhail Popov <mpopov(a)wikimedia.org> wrote:
> Hi folks,
>
> I wanted to highlight a few really interesting pieces of data/stats
> regarding the release of the Suggested Edits feature on Wikipedia app for
> Android. These come from the daily report
> <https://analytics.wikimedia.org/datasets/wikipedia-android-app-reports/sugg…>,
> which is also where you'll find a brief description of the feature.
>
> First, at this time 25.3% of editors (whose contributions are being
> tracked since launch of the backend) have unlocked the feature by making
> the 5+ title description edits
> <https://www.mediawiki.org/wiki/Wikimedia_Apps/Short_descriptions>
> currently required to unlock it. (See: unlock stats
> <https://analytics.wikimedia.org/datasets/wikipedia-android-app-reports/sugg…>)
> That's 632 editors out of the 2495 editors who have made at least one title
> description edit since April 5th. We have plans to experiment with this
> threshold and see what happens if we lower the barrier to entry.
>
>
> By the way, we don’t expect all logged-in users to edit or unlock the
> feature (by making the required number of title description edits), as
> there are incentives on the mobile apps to use an account just for reading
> (e.g. reading list syncing
> <https://wikimediafoundation.org/2018/05/25/synced-reading-lists/>).
> However, perhaps we should advertise this ability better (especially to
> logged-in users) and that those title descriptions don’t require any
> knowledge of wikitext.
>
>
> And since the production release, the feature has had a steady stream of
> 20+ users unlocking it per day. What are our users doing with it once they
> unlock it? They’ve been using it! (Sorry if the text in the included graph
> is too small to be legible, it's larger in the report.)
>
> Nearly half of all title description edits made with the Android app each
> day are coming in from editors using the Suggested Edits feature to add &
> translate descriptions. More than half, even, on some days! Furthermore,
> some of those edits are made by users who have previously used the feature.
> Every day we have some editors who are using Suggested Edits for the first
> time, but there are also quite a few who are returning to the Editor Tasks
> screen & contributing more. (See: edit stats
> <https://analytics.wikimedia.org/datasets/wikipedia-android-app-reports/sugg…>
> )
>
> “Okay, so what’s the quality of those 200-400 descriptions being added
> every day?” you might ask. Well, one way we can check that is to check how
> many of those edits are reverted within 48 hours. Turns out, almost none
> of them:
>
> This is especially impressive when compared to the proportion of other
> title description edits that are reverted. (See: revert rate
> <https://analytics.wikimedia.org/datasets/wikipedia-android-app-reports/sugg…>
> )
>
> When the user goes to the Suggested Edits screen and opens a task, they
> begin receiving suggestions of articles to add descriptions to (or
> translate descriptions, if they have unlocked that next tier of Suggested
> Edits). On average, users express interest in editing 30-40% of those
> suggestions. Among the suggestions they tapped to edit, they end up
> actually making an edit around 60% of the time (although the average varies
> from 40% to 70%). (See: interactions
> <https://analytics.wikimedia.org/datasets/wikipedia-android-app-reports/sugg…>
> and other engagement stats
> <https://analytics.wikimedia.org/datasets/wikipedia-android-app-reports/sugg…>
> )
>
> Since the suggested edits are currently completely random, this leaves us
> with a lot of room for improvement by, say, employing machine learning and
> simple recommendation systems to suggest articles without title
> descriptions that are similar to articles the user has added title
> descriptions to previously. (Just a thought.) For example, in my own
> experience with the suggestions I tend to skip articles that I don’t feel
> confident enough to write short descriptions for, which are often articles
> well outside my interests.
>
> We’re still in the first month of the production release, so it’s hard to
> draw conclusions about the longevity of this feature. These early numbers
> are promising, and hopefully the number of editors using this feature
> continues to grow because then those editors might be inspired to edit
> articles too (if they haven’t yet). Of course, if we see people get bored
> over time we might have to consider ways to encourage/inspire long-term
> use. We also have plans to explore ways to recognize users for their
> contributions.
>
> So congratulations to the Android & Reading Infrastructure teams and
> congrats to Rita Ho (now on the Growth team) for an impressive release. We
> all look forward to the addition of image caption translation and seeing
> the impact of the expanded Suggested Edits v2 on Structured Data on Commons.
>
>
> Thanks for reading! :D
>
> Cheers,
> Mikhail
>
> --
> *Mikhail Popov*, Data Analyst (he/him)
> Product Analytics <https://www.mediawiki.org/wiki/Product_Analytics> //
> Audiences <https://www.mediawiki.org/wiki/Wikimedia_Audiences> // Wikimedia
> Foundation <https://wikimediafoundation.org/>
>
> Other info (including PGP): https://people.wikimedia.org/~bearloga/
>
_______________________________________________
Mobile-l mailing list
Mobile-l(a)lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/mobile-l
For historic reasons the mobile site was built using client side templates
using a templating library called Hogan.js. This caused problems with
development as engineers wanting to build client side experiences using
templates would have to use different template languages for desktop and
mobile experiences or ship two both Mustache and Hogan to end users.
We've recently been simplifying and cleaning up the codebase, reducing
technical debt [1] and as part of this effort have switched templates
inside Minerva and MobileFrontend from Hogan to Mustache [2, 3] to bring
them in line with the rest of the platform.
The Mustache library is smaller than Hogan and appears to be better
maintained. It also has a PHP implementation which is used across MediaWiki
inside cores and skins.
Longer term we are reconsidering the use of templates in our part of the
tech stack but if you are developing extensions or skins that operate in an
environment using a separate mobile skin you can safely and are encouraged
to make use of Mustache to share code that needs to run in both PHP and JS.
[1]
https://medium.com/freely-sharing-the-sum-of-all-knowledge/how-we-tackled-t…
[2] https://gerrit.wikimedia.org/r/#/c/506340/
[3] https://phabricator.wikimedia.org/T220620
Hello,
I will be the train conductor toward 1.34.0-wmf5. The planned schedule
for this week is:
Tuesday: branch cut pairing with Lars "liw" Wirzenius. Should be around
noon UTC.
Wednesday: deploy during the American morning window:
19:00–21:00 UTC
12:00–14:00 PDT
21:00–23:00 UTC+2
Thursday: deploy during European window
13:00–15:00 UTC
06:00–08:00 PDT
15:00–17:00 UTC+2
I have updated the deployment calendar:
https://wikitech.wikimedia.org/wiki/Deployments
cheers,
--
Antoine "hashar" Musso