Wikitech-l May 2018

wikitech-l@lists.wikimedia.org

80 participants
83 discussions

MediaWiki-CodeSniffer 19.0.0 and 20.0.0 released
by Kunal Mehta 25 May '18

25 May '18

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Hello! With MediaWiki core now requiring PHP 7.0 or HHVM as the minimum version, CodeSniffer will now also require the same, and targets those versions as the minimum for the code it will be checking starting with version 20.0.0. 19.0.0 contains new sniffs and bug fixes, and is the last version to support PHP 5.5 and 5.6. I will have libraryupgrader upgrade all repositories directly to 20.0.0. If you want to continue to support older PHP versions in your project, upgrade your project to use 19.0.0 directly. libraryupgrader will skip projects using that version, since it means you explicitly want to support older PHP versions. Here's the changelog for 19.0.0: * Add break and continue to ParenthesesAroundKeywordSniff (Umherirrender ) * Check if the default of null is in the type list of @param (Umherirrender) * Do not enforce name for traits with phpunit annotations (Umherirrender ) * Don't allow 'iterable' type hint (Kunal Mehta) * Prevent usage of nullable and void type hints (Kunal Mehta) * Prohibit PHP's vanilla execution (Max Semenik) * Reorganize PHP 7.0 compatibility sniffs into a category (Kunal Mehta) And for 20.0.0: * Require PHP 7 or HHVM to run (Kunal Mehta) * Document why we still need to keep ScalarTypeHintUsageSniff (Kunal Mehta) * Drop PHP7UnicodeSyntaxSniff sniff (Kunal Mehta) - -- Legoktm -----BEGIN PGP SIGNATURE----- iQIzBAEBCgAdFiEE+h6fmkHn9DUCyl1jUvyOe+23/KIFAlsHy48ACgkQUvyOe+23 /KICmA/+OCzvr49gSu8VeB4+dQZR2qHp25rdShszsmsqr6iXKeObxUahLM0TcgtO 3x/TNCuT2uGnXrwVhzfqIglj0xs85niRx11tvCAm1rFPCMZKW8k1usA/s7nI5yQ4 3vnlkyZxhTKL+4VG0U0v2aMcQh8h+WhLyGqFZ9BW9CxzjZpxXuNJ/mP7KJtqaCZp EH/23gzf/fez1szV6ZIeh42Bv11HRxZBGpiJGnh7Vs5xKmwzfhUZQsvKBq5vBit0 +snbt+c4QpqZ9hEsa5vFqYQKDRj6EybuFlTLRmPYXScfm0udm+6h5EqCfuz2QdUB n88Cc/FApsgtUlve0LsOalpU/ePvEd3TPb33LU1mc/+bhBZs4j1E5mHlgmI28pWA 1UxuK8V5KP63ZcaWQsemU7vQ4wnS0PyPF+gabDxLmJNtW929AZe52mZxKq7lBO4K rUdqHoGZylmIM/etM5LLnEpZ2rNPL9+S+JAtFV/kke60F6VLVFgfDMIVH3phvj7t HrO2J+jq5eRQ8C4K1zvMXpyz1+vBtxma1yBsZMcrZZOlMaxoTjczWoLro3izBqs4 6BIZD4koEdtOJhcsz1GgnyaF6jGpWESirjwf9zRoruoZfGMrozEpvrk4SRiuHVoF PqBs9bSUJ+IjrzQZD4dtdBEcb1m6sZ6UlQhxJ+8TQ3ChnHIGM5I= =jP1N -----END PGP SIGNATURE-----

1 0

MediaWiki core master now requires PHP 7.0 or HHVM
by Kunal Mehta 25 May '18

25 May '18

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Hi, MediaWiki core's master branch now requires a minimum of PHP 7.0 or HHVM[1], as decided upon in the RfC. CI has been updated no longer run PHP 5.5 tests. There are already quite a few patches[2] to remove code that isn't necessary now, or start using new features :) But out of caution, we're waiting until after next week's Wikimedia train deploy before merging those to ensure it doesn't need to be reverted for any reason. It's important to remember that while nearly all of the new PHP 7.0 features can now be used, they still need to be supported in HHVM (with hhvm.php7.all disabled). Notably, this means that scalar type hints cannot be used. PHPCS should prevent those features from being used (more on that in a separate email). Thanks to everyone who made this finally happen, especially the Wikimedia Operations team :) - -- Legoktm [1] https://gerrit.wikimedia.org/r/#/c/405216/ [2] https://gerrit.wikimedia.org/r/#/q/topic:new-php -----BEGIN PGP SIGNATURE----- iQIzBAEBCgAdFiEE+h6fmkHn9DUCyl1jUvyOe+23/KIFAlsHydgACgkQUvyOe+23 /KJvEBAAj3ljVLOuSQitaB+6xakUTlZZpkcjRLyrbJ8KbfxyycB94pzlZ4fRdqHY nBnrokrawqQqgVEai9hq7nfVngWYH2eC11dhIXrpj2oklxswVaOxxwhPF92SJ9IP cuDawz9v6sqgMKDnQmHmTkpNmsWzez4d7LZMPW6UHKSGBl48ZZc5ZiTYlFyBKeLB BY5CNHY41flx21Z+BTQBQ2+tZ/Fm2kv6tAgI9gj8wpS5lviq1bhO+AH2/7qEcpjm LHZTcvrxHgctgU8XbEWXeGbNKK9/JUyuHApiDcgSXi81qGRHgaUytmYunXNQmsP8 51GzpGBL8R7YVP6uPFeYEcEJgvFAFa+xyeGHjDtTNniUj5co3eVixWvD668jCFc9 Lfd4O73vNMQluksNw81DEZQ5Pt+MMhA1DMqmAw+rwRYVdunfbumhh1uze03nJuCj Pk386sJkXVmawbc8PV9U8tnUoNIY+ngdzjl0ivOGwlxRpt30Usv0XxiA2i1R9IUU +BNGETmgpRg9i7cA4yqYGeOUeiYQhh4PHQeKIURp0M7BHChYsRCUqg6+blSNRqf4 TXpwIzAZ7Y3DjCxJLmn2zF1wHu5qSF20Af+hCf6A3WzYrnULGe2UtAk2BdOpJJ7h zgtG/lLuQPHCXxAfrP8gkVtfkTL+LGD1ZZm+AGlpDWYNNnB5pqE= =Xzun -----END PGP SIGNATURE-----

1 0

Today: Technical Advice IRC Meeting
by Michael Schönitzer 23 May '18

23 May '18

Sorry for cross-posting! Reminder: Technical Advice IRC meeting again **today, 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

TechCom Radar 2018-05-19
by Kate Chapman 21 May '18

21 May '18

Hi All, Here are the minutes from this week's TechCom meeting: TechCom held a public meeting at the Hackathon in Barcelona. These minutes are the result of that meeting. * Detailed Meeting Notes: <https://etherpad.wikimedia.org/p/wmhack2018-techcom> * No public IRC RFC meeting on 2018-05-23 * No internal TechCom meeting on 2018-05-23 * There is a request for feedback on the future of extension management (not an official TechCom RFC yet, but is being monitored) <https://www.mediawiki.org/wiki/Requests_for_comment/Extension_management_fe…> * Held a public discussion of TechCom’s Platform Architecture Principles <https://www.mediawiki.org/wiki/Wikimedia_Technical_Committee/MediaWiki_Plat…> Notes: <https://www.mediawiki.org/wiki/Wikimedia_Technical_Committee/MediaWiki_Plat…> * TechCom-RFC Inbox was empty so no new RFCs were triaged: <https://phabricator.wikimedia.org/tag/techcom-rfc/> 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)

1 0

Wiki Dialogue Systems
by Adam Sobieski 21 May '18

21 May '18

INTRODUCTION Some technical topics are broached toward the crowdsourcing of dialogue system content and behavior. COLLABORATIVE AUTHORING The content and behavior of a dialogue system can be represented in a number of ways. Firstly, the content and behavior of a dialogue system can be represented in programming language source code files. Collaborative authoring, in this case, is a matter of integrated development environments and source code repositories, version control systems. Secondly, some or all of the content and behavior of a dialogue system can be separated from the source code files as data stored in some data format or in a database. Collaborative authoring, in this case, could require custom software tools. Thirdly, a number of services, cognitive services, can encapsulate the content and behavior of a dialogue system. Collaborative authoring, in this case, could require utilization of such services or related user interfaces. Fourthly, the content and behavior of a dialogue system can be represented as a set of interrelated, URL-addressable, editable pages. Servers can provide content for a number of different content types, for example hypertext for content authors and other formats for dialogue system user agents. Server-side scripting can be utilized to generate pages and generated pages can contain client-side scripting. Fifthly, the content and behavior of a dialogue system can be represented as a set of interrelated, URL-addressable, editable diagrams. Sixthly, the content and behavior of a dialogue system can be represented in transcript form. Transcript-based user interfaces may resemble instant messaging applications, scrollable sequences of speech bubbles, with speech bubbles coming from the left and right sides, such that users can edit the content in dialogue systems’ speech bubbles. Users could opt to view more than plain text in speech bubbles. There could also be vertical, colored bands in one or both margins, visually indicating discourse behaviors, moves, objectives or plans which span one or multiple utterances. COLLABORATIVE DEBUGGING Debugging dialogue systems is an important topic. Debugging scenarios include switching from interactions with dialogue systems to authoring processes such that dialogue context data is preserved. NATURAL LANGUAGE GENERATION AND UNDERSTANDING Natural language generation can produce editable structured documents from the data stored in databases and knowledgebases. Generated content can contain, beyond natural language, data and program logic to facilitate the processing of constrained or unconstrained edits. Edits to generated content can result in changes to stored data. COMPUTER-AIDED WRITING Computer-aided writing can convenience content authors and assure quality. Software can, generally speaking, provide users with information, warnings and errors with regard to tentative edits. Software can support users including with regard to their spelling, grammar, word selection, readability, text coherence and cohesion. Software can measure the neutral point of view of natural language. Software can also process tentative edits with regard to their logical consistency with respect to data stored in databases and knowledgebases. WIKI DIALOGUE SYSTEMS Exploration into the collaborative authoring and debugging of dialogue systems could result in new wiki technologies. Wiki dialogue systems could resemble spoken language dialogue systems with transcript-based user interfaces, users able to easily switch between dialogue-based interactions and the editing of dialogue system content and behavior. Best regards, Adam Sobieski http://www.phoster.com/contents/

1 0

[mediawiki/core CR request] Translate special pages into Gorontalo
by Martin Urbanec 20 May '18

20 May '18

Hello all, I'd like to request CR+2 of https://gerrit.wikimedia.org/r/#/c/428915/, which is translating special pages into Gorontalo. Thanks in advance, Martin

1 0

Download a wiki?
by Bart Humphries 20 May '18

20 May '18

We have a very old wiki which has basically never been updated for the past decade and which was proving stubbornly resistant to updating several years ago. And now the owner of the server has drifted away, but we do still have control over the domain name itself. The best way that we can think of to update everything is to scrape all of the pages/file, add them to a brand new updated wiki on a new server, then point the domain to that new server. Yes, user accounts will be broken, but we feel that this is the most feasible solution unless someone else has another idea. However, there's a lot of pages on meritbadge.org -- which is the wiki I'm talking about. Any suggestions for how to automate this scraping process? I can scrape the HTML off every page, but what I really want is to get the wikitext off of every page. Bart Humphries bart.humphries(a)gmail.com (909)529-BART(2278)

4 4

⠠⠺⠓⠁⠞⠄⠎ ⠍⠁⠅⠊⠝⠛ ⠽⠕⠥ ⠓⠁⠏⠏⠽ ⠞⠓⠊⠎ ⠺⠑⠑⠅⠦ / What's making you happy this week? (Week of 20 May 2018)
by Pine W 20 May '18

20 May '18

*Between the Brackets* Yaron Koren produced a 30 minute digest of previous episodes of this podcast. Much of the episode will be understandable by people who are not developers but are familiar with how MediaWiki works. I enjoyed listening to this: https://betweenthebrackets.libsyn.com/episode-8-btb-digest-1 *WMF awards of Project Grants and Rapid Grants* * Nine Rapid Grants, with maximum amounts of $2000 each, were awarded to promote readership: https://blog.wikimedia.org/2018/05/16/rapid-grants-awarded/ * Eleven Project Grants, totaling $354,654, were awarded for diverse projects: https://lists.wikimedia.org/pipermail/wikimedia-l/2018-May/090291.html. There will be a Project Showcase video meeting on June 14. *Reports from Wikimedia Conference 2018 participants* I especially appreciated this detailed report from Peaceray and Joe Mabel which mentions a wide range of subjects including Structured Data on Commons, Learning Days, possible ways to incorporate more diverse citations into Wikipedia, lightning talks, libraries and partnerships, and general thoughts about the conference: https://meta.wikimedia.org/wiki/Cascadia_Wikimedians/2018_Wikimedia_Confere…. Conference reports are currently available in English, Thai, French, Ukrainian, Latvian, German, and Polish: https://meta.wikimedia.org/wiki/Wikimedia_Conference_2018/Further_reports. *Report from the Wikimedia Conference 2018 Strategy Track* Significant good-faith effort appears to be invested in the strategy process: https://meta.wikimedia.org/wiki/Wikimedia_Conference_2018/Documentation/Mov… What's making you happy this week? You are welcome to comment in any language. Pine ( https://meta.wikimedia.org/wiki/User:Pine )

1 0

PHPUnit 6+ on older versions of MW
by Jeroen De Dauw 17 May '18

17 May '18

Hey, I updated one of my extensions to use PHPUnit 6+ and am having troubles getting the tests to run with older versions of MediaWiki. In particular, I'd like my tests to run with MW 1.27. I suspect this is somehow possible and has already been done in other extensions. Cheers -- Jeroen De Dauw | https://entropywins.wtf | https://keybase.io/jeroendedauw Software Crafter | Speaker | Student | Strategist | Contributor to Wikimedia and Open Source ~=[,,_,,]:3

2 3

Provide input on the future direction of MediaWiki's extension management system
by Kunal Mehta 17 May '18

17 May '18

Hi everyone, As part of the MediaWiki Platform Team's goal to develop a roadmap for MediaWiki, we want to solicit input on the future direction of MediaWiki's extension management system. One of MediaWiki's greatest strengths is the diverse extension ecosystem. But navigating that ecosystem and managing those extensions can be difficult and cumbersome. Please provide input on what features you'd like to see at: <https://www.mediawiki.org/wiki/Requests_for_comment/Extension_management_fe…>. You can suggest a specific feature, or endorse and comment on other people's proposals. I've put down a few proposal to help start the discussion, but I'm sure that everyone has plenty more :-). The goal will be to collate the input provided there, and use it to plan future development work on improving extension management. If you know other people who use MediaWiki and have valuable opinions, please let them know about the RfC. Thanks, Kunal / Legoktm

1 0

← Newer
1
2
3
4
5
6
7
8
9
Older →

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