Wikitech-l August 2018

wikitech-l@lists.wikimedia.org

101 participants
92 discussions

Re: [Wikitech-l] coc ban
by Saint Johann 08 Aug '18

08 Aug '18

That was about the other thing, putting Code of Conduct file into every MediaWiki extension. Wikimedia Phabricator is by design a MediaWiki development space, so it’s under code of conduct by all definitions. (Although I must comment that banning a person for a ‘WTF’ type of comment is really unwarranted, especially when said to Wikimedia employees as opposed to volunteers.) Oleg

5 7

Re: [Wikitech-l] coc ban
by Saint Johann 08 Aug '18

08 Aug '18

I’m sorry, but no, even the evidence that Jimmy Wales is a worst human being on the entire planet Earth wouldn’t make some kinds of language (like the one you are quoting from) acceptable in a collaborative environment. Of course, he should apologise, but CoCC doesn’t have any authority about that, so it’s not reasonable to discuss it in such context. Please do not derail the conversation about this particular incident by going on a tangent about unrelated issues or ‘snowflakes’. The problem here is the repercussions too harsh for the language that is being quoted, not some general idea that MediaWiki development spaces should have some kind of rules. Oleg On 08/08/2018 17:44, wikitech-l-request(a)lists.wikimedia.org wrote: > Saying "WTF" is by default acceptable for all projects unless the WMF > board agrees a resolution and enforces it on its own board members, as > well as volunteers and WMF employees. If anyone is blocked or banned > under the Technical CoC for using similar language which has been > published by WMF board members, this should be grounds for a > successful appeal unless and until the same standards are seen to be > applied to WMF board members along with the same block and ban > actions. > > Just in case readers here missed the precedent set in 2016, Wales has > never retracted nor apologised for writing on the English Wikipedia > that a statement by Heilman was "utter fucking bullshit". Both parties > were Wikimedia Foundation board members at the time, and are board > members now.[1][2] > > Links > 1. https://en.wikipedia.org/w/index.php?title=User_talk:Jimbo_Wales&diff=70167… > 2. https://motherboard.vice.com/en_us/article/8q8gvg/wikipedias-secret-google-… > > Fae

1 0

Wednesday: Technical Advice IRC Meeting
by Michael Schönitzer 07 Aug '18

07 Aug '18

Sorry for cross-posting! Reminder: Technical Advice IRC meeting again **Wednesday 3-4 pm UTC** on #wikimedia-tech. The Technical Advice IRC Meeting (TAIM) 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 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

This week's TechCom IRC Meeting is on RFC: Block users by page/namespace
by Kate Chapman 06 Aug '18

06 Aug '18

Hi All, TechCom is hosting an IRC discussion on RFC: Block users by page/namespace <https://phabricator.wikimedia.org/T199917> this Wednesday August 8th at 2pm PST(21:00 UTC, 23:00 CEST) in #wikimediaoffice The goal of the Partial Blocks project is to give wiki administrators a more robust set of tools to be able to better respond to different user conflict situations. To retain constructive contributors who cause disruption on one page (e.g. contentious article page, user talk page of someone they constantly berate, etc.) we want to give admins the ability to block them from editing specific pages and/or all articles inside a namespace. 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)

1 0

TemplateStyles for everyone
by Chris Koerner 06 Aug '18

06 Aug '18

Hello. The team working on TemplateStyles at the Wikimedia Foundation would like to enable TemplateStyles on all Wikimedia later this week. TemplateStyles is a feature to allow non-administrators to write and manage CSS styles for templates. It allows contributors who edit templates to separate content and presentation. A good web practice that makes it easier to manage the layout of templates. If you don't edit templates, this will not have any impact on your contributions. TemplateStyles is useful for a few reasons. * It makes it possible for templates to work better on mobile. * It cuts out confusion on where to apply CSS rules. * Editing CSS is currently limited to administrators, which is a major barrier to participation. * All stylesheets must be loaded on all pages (whether they actually use the page or not), which wastes bandwidth and makes debugging style rules more difficult. You can learn more about TemplateStyles on MediaWiki.org.[0] Technical documentation is also available.[1] This is an optional feature and no one must use it, but template contributors are encouraged to do so! Please discuss and let us know if there are any concerns. If there are no concerns we will proceed to deploy the feature on the 9th of August. [0] https://www.mediawiki.org/wiki/Help:TemplateStyles [1] https://www.mediawiki.org/wiki/Extension:TemplateStyles Yours, Chris Koerner Community Relations Specialist Wikimedia Foundation

1 0

Readers Monthly update for July 2018
by Chris Koerner 06 Aug '18

06 Aug '18

Hello all, This is the monthly update from the Readers team at the Wikimedia Foundation for July 2018. Feedback and questions are encouraged. ==Discussions== === Apps=== * Wikipedia for iOS released a first beta of the next major version, 6.0.0. This update includes a fully user controlled Explore feed, similar to the recent changes on Android. It also includes major design and navigation improvements. === Web === * Page Previews now aborts in-flight requests if the user has shifted their focus, resulting in less data being sent to the user. [0] Indeed, Page Previews is now sending ~25% of the requests that it used to at peak. [1] *We are continuing work on advanced mobile contributions. [2] We conducted more than 20 interviews with editors at Wikimania and collected information on the most requested pages and workflows for editing and contributing on mobile. === Reading Infrastructure === * Doing definition work for T199096ː Add support for wikidata summaries in the /page/summary/ endpoint consulting with Wikidata and Readers web team [3] * Page Content Service: Improving mobile-html (fka. content-html) endpoint output. [4] Added several transformations from the #wikimedia-page-library. [5] * T198622ː Migrating maps servers to stretch with the current style and subtasks (Mapnik library upgrades for the stretch migration) [6] === New Readers === * New Reader updates can be found at Meta. [7] === Multimedia === * Video downloads will start being produced in VP9 format soon. [8] [0] https://phabricator.wikimedia.org/T197700 [1] https://grafana.wikimedia.org/dashboard/db/reading-web-page-previews?orgId=… [2] https://www.mediawiki.org/wiki/Reading/Web/Advanced_mobile_contributions [3] https://phabricator.wikimedia.org/T199096 [4] https://www.mediawiki.org/wiki/Page_Content_Service#Mobile_HTML [5] https://github.com/wikimedia/wikimedia-page-library [6] https://phabricator.wikimedia.org/T198622 [7] https://meta.wikimedia.org/wiki/New_Readers/Updates [8] https://www.mediawiki.org/wiki/Extension:TimedMediaHandler/VP9_transition --- Subscribe to receive theses updates as on-wiki notifications or opt-in email. https://www.mediawiki.org/wiki/Newsletter:Readers_Monthly The archive of all past updates can be found on MediaWiki.org: https://www.mediawiki.org/wiki/Reading/Status_updates Yours, Chris Koerner Community Relations Specialist Wikimedia Foundation

1 0

Discovery Weekly Update for the week starting 2018-07-30
by Chris Koerner 06 Aug '18

06 Aug '18

Greetings, This is the weekly update from the Search Platform team for the week starting 2018-07-30. As always, feedback and questions welcome. == Discussions == === Search === * David did a lot of work surrounding the upgrade to ElasticSearch 6.3: ** updated an extra plugin[0] ** updated the LTR plugin [1] ** worked on an older issue that we were waiting to fix for an experimental plugin that was throwing an exception on some requests [2] ** upgraded the experimental highlighter [3] ** upgraded the extra-analysis plugin [4] * Trey fixed an address stemming issue in Polish analyzer for search [5] and it'll be fully in production when a re-index occurs [6] * Trey also worked on a review of the Esperanto Morphological Libraries when a volunteer wanted to help in this effort (and knew Esperanto) [7] * David worked on a few cirrus integration tests are were randomly and consistently failing (V => Venom > V:N) [8] * Trey took on the task of reviewing the work of applying Indonesian Analysis Chain for Malay (writeup and review) [9] [10] * David took on the fairly massive task of changing how SpecialSearch/SearchEngine handles the 'prefix' URI param set by the InputBox extension with lots of help from others [11] * David did quite a bit of work on deprecating the SearchEngine::replacePrefixes with several related patches [12] * Trey worked on exploring the potential applications for NLP to be applied in Search (review and write-up [13] [14] * Stas implemented fulltext search for Lexemes when Lexeme namespace is requested in the search [15] * Stas added collecting click data from Wikidata prefix search into event logs so that we know what the users are selecting when using Wikidata prefix search [16] and it'll be in production late this week with the train * Erik and David worked on the completion suggester code which didn't gracefully handle shard failures during the fetch phase, which caused the response received by cirrus to not contain the necessary information [17] and it'll be in production late this week with the train * After a lot of discussion, Erik fixed an issue where intitle search didn't match the stop words [18] and it'll be in production late this week with the train * Gehel and Erik worked on ensuring discovery.query_clicks_* data is purged per privacy policy, with adding support for hourly or daily partition dropping [19] === Wikidata Query Service === * Wikibase Constraints violations are now loaded into WDQS database and are queryable. [20] [0] https://phabricator.wikimedia.org/T198067 [1] https://phabricator.wikimedia.org/T198066 [2] https://phabricator.wikimedia.org/T178425 [3] https://phabricator.wikimedia.org/T198069 [4] https://phabricator.wikimedia.org/T198068 [5] https://phabricator.wikimedia.org/T186046 [6] https://phabricator.wikimedia.org/T200037 [7] https://phabricator.wikimedia.org/T197240 [8] https://phabricator.wikimedia.org/T199445 [9] https://www.mediawiki.org/wiki/User:TJones_(WMF)/Notes/Analysis_of_Applying… [10] https://phabricator.wikimedia.org/T196780 [11] https://phabricator.wikimedia.org/T198318 [12] https://phabricator.wikimedia.org/T198860 [13] https://www.mediawiki.org/wiki/User:TJones_(WMF)/Notes/Potential_Applicatio… [14] https://phabricator.wikimedia.org/T193070 [15] https://phabricator.wikimedia.org/T196188 [16] https://phabricator.wikimedia.org/T196186 [17] https://phabricator.wikimedia.org/T180807 [18] https://phabricator.wikimedia.org/T68969 [19] https://phabricator.wikimedia.org/T189845 [20] https://phabricator.wikimedia.org/T172380 --- 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

1 0

Wikilabels now enforces SSL
by Amir Sarabadani 06 Aug '18

06 Aug '18

Hey, Some people reported that they have trouble labelling edits in wikilabels [1] (specially for Wikidata and that's why I'm cross-posting to wikidata-l too). That was due to the fact that wikilabels is behind a proxy on cloud VPS which confuses the application and sometimes it thinks the request is made over HTTP and changes the links/redirects to http instead of https and basically jumping over to SSL and not-SSL continuously causing OAuth redirect loops (because cookies can't jump around like requests). There were several options but the most secure and sane one was to enforce SSL and tell the application to consider everything as SSL request. This would solve lots of bugs and issues in wikilabels. We apologize for any inconvenience caused by it. It was difficult to understand the underlying problem because it was happening for some people and not all and was hard to reproduce the bug. Also, If you encounter any (new) issue, Please let me know immediately. More info: https://phabricator.wikimedia.org/T184437 [1]: https://labels.wmflabs.org/ 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 0

Re: [Wikitech-l] How to make oauth authentication with wikipedia?
by rupert THURNER 06 Aug '18

06 Aug '18

On Sun, Jul 29, 2018 at 4:30 PM, Bryan Davis <bd808(a)wikimedia.org> wrote: > On Sun, Jul 29, 2018 at 12:37 AM rupert THURNER > <rupert.thurner(a)gmail.com> wrote: > > > > if one takes an example, lke https://tools.wmflabs.org/video2commons/, > is > > this implemented like it should? is there any difference from "any" > > application or applications on the tools server? am looking at the code > > here currently: > > https://github.com/toolforge/video2commons/blob/master/ > video2commons/frontend/app.py > > the "dologin" method. > > Yes, there is a major difference between a web application like the > video2commons tool and a device native application like an Android > app. That difference is that in a web application secret data can be > kept on the web server side that is not visible to the end user. This > allows the OAuth application secret to be used in signing requests to > the Wikimedia servers without exposing that secret to anyone who is > looking at the source code of the web application. This separation is > not possible when the application is running on end-user controlled > devices as a phone or desktop application does. > > interesting, never thought about it. i found an entry on stackexchange confirming what you said. additionally it states that oauth is not for authenticaiton. oauth's purpose is to access users resources from some resource provider, while openid_connect should be used to authenticate. does openid_connect work with wikipedia and is it the best option currently? [0] https://security.stackexchange.com/questions/133065/why-is-it-a-bad-idea-to… [1] https://connect2id.com/learn/openid-connect [2] https://www.mediawiki.org/wiki/Extension:OpenID_Connect rupert

2 1

TechCom Radar 2018-08-01
by Kate Chapman 06 Aug '18

06 Aug '18

Hi All, Here are the minutes from this week's TechCom meeting: * IRC Meeting hosted for: RFC: Modern Event Platform - Choose Schema Tech <https://phabricator.wikimedia.org/T198256> consensus in meeting was to move forward with JSONSchema with strict policies about what is allowed (e.g. no additionalProperties) and how to do schema evolution. * Discussion on RFC: Block users by page/namespace discussion continues <https://phabricator.wikimedia.org/T199917> * Triaged: Pages do not have stable identifiers <https://phabricator.wikimedia.org/T196950> and was decided to postpone until after Unify various deletion systems <https://phabricator.wikimedia.org/T20493> which may solve the issue * Triaged: Editor should flag mobile editing warnings <https://phabricator.wikimedia.org/T200880> seeking clarification and then will review again. * Triaged and shortly scheduling IRC meeting for: RfC: Release notes automation <https://phabricator.wikimedia.org/T200392> 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)

1 0

← Newer
1
2
3
4
5
6
7
8
9
10
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