Wikitech-l September 2014

wikitech-l@lists.wikimedia.org

129 participants
127 discussions

RFC meeting today
by Tim Starling 22 Sep '14

22 Sep '14

This week only, we will have a Thursday 21:00 UTC meeting to discuss Aude's proposed Linker refactor: <https://www.mediawiki.org/wiki/Requests_for_comment/Linker_refactor> The time is: * UTC: Thursday 21:00 * US PDT: Thursday 14:00 * Europe CEST: Thursday 23:00 * Australia AEST: Friday 07:00 Next week, it will be back to the usual time of Wednesday UTC. A few hours ago, we discussed Andrew Wight's RFC "Page protection as a component", with the few people who were in #wikimedia-office at the usual time despite no meeting being announced. My apologies for the lack of an announcement. Logs are available at: <https://tools.wmflabs.org/meetbot/wikimedia-office/2014/wikimedia-office.20…> -- Tim Starling

2 1

Bugzilla Weekly Report
by reporter＠zirconium.wikimedia.org 21 Sep '14

21 Sep '14

1 0

ANN: Version 1.0.0 of the Memento Headers Extension
by Shawn Jones 21 Sep '14

21 Sep '14

All, Thanks to new architecture developments within the Memento Project, we are pleased to announce the availability of Version 1.0.0 of the Memento Headers time travel Extension for MediaWiki. The extension can be downloaded via [1]. Information on the extension is available at [2]. A demonstration wiki equipped with the extension is available at [3]. This extension only supplies the headers necessary to work with Memento clients [4], and does not provide all of the features of Memento for a MediaWiki installation. it relies upon an external TimeGate server, provided online by the Memento Project, to actually provide the datetime negotiation necessary for web time travel. Memento clients allow one to select a past date and time to browse, and then browse the web as if it were that date and time. Installing the Memento Headers extension in a MediaWiki installation allows Memento clients to seamlessly transition from using web archives to wikis, allowing one to view past versions of web pages without interruption. Earlier today, we announced the availability of version 2.1.0 of the full Memento extension. That extension provides additional functionality, such as ensuring that old revisions of images and templates match the revision of the page in which they are embedded. The Memento Headers extension does NOT provide such functionality. The Memento Headers extension only provides the headers necessary for Memento clients to find the oldid pages in MediaWiki installations that best match the datetime requested by the user. As noted in the earlier announcement, the Memento protocol is currently used by major web archives [5] and supported by the International Internet Presevation Consortium [6]. Though we have the support of web archives, the Memento team also considers time travel in MediaWiki to be a major use of the protocol. Videos [7] and [8] show Memento at work in the web at large, the latter paying attention to navigation within Wikipedia. Video [9] shows Memento at work in the full Memento MediaWiki extension. We really look forward to any feedback the Wikimedia community can provide on this new exciting (though limited) way to provide and experience Memento. On behalf of the Memento Team, Shawn M. Jones Graduate Research Assistant Department of Computer Science Old Dominion University Email: sjone(a)cs.odu.edu Research group: http://ws-dl.blogspot.com Twitter: @shawnmjones — [1] https://github.com/mementoweb/mediawiki-memento-headers/releases/tag/v1.0.0 [2] https://www.mediawiki.org/wiki/Extension:MementoHeaders [3] http://ws-dl-05.cs.odu.edu/demo-headers/index.php/Main_Page [4] http://bit.ly/memento-for-chrome [5] http://mementoweb.org/depot/ [6] http://netpreserve.org/ [7] http://www.youtube.com/watch?v=0_70lQPOOIg [8] http://www.youtube.com/watch?v=WtZHKeFwjzk [9] https://www.youtube.com/watch?v=ciClYjTnscs

1 0

ANN: Version 2.1.0 of the Memento MediaWiki Extension
by Shawn Jones 21 Sep '14

21 Sep '14

All, Thanks to a few informal code reviews, version 2.1.0 of the Memento time travel Extension for MediaWiki has been released. The extension can be downloaded via [1]. Information on the extension is available at [2]. A demonstration wiki equipped with the extension is available at [3]. This release incorporates changes to enrich the code based on additional review and feedback from members of the WikiMedia team. The extension fixed a few bugs, now supports the newer JSON-based i18n system, and has removed three configuration options in order to streamline the code. We fully appreciate the feedback we’ve received and appreciate any additional feedback the community can provide. Our goal is to make the extension as solid as possible for MediaWiki users everywhere. The extension works with Memento clients [4]. Memento clients allow one to select a past date and time to browse, and then browse the web as if it were that date and time. Installing this extension in a MediaWiki installation allows Memento clients to seamlessly transition from using web archives to wikis, allowing one to view the past versions of web pages without interruption. This has numerous applications, from avoiding spoilers [5] to studying the evolution of legal discourse. Additionally, this extension attempts to address the issue of "temporal coherence", ensuring that old revisions of images and templates match the revision of the page they are embedded in. This functionality is still optional and experimental, but has received some interest from the community. Earlier this summer, we presented our experiences with reconstructing the past using MediaWiki [6, 7], and demonstrated using the extension to avoid spoilers in Game of Thrones [8, 9, 10] at WikiConference USA 2014. The extension is fully compliant with RFC 7089 [11], which specifies the Memento protocol. The effort was supported in part by the Andrew W. Mellon Foundation and is a joint effort between Old Dominion University and Los Alamos National Laboratory. Videos [12] and [13] show Memento at work in the web at large, the latter paying attention to navigation within Wikipedia. The Memento protocol is currently used by major web archives [14] and supported by the International Internet Presevation Consortium [15]. Though we have the support of web archives, the Memento team also considers time travel in MediaWiki to be a major use of the protocol. We really appreciate the feedback from the Wikimedia team and look forward to additional assistance and improvements. Thank you again, on behalf of the Memento Team, Shawn M. Jones Graduate Research Assistant Department of Computer Science Old Dominion University Email: sjone(a)cs.odu.edu Research group: http://ws-dl.blogspot.com Twitter: @shawnmjones — [1] https://github.com/mementoweb/mediawiki/releases/tag/v2.1.0 [2] https://www.mediawiki.org/wiki/Extension:Memento [3] http://ws-dl-05.cs.odu.edu/demo/ [4] http://bit.ly/memento-for-chrome [5] http://ws-dl.blogspot.com/2013/12/2013-12-18-avoiding-spoilers-with.html [6] http://wikiconferenceusa.org/wiki/Submissions:Reconstructing_the_past_with_… [7] http://www.slideshare.net/shawnmjones/reconstructing-the-past-with-media-wi… [8] http://wikiconferenceusa.org/wiki/Submissions:Using_the_Memento_Mediawiki_E… [9] http://www.slideshare.net/shawnmjones/using-the-memento-mediawiki-extension… [10] https://www.youtube.com/watch?v=ciClYjTnscs [11] http://tools.ietf.org/html/rfc7089 [12] http://www.youtube.com/watch?v=0_70lQPOOIg [13] http://www.youtube.com/watch?v=WtZHKeFwjzk [14] http://mementoweb.org/depot/ [15] http://netpreserve.org

1 0

Re: [Wikitech-l] [Wikimedia-l] Invitation to beta-test HHVM
by Pine W 21 Sep '14

21 Sep '14

Just a few thoughts: * I agree that the tone of the email that started this discussion about software quality standards was unnecessarily critical. Even in production releases, users may find occasional bugs. * The intent of HHVM implementation and James' quick response to the problem report are nice to see. * The perfect should not be the enemy of the good, especially for opt-in pre-production releases. * Regarding standards for different release phases, I would need to think more about that but hope that someone will set up a proposed checklist on MediaWiki.org. We have some quality experts like Chris McMahon and their input would be helpful. Pine

1 0

Re: [Wikitech-l] [Wikimedia-l] Invitation to beta-test HHVM
by Pine W 21 Sep '14

21 Sep '14

Thanks, but I'm looking for something that is more specific to MediaWiki and that commits development teams to specific, standardized, and transparently measured quality metrics as products advance or regress in their path to production release. Pine

3 2

Re: [Wikitech-l] [Wikimedia-l] Invitation to beta-test HHVM
by Pine W 21 Sep '14

21 Sep '14

Given longtime experience with problematic releases of MediaWiki features, I think that published quality standards that products must meet in order to become production releases could help to limit the number and seriousness of additional troubled launches. These standards would also reduce the ambiguity around terms like alpha and beta. Pine

1 0

[BREAKING CHANGE] Deprecated JavaScript methods to be removed in MediaWiki 1.25
by Krinkle 20 Sep '14

20 Sep '14

TL;DR: * Several deprecated methods in MediaWiki's JavaScript modules will be removed in a few weeks' time. * Ensure your code no longer uses these methods and update it if needed. * Check and fix any gadgets or scripts you or your wikis rely upon. As part of the regular update cycle, a number of deprecated methods in our JavaScript modules will be removed in the MediaWiki 1.25 release. This is an announcement to give people notice they should update any extensions, gadgets and scripts they have written, maintain, or rely upon. Usually we don't give this much attention to removal of deprecated methods, but due to this being our first proper development cycle for our front-end code base, I want to make sure this reaches everyone. You're likely not yet in the habit of updating front-end code between MediaWiki releases. Deprecated methods to be removed in MediaWiki 1.25: * Remove mw.user.name() method. [1] Deprecated since MediaWiki 1.20. Use mw.user.getName() instead. * Remove mw.user.anon() method. [1] Deprecated since MediaWiki 1.20: Use mw.user.isAnon() instead. * Remove mediawiki.api methods' "ok" and "err" callback parameters. [2] Deprecated since MediaWiki 1.23. Use the returned Promise interface instead. * Remove mediawiki.api.category "async" parameter. [2] Deprecated since MediaWiki 1.23. The ability to override $.ajax() to be synchronous has been removed. The default (asynchronous) behaviour remains. Use the Promise interface to retreive the fetched data from the API. * Remove jquery.json module. Deprecated since MediaWiki 1.24. [3] Use standardised JSON.stringify and JSON.parse methods. And depend on the "json" module which will automatically load a polyfill in older browsers. ## Timeline These removals will land in MediaWiki 1.25alpha in early October 2014, and deployed to Wikimedia wikis the week after from October 4th onwards (1.25wmf2). The MediaWiki 1.25.0 stable release is expected to come out around April 2015. You should make sure that your code is updated before your wiki upgrades to MediaWiki 1.25. If you know code you rely upon will be affected but don't know how to fix it, please check with your wiki's community for local experts. If none of them can help, you can ask for assistance on the wikitech-ambassadors mailing list. [5] ## Reminders In case you've missed the previous announcements: * The migration period for jQuery core is still on-going and is also scheduled for MediaWiki 1.25. [4] More about that in the mail from June 2014: https://www.mail-archive.com/mediawiki-l%40lists.wikimedia.org/msg13651.html * Learn about deprecation notices and how you can see them in your browser. https://www.mail-archive.com/wikitech-l%40lists.wikimedia.org/msg72198.html [1] https://gerrit.wikimedia.org/r/#/c/111422/ [2] https://gerrit.wikimedia.org/r/#/c/118733/ [3] https://gerrit.wikimedia.org/r/#/c/140560/ [4] https://gerrit.wikimedia.org/r/#/c/137168/ [5] https://lists.wikimedia.org/mailman/listinfo/wikitech-ambassadors -- Krinkle PS: You can get a sense of the progress on our different migrations, past and present, via these graphs: http://codepen.io/Krinkle/full/zyodJ/

1 0

Re: [Wikitech-l] [Wikimedia-l] Invitation to beta-test HHVM
by Guillaume Paumier 20 Sep '14

20 Sep '14

Hello, On Sat, Sep 20, 2014 at 9:32 PM, Rand McRanderson <therandshow(a)gmail.com> wrote: > Here is one idea. A dashboard of top level Wikimedia projects with > statuses, estimates, and a key to terms. Or does this exist? There is https://www.mediawiki.org/wiki/Wikimedia_Engineering/Dashboard It doesn't have everything you mentioned, but we can build on it and improve it. -- Guillaume Paumier

1 0

Fixing PollNY -- ResourceLoader woes
by Jack Phoenix 20 Sep '14

20 Sep '14

Hi all, A few days ago I was fiddling around with my Labs instance [1], which serves as a development/testing/showcase area for social tools [2]. Somehow I ended up on Special:ViewPoll [3] and got curious as to why a JavaScript hover effect (mouseover/mouseout) didn't work on that page -- I was sure it used to work just fine not that long time ago. Without thinking that much about it, I clicked on the one and only poll listed on the page [4], and turns out the whole Poll: page is about as broken as it can be due to a JavaScript error. After a while of debugging, consultation and more debugging, turned out that my local development setup had $wgResourceLoaderDebug = true; in its LocalSettings.php, which apparently hides some race conditions or something like that. The Labs instance tries to be a more faithful representation of a production wiki, and as such, it doesn't have this setting enabled and hence why the problem manifests there. PollNY itself is a rather old extension, as most original social tools are (see the MW.org page [2] for details), and as such, it likely has some non-optimal code and it's also gone through plenty of iterations in the past. As a matter of fact, when porting PollNY to use ResourceLoader, it seems I myself made some suboptimal choices, such as bundling both CSS and JS into the same module and loading this module with 'position' => 'top'. Anyway, after decoupling the main CSS into its own module (locally, haven't submitted this to git yet), tweaking the callers and whatnot, I was able to get the hover effects on Special:ViewPoll to work as intended. While this is definitely a step forward, the actual problem with pages in the Poll: namespace still persists. PollNY has two JS files, LightBox.js and Poll.js. LightBox.js contains a lightbox implementation and technically it's not needed for stuff like the <pollembed> tag etc. and it should only be loaded on Poll: pages. Poll.js, on the other hand, is basically needed everywhere where there is PollNY; special pages, pages that embed a poll via the <pollembed> tag, Poll: pages... Now, the actual issue is that no matter what I do, I get a "TypeError: 'LightBox' is not defined" on Poll: pages (such as [4]). In the git master version, this is due to the aforementioned race condition: line 466 of Poll.js tries to use mw.loader.load() to load the LightBox RL module if it's not already loaded, but in RL's production mode this fails, because, as I've been told by those with more intimate knowledge of ResourceLoader and its inner workings, mw.loader.load is asynchronous. I've tried mw.loader.using, but it doesn't seem to do anything as far as fixing the issue goes. Please let me know if you're able to help me out with this; I've ran out of ideas. [1] http://social-tools.wmflabs.org/ [2] https://www.mediawiki.org/wiki/Social_tools [3] http://social-tools.wmflabs.org/wiki/Special:ViewPoll [4] http://social-tools.wmflabs.org/wiki/Poll:How_is_the_weather_today%3F Thanks and regards, -- Jack Phoenix MediaWiki developer

4 7

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

Jump to page:

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 September 2014