Wikitech-l April 2018

wikitech-l@lists.wikimedia.org

71 participants
80 discussions

Tomorrow: Technical Advice IRC Meeting
by Michael Schönitzer 17 Apr '18

17 Apr '18

Sorry for cross-posting! Reminder: Technical Advice IRC meeting again **tomorrow, Wednesday 3-4 pm UTC** on #wikimedia-tech. 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.

1 0

File upload file in HTMLForm with ooui
by Toni Hermoso Pulido 17 Apr '18

17 Apr '18

Hello, I'm trying to migrate a HTMLForm to use ooui by following https://www.mediawiki.org/wiki/OOUI/Using_OOUI_in_MediaWiki htmlForm = HTMLForm::factory( 'ooui', $formDescriptor, 'myform' ); I noticed that a file upload form field that I had defined is not rendered correctly when using ooui. 'fileupload' => array( 'section' => 'upload', 'label' => 'Upload file', 'class' => 'HTMLTextField', 'type' => 'file' ), This is shown as a text field but not as a file upload, as I would have expected... Is there any way to handle this and using OOUI at the same time? Thanks!

3 5

Re: [Wikitech-l] Wikistats 2.0 - Now with Maps!
by יגאל חיטרון 16 Apr '18

16 Apr '18

Hello and thank you. What do you mean in country named "--"? Igal (User:IKhitron) On Feb 15, 2018 00:15, "Nuria Ruiz" <nuria(a)wikimedia.org> wrote: Hello from Analytics team: Just a brief note to announce that Wikistats 2.0 includes data about pageviews per project per country for the current month. Take a look, pageviews for Spanish Wikipedia this current month: https://stats.wikimedia.org/v2/#/es.wikipedia.org/reading/ pageviews-by-country Data is also available programatically vi APIs: https://wikitech.wikimedia.org/wiki/Analytics/AQS/ Pageviews#Pageviews_split_by_country We will be deploying small UI tweaks during this week but please explore and let us know what you think. Thanks, Nuria _______________________________________________ Wikitech-l mailing list Wikitech-l(a)lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l

6 12

Was macht dich diese Woche glücklich? / What's making you happy this week? (Week of 15 April 2018)
by Pine W 16 Apr '18

16 Apr '18

*Conference* The 2018 Wikimedia Conference <https://meta.wikimedia.org/wiki/Wikimedia_Conference_2018> starts this week in Germany. The core conference will occur from the 20th through the 22nd. *WMF Research Showcase* On Wednesday, the WMF Research Showcase <https://www.mediawiki.org/wiki/Wikimedia_Research/Showcase#April_2018> will include presentations on two subjects that I think will interest a number of Wikipedians: 1. "The Critical Relationship of Volunteer Created Wikipedia Content to Large-Scale Online Communities" 2. "The Rise and Decline of an Open Collaboration System, a Closer Look" *Photography* As often happens, Wikimedia Commons contributors have selected some great pictures of the day for this month <https://commons.wikimedia.org/wiki/Template:Potd/2018-04>. Here are a few examples: 1. https://commons.wikimedia.org/wiki/File:Lynx_lynx_-_05.jpg 2. https://commons.wikimedia.org/wiki/File:Mezquita_de_Agha_Bozorg,_Kashan,_Ir… 3. https://commons.wikimedia.org/wiki/File:Soyuz_TMA-13_Edit.jpg 4. https://commons.wikimedia.org/wiki/File:Rho_Ophiucus_Widefield.jpg 5. https://commons.wikimedia.org/wiki/File:Indosylvirana_urbis-Kadavoor-2017-0… 6. https://commons.wikimedia.org/wiki/File:Castillo_de_Zafra,_Campillo_de_Due%… 7 https://commons.wikimedia.org/wiki/File:Cirrus_front_over_Austnesfjorden,_A… 8 https://commons.wikimedia.org/wiki/File:Fr%C3%BChlingsallee_Tulpenbl%C3%BCt… What's making you happy this week? You are welcome to comment in any language Pine ( https://meta.wikimedia.org/wiki/User:Pine )

2 1

Announcing project ‘Invest in the MobileFrontend & MinervaNeue frontend architecture’
by Joaquin Oltra Hernandez 16 Apr '18

16 Apr '18

Hi! Over the next fiscal year, the Wikimedia Foundation Readers Web team will be making technical improvements to the mobile web codebases (MobileFrontend and MinervaNeue). The project, which we’re calling ‘Invest in the MobileFrontend & MinervaNeue frontend architecture’, contained in Output 2.7 of the Platform Evolution CDP [1], is currently in its specification and planning stages. The outcomes of the project are: 1. Improve developer experience (on-boarding, maintenance, development) 2. Reduce technical debt and make production improvements 3. Separate presentation and logic 4. Make Minerva and MobileFrontend better citizens of the MediaWiki ecosystem MobileFrontend & MinervaNeue, which power the Wikimedia mobile sites, make heavy use of client-side UIs with templates, CSS and JavaScript. Over the past eight years of developing a mobile-first wiki experience we have learnt and frontend technology has evolved. We will improve and modernize the code bases to continue supporting our mobile web users in the future. Please see Outcomes 1, 2 and 3 in the wiki page for more detail. Minerva will become an independent skin without a dependency on MobileFrontend, and vice versa. Please see Outcome 4 in the wiki page for more detail. Please visit the project page on MediaWiki.org to learn more about the outcomes and outputs, and share your questions. [2] N.B. This project is distinct from “Output 3.1: Contribution tools on mobile web via an existing mediawiki skin” [3], described in the FY 2018-2019 plan. _____________________ Joaquin Oltra Hernandez Senior Software Engineer, Readers Web [1]: https://wikifarm.wmflabs.org/platformevolution/index.php/Plan:FY18-19/2/7 [2]: https://www.mediawiki.org/wiki/Reading/Web/Projects/Invest_in_the_MobileFro… [3]: https://meta.wikimedia.org/wiki/Wikimedia_Foundation_Annual_Plan/2018-2019/…

3 5

Re: [Wikitech-l] Wikitech-l Digest, Vol 176, Issue 39
by Solen win 16 Apr '18

16 Apr '18

Dear Sir, As i found information below, I did not know how to get Bitcoin into my wallet. Pls help me. bitcoin:1NhNVfGXYNY5Z43iErDnmLx7w62TcJuKhm?amount=15.03000000&label=bitcoin%3A3FkenCiXpSLqD8L79intRNXUgjRoH9sjXa On 3/30/18, wikitech-l-request(a)lists.wikimedia.org <wikitech-l-request(a)lists.wikimedia.org> wrote: > 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. Re: changes coming to large dumps (Ariel Glenn WMF) > 2. TechCom Radar, 2018-03-28 (Kate Chapman) > 3. Code of conduct committee call for new members (Amir Ladsgroup) > 4. Re: MediaWiki train rolled back to wmf.26 (Greg Grossmeier) > 5. Better Support for Mobile in Wikistats2 (Nuria Ruiz) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Thu, 29 Mar 2018 15:42:19 +0300 > From: Ariel Glenn WMF <ariel(a)wikimedia.org> > To: Ariel Glenn WMF <ariel(a)wikimedia.org> > Cc: Wikimedia developers <wikitech-l(a)lists.wikimedia.org>, Wikipedia > Xmldatadumps-l <Xmldatadumps-l(a)lists.wikimedia.org> > Subject: Re: [Wikitech-l] changes coming to large dumps > Message-ID: > <CALCvg_4S1zrn1ysjDhRAWtWtNvH5ZB2ARa5arSNEn401c5j8hA(a)mail.gmail.com> > Content-Type: text/plain; charset="UTF-8" > > Here it comes: > > For the April 1st run and all following runs, the Wikidata dumps of > pages-meta-current.bz2 will be produced only as separate downloadable > files, no recombined single file will be produced. > > No other dump jobs will be impacted. > > A reminder that each of the single downloadable pieces has the siteinfo > header and the mediawiki footer so they may all be processed separately by > whatever tools you use to grab data out of the combined file. If your > workflow supports it, they may even be processed in parallel. > > I am still looking into what the best approach is for the pags-articles > dumps. > > Please forward wherever you deem appropriate. For further updates, don't > forget to check the Phab ticket! https://phabricator.wikimedia.org/T179059 > > On Mon, Mar 19, 2018 at 2:00 PM, Ariel Glenn WMF <ariel(a)wikimedia.org> > wrote: > >> A reprieve! Code's not ready and I need to do some timing tests, so the >> March 20th run will do the standard recombining. >> >> For updates, don't forget to check the Phab ticket! >> https://phabricator.wikimedia.org/T179059 >> >> On Mon, Mar 5, 2018 at 1:10 PM, Ariel Glenn WMF <ariel(a)wikimedia.org> >> wrote: >> >>> Please forward wherever you think appropriate. >>> >>> For some time we have provided multiple numbered pages-articles bz2 file >>> for large wikis, as well as a single file with all of the contents >>> combined >>> into one. This is consuming enough time for Wikidata that it is no >>> longer >>> sustainable. For wikis where the sizes of these files to recombine is >>> "too >>> large", we will skip this recombine step. This means that downloader >>> scripts relying on this file will need to check its existence, and if >>> it's >>> not there, fall back to downloading the multiple numbered files. >>> >>> I expect to get this done and deployed by the March 20th dumps run. You >>> can follow along here: https://phabricator.wikimedia.org/T179059 >>> >>> Thanks! >>> >>> Ariel >>> >> >> > > > ------------------------------ > > Message: 2 > Date: Thu, 29 Mar 2018 08:45:12 -0500 > From: Kate Chapman <kate(a)cascadiatm.com> > To: Wikimedia developers <wikitech-l(a)lists.wikimedia.org> > Subject: [Wikitech-l] TechCom Radar, 2018-03-28 > Message-ID: <e1814151-0fad-2da4-6242-bd1a1075d4b3(a)cascadiatm.com> > Content-Type: text/plain; charset=utf-8 > > 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) > > > > > ------------------------------ > > Message: 3 > Date: Thu, 29 Mar 2018 18:25:04 +0000 > From: Amir Ladsgroup <ladsgroup(a)gmail.com> > To: wikitech-l <wikitech-l(a)lists.wikimedia.org>, Wikimedia Mailing > List <wikimedia-l(a)lists.wikimedia.org>, MediaWiki announcements and > site admin list <mediawiki-l(a)lists.wikimedia.org> > Subject: [Wikitech-l] Code of conduct committee call for new members > Message-ID: > <CA+ttme2gtsmoGWivh3=O7AA5kRMBZzmnJPVA6ux-05f2D_k49A(a)mail.gmail.com> > Content-Type: text/plain; charset="UTF-8" > > 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 > > > ------------------------------ > > Message: 4 > Date: Thu, 29 Mar 2018 14:36:56 -0700 > From: Greg Grossmeier <greg(a)wikimedia.org> > To: Wikitech-l <wikitech-l(a)lists.wikimedia.org>, Development and > Operations engineers <engineering(a)lists.wikimedia.org> > Subject: Re: [Wikitech-l] MediaWiki train rolled back to wmf.26 > Message-ID: <20180329213656.k3tsfomkfc4w45sd@x1> > Content-Type: text/plain; charset="utf-8" > > This is still the case. Updates available on the relevant tasks. > > We plan to resume the train (catch up) early next week. > > Sorry for the inconvenience. > > Greg > > <quote name="Greg Grossmeier" date="2018-03-28" time="16:03:23 -0700"> >> 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 | > > > > -- > | Greg Grossmeier GPG: B2FA 27B1 F7EB D327 6B8E | > | Release Team Manager A18D 1138 8E47 FAC8 1C7D | >

1 0

Mobile MonoBook
by Isarra Yos 14 Apr '18

14 Apr '18

I have made a patch for a responsive version of MonoBook with mobile support. See: https://gerrit.wikimedia.org/r/c/421199/ or if you just want a live demo, https://wiki.zaori.org/wiki/Page_title?useskin=monobook - load it on a phone or make your browser window narrow or something and you can see what it looks like. This is a prototype nojs version; I intend to make an even sillier js layout with popovers and stuff as a followup patch. A potential issue has already been raised with the icons: I don't really know how to make text strings actually, well, reliably fit on mobile devices, but a lack of support for no-image usage could also be a real problem in MonoBook. Feedback on that or whatever, as well as other testing and reviews, would be greatly appreciated. There is also a rather more immediate problem at present. As you can see on the patch, jenkins has -1ed it for style problems. Unfortunately I have no idea what the style problems are because the output of that test is totally useless (https://phabricator.wikimedia.org/T190072) - can anyone tell me what the problem(s) are so I can fix them? And/or just resolve T190072? Please? It's starting to get a bit annoying, frankly, as it's been coming up across several of these patches. -I

4 6

Horizon and CI downtime Tomorrow, 2018-04-13
by Andrew Bogott 13 Apr '18

13 Apr '18

Next Friday we'll be upgrading our OpenStack cluster. The upgrade should not interrupt any existing tools or instances, but during the upgrade it will be impossible to create, delete, or modify WMCS VMs. I'll start the process at around 14:00 UTC (7AM PDT). The complete upgrade may take much of the day; Horizon will be disabled for the duration of this update. CI/Nodepool will function intermittently during this time. -Andrew

1 2

Proposal to remove $wgValidateAllHtml and MWTidy::checkErrors() without deprecation
by Kunal Mehta 13 Apr '18

13 Apr '18

Hi, As part of the goal to have MediaWiki 1.31 default to using RemexHtml and replacing tidy, we want to remove MWTidy::checkErrors() and $wgValidateAllHtml as part of MediaWiki 1.31, without a deprecation period. MWTidy::checkErrors() basically ran the provided input through tidy, and checked if it complained. This doesn't make sense using an HTML 5 parser, since they provide recovery conditions to fix parse errors. If $wgValidateAllHtml was set, MediaWiki would output an error page instead of the content if tidy reported errors in the output. Technically, this also means removing TidyDriverBase::validate() (unused besides MWTidy::checkErrors()), and MediaWikiTestCase::assertValidHtmlDocument/assertValidHtmlSnippet() (now unused; previously only used in Capiunto as a defensive check). There is some more rationale and discussion on the task for this: [2]. The Gerrit patch is [3]. [1] https://phabricator.wikimedia.org/T185753 [2] https://phabricator.wikimedia.org/T191670 [3] https://gerrit.wikimedia.org/r/#/c/425093/ -- James & Legoktm

1 1

Review and update your extensions for PHPUnit 6
by Kunal Mehta 13 Apr '18

13 Apr '18

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Hi, tl;dr: Read the "So what do you need to do?" section We're currently in the process of upgrading the MediaWiki PHPUnit version to 6. To avoid an immediate breaking change, we will be doing this transition in two steps. First, we will start running tests with both PHPUnit 4 and 6 (next week), using a compatibility layer to support both. Then at some point during the 1.32 or 1.33 release cycles, we'll drop the compatibility layer and just support 6 (and maybe a later version too?). There are two parts to the compatibility layer. First, an autoloader hack aliases most of the old PHPUnit_Framework_Whatever classes to the new namespaced versions, PHPUnit\Framework\Whatever. This allows tests that use the old class names to continue to work, without any modification. The second part is a trait, PHPUnit4And6Compat, which provides implementations of the getMock() and setExpectedException() functions that were removed in PHPUnit 6. It also has a forward-port of the new createMock() replacement. MediaWikiTestCase uses this trait by default So what do you need to do? First, run your extension tests locally against PHPUnit 6. Edit MediaWiki core's composer.json's dependency on phpunit/phpunit to say "^6.5", run composer update, and then run your extension's tests. If you run into issues about getMock/setExpectedException, then you probably need to add "use PHPUnit4And6Compat;" to your test class. See [1] for an example. Other problems could relate to some class names changing. If you get stuck, please cc or ping me and I can take a look. I'd like to start running voting tests against PHPUnit 4 and 6 next week on Thursday (April 12). This should give us just enough time to fix any resulting issues before the 1.31 branch. [1] https://gerrit.wikimedia.org/r/#/c/424843/ Thanks, - -- Kunal / Legoktm -----BEGIN PGP SIGNATURE----- iQIzBAEBCgAdFiEE+h6fmkHn9DUCyl1jUvyOe+23/KIFAlrJlKcACgkQUvyOe+23 /KKmbQ//UalxjQ9xzsn7sceXUM6y8YFgQtJH08RRq+34tZMXJSEPdoif3xlJm53L 5HfVuFcF73wAtLElM1JKjB30fYOD+7yZ+joLzrgBJ+81bHDncCK+ldOUPrSSHvcZ PuWMcjJ9QimFSRon/ar09GRIEaL1WbXDM+J4EOlViThuTAevoqO+lgeSimkPBkPD K1mxtpES5DGLRiQhAX1OZtuOJBuKfX0bshX7RO833Z2ZnwCLjcTTyyUQClANP9yR xsVQCqtUTvtbMnx3zH3FhWxbI6qQosEqdK+nS2kwXMKw72roKXe3r6yDJtqHNaTy gz/lj3HJYynNjVcF9sVDmBL5pqrpG5NLDiz4AZJrViaRLsfqX+ibcKPQpoaWh9fh gz6Y7DzFpB3gDXepJmy+SJCidksB6YMOs+BQMQjqKBSrVHvFuKIt3zHxZ13aUQ+L lCyp7pfB83Q1NpKm8ss2lUVGDiEL+1yU45c3MixBjdx/I4fCdF5RfdEpHA/N1scG G4uMiPf9TprV3vHk57sS7AAZembqOGj5lTCceKAgFVil0TlHzsYjgBcaQbU0qecI bb9/uxPeEP7pJ4mEbgJGzCa9aQaVI6qQ+LORC84BD24l3k8M/6pFfkZ52BOz2lAy VE/2rXRcmFPbTkWgh8J3yEIjwgCeDOKK/JDVyhdIeWwz65MOOMs= =BmSB -----END PGP SIGNATURE-----

1 1

2026

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