Hey folks, I'm helping Rebecca Maung (rmaung(a)wikimedia.org) distribute
this request. Her words below:
The Wikimedia Foundation is asking for your feedback in the annual
Community Insights survey. We want to know how well we are supporting
your work on- and off-wiki, and how we can change or improve things in
the future. The opinions you share will directly affect the current
and future work of the Wikimedia Foundation.
If you are a volunteer developer, and have contributed code to any
pieces of MediaWiki, gadgets, or tools, please complete the survey. It
is available in various languages and will take between 15 and 25
minutes to complete.
Follow this link to the survey:
https://wikimedia.qualtrics.com/jfe/form/SV_0pSrrkJAKVRXPpj?Target=dev
If you have seen a similar message elsewhere and have already taken
the Community Insights survey, please do not take it twice.
You can find more information about this survey on the project page
and see how your feedback helps the Wikimedia Foundation support
contributors like you. This survey is hosted by a third-party service
and governed by this privacy statement. Please visit our frequently
asked questions page to find more information about this survey.
If you need additional help, send an email to surveys(a)wikimedia.org.
Thank you!
//Johan Jönsson
--
Hi,
for HTML version see
https://www.mediawiki.org/wiki/Scrum_of_scrums/2019-09-11
Željko
--
= 2019-09-11 =
== Callouts ==
* SRE says: Possible networking issues at times, redirect bug reports to
Numerous people reporting issues saving edits and viewing previews/diffs
https://phabricator.wikimedia.org/T232491 as the canonical bug for those
* Release Engineering
** Train blocked (Core Platform) - T232613 LBFactoryMulti.php PHP Notice:
Undefined index:
** REMINDER: We're at 1.34.0-wmf.22 this week. The last branch for this
release will be wmf.25 on 30 September. Teams who want to ship things for
MW 1.34 should land them now. (If you do not mark code as deprecated in the
next few weeks, you have to maintain it for 9 months.)
== Product ==
=== Contributors ===
==== Editing ====
* Updates:
** Talk Pages: Team is conducting research this week to identify technical
constraints for features we will likely need to build, see what can be
learned from existing gadgets
** ve.ui.MWEditModeTool: Fix showing active editor (task T232359) by
Bartosz Dziewoński
** Mobile surfaceReady: Account for selection changing in listeners (task
T232136)
** Fix HTML blacklist inheritance (task T150418)
** MWLinkAnnotationInspector: track edits to the label field (task T229841)
==== Growth ====
* Updates:
** Set correct merge strategy for help panel links (task T231935)
** Help panel: Right-align the continue button (task T224256)
** [LiquidThreads] Another speculative fix for when topmostThread title is
not found (task T61791)
=== Readers ===
==== iOS native app ====
* Updates:
** Development on 6.4 release
https://phabricator.wikimedia.org/tag/ios-app-v6.4-seamonkey-on-a-hoverboar…
*** iOS 13 & iPadOS updates
*** New loading screen for dark mode
*** Bug fixes
** Research on 6.5 release
*** History & diffs API discussions with CorePlatform
https://phabricator.wikimedia.org/tag/ios-app-v6.5/
*** Diff engine PR is up https://phabricator.wikimedia.org/T228794
==== Android native app ====
* Updates:
** Gearing up for a minor release. We have pushed a new version to beta:
https://play.google.com/apps/publish/?account=6169333749249604352#AppDashbo…
** Currently working on Suggested Edits, V3 on N board:
https://phabricator.wikimedia.org/project/view/4123/
==== Product Infrastructure ====
* Updates:
** Research week — full team researching technical requirements for
upcoming projects
** Requested DBA & security readiness reviews for MachineVision
==== Structured Data ====
* Blocking:
** Search Platform - Core Platform (or Structured Data?): RecentChange
support for SDC: https://phabricator.wikimedia.org/T230862
* Updates:
** UBNs to do with entity ids and page ids clashing resolved
** mostly working on Machine Vision project, new input types for
statements, and finishing off campaigns work
==== Parsing ====
* Blocked by:
** https://phabricator.wikimedia.org/T232538 blocked on Core Platform Team
which blocks deployment to beta cluster which blocks CPT's RESTBase <->
Parsoid/PHP integration testing
* Updates:
** Parsoid/PHP: Ongoing round trip testing and bug fixes
=== UI Standardization ===
* Updates:
** OOUI v0.34.0 and 0.34.1 released,
https://phabricator.wikimedia.org/diffusion/GOJU/browse/master/History.md;v…
** Unifying messages in MW core, shared.css and MF
** Further development on “Components” section for Design Style Guide
== Technology ==
=== Analytics ===
* Blocking:
** Search Platform - Point discovery dashboards at SearchSatisfaction
eventlogging table: https://phabricator.wikimedia.org/T229882
=== Fundraising Tech ===
* Updates:
** CiviCRM
*** Bugfixes following version upgrade
*** Pulling more data from bulk mailing house into Civi
https://phabricator.wikimedia.org/T230509
** Payments-wiki
*** Deployed a bunch of form updates and variants
*** Better messaging for donors who cancel from hosted card entry forms:
https://phabricator.wikimedia.org/T224063
** CentralNotice
*** Fix to hang on message cache rebuild is going out on train this week:
https://phabricator.wikimedia.org/T231703
*** Fixed another translatable message bug in the process:
https://phabricator.wikimedia.org/T72939
*** About ready to merge campaign fallback:
https://phabricator.wikimedia.org/T226344
=== Core Platform ===
* Blocking:
** Wikidata: (not critical blocker yet) We would appreciate review from
core/frontend on https://phabricator.wikimedia.org/T208601 /
https://gerrit.wikimedia.org/r/535206
** Search Platform - Core Platform (or Structured Data?): RecentChange
support for SDC: https://phabricator.wikimedia.org/T230862
** Performance: CR of RDBMS change
https://gerrit.wikimedia.org/r/#/c/mediawiki/core/+/394430/
** Release Engineering - train blocked - T232613 LBFactoryMulti.php PHP
Notice: Undefined index:
** Parsing - https://phabricator.wikimedia.org/T232538 blocked on Core
Platform Team which blocks deployment to beta cluster which blocks CPT's
RESTBase <-> Parsoid/PHP integration testing
* Updates:
** Core REST API progress for iOS
** API tests
** OAuth 2.0 development
** Documentation for REST API extensions
=== Engineering Productivity ===
==== Performance ====
* Blocked by:
** Core Platform: CR of RDBMS change
https://gerrit.wikimedia.org/r/#/c/mediawiki/core/+/394430/
* Updates:
** Speaking at Mozilla's Automationeers Assemble tomorrow:
https://m.wiki.mozilla.org/Automationeers_Assemble
** Ongoing issue with our WebPageTest instance affecting Chrome Emulated
Mobile tests, slower by 1s since September 4
** A performance regression on enwiki identified as affecting only Firefox
in synthetic testing turned out to be a significant DOM element increase
due to a Cite template update (migration errors) that happened on September
3
==== Release Engineering ====
* Blocked by:
** Core Platform - train blocked - T232613 LBFactoryMulti.php PHP Notice:
Undefined index:
* Updates:
** The phabricator "Report Error Code" form (
https://phabricator.wikimedia.org/maniphest/task/edit/form/46/ ) has been
updated with separate fields for the stack trace and error code/request id.
** REMINDER: We're at 1.34.0-wmf.22 this week. The last branch for this
release will be wmf.25 on 30 September. Teams who want to ship things for
MW 1.34 should land them now. https://phabricator.wikimedia.org/T232026 (If
you do not mark code as deprecated in the next few weeks, you have to
maintain it for 9 months.)
** Train Health
*** Last week: 1.34.0-wmf.21 - https://phabricator.wikimedia.org/T220746
*** This week: 1.34.0-wmf.22 - https://phabricator.wikimedia.org/T220747
**** Core Platform - T232613 LBFactoryMulti.php PHP Notice: Undefined index:
*** Next week: 1.34.0-wmf.23 - https://phabricator.wikimedia.org/T220748
=== Scoring Platform ===
* Updates:
** ORES uwsgi issue --> Tons of Icinga noise
https://phabricator.wikimedia.org/T231222
** Some people still using wmflabs rather than prod
https://phabricator.wikimedia.org/T231776
** Fixes "Jade" role in MW Vagrant https://phabricator.wikimedia.org/T231497
** Reduced statsd metrics generation for ORES
https://phabricator.wikimedia.org/T232164
** Still waiting for invite to Design Review meetings (Blocked on Design)
** Making progress on MW API for Jade
https://phabricator.wikimedia.org/T199834
=== Search Platform ===
* Blocked by:
** Core Platform (or Structured Data?): RecentChange support for SDC:
https://phabricator.wikimedia.org/T230862
** Site Reliability Engineering: dumpRDF for MediaInfo entities loads each
page individually: https://phabricator.wikimedia.org/T222497
** Analytics: https://phabricator.wikimedia.org/T229882
* Updates:
** Restored display of commons image in the sister search sidebar for all
wikis except enwiki: https://phabricator.wikimedia.org/T232032
=== Security ===
* Updates:
** Team survey is out and will close end of week
** Data Map requests for updating / completion will go out to teams on
Friday
** No Security Review updates this week
=== Site Reliability Engineering ===
* Blocking:
** Search Platform on dumpRDF for MediaInfo entities loads each page
individually: https://phabricator.wikimedia.org/T222497. No one working on
it yet, we will post an update on task as soon as it happens
* Updates:
** Possible networking issues at times, redirect bug reports to Numerous
people reporting issues saving edits and viewing previews/diffs
https://phabricator.wikimedia.org/T232491 as the canonical bug for those
** wikifeeds is ready to be deployed to kubernetes
** PHP7 ration bumped to 33%
** Resuming work on migrating restrouter
== Wikimedia DE ==
=== Wikidata ===
* Blocked by:
** Core Platform? (not critical blocker yet) We would appreciate review
from core/frontend on https://phabricator.wikimedia.org/T208601 /
https://gerrit.wikimedia.org/r/535206
Sorry for cross-posting!
Reminder: Technical Advice IRC meeting this week **Wednesday 3-4 pm UTC**
on #wikimedia-tech.
Questions can be asked in English, Persian, Spanish!
The Technical Advice IRC Meeting (TAIM) 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!
--
Raz Shuty
Engineering Manager
Wikimedia Deutschland e. V. | Tempelhofer Ufer 23-24 | 10963 Berlin
Phone: +49 (0)30 219 158 26-0
https://wikimedia.de
Imagine a world, in which every single human being can freely share in the
sum of all knowledge. That‘s our commitment.
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.
(Note: This is only an early heads-up, to be prepared. Google Code-in
has NOT been announced yet, but last year, GCI mentors asked for more
time in advance to identify tasks to mentor. Here you are. :)
* You have small, self-contained bugs you'd like to see fixed?
* Your documentation needs specific improvements?
* Your user interface has some smaller design issues?
* Your Outreachy/Summer of Code project welcomes small tweaks?
* You'd enjoy helping someone port your template to Lua?
* Your gadget code uses some deprecated API calls?
* You have tasks in mind that welcome some research?
Google Code-in (GCI) is an annual contest for 13-17 year old students.
GCI 2019 has not yet been announced but usually takes place from late
October to December. It is not only about coding: We also need tasks
about design, docs, outreach/research, QA.
Read https://www.mediawiki.org/wiki/Google_Code-in/Mentors , add
your name to the mentors table, and start tagging tasks in Wikimedia
Phabricator by adding the #gci-2019 project tag.
We will need MANY mentors and MANY tasks, otherwise we cannot make it.
Last year, 199 students successfully worked on 765 tasks supported by
39 mentors. For some achievements from the last round, see
https://wikimediafoundation.org/news/2019/02/20/partnerships-make-it-possib…
Note that "beginner tasks" (e.g. "Set up Vagrant") and generic
tasks are very welcome (like "Choose and replace 2 uses of
Linker::link() from the list in T223010" style).
We also have more than 400 unassigned open #good-first-bug tasks:
https://phabricator.wikimedia.org/maniphest/query/3YnDUWYJfXSo/#R
Can and would you mentor some of these tasks in your area?
Please take a moment to find / update [Phabricator etc.] tasks in your
project(s) which would take an experienced contributor 2-3 hours. Read
https://www.mediawiki.org/wiki/Google_Code-in/Mentors
, ask if you have any questions, and add your name to
https://www.mediawiki.org/wiki/Google_Code-in/2019#List_of_Wikimedia_mentors
Thanks (as we will not be able to run this without your help),
andre
--
Andre Klapper (he/him) | Bugwrangler / Developer Advocate
https://blogs.gnome.org/aklapper/
Hello,
The current primary master for m1 (db1063), which is mostly for internal
services + etherpad isn't in a great healthy status: it is an old host,
which needs to be decommissioned and which is having disks failing pretty
much every week (plus disks on predictive failure).
We have decided to fail it over one of the newer hosts, db1135:
https://phabricator.wikimedia.org/T231403
We have scheduled this switchover for: Tuesday 10th September at 16:00 UTC
This failover should be rather quick and would only take a few seconds
(while we re-load the haproxy) - during those few seconds, the following
services will be on read-only:
bacula
etherpadlite
librenms
puppet
racktables
rt
Communication will happen at #wikimedia-operations
If you are around at that time and want to help with the monitoring, please
join us!
Thanks
Hello,
When adding an extension requirement in extension.json, CI would most
probably complain since it does not clone the extension. It has to be
added to the CI configuration:
https://gerrit.wikimedia.org/r/integration/config.git
edit zuul/parameters_functions.py
Add the requirement to the 'dependencies' mapping, then send for review.
Unfortunately one of the CI maintainers would have to approve and deploy it.
As a twist, I wrote a few bits that should make it possible for CI to
automatically process and clone the requirements and thus let us phase
out the central config. But that takes a bit of time to accomplish it
properly.
The long story:
MediaWiki extension registration lets one define a requirement upon
other extension/skins. If one writes an extension that extend
VisualEditor, most probably VisualEditor is required, the extension.json
would thus have:
{
"requires": {
"extensions": {
"VisualEditor": "*"
}
}
}
Due to a bug, CI was no more failing when a requirement was not
fulfilled. In fact the extension would not even be enabled when running
maintenance/install.php --with-extensions
That has been fixed via:
https://gerrit.wikimedia.org/r/#/c/mediawiki/core/+/533239/
From now on, on master branch, CI would fail when a requirement is
missing. Unfortunately, CI does not magically clone the requirements
yet, so you would have to also add them to the CI config (see above).
[requirements]
https://www.mediawiki.org/wiki/Manual:Extension_registration#Requirements_(…
--
Antoine "hashar" Musso
Hi,
Can someone help me with an SQL snippet for reverted changes? I know some
tools have this metric but I am not able to isolate the relevant query in
their code.
Thanks,
Strainu
There are several papers about how to stop DDoS by using cryptographic
puzzles.[1] The core idea is to give the abuser some algorithmic work he
has to solve, thereby forcing him to waste processing power, and then to
slow him down to a manageable level.[2] That only work if you are the
target, and not some intermediary are targeted.
Could it be a solution for the WMF servers?
[1] http://d-scholarship.pitt.edu/24944/1/mehmud_abliz_dissertation.pdf
(just a random pick)
[2]
https://searchsecurity.techtarget.com/answer/TLS-protocol-Can-a-client-puzz…
(about
TLS, but can also be done at the application level)