Wikitech-l July 2015

wikitech-l@lists.wikimedia.org

97 participants
74 discussions

VE stopped working on 1.25 after import & update of wiki db (1.23->1.25)
by Daren Welsh 12 Jul '15

12 Jul '15

We have an existing wiki using MW 1.23. We are working on a build script to generate a wiki using MW 1.25. Eventually the script will also automate the database import and update, but for now I'm still learning the steps. I built a VM with 1.25 and VE using some scripts that we are building[1]. VE seemed to be happily working. Then I imported our 1.23 SQL database and files (/images). I ran update.php and runJobs.php. Now it seems VE hangs at about the 75% point of the blue "progress bar" after clicking "Edit". Note that I am still able to edit source. I know this is not enough to get a full answer, but I'm hoping you can help me find some more resources to try. For example, are there any significant changes between the REL1_25 branch of Parsoid and HEAD? I see the branch on Gerrit, but I couldn't see that branch in git for a checkout. Thanks, Daren [1] https://github.com/enterprisemediawiki/Meza1 -- __________________ http://enterprisemediawiki.org http://mixcloud.com/darenwelsh http://www.beatportfolio.com

4 5

[RfC] Content model storage
by Legoktm 12 Jul '15

12 Jul '15

Hi, I've written up an RfC to change the way we currently store a page's and revisions' content model and format: <https://www.mediawiki.org/wiki/Requests_for_comment/Content_model_storage> in the database. Please leave comments on the talk page. Thanks! -- Legoktm

2 1

+2 in mediawiki/* for Liangent
by Legoktm 12 Jul '15

12 Jul '15

Hi, Per [1], I gave Liangent +2 powers in mediawiki/* repos. Congratulations! [1] https://phabricator.wikimedia.org/T98386 -- Legoktm

5 4

Flow, LiquidThreads, and XML dumps
by wp mirror 12 Jul '15

12 Jul '15

Dear Sir of Madam, I would like to see what impact Flow will have on dump files. I see that LiquidThreads still appear in the XML dumps of enwikinews (as of 20150602). Will the tables containing Flow records be dumped in SQL or XML format? Are there now any SQL or XML dumps that contain Flow records? If not, can you forecast when Flow will appear in the dumps? SIncerely Yours, Kent

2 1

Re: [Wikitech-l] API BREAKING CHANGE: Default continuation mode for action=query will change at the end of this month
by Mr. Stradivarius 10 Jul '15

10 Jul '15

> On *Wed, Jul 8, 2015 at 6:17 AM, Marco F <* *maic23 at live.de <wikitech-l%40lists.wikimedia.org?Subject=Re%3A%20%5BWikitech-l%5D%20API%20BREAKING%20CHANGE%3A%20Default%20continuation%20mode%20for%0A%20action%3Dquery%20will%20change%20at%20the%20end%20of%20this%20month&In-Reply-To=%3CDUB127-W101D748884FAB0EF70713FC4910%40phx.gbl%3E>> wrote:> *> You can't expect the average user to go to Phabricator or post on this mailing > list. If you are lucky, they complain on the respective talk pages like [1] or > some other place. > > I think, there is be quite a substantial amount of programs around which still > use the old interface and are broken now. Waiting for someone to notice and > fix... > > Marco > > [1] https://commons.wikimedia.org/w/index.php?title=MediaWiki_talk%3AGadget-Cat… I'm sure there are still some out there, but probably not as many as you think. I know that there aren't any gadgets or user scripts on enwiki or mediawikiwiki that use the old syntax, because I cleaned them up personally. I also got myself global interface editor rights and fixed all the gadgets in the MediaWiki namespace on every Wikimedia wiki. That still leaves bots, other external tools, and user scripts that aren't gadgets, so it's hard to say what's still left to fix. But most of the important gadgets are working, at least. Another good idea might be to look through the public repositories for external tools and bot frameworks to check whether they have implemented the change. I think we can safely assume that the big ones like Huggle, Twinkle and AWB have been fixed, due to the lack of noise at enwiki's technical village pump. But there may well be smaller external tools out there that still need fixing. Also, if anyone is interested, I have compiled a list of scripts on all WMF wikis that may need updating.[1] It has 129 pages in at the moment, although some are false positives, and some are personal scripts for inactive users that we don't need to bother with. Strad [1] https://en.wikipedia.org/wiki/User:Mr._Stradivarius/Query-continue

4 4

Interwiki navigation via search box appears to be broken
by Pine W 10 Jul '15

10 Jul '15

For example, searching for "Commons:main" on ENWP no longer takes the user to the Commons main page. Fix please. (: Thanks, Pine

1 1

Data and Developer Hub protoype
by S Page 09 Jul '15

09 Jul '15

http://devhub.wmflabs.org is a prototype of the "Data and developer hub", a portal and set of articles and links whose goal is to encourage third-party developers to use Wikimedia data and APIs. Check it out, your feedback is welcome! You can comment on the talk page of the project page https://www.mediawiki.org/wiki/dev.wikimedia.org , or file Phabricator tickets in the project dev.wikimedia.org [1]. Since December 2013 Moiz Syed and others discussed creating "a thing" to expose our APIs and data to developers. When S Page moved to WMF tech writer, he wrote some articles for this on mediawiki.org and with Quim Gil developed a landing page from the wireframe designs [2]. The prototype is using the Blueprint skin and running on a labs instance, but the articles are all regular wiki pages on mediawiki.org that we regularly import to http://devhub.wmflabs.org Thanks to everyone who participated in the gestation of this idea! -- S Page and Quim Gil == FAQ == Q: How can I feature my awesome API or data set? A: Create a task in the #dev.wikimedia.org and #documentation projects [3] with "Article" in the title. You can draft an article yourself, following the guidelines [4]. Q: Yet another site? Arghh! A: Agreed, T101441 "Integrate new Developer hub with mediawiki.org" [5]. It's a separate site for now in order to present a different appearance. Q: But why a different appearance? Why a separate skin? Our competition for developer mindshare is sites like https://developers.google.com/ . We believe looking like a 2000s wiki page is a *deterrent* to using Wikimedia APIs and data. We hope that many third-party developers join our communities and eventually contribute to MediaWiki, but "How to contribute to MediaWiki" [6] is not the focus, providing free open knowledge is. Q: Why the Blueprint skin? A: The Design team (now Reading Design) developed it for the OOUI Living Style Guide [7] and it has some nice features: a fixed header, and a sidebar that gets out of the way and combines page navigation and the TOC of the current page. Q: So why not use the Blueprint skin on mediawiki.org? A: Agreed, T93613 "Deploy Blueprint on mediawiki.org as optional and experimental skin" is a blocker for T101441. We appreciate help with it and its blockers. Q: I hate the appearance. A: That's not a question :) You can forget the prototype exists and view the same content at https://www.mediawiki.org/wiki/API:Data_and_developer_hub Q: What is "dev.wikimedia.org"? A: http://dev.wikimedia.org will be the well-known shortcut to the landing page. And dev.wikimedia.org is the project name for this "Data and developer hub". Q: I thought dev.wikimedia.org was going to integrate source documentation/replace doc.wikimedia.org/enumerate all Wikimedia software projects/cure cancer, what happened? A: One step at a time. For now, its goal is, to repeat, "to encourage third-party developers to use Wikimedia data and APIs". Q: Why are the pages in the API: namespace? A: That's temporary, they will probably end up in a dev: namespace on mediawiki.org that uses the Blueprint skin by default (T369). Q: Where are the talk pages? A: It's a bug that the sidebar doesn't have a "Discussion" link (T103785). The talk pages on the prototype all redirect to the talk pages for the original pages on mediawiki.org, and Flow is enabled on them. [1] https://phabricator.wikimedia.org/maniphest/task/create/?projects=dev.wikim… [2] https://www.mediawiki.org/wiki/Dev.wikimedia.org#Structure [3] https://phabricator.wikimedia.org/maniphest/task/create/?projects=dev.wikim… [4] https://www.mediawiki.org/wiki/dev.wikimedia.org/Contributing [5] https://phabricator.wikimedia.org/T93613 and its blockers [6] https://www.mediawiki.org/wiki/How_to_contribute (a fine general entry point) [7] http://livingstyleguide.wmflabs.org/ -- =S Page WMF Tech writer

8 16

Plan for a Developer Relations team
by Quim Gil 09 Jul '15

09 Jul '15

Hi, the Engineering Community team is working on a plan to evolve onto a Developer Relations team. This is not just a change of name. See *https://www.mediawiki.org/wiki/Engineering_Community_Team/Developer_Relations_team <https://www.mediawiki.org/wiki/Engineering_Community_Team/Developer_Relatio…>* Your feedback is welcome, in the wiki page or here. Related task: https://phabricator.wikimedia.org/T97283 -- Quim Gil Engineering Community Manager @ Wikimedia Foundation http://www.mediawiki.org/wiki/User:Qgil

4 6

2015-07-08 Scrum of Scrums notes
by Grace Gellerman 08 Jul '15

08 Jul '15

https://www.mediawiki.org/wiki/Scrum_of_scrums/2015-07-08

2 1

API BREAKING CHANGE: Default continuation mode for action=query will change at the end of this month
by Brad Jorsch (Anomie) 08 Jul '15

08 Jul '15

As has been announced several times (most recently at https://lists.wikimedia.org/pipermail/wikitech-l/2015-April/081559.html), the default continuation mode for action=query requests to api.php will be changing to be easier for new coders to use correctly. *The date is now set:* we intend to merge the change to ride the deployment train at the end of June. That should be 1.26wmf12, to be deployed to test wikis on June 30, non-Wikipedias on July 1, and Wikipedias on July 2. If your bot or script is receiving the warning about this upcoming change (as seen here <https://www.mediawiki.org/w/api.php?action=query&list=allpages>, for example), it's time to fix your code! - The simple solution is to simply include the "rawcontinue" parameter with your request to continue receiving the raw continuation data ( example <https://www.mediawiki.org/w/api.php?action=query&list=allpages&rawcontinue=1>). No other code changes should be necessary. - Or you could update your code to use the simplified continuation documented at https://www.mediawiki.org/wiki/API:Query#Continuing_queries (example <https://www.mediawiki.org/w/api.php?action=query&list=allpages&continue=>), which is much easier for clients to implement correctly. Either of the above solutions may be tested immediately, you'll know it works because you stop seeing the warning. I've compiled a list of bots that have hit the deprecation warning more than 10000 times over the course of the week May 23–29. If you are responsible for any of these bots, please fix them. If you know who is, please make sure they've seen this notification. Thanks. AAlertBot AboHeidiBot AbshirBot Acebot Ameenbot ArnauBot Beau.bot Begemot-Bot BeneBot* BeriBot BOT-Superzerocool CalakBot CamelBot CandalBot CategorizationBot CatWatchBot ClueBot_III ClueBot_NG CobainBot CorenSearchBot Cyberbot_I Cyberbot_II DanmicholoBot DeltaQuadBot Dexbot Dibot EdinBot ElphiBot ErfgoedBot Faebot Fatemibot FawikiPatroller HAL HasteurBot HerculeBot Hexabot HRoestBot IluvatarBot Invadibot Irclogbot Irfan-bot Jimmy-abot JYBot Krdbot Legobot Lowercase_sigmabot_III MahdiBot MalarzBOT MastiBot Merge_bot NaggoBot NasirkhanBot NirvanaBot Obaid-bot PatruBOT PBot Phe-bot Rezabot RMCD_bot Shuaib-bot SineBot SteinsplitterBot SvickBOT TaxonBot Theo's_Little_Bot W2Bot WLE-SpainBot Xqbot YaCBot ZedlikBot ZkBot -- Brad Jorsch (Anomie) Software Engineer Wikimedia Foundation

12 23

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 July 2015