Wikitech-l January 2019

wikitech-l@lists.wikimedia.org

79 participants
75 discussions

Upcoming Search Platform Office Hours—January 9th
by Trey Jones 09 Jan '19

09 Jan '19

The Search Platform Team <https://www.mediawiki.org/wiki/Wikimedia_Search_Platform> usually holds office hours the first Wednesday of each month—but since this month that would have been Jan 2nd, we’ve delayed for a week. Come ask us anything about Wikimedia search! We’re particularly interested in: * Opportunities for collaboration—internally or externally to the Wikimedia Foundation * Challenges you have with on-wiki search, in any of the languages we support But we're happy to talk about anything search-related. Feel free to add your items to the Etherpad Agenda for the next meeting. Details for our next meeting: Date: Wednesday, December 9th, 2018 Time: 16:00-17:00 GMT / 08:00-9:00 PST / 11:00-12:00 EST / 17:00-18:00 CET Etherpad: https://etherpad.wikimedia.org/p/Search_Platform_Office_Hours Google Meet link: https://meet.google.com/vyc-jvgq-dww *N.B.:* Google Meet System Requirements <https://support.google.com/meet/answer/7317473> —Trey Trey Jones Sr. Software Engineer, Search Platform Wikimedia Foundation

1 1

Jenkins is broken on master mediawiki core and extensions
by Amir Sarabadani 09 Jan '19

09 Jan '19

Hello, Due to an issue in stylelint library, all patches now fail on npm tests. The reason is one of dependencies of stylelint is broken so there is not much we can do until the new release gets picked up by npm registry. Sorry for any inconvenience, and for more information see https://phabricator.wikimedia.org/T213249 Best -- Amir Sarabadani Software Engineer 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/029/42207.

1 1

Thank you Tuesday
by Derick N. Alangi 08 Jan '19

08 Jan '19

Hello Everyone, I'm starting today's "Thank you Tuesday" thread with a big Merry Christmas to all Wikimedia Developers. Wikimedia Developers are just awesome and they have a way of doing with things (Computers + MediaWiki = Wikipedia). I want to thank all developers in the movement that have helped me become better at my contributions to MediaWiki and other related Wikimedia projects. A short list below; Legoktm, Reedy, Pmiazga, Jdlrobson, Thiemo_WMDE, Bawolff, Jdforrester, Krinkle, Matmarex, Volker_E, Sklaporte, Hoo, Lydia_WMDE, Nikerabbit, Aklapper, Xqt, Framawiki, QuimGil, Apergos, Amire80, BryanDavis and MaxSem + the *entire* Wikimedia developer community. See, the list is so long as over time, I've worked with developers that have in one way or another shaped my way of doing things in the Wikimedia movement. The list above is just a short list and I want to take today to thank all of them for their awesomeness and for helping people get better at writing code in Wikimedia. You are all awesome and I love you all! Enjoy your Christmas / Holidays <3. Who do you want to thank on this special day? *--* *Derick*

3 2

Changes to the Block paradigm
by Moriel Schottlender 08 Jan '19

08 Jan '19

Greetings, Have you written code that deals with or depends on user blocks? Read on. = TL;DR: = The new “Partial Blocks” feature has fundamentally changed the way MediaWiki considers what “block” means; any code that handles blocks should consider whether the questions it is asking are still valid or should adjust its expectations. Please read for more details. = Preamble = A couple of months ago, as part of the Anti Harassment Tools team’s continued work on improving the general experience of our users and providing more robust tools to administrators, an RFC to enable “Partial Blocks[1]” has passed and has been implemented in MediaWiki, affecting the way blocking users operates. While the actual feature, enabling the blocking of users for specific pages and namespaces, will be slowly rolled out as part of our rollout and testing plans, the change has resulted in a complete change of paradigm for what “block” means throughout our code. = Change of paradigm = Until recently, Block was fairly straight forward; whether a block was done on an IP range or a specific user, the question the code would ask is “is the user blocked from this action” and the answer will be a boolean yes or no, depending on whether the user was blocked from the wiki and whether the action was a blockable action. With the new Partial Blocks feature, that question is now more elaborate. We are giving admins and wikis in general much more robust options when deciding to block IPs or users. “Sitewide” block is no longer the only option. Now, a user can be blocked from editing a specific page, and soon from a specific namespace. There are also blocks that prevent a specific action, such as uploading files or creating new pages. This means that the question “is the user blocked” is no longer accurate. In most cases, the question should be “is the user blocked from the action on this page”, because users may receive a block that is not sitewide, but from a specific page or set of pages. = What we worked on = The Anti Harassment Tools team has been working diligently on making sure that the new blocking behavior does not produce obvious regressions in production, and does not add to any still existing inconsistencies. In cases where we identified a clear mismatch, we’ve tried to either fix it outright or alert the code owners to adjust. If we have missed any iteration or use-case, please open a Phabricator ticket and add the ‘anti-harassment’[2] tag to it. If the use-case is sensitive or identifies a current loop-hole in the way blocks work, please make it a security ticket and alert us and the relevant team immediately. = General steps forward = While the team is following up on making the code clear and robust and fixing what we’ve identified as paradigm-changes to deal with, there are still many instances where the changes required to the code are not straight-forward or clear. Some extensions ask whether a user is blocked and may need to change the way that the product’s “business logic” behaves. These are cases where we cannot make the decision for the codebase. We encourage you to look at your product and consider adjusting if necessary. = General guidance = We’ve identified some areas that may help code owners adjust their products to properly take advantage of the new feature and adjust to the new paradigm change. This list is not exhaustive, but may help you spot areas in your code that can easily be changed: * User::isBlocked() has changed its meaning, and its use cases should be re-examined depending on what your code intends to check. For the most part, if there’s a Title object available, User::isBlockedFrom() is a good option. Otherwise, consider using User::getBlock() and Block::isSitewide() * Block::prevents( ‘edit’ ) is an operation that doesn’t make sense anymore, because a block on the ‘edit’ action now depends on context (the title). * Determining whether a block prevents a user from editing their own user talk page has changed. For a sitewide block, if the $wgBlockAllowsUTEdit config is false, then the block prevents the user editing their user talk page, but if it is true, then whether they can edit their user talk page depends on the ipb_allow_usertalk flag on the block. For a partial block to a page or pages, these flags are not taken into account: if the user’s talk page is specified as a blocked page, then they cannot edit their user talk page; if it is not, then they can edit it. Block::prevents( ‘editownuserpage’ ) should therefore not be checked for a partial page block[3]. We plan to deprecate that parameter officially, please consider if this affects your code. * Please check that any classes that extend Action or FormSpecialPage return the correct value for requiresUnblock(). To summarize, in general, the meaning of asking whether a block exists has changed, and any code piece that needs this information should adjust itself to account for partial blocks, depending on its goals. Thank you, Moriel, on behalf of the Anti Harassment Tools Team References: [1] Partial blocks: https://meta.wikimedia.org/wiki/Community_health_initiative/Per-user_page,_… [2] Anti Harassment tools board: https://phabricator.wikimedia.org/project/view/2660/ [3] For a discussion of this, see: https://phabricator.wikimedia.org/T210475 -- Moriel Schottlender (she/her) Senior Software Engineer, Tech Lead Community Tech and Anti Harassment Tools @mooeypoo (IRC / Phabricator)

2 2

Wikimedia Hackathon 2019: Registration Open!
by Rachel Farrand 07 Jan '19

07 Jan '19

On behalf of Wikimedia Czech Republic and the Wikimedia Foundation Community Relations team we are please to announce that registration for the Wikimedia Hackathon 2019 <https://www.mediawiki.org/wiki/Wikimedia_Hackathon_2019/Register_and_Attend> is now open for both scholarships and regular attendees! The hackathon will be held at the Czech National Library of Technology <https://en.wikipedia.org/wiki/Czech_National_Library_of_Technology> in Prague, CZ between 17-19 May 2019. We have identified three focus areas <https://www.mediawiki.org/wiki/Wikimedia_Hackathon_2019/Program> for the event which we will continue to refine and clarify over the next months. We welcome your suggestions and collaboration on additional focus areas or larger projects and as usual welcome participants who plan to work on or learn about any project that they like related to any area of Wikimedia Technology. If you have any questions or comments please contact: *hackathon(a)wikimedia.cz <hackathon(a)wikimedia.cz>* Otherwise, please continue to follow our program and organizational developments on Wikimedia Hackathon 2019 on Mediawiki <https://www.mediawiki.org/wiki/Wikimedia_Hackathon_2019>. Please help us by forwarding this email to relevant lists! -- Rachel Farrand Events Program Manager Technical Collaboration Team Wikimedia Foundation

1 1

Community Consensus to apply some colour to PolyGerrit's header
by Paladox 07 Jan '19

07 Jan '19

Hi, if you like the header from ( https://gerrit-new.wmflabs.org/r/q/status:open ) and would like it applied to https://gerrit.wikimedia.org/r/ please +1 https://gerrit.wikimedia.org/r/c/operations/puppet/+/482379/ Community consensus is required before it can be merged.

1 0

blocking - unblocking, wikivoyage
by 80hnhtv4agou＠bk.ru 07 Jan '19

07 Jan '19

I do not see what community this is being controlled by; 1. there is no notice boards, or request for administrators, etc.. 2. there is no arbitration commity to go to, etc.. 3. there are no rules on who may be blocked. 4. there is no unblocking feature, and yet there is a review page. https://en.wikivoyage.org/wiki/Category:Requests_for_unblock 5. there is nothing in place to punish administrators that abuse there blocking powers etc.. 6. there is no active user talk page to request an unblock.

2 1

MediaWiki 1.32.0-rc.2 is ready for testing
by Mukunda Modell 05 Jan '19

05 Jan '19

Links to the archives, signatures and keys relevant to this release are at the end of this message. There have been some changes[1] since the previous release candidate. Unfortunately, I didn't manage to get a viable rc.2 built before the holiday break, however, I don't currently anticipate further delays. As of today, all known release critical bugs are resolved on the 1.32 branch. With a fair amount of confidence I expect to release 1.32.0 final sometime next week. Warning: This is not a final release and should not be used for production websites. Known issues are tracked in Phabricator on the release work-board[1]. As always please do try out the release candidate in a test environment and report any issues that you discover. Please use the #MW-1.32-Release[2] tag in Phabricator when reporting issues specific to this release. ********************************************************************** Download: https://releases.wikimedia.org/mediawiki/1.32/mediawiki-1.32.0-rc.2.tar.gz Download without bundled extensions: https://releases.wikimedia.org/mediawiki/1.32/mediawiki-core-1.32.0-rc.2.ta… Patch to previous version (1.32.0-rc.1): https://releases.wikimedia.org/mediawiki/1.32/mediawiki-1.32.0-rc.2.patch.gz GPG signatures: https://releases.wikimedia.org/mediawiki/1.32/mediawiki-core-1.32.0-rc.2.ta… https://releases.wikimedia.org/mediawiki/1.32/mediawiki-1.32.0-rc.2.tar.gz.… https://releases.wikimedia.org/mediawiki/1.32/mediawiki-1.32.0-rc.2.patch.g… Public keys: https://www.mediawiki.org/keys/keys.html [1] https://phabricator.wikimedia.org/source/mediawiki/compare/?head=1.32.0-rc.… [2] https://phabricator.wikimedia.org/project/board/3306/ [3] https://phabricator.wikimedia.org/maniphest/task/edit/form/1/?tags=MW-1.32- Release

2 1

Patchsets by new Gerrit contributors waiting for code review and/or merge
by Andre Klapper 03 Jan '19

03 Jan '19

CR0: Please review and provide guidance if you are familiar with the code, and decide (CR±1 or CR±2): * https://gerrit.wikimedia.org/r/#/c/mediawiki/core/+/462155/ ** Adds alternative file icon paths ** 2018-October-14 ** Maintainers/Stewards: MediaWiki Platform team? * https://gerrit.wikimedia.org/r/#/c/avro-php/+/466838/ ** Convert Avro-PHP to PSR-Compliant Project ** 2018-October-18 ** Maintainers/Stewards: Analytics / Discovery (?) * https://gerrit.wikimedia.org/r/#/c/mediawiki/skins/Material/+/471766/ ** Add scrollbar:: to view more content on sidebar ** 2018-November-06 ** Maintainers/Stewards: ??? * https://gerrit.wikimedia.org/r/#/c/mediawiki/core/+/472758/ ** Added Id to the input box ** 2018-November-10 ** Maintainers/Stewards: MediaWiki Platform team? * https://gerrit.wikimedia.org/r/#/c/mediawiki/core/+/474769/ ** Add Special:CategoriesToEmpty ** 2018-November-20 ** Maintainers/Stewards: MediaWiki Platform team? * https://gerrit.wikimedia.org/r/#/c/mediawiki/core/+/472184/ ** Avoid hitting DB in Category getters when they have the required info ** 2018-November-23 ** Maintainers/Stewards: MediaWiki Platform team? * https://gerrit.wikimedia.org/r/#/c/operations/mediawiki-config/+/478498/ ** Upload HD logos for several projects ** 2018-December-12 ** Maintainers/Stewards: ??? * https://gerrit.wikimedia.org/r/#/c/wikimedia/fundraising/crm/+/479533/ ** Update ctools to 1.1.4 ** 2018-December-13 ** Maintainers/Stewards: Fundraising Tech * https://gerrit.wikimedia.org/r/#/c/mediawiki/extensions/Cargo/+/480039/ ** Added new feature: order virtual fields by the order they inserted to list on cargo store ** 2018-December-17 ** Maintainers/Stewards: ??? * https://gerrit.wikimedia.org/r/#/c/mediawiki/extensions/Echo/+/471910/ ** Test: notify a new user with welcome message ** 2018-December-17 ** Maintainers/Stewards: Growth team * https://gerrit.wikimedia.org/r/#/c/mediawiki/core/+/481313/ ** Allow TOC to "duplicate" existing anchors in MediaWiki ** 2018-December-25 ** Maintainers/Stewards: MediaWiki Platform team? CR+1: Please help make a decision (CR±1, CR±2) on these CR+1 patches: * https://gerrit.wikimedia.org/r/#/c/mediawiki/extensions/PluggableAuth/+/468… ** Adding separate option for local API login ** 2018-October-20 ** Maintainers/Stewards: ??? Read https://www.mediawiki.org/wiki/Gerrit/Code_review#By_project how you can get notified of new patches in your code areas of interest. Thanks in advance for your reviews! Of last time's 10 listed patches, 3 got abandoned by Zfilipin, Jforrester, Sbassett. Maintainers/Stewards data taken from https://www.mediawiki.org/wiki/Developers/Maintainers CR0 source: https://gerrit.wikimedia.org/r/#/q/ownerin:newcomers+status:open+label:Veri… CR+1 source: https://gerrit.wikimedia.org/r/#/q/ownerin:newcomers+status:open+label:Veri… -- Andre Klapper | Bugwrangler / Developer Advocate https://blogs.gnome.org/aklapper/

1 0

TechCom Radar 2019-01-02
by Kate Chapman 03 Jan '19

03 Jan '19

Hi All, Here are the minutes from this week's TechCom meeting: * Had initial discussion of RFC: MediaWiki 2018 extension interfaces <https://phabricator.wikimedia.org/T212482> this RFC comes out of a TechConf session and aims to make official supported and recommended interfaces. * No Public IRC meeting this week * No Public IRC meeting next week 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

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