= 2018-07-11 =
== Callouts ==
* Fundraising campaigns
https://meta.wikimedia.org/wiki/CentralNotice/Calendar
* Datacenter switchover will happen on the end of this quarter. Dates not
fully set, but a tentative range is 17-29 September 2018 and a switchback
on 8-19 October 2018. We plan for at least 3 weeks this time around.
* Analytics: Spark is now available in Jupyter notebooks
== Audiences ==
=== Readers ===
==== iOS native app ====
Natalia
* Blocked by:
* Blocking:
* Updates:
** Planning to be feature complete on 6.0.0 (
https://phabricator.wikimedia.org/tag/ios-app-v6.0-walrus-on-a-unicycle/) by
the end of the week of July 9
** User testing of feed redesign and search coming up (
https://phabricator.wikimedia.org/T198932 )
==== Android native app ====
* Blocked by:
* Blocking:
* Updates:
** Multi-language release is in production.
** Working on completing prototypes for A/B testing at Wikimania (includes
navigation redesigns, table-of-contents variations, and Wikitext Keyboard)
** https://phabricator.wikimedia.org/project/view/3367/
==== Readers Web ====
* Blocked by:
* Blocking:
* Updates:
**Mobile website (MinervaNeue / MobileFrontend):
***Page issues UI T199005 T191532 T197932 T191528 T199005 T198115 T197931
***Improve diff UI T197491 T197729
***Fixes and hygiene T193418 T193821 T198930 T197106 T199156 T193754
T196767 T188937 T193069
***Finalizing designs for collapsible templates T111565
***Planning for advanced mobile contributions
**Desktop website (Popups):
***Abort outdated HTTP requests T197700
***Send the Accept-Language header when calling API T198619
**Design and product are preparing user interviews for Wikimania
==== Readers Infrastructure ====
James
* Blocked by:
** Release Engineering (CI) for merge of
https://gerrit.wikimedia.org/r/c/integration/config/+/442126
** Language Team for review of the stack with
https://gerrit.wikimedia.org/r/c/mediawiki/core/+/443687
* Blocking:
* Updates:
** Working with the iOS and Android teams on using the Page Library's
transforms in the service. (T170584)
** Still working on supporting lang variants in MCS via the uselang
parameter to MW API requests. (T195948)
** Safari Reading List extension now submitted, awaiting approval from
Safari extension store. (T191998)
** Maps work continues; working with Discovery colleagues to move the test
cluster out of production. (T172090)
==== Multimedia ====
Matthias
* Blocked by:
* Blocking:
* Updates:
** Working on search interface prototyping, so users can search by Wikibase
properties/values
** Continuing work on search backend
=== Contributors ===
==== Community Tech ====
Moriel
* Blocked by:
** PageTriage, can't merge anything right now:
https://phabricator.wikimedia.org/T198137 (help)
* Blocking:
* Updates: GlobalPreferences is deployed; we're working on API modules
**
==== Anti-Harassment Tools ====
Moriel
* Blocked by:
* Blocking:
* Updates:
** RfC coming
==== Editing ====
* Blocked by:
* Blocking:
** Updates:
**
==== Parsing ====
* Blocked by:
* Blocking:
* Updates:
==== Growth ====
* Blocked by:
* Blocking:
* Updates:
**
==== Language ====
Kartik
* Blocked by:
* Blocking:
* Updates:
** Content Translation v2 - work continues: MT warnings and calculations,
Users to notify about old drafts and bug fixes
=== Audiences Design ===
* Blocked by:
* Blocking:
* Updates:
**
==== UI Standardization ====
* Blocked by:
* Blocking:
* Updates:
** New OOUI release coming to MW master today, nothing major.
== Technology ==
=== Analytics ===
Francisco
* Blocked by:
* Blocking:
**Eventlogging outage -
https://wikitech.wikimedia.org/wiki/Incident_documentation/20180705-EventLo…
* Updates
**Close to deploy pagecounts (legacy pageviews) to wikistats, they been
available on API for a while
**Maps improvements
**Working with security on threat model of analytics stack. [wiki, email]
**We had a data drop (now backfilled) that highlighted lack of alarms in
our current eventlogging hadoop pipeline, we will be working on those.
=== Cloud Services ===
* Blocked by:
* Blocking:
* Updates:
**
=== Fundraising Tech ===
Elliott
* Blocked by:
* Blocking:
* Updates:
** Running another 1-hour test on new API for main CC processor
*** sorry for the email disruption!
**** Amazon IP address change led to a failmail for each incoming payment
notification
**** Casey working with net ops team to get firewall rules updated
** More CiviCRM core updates
** More work on CiviCRM donor data deletion extension
** More work on backend for EventLogging-based banner/landingpage
impressions stats
** Testing new CiviCRM extension for recurring donations
** Adding per-country email opt-in checkbox on donation forms
=== MediaWiki Core Platform ===
Cindy
* Blocked by:
* Blocking:
* Updates:
** MediaWiki Platform Team is now part of the Core Platform Team (with
Services)
** Deployed a change to Phabricator config in response to more Phabricator
vandalism
** Working on https://phabricator.wikimedia.org/T100782, "Redirect loop
detected" error live in production
** Platform Evolution Program:
*** Sent kickoff emails to stakeholder teams
*** preparing questions for stakeholders to get input for Wikimedia
Technical Conference
** patches needing review
*** https://gerrit.wikimedia.org/r/c/mediawiki/core/+/443440 (<style>-in-TOC
bugfix)
*** https://gerrit.wikimedia.org/r/c/mediawiki/core/+/322729 (Externallinks
indexing)
*** https://gerrit.wikimedia.org/r/c/mediawiki/core/+/444464 (mobile
Commons login failure bugfix)
2** the usual code review and bug work
=== Performance ===
Ian
* Blocked by:
** None
* Blocking:
** None
* Updates:
** All wikis are writing to both nutcracker and to mcrouter (
https://gerrit.wikimedia.org/r/444932). Reads are coming only from
nutcracker for the time being to ensure the mcrouter cache is hot before
switching.
** Fixed a regression in SaveTiming related to an MCR change:
https://phabricator.wikimedia.org/T198483
** Working on a patch that will cause a warning when a duplicate parse
occurs: https://phabricator.wikimedia.org/T172941
** Released CSSJanus 1.3.0
=== Release Engineering ===
Antoine
* Blocked by:
* Blocking:
** James F. https://gerrit.wikimedia.org/r/c/integration/config/+/442126
** Moriel: UBN https://phabricator.wikimedia.org/T198137 (help)
* Updates:
** Mediawiki train happening during European time this week:
https://lists.wikimedia.org/pipermail/wikitech-l/2018-July/090287.html
** MediaWiki 1.29 is end of life https://phabricator.wikimedia.org/T197669
** Working with MediaWiki Platform Team / Cindy about MediaWiki releasing
** (Security team) Two-factor authentication to be enforced on GitHub
https://phabricator.wikimedia.org/T198810
** Phabricator spam / anti vandalism is ongoing
** Help clean up unused config in production:
https://wikitech.wikimedia.org/wiki/User:Krinkle/Unused_config
=== Research ===
* Blocked by:
* Blocking:
* Updates:
=== Scoring Platform ===
Adam W.
* Blocked by:
** JADE deployment discussions, around schema scalability.
*** https://phabricator.wikimedia.org/T196547
*** https://www.mediawiki.org/wiki/Everything_is_a_wiki_page vs. scalability
***
https://en.wikipedia.org/wiki/User:Risker/Risker%27s_checklist_for_content-…
*** Are we going to re-architect this away from wiki pages after all?
* Blocking:
* Updates:
=== Search Platform ===
Stas
* Blocked by:
* Blocking:
* Updates:
** Refactored search configs to move tuning to mediawiki-config:
https://phabricator.wikimedia.org/T182717
** Fixed namespace/redirect mixup in search:
https://phabricator.wikimedia.org/T115756
** Created separate namespace index:
https://phabricator.wikimedia.org/T192699
** Working on puppet setup multi-instance Elasticsearch:
https://phabricator.wikimedia.org/T198351
** Working on fixing Polish analyzer:
https://phabricator.wikimedia.org/T186046
** Working on ES 6.3 upgrade: https://phabricator.wikimedia.org/T198067
** Working on Lexeme fulltext search:
https://phabricator.wikimedia.org/T196188
** Working on query parsing refactoring:
https://phabricator.wikimedia.org/T185108
=== Security ===
* Blocked by:
* Blocking:
* Updates:
**
=== Site Reliability Engineering ===
* Blocked by:
** None
* Blocking:
** None
* Updates:
** Proton is up and running.
** Eqiad network maintenance ongoing, mostly handled without issues, do
expect the occasional hiccup
** Work started on PHP7 for MediaWiki
** grafana-admin.wikimedia.org last users, update your bookmarks.
== Wikidata ==
* Blocked by:
* Blocking:
* Updates:
**
https://www.mediawiki.org/wiki/Scrum_of_scrums/2018-07-11
== German Technical Wishlist ==
* Blocked by:
* Blocking:
* Updates:
**
== Multi-Content Revisions ==
* Blocked by:
* Blocking:
* Updates:
** read old / write both mode for revision / content schema migration will
be enabled on beta and master (not WMF) next week. See full timeline at
https://docs.google.com/spreadsheets/d/1TkznqoaMH6HTQBSMxXPRhSOo8auf1oMLx6c…
** Storage layer (phase 1) tasks nearing completion
** Delivery date of MCR code for SDC use case is '''1 Sept 2018'''
== SoS Meeting Bookkeeping ==
* Updates:
**Removed the goals dependency check-in from notes template. Will address
that communication via another mechanism.
Wikitech-l,
Greetings. I would like to describe an exciting scenario possible with OpenID Connect.
In the scenario, after choosing to verify their name on their Wikipedia account, a user logs onto Wikipedia and uses OpenID Connect to link their Wikipedia account to multiple verified accounts, for example their Facebook and LinkedIn accounts. At the end of the process, we can envision the user obtaining a checkmark next to their full name on Wikipedia, their real name and a verification icon appearing next to their edits and on their user page. There might even be, per user settings, hyperlinks to their Facebook and LinkedIn pages on their Wikipedia user page. With such features, we can envision allowing groups of users or admins to determine that certain articles require a verified account to edit.
Presently, OpenID Connect functionality is available for MediaWiki as an extension. I would like to see the OpenID Connect functionality under discussion expanded to support scenarios including aforementioned and also integrated into MediaWiki.
Thank you. I hope that the above ideas are also interesting to you in the Wikitech-l community.
Best regards,
Adam Sobieski
http://www.phoster.com/contents/
Congratulations!
On Tue, Jul 10, 2018 at 11:25 AM Whatamidoing (WMF)/Sherry Snyder <
ssnyder(a)wikimedia.org> wrote:
> Congratulations! This is going to be a wonderful feature, and it wouldn't
> have happened without the team's dedication and persistence in the face of
> multiple difficulties. I'm so happy that this has been successfully
> deployed.
>
>
>
> On Tue, Jul 10, 2018 at 11:20 AM Niharika Kohli <nkohli(a)wikimedia.org>
> wrote:
>
>> Hello all,
>>
>> I'm happy to announce that GlobalPreferences
>> <https://www.mediawiki.org/wiki/Help:Extension:GlobalPreferences> is now
>> available on all Wikimedia wikis. This project came out of the Wishlist
>> Survey in December 2016 (
>> https://meta.wikimedia.org/wiki/2016_Community_Wishlist_Survey/Results).
>> It was #4 on the list. The Community Tech team (
>> https://meta.wikimedia.org/wiki/Community_Tech) has worked for over 14
>> months, well past the yearly deadline, to deliver on it. This is one of the
>> most important projects this team has ever undertaken.
>>
>> You can enable Global Preferences from *Preferences > Set your global
>> preferences* under your User Profile. You can also set per-wiki
>> exceptions
>> <https://www.mediawiki.org/wiki/Help:Extension:GlobalPreferences#Local_excep…> for
>> each global preference.
>>
>> This has been a long-desired feature (with the earliest known ticket
>> dating back to July 2008 - https://phabricator.wikimedia.org/T16950).
>> I'd like to give a shout out to Kunal Mehta (Legoktm), Sam Wilson and Max
>> Semenik for all their hard work that went into this project.
>>
>> You can read more about the genesis of the project on the project page:
>> https://meta.wikimedia.org/wiki/Community_Tech/Global_preferences
>>
>> You can find more information about how to use GlobalPreferences on the
>> Help page:
>> https://www.mediawiki.org/wiki/Help:Extension:GlobalPreferences
>>
>> Questions and comments are welcome on the discussion page:
>> https://www.mediawiki.org/wiki/Help_talk:Extension:GlobalPreferences
>>
>> If there is a project you deeply care about and would like our team to
>> work on, please remember to submit a proposal for it during the next
>> Wishlist survey (
>> https://meta.wikimedia.org/wiki/2018_Community_Wishlist_Survey)
>> scheduled to take place in November 2018. Make sure to let your friends at
>> Wikimania know about it too. :)
>>
>> Thanks!
>> --
>> Niharika
>> Product Manager
>> Community Tech
>> Wikimedia Foundation
>>
>>
>> _______________________________________________
>> Wmfall mailing list
>> Wmfall(a)lists.wikimedia.org
>> https://lists.wikimedia.org/mailman/listinfo/wmfall
>>
> --
> Sherry Snyder (WhatamIdoing)
> Community Liaison, Wikimedia Foundation
> _______________________________________________
> Wmfall mailing list
> Wmfall(a)lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/wmfall
>
Reminder: Technical Advice IRC meeting again **tomorrow, Wednesday 3-4 pm
UTC** on #wikimedia-tech.
This time in English and Farsi!
The Technical Advice IRC meeting is open for all volunteer developers,
topics and questions. 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 WMDE’s tech team)
--
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.
Hello all,
I would like to announce the release of MediaWiki Language Extension
Bundle 2018.07. This bundle is The bundle is compatible with MediaWiki
1.30 and 1.31 or above and requires PHP 5.5.9 or above.
Next MLEB is expected to be released in 3 months. If there are major
changes or important bug fixes, we will do intermediate release.
Please give us your feedback at
[[Talk:MLEB|https://www.mediawiki.org/wiki/Talk:MLEB]].
* Download: https://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2018.07.tar…
* sha256sum: 36aa80c78be6dcfb533f96dc25afdabd2fd4716452c1b5a6f2bc982def1af7bc
* Signature: https://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2018.07.tar…
Quick links:
* Installation instructions are at: https://www.mediawiki.org/wiki/MLEB
* Announcements of new releases will be posted to a mailing list:
https://lists.wikimedia.org/mailman/listinfo/mediawiki-i18n
* Report bugs to: https://phabricator.wikimedia.org/
* Talk with us at: #mediawiki-i18n @ Freenode
Release notes for each extension are below.
-- Kartik Mistry
== Highlights and upgrade notes ==
== Babel ==
=== Noteworthy changes ===
* Fixed Mobileview. (T178782)
== cldr ==
=== Noteworthy changes ===
* Updated cldr to version 33.
== CleanChanges ==
=== Noteworthy changes ===
* Enable CCFiltersOnly by default.
[https://translatewiki.net/wiki/Special:Gadgets/export/HoverPopTools
Gadget] can be use as replacement.
== LocalisationUpdate ==
* Maintainance updates only.
== Translate ==
=== Noteworthy changes ===
* Special:SupportedLanguages: List of authors is now sorted by the
number of contributions.
* Message keys coming from external files are now handled with more
care and less likely to produce invalid or inaccessible pages.
([[phab:T193023|T193023]])
* Translation interface has a new keyboard shortcut for saving
translations: Ctrl+Enter. ([[phab:T194915|T194915]])
* Links in displayed message documentation now open in a new tab by default.
* refresh-translatable-pages.php script can now use JobQueue, which is
more efficient on wikis with thousands of translatable pages.
([[phab:T195347|T195347]])
* Translation interface: Fixed positioning of insertables in Timeless skin.
* Custom languages defined in $wgExtraLanguages now always appear in
Special:Translate and Special:SearchTranslations.
([[phab:T112889|T112889]])
* PHPlot is now listed as a composer dependency.
* Improved the interplay of $wgTranslateBlacklist and
blacklist/whitelist in message group configuration.
== UniversalLanguageSelector ==
=== Noteworthy changes ===
* Maintenance and localisation updates.
==== Input Methods ====
* Fixed rule for 'ж' in Serbian keyboard.
* Added Fon keyboard.
--
Kartik Mistry | કાર્તિક મિસ્ત્રી
kartikm.wordpress.com
Hey,
As a pet project of mine, I have been trying to find and fix discrepancies
between the database schema in the codebase (like tables.sql in mediawiki
core) and production. I wrote a script to do a basic analysis and got the
results but it was so big that I needed to cluster them so now we have this
reports: https://phabricator.wikimedia.org/T104459#4314828
Some are hot fixes (like tmp_2 indexes) that probably need to be added to
the codebase (with proper name) or dropped from production which needs
investigation.
Some are unimplemented schema changes, like user_options column in user
table that was dropped in the code nine years ago but fell into the cracks
and never got fixed in production.
Some are changes that partially implemented like page_no_title_convert
field on page table that only appear in 32 hosts (around two third of the
hosts) and there is mention of adding it in HISTORY but I can't find any
mention of removing it neither its existence so I have no idea how to
proceed here.
The problem is that these cases need investigation before we can hand it
off to our DBAs. For example, rc_cur_time field in recentchanges table has
been dropped from the mediawiki core in 2014 but it exists in production
but it also still exists in oracle, potgres and mssql schemas but not in
mssql, sqlite or mysql schemas. In this case, we need to fix both
production and several schemas in mediawiki core.
Or text table on 21 hosts (around half of them) has an extra field called
inverse_timestamp which I can't find any mention of it in the code but
there used to be a field with this name in revision table that got dropped
in 2005 and I have no idea how to proceed here.
It would be great if you take a look the clustered reports [1] and make a
phabricator ticket for them and investigate how to proceed here. Thank you
[1]: https://phabricator.wikimedia.org/T104459#4310482
Best