Wikipedia talk:Wikipedia Signpost/2012-12-24/Technology report

That is good news in this Holiday season! Everytime I try to understand the whole Toolserver problem I keep thinking of that line from the movie Cool Hand Luke where the guard beats up a prison inmate and then calmly explains "What we've got here is (a) failure to communicate". Jane (talk) 10:30, 26 December 2012 (UTC)

No offense, and I'm not sure what engvar applies to the Signpost but it's normalise, quoted, in the header, and normalize, in an unattributed quote, in the body. Perhaps it would be best to avoid both usages.--Wehwalt (talk) 11:02, 26 December 2012 (UTC)
 * Wehwalt, I'm pretty sure we're not permitted to change spelling variety in quotes (MOS). It does lead to clashes within text, but there's no perfect way. Tony   (talk)  13:15, 26 December 2012 (UTC)
 * But my point (badly expressed, I'm afraid) is that you did just that. Which is the quoted word? Normalize or normalise?--Wehwalt (talk) 14:04, 26 December 2012 (UTC)
 * Quite. I'm afraid I was sufficiently ambivalent about changing the original z to an s (all Tech Reports I write are in British English for personal convenience) that I changed my mind halfway through. Correct now though :) Happy tidings, - Jarry1250 [Deliberation needed] 16:02, 26 December 2012 (UTC)


 * The way I look at it, as interested person but not a developer of any kind, was that I was rather a bomb that was dropped, then a bit of negotiation about the end of the Toolserver. But I am aware I don't know all the ins and outs. Main question is, why the tight schedule of conversion? That Wikilabs will be live soon, okay. But why immediately closedown Toolserver? Can the transition period not a bit longer (an extra year or so) to give less pressure and stress? When tools and bot are gradually moved to Wikilabs, the load on Toolserver will also gradually get lower. Most likely, that will make investment in new equipment superfluous, reducing costs for Toolserver. The way I look at it, Sumana Harihareswara has a nice challenge on his hands. First, she will have to restore confidence between the Toolserver lads and lasses. Second, she will need to start a kind of Outreach and or Helpdesk, to assist the tool and bot managers to move over. I have every confidence that she will be able to do that, but not in the present, limited time schedule. The Banner talk 11:11, 26 December 2012 (UTC)

If the production database replication and access (i.e., cross-database joins and joins with user databases) turns out to work better, faster, more reliably, or with less lag on Labs than the Toolserver, I suspect volunteers will quickly flock to it in droves. But that remains to be seen. We should know in the next three months. 70.59.14.20 (talk) 13:03, 26 December 2012 (UTC)


 * I am a Toolserver developer who runs a handful of tools from the system. I'm used to the way it works and it's fairly simple to get things done. However, with the downtime in 2012 and the prospect of it being gone, I thought I would migrate to Labs. I talked with the Labs team and set up an account and a million other things in a complex system of projects, instances, permissions, keys - at the end of the day the idea of running tools on a LAMP stack was really a lot of work. I'm still at the Toolserver. Mono 18:28, 26 December 2012 (UTC)


 * WMDE? PEAOFU (Please explain acronym on first use) - Nabla (talk) 21:40, 26 December 2012 (UTC)
 * Thank you, Jarry1250 - Nabla (talk) 05:01, 27 December 2012 (UTC)


 * I have always been a bit worried that Toolserver was a risk point for the project. I am however more worried that WMF is trying to Borg it.  Freedom to fork is critical, having Toolserver independent helps that freedom.  I am also concerned with the bureaucratic overhead Mono mentions above. Rich Farmbrough, 01:21, 27 December 2012 (UTC).