Wikitech-l August 2019

wikitech-l@lists.wikimedia.org

50 participants
61 discussions

Wikidata and Health Session at 10.30
by Houcemeddine A. Turki 17 Aug '19

17 Aug '19

Dear all, I thank you for your efforts. I invite you to our session about Wikidata and Health that will occur on 10.30 in Tu's Room. It will be an honour to see your opinions about this important area. Yours Sincerely, Houcemeddine Turki (he/him) Medical Student, Faculty of Medicine of Sfax, University of Sfax, Tunisia Undergraduate Researcher, UR12SP36 GLAM and Education Coordinator, Wikimedia TN User Group Member, WikiResearch Tunisia Member, Wiki Project Med Member, WikiIndaba Steering Committee Member, Wikimedia and Library User Group Steering Committee Co-Founder, WikiLingua Maghreb Founder, TunSci ____________________ +21629499418

1 0

Wikiwisdom: A Project Proposal
by Adam Sobieski 16 Aug '19

16 Aug '19

Wikimedia-l, Wikitech-l, I would like to share a new project proposal: https://meta.wikimedia.org/wiki/Wikiwisdom . The project intends to provide a large-scale, crowdsourced collection of wisdom materials (anecdotes, proverbs, quotations, lyrics, poetry, narratives and humor). The project intends to increase the ease with which people can search for, discover and share wisdom materials. The project intends to advance scholarly and scientific research into wisdom, folklore, heritage, tradition, history and culture. Thank you for taking a look at the project proposal. You may edit the project proposal page and add yourself as an interested person. The discussion page of the project proposal is also available for discussions. Best regards, Adam Sobieski http://www.phoster.com/contents/

2 1

[GlobalFactSync] User Script, Data Browser, Reference web service - WMF Grant project
by Sebastian Hellmann 15 Aug '19

15 Aug '19

Dear all, we would like to share consolidated updates for the GlobalFactSync (GFS) project with you (copied from https://meta.wikimedia.org/wiki/Grants:Project/DBpedia/GlobalFactSyncRE/News) We polished everything for our presentation at Wikimania tomorrow: https://wikimania.wikimedia.org/wiki/2019:Technology_outreach_%26_innovatio… All feedback welcome! -- Sebastian (with the team: Tina, Włodzimierz, Krzysztof, Johannes and Marvin) User Script, Data Browser, Reference web service (15. August 2019) After the Kick-Off note end of July <https://meta.wikimedia.org/wiki/Grants:Project/DBpedia/GlobalFactSyncRE/New…>, which described our first edit and the concept better, we shaped the technical microservices and data into more concise tools that are easier to use and demo during our Wikimania presentation <https://wikimania.wikimedia.org/wiki/2019:Technology_outreach_%26_innovatio…>: 1. User Script <https://en.wikipedia.org/wiki/User_scripts> available at User:JohannesFre/global.js <https://meta.wikimedia.org/wiki/User:JohannesFre/global.js> shows links from each article and Wikidata to the Data Browser and Reference Web Service <https://meta.wikimedia.org/wiki/User:JohannesFre/global.js> 1. User Script Linking to the GFS Data Browser 2. GFS Data Browser <https://global.dbpedia.org/> Github <https://github.com/dbpedia/gfs> now accepts any URI in subject from Wikipedia, DBpedia or Wikidata, see the Boys Don't Cry example from Kick-Off Note <https://global.dbpedia.org/?s=https%3A%2F%2Fglobal.dbpedia.org%2Fid%2F2nrbo…>, Berlin/Geo-coords lat <https://global.dbpedia.org/?s=https%3A%2F%2Fglobal.dbpedia.org%2Fid%2F4pafr…> long <https://global.dbpedia.org/?s=https%3A%2F%2Fglobal.dbpedia.org%2Fid%2F4pafr…>, Albert Einstein's Religion <https://global.dbpedia.org/?s=https%3A%2F%2Fglobal.dbpedia.org%2Fid%2F55LmB…>. *Not Live yet, edits/fixes are not reflected* 3. Reference Web Service (Albert Einstein: http://dbpedia.informatik.uni-leipzig.de:8111/infobox/references?article=ht…) extracts (1) all references from a Wikipedia page, (2) matched to the infobox parameter and (3) also extracts the fact from it. The service will remain stable, so you can use it. Furthermore, we are designing a friendly fork of HarvestTemplates <https://github.com/Pascalco/harvesttemplates> to effectively import all that data into Wikidata. Kick-off note (25. Juli 2019) *GlobalFactSync - Synchronizing Wikidata and Wikipedia's infoboxes* How is data edited in Wikipedia/Wikidata? Where does it come from? And how can we synchronize it globally? The GlobalFactSync <https://meta.wikimedia.org/wiki/Grants:Project/DBpedia/GlobalFactSyncRE> (GFS) Project — funded by the Wikimedia Foundation — started in June 2019 and has two goals: * Answer the above-mentioned three questions. * Build an information system to synchronize facts between all Wikipedia language-editions and Wikidata. Now we are seven weeks into the project (10+ more months to go) and we are releasing our first prototypes to gather feedback. /How – Synchronization vs Consensus/ We follow an absolute *Human(s)-in-the-loop* approach when we talk about synchronization. The final decision whether to synchronize a value or not should rest with a human editor who understands consensus and the implications. There will be no automatic imports. Our focus is to drastically reduce the time to research all references for individual facts. A trivial example is the release date of the single “Boys Don’t Cry” (March 16th, 1989) in the English <https://en.wikipedia.org/wiki/Boys_Don%27t_Cry_(Moulin_Rouge_song)>, Japanese <https://ja.wikipedia.org/wiki/%E6%B6%99%E3%82%92%E3%81%BF%E3%81%9B%E3%81%AA…'t_Cry%E3%80%9C>, and French <https://fr.wikipedia.org/wiki/Namida_wo_Misenaide_(Boys_Don%27t_Cry)> Wikipedia, Wikidata <https://www.wikidata.org/wiki/Q3020026#P577> and finally in the external open database MusicBrainz <https://musicbrainz.org/artist/e57182dc-2693-46fc-a739-a81c734a4326>. A human editor might need 15-30 minutes finding and opening all different sources, while our current prototype can spot differences and display them in 5 seconds. We already had our first successful edit where a Wikipedia editor fixed the discrepancy with our prototype: “I’ve updated Wikidata so that all five sources are in agreement.” We are now working on the following tasks: * Scaling the system to all infoboxes, Wikidata and selected external databases (see below on the difficulties there) * Making the system: o “live” without stale information o “reliable” with less technical errors when extracting and indexing data o “better referenced” by not only synchronizing facts but also references /Contributions and Feedback/ To ensure that GlobalFactSync will serve and help the Wikiverse we encourage everyone to try our data and micro-services and leave us some feedback, either on our Meta-Wiki page <https://meta.wikimedia.org/wiki/Grants_talk:Project/DBpedia/GlobalFactSyncRE> or via gfs(a)infai.org <mailto:gfs@infai.org>. In the following 10+ months, we intend to improve and build upon these initial results. At the same time, these microservices are available to every developer to exploit it and hack useful applications. The most promising contributions will be rewarded and receive the book “Engineering Agile Big-Data Systems”. Please post feedback or any tool or GUI here. In case you need changes to be made to the API, please let us know, too. For the ambitious future developers among you, we have some budget left that we will dedicate to an internship. In order to apply, just mention it in your feedback post. Finally, to talk to us and other GlobalfactSync-Users you may want to visit WikidataCon and Wikimania, where we will present the latest developments and the progress of our project. /Data, APIs & Microservices (Technical prototypes)/ Data Processing and Infobox Extraction: For GlobalFactSync we use data from Wikipedia infoboxes of different languages, as well as Wikidata, and DBpedia and fuse them to receive one big, consolidated dataset – a PreFusion dataset <https://databus.dbpedia.org/dbpedia/prefusion> (in JSON-LD). More information on the fusion process, which is the engine behind GFS, can be found in the FlexiFusion paper <https://svn.aksw.org/papers/2019/ISWC_FlexiFusion/public.pdf>. One of our next steps is to integrate MusicBrainz into this process as an external dataset. We hope to implement even more such external datasets to increase the amount of available information and references. *First microservices:* We deployed a set of microservices to show the current state of our toolchain. * [Initial User Interface] The GFS Data Browser is our GlobalFactSync UI prototype (available at http://global.dbpedia.org) which shows all extracted information available for one entity for different sources. It can be used to analyze the factual consensus between different Wikipedia articles for the same thing. Example: Look at the variety of population counts for Grimma <https://global.dbpedia.org/?s=https%3A%2F%2Fglobal.dbpedia.org%2Fid%2F9QwA&…>. * [PreFusion JSON API] While the UI allows simple, fast and easy browsing for one entity at a time, we also provide raw access to the underlying data (PreFusion dump). The query UI (http://global.dbpedia.org:8990 (user: read, pw: gfs) can be utilized to run simple analytical queries. Thus, we can determine the number of locations having at least one population value <http://global.dbpedia.org:8990/db/prefusion/provenance?query=%7B%0D%0A++++%…> (1,194,007) but can also focus on examples with data quality problems (e.g. one of the 4,268 locations with more than 10 population values <http://global.dbpedia.org:8990/db/prefusion/provenance?query=%7B%0D%0A++++%…>). Moreover, documentation about the PreFusion dataset and the download link for the data are available on the Databus website <https://databus.dbpedia.org/dbpedia/prefusion>. * [Reference Data Download] We ran the Reference Extraction Service over 10 Wikipedia languages. Download dumps here <http://dbpedia.informatik.uni-leipzig.de/repo/lewoniewski/gfs/infobox-refs/…>. * [Reference Extraction Service] Good references are crucial for an import of facts from Wikipedia to Wikidata. We are currently working with colleagues from Poznań University of Economics and Business on reference extraction for facts from Wikipedia. A current development reference extraction microservice <http://dbpedia.informatik.uni-leipzig.de:8111/infobox/references?article=ht…> shows all references and the location where they were spotted in the Infobox – ad hoc – for a given article: http://dbpedia.informatik.uni-leipzig.de:8111/infobox/references?article=ht… ( ‘&format=tsv’ also available) * [Infobox Extraction Service] A similar ad hoc extraction of factual information from infoboxes and other Wikipedia article information is available here. This microservice displays information which can be extracted with the help of DBpedia mappings from an infobox e.g. from the German Facebook Wikipedia article: http://dbpedia.informatik.uni-leipzig.de:9998/server/extraction/en/extract?…. See here for more options: http://dbpedia.informatik.uni-leipzig.de:9999/server/extraction/. * [ID service] Last but not least, we offer the Global ID Resolution Service <https://global.dbpedia.org/same-thing/lookup/?uri=http://dbpedia.org/resour…>. It ties together all available identifiers for one thing (i.e. at the moment all DBpedia/Wikipedia and Wikidata identifiers – MusicBrainz coming soon…) and shows their stable DBpedia Global ID. /Finding sync targets/ In order to test out our algorithms, we started by looking at various groups of subjects, our so-called sync targets. Based on the different subjects a set of problems were identified with varying layers of complexity: * identity check/check for ambiguity — Are we talking about the same entity? * fixed vs. varying property — Some properties vary depending on nationality (e.g., release dates), or point in time (e.g., population count). * reference — Depending on the entity’s identity check and the property’s fixed or varying state the reference might vary. Also, for some targets, no query-able online reference might be available. * normalization/conversion of values — Depending on language/nationality of the article properties can have varying units (e.g., currency, metric vs imperial system). The check for ambiguity is the most crucial step to ensure that the infoboxes that are being compared do refer to the same entity. We found, instances where the Wikipedia page and the infobox shown on that page were presenting information about different subjects (e.g., see here <https://en.wikipedia.org/wiki/Boys_Don%27t_Cry_(Moulin_Rouge_song)>). /Examples/ As a good sync target to start with the group ‘NBA players’ was identified. There are no ambiguity issues, it is a clearly defined group of persons, and the amount of varying properties is very limited. Information seems to be derived from mainly two web sites (nba.com and basketball-reference.com) and normalization is only a minor issue. ‘Video games’ also proved to be an easy sync target, with the main problem being varying properties such as different release dates for different platforms (Microsoft Windows, Linux, MacOS X, XBox) and different regions (NA vs EU). More difficult topics, such as ‘cars’, ’music albums’, and ‘music singles’ showed more potential for ambiguity as well as property variability. A major concern we found was Wikipedia pages that contain multiple infoboxes (often seen for pages referring to a certain type of car, such as this one <https://en.wikipedia.org/wiki/Volkswagen_Polo>). Reference and fact extraction can be done for each infobox, but currently, we run into trouble once we fuse this data. Further information about sync targets and their challenges can be found on our Meta-Wiki discussion page <https://meta.wikimedia.org/wiki/Grants_talk:Project/DBpedia/GlobalFactSyncR…>, where Wikipedians that deal with infoboxes on a regular basis can also share their insights on the matter. Some issues were also found regarding the mapping of properties. In order to make GlobalFactSync as applicable as possible, we rely on the DBpedia community to help us improve the mappings. If you are interested in participating, we will connect with you at http://mappings.dbpedia.org and in the DBpedia forum <https://forum.dbpedia.org/>. Bottomline – We value your feedback!

1 0

Scrum of scrums/2019-08-14
by Željko Filipin 14 Aug '19

14 Aug '19

Hi, for HTML version see https://www.mediawiki.org/wiki/Scrum_of_scrums/2019-08-14 Željko -- = 2019-08-14 = == Callouts == * Release Engineering: ** This week: 1.34.0-wmf.18 - https://phabricator.wikimedia.org/T220743 - No train this week due to Wikimania ** Next week: 1.34.0-wmf.19 - https://phabricator.wikimedia.org/T220744 *** Core Platform - Hardcoded value in <nowiki>[[MediaWiki:Logentry-rights-blockautopromote/en]]</nowiki> https://phabricator.wikimedia.org/T230296 *** Wikidata - OutOfBoundsException in WikibaseQualityConstraints setup on Beta Wikidata https://phabricator.wikimedia.org/T230050 == Product == === Readers === ==== iOS native app ==== * Updates: ** New bug fix release that has some reading list fixes https://phabricator.wikimedia.org/tag/ios-app-v6.3.2_lobster-on-a-vespa/ ** Working on defining API requirements for article history & diffs https://phabricator.wikimedia.org/tag/ios-app-v6.4-seamonkey-on-a-hoverboar… ==== Readers Web ==== * Updates: ** Summary: wrapping up advanced mode outreach and menu changes, and starting desktop refresh technical planning. ** Responsive website (MinervaNeue / MobileFrontend / Portals): *** [ https://www.mediawiki.org/wiki/Reading/Web/Advanced_mobile_contributions Advanced mobile contributions]: **** [https://phabricator.wikimedia.org/T230154 <nowiki>VE edit cards broken by Minerva change</nowiki>] **** [https://phabricator.wikimedia.org/T230162 <nowiki>"User Rights" in overflow menu has no icon</nowiki>] **** [https://phabricator.wikimedia.org/T214531 <nowiki>History links with curid set do not redirect properly on mobile</nowiki>] **** [https://phabricator.wikimedia.org/T226125 <nowiki>Notifications should appear in a modal dialog or drawer</nowiki>] **** [https://phabricator.wikimedia.org/T226068 <nowiki>AMC Outreach - Modal</nowiki>] **** [https://phabricator.wikimedia.org/T225959 <nowiki>[Bug] Overflow menu has blank entry on community portal when no Wikidata item exists</nowiki>] **** [https://phabricator.wikimedia.org/T225747 <nowiki>[AMC] Rename setting "Advanced mode" (instead of "Advanced contributions mode")</nowiki>] **** [https://phabricator.wikimedia.org/T206354 <nowiki>Main menu should slide over content</nowiki>] **** [https://phabricator.wikimedia.org/T221395 <nowiki>[Bug] BetaOptinPanel turns on Beta and turns off AMC</nowiki>] *** Desktop refresh: **** Technical planning. *** Miscellaneous: **** [https://phabricator.wikimedia.org/T229653 <nowiki>mobilecite is missing i18n title messages for Special:Specialpages</nowiki>] **** [https://phabricator.wikimedia.org/T217295 <nowiki>ReferencesDrawer should be a Drawer, not extend the Drawer</nowiki>] **** [https://phabricator.wikimedia.org/T217102 <nowiki>MFA: TalkSectionAddOverlay should use Overlay.make pattern</nowiki>] **** [https://phabricator.wikimedia.org/T214647 <nowiki>[EPIC] Re-define the contract for displaying drawers and overlays in MobileFrontend</nowiki>] **** [https://phabricator.wikimedia.org/T229972 <nowiki>[Bug] can't re-enter Talk overlay after adding a discussion</nowiki>] **** [https://phabricator.wikimedia.org/T225877 <nowiki>Two link rel="canonical" if $wgEnableCanonicalServerLink and $mfNoIndexPages is true</nowiki>] **** [https://phabricator.wikimedia.org/T225460 <nowiki>Add Redux to MobileFrontend</nowiki>] **** [https://phabricator.wikimedia.org/T224998 <nowiki>Convert Anchor to ES6 class</nowiki>] **** [https://phabricator.wikimedia.org/T220849 <nowiki>Separate View code from SearchOverlay</nowiki>] **** [https://phabricator.wikimedia.org/T150189 <nowiki>Make toasts tappable links when redirecting a user away from a page</nowiki>] ==== Product Infrastructure ==== * Updates: ** Released new endpoint transform/html/to/mobile-html for apps edit preview feature ** MachineVision extension enabled on Beta (see https://www.mediawiki.org/wiki/Wikimedia_Product/Machine_vision_middleware for background) ** Working on launching wikifeeds to resolve the excessive load on mobileapps *** Helm chart currently in review: https://gerrit.wikimedia.org/r/#/c/operations/deployment-charts/+/526679/ == Technology == === Fundraising Tech === * Blocked by: ** need security's blessing on https://gerrit.wikimedia.org/r/526756 to allay deployer fears. * Updates: ** Ready to deploy EventLogging-based pipeline to get and transform banner and landing page view stats from main cluster to payments cluster DBs: https://phabricator.wikimedia.org/T195594 ** India donation form tweaks: https://phabricator.wikimedia.org/T228698 ** More initial tests of one-time to recurring donation conversion: https://phabricator.wikimedia.org/T227051, https://phabricator.wikimedia.org/T227048 ** Resuming final piece of work to cut db links between payments-wiki front end and CiviCRM back end ** Reviewing core CSP work to make sure CentralNotice banner-preview CSP doesn't break: https://phabricator.wikimedia.org/T229607 ** Working through issues blocking updating fundraising python tools to python3: https://phabricator.wikimedia.org/T213757 ** Improvements to CiviCRM data import and export ** Updating CiviCRM dependencies and leaving php5.6 behind. Thanks rel-eng for helping getting our tests up to date. === Core Platform === * Blocking: ** Release Engineering: *** MediaWiki installer silently ignores invalid extensions https://phabricator.wikimedia.org/T225512 *** Hardcoded value in <nowiki>[[MediaWiki:Logentry-rights-blockautopromote/en]]</nowiki> https://phabricator.wikimedia.org/T230296 === Engineering Productivity === ==== Release Engineering ==== * Blocked by: ** Core Platform Team: *** MediaWiki installer silently ignores invalid extensions https://phabricator.wikimedia.org/T225512 *** Hardcoded value in <nowiki>[[MediaWiki:Logentry-rights-blockautopromote/en]]</nowiki> https://phabricator.wikimedia.org/T230296 ** Wikidata *** OutOfBoundsException in WikibaseQualityConstraints setup on Beta Wikidata https://phabricator.wikimedia.org/T230050 * Updates: ** Train Health *** Last week: 1.34.0-wmf.17 - https://phabricator.wikimedia.org/T220742 - Fully deployed *** This week: 1.34.0-wmf.18 - https://phabricator.wikimedia.org/T220743 - No train this week due to Wikimania *** Next week: 1.34.0-wmf.19 - https://phabricator.wikimedia.org/T220744 **** Core Platform - Hardcoded value in <nowiki>[[MediaWiki:Logentry-rights-blockautopromote/en]]</nowiki> https://phabricator.wikimedia.org/T230296 **** Wikidata - OutOfBoundsException in WikibaseQualityConstraints setup on Beta Wikidata https://phabricator.wikimedia.org/T230050 === Security === * Blocking: ** Fundraising tech needs security's blessing on https://gerrit.wikimedia.org/r/526756 to allay deployer fears. == Wikimedia DE == === Wikidata === * Blocking: ** Release Engineering: *** OutOfBoundsException in WikibaseQualityConstraints setup on Beta Wikidata https://phabricator.wikimedia.org/T230050

1 0

TechCom Radar 2019-07-30
by Daniel Kinzler 13 Aug '19

13 Aug '19

Hi All, Here are the minutes from this week's TechCom meeting (and sorry for the delay): * RFC approved after last call: Heredoc arguments for templates (aka "hygienic" or "long" arguments). Implementation will probably have to wait until Parsoid has been ported to PHP, so we don't have to implement it three times. <https://phabricator.wikimedia.org/T99268> * RFC approved after last call: Abstract schemas and schema changes. This allows database updates to be written in a form agnostic to the underlying RDBMS, using the DBAL library. We will be dropping support for Oracle and MSSQL for core to make this feasible. The maintainers of the Oracle and MSSQL backends have expressed interested in adding support back as extensions. <https://phabricator.wikimedia.org/T191231> * RFC approved after last call: Create a proper command-line runner for MediaWiki maintenance tasks. Implementation is pending priorization by the Core Platform Team. <https://phabricator.wikimedia.org/T99268>. * RFC under discussion: Set explicit PHP support target for MediaWiki. <https://phabricator.wikimedia.org/T228342> * The TechCom meeting on August 14 will be a public meeting held as a session at the Wikimania Hackathon, at 15:00 Sweden time (6am in California). * There is no RFC discussion scheduled, and no last calls ongoing. You can also find our meeting minutes at <https://www.mediawiki.org/wiki/Wikimedia_Technical_Committee/Minutes> See also the TechCom RFC board <https://phabricator.wikimedia.org/tag/mediawiki-rfcs/>. If you prefer you can subscribe to our newsletter here <https://www.mediawiki.org/wiki/Newsletter:TechCom_Radar> Cheers, Daniel

1 0

Hack : Web based face login for wikipedia
by Santosh Shingare 09 Aug '19

09 Aug '19

Hello Wikimedian, 3D face recognition has become a trending research direction in both industry and academia. Using your face to authorize to unlock your phone is popular, but on the web it has not been seen a lot, maybe because it’s not trivial to implement. Is it possible to implement face verification using just HTML5, Javascript and some Go? Yes! I did it in an hour using Javascript, Nodejs, and OpenCV for wikipedia login. I Implemented face recognition and web login for wikipedia. Please check following video and screenshots. Very soon I will share code on Github. - https://commons.wikimedia.org/wiki/File:Web_login_with_face_recognition.webm - https://commons.wikimedia.org/wiki/File:Web_login_with_face_recognition_log… - https://commons.wikimedia.org/wiki/File:Web_login_with_face_recognition_and… - https://commons.wikimedia.org/wiki/File:Web_login_with_face_recognition_and… Feel free to revert if you have any question. Thanks & Regards Santosh Shingare, Executive member, Wikimedia India Chapter +91 9890984632 Skype: cherishsantosh | http://wiki.wikimedia.in

3 2

Scrum of scrums/2019-08-07
by Deb Tankersley 08 Aug '19

08 Aug '19

Hello, For HTML version, see: https://www.mediawiki.org/wiki/Scrum_of_scrums/2019-08-07 Deb --- = 2019-08-07 = == Callouts == * Wikidata/WMDE: we would appreciate if there were any updates with regards to fixing issues with the Graphoid, which cause problems on many Wikipedias who use it (https://phabricator.wikimedia.org/T226250), . Some investigation as been done but Yurik doesn't seem to be willing to investigate more or to touch the code. Are there any news about the ownership of Graphoid (WMF team taking over? leaving unmaintained? undeploying?), see https://phabricator.wikimedia.org/T211881. * Informational information from Parsing: ** Tim isolated a GC bug in PHP from the SEGV crasher we found running Parsoid/PHP parser tests *** https://phabricator.wikimedia.org/T228346 is the SEGV phab task and https://bugs.php.net/bug.php?id=78379 is the upstream bug report against PHP *** Please take a look at https://gerrit.wikimedia.org/r/c/mediawiki/services/parsoid/+/527952/4/src/… for a workaround in Parsoid in case your codebases might benefit from this. * Growth: One more threshold update for huwiki: https://phabricator.wikimedia.org/T230031 * Structured Data: As we roll out new features on Commons, we have been seeing a couple of errors that seem to be a product of the MediaInfo extension using underlying Wikibase code in ways different than originally intended. Example: https://phabricator.wikimedia.org/T229280. This is not an emergency or train blocker, but would be good to chat about how we can work together to address issues like this going forward * Search: need some feedback from Slovak speakers: https://phabricator.wikimedia.org/T223787 * Next week: No train due to Wikimania * Services: We fixed ORES precache to handle new "stream" param (not "topic"). Should be good to remove your workaround. https://phabricator.wikimedia.org/T228689 == Product == === Contributors === ==== Editing ==== * Updates: ** Preparing for Wikimania ** Deployed Edit Cards v2 ** Created a Prototype for Toolbar v1 on Mobile ** Working on Phase 2 of Talk Pages report ==== Growth ==== * Updates: ** Preparing for Task Recommendations work === Readers === ==== iOS native app ==== * Updates: ** 6.3.1 released yesterday https://phabricator.wikimedia.org/tag/ios-app-v6.3.1_lobster-on-an-orv/ *** bug fixes *** talk pages enhancements ** 6.4 exploratory phase https://phabricator.wikimedia.org/tag/ios-app-v6.4-seamonkey-on-a-hoverboar… *** iOS13 / iPadOS updates *** Working on a big release that improves article history https://phabricator.wikimedia.org/tag/ios-app-v6.4-seamonkey-on-a-hoverboar… ==== Android native app ==== * Updates: ** Suggested Edits v2 (editing image captions) released to production! ** Mobile html integration is almost done. At 70% now. ==== Readers Web ==== * Updates: ** Summary: [https://phabricator.wikimedia.org/T228916 advanced (mobile) contributions deployed today.] \o/ ** Responsive website (MinervaNeue / MobileFrontend / Portals): *** [ https://www.mediawiki.org/wiki/Reading/Web/Advanced_mobile_contributions Advanced mobile contributions]: **** [https://phabricator.wikimedia.org/T229722 <nowiki>All edits are tagged as "advanced mobile edit" when wgMFAdvancedMobileContributions is true</nowiki>] **** [https://phabricator.wikimedia.org/T229295 <nowiki>Cleanup AMC feature flagging</nowiki>] **** [https://phabricator.wikimedia.org/T229704 <nowiki>Contributions page has regressed since changes to RecentChanges adding visual clutter</nowiki>] **** [https://phabricator.wikimedia.org/T229399 <nowiki>[Bug] [AMC] 1px gap at bottom of page actions without download icon (due to font size usage)</nowiki>] **** [https://phabricator.wikimedia.org/T229360 <nowiki>[AMC] Recent changes design review</nowiki>] **** [https://phabricator.wikimedia.org/T228890 <nowiki>Notification icon should be visible when the notification drawer is open</nowiki>] **** [https://phabricator.wikimedia.org/T228681 <nowiki>Decommision MobileWebMainMenuClickTracking</nowiki>] **** [https://phabricator.wikimedia.org/T228516 <nowiki>Inform AMC users that grouped results are not available on the recent changes page</nowiki>] **** [https://phabricator.wikimedia.org/T228280 <nowiki>Disable grouped results on RecentChanges page on mobile</nowiki>] **** [https://phabricator.wikimedia.org/T226125 <nowiki>Notifications should appear in a modal dialog or drawer</nowiki>] **** [https://phabricator.wikimedia.org/T226068 <nowiki>AMC Outreach - Modal</nowiki>] **** [https://phabricator.wikimedia.org/T225959 <nowiki>[Bug] Overflow menu has blank entry on community portal when no Wikidata item exists</nowiki>] **** [https://phabricator.wikimedia.org/T225747 <nowiki>[AMC] Rename setting "Advanced mode" (instead of "Advanced contributions mode")</nowiki>] **** [https://phabricator.wikimedia.org/T223363 <nowiki>Cleanup Special:RecentChanges filters appearance on Minerva (mobile)</nowiki>] **** [https://phabricator.wikimedia.org/T221137 <nowiki>Skin should reset SkinOptions on UserLogout action.</nowiki>] **** [https://phabricator.wikimedia.org/T221012 <nowiki>Extract $skinOptions from SkinMinerva class</nowiki>] **** [https://phabricator.wikimedia.org/T218206 <nowiki>AMC Navigation - make main menu scrollable</nowiki>] **** [https://phabricator.wikimedia.org/T217197 <nowiki>Move skin "subtitle" markup that contains redirect and breadcrumbs</nowiki>] **** [https://phabricator.wikimedia.org/T206354 <nowiki>Main menu should slide over content</nowiki>] **** [https://phabricator.wikimedia.org/T225213 <nowiki>[SPIKE 8hr] Main Menu should work without javascript</nowiki>] *** Miscellaneous: **** [https://phabricator.wikimedia.org/T229972 <nowiki>[Bug] can't re-enter Talk overlay after adding a discussion</nowiki>] **** [https://phabricator.wikimedia.org/T229653 <nowiki>mobilecite is missing i18n title messages for Special:Specialpages</nowiki>] **** [https://phabricator.wikimedia.org/T229701 <nowiki>Talk page replies lost when clicking on links</nowiki>] **** [https://phabricator.wikimedia.org/T221978 <nowiki>[Bug] Visiting a talk section flashes page content</nowiki>] **** [https://phabricator.wikimedia.org/T217295 <nowiki>ReferencesDrawer should be a Drawer, not extend the Drawer</nowiki>] **** [https://phabricator.wikimedia.org/T214647 <nowiki>[EPIC] Re-define the contract for displaying drawers and overlays in MobileFrontend</nowiki>] **** [https://phabricator.wikimedia.org/T225460 <nowiki>Add Redux to MobileFrontend</nowiki>] **** [https://phabricator.wikimedia.org/T220849 <nowiki>Separate View code from SearchOverlay</nowiki>] **** [https://phabricator.wikimedia.org/T211775 <nowiki>[Bug] Remove download button from pages that don't exist</nowiki>] **** [https://phabricator.wikimedia.org/T150189 <nowiki>Make toasts tappable links when redirecting a user away from a page</nowiki>] **** [https://phabricator.wikimedia.org/T229036 <nowiki>[Bug] Watchlist has skewed thumbnails</nowiki>] ==== Product Infrastructure ==== * Updates: ** Profiling Wikifeeds https://phabricator.wikimedia.org/T229287#5394483 ** Created Beta cluster instance with node 10 for migrating Proton https://phabricator.wikimedia.org/T217114 ** Machine Vision Middleware APIs ** Event Platform Client documentation ==== Structured Data ==== * Blocked by: ** Not a real "block" but it would be good to chat with someone from the Wikidata team about this issue which has appeared occasionally on production since some new structured data features went live on Commons: https://phabricator.wikimedia.org/T229280 * Updates: ** launch of arbitrary wikibase statements on commons went ok ** about to commence work on supporting configurable structured data for campaigns ==== Parsing ==== * Updates: ** Parsoid/PHP parser tests ~99% green now ** Work in progress to enable large scale roundtrip testing on scandium ( https://phabricator.wikimedia.org/T229356 is the tracker task for those interested) *** Enabling Parsoid/PHP on scandium will also let us run performance tests with production content ** Tim isolated a GC bug in PHP from the SEGV crasher we found running Parsoid/PHP parser tests *** https://phabricator.wikimedia.org/T228346 is the SEGV phab task and https://bugs.php.net/bug.php?id=78379 is the upstream bug report against PHP *** Please take a look at https://gerrit.wikimedia.org/r/c/mediawiki/services/parsoid/+/527952/4/src/… for a workaround in Parsoid in case your codebases might benefit from this. === UI Standardization === * Updates: ** Design Style Guide *** Components: Updated overview with slicing structure for “Components” section *** Components: Provided WIP patch for “Components” section at https://github.com/wikimedia/WikimediaUI-Style-Guide/pull/22 ** AMC: Improving collapsible HTMLForm styling in preparation of Special:Contributions transformation to OOUI ** No OOUI release this week due to other priorities above == Technology == === Fundraising Tech === * Updates: ** Ready to deploy EventLogging-based pipeline to get and transform banner and landing page view stats from main cluster to payments cluster DBs (replaces old solution, inexplicably written as a Django app, that parses full web logs reconstructed from Kafkatee): https://phabricator.wikimedia.org/T195594 ** Fixing CentralNotice QUnit tests: https://phabricator.wikimedia.org/T227879 ** Tweaks to India donation form in response to limited initial tests: https://phabricator.wikimedia.org/T228698 ** Deployment and first real-money tests of one-time to recurring donation conversion: https://phabricator.wikimedia.org/T227051, https://phabricator.wikimedia.org/T227048 ** Resuming final piece of work to cut db links between payments-wiki front end and CiviCRM back end ** Training up fundraising non-tech people to bypass Rube Goldberg machine currently used to import Thank You email content from metawiki: https://phabricator.wikimedia.org/T229965 ** Getting up to speed on progress of core CSP work to make sure CentralNotice banner-preview CSP doesn't break: https://phabricator.wikimedia.org/T229607 ** Working through issues blocking updating fundraising python tools to python3: https://phabricator.wikimedia.org/T213757 ** Improvements to CiviCRM data import and export === Core Platform === * Blocking: ** MediaWiki installer silently ignores invalid extensions https://phabricator.wikimedia.org/T225512 * Updates: ** Further rollouts of Kask, paused for performance review ** Final routes of Parsoid API in PHP ** API integration testing === Engineering Productivity === ==== Performance ==== * Blocked by: ** SRE: DeferredUpdates enqueue-on-failure patch (figure out why it fails wikibase tests); https://gerrit.wikimedia.org/r/#/c/mediawiki/core/+/497537/ * Updates: ** Published the Excellence monthly for June 2019. https://phabricator.wikimedia.org/phame/post/view/163/production_excellence… [wiki][email] ** AbuseFilter: Continued CR for Daimona's on-going perf work. – https://phabricator.wikimedia.org/T156095 ** Started widespread audit of CSS image-embed performance to improve page load times. – https://phabricator.wikimedia.org/T121730 ==== Quality and Test Engineering ==== * Updates: ** MediaWiki installer silently ignores invalid extensions https://phabricator.wikimedia.org/T225512 ==== Release Engineering ==== * Blocked by: ** Core Platform Team: *** MediaWiki installer silently ignores invalid extensions https://phabricator.wikimedia.org/T225512 * Updates: ** Train Health *** Last week: 1.34.0-wmf.16 - https://phabricator.wikimedia.org/T220741 – Fully deployed *** This week: 1.34.0-wmf.17 - https://phabricator.wikimedia.org/T220742 – No known blockers yet *** Next week: No train this week due to Wikimania ** Code Health ** Log Health === Scoring Platform === * Blocked by: ** Growth https://phabricator.wikimedia.org/T230031 * Updates: ** ORES deployment (probably Tuesday, Aug 6th): https://phabricator.wikimedia.org/T229848 *** Improvements to huwiki editquality models *** Improvements to enwiki article quality model *** Improvements to wikidata item quality model *** Fixed ORES precache to handle new "stream" param (not "topic") ** Completed https://www.mediawiki.org/wiki/JADE/Use_cases ** Designed a "catch-all" endpoint for Jade. See https://phabricator.wikimedia.org/T229362 Is this a good idea? === Search Platform === * Blocked by: need some feedback from Slovak speakers: https://phabricator.wikimedia.org/T223787 * Updates: ** Improved documentation on search boolean operators: https://phabricator.wikimedia.org/T228925 *** Docs here: https://www.mediawiki.org/wiki/Help:CirrusSearch/Logical_operators ** Set up load balancing for cloudelastic: https://phabricator.wikimedia.org/T224324 ** Set up “did you mean” satisfaction metrics dashboard: https://phabricator.wikimedia.org/T229268 ** Fixed some missing updates after WDQS reload and underlying cause: https://phabricator.wikimedia.org/T228640 ** Waiting for feedback on Slovak stemmer: https://phabricator.wikimedia.org/T223787 ** Working on creating RDF export for SDC/MediaInfo: https://phabricator.wikimedia.org/T221917 ** Working on getting glent suggestions into Elastic indexes: https://phabricator.wikimedia.org/T227364 ** Working on CirrusSearch configuration for cloudelastic: https://phabricator.wikimedia.org/T220625 ** Working on WDQS Updater performance improvements: https://phabricator.wikimedia.org/T212826 === Security === * Updates: ** Team members out / at conferences, intermittent progress will be made on existing tickets over the next 1-2 weeks. === Site Reliability Engineering === * Blocking: ** WMDE/Wikidata would appreciate some review on https://gerrit.wikimedia.org/r/c/operations/puppet/+/526627 ** SRE: DeferredUpdates enqueue-on-failure patch (figure out why it fails wikibase tests); https://gerrit.wikimedia.org/r/#/c/mediawiki/core/+/497537/ * Updates: ** SRE is migrating all cron/maintenance jobs to PHP7, tracking task: https://phabricator.wikimedia.org/T195392 == TechCom == * Updates: ** Last Calls being review in today's TechCom meeting: *** Proper command-line runner for MediaWiki maintenance tasks https://phabricator.wikimedia.org/T99268 *** Heredoc arguments for templates (aka "hygienic" or "long" arguments) https://phabricator.wikimedia.org/T114432 *** Abstract schemas and schema changes https://phabricator.wikimedia.org/T191231 == Wikimedia DE == === Wikidata === * Blocked by: ** Site Reliability Engineering: WMDE/Wikidata would appreciate some review on https://gerrit.wikimedia.org/r/c/operations/puppet/+/526627

1 0

[Tech Talks] Call for Speakers!
by Sarah R 07 Aug '19

07 Aug '19

Hi Everyone, We're looking for speakers who are interested in presenting at the monthly Tech Talks series <https://www.mediawiki.org/wiki/Wikimedia_Technical_Talks> ! Tech talks are a great opportunity for you to share information with the wider Wikimedia community about technical topics and projects you are working on. Giving a tech talk is a great way to develop your presentation skills, while sharing your valuable technical knowledge with others. Content can range from deep dives into very technical topics for very technical audiences to helping nontechnical audiences understand a concept or project your team is working on. You can browse upcoming and past technical talks <https://www.mediawiki.org/wiki/Wikimedia_Technical_Talks#Upcoming_Wikimedia…> for ideas and inspiration. Tech talks are typically broadcast live and recorded for future viewing. Time, date, and format are flexible. Tech talks can be scheduled up to six months in advance. If you are interested, you can submit a proposal for a talk through Phabricator <https://phabricator.wikimedia.org/maniphest/task/edit/form/1/?title=Tech%20…>, and the organizers will contact you with more information. Kindly, Sarah R. Rodlund Technical Writer, Developer Advocacy <https://meta.wikimedia.org/wiki/Developer_Advocacy> srodlund(a)wikimedia.org

1 0

Github: WMFGerrit closing pull requests
by Tyler Cipriani 06 Aug '19

06 Aug '19

tl;dr: If your team doesn't do any development on GitHub then this email likely doesn't affect you. As you may or may not know there is now a read-only replica of Gerrit available at https://gerrit-replica.wikimedia.org/ (hooray); however, over the weekend we noticed some missing tags from that mirror (boo). To fix the missing tags for the replica I forced replication to run for all repos in Gerrit today as part of a configuration restart. After a replication sync I was able to ensure that all repos on the new replica were now up-to-date; however, it also closed all the pull requests that were made via pushing branches to wikimedia-org GitHub repos (which is the work flow of several apps teams and possibly others). Apologies for the inconvenience and thanks to Dmitry Brant and Joe Walsh for pinging me about the problem. I've since removed GitHub as a "mirror" -- meaning Gerrit will not delete branches there. Paladox has filed a task upstream to allow us to specify a full replication for a particular remote (i.e., gerrit-replica but not GitHub) instead of all remotes[0], and for added suspenders for our belt I've made a patch set that should exclude these projects from replicating to from Gerrit to GitHub in the future[1]. I think all of the fallout of this change is taken care of (judging from my GitHub search): <https://github.com/search?p=1&q=org%3Awikimedia+is%3Aunmerged+type%3Apr+upd…> But if your project was affected, please either reach out to me or add your project to the GitHub exclusion list in Puppet like in my patchset[1] and add me as a reviewer. Thanks and sorry -- Tyler [0]. <https://bugs.chromium.org/p/gerrit/issues/detail?id=11280> [1]. <https://gerrit.wikimedia.org/r/c/operations/puppet/+/528276>

2 1

Category aliasing proposals
by Adam Wight 06 Aug '19

06 Aug '19

Friends, As part of an investigation into category aliasing (think “theater directors” vs. “theater directors"), we’ve identified two potential technical implementations and I’m hoping to get feedback to help us choose between the proposals, or change course entirely. For a summary of the problem and solutions, please see https://meta.wikimedia.org/wiki/WMDE_Technical_Wishes/Gendered_Categories and join the talk page if you wish. Some questions on my mind are: * Will the proposed hard-redirect category behavior break any MediaWiki or third-party software assumptions about hard redirects or categories? * Is “non-page” category aliasing really the mountain of tech debt I imagine it to be? * Have there been other attempts to solve this problem? Kind regards, Adam from the Technical Wishes Team at Wikimedia Germany

2 2

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

Wikitech-l August 2019