Wikitech-l March 2019

wikitech-l@lists.wikimedia.org

94 participants
76 discussions

LDK Conference || 20.-22.5.19 || Leipzig University
by Sebastian Hellmann 27 Mar '19

27 Mar '19

Apologies for cross-posting ==== 2nd Language, Data and Knowledge (LDK) conference May 20-22, 2019 Leipzig, Germany ==== Call for Participation With the advent of digital technologies, language data becomes more and more valuable. In that context, we would like to draw your attention to the 2nd Language, Data and Knowledge (LDK) conference which will be held in Leipzig from May 20th till 22nd, 2019. This new biennial conference series aims at bringing together researchers from across disciplines concerned with language data in data science and knowledge-based applications. We invite practitioners, professionals, researchers and anyone with an interest in language data to be part of this event in Leipzig and catch up with the latest research outcomes in the areas of acquisition, provenance, representation, maintenance, usability, quality as well as legal, organizational and infrastructure aspects of language data. # Keynote Speakers We already have the following keynote speakers confirmed - Keynote #1: Christian Bizer, Mannheim University - Keynote #2: Christiane Fellbaum, Princeton University - Keynote #3: Eduard Werner, Leipzig University # Associated Events The following events are co-located with LDK 2019: 3rd Summer Datathon on Linguistic Linked Open Data (SD-LLOD-19) from May 12th to 17th, 2019 at the Leibniz Center for Informatics in Wadern, Germany Please find more information about the Datathon here: https://datathon2019.linguistic-lod.org/ Workshops on the 20th May 2019 - Translation Inference across Dictionaries (TIAD) - 3rd Workshop on Humanities in the Semantic web (WHiSe III) - 2nd OntoLex Face to Face Meeting Please find more information about the workshops here: http://2019.ldk-conf.org/co-located-events/ DBpedia Community Meeting on the 23rd May 2019 - 13th DBpedia Community Meeting https://wiki.dbpedia.org/meetings/Leipzig2019 Further information on the LDK program can be found here: http://2019.ldk-conf.org/events-programme/ To register and be part of the LDK conference and its associated events, please go to http://2019.ldk-conf.org/registration/. We are looking forward to meeting you in Leipzig. Kind regards Your LDK-Team

1 0

Wednesday: Technical Advice IRC Meeting
by Michael Schönitzer 27 Mar '19

27 Mar '19

Reminder: Technical Advice IRC meeting this week **(Wednesday) 4-5 pm UTC** on #wikimedia-tech. Question can be asked in English, German & Romanian. ⏰ Please note: due to summer time change this week will be the last meeting at 4 pm UTC. Beginning with next week the meeting will start at 3 pm! ⏰ The Technical Advice IRC Meeting is a weekly support event for volunteer developers. Every Wednesday, two full-time developers are available to help you with all your questions about Mediawiki, gadgets, tools and more! 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 the Technical Advice IRC Meeting crew) -- Michael F. Schönitzer Wikimedia Deutschland e. V. | Tempelhofer Ufer 23-24 | 10963 Berlin Tel. (030) 219 158 26-0 https://wikimedia.de Unsere Vision ist eine Welt, in der alle Menschen am Wissens der Menschheit teilhaben, es nutzen und mehren können. Helfen Sie uns dabei! https://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 0

Coming soon: an option to add a confirmation prompt to your rollback links
by Johanna Strodt 26 Mar '19

26 Mar '19

//sorry for cross-posting This week’s train will add a new option to the user preferences: People with rollback rights can add a confirmation prompt to their rollback links, if they want to. While most people with rollback rights want to use them to revert vandalism quickly, some people prefer a confirmation prompt. Contributors from German Wikipedia have asked for this, because quite a lot of people on dewiki accidentally click on the rollback link, e.g. when they want to thank someone. But there are also people in other wikis who use various methods to prevent themselves from accidentally rolling back. Wikimedia Germany’s Technical Wishes team[1] has now built a confirmation prompt that works inline, like the thanks notification. - On German Wikipedia, the confirmation prompt for rollbacks will be activated as a default. Users who want to rollback quickly can turn it off individually in their user settings.[2] - In most wikis, this confirmation prompt will be switched off by default. In these wikis, you can turn it on individually if you want to. [3] The planned deployment date for the confirmation prompt is March 26-28 on all wikis except dewiki. Please see the project page for more information.[4] Feedback is always welcome on the central feedback page.[5] Best, Johanna for the Technical Wishes team [1] https://meta.wikimedia.org/wiki/WMDE_Technical_Wishes [2] https://de.wikipedia.org/wiki/Spezial:Einstellungen#mw-prefsection-rendering [3] e.g. https://en.wikipedia.org/wiki/Special:Preferences#mw-prefsection-rendering [4] https://meta.wikimedia.org/w/index.php?title=WMDE_Technical_Wishes/Rollback [5] https://meta.wikimedia.org/wiki/Talk:WMDE_Technical_Wishes/Rollback -- Project Manager Community Communications Technical Wishlist, Wikimedia Deutschland

1 0

Question to WMF: Backlog on bugs
by John Erling Blad 26 Mar '19

26 Mar '19

The backlog for bugs are pretty large (that is an understatement), even for bugs with know fixes and available patches. Is there any real plan to start fixing them? Shall I keep telling the community the bugs are "tracked"? /jeblad

25 86

Discovery Weekly Update for the week starting 2019-03-18
by Chris Koerner 26 Mar '19

26 Mar '19

Hello, This is the weekly update from the Search Platform team for the week starting 2019-03-18. As always, feedback and questions are welcome. == Discussions == === Search === * Nearly done with the upgrade to ElasticSearch v6: ** Upgrade relforge to elasticsearch 6.5.4 [0] ** Upgrade deployment-elastic* to 6.5.4 [1] ** Build wmf-elasticsearch-search-plugins.deb that supports elastic 6.5.4 [2] * There was a minor bug in not getting a search result for "garrett marquis" or "Garrett Marquis"; Erik investigated and found it was a minor html issue and corrected it. FYI, it will take ~8 weeks for all content across all wikis to be reindexed. [3] * As part of the work done to separate the CirrusSearch/Elastic specific code from Wikibase code base, Stas deployed WikibaseCirrusSearch in production and all searches are now running through it [4] === WDQS === * New Release of Blazegraph (2.1.5) is announced. We have released 0.3.1 version of WDQS build with it. [5] [0] https://phabricator.wikimedia.org/T218116 [1] https://phabricator.wikimedia.org/T218247 [2] https://phabricator.wikimedia.org/T199791 [3] https://phabricator.wikimedia.org/T218001 [4] https://phabricator.wikimedia.org/T218715 [5] https://phabricator.wikimedia.org/T218746 ---- 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

GSOC 2019
by Adarsh Jaiswal 25 Mar '19

25 Mar '19

Hi everyone, I am Adarsh Jasiwal, currently in 1st year B. Tech. CSE and i want to contribute into your Wikimedia Foundation. I know the basics of web development and have done some projects based on it. If you could possibly tell me how could I be of any help I will be very Happy to help. Thanks , Regards, Adarsh Jaiswal.

2 1

Temporary personal break from mailing lists
by Pine W 24 Mar '19

24 Mar '19

Hi mailing list colleagues, I'm not sure whether I should make this be public, but I tend to be a frequent participant on mailing lists so maybe sharing this would be good. I am taking a temporary break from participating on Wikimedia mailing lists. Recently I am finding myself frequently experiencing frustration in conversations on lists, and I am concerned that in my frustration I may write something that I later regret. Also, I would like to be a generally positive presence on the lists, and I think that a "reset" would be good. I will remain in the Wikiverse for the foreseeable future. I like Wikimedia's educational mission, and I like my current principal project. I will continue to be a list subscriber, and may occasionally read list discussions. Also, I will continue to read off list emails. Perhaps in a month or two I will resume participating on lists. Thanks for all that you do in support of the mission. The Wikiverse is amazing and I am grateful to be a small part of it. Pine ( https://meta.wikimedia.org/wiki/User:Pine )

1 0

Where should extension default preferences be specified?
by Thomas Eugene Bishop 24 Mar '19

24 Mar '19

There are two places the default value for an extension-specific preference can be specified: (1) DefaultUserOptions in extension.json (2) onGetPreferences (or whatever function hooks GetPreferences) in MyExtension.hooks.php Which is better? If you do it in both places, and the defaults are in conflict, evidently onGetPreferences wins. This can be seen as follows: In extension.json add "DefaultUserOptions": { "BeSilly": false } In onGetPreferences add $preferences['BeSilly'] = array( 'type' => 'toggle', 'label' => 'Be silly', 'section' => "$sillySection", 'default' => true ); The result is that the checkbox is checked by default. If you omit the default from extension.json and include it only in onGetPreferences, the result is the same. It seems that using onGetPreferences is preferable, since the default can be combined there (encapsulated) with the other information about the preference, while putting the default in DefaultUserOptions separates it from the related information, a dependency to be avoided unless there’s some advantage I’m missing. Putting it in both places is at best redundant. However, the documentation in https://www.mediawiki.org/wiki/Manual:Hooks/GetPreferences appears to recommend $wgDefaultUserOptions or DefaultUserOptions. While it shows one example of specifying 'default' in onGetPreferences, it also shows an example in which 'default' is not specified in onGetPreferences. So what’s best? I don’t want to use onGetPreferences for the default if a future version of MediaWiki is going to turn that into a mistake. Also, does DefaultUserOptions serve any purpose, if onGetPreferences accomplishes the same thing better? Thanks in advance for any advice or clarification. Tom Wenlin Institute, Inc. SPC (a Social Purpose Corporation) 文林研究所社会目的公司 Software for Learning Chinese E-mail: wenlin(a)wenlin.com Web: http://www.wenlin.com Telephone: 1-877-4-WENLIN (1-877-493-6546) ☯

2 3

TechCom Radar 2019-03-20
by Kate Chapman 23 Mar '19

23 Mar '19

Hi All, Here are the minutes from this week's TechCom meeting: * IRC meeting RFC: Skin templating <https://phabricator.wikimedia.org/T217158> March 27 at 11pm PST (March 28 06:00 UTC, 07:00 CET) in #wikimedia-office * RFC Approved: RfC: Standards for external services in the Wikimedia infrastructure. <https://phabricator.wikimedia.org/T208524> * RFC Approved: The Great Namespaceization and Reorg <https://phabricator.wikimedia.org/T166010> * IRC Meeting hosted RFC: Add a frontend build step to skins/extensions to our deploy process <https://phabricator.wikimedia.org/T199004> * Minutes: <https://tools.wmflabs.org/meetbot/wikimedia-office/2019/wikimedia-office.20…> * Log: <https://tools.wmflabs.org/meetbot/wikimedia-office/2019/wikimedia-office.20…> * IRC Meeting hosted RFC: Let's stop using QUnit as a mechanism for integration tests <https://phabricator.wikimedia.org/T212521> ** Minutes: <https://tools.wmflabs.org/meetbot/wikimedia-office/2019/wikimedia-office.20…> ** Log: <https://tools.wmflabs.org/meetbot/wikimedia-office/2019/wikimedia-office.20…> 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

Security Notification: A quick update on ongoing attempts to disrupt Wikimedia services
by David Sharpe 22 Mar '19

22 Mar '19

Hello, Over the past several days an individual has continued to attempt disruption of Wikimedia Services. The Wikimedia Foundation’s incident response processes are activated and countermeasures are in place. There have been a few times where brief service outages affecting Gerrit and Phabricator were necessary. We are working around the clock to safeguard all systems. We are putting a series of countermeasures and protections in place to limit the potential impact of similar activity going forward. We aren’t at liberty to provide more detail right now without putting our efforts at risk, but will update you again when we can. Please report any suspicious activity to security(a)wikimedia.org <mailto:security@wikimedia.org>. Thank you! Respectfully, David Sharpe Senior Information Security Analyst Wikimedia Foundation

2 1

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