Wikitech-l March 2018

wikitech-l@lists.wikimedia.org

68 participants
72 discussions

Better Support for Mobile in Wikistats2
by Nuria Ruiz 29 Mar '18

29 Mar '18

Hello! Analytics is working on better support for mobile in wikistats2: http://stats.wikimedia.org/v2 Do take a look at latest changes and if there are issues that prevent you from using this site in mobile let us know. A phabricator ticket (http://phabricator.wikimedia.org) with a screenshot will be great. Site should be usable in: * last two versions of any major desktop browser (chrome, FF, edge and safari) * any newish iOS device (iphone4 and up) that has been kept up to date * android 4.4 and up We are still working on improving our mobile support and happy to take requests on higher levels of support for browsers we might have not considered. This is the work we have planned for next quarter: - Persistent links for metrics. Bookmarks. task T179444 <https://phabricator.wikimedia.org/T179444> - Support annotations task T178015 <https://phabricator.wikimedia.org/T178015> - Label non obvious concepts task T177950 <https://phabricator.wikimedia.org/T177950> - Improvements on pageview data per country task T188928 <https://phabricator.wikimedia.org/T188928> Thanks, Nuria

1 0

MediaWiki train rolled back to wmf.26
by Greg Grossmeier 29 Mar '18

29 Mar '18

The new MediaWiki weekly branch has some issues that are preventing us from deploying as planned. The specific issue: https://phabricator.wikimedia.org/T190960 The tracking task for the train: https://phabricator.wikimedia.org/T183966 Reminder that you can use the "Wikimedia MediaWiki versions"[0] tool on ToolForge to to know which wikis have which version at any time. Greg [0] https://tools.wmflabs.org/versions/ -- | Greg Grossmeier GPG: B2FA 27B1 F7EB D327 6B8E | | Release Team Manager A18D 1138 8E47 FAC8 1C7D |

1 1

Code of conduct committee call for new members
by Amir Ladsgroup 29 Mar '18

29 Mar '18

Hello all, It's coming close to time for annual appointments of community members to serve on the Code of Conduct (CoC) committee. The Code of Conduct Committee is a team of five trusted individuals plus five auxiliary members with diverse affiliations responsible for general enforcement of the Code of conduct for Wikimedia technical spaces. Committee members are in charge of processing complaints, discussing with the parties affected, agreeing on resolutions, and following up on their enforcement. For more on their duties and roles, see https://www.mediawiki.org/wiki/Code_of_Conduct/Committee <http://meta.wikimedia.org/wiki/Ombudsman_commission> This is a call for community members interested in volunteering for appointment to this committee. Volunteers serving in this role should be experienced Wikimedians or have had experience serving in a similar position before. The current committee is doing the selection and will research and discuss candidates. Six weeks before the beginning of the next Committee term, meaning 8th of April 2018, they will publish their candidate slate (a list of candidates) on-wiki. The community can provide feedback on these candidates, via private email to the group choosing the next Committee. The feedback period will be two weeks. The current Committee will then either finalize the slate, or update the candidate slate in response to concerns raised. If the candidate slate changes, there will be another two week feedback period covering the newly proposed members. After the selections are finalized, there will be a training period, after which the new Committee is appointed. The current Committee continues to serve until the feedback, selection, and training process is complete. If you are interested in serving on this committee or like to nominate a candidate, please write an email to techconductcandidates AT wikimedia.org with details of your experience on the projects, your thoughts on the code of conduct and the committee and what you hope to bring to the role and whether you have a preference in being auxiliary or constant member of the committee. The committee consists of five members plus five auxiliary members and they will serve for six months; all applications are appreciated and will be carefully considered. The deadline for applications is end of day on 5th of April, 2018. Please feel free to pass this invitation along to any users who you think may be qualified and interested. Best, Amir on behalf of the CoC committee

1 0

TechCom Radar, 2018-03-28
by Kate Chapman 29 Mar '18

29 Mar '18

Hi All, Here are the minutes from this week's TechCom meeting: * This week’s IRC Meeting: Tracking dependencies for multiple Content objects per page (MCR) <https://phabricator.wikimedia.org/T190063> Meeting log: <https://tools.wmflabs.org/meetbot/wikimedia-office/2018/wikimedia-office.20…> (summary still to be posted in Phabricator ticket) * RFC Declined (topic can be picked up again when resourced): Define an official thumb API <https://phabricator.wikimedia.org/T66214> * Ops has turned on some services in Eqsin data center, showing improvement for readers in Singapore. Still experimental, but initial results positive. 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/>. -- Kate Chapman TechCom Facilitator (Contractor)

1 0

Turn mapframe for English Wikipedia? We’re ready if you are
by Joe Matazzoni 28 Mar '18

28 Mar '18

In October 2017, English Wikipedia community members approved an RfC requesting implementation of mapframe <https://en.wikipedia.org/wiki/Wikipedia:Village_pump_(technical)/Archive_15…> [1]—a feature that enables contributors to easily display dynamic maps on article pages. At the time, there was some question about whether technical support for the maps service would be available long term, and the Foundation asked that the community stand by. I’m writing now to say that those questions have been answered, and a small team will be assigned for routine maps maintenance. So, unless we hear from the English Wikipedia community that the consensus on adding mapframe has changed since last year’s RfC, we plan to move forward in April 2018. You can read more about this plan and leave comments on Village Pump [2]. If you foresee any issues, let us hear from you. Otherwise, happy mapping! [1] https://en.wikipedia.org/wiki/Wikipedia:Village_pump_(technical)/Archive_15… <https://en.wikipedia.org/wiki/Wikipedia:Village_pump_(technical)/Archive_15…>? [2] https://en.wikipedia.org/wiki/Wikipedia:Village_pump_(technical)#Turn_on_ma… <https://en.wikipedia.org/wiki/Wikipedia:Village_pump_(technical)#Turn_on_ma…> Joe Matazzoni Product Manager, Collaboration Wikimedia Foundation

1 0

Re: [Wikitech-l] [Ops] new deployment server (tin -> deploy)
by Mukunda Modell 28 Mar '18

28 Mar '18

Update: deployments are moving back to tin temporarily while we work out what to do about php7 (or rather, the lack of php5 in stretch) See https://phabricator.wikimedia.org/T190909 On Wed, Mar 28, 2018 at 4:32 AM, Chad Horohoe <chorohoe(a)wikimedia.org> wrote: > Indeed. There was nobody aiming for making php -l or l10nupdate or anything > else *faster*....it was a planned move to stretch and HHVM has been > unacceptably > slow in this area. The decision earlier today to use PHP7 was to avoid the > huge > penalty if we fell back to HHVM instead of using PHP5. > > In any case: we've reverted back to tin for now: > https://gerrit.wikimedia.org/r/#/c/422376/ > > -Chad > > > On Wed, Mar 28, 2018 at 2:25 AM Mukunda Modell <mmodell(a)wikimedia.org> > wrote: > >> This isn't really motivated by any enthusiasm for php7. The issue is that >> php5 has been dropped from stretch and updating the os is a blocker for a >> bunch of other things. So we have to deal with the php7 issue to unblock a >> bunch of other stuff which is not available on jessie. >> >> On Wed, Mar 28, 2018 at 3:19 AM, Antoine Musso <hashar(a)free.fr> wrote: >> >>> On 28/03/2018 00:24, Daniel Zahn wrote: >>> > Hi, >>> > >>> > good old tin.eqiad.wmnet was out of warranty and running jessie, >>> > so as part of our hardware refresh goal it had to be replaced by >>> > something new. >>> > >>> > We now have deploy1001.eqiad.wmnet and it's running on stretch with >>> PHP7 >>> > and we just switched deployment servers and Mukunda is running the >>> first >>> > deploy from it as we speak. >>> > >>> > <+logmsgbot> !log twentyafterfour@deploy1001 Started scap: Deploy >>> > 1.31.0-wmf.27 to test wikis >>> > >>> > >>> > Here are the related puppet changes that switched it and added stretch >>> > support: >>> > >>> > https://gerrit.wikimedia.org/r/#/q/project:operations/ >>> puppet+branch:production+topic:deploy1001 >>> > >>> > >>> > Additionally mwscript needed a way to detect php5 or php7, for that >>> see: >>> > https://gerrit.wikimedia.org/r/#/c/422348/ >>> > >>> > There are also more details on today's SAL and on: >>> > https://phabricator.wikimedia.org/T175288 >>> >>> Hello, >>> >>> I am not sure it is a good idea to switch to PHP7 right now, specially >>> in production. I understand the incentive to get l10nupdate , scap php >>> -l etc faster, but really switching mwscript to php7 is too early. >>> >>> There are a few reasons: >>> >>> - Although CI runs PHP7 tests, the jobs run on Jessie with different >>> libraries than Stretch and we use community made Debian packages ( >>> https://deb.sury.org/ ). >>> >>> - The beta cluster is on HHVM, with the equivalent of tin using php5.6. >>> That is where we catch a lot of low hanging fruits. >>> >>> - We all know our test coverage is far from the production reality. >>> >>> - worker machines such as terbium/wasat do rely on mwscript for >>> production critical jobs. I guarantee they will magically explode the >>> minute they are switched to PHP7. >>> >>> - application servers SHELL OUT to mwscript to get other wikis >>> configuration (see SiteConfiguration::getConfig() ). >>> >>> >>> - of course various PHP7 objects/functions would have a slightly >>> different behavior compared to PHP5/HHVM. That has hit us hard >>> previously when we switched. >>> >>> I appreciate all the enthusiasms toward migration to PHP7. But can we >>> please do it professionally with stages and proper testing? I would >>> rather avoid having the whole site down and making the news front page. >>> >>> cheers, >>> >>> -- >>> Antoine "hashar" Musso >>> >>> >>> _______________________________________________ >>> Ops mailing list >>> Ops(a)lists.wikimedia.org >>> https://lists.wikimedia.org/mailman/listinfo/ops >>> >> >> _______________________________________________ >> Ops mailing list >> Ops(a)lists.wikimedia.org >> https://lists.wikimedia.org/mailman/listinfo/ops >> >

2 2

MediaWiki-CodeSniffer 17.0.0 released
by Kunal Mehta 28 Mar '18

28 Mar '18

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Hello! MediaWiki-CodeSniffer 17.0.0 is now available for use in your MediaWiki extensions and other projects. This release features new sniffs, performance improvements, and other bug fixes. Notably, the "MissingParamComment" warning was removed - it often led to people adding documentation like "@param User $user User object" where the comment was not useful, and just a duplicate of the name or type. The full changelog since 16.0.1: * Allow globals to start with numbers (Umherirrender) * Check for close parenthesis first and shorten out earlier (Thiemo Kreu z) * Check for use statement with non-compound name (Umherirrender) * Don't require @covers from abstract tests (Max Semenik) * Forbid usage of assert() (Kunal Mehta) * Improve ClassMatchesFilenameSniff::isMaintenanceScript (Umherirrender) * Improve performance of PrefixedGlobalFunctionsSniff (Umherirrender) * Optimize ClassMatchesFilename sniff for performance (Thiemo Kreuz) * Optimize DirUsage sniff for performance (Thiemo Kreuz) * Optimize MultipleEmptyLines sniff for performance (Thiemo Kreuz) * Remove warning about "missing" @param comments (Thiemo Kreuz) * Simplify UnusedGlobalVariables sniff (Thiemo Kreuz) * Skip closing parentheses in "( )" and "[ ]" instead of rechecking (Thiemo Kreuz) * Skip empty () and [], not processing closing token a second time (Thiemo Kreuz) * Update squizlabs/php_codesniffer to 3.2.3 (Kunal Mehta) * Use faster array_key_exists instead of in_array in 2 sniffs (Thiemo Kreuz) * Use faster strcasecmp() instead of strtolower() for comparisons (Thiemo Kreuz) * Use File::findExtendedClassName to get extends name (Umherirrender) * Use File::getDeclarationName to get the function name (Umherirrender) * Use File::getMethodProperties to get visibility (Umherirrender) * Validate @license against SPDX (Umherirrender) * Validate phpunit annotations (Umherirrender) - -- Legoktm -----BEGIN PGP SIGNATURE----- iQIzBAEBCgAdFiEE+h6fmkHn9DUCyl1jUvyOe+23/KIFAlq8BRYACgkQUvyOe+23 /KJbvg//c9C8YCRm7GSahC5swIlOMaBlTFDT85ZKHsRML1FGWAv2N1SKMTBNkTn/ Az6qfo8DriqOwApgIxA9TXMI3JareBWQzphuXGWz7OMGQD029rolTQ5T5urPNcu+ nEgcPEvLiwC1Mflj3abfVhr4FTncAI9zpjBoSwIF5EOfJRsx79lEuX6Gz9gVBxU+ 4zsvQ0kx0zf6wLinK5i8WsIaV5nJN218vr4/wkI1g85zCVdqoebVrYGfF5sI7FAt P1ZYpzSd0eY5EYxkiBkjd6ZmzjIY8hnwKOl80lDBNPzH6+K0tOP0nj8p9nIeJVyS X0/shWSJsdjgr3rpD6zdzFi69ow9zwffIsT+tlWUIuFsv/fXfEZkXwPLQECSSBTv sHfKPQgUWgmdPEvHaGp7SyN7xExIbPm+kxPwsOEYufsDPU/c0M2BOC+FF5d7eFa2 luVItCnCaou6fwT4CdI0XQX2eVjTk0D1P32gs0P6pDcKjG8Elg4k5UEmQUnP4Iyy HalGL8bjzlLcdwJTOWgWyH7JUHcv1v0gVvja35SUHpgdMCwINvnZFpKc8BMFj6MG b6f8LrL2bbdmxWhJxdp0Oqk0J7jzaGMYahtb+hPk9ENV0mi5TUGDHUW2msBLvWwa ZriHPMbOnalCiZq+Sn6vomKM+hs9aXyyJiVXyNdSH0JhhPke9Jo= =Lgpe -----END PGP SIGNATURE-----

1 0

Re: [Wikitech-l] Example .spec file for packaging Mediawiki with RPM
by Hogan, Michael C 28 Mar '18

28 Mar '18

Kunal, thank you for the reference to the Fedora .spec files. Anyone know if there's a technical / policy reason for the Fedora EPEL package to be stuck at mediawiki123? https://mirror.umd.edu/fedora/epel/7/x86_64/Packages/m/ -Michael -----Original Message----- From: Wikitech-l [mailto:wikitech-l-bounces@lists.wikimedia.org] On Behalf Of wikitech-l-request(a)lists.wikimedia.org Sent: Tuesday, March 27, 2018 5:00 AM To: wikitech-l(a)lists.wikimedia.org Subject: Wikitech-l Digest, Vol 176, Issue 34 Send Wikitech-l mailing list submissions to wikitech-l(a)lists.wikimedia.org To subscribe or unsubscribe via the World Wide Web, visit https://lists.wikimedia.org/mailman/listinfo/wikitech-l or, via email, send a message with subject or body 'help' to wikitech-l-request(a)lists.wikimedia.org You can reach the person managing the list at wikitech-l-owner(a)lists.wikimedia.org When replying, please edit your Subject line so it is more specific than "Re: Contents of Wikitech-l digest..." Today's Topics: 1. Replacing Tidy on Wikimedia wikis: Next round (Subramanya Sastry) 2. Example .spec file for packaging Mediawiki with RPM? (Hogan, Michael C) 3. Re: Example .spec file for packaging Mediawiki with RPM? (Kunal Mehta) ---------------------------------------------------------------------- Message: 1 Date: Mon, 26 Mar 2018 14:53:27 -0700 From: Subramanya Sastry <ssastry(a)wikimedia.org> To: wikitech-l(a)lists.wikimedia.org Subject: [Wikitech-l] Replacing Tidy on Wikimedia wikis: Next round Message-ID: <d8a9b509-251f-a92f-9bbf-73b3f620248a(a)wikimedia.org> Content-Type: text/plain; charset=utf-8; format=flowed Hello everyone, On behalf of the Parsing Team @ the WMF, I am announcing our plans to replace Tidy with Remex on the next set of wikis. On April 4th, we plan to turn off Tidy on all wikiquotes (except frwikiquote) [1] and wikimedia wikis [2]. 23 wikis will have Tidy replaced. On April 11th, we plan to turn off Tidy on all wikis with < 50 entries in all high priority linter categories [3]. About 60 wikis will have Tidy replaced. Please follow T175706 [4] to monitor progress of Tidy replacement. Currently about 600 wikis have had Tidy replaced and we have another 300 wikis to go. We plan to finish this transition from Tidy to RemexHtml by end of June 2018. If you have any questions or concerns, please leave a comment on the associated phabricator tickets or leave a message on mw.org [5]. Thanks, Subbu. [1] https://phabricator.wikimedia.org/T188881 [2] https://phabricator.wikimedia.org/T190726 [3] https://phabricator.wikimedia.org/T190731 [4] https://phabricator.wikimedia.org/T175706 [5] https://www.mediawiki.org/wiki/Help_talk:Extension:Linter ------------------------------ Message: 2 Date: Mon, 26 Mar 2018 22:02:49 +0000 From: "Hogan, Michael C" <Michael.C.Hogan2(a)boeing.com> To: "wikitech-l(a)lists.wikimedia.org" <wikitech-l(a)lists.wikimedia.org> Subject: [Wikitech-l] Example .spec file for packaging Mediawiki with RPM? Message-ID: <522be458713a415bb5e2cb933f77362d(a)XCH15-04-08.nw.nos.boeing.com> Content-Type: text/plain; charset="us-ascii" Anyone know of a Mediawiki RPM .spec file posted online? I've only been able to find pre-packaged RPMs. Thank you! ------------------------------ Message: 3 Date: Mon, 26 Mar 2018 17:00:20 -0700 From: Kunal Mehta <legoktm(a)member.fsf.org> To: wikitech-l(a)lists.wikimedia.org Subject: Re: [Wikitech-l] Example .spec file for packaging Mediawiki with RPM? Message-ID: <109bc4b8-78ce-37cb-abc3-a6f746a4e295(a)member.fsf.org> Content-Type: text/plain; charset=utf-8 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Hi, On 03/26/2018 03:02 PM, Hogan, Michael C wrote: > Anyone know of a Mediawiki RPM .spec file posted online? I've only > been able to find pre-packaged RPMs. Thank you! The .spec files that Fedora uses are available at <https://src.fedoraproject.org/rpms/mediawiki/tree/master>. - -- Legoktm -----BEGIN PGP SIGNATURE----- iQJLBAEBCgA1FiEE+h6fmkHn9DUCyl1jUvyOe+23/KIFAlq5iZIXHGxlZ29rdG1A bWVtYmVyLmZzZi5vcmcACgkQUvyOe+23/KLvtw//VRq2kgLTUO9Iaj+lUHBZKHo7 svXF2XN9sOiJL/gUahLyWBn69wSAky8vmuGRWSqttrJ6baqHuV0bjZf7wx8ba7PJ j0nb6q6swlNS5yUAp9shk7c4MuPnByqoet3iFjfDjxocQH8XNFiDPpAxO2W09YoH dPZ1yQRQZCRj8ZeJSSfr+LY0wXaPB/h9m8IX8dDemvG3Cw3D5AGaA/wLUH1Mif/Y Yibrynh9b+NpQeBg6UG4MrpkNS6c54TW+SCkQS6ljLzeSZkuPfHCfqv/VcAQm2QT clA50xnl31XSCIRwFjKV/F/xFmlUXaC1iwJsqYJZnXmTe/GXrP5n2s8xVgnws7hp LAqr8Pcws0wHtSrPmaXBrrngFazUvf2VIVP6sP13cIoc2j3HXaUjAFTo4oDpx0BD CXQXFXfpAgXT7Te60OgvtNQp3Zg3CZcev7WcpzjZfl3/m+M70wQLzGy5HS7hBdXY LfEmpfc7QyKl0W8CdwsX+h58okFsxSdKu6wS9kstUotw5EMX62YYvmmSTqJck8r+ jzagCQF++Ler/TAeCK3LqICpwnZ3w9CZWO8fL12iOnxHnGya2YMsGsFBR4SBEgZ0 AghqVRFQEaSl1WxnEIMtSdFqLf3fGRYWl+1l0a3u7xuQ3DQXbYKtjXmemDaEeYfZ NafRDhU0jFvKbNrhzj8= =O2z6 -----END PGP SIGNATURE----- ------------------------------ Subject: Digest Footer _______________________________________________ Wikitech-l mailing list Wikitech-l(a)lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l ------------------------------ End of Wikitech-l Digest, Vol 176, Issue 34 *******************************************

2 1

Discovery Weekly Update for the week starting 2018-03-19
by Chris Koerner 28 Mar '18

28 Mar '18

Hi, Below you'll find the weekly update from the Search Platform team for the week starting 2018-03-19. As always, feedback and questions welcome. == Discussions == === Search === * Trey has finished his initial review of a Slovak stemmer, and so far it looks like like the less aggressive version of the stemmer performs well. [0] Next steps may include more testing and packaging a version of the stemmer into an Elasticsearch plugin. == Did you know? == * The English word ''nice'' has undergone many big swings in meaning, including “foolish”, “painstaking”, “strict”, “subtle”, and “risky”. See the obsolete and dated senses in English Wiktionary [1] or the etymological information at Etymonline [2]. [0] https://www.mediawiki.org/wiki/User:TJones_(WMF)/Notes/Slovak_Stemmer_Analy… [1] https://en.wiktionary.org/wiki/nice#English [2] https://www.etymonline.com/word/nice --- Subscribe to receive on-wiki (or opt-in email) notifications of the Discovery weekly update. https://www.mediawiki.org/wiki/Newsletter:Discovery_Weekly The archive of all past updates can be found on MediaWiki.org: https://www.mediawiki.org/wiki/Discovery/Status_updates Interested in getting involved? See tasks marked as "Easy" or "Volunteer needed" in Phabricator. [1] https://phabricator.wikimedia.org/maniphest/query/qW51XhCCd8.7/#R [2] https://phabricator.wikimedia.org/maniphest/query/5KEPuEJh9TPS/#R Yours, Chris Koerner Community Liaison Wikimedia Foundation

1 0

2018-03-28 Scrum of Scrums meeting notes
by Grace Gellerman 28 Mar '18

28 Mar '18

https://www.mediawiki.org/wiki/Scrum_of_scrums/2018-03-28 = 2018-03-28 = == Callouts == * Fundraising campaigns https://meta.wikimedia.org/wiki/CentralNotice/Calendar - next up: Netherlands 2018-04-03 through 2018-05-01 * Language blocked on Research: Recommendation API fails with internal error if the optional seed_article param is missing (T190266) * English Wikipedia is rolling out local Wikidata description overrides, which are available via a different API. All on-wiki functionality should be updated to use prop=description instead of prop=pageterms. Affected teams will be contacted by Lani over the coming week; if we forget about you, please reach out. (T184000) * OOUI's default font size has changed from 12.8px to 14px https://phabricator.wikimedia.org/T97631 , and the icons were resized and redesigned https://phabricator.wikimedia.org/T177432 . If you have code using OOUI, you may need to update it after these changes. == Audiences == === Readers === ==== iOS native app ==== * Blocked by: - * Blocking: - * Updates: ** Stil working on Reading Lists (current release board: https://phabricator.wikimedia.org/tag/ios-app-v5.8.0-manatee-on-a-skateboar…), planning to do user testing early this week (details about what we'll be covering: https://phabricator.wikimedia.org/T188962) ** Senior iOS Software Engineer job ad posted ( https://boards.greenhouse.io/wikimedia/jobs/1072152?gh_src=q87rx4bt1#.Wrjw-…), we're preparing hiring materials (tech questions, tech task) ==== Android native app ==== * Blocked by: * Blocking: * Updates: ** Reading list syncing rolled out to 100% of Beta audience (~250K users) ** Will start rolling out to production in ~1-2 more weeks, while we gather feedback from beta users. ==== Readers Web ==== * Blocked by: * Blocking: * Updates: ** *Quarterly goal dependency update: ** Increase learning by lowering the cost of exploration *** Reading Web/Performance ** Continue improving the ways that users can download articles of interest for later consumption *** Reading Web: Tech Ops/RelEng ==== Readers Infrastructure ==== * Blocked by: * Blocking: * Updates: ** enabled Wikidata description override for enwiki on Wednesday (T184000) ** enabled TemplateStyles for wikivoyages on Wednesday (T189834) ===== Maps ===== * Blocked by: Ops creating a schema on maps test server ( https://phabricator.wikimedia.org/T190238) * Blocking: * Updates: *Working with collab * Making progress towards new style deployment ==== Multimedia ==== * Updates ** Search for MediaInfo: Patch merged, follow-up work progressing - thanks to the Search and WMDE teams for being helpful there ** Multi-lingual captions in UploadWizard: Work progressing, thanks to WMDE for being helpful there ** File page display/editing of MediaInfo data: Patch up, working now, thanks especially to Thiemo (WMDE) for walking through stuff when needed Quarterly goal dependency update ** Prepare backend infrastructure for structured data search: Nearly done *** SDC: Search PF/Multimedia/Wikidata ** Wikimedia Technology/Goals/2017-18 Q3#Segment 2: Search integration and exposure: Nearly done *** SDC: Research/Multimedia ** Prepare backend infrastructure for structured data search: Nearly done *** SDC: Search PF/Multimedia/Wikidata === Contributors === ==== Community Tech ==== * Blocked by: * Blocking: * Updates: ** Resolving issues uncovered by GlobalPreferences test deployment last week ==== Anti-Harassment Tools ==== * Blocked by: None * Blocking: None that we know of * Updates: ** Bug Fixes completed for Interaction Timeline ** Continue work on Blocking Tool improvlements ** Continue research on Reporting Tool ==== Editing ==== * Blocked by: None * Blocking: None ** Updates: OOUI font size fixes ==== Parsing ==== * Blocked by: * Blocking: * Updates: ** *Quarterly goal dependency update: ** Support work towards unifying MediaWiki's parser implementations, in liaison with Technology's MediaWiki team *** Parsing:Mediawiki PF/Services ==== Collaboration ==== * Blocked by: * Blocking: * Updates: ** OOUI font size update on the train this week, lots of tweaks to deal with that ** Got maps service working in labs and pointed beta wikis to it. Need to migrate to a new VM though, due to OpenStack issues ** Localized maps labels expected in beta labs end of this week / early next ==== Language ==== * Blocked by: ** Research: Recommendation API fails with internal error if the optional seed_article param is missing (T190266) * Blocking: * Updates: ** Work on CX2 continue, except tools column. === Audiences Design === * Blocked by: * Blocking: * Updates: ==== UI Standardization ==== * Blocked by: * Blocking: * Updates: ** OOUI – v0.26.1 released https://phabricator.wikimedia.org/diffusion/GOJU/browse/master/History.md;v… *** In-time release before MW core cut to address findings from icons/font-size rollout in v0.26.0 on two main tasks below *** WikimediaUI theme's new icon set in place https://phabricator.wikimedia.org/T177432 ! *** Unified VE in Vector/WikimediaUI interface base font-size to usage of OOUI in core/extensions elsewhere https://phabricator.wikimedia.org/T97631 ! ** Style Guide *** Continued work on v1 goals https://phabricator.wikimedia.org/tag/wikimediaui_style_guide/ == Technology == === Analytics === * Blocked by: * Blocking: * Updates: ** Jupyter notebooks hardware has been refreshed and updated software. ** Working with audiences on rolling out the popups feature (desktop previews of pages) to all wikipedias. Not yet enabled on enwiki or dewiki ** responsive Wikistats work is ongoing ** Geowiki dashboard from hadoop data should be finished this week ** Google Summer of Code (improvements to Wikistats 2 UI) - We are currently in the process of chosing among two participants * Quarterly goal dependency update: **Improve, adjust, or create features geared at the needs identified in New Editors research project. *** New Editors Experience:Analytics === Cloud Services === * Blocked by: * Blocking: * Updates: ** === Fundraising Tech === * Blocked by: * Blocking: * Updates: ** Drupal security release dropping today. ** More work on recurring charges with our new payment processor integration. ** Second round of unintended recurring charge cancelations and refunds. ** More work on using EventLogging to get banner impression and fundraiser landing page stats === MediaWiki Platform === * Blocked by: * Blocking: * Updates: ** Announced April 16 as the "pencils down" date for MW 1.31 ** Met with SRE to discuss multi-DC planning ** Actively participated in Enterprise MediaWiki Conference (EMWCon) ( https://www.mediawiki.org/wiki/EMWCon_Spring_2018) *** Cindy presented "Toward a MediaWiki Roadmap" and was a panelist on "MediaWiki Best Practices" panel *** Celebrated MediaWiki's 15th birthday ( https://twitter.com/CindyCicalese/status/976862020925566976) *** Toured NASA Johnson Space Center to get first-hand view of the use of their wikis (https://twitter.com/CindyCicalese/status/976517916488323072) ** Finished extension updates related to Actor table ** MCR code review and development for API updates for query modules ** Comment table follow up schema change still in progress ** Improving test coverage for API modules ** Usual code review and bug fixes *Quarterly goal dependency update: ** Support work towards unifying MediaWiki's parser implementations, in liaison with Technology's MediaWiki team *** Parsing:Mediawiki PF/Services *** Platform Evolution CDP planning in progress * Reduce product and technical debt to modernise our tools and technologies, and to make future changes more effective and efficient *** Parsing/Mediawiki PF *** Platform Evolution CDP planning in progress **1.1 It is possible to store structured data within wiki pages, in particular on media file pages on Commons. We will enable the MediaWiki storage layer to correctly store and process structured data elements within wiki pages. *** SDC: Mediawiki PF/Wikidata *** MCR development in progress === Performance === * Blocked by: ** None * Blocking: ** None * Updates: ** eqsin live, working with Traffic to monitor/evaluate performance impact. (So far: really good!) ** Continuing to have issues with coal, hoping that a new version that went out just now will work ** Prepping a survey-based study on performance perception, using the QuickSurveys extension ** Patch expected today for the ResourceLoader parts of getting Safe Mode working with VisualEditor ** Dynomite option didn't work for multi-DC WANObjectCache, going back to mcrouter. Got some traction with the team at Facebook that maintains that code base, so that's good. (Thanks to Giuseppe from SRE) === Release Engineering === * Blocked by: * Blocking: * Updates: ** * Quarterly goal dependency update: ** Continue improving the ways that users can download articles of interest for later consumption *** Reading Web: Tech Ops/RelEng ** Update: * === Research === * Blocked by: * Blocking: * Updates: *Quarterly goal dependency update: ** Wikimedia Technology/Goals/2017-18 Q3#Segment 2: Search integration and exposure *** SDC: Research/Multimedia ** Update: * === Scoring Platform === * Blocked by: RelEng on git lfs * Blocking: None * Updates: ** ores-support-checklist is almost ready. It's live: http://tools.wmflabs.org/ores-support-checklist ** Will announce it soon === Search Platform === * Blocked by: * Blocking: * Updates: ** *Quarterly goal dependency update: ** Prepare backend infrastructure for structured data search *** SDC: Search PF/Multimedia/Wikidata- Lexeme in progress ** Update: *** Wikidata fulltext search - new code enabled with today's train *** Evaluating feature generation by `query_explorer` functionality of LTR plugin: https://phabricator.wikimedia.org/T187148 *** Working on query parsing refactoring: https://phabricator.wikimedia.org/T185108 *** Working Slovak analysis: https://phabricator.wikimedia.org/T178929 *** Working on Lexeme completion search: https://phabricator.wikimedia.org/T189745 === Security === * Blocked by: * Blocking: * Updates: ** === Services === * Blocked by: none * Blocking: none * Updates: ** New REST endpoints with Reading Infrastructure *** Page Metadata https://en.wikipedia.org/api/rest_v1/#!/Page_content/get_page_metadata_titl… *** Page References https://en.wikipedia.org/api/rest_v1/#!/Page_content/get_page_references_ti… ** Fixed the issue with jobqueue -> mysql connection spikiness ** Cirrus search jobs transfer started. Switched to kafka for test wikis === Site Reliability Engineering === * Blocked by: ** None * Blocking: ** None * Updates: ** Singapore is already serving live traffic, enabling more countries every week ** Backups goal completed successfully ** PuppetDB upgraded, puppetmasters upgraded, debian stretch upgrades (goal) completed successfully ** hardware refreshing last steps being finished (goal) ** Mathoid 100% served from the kubernetes cluster, migration successful ** *Quarterly goal dependency update: ** Continue improving the ways that users can download articles of interest for later consumption *** Reading Web: Tech Ops/RelEng ** Update: Postponed for early next quarter * ** Audiences DesignStandardise our user interfaces to match user expectation of quality from our products *** Audiences Design: Ops ** Update: AFAIK this is done * == Wikidata == * Blocked by: ** None * Blocking: * Updates: ** Continuing to work on better Lua functions ** Continue work on release for Lexeme, probably at the end of April *Quarterly goal dependency update: **1.1 It is possible to store structured data within wiki pages, in particular on media file pages on Commons. We will enable the MediaWiki storage layer to correctly store and process structured data elements within wiki pages. *** SDC: Mediawiki PF/Wikidata ** Update: * ** Prepare backend infrastructure for structured data search *** SDC: Search PF/Multimedia/Wikidata ** Update: * == German Technical Wishlist == * Blocked by: ** Wikidiff2 review (still the same as the weeks before): https://gerrit.wikimedia.org/r/404293 * Blocking: * Updates: ** Shaping AdvancedSearch extension for Beta phase: https://phabricator.wikimedia.org/T187436 ** Making sure FileImporter works with AbuseFilter as expected: https://phabricator.wikimedia.org/T160540 ** Documenting technical control and data flow of FileImporter before deployment: https://phabricator.wikimedia.org/T190716

1 0

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 March 2018