Wikitech-l March 2011

wikitech-l@lists.wikimedia.org

122 participants
96 discussions

GSOC Proposal for Account Creation, Login Screens, and Ajax-ification of everything
by Akshay Agarwal 25 Mar '11

25 Mar '11

Hi, I am Akshay Agarwal, a third year CSE student & a freelance web developer. Please have a look at my GSoc Proposal http://www.mediawiki.org/wiki/User:Akshay.agarwal & suggest necessary changes. Looking forward to your feedback, -- Thanks & Regards, Akshay Agarwal

5 7

Moving the Dump Process to another language
by Yuvi Panda 25 Mar '11

25 Mar '11

Hi, I'm Yuvi, a student looking forward to working with MediaWiki via this year's GSoC. I want to work on something dump related, and have been bugging apergos (Ariel) for a while now. One of the things that popped up into my head is moving the dump process to another language (say, C#, or Java, or be very macho and do C++ or C). This would give the dump process quite a bit of a speed bump (The profiling I did[1] seems to indicate that the DB is not the bottleneck. Might be wrong though), and can also be done in a way that makes running distributed dumps easier/more elegant. So, thoughts on this? Is 'Move Dumping Process to another language' a good idea at all? P.S. I'm just looking out for ideas, so if you have specific improvements to the dumping process in mind, please respond with those too. I already have DistributedBZip2 and Incremental Dumps in mind too :) [1]: https://bugzilla.wikimedia.org/show_bug.cgi?id=5303 Thanks :) -- Yuvi Panda T http://yuvi.in/

7 10

Re: [Wikitech-l] Enable WikiTrust spanish support
by Wilfredo Rodriguez 25 Mar '11

25 Mar '11

2011/3/25 Luca de Alfaro <luca(a)dealfaro.org>: > Dear Wilfredor, > I think a list of page_ids, one id per line, would be fine. > You could also give us a list > page_id,title Line example: 45063840,"Simón Bolívar" > where title is enclosed in " and where the "'s are quoted, following one of > the standard csv formats... > The answer we give back to you can contain page titles, so you can then > check if any title has changed. > If this does not work for you let us know; we are flexible. Nice! > Ok, we will bring up WikiTrust on the Spanish Wikipedia. It's quite easy > for us to do so. Excellent! I'd like, please let me know when this is done. I do not know the logistics of the process, however, I have closely followed in wp:en 1.0. > Thanks for your interest! The appreciation is mutual > Luca User:Wifredor

1 0

[GSoC 2011] Introduction + About some ideas
by Sagie Maoz 25 Mar '11

25 Mar '11

Hi guys, My name is Sagie, I'm a first-year CS and linguistics student at Tel-Aviv University. I'm applying for GSoC this summer and wanted to introduce myself. I actually talked with some of you on #mediawiki last night, under the handle "n0nick". I've been a professional web developer for 6 years, mostly done PHP work. I'm fairly familiar with web & wiki frameworks in general, and have had some (short) experience with MediaWiki. I'd like to read your thoughts on the following projects I had my eyes on: * Inline Editing extension for MW/SMW Sounds like a very interesting and useful project to work on, and seems to me it fits the timeframe. I saw that there's been a lot of work done already for this task by user janpaul123, and was wondering what's the status of this project and how I can help with making this a possible GSoC project. * Sidebar/toolbar customization GUI I understand there's overhaul work being done on element skin systems, but I talked with Dantman about the sidebar customization and from what I understand, it's possible to take this project as long as my work is abstract (and good) enough. Anyone has other thoughts on this? Should I perhaps avoid working on something that might interfere with current developers work? * Email notifications Again, I see in the wiki page that some work has been done on this, and testing and bugfixing is required. Do you think it could be a suitable summer project? Would love to hear your thoughts. Thanks, -- Your friend in time, Sagie Maoz sagie(a)maoz.info // +1 (347) 556.5044 // +972 (52) 834-3339 http://sagie.maoz.info/ http://n0nick.net/ /* simba says roar! */

3 2

Ehcache on Wikimedia
by Tim Starling 24 Mar '11

24 Mar '11

Our parser cache hit ratio is very low, around 30%. http://tstarling.com/stuff/hit-rate-2011-03-25.png This seems to be mostly due to insufficient parser cache size. My theory is that if we increased the parser cache size by a factor of 10-100, then most of the yellow area on that graph should go away. This would reduce our apache CPU usage substantially. The parser cache does not have particularly stringent latency requirements, since most requests only do a single parser cache fetch. So I researched the available options for disk-backed object caches. Ehcache stood out, since it has a suitable feature set out of box and was easy to use from PHP. I whipped up a MediaWiki client for it and committed it in r83208. My plan is to do a test deployment of it, starting on Monday my time (i.e. Sunday night US time), and continuing until the cache fills up somewhat, say 2 weeks. This deployment should have no user-visible consequences, except perhaps for an improvement in speed. -- Tim Starling

2 2

parse vs. recursiveTagParse
by Stephan Gambke 24 Mar '11

24 Mar '11

I work on an extension that used to call parse() directly. Then after some advice from mw developers this was changed to a call to recursiveTagParse because "parse should not be called directly". Only problem is, the method that used to call parse() is used to populate a Special page, so parse() is never called in the first place, right? This means all the things parse() does in addition to recursiveTagParse have to be copied over. So, what exactly makes it so inadvisable to call parse()? Stephan

3 3

[Selenium] Structured description of tests?
by Benedikt Kaempgen 24 Mar '11

24 Mar '11

Hello, As I see from [1-4], test descriptions for MW with the Selenium Framework are not much structured at the moment. I think, this will make it difficult to maintain these tests. Any suggestions how we could improve this? For a start, a bachelor student of mine will be looking into how to describe system tests for Semantic MediaWiki (and extensions) using categories and properties of Semantic MediaWiki. We are planning that tests are derived from and link to contents in the user/admin manual. Regards, Benedikt [1] http://www.mediawiki.org/wiki/Cite_Extension_Test_Plan [2] http://www.mediawiki.org/wiki/ConfirmEdit_Test_Plan [3] http://www.mediawiki.org/wiki/New_installer/Test_plan [4] http://www.mediawiki.org/wiki/Selenium/Deployment#Automation_work_done_by_th e_Calcey_team -- AIFB, Karlsruhe Institute of Technology (KIT) Phone: +49 721 608-47946 Email: benedikt.kaempgen(a)kit.edu Web: http://www.aifb.kit.edu/web/Hauptseite/en

2 2

Ops problem with secure.wikimedia.org
by George Herbert 23 Mar '11

23 Mar '11

Trying to edit is failing: Proxy Error The proxy server received an invalid response from an upstream server. The proxy server could not handle the request GET /wikipedia/en/w/index.php. Reason: Error reading from remote server Reading articles still works ok. -- -george william herbert george.herbert(a)gmail.com

1 0

Review InterWiki Transclusion branch (pretty please?)
by mhershberger＠wikimedia.org 23 Mar '11

23 Mar '11

I think I understand the desire for better, easier tools (git does make branching and merging super-easy), but could I sidetrack the git discussion for a bit and ask that people review the InterWiki Transclusion branch (http://hexm.de/0y)? Roan has already reviewed a big part of the code, but his time is very limited right now. People have been asking for this for quite a while: the bug number is 9890 (https://bugzilla.wikimedia.org/9890). I'd like to get it reviewed before too much bit-rot sets in. Mark.

1 0

Toolserver source control (was Re: Converting to Git?)
by Ryan Lane 23 Mar '11

23 Mar '11

> As to Toolserver, this environment and its functionality is deeply flawed. > As the tools are open source, there is no reason why relevant tools cannot > be brought into GIT and upgraded to a level where they are of production > quality. Either GIT is able to cope or its distributed character adds no > real value. > > The notion that it has to be MediaWiki core and or its extensions first is > absurd when you consider that it is what we use to run one of the biggest > websites of the world. We rely on the continued support for our production > process. The daily process provided by LocalisationUpdate is such a > production process. When the continuity of production processes is not a > prime priority, something is fundamentally wrong. You are misunderstanding. The thread isn't about toolserver, so you are muddying up a perfectly valid thread with something totally non-related. Yes, toolserver has a problem, and it should be addressed. It isn't a problem with the MediaWiki developer community though, it's a problem with the toolserver community, and they need to fix it. But again, let's focus on one issue at a time. - Ryan Lane

9 12

← 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 March 2011