Wikitech-l April 2019

wikitech-l@lists.wikimedia.org

69 participants
75 discussions

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

17 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

OOUI: problem with button groups
by Huji Lee 15 Apr '19

15 Apr '19

Hello, While I am waiting for my other OOUI-related question to be answered, I want to ask a brand new one! Please see the code here: https://meta.wikimedia.org/wiki/User:Huji/OOUI2.js Once you enable this script, you will be shown a dialog with two sets of buttons. The first set has "Show Emotions" pre-selected, and you see two buttons (Happy and Sad) in the second button group. You can click on those buttons and you will see they get highlighted as you select them. Next, you can click on "Show Animals" and that will swap the second row with a new ButtonSelectWidget which has two choices (Cat and Dog). Again, you can click on Cat or Dog and they will get highlighted and function normally. *Now the problem:* Click on "Show Emotions" again; it will bring back the other ButtonSelectWidget, the one with Happy and Sad buttons; but these buttons do not work anymore. If you click on the they won't get selected, and indeed, the 'choose' even is not triggered for that ButtonSelectWidget anymore either. I also tried a different implementation in which instead of swapping the contents of the panel, I recreate the ButtonSelectWidget each time, but that also had the same problem. Am I doing something wrong, or have I uncovered a bug in OOUI? Thanks, Huji

3 3

Discovery Weekly Update for the week starting 2019-04-08
by Chris Koerner 15 Apr '19

15 Apr '19

Greetings, This is the weekly update from the Search Platform team for the week starting 2019-04-08. As always, feedback and questions are welcome. == Discussions == === Search === * New WikibaseCirrusSearch code is deployed and enabled on all wikis, including Wikidata & Commons. [0] *We re-indexed all Greek, Turkish, and Irish-language wikis with better handling of Greek accents [1], Turkish İ/ı [2], and Irish initial mutation [3] when lowercasing searches in quotes. [4] * We noticed that indices can move to readonly state when disk space is low and needs to be reset manually once disk space is available again, so we made it a cookbook [5] * David wrote a patch to help with an exception from CirrusSearch/Sanity/Checker (cannot fetch ids from index) [6] * We fixed/finalized more things with the ES6 upgrade: ** Create checks that alerts on cirrussearch update lags [7] ** Elasticsearch 6: the classic similarity is deprecated [8] ** Setup elasticsearch on cloudelastic100[1-4] [9] ** Rack/setup/install cloudelastic100[1-4].eqiad.wmnet systems [10] * Erik converted mjolnir from KafkaRDD to direct kafka-python usage, because KafkaRDD in pyspark only supports the 0.8 api [11] === Wikidata Query Service === * Deployed patch to fix an issue in Blazegraph workbench [12] * Working on improving cache behavior of Updater [13] [0] https://phabricator.wikimedia.org/T218954 [1] https://en.wikipedia.org/wiki/Greek_diacritics#Accents [2] https://en.wikipedia.org/wiki/Dotted_and_dotless_I [3] https://en.wikipedia.org/wiki/Irish_initial_mutations [4] https://phabricator.wikimedia.org/T217806 [5] https://phabricator.wikimedia.org/T219799 [6] https://phabricator.wikimedia.org/T218945 [7] https://phabricator.wikimedia.org/T219601 [8] https://phabricator.wikimedia.org/T219268 [9] https://phabricator.wikimedia.org/T214921 [10] https://phabricator.wikimedia.org/T194186 [11] https://phabricator.wikimedia.org/T219932 [12] https://phabricator.wikimedia.org/T219406 [13] https://phabricator.wikimedia.org/T217897 ---- 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 (he/him) Community Relations Specialist Wikimedia Foundation

1 0

Call for hosts: Wikimedia Hackathon 2020
by Rachel Farrand 15 Apr '19

15 Apr '19

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

1 0

Improving the mediawiki.org frontpage: It's available!
by Andre Klapper 15 Apr '19

15 Apr '19

Hi everybody, https://www.mediawiki.org has a new frontpage! Thank you to everyone who provided great feedback and comments on https://www.mediawiki.org/wiki/Talk:MediaWiki/Homepage_improvements_2018 and https://www.mediawiki.org/wiki/Talk:MediaWiki/Homepage_improvements_2018/Pr… in the last weeks! Several improvements have been implemented before going live. For a list of potential future work on problems with related pages, see https://www.mediawiki.org/wiki/MediaWiki/Homepage_improvements_2018#Potenti… Enjoy! andre (This email is a follow-up to the previous three announcements: https://lists.wikimedia.org/pipermail/wikitech-l/2018-September/090886.html https://lists.wikimedia.org/pipermail/wikitech-l/2018-December/091213.html https://lists.wikimedia.org/pipermail/wikitech-l/2019-March/091814.html ) -- Andre Klapper | Bugwrangler / Developer Advocate https://blogs.gnome.org/aklapper/

5 5

Code of conduct committee call for new members
by Amir Sarabadani 14 Apr '19

14 Apr '19

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 23th of April 2019, 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 a year; all applications are appreciated and will be carefully considered. The deadline for applications is end of day on 20th of April, 2019. 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

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