Friends,
This is a Scoring Platform technical update for the last couple of weeks of
work.
*Deployments*
We completed a biweekly deployment today, adding models for quite a few new
wikis. Congratulations, and a big thank you to everyone who helped us
coordinate and gather the data to accomplish this!
Epic: https://phabricator.wikimedia.org/T170485
*New models*
- Albanian Wikipedia: new models for reverted, damaging, and goodfaith.
- Bengali Wikipedia: new model for reverted.
- Greek Wikipedia: new model for reverted.
- Tamil Wikipedia: new model for reverted.
- Romanian Wikipedia: new models for damaging and goodfaith.
- Turkish Wikipedia: fixes to the article quality model ("wp10") (
https://phabricator.wikimedia.org/T170838 )
*Service updates*
- Switched precaching from RCStream (deprecated) to new EventStreams,
https://phabricator.wikimedia.org/T166046
- Better error handling for bad API params,
https://phabricator.wikimedia.org/T168920
- Patched a DoS caused by a combination of bad regex and inadequate
timeout code. Incident:
https://wikitech.wikimedia.org/wiki/Incident_documentation/20170623-ORES
Note that Albanian and Romanian Wikipedias will soon support ORES in their
Recent Changes feeds. Subscribe to
https://phabricator.wikimedia.org/T170723 for updates.
Regards,
Adam
*https://www.mediawiki.org/wiki/Scrum_of_scrums/2017-07-19
<https://www.mediawiki.org/wiki/Scrum_of_scrums/2017-07-19>*
*= 2017-07-19 =*
*contact: https://www.mediawiki.org/wiki/Wikimedia_Engineering
== Callouts ==
* FR-tech requesting help with Translate extension:
https://phabricator.wikimedia.org/T170968
* Skilled in RewriteRules? https://gerrit.wikimedia.org/r/360891 and
https://gerrit.wikimedia.org/r/357985 need review.
* Help cleaning up /srv/deployment - if you have software on the deployment
server that is no longer deployed please add it here:
https://phabricator.wikimedia.org/T170881
* Need some ops help/review with WDQS spam problem:
https://phabricator.wikimedia.org/T170860
* Node.js upgrade is on the way, please test your service if you didn't
yet: https://phabricator.wikimedia.org/T170548
** Reading Web: Input would appreciated if you are familiar with
Special:ShortPages (https://phabricator.wikimedia.org/T170687#3444846)
== Audiences ==
=== Readers ===
==== iOS native app ====
* Blocked by: none
* Blocking: none
* Updates: 5.5 (with Places & feed design updates) is (our first?)
sustained 5-star rated release, Continuing work on 5.6 (dark mode, on this
day feed content) https://phabricator.wikimedia.org/project/view/2701/
==== Android native app ====
* Blocked by: n/a
* Blocking: n/a
* Updates:
** Cookie release work is all in QA/design review (
https://phabricator.wikimedia.org/project/view/2763/)
** Offline compilations work is well underway (
https://phabricator.wikimedia.org/project/view/2833/)
** Stephen working on cross-platform CSS/JS consolidation, lazy loaded
images in articles, dark mode UI
** engineer interviews in progress; resumes are coming in for the PM
position
==== Reading Web ====
* Blocked by:
RelEng: We have PHPUnit tests that are not being run
https://phabricator.wikimedia.org/T170880 - would appreciate some help
debugging the issue
* Blocking:
* Updates:
** Working on print styles for desktop.
** Input would appreciated if you are familiar with Special:ShortPages (
https://phabricator.wikimedia.org/T170687#3444846)
**Planning to roll out Page previews to all wikis except German and English.
**Updating Vector's print styles
** Planning new HTML summary endpoint (
https://phabricator.wikimedia.org/T113094 )
==== Reading Infrastructure ====
* Blocked by: N/A
* Blocking: N/A
* Updates:
** working on Reading Lists
** TemplateStyles deployed to wikitech, mediawiki.org
** Measured payload differences of output between Parsoid and various
transformations in MCS. https://phabricator.wikimedia.org/T164033
** Looking into structured reference list content.
==== Multimedia ====
* Blocked by: (maybe) RelEng re: issues with Beta thumbnailing of 3D files
(sent Tyler an e-mail) - https://phabricator.wikimedia.org/T170444
* Blocking: N/A
* Updates: Design work on 3D extension is nearly done for our MVP release.
==== Discovery ====
* Blocked by: N/A
* Blocking: N/A
* Updates:
** Maps team out this week
** Finishing up AB test on Special:Search page
=== Community Tech ===
* Blocked by:
* Blocking:
* Updates:
** Still working on section IDs, LoginNotify and CodeMirror
=== Contributors ===
==== Editing ====
* Blocked by:
* Blocking:
* Updates:
==== Parsing ====
* Updates:
** https://www.mediawiki.org/wiki/Parsing/Notes/Section_Wrapping documents
constraints around adding <section> wrappers in Parsoid's output ( we
aren't going to do this for PHP parser output because it isn't DOM based ).
This will eliminate the need for MobileContentService to do their own
thing. However, our proposed solution behaves differently from MCS'
currently deployed version in some edge cases (<div> wrapping multiple
sections or partial sections, for ex) -- MCS folks are already aware of
this. But, if anyone else has opinions / thoughts on this, please leave
them on the talk page. https://phabricator.wikimedia.org/T114072 is the
associated phab task
==== Global Collaboration ====
===== Language =====
* Blocked by:
* Blocking:
** https://phabricator.wikimedia.org/T170591 Blocking FT. Kartik looking
at it, but more eyes are welcome!
* Updates:
** Adaption logic moving to cxserver.
** OOjs UI work for ContentTranslation continue.
===== Collaboration =====
* Updates
** RCFilters
*** RCFilters UI: Add 'remove' and 'restore defaults' to filter list
*** RCFilters UI: Read default states of filters
*** rcfilters: Remove implemented filters from list of links
*** Bug fixes
==== Contributors Design ====
* Blocked by:
* Blocking:
* Updates:
==== UI Standardization ====
* Updates:
** WikimediaUI Style Guide:
*** Added WikimediaUI Style Guide own imagery to repo's resources directory
and make style guide use HiDPI images instead of 1x PNGs
** OOjs UI: no release this week, changes/ongoing since v0.22.3
*** (continued from last week): Further aligning OOjs UI with WikimediaUI
Base
*** Connecting documentation on mediawiki.org with OOjs UI demo
*** Reverting "FieldsetLayout: Temporarily remove use of `<legend>` due to
Chrome 55... – accessibility improvement (James Forrester)
*** WikimediaUI theme: Use icon instead of indicator in
Tag-/CapsuleItemWidget
** MW core:
*** Simplify print style rules and tackle improvements desktop print
== Technology ==
=== Analytics ===
* Blocked by:
* Blocking:
* Updates:
- Running eventlogging purging as of now, still deleting data from
2014/early 2015.
- Had an outage on eventlogging after consuming data from eventbus
events are backfilled now:
-
https://wikitech.wikimedia.org/wiki/Incident_documentation/20170711-EventLo…
-
https://wikitech.wikimedia.org/wiki/Analytics/Systems/EventLogging#Changes_…
- DE data analyst leaked password for db, that is corrected and changed
now
- Working on our first deployment of wikistats 2.0, still no backend,
just frontend and pageview metrics against AQS.
- Added detailed desktop browser stats for all wikimedia sites.
- Numbers very stable for a while with Chrome on the lead with 44%
https://analytics.wikimedia.org/dashboards/browsers/#desktop-site-by-browser
- Waiting for final vetting of project-family unique devices data from
data analysts (unique devices on *.wikipedia.org)
=== Cloud Services ===
* Blocked by:
* Blocking:
* Updates:
=== Fundraising Tech ===
* Blocked by:
** Translate extension is writing huge numbers of db rows on banner save:
https://phabricator.wikimedia.org/T170968
* Blocking:
* Updates:
** Doing weekly one hour tests of Big English countries, getting some good
data (and plenty of donations!)
** CentralNotice
*** Met with WMDE fundraising to get them involved with CentralNotice coding
*** They reported timeouts saving banners:
https://phabricator.wikimedia.org/T170591
*** See root cause in 'blocked by' and callouts
** CiviCRM:
*** more work on third-party mailer integration
**** https://phabricator.wikimedia.org/T161760,
https://phabricator.wikimedia.org/T161758,
https://phabricator.wikimedia.org/T170900
*** more location import fixes: https://phabricator.wikimedia.org/T169025
** DonationInterface and SmashPig payments library
*** Fixing last couple bugs in new PayPal integration
**** https://phabricator.wikimedia.org/T167923 and
https://phabricator.wikimedia.org/T170478
*** making steady progress with new API for main credit card processor
(Ingenico):
**** https://phabricator.wikimedia.org/T163946 and
https://phabricator.wikimedia.org/T163948
=== MediaWiki Platform ===
* Blocked by:
* Blocking:
* Updates:
=== Performance ===
* Blocked by:
* Blocking:
* Updates:
=== Release Engineering ===
* Blocked by: None
* Blocking: None?
* Updates:
** Train back on track, wmf.9 rolled forward Monday thanks to ebernhardson
and jdlrobson for the heroic debugging and patch making respectively
** An attempt at [https://phabricator.wikimedia.org/T170881 cleanup of
/srv/deployment] halp please
=== Research ===
* Blocked by:
* Blocking:
* Updates:
=== Scoring Platform ===
* Blocked by:
* Blocking:
** Scheduling a meeting with Collaboration, hopefully to finalize details
of splitting ownership of the Extension:ORES repo, and cleaning up
preferences for the legacy and noscript ORES UI.
* Updates:
** Deployed a bevy of new models, https://phabricator.wikimedia.org/T170485,
supporting Albanian, Bengali, Greek, Romanian, Tamil, and Turkish.
** Noticed that a wdqs thing "recommendation api" is breaking puppet on
beta labs. https://phabricator.wikimedia.org/T171075
=== Search Platform ===
* Blocked by: none
* Blocking: none
* Updates:
* Continuing work on ML-assisted ranking
* Japanese analyzer research finished, not deploying for now (
https://phabricator.wikimedia.org/T166731)
* "Explore similar" A/B test running
* Working on interleaved search results A/B test
* Ops help needed for WDQS spam problem (
https://phabricator.wikimedia.org/T170860 )
=== Security ===
* Blocked by: Comm. with Legal on several issues
* Blocking: Legal, and several other teams who are waiting for security
reviews
* Updates:
** Security reviews:
*** vue.js
*** OIT apps
* Bawolff will be mostly unavailable until August 1
=== Services ===
* Blocked by: none
* Blocking: none
* Updates:
** Working on new storage model on RESTBase
** Node.js 6.11.1 upgrade is coming
*** https://phabricator.wikimedia.org/T170548
=== Technical Operations ===
* Blocked by: none
* Blocking: none?
* Updates:
** Work on goals ongoing
https://www.mediawiki.org/wiki/Wikimedia_Technology/Goals/2017-18_Q1#Techni…
** Switch upgrades in codfw almost finished
== Wikidata ==
* Blocked on reviews of two patches that introduce RewriteRules:
** https://gerrit.wikimedia.org/r/360891
** https://gerrit.wikimedia.org/r/357985
* Reworked the query service UI: https://phabricator.wikimedia.org/T170279
* Units in quantities are now properly usage-tracked:
https://phabricator.wikimedia.org/T170167
* Spend time to think about constraint reports on deprecated statements:
https://phabricator.wikimedia.org/T167653
* Final touches on Lexeme demo for Wikimania:
https://phabricator.wikimedia.org/T165588
== German Technical Wishlist ==
* Collecting input and assigning priorities to the top 10 wishes from the
recent poll.
Forwarding.
Pine
---------- Forwarded message ----------
From: Aaron Halfaker <ahalfaker(a)wikimedia.org>
Date: Wed, Jul 19, 2017 at 11:42 AM
Subject: [AI] Announcement of the Scoring Platform team
To: Wikimedia Mailing List <wikimedia-l(a)lists.wikimedia.org>, Application
of Artificial Intelligence and other advanced computing strategies to
Wikimedia Projects <ai(a)lists.wikimedia.org>
Hey folks,
This is a little overdue, but I wanted to work with comms to craft a blog
post that would help us do a bit of outreach around the announcement of the
team. That just went live.
See https://blog.wikimedia.org/2017/07/19/scoring-platform-team/
-Aaron
Principal research scientist
Lead of the Scoring Platform team
Wikimedia Foundation
_______________________________________________
AI mailing list
AI(a)lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/ai
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Hello everyone.
This is a security announcement for the CentralAuth
extension. There were 2 issues discovered in the
extension, and all users are strongly encouraged to
upgrade.
Issue 1: XSS in Special:GlobalGroupPermissions
Due to a lack of escaping in the
Special:GlobalGroupPermissions page, an attacker
would be able to inject arbitrary javascript into
the page, potentially leading to the take over
of other user's accounts.
The fix for this issue was accidentally included
in another patch - fadb367ad (February 1, 2017).
If you are using the master branch of the
extension, you need to ensure that your
copy is newer than February 1.
All versions of the REL1_29 branch have this
fix.
For REL1_28 please ensure that you have the
commit 1e9d612 (July 19, 2017)
For REL1_27 please ensure that you have the
commit aa3401503 (July 19, 2017)
This issue was discovered by Grunny.
For more information, please see:
https://phabricator.wikimedia.org/T134863
Issue 2: Open redirect in AutoLogin
An attacker can cause a user who is
globally logged in, but not logged in
on a specific wiki, to be redirected
to an arbitrary interwiki link, even
for interwiki prefixes without the
iw_local bit set.
To get the fix for this issue, please
ensure that your copy of CentralAuth
is from at least July 19, 2017
Associated git commits:
* Master: 6a84c0cb4e31
* REL1_29: 2a220af1e4ac
* REL1_28: 4acfa2865a05
(Now requires at least 1.28.1)
* REL1_27: 4db90e20808f
(Now requires at least 1.27.2)
Associated bug:
https://phabricator.wikimedia.org/T134931
Sincerely,
Brian Wolff
Wikimedia Security Team
-----BEGIN PGP SIGNATURE-----
iQIcBAEBCAAGBQJZbudjAAoJEDYflDsVwI3Ux1AQAJXV2pcQicZzApo+WUbqD5aS
5GSEmNlLsS5E16r/tYU2Fhih2qxPJ/iNYCjQI0xZPDWPmi3r8aErEwMs4XS9bfjW
EG/uUsS0DPu9U7BJ+x2h3vOmUFyhyIWHhHMV+6OIAXWyb5Pzm0+oiE8Cw7wx7NId
ZsgTom0T0abXd597mzUomQbGLUPl4gWBbZYqclP9VS8S1xX6ci+UAo0D2hTe9bPN
r0K2C7cmYY0Ltpr2dy9lP3TeEOhsYK3/KQVLZkpTI6h2WZKZSnQKPJzF/qPJEdP8
Zni5zE7heMo+mgXBb6Vcl/+5CDgdxndbdAz9qrgRM51AbF/IfjQAahrs3uc+C7Le
2/zTNkUVxgCyWRrsDVjU8HJHeB/d26fZDNr8cGkXP6BZuTs3bKGG5gCZIVIRmoO8
cMJx0y0vCudDelIFXyE0NssKbKjyUeRZ9djw/kpIQ29CpR211lZuy5tPWB5Tr7/s
9CiwJUPyOjLV6N1icGC3pZfzwxPseJXSY+/J/PwPfwqn/z3IdTiKW9+NfFvp1Tvb
JIPt3ZUN/WbySdGlkTw0fNUo+ILSceDw7cdmRcm08UIV8Ce/xmLhHKF9uinXbAOU
Me0yjKLzHDIZBCCYdZJNPUzRZY+n63Sq0+22Ub4Tv348Pk8kIqtyY+gZuM6l7oMu
SW9yOQQSc5TxNLrPsCUP
=b2xq
-----END PGP SIGNATURE-----
Hello,
I've been looking at this parameter in skin.json and its implementation
seems a bit weird to me (or I might just not understand it properly). My
original goal was to flat out disable OOJS-UI since the default themes
(WikimediaUI and Apex) do not really look good on dark skins, and even
on light skins are only implemented on half the pages (and don't look at
extensions that are not deployed on Wikipedia). Since just flat out
disabling doesn't seem to be possible as special pages enable it
directly, my next goal was to create a custom class for a OOJS-UI theme
that basically doesn't apply any styles. to do that I added
"SkinOOUIThemes": {
"liquiflow": "Blank"
}
to my skins skin.json and loaded a class
<?php
namespace OOUI;
class BlankTheme extends Theme {}
However now the wiki tries to load a style from
"$IP/resources/lib/oojs-ui/oojs-ui-core-blank.css" and this seems to be
not customizable. Am i doing this wrong or is this implementation just
not possible? Adding a CSS file right there seems like a core hack which
i want to avoid, ideally I'd like to not even load a CSS file in the
first place.
Cheers
Alex
Hi folks,
The Wikimedia Commons app [1] (a community-maintained Android app that
allows users to upload photos to Commons from their phone) was funded via
an Individual Engagement Grant [2] last year and has several new features -
a list and map of nearby places that need photos (based on Wikidata),
category suggestions based on the image title, prevention of duplicate
uploads, and a new tutorial to educate new users on what types of photos
should or should not be uploaded. During the grant period, 20554 new files
were uploaded via the app with an overall deletion rate of 15.74% (11.7% in
the final two weeks after the new tutorial was implemented), and 3485
images that were uploaded via the app were used in Wikimedia articles.
While we are very happy with the progress made, there are many other
improvements that we would like to make but were not able to fit into the
scope of the previous grant. Thus we are proposing a renewal [3] of the IEG
in order to work on these. Highlights of the proposed improvements include:
- Enhancing the "Nearby places that need photos" feature by (1) allowing
users to upload their image directly from a location on the list or map,
with suggested title and categories based on the associated Wikidata item,
and (2) displaying the user's real-time position on the map to allow easier
navigation to the location they wish to photograph
- Improving user education by displaying Commons account and user talk
notifications (e.g. picture nominated for deletion) in the app, adding a
gallery of featured images, and adding various notices and explanations in
the upload screen
- A sleeker, more intuitive, and more interactive user interface - a
floating action button for uploads, "Nearby places that need photos" in a
tab alongside the user's contributions, and a panel to display Commons
account notifications and information about the nearest place that needs
photos
- Various technical and quality-of-life improvements, such as two-factor
authentication login, multiple uploads, preventing overwrites, and fixing
memory leaks and battery drain issues
We are especially excited about the "Nearby places that need photos"
enhancements, as we feel that it can help reduce the number of geo-located
Wikidata items that lack pictures, and provide pictures for Wikimedia
articles that lack them. We believe that this is one of our main strengths
as a mobile app - users can have a seamless workflow where they can browse
the places that need photos, select one and move to the location, and then
directly upload the photo after taking it (with relevant titles and
categories suggested), all within the same app and without needing to use a
computer.
Please do take a look at our proposal [3], feel free to provide feedback
and make new suggestions on the Discussion page, and/or endorse the
proposal if you see fit. If you would like to be part of the project, new
volunteers and additions to our diverse team are always welcome - please
visit our GitHub repository [4] and say "Hi". :)
Many thanks!
Regards,
Josephine (Commons app project maintainer)
[1] *https://play.google.com/store/apps/details?id=fr.free.nrw.commons
<https://play.google.com/store/apps/details?id=fr.free.nrw.commons>*
[2] https://meta.wikimedia.org/wiki/Grants:IEG/Improve_%
27Upload_to_Commons%27_Android_App
[3]
https://meta.wikimedia.org/wiki/Grants:Project/Improve_%27Upload_to_Commons…
[4] https://github.com/commons-app/apps-android-commons