Wikitech-l May 2020

wikitech-l@lists.wikimedia.org

51 participants
59 discussions

Production Excellence #20: April 2020
by Krinkle 14 May '20

14 May '20

📘 Read on Phabricator at https://phabricator.wikimedia.org/phame/post/view/193/ ------- How are we doing on that strive for operational excellence during these unprecedented times? ## 📊 Numbers for March and April * 3 documented incidents. [1] * 60 new Wikimedia-prod-error reports. [2] * 58 Wikimedia-prod-error reports closed. [3] * 178 currently open Wikimedia-prod-error reports in total. [4] For more about recent incidents and pending actionables see Wikitech and Phabricator, at https://wikitech.wikimedia.org/wiki/Incident_documentation and https://phabricator.wikimedia.org/project/view/4758/ ------- ## 📉 Outstanding reports Breakdown of recent months: * April 2019: Two reports closed, 2 of 14 left. * May: (All clear!) * June: 4 of 11 left (unchanged). * July: 8 of 18 left (unchanged). * August: 2 of 14 reports left (unchanged). * September: 7 of 12 left (unchanged). * October: Two reports closed, 4 of 12 left. * November: One report closed, 4 of 5 left. * December: Two reports closed, 4 of 9 left. * January 2020: One report closed, 5 of 7 reports left. * February: One report closed, 6 of 7 reports left. * ❇️ March: 2 new reports survived the month of March. * ❇️ April: 13 new reports survived the month of April. Take a look at the workboard and look for tasks that could use your help. → https://phabricator.wikimedia.org/tag/wikimedia-production-error/ At the end of February the total of open reports over recent months was 58. Of those, 12 got closed, but with 15 new reports from March/April still open, the total is now up at 61 open reports. The workboard overall (which includes pre-2019 tasks) has 178 tasks open. This is actually down by a bit for the first time since October with December at 196, January at 198, and February at 199, and now April at 178. This was largely due to the Release Engineering and Core Platform teams closing out forgotten reports that have since been resolved or otherwise obsoleted. ------- ## 🎉 Thanks! Thank you to everyone who helped by reporting, investigating, or resolving problems in Wikimedia production. Thanks! Until next time, – Timo Tijhof ------- Footnotes: [1] Incidents. – https://wikitech.wikimedia.org/wiki/Incident_documentation [2] Tasks created. – https://phabricator.wikimedia.org/maniphest/query/HjopcKClxTfw/#R [3] Tasks closed. – https://phabricator.wikimedia.org/maniphest/query/ts62HKYPBxod/#R [4] Open tasks. – https://phabricator.wikimedia.org/maniphest/query/Fw3RdXt1Sdxp/#R

1 0

VisualEditor - still in beta?
by Martin Urbanec 14 May '20

14 May '20

Hello, It's been years since VisualEditor is available, but it's still in Beta at many wikis. Why is that? If a wiki wants VE to grow out of beta, can that happen? Thanks, Martin

2 3

Scrum of scrums/2020-05-13
by Željko Filipin 13 May '20

13 May '20

Hi, for HTML version, see https://www.mediawiki.org/wiki/Scrum_of_scrums/2020-05-13 Željko -- = 2020-05-13 = == Callouts == * From PI to SRE: What's the current timeline for getting mobileapps and chromium-render onto the the deployment pipeline / k8s? ([[phab:T218733]], [[phab:T225680]] ) * Release Engineering ** [All] Review guidance at [[wikitech:Deployments/Covid-19]] and Code Deployment Office Hour at 17:00UTC in #wikimedia-office == Product == === Growth === * Blocking: ** Release Engineering - [Low priority] Growth team: Fix Flow DB errors from phpunit tests – [[phab:T249839]], blocking [[phab:T246358]] === Android native app === * Updates: ** All set for a Beta rollout of Suggested Edits V4 and Mobile-html features. ** Currently working on Suggested Edits V5:[[phab:project/view/4645/]] === Web === * Updates: ** '''Summary''': new Desktop Improvements Project (DIP) header is merged, prototyping, scaffolding, and task prioritization for Vue.js search, and collapsible sidebar is under development. ** [[Reading/Web/Desktop_Improvements|Desktop Improvements Project (Vector / DIP)]]: *** [[phab:T251521|<nowiki>Regression: Vector skin did not populate all variants option in the variant drop-down menu</nowiki>]] *** [[phab:T250093|<nowiki>Add title attribute to opt-out link</nowiki>]] *** [[phab:T249372|<nowiki>[Dev] DRY up the menu templating code</nowiki>]] *** [[phab:T249073|<nowiki>[Spike 4hrs] Discuss and agree on nomenclature and rules for template partial usage and CSS organization from experience with header</nowiki>]] *** [[phab:T246419|<nowiki>Build collapsible sidebar and sidebar button</nowiki>]] *** [[phab:T240622|<nowiki>[Technical debt payoff] Remove InlineDiffFormatter and InlineDifferenceEngine from MobileFrontend</nowiki>]] *** [[phab:T251212|<nowiki>[Dev] Drop VectorTemplate usage in Vector</nowiki>]] *** [[phab:T244392|Vue.js search case study]]: **** [[phab:T249299|<nowiki>[Epic] Build the new Vue.js search experience</nowiki>]] **** [[phab:T249051|<nowiki>Where does the application-specific Vue.js search code live and what impact does this decision have on the long term?</nowiki>]] **** [[phab:T249725|<nowiki>Should Desktop Improvements use Vue 2 or Vue 3 for Vue.js search?</nowiki>]] **** Prototyping and task prioritization ** Mobile website (MinervaNeue / MobileFrontend): *** [[phab:T249518|<nowiki>[AMC] Regression on History page in Advanced Mode</nowiki>]] *** [[phab:T251817|<nowiki>[Dev] Allow extensions to update the footer without resorting to SkinTemplateOutputPageBeforeExec hook</nowiki>]] === Product Infrastructure === * Blocked by: ** SRE on migrating mobileapps and chromium-render to the pipeline (see Callouts) * Updates: ** Push Notifications RFC moved to Last Call [[phab:T249065]] == Technology == === Fundraising Tech === * Updates: ** Building employer search into payments form for matching gifts: [[phab:T251200]] ** Smoke testing changes to pipeline to sever direct link between payments-wiki and backend DB: [[phab:T215463]] ** Deploying new CentralNotice features: region-level geotargeting and banner templates: [[phab:T252596]] ** Figuring out best way to notify donors when recurring donation fails: [[phab:T230064]] ** Migrating recurring donations from main card processor's old API to new one: [[phab:T169357]] === Engineering Productivity === ==== Quality and Test Engineering ==== * Updates: ** QTE Office Hours - May 15th - 16:00 UTC ==== Release Engineering ==== * Blocked by: ** [Low priority] SRE Service Ops: Provide our special component/php72 in buster-wikimedia — [[phab:T250515]] ** [Low priority] Wikibase team: Fix WikibaseLexeme DB errors from phpunit tests – [[phab:T249838]], blocking [[phab:T246358]] ** [Low priority] Growth team: Fix Flow DB errors from phpunit tests – [[phab:T249839]], blocking [[phab:T246358]] * Updates: ** [All] Deployments/Covid-19 [[wikitech:Deployments/Covid-19]] ** Train Health *** Last week: 1.35.0-wmf.31 - [[phab:T249963]] *** This week: 1.35.0-wmf.32 - [[phab:T249964]] *** Next week: 1.35.0-wmf.32 - No train (EngProd virtual off-site) === Site Reliability Engineering === * Blocking: ** Product infrastructure on move of mobileapps and chromium-render to k8s ** Release Engineering - [Low priority] SRE Service Ops: Provide our special component/php72 in buster-wikimedia — [[phab:T250515]] == Wikimedia DE == === Wikidata === * Blocking: ** Release Engineering - [Low priority] Wikibase team: Fix WikibaseLexeme DB errors from phpunit tests – [[phab:T249838]], blocking [[phab:T246358]]

1 0

[Train] 1.35.0-wmf.32 status update (blocked)
by Brennen Bearnes 12 May '20

12 May '20

The 1.35.0-wmf.32 version of MediaWiki is currently blocked[0]. The new version can't proceed to group0 until this issue is resolved: * T247028: Database 'INSERT' query rate doubled (module_deps regression?) - https://phabricator.wikimedia.org/T247028 Thanks in advance for any assistance! -- Your train conductor from last week, making a guest appearance to send this mail [0]. <https://phabricator.wikimedia.org/T249964>

1 0

New Feature from Community Tech: Enhanced Password Reset
by Ilana Fried 12 May '20

12 May '20

Hello everyone, The Community Tech team[1] has released a new feature: Enhanced Password Reset[2]. We developed this feature in response to the #3 wish[3] from the 2019 Community Wishlist Survey[4]. With this feature, you can prevent password reset emails from being sent unless both your username and email address are provided on Special:PasswordReset. This is an optional feature, available in the “Email options” section of Preferences. If you enable the feature, you can reduce harassment through unsolicited password reset emails. For more information, you can visit the Help:Password Reset page[5] and the project page[6]. Thank you, Ilana Fried Product Manager, Community Tech [1]. https://meta.wikimedia.org/wiki/Community_Tech [2]. https://www.mediawiki.org/wiki/Help:Reset_password#I%E2%80%99m_getting_pass… [3]. https://meta.wikimedia.org/wiki/Community_Wishlist_Survey_2019/Anti-harassm… [4]. https://meta.wikimedia.org/wiki/Community_Wishlist_Survey_2019/Results [5] https://www.mediawiki.org/wiki/Help:Reset_password [6] https://meta.wikimedia.org/wiki/Community_Tech/Password_Reset_Update

5 4

CI downtime Monday May 11st 12:00 UTC
by Antoine Musso 11 May '20

11 May '20

Hello, We need to upgrade the operating system on the server hosting the CI systems (Zuul, Jenkins). We will switch the services from contint1001 (eqiad) to contint2001 (codfw) which has been upgraded to Buster. The maintenance is scheduled for Monday May 11st 14:00 CEST (12:00 UTC), just after the European SWAT window. The maintenance window is TWO HOURS, but probably the switch will be complete in a shorter time frame. During the maintenance, CI will not be available: no tests will be run and events (code-review +2, rebase, new patchsets) will not be captured. The beta cluster will NOT be automatically updated. If a change has to happen on the configuration repositories: * operations/puppet : locally run: bundle update && bundle exec rake test * operations/mediawiki-config : locally run: composer install && composer test Then manually V+2 and Submit the change. After the maintenance, Antoine will retrigger most events. The related changes are: https://gerrit.wikimedia.org/r/c/operations/dns/+/594480 https://gerrit.wikimedia.org/r/c/operations/puppet/+/594477 The related ticket is: https://phabricator.wikimedia.org/T224591 Synchronization will happen on IRC in #wikimedia-operations Later we will switch back from contint2001 to contint1001. The goal is to get rid of jessie servers and run fully on buster. cheers, -- Antoine Musso && Daniel Zahn

2 2

Maps on wikidata
by Strainu 10 May '20

10 May '20

Hey folks, Can someone point me to the code that decides which zoom to use for the maps that are displayed in the items with coordinates? Thanks, Strainu

3 3

Contribute and help enhance our Wikimedia Foundation projects.
by Fokou Joel 10 May '20

10 May '20

Good evening/morning I'm Fokou Joel, level 300 Computer Engineering student in the Faculty of Engineering And Technology at the University of Buea (Cameroon). I'm getting a lot of experience in Software Development especially in Web Development, Algorithms and Datastructures, and Mobile Development. I have the ability to highly develop, improve, and enhance Application while programming and optimization as well. To be more explicit, I develop in PHP, JavaScript, HTML5 and CSS3 ReactJS, JQuery, Java, and C++. Coming to the database, I work with MySQL and Postgresql. I am really interested to contribute to this amazing community, Meanwhile, I will really appreciate if someone can point me from where to start. Thank you beforehand. Best regard

3 2

How to get number of articles or related metrics for indic wiki's ?
by Shrinivasan T 09 May '20

09 May '20

Hello all, I am planning to build a grafana dashboard using Prometheus for the counts of all indic wiki articles. Have to get all the counts and write a custom exporter. Planning for a dashboard showing counts for articles in all indic languages. Another dashboard to show counts for all wiki projects for selected language. Have few queries. 1. How to get the number of articles in a wiki for example, tamil wikipedia ? Any api is there to get numbers? 2. Can we run a sparql query from our own server? 3. Once these dashboards are built, can we host custom exporter, Prometheus and grafana in tool server or any wiki cloud server? Whom to contact for hosting these ? Will do these in remote Hackathon this weekend. Shrini

2 2

Re: [Wikitech-l] [Wikimedia-l] Wikimedia Meet
by Amir Sarabadani 09 May '20

09 May '20

Hey, A quick update. In order to improve its security, from now on, ticketmasters don't need to know your username and password (and don't send them your desired username and password anymore). You ask them a token and they generate you an one-time-use token for you and then you can use that in https://meet-auth.wmflabs.org/create to create your account for yourself. Stay safe, stay home. On Sun, Apr 26, 2020 at 1:11 AM Alessandro Marchetti via Wikimedia-l < wikimedia-l(a)lists.wikimedia.org> wrote: > I told so many times WMF should support infrastructure for the > volunteers, so thank you very much for this step in that direction. > A.M. > > Il domenica 26 aprile 2020, 01:08:01 CEST, Tito Dutta < > trulytito(a)gmail.com> ha scritto: > > Hello, > That's super great news. I definitely want to try it. Thanks a lot for > working on this. > > Thanks > Tito Dutta > Note: If I don't reply to your email in 2 days, please feel free to remind > me over email or phone call. > > > On Sun, 26 Apr 2020 at 01:57, Amir Sarabadani <ladsgroup(a)gmail.com> wrote: > > > Hey, > > "Wikimedia Meet" [0] (https://meet.wmcloud.org), is a project in > Wikimedia > > CloudVPS for Wikimedians to meet virtually instead of using commercial > > services like Zoom which might have security and privacy implications > > [1][2]. Currently it's a jitsi (jitsi.org) installation. > > > > If you want to just use/test it, let me know and I create you a user and > > password. You can share the username and password with anyone you want to > > meet but please do not post it publicly. In your email you can also give > me > > your desired user and password. **Do not reuse any password**. You can > also > > contact any of the ticketmasters instead of me: > > https://meta.wikimedia.org/wiki/Wikimedia_Meet#List_of_ticketmasters > > > > In order to make this project more robust, I'm looking for Ticketmasters > > too, Ticketmasters create accounts for others (It doesn't require any > > technical knowledge, you fill a form in web for others) > > > > If you want to help maintaining it (which would be greatly appreciated) > let > > me know and I give you the needed access. I put the technical > documentation > > in mediawiki.org [3]. There are several bits you can help with, like > > puppetizing it, scalability, observability, improving authentication, > > trying to see if BBB can be used as well, and so much more. You can find > > the tickets in the phabricator board and assign a ticket to yourself if > you > > feel like helping out. > > > > [0] https://meta.wikimedia.org/wiki/Wikimedia_Meet > > [1] https://blogs.harvard.edu/doc/2020/03/27/zoom/ > > [2] > > > > > https://www.theguardian.com/technology/2020/apr/02/zoom-technology-security… > > [3] https://www.mediawiki.org/wiki/Wikimedia_Meet > > > > Hope that would be useful for our users :) > > Best > > -- > > Amir (he/him) > > _______________________________________________ > > Wikimedia-l mailing list, guidelines at: > > https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines and > > https://meta.wikimedia.org/wiki/Wikimedia-l > > New messages to: Wikimedia-l(a)lists.wikimedia.org > > Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, > > <mailto:wikimedia-l-request@lists.wikimedia.org?subject=unsubscribe> > _______________________________________________ > Wikimedia-l mailing list, guidelines at: > https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines and > https://meta.wikimedia.org/wiki/Wikimedia-l > New messages to: Wikimedia-l(a)lists.wikimedia.org > Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, > <mailto:wikimedia-l-request@lists.wikimedia.org?subject=unsubscribe> > _______________________________________________ > Wikimedia-l mailing list, guidelines at: > https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines and > https://meta.wikimedia.org/wiki/Wikimedia-l > New messages to: Wikimedia-l(a)lists.wikimedia.org > Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, > <mailto:wikimedia-l-request@lists.wikimedia.org?subject=unsubscribe> -- Amir (he/him)

2 3

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 May 2020