Wikitech-l April 2019

wikitech-l@lists.wikimedia.org

69 participants
80 discussions

Wikimedia production excellence (March 2019)
by Krinkle 21 Apr '19

21 Apr '19

📘 Read on Phabricator at https://phabricator.wikimedia.org/phame/live/1/post/150/ ------- How’d we do in our strive for operational excellence last month? Read on to find out! ## 📊 Month in numbers * 8 documented incidents. [1] * 31 new Wikimedia-prod-error issues reported. [2] * 28 Wikimedia-prod-error issues closed. [3] The number of incidents this month was slightly above average compared to earlier this year (7 in February, 4 in January), and this time last year (4 in March 2018, 7 in February 2018). To read more about these incidents, their investigations, and conclusions; check https://wikitech.wikimedia.org/wiki/Incident_documentation#2019. There are currently 177 open Wikimedia-prod-error issues, similar to last month. [4]\ ## 📉 Current problems Take a look at the workboard and look for tasks that might need your help. The workboard lists known issues, grouped by the week in which they were first observed. → https://phabricator.wikimedia.org/tag/wikimedia-production-error/ Or help someone that’s already started with their patch, via "Tasks #Patch-For-Review". [5] Breakdown of recent months (past two weeks not included): * September: ✔️ Done! The last two issues were resolved. * October: ✔️ Done! The last issue was resolved. * November: 2 issues left (from 1.33-wmf.2). 1 issue was fixed. * December: 4 issues left (from 1.33-wmf.9). 1 issue was fixed. * January: 2 issues left (1.33-wmf.13 – 14). 1 issue was fixed. * February: 5 issues (1.33-wmf.16 – 19). * March: 10 new issues (1.33-wmf.20 – 23). By steward and software component, for issues remaining from February and March: * CPT / JobQueue: https://phabricator.wikimedia.org/T218692 * CPT / MCR: https://phabricator.wikimedia.org/T217329 * CPT / Parser: https://phabricator.wikimedia.org/T216664 * CPT / Revision-backend: https://phabricator.wikimedia.org/T220353, https://phabricator.wikimedia.org/T220257 * Growth / Page deletion: https://phabricator.wikimedia.org/T219816 * Growth / Watchlist: https://phabricator.wikimedia.org/T220245 * Language / Translate: https://phabricator.wikimedia.org/T217380, https://phabricator.wikimedia.org/T219736 * Multimedia / WikibaseMediaInfo: https://phabricator.wikimedia.org/T217285 * Operations / PHP-7.2: https://phabricator.wikimedia.org/T221347 * Search Platform / Elastica: https://phabricator.wikimedia.org/T219234 💡Ideas: To suggest an investigation to highlight in a future edition, feel free contact me by e-mail, or private message on IRC. ## 🎉 Thanks! Thanks to Aaron Schulz, Antoine Musso, Arlo Breault, Bartosz Dziewoński, Brad Jorsch, Daimona, James Forrester, Kosta Harlan, Leszek Manicki, Max Semenik, Niklas Laxström, Petar Petković, Santhosh Thottingal, Stephen Niedzielski, Subbu Sastry, Umherirrender, and Željko Filipin, and everyone else who helped last month by reporting, investigating, or patching errors found in production! Until next time, – Timo Tijhof 🦅 *“This isn’t flying. This is falling… with style!”* ------- Footnotes: [1] Incidents. – https://wikitech.wikimedia.org/wiki/Special:PrefixIndex?prefix=Incident+doc… [2] Tasks created. – https://phabricator.wikimedia.org/maniphest/query/As7RRbh3r2Bq/#R [3] Tasks closed. – https://phabricator.wikimedia.org/maniphest/query/9N6mnWSsJTsu/#R [4] Open tasks. – https://phabricator.wikimedia.org/maniphest/query/47MGY8BUDvRD/#R [5] Open tasks having #Patch-For-Review. – https://phabricator.wikimedia.org/maniphest/query/pzVPXPeMfRIz/#R

1 0

Re: [Wikitech-l] Call for hosts: Wikimedia Hackathon 2020
by Houcemeddine A. Turki 20 Apr '19

20 Apr '19

Dear Ms., I thank you for your efforts. The University of Sfax is interested in hosting the event. Located in Tunisia, the University of Sfax is among the best Computer Science research universities in Arab World and in Africa and has a large community of computer scientists and Wikimedia researchers. 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 -------- Message d'origine -------- De : Rachel Farrand <rfarrand(a)wikimedia.org<mailto:rfarrand@wikimedia.org>> Date : 2019/04/15 18:49 (GMT+01:00) À : chapters(a)wikimedia.ch<mailto:chapters@wikimedia.ch>, Wikimedia developers <wikitech-l(a)lists.wikimedia.org<mailto:wikitech-l@lists.wikimedia.org>>, eds(a)listen.wikimedia.de<mailto:eds@listen.wikimedia.de>, affiliates(a)lists.wikimedia.org<mailto:affiliates@lists.wikimedia.org> Objet : [Wikitech-l] Call for hosts: Wikimedia Hackathon 2020 Hello! Is your organization interested in hosting and co-organizing the 2020 Wikimedia Hackathon? We are looking for co-organizers! Details about the decision process can be found here: - https://www.mediawiki.org/wiki/Hackathons/2020_Decision_Process - https://www.mediawiki.org/wiki/Hackathons/Proposing_a_hackathon#Hackathon_l… 20 <https://www.mediawiki.org/wiki/Hackathons/Proposing_a_hackathon#Hackathon_l…> Details about what it takes to organize a hackathon can be found here: - https://www.mediawiki.org/wiki/Hackathons/Handbook - https://www.mediawiki.org/wiki/Hackathons CHANGES FOR 2019 - Because of changes to the Wikimedia Foundation budgeting process, we are still working on confirming exact budgeting and requirements for this event. Generally we expect similar size and budget to previous years, but this is not finalized. - We are open & encouraging to bids from anywhere, but locations outside of Europe and the USA will be given extra weight. - Focus areas will be defined much further in advance, however participants can work on whatever they like related to Wikimedia Technology / Development. - We are continuing to work on changes around our newcomer support and onboarding as well as our mentoring programs - this will continue to develop until the event. At the same time we are still maintaining additional focus on providing a well-facilitated and organized meeting space for groups and the most active volunteers in the developer community to collaborate face to face, with appropriate representation of Foundation, affiliates, and volunteers, to discuss the future of Wikimedia technologies in depth. - We hope to expand our scholarship program to include more participants from outside of the USA and Europe. Ideally we will announce the host for 2020 by the Prague Hackathon in May. If multiple chapters or organizations are interested, we hope to work together to figure out the the best solution. Any organizations interested in hosting should please create a Phabricator ticket and associate it with the #Developer-Relations project, or email rfarrand(a)wikimedia.org<mailto:rfarrand@wikimedia.org> with a proposal or questions. Srishti and I are happy to assist in creating the ticket if needed. Examples: https://phabricator.wikimedia.org/T162836, https://phabricator.wikimedia.org/T96826, https://phabricator.wikimedia.org/T127050 Please include as much information as possible from: Proposing a hackathon <https://www.mediawiki.org/wiki/Hackathons/Proposing_a_hackathon> Additionally if you are interested in working together on a smaller technical event focused around newcomers in your region please also let me know! We are in the initial stages of building a program around this. Please email me at rfarrand(a)wikimedia.org<mailto:rfarrand@wikimedia.org> with any questions or concerns. I am not on the chapters@ list, so if there is anything that I should respond to, make sure to keep me on CC. Also please forward this email anywhere you think it might be useful. Looking forward to hearing from you! -- Rachel Farrand Events Program Manager Technical Collaboration Team Wikimedia Foundation _______________________________________________ Wikitech-l mailing list Wikitech-l(a)lists.wikimedia.org<mailto:Wikitech-l@lists.wikimedia.org> https://lists.wikimedia.org/mailman/listinfo/wikitech-l

1 0

Gerrit goes 3.0!
by Paladox 19 Apr '19

19 Apr '19

Hi, with the future of Gerrit comes a bright future. Gerrit PolyGerrit has changed to Google Germany PolyGerrit team (created in january). Upstream are planning to ramp up development of PolyGerrit very soon. Gerrit has just had 3.0 branched within the last 2 hours! Which means that is going to be a big release. Gerrit 3.0 key features are no more db's making it easier to both backup and fail gerrit over in case of an emergency. Another key feature is that PolyGerrit is now the only UI in Gerrit. The old UI has been removed! Let's move onto 2.16. We plan to update to Gerrit 2.16 soon [1]. With this update, it will be one of the largest update's to have happened to Wikimedia's Gerrit! PolyGerrit's becomes the default UI. PolyGerrit's UI has changed a lot since 2.15 [2]. PolyGerrit's UI update also include improvements for new users, such as being guided with a screen like [3]. The user will also be told how to update their own change through a dialog on their change. This may improve their experience and help encourage new users to contribute! With this email, i would like to encourage all users to try out the new ui which you can by doing: https://gerrit.wikimedia.org/r/?polygerrit=1 or clicking "Switch to New UI" in the footer. Not all features are implemented like inline editing, project dashboard, editing of project access rules and more. You will find yourself needing to switch back to the OLD UI if you need to do any of that. Once we switch to Gerrit 2.16, you will find your self switching virtually never switching to the OLD UI. Upstream (google) switched off the OLD UI last year and has been a great success! [1] https://phabricator.wikimedia.org/T200739 [2] https://phabricator.wikimedia.org/F28699064 https://phabricator.wikimedia.org/F28699068 https://phabricator.wikimedia.org/F28699070 [3] https://phabricator.wikimedia.org/F28699002

2 1

I'm Support.
by Zin Bo 19 Apr '19

19 Apr '19

zinbo434(a)gmail.com

1 0

TechCom Radar 2019-04-17
by Kate Chapman 18 Apr '19

18 Apr '19

Hi All, Here are the minutes from this week's TechCom meeting: * First TechCom office hours were hosted, committee is planning on making this a regular occurrence: * Log: <https://tools.wmflabs.org/meetbot/wikimedia-office/2019/wikimedia-office.20…> * Minutes: <https://tools.wmflabs.org/meetbot/wikimedia-office/2019/wikimedia-office.20…> * Last Call until April 24: <https://phabricator.wikimedia.org/T220657> Establish Architecture Principles as a policy 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> Thanks, Kate -- Kate Chapman Senior Program Manager, Core Platform Wikimedia Foundation kchapman(a)wikimedia.org

1 0

Reading experience improvements on mobile are live
by Volker E. 18 Apr '19

18 Apr '19

Hi all, last week we've successfully brought the improved font choice to our mobile skin MinervaNeue onto all wikis. It helps to provide our users a better reading experience – across languages, in and beyond latin scripts and a more modern typographic feel to many of our text-focussed projects, taking advantage of specifically designed and optimized fonts for every major system. Technically we're applying an operating system font first stack for running text (every text element besides main page titles, headings of 2nd order, blockquotes, code snippets, basically most of every page) on mobile devices for most popular systems[0]. Thanks to everybody who has helped in the process of this project, Nirzar Pangarkar for bringing the idea to the table[1], Jon Robson, Jan Drewniak, and the rest of Reading Web team for co-researching and supporting the implementation, Alex Hollender for fine-tuning design parts as well as documenting pre- and post-change, Brad Jorsch for important reminder of learnings from the Typography Refresh 2014 and Chris Koerner for accompanying the communication externally along the way. You can read more on the details on the project page and at the Phabricator task. Please let us know if you have any questions or further feedback, either by responding to me or on the project's talk page[2]. [0] - https://m.mediawiki.org/wiki/Design/Projects/Improve_mobile_reading_experie… [1] - https://phabricator.wikimedia.org/T175877 [2] - https://www.mediawiki.org/wiki/Talk:Design/Projects/Improve_mobile_reading_… Enjoy and best regards, Volker -- Senior UX Engineer, Lead User-Interface Standardization Wikimedia Foundation volker.e(a)wikimedia.org | @Volker_E

1 0

New: TechCom office hour on April 17.
by Daniel Kinzler 17 Apr '19

17 Apr '19

Hi all! On April 17, TechCom will hold an ask-us-anything office hour on IRC. In the past, we have held discussions about RFCs in this slot. In the future, we want to do focus RFC discussions more on phabricator - we will still have IRC meetings about RFCs some times, but we want to to try an more open format with the office hours, to give room to ask TechCom questions or bring up recent discussions and concerns outside the RFC process. The first TechCom office hour will be held on #wikimedia-office next week, April 17, 2pm PDT (21:00 UTC, 23:00 CEST). Come and ask us anything, or tell us about your ideas and concerns. -- Daniel Kinzler Principal Software Engineer, Core Platform Wikimedia Foundation

2 2

All Wikimedia production services will move to the Kubernetes pipeline
by James Forrester 17 Apr '19

17 Apr '19

*TL;DR*: As part of the annual plan, we are moving Wikimedia Services to be run in an orchestrated platform driven by a new build pipeline (yes, that means containers). All new services for Wikimedia production must now start using this platform. By the end of June 2019, we will have started converting most remaining services. If you're responsible for an existing or new service, please talk to us. Some Wikimedia functionality is provided by services which operate alongside MediaWiki, complimenting or supporting important features for users. They currently mostly run directly on the "bare metal" shared service clusters. The Deployment Pipeline "TEC3" annual plan[0] involves modernising production platforms, and we have a goal to move all of these to the new platform we've been building. There are many benefits of changing to use this platform: * Adding/removing capacity is easy as easy as a deployment; consequently, overall our clusters will be more scalable, and used more efficiently; * Rolling deployments are the default, reducing disruption and increasing dependability for readers, editors, and other end-users of our services; * Deployments are automatically versioned, rather than relying on a manual process from deployers; * There is increased testing before the deployment, by means of a staging cluster; and * Developers no longer need to create and use deploy repos manually, the pipeline does this. If you are an owner, developer, or deployer of a current or forthcoming Wikimedia production service, we need to hear from you. Some services have already moved to this new platform, and others are moving to it.[1] We are building and improving the features as we discover needs, so while we are confident now that services can run on this platform run reliably, we still lack comprehensive documentation for this platform. We are already in the process of creating it but we would like your input to make sure that we are supporting all our stakeholders. Please peruse the page about the deployment pipeline on wikitech[2] and poke around. What documentation do you actually want? How can we make your work simpler and more straight-forward? Please file a task in Phabricator[3] or comment on the talk page.[4] [0] - https://www.mediawiki.org/wiki/Wikimedia_Technology/Annual_Plans/FY2019/TEC… [1] - https://phabricator.wikimedia.org/T198901 [2] - https://wikitech.wikimedia.org/wiki/Deployment_pipeline [3] - https://phabricator.wikimedia.org/project/profile/2453/ [4] - https://wikitech.wikimedia.org/wiki/Talk:Deployment_pipeline Deployment Pipeline team -- *James D. Forrester* (he/him <http://pronoun.is/he> or they/themself <http://pronoun.is/they/.../themself>) Wikimedia Foundation <https://wikimediafoundation.org/>

1 0

Thank you Tuesday
by Krinkle 17 Apr '19

17 Apr '19

(A few days late, or a day early.) Thank to Ebe123 and Daimona Eaytoy for their work on the Score and AbuseFilter extensions. For years they've been working on these code bases and consistently very responsive to bug reports, maintenance inquiries, and offering help to other interested contributors. Thanks for being awesome! -- Timo

5 5

Change to Wikitech logins: Username now case-sensitive
by Bryan Davis 16 Apr '19

16 Apr '19

A change was deployed to the Wikitech config 2019-04-15T23:16 UTC which prevents users from logging into the wiki with a username that differs in case from the 'cn' value for their developer account. This change is not expected to cause problems for most users, but there may be some people who have historically entered a username with mismatched case (for example "bryandavis" instead of "BryanDavis") and relied on MediaWiki and the LdapAuthentication plugin figuring things out. This will no longer happen automatically. These users will need to update their password managers (or brains if they are not using a password manager) to supply the username with correct casing. The "wrongpassword" error message on Wikitech has been updated with a local override to help people discover this problem. See <https://phabricator.wikimedia.org/T165795> for more details. Bryan, on behalf of the Cloud Services team -- Bryan Davis Wikimedia Foundation <bd808(a)wikimedia.org> [[m:User:BDavis_(WMF)]] Manager, Technical Engagement Boise, ID USA irc: bd808 v:415.839.6885 x6855

4 4

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 2019