Wikitech-l August 2018

wikitech-l@lists.wikimedia.org

101 participants
90 discussions

Fwd: Wikimedia Foundation Readers Roadmap Review - 27 August 2018

by Adam Baso

Cross-post. ---------- Forwarded message --------- From: Adam Baso <abaso(a)wikimedia.org> Date: Tue, Aug 28, 2018 at 9:31 AM Subject: Re: Wikimedia Foundation Readers Roadmap Review - 27 August 2018 To: <wikitech-ambassadors(a)lists.wikimedia.org> And here are the MP3 and WebM on Commons of the Readers Roadmap Review from yesterday. http://commons.wikimedia.org/wiki/File:Readers_Roadmap_Review_-_2018-08-27.… https://commons.wikimedia.org/wiki/File:Wikimedia_Foundation_Readers_Roadma… On Mon, Aug 27, 2018 at 4:19 PM Adam Baso <abaso(a)wikimedia.org> wrote: > Hello - > > We recorded a roadmap review this morning for the Wikimedia Foundation's > Readers team. This covers material about efforts on the web, native apps, > multimedia, infrastructure, and parsing. Enjoy! > > YouTube* > https://www.youtube.com/watch?v=MZeL0rBDJ3s&t=20 > > PDF > > https://commons.wikimedia.org/wiki/File:Wikimedia_Foundation_Readers_Roadma… > > As a reminder, you can find our department (Audiences) annual plan on Meta: > > > https://meta.wikimedia.org/wiki/Wikimedia_Foundation_Annual_Plan/2018-2019/… > . > > Thanks! > > Adam Baso > Engineering Director > Wikimedia Foundation - Readers > > * I'm converting the video for WebM VP9 on Commons as well. >

5 years, 7 months

The yellow line

by יגאל חיטרון

Hello. Does anybody know which patch removed the preference "turn off the yellow message for new edits of your talk page", and why? Thank you.

5 years, 7 months

Discovery Weekly Update for the week starting 2018-08-20

by Chris Koerner

Hello, This is the weekly update from the Search Platform team for the week starting 2018-08-20. As always, feedback and questions welcome. == Discussions == === Search === * Gehel did a lot of work on getting the servers ready for ElasticSearch 6: resolving a deprecated data directory structure [0], migrating from Jessie to Stretch [1], and migrating the cirrus cluster to RAID0 [2] * Erik and Gehel fixed an issue where the mjolnir-kafka-bulk-daemon was failing on all elastic / eqiad nodes [3] * Erik also added stats collection for observability of mjolnir daemons using prometheus [4] * We had an issue where the warning message was not very informative when doing a search with greater than 10,000 results; Erik updated the warning to now read: "''A warning has occured while searching: Could not retrieve results. Up to 10000 search results are supported, but results starting at 10000 were requested.''" [5] * When the ElasticSearch server went down recently, there were various PHP notices spamming the logs. Erik was able to fix this by better handling the null result from link count msearch [6] * Trey worked on creating and merging, a Esperanto Elasticsearch plugin using Esperanto morphological libraries [7] * Stas worked on a enabling indexing all entity-valued statements [8] which is now enabled for newly edited items and will be added to all items on next reindex [9] === WDQS === * Stas has fixed some bugs in categories daily RDF diffs generation [10] and wrote puppet recipies to enable auto-loading them on WDQS servers. Switch from weekly to daily loading to start on Monday 27th. ---- [0] https://phabricator.wikimedia.org/T199389 [1] https://phabricator.wikimedia.org/T193649 [2] https://phabricator.wikimedia.org/T198391 [3] https://phabricator.wikimedia.org/T202120 [4] https://phabricator.wikimedia.org/T201948 [5] https://phabricator.wikimedia.org/T201360 [6] https://phabricator.wikimedia.org/T105887 [7] https://phabricator.wikimedia.org/T200099 [8] https://phabricator.wikimedia.org/T199884 [9] https://phabricator.wikimedia.org/T147505 [10] https://phabricator.wikimedia.org/T201216 ---- 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 Community Relations Specialist Wikimedia Foundation

5 years, 7 months

Fwd: Wikimedia Foundation Readers Roadmap Review - 27 August 2018

by Adam Baso

Cross-post. ---------- Forwarded message --------- From: Adam Baso <abaso(a)wikimedia.org> Date: Mon, Aug 27, 2018 at 4:19 PM Subject: Wikimedia Foundation Readers Roadmap Review - 27 August 2018 To: <wikitech-ambassadors(a)lists.wikimedia.org> Hello - We recorded a roadmap review this morning for the Wikimedia Foundation's Readers team. This covers material about efforts on the web, native apps, multimedia, infrastructure, and parsing. Enjoy! YouTube* https://www.youtube.com/watch?v=MZeL0rBDJ3s&t=20 PDF https://commons.wikimedia.org/wiki/File:Wikimedia_Foundation_Readers_Roadma… As a reminder, you can find our department (Audiences) annual plan on Meta: https://meta.wikimedia.org/wiki/Wikimedia_Foundation_Annual_Plan/2018-2019/… . Thanks! Adam Baso Engineering Director Wikimedia Foundation - Readers * I'm converting the video for WebM VP9 on Commons as well.

5 years, 7 months

Breaking change in ORES API: "wp10" models are renamed to "articlequality"

by Amir Sarabadani

Hello, If you don't use ORES API, please ignore this email. If you are using wp10 models in your tool, gadget, or research, please note that these models are now renamed to "articlequality" to better reflect what they are (in comparison to "editquality"). articlequality models are deployed on English, Russian, French, Persian, Turkish, and Basque Wikipedia languages. So URLs like this: https://ores.wikimedia.org/v3/scores/enwiki/855137823/wp10 Need to be changed to something like this: https://ores.wikimedia.org/v3/scores/enwiki/855137823/articlequality Same goes with parsing the results. The "wp10" still exists as an alias and if you don't determine models (meaning you want scores for all models) we respond with wp10 and articlequality data duplicated [1] but we might pull the plug after four weeks after this announcement. [1]: For example see: https://ores.wikimedia.org/v3/scores/enwiki/855137823 For more information see: https://phabricator.wikimedia.org/T196240 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.

5 years, 7 months

VPS users, please claim your projects (second notice)

by Andrew Bogott

In an attempt to identify abandoned VPS projects, I've created a wiki page that lists all existing projects, here: https://wikitech.wikimedia.org/wiki/Cloud_VPS_2018_Purge Currently 85 projects[2] on that list are unclaimed. If you are a VPS user, please visit that page and mark any projects that you use as {{Used}}. Note that it's not necessary for you to be a project admin to mark something -- if you know that you're currently using a resource and want to keep using it, go ahead and mark it accordingly. If you /are/ a project admin, please take a moment to mark which VMs are or aren't used in your projects. When October arrives, I will shut down and begin the process of reclaiming unused projects. If you think you use a VPS project but aren't sure which, I encourage you to poke around on https://tools.wmflabs.org/openstack-browser/ to see what looks familiar. You can also log in to http://horizon.wikimedia.org which will provide you with a handy menu of projects that you are currently a member of. Thank you! -Andrew and the WMCS team [1] https://phabricator.wikimedia.org/phame/post/view/112/neutron_is_finally_co… [2] Here, for good measure, is that list. Every one of these projects is currently a candidate for deletion: aicaptcha analytics bots chicotestproject ci-staging codereview collection-alt-renderer commonsarchive community-labs-monitoring contributors dashiki deep-learning-services discourse discourse-wam download etytree fastcci getstarted glampipe globaleducation hat-imagescalers hound iiab iiifls1 ircd jupyter kubernetes-testing maps maps-team math matrix mcr-dev mediahandler-tests mediawiki-docker multimedia mw-api-testing mw-extension-ids mwfuzz mwoffliner newsletter nonfreewiki openocr ores orig otrs pagemigration paws phlogiston piwik project-smtp rcm rdfiodev reading-lists reading-web-staging recommendation-api redirects reportcard sciencesource sentry services services-testbed t136871 test-twemproxy thumbor tor traffic twl utrs video wcdo wdq-mm wikibase-nearest-neighbors wikibrain wikidata-federation wikidata-page-banner wikidata-primary-sources-tool wikidumpparse wikifactmine wikimetrics wikisource-tools wikistream wikitolearn-dev wildcat wlmjudging wmf-research-tools

5 years, 7 months

Signature change without deprecation: ContentHandler::getUndoContent

by Gergo Tisza

https://gerrit.wikimedia.org/r/c/mediawiki/core/+/447099 changes the signature of ContentHandler::getUndoContent from <Revision, Revision, Revision> to <Revision|Content, Revision|Content, Revision|Content[, bool]> (with Revision soft-deprecated). This is a breaking change as ContentHandler is meant to be subclassed, and any subclass that typehints Revision will raise a warning at compile-time, and a fatal when called with Content. Searching Gerrit, Github and Google only yielded a single instance of a subclass overriding the method (which is being fixed) and providing backwards compatibility in a robust way does not seem feasible, so we are changing the method signature without a deprecation period (in the sense of subclass compatibility; with respect to calling the method with Revision, we follow the normal deprecation process). For more information on the MediaWiki deprecation policy see https://www.mediawiki.org/wiki/Deprecation_policy#Removal_without_deprecati…

5 years, 7 months

This Week's Log Health

by Tyler Cipriani

Hi all! The state of the Wikimedia error logs makes determining the health of a deployment difficult. This week there were a number of log messages that made determining the health of this week's train difficult. This email is a request for help for a couple of troubling messages currently showing up on our error logs; please help to investigate these log messages if you are able: * Exception thrown for failure to save settings appears ~ 1000 times/day[0] * "Falling back to DifferenceEngineSlotDiffRenderer" Logspam[1] Thank you for your help! <3 -- Tyler [0] <https://phabricator.wikimedia.org/T202149> [1] <https://phabricator.wikimedia.org/T202686>

5 years, 7 months

TechCom Radar 2018-08-22

by Kate Chapman

Hi All, Here are the minutes from this week's TechCom meeting: * Approved: RFC: Modern Event Platform - Choose Schema Tech <https://phabricator.wikimedia.org/T198256> * On Last Call (ending 5 September 2pm PST(21:00 UTC, 23:00 CET). RFC: Block users by page, namespace, and/or action (Partial Blocks) <https://phabricator.wikimedia.org/T199917> * Hosted an IRC discussion for: Introduce a new namespace for collaborative judgments about wiki entities <https://phabricator.wikimedia.org/T200297> * Minutes: <https://tools.wmflabs.org/meetbot/wikimedia-office/2018/wikimedia-office.20…> * Log: <https://tools.wmflabs.org/meetbot/wikimedia-office/2018/wikimedia-office.20…> * Accepted as a new RFC and will host IRC discussion on 29 August 2pm PST(21:00 UTC, 23:00 CET) in #wikimedia-office: RFC: Modern Event Platform: Schema Registry / Metadata Service <https://phabricator.wikimedia.org/T201643> This RFC outlines the current state of event schema registries and then options for where to go forward. The recommendation is to develop a new schema registry / metadata service. * Accepted as a new RFC and will be scheduling IRC meeting soon: ParallelMaintenance helper class for multi-process maintenance scripts <https://phabricator.wikimedia.org/T201970> this change would allow parallelizing of long running maintenance scripts. * Accepted as a new RFC and will be scheduling IRC meeting soon: RfC: Create a proper command-line runner for MediaWiki maintenance tasks <https://phabricator.wikimedia.org/T99268> this RFC proposes to create an organized structure and runner for running of maintenance tasks. * Accepted as a new RFC and will be scheduling IRC meeting soon: RFC: Modern Event Platform: Scalable Event Intake Service <https://phabricator.wikimedia.org/T201963> This RFC's goal is to decide if we should use something other than EventLogging/EventBus and lays out two possible options in addition to staying with the EventLogging/EventBus * Accepted as RFC, but needs more information prior to IRC meeting: Consolidate WikiPage action and special page systems <https://phabricator.wikimedia.org/T201967> originally brought up in 2011 this RFC seeks to unify the way that page actions are done. 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 TechCom Facilitator (Contractor)

5 years, 7 months

RFC Discussion Wednesday - new namespace for collaborative judgments about wiki entities

by Kate Chapman

Hi All, A reminder that TechCom is hosting a RFC discussion via IRC on Wednesday. Introduce a new namespace for collaborative judgments about wiki entities <https://phabricator.wikimedia.org/T200297> This meeting is to discuss the use of JADE to record the judgments and discuss concerns related to this approach. The meeting is scheduled for 22 August at 2pm PST(21:00 UTC, 23:00 CET) in #wikimedia-office If you haven't joined a #wikimediaoffice meeting before more information can be found here: <https://meta.wikimedia.org/wiki/IRC_office_hours#How_to_participate> More information regarding the TechCom RFC process is available here: https://www.mediawiki.org/wiki/Wikimedia_Technical_Committee/Processes#RFC_… Thanks, Kate -- Kate Chapman TechCom Facilitator (Contractor)

5 years, 8 months

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

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