> There's no need to do it manually. Just tell people to run the phpcs
> autofixer before they rebase, and the result should be identical to
> what's already there. And we can have PHPCS run in the other direction
> for backports ( -> array()).
Unfortunately, it's not that simple. If you run phpcbf before you
rebase, you end up with a commit which changes every instance of
array() to , even in lines the developer didn't touch. Then if any
of those phpcbf changes appear close to a recent real change in
master, the context won't match and you'll get a conflict.
A simple one-line change in a file with many array literals and many
intervening changes in master tends to end up with many conflicts on
So I wrote a script to do it in a different way:
This script runs phpcbf on the base, and separately on the head of the
work branch, and then creates a patch based on the difference between
the two. So the patch contains short arrays on both sides. Then the
patch is applied to master to generate the new commit. I tried this on
https://gerrit.wikimedia.org/r/#/c/236508/ and it seemed to work.
-- Tim Starling
The new Developer Relations Weekly Summary can be found at
We have been focusing on
* Goal: Define potential actions to reduce code review queues and waiting
* Travel sponsorship for WikiArabia Tech Meetup 2016 in Amman and Ramallah.
* Provide a reply to Letter to Wikimedia Foundation: Superprotect and Media
* Technical Collaboration's team strategy, annual plan FY2016-17, and
quarterly goals April - June 2016.
Engineering Community Manager @ Wikimedia Foundation
= *2016-03-09* =
== Product ==
=== Community Tech ===
** Waiting for Niklas to get back from vacation to merge patch to add
pageviews tool into translatewiki.net
** Deadlink fixing bot is going well. Just built a logging interface for
Internet Archives to monitor progress: http://tools.wmflabs.org/deadlinks/
** Continuing to collaborate with MusikAnimal on Pageviews tool:
*** New topviews interface: http://tools.wmflabs.org/pageviews/topviews/
=== Discovery ===
==== Discovery Engineering ====
** Security: SVG sanitizer
** Ops: Maps Hardware https://phabricator.wikimedia.org/T125126
** New portal version deployed on beta, up for general deployment soon
** Completion suggester to be deployed on lower-volume wikis on 10th
** Working on Relevance Forge (nee Relevance Labs)
** WDQS GUI now has maps for queries returning coordinates
** Deployed Maps to Wikivoyage - listening to community feedback
** WDQS query caching problem root cause found,
** Discovery data access guidelines published:
=== Editing ===
==== Collaboration ====
** External Store - Continuing work
** No new blockers. Matthias put up an XSD for the Flow dumps.
** Rolling out cross-wiki notifications beta feature to all wikis tomorrow
** There have been some issues with duplicate thank-you notifications (for
edit milestones, e.g. 100th edit), which are being worked on.
** Also working on some Echo bundling i18n issues and enhancements to the
Notifications special page
=== Fundraising Tech ===
* No blockers
* preparing real donor test of backup worldwide credit card processor
* Working out final details of Latin American payment processing expansion
* Steady stream of CiviCRM enhancements for us and upstream
* More experiments in fraud monitoring and blocking
* Investigating firewall rules for PCI scan
* Investigating possibility of using current PHP/MW
* Replaced dying drive in ActiveMQ box, cursed SPOF
=== Reading ===
==== Android ====
** 2.1.142 beta publishing very soon.
** Reading list endpoint needs - depending on timing/approach may need
==== iOS ====
** Need Piwik access for Josh Minor - done.
** iOS v5.0 is schedule to release this Thursday March 10th
** We need to do additional updates to the Apple site association file we
host for further app enhancements (
==== Web ====
** Path forward needed on a references API -
https://phabricator.wikimedia.org/T125329 Invitation to join conversation.
** Hopefully lazy loaded images we will begin rolling out week commencing
14th [Dependency: performance team]
==== Reading Infrastructure ====
* *AuthManager is still coming!* (see last week for details)
* load.php now logs warnings when the session is accessed in wmf.16. See
== Technology ==
=== Analytics ===
** Hadoop issues with encoding have been fixed, querying is totally ok now,
data has been back-filled and has been ready for re-computation since
earlier this week
* '''Blocked''': (none)
** Working on goals for next quarter, currenlty mostly revolving around
transitioning Erik Zachte's work to Wikistats 2.0
** If you're using UDFs in Hive, you need to add their jars explicitly now,
but this gives more flexibility to test changes to UDFs
** Bots following the user agent policy are now detected correctly in our
pageview data pipeline
** data on unique devices estimated by the last access cookie is now
publicly available, but please let us announce it first on analytics-l
before spreading word of its existence (we want to make sure people know
what this is)
** The "-" article should no longer show up in the "top articles" endpoint
of the pageview API, starting with today's data
=== Release Engineering ===
** Are we doing deployments week of Jerusalem Hackathon? [Sync with ops and
** Reminder: code freeze week of 3/21 for codfw fallover. E-mail/tech news
forthcoming as well.
** Notice: Expect an e-mail shortly, but trebuchet is now deprecated for
all new service deployments going forward. New services should use scap3.
=== Research ===
==== Research and Data ====
** None that we know of.
** Stopped the reader survey (at a 1:50 rate) on 2016-03-08. Research
documentations are in
** No major news for the coming week.
=== Security ===
** SVG sanitizer - is this blocking a quarterly goal?
** password hash format updated
** Lots of security patches deployed - releng, release soon (T124940)?
** AuthManger review starting
=== Services ===
** morelike API live - https://phabricator.wikimedia.org/T125983
*** Reading: Android wants 320px thmubs, is the rest of Reading OK with it?
** RB cluster expansion continuing
*** switched to 2.1.13, soon testing of 2.2.5
*** start of Brotli compression in staging imminent
** rate limiting in service-runner
*** RB endpoints - now only logging excesses, soon will start enforcing them
** API: removing some listing endpoints
=== Technical Operations ===
** ORES - moving into a python wheel repo structure
** moved ocg to use a replicated redis
** redis replicated and encrypted on the sessions
** got <40 precise machines now
** Please delete unwanted labs instances
Summary: The time at which a deployment regularly happens may be
different for you due to day light savings. Double check the calendar if
Deployments are effected by DST changes in the US as all items in the
Deployments calendar are in SF-local time, eg the main MediaWiki train
 Don't mind that one item from Antoine for the CI upgrade yesterday
being in UTC :)
----- Forwarded message from Elena Hernandez <ehernandez(a)wikimedia.org> -----
> Date: Tue, 8 Mar 2016 15:51:12 -0800
> From: Elena Hernandez <ehernandez(a)wikimedia.org>
> To: "Staff (All)" <wmfall(a)lists.wikimedia.org>
> Subject: [Wmfall] [Announcement] Get ready to spring forward Sunday, March 13th!
> Hello! This Sunday, March 13th, some Americans are going to experience
> Daylight Saving Time at 2 AM, and the clocks are going to jump forward one
> If DST applies to you, and you have any analog clocks, don't forget to set
> the clock forward before you go to bed on Saturday.
> Your Talent and Culture Team
>  https://en.wikipedia.org/wiki/Daylight_saving_time
>  https://en.wikipedia.org/wiki/Daylight_saving_time_in_the_United_States
> Wmfall mailing list
----- End forwarded message -----
| Greg Grossmeier GPG: B2FA 27B1 F7EB D327 6B8E |
| identi.ca: @greg A18D 1138 8E47 FAC8 1C7D |
I wanted to discuss an old patch that we worked on during adding page
language support(which is indeed a big patch).
We tried to refactor and create a new class for different language
Now the work done in terms of applying the page language support is
happening for a lot of wikis, the dependent patches should be needed soon.
I am not sure about whether and how to proceed with this. Should we rather
not try to refactor it and work on the smaller patches that are dependant
on it? Could someone give suggestions on how to work towards making the
patch better based on Daniel's comments on the patch?
The project page for coordinating online and offline events for
International Women's Day (March 8) and Women's History Month has been
published on Meta at:
The theme of the edit-a-thon this year on the English Wikipedia is Women
in STEM. The theme covers various sub-domains like Women in Tech, STEM
conferences, STEM opportunities and initiatives for women etc.
This year the edit-a-athon would take place during a weekend, March 26-27,
I urge various language editors to add lists of articles to create and
expand as a part of the edit-a-thon:
Thanks and Regards,
Computer Science Engineering
B.Tech Final Year (Senior)
Indian Institute of Technology Roorkee