Wikitech-l June 2015

wikitech-l@lists.wikimedia.org

110 participants
99 discussions

Getting article content
by Aran 18 Jun '15

18 Jun '15

I just noticed that Article::getContent is deprecated now, and the code says that WikiPage::getContent is now the preferred method. What's the recommended way to get the current text content of a normal wikitext article now? Would it be this? $text = $article->getPage()->getContent()->getNativeData();

2 1

Overriding Jenkins versus make-work patches
by Brad Jorsch (Anomie) 18 Jun '15

18 Jun '15

We have an (informal?) policy that deprecation warnings shouldn't be raised in WMF production. Thus if a core patch is going to add deprecation warnings we have to make sure that all extensions deployed on the cluster are updated to not trigger the warning. We can accomplish this by carefully managing the addition of the warnings, by detecting the core version from the extension and changing behavior, or by simply updating both core and extension at the same time. With Gerrit change 134827,[1] the affected extensions are Flow and CentralAuth. For neither of these extensions do we care that extension-master works with non-master versions of MediaWiki core, and patches to update the extensions are ready.[2][3] So normally we'd just merge all three at once and be done with it. The problem is unit tests: we can't merge the core change[1] first because Flow's unit tests will fail on the deprecation warning, and we can't merge the Flow change[2] first because it doesn't work without the core change. There are various ways to work around this, but all are ugly: 1. Merge the core change over Jenkins's objections, then the Flow change can be merged as normal. But overriding Jenkins sucks. 2. Split the core patch into two parts: part 1 does everything except add the wfDeprecated() call, while part 2 adds just the wfDeprecated() call and will be merged immediately after. The make-work here just to make Jenkins happy sucks and slightly clutters the commit history. 3. Rewrite the Flow unit test to detect whether core has the core change and alter behavior accordingly. This is even more make-work than option 2 when we're otherwise happy to just coordinate the merges. Which ugly option do we as a development community prefer in this situation? Personally I'd go for option 1 as the most expedient with the fewest long-term consequences. [1]: https://gerrit.wikimedia.org/r/#/c/134827/ [2]: https://gerrit.wikimedia.org/r/#/c/190023/ [3]: https://gerrit.wikimedia.org/r/#/c/190026/ P.S. Let's not side-track this into whether the "extension master only needs to be compatible with core master" policy for Flow and CentralAuth is good/bad, or that situations exist where options 2 or 3 are necessary choices (e.g. #2 when the extension fixes aren't ready yet and #3 when an extension involved doesn't have the "master is only compatible with core master" policy), or whether allowing core changes to be merged that cause non-WMF-deployed extensions to raise deprecation warnings is somehow discriminating against non-WMF-deployed extensions. Start a new thread if you want to discuss those, please. -- Brad Jorsch (Anomie) Software Engineer Wikimedia Foundation

8 12

Implementing features for the sake of implementing features
by Eran Rosenthal 18 Jun '15

18 Jun '15

Sometimes programmers waste their time for implementing non-useful/non-important features, but sometimes such features aren't just not useful, but harmful.[1; you are more than welcome to convince me otherwise] Both developers, designers and project managers should always ask themselves why do we need such feature before going to implement it and should be able to convince others on the motivation for it. I think that sometimes we fail… (and sometimes even in the "postmortem" step[1]) The question is how can Wikimedia foundation improve the process? For large changes there are already reviews and RFC on mediawiki wiki, but for smaller ones it is sometimes missed (and even phabricator ticket). Should any feature should be associated with phab task?[2] Eranroz ----- [1] <https://phabricator.wikimedia.org/T100691>https <https://phabricator.wikimedia.org/T100691>:// <https://phabricator.wikimedia.org/T100691>phabricator.wikimedia.org <https://phabricator.wikimedia.org/T100691>/T100691 <https://phabricator.wikimedia.org/T100691> / https://gerrit.wikimedia.org/r/#/c/95723/ defeature __NOEDITSECTION__ from VE [2] https://www.mediawiki.org/wiki/VisualEditor/2015_Process_Review#Recommendat… .

2 1

2015-06-17 Scrum of Scrums notes
by Grace Gellerman 17 Jun '15

17 Jun '15

https://www.mediawiki.org/wiki/Scrum_of_scrums/2015-06-17

1 0

(off) Baidu Baike current dump
by Farkas, Illes 17 Jun '15

17 Jun '15

Hello, Does anyone know a method for downloading the current dump of Baidu Baike? Suggestions for alternative mailing lists would be also great. Thanks, Illes http://goo.gl/trcz4

2 1

RFC meeting this week
by Tim Starling 17 Jun '15

17 Jun '15

In the next RFC meeting, we will discuss the following RFC: * Request timeouts and retries https://phabricator.wikimedia.org/T97204 * Re-evaluate varnish-level request-restart behavior on 5xx https://phabricator.wikimedia.org/T97206 The meeting will be on the IRC channel #wikimedia-office on chat.freenode.net at the following time: * UTC: Wednesday 21:00 * US PDT: Wednesday 14:00 * Europe CEST: Wednesday 23:00 * Australia AEST: Thursday 07:00 -- Tim Starling

1 0

Tech Talk: Kanban: An alternative to Scrum?
by Rachel Farrand 16 Jun '15

16 Jun '15

Please join us for the following tech talk: *Tech Talk**:* Kanban: An alternative to Scrum? *Presenter:* Kevin Smith *Date:* June 15th *Time:* 22:00 UTC <http://www.timeanddate.com/worldclock/fixedtime.html?msg=Tech+Talk%3A+Kanba…> Link to live YouTube stream <http://www.youtube.com/watch?v=zT8cUtMTGPI> *IRC channel for questions/discussion:* #wikimedia-office Google+ page <https://plus.google.com/u/0/b/103470172168784626509/events/cg2sb5m878c8ot3n…>, another place for questions *Summary: *Kanban is becoming a popular buzzword in software development. Some teams are looking at starting with a Kanban process as a stepping stone toward Scrum, while others are considering switching from Scrum to Kanban. Meanwhile, the author of "The Kanban Method" claims that "Kanban is NOT a software development lifecycle or project management methodology!" This talk will attempt to clarify what Kanban is (and is not), how it compares to Scrum, and why a team might choose to use it. *About the speaker: *Kevin has been practicing agile software development for over 15 years. He joined the WMF as an Agile Coach in March 2015.

1 4

Jenkins now runs HHVM 3.6.1
by Antoine Musso 16 Jun '15

16 Jun '15

Hello, I have completed the upgrade of HHVM from 3.3.1 to 3.6.1 on the continuous integration slaves. Seems everything is passing just fine now. == context == We upgraded hhvm once but that failed https://phabricator.wikimedia.org/T98876 The main blocker was an issue with a mediawiki/core test that invokes gmp_init(). Stas Malyshev, Giuseppe Lavagetto, Bryan Davis and Ori Livneh all looked at it and found a workaround. https://phabricator.wikimedia.org/T98882 The upgrade was tracked with: Upgrade HHVM on CI Trusty slaves from 3.3.1 to 3.6.1 https://phabricator.wikimedia.org/T102616 -- Antoine "hashar" Musso

1 0

API mustposttoken / notoken error
by planetenxin 15 Jun '15

15 Jun '15

After an upgrade from 1.23.x to 1.25.1 I get an 'mustposttoken' error when I try to edit a page via API: "code":"mustposttoken","info":"The 'token' parameter was found in the query string, but must be in the POST body" When I remove the token parameter from the query parameters and add the token parameter to the post body, I get "code":"notoken","info":"The token parameter must be set" Any ideas? /Planetenxin

2 4

Search errors on multiple Wikimedia projects
by Pine W 15 Jun '15

15 Jun '15

I'm getting this same error on multiple Wikimedia projects: "An error has occurred while searching: Search is currently too busy. Please try again later." Help? Pine

5 5

← 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 June 2015