Wikitech-l February 2009

wikitech-l@lists.wikimedia.org

117 participants
106 discussions

Javascript localization, minify, gzip & cache forever
by Michael Dale 24 Feb '09

24 Feb '09

So I was running into the problem of localizing the messages for the add_media_wizard & mv_embed & associated libraries. So I have taken a first pass at witting the script server (that I had previously described) http://tinyurl.com/ae44vd Below is a description of how it works. the code is in the svn http://tinyurl.com/darmme ... I think it would be good to consider wider usage or at least turning it on sometime soon so I can deploy the add_media_wizard as a multi-lingual gadget. I am happy to volunteer to write a basic patch for putting it in the root. MediaWiki folder. (since its another entry point I imagine it should go in the root) I have put a copy of this desc on http://www.mediawiki.org/wiki/ScriptLoader ... let me know if there is a better place to put that on mediaWiki == Primary Motivation: == We need a script server to package language text into javascript. When a user invokes a interface component say the add media wizard we don't want to pull the entire interface code base and all the messages at once. Instead we just want to grab enough to display the current interface interaction. Once the user click on some tab say the 'archive.org search' we then want to import the code to run the archive.org search and the localized messages specific to that interface component. In other words we don't want to package all the message text in the html output of the initial page because in their are lots of possible interface interactions from any given point of invoking the user interface. == Secondary Benefits == If we are ruining all the javascript though a php script might as well group requests, minify; gzip; use the local file cache system; send headers to cache forever on the squids, and we make each javascript request unique based on svn version and avoid re-validate requests. All these combined do speed things up a good deal on the first time a user loads page. == How to use== In your Global settings you add to the global wgJSAutoloadClasses variable something like for every javascript class you want to load. $wgJSAutoloadClasses['mv_embed'] = '/local/path/to/my/javascript/mv_embed.js'; then at the top of mv_embed.js you would put something like: loadGM({ "msg_key":"Fall-back text if script server is disabled" ... } note the json variable that you pass to loadGM has to be valid JSON (not javascript) or php will complain. Then in your message file you put the normal msg key pairs: "msg_key":"My localized text", Right now we only support basic $1 replace ... obviously things get tricky with contextual wiki-text type replacements. (don't use that in js messages) Then you can modify your head javascript include: with something like: if( $wgEnableScriptLoader ){ $unique_req_param = SVN_VERSION $debug_param = ($mvgJSDebug) ? '&debug=true' : ''; $wgOut->addScript(... mvwScriptLoader.php?" . "class=all_the_class_i_need_separated_by_commas" . '&urid=' .$unique_req_param . $debug_param . "\"></script>" ); Note the use of a few config vars...here are the config vars: ===Configuration vars=== $wgEnableScriptLoader = true; //if the script loader should be used at all $mvgJSDebug=false; // if set to true will send raw, fresh un-minified, localized javascript $wgEnableScriptLoaderJsFile = true; //if you can use the script loader with js files based on the root script folder ie: ?file=/skin/common.js (rather than only js classes looked up with $wgEnableScriptLoader) $wgEnableScriptMinify = true; peace, michael.

4 6

Extension:SpamBlacklist download painful
by jidanni＠jidanni.org 24 Feb '09

24 Feb '09

3 4

action=view links for [[:Category:With members, but no text]]
by jidanni＠jidanni.org 24 Feb '09

24 Feb '09

How can one link to a [[:Category:With members, but no text]] but with no action=edit produced? > Use {{fullurl}}. Yes, but the <a>...</a> produced is many times larger than that of an internal link, a few of these and the bloat adds up. > Use {{localurl}}. Yes, but that does not create a link. > Hack up includes/*.php. Yes, but let's assume we are just a lowly user.

6 12

MediaWiki 1.14.0 and 1.13.5 released
by Tim Starling 24 Feb '09

24 Feb '09

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 We are proud to announce the first stable release of the 2009 Q1 branch of MediaWiki, version 1.14.0. We are also releasing MediaWiki 1.13.5. This is a maintenance release which corrects some bugs in the installer, introduced during the hasty security release of 1.13.4. It is not necessary to upgrade if you do not intend on using the installer. Thanks to our localisation community at translatewiki.net, MediaWiki 1.14.0 now has 311,000 localised interface text fragments spread across 298 languages, that's 17% more than in 1.13.0. MediaWiki is now using a "continuous integration" development model with quarterly snapshot releases. The latest development code is always kept "ready to run", and in fact runs our own sites on Wikipedia. Release branches will continue to receive security updates for about a year from first release, but nonessential bugfixes and feature developments will be made on the development trunk and appear in the next quarterly release. Those wishing to use the latest code instead of a branch release can obtain it from source control: <http://www.mediawiki.org/wiki/Download_from_SVN> Upgrade FAQ: http://www.mediawiki.org/wiki/Manual:FAQ#Upgrading Full release notes: <http://svn.wikimedia.org/svnroot/mediawiki/tags/REL1_14_0/phase3/RELEASE-NO…> <http://svn.wikimedia.org/svnroot/mediawiki/tags/REL1_13_5/phase3/RELEASE-NO…> ********************************************************************** MEDIAWIKI 1.14.0 ********************************************************************** Download: http://download.wikimedia.org/mediawiki/1.14/mediawiki-1.14.0.tar.gz Patch to previous version (1.14.0rc1), without interface text: http://download.wikimedia.org/mediawiki/1.14/mediawiki-1.14.0.patch.gz Interface text changes: http://download.wikimedia.org/mediawiki/1.14/mediawiki-i18n-1.14.0.patch.gz GPG signatures: http://download.wikimedia.org/mediawiki/1.14/mediawiki-1.14.0.tar.gz.sig http://download.wikimedia.org/mediawiki/1.14/mediawiki-1.14.0.patch.gz.sig http://download.wikimedia.org/mediawiki/1.14/mediawiki-i18n-1.14.0.patch.gz… Public keys: https://secure.wikimedia.org/keys.html ********************************************************************** MEDIAWIKI 1.13.5 ********************************************************************** Download: http://download.wikimedia.org/mediawiki/1.13/mediawiki-1.13.5.tar.gz Patch to previous version (1.13.4), without interface text: http://download.wikimedia.org/mediawiki/1.13/mediawiki-1.13.5.patch.gz Interface text changes: http://download.wikimedia.org/mediawiki/1.13/mediawiki-i18n-1.13.5.patch.gz GPG signatures: http://download.wikimedia.org/mediawiki/1.13/mediawiki-1.13.5.tar.gz.sig http://download.wikimedia.org/mediawiki/1.13/mediawiki-1.13.5.patch.gz.sig http://download.wikimedia.org/mediawiki/1.13/mediawiki-i18n-1.13.5.patch.gz… Public keys: https://secure.wikimedia.org/keys.html -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkmhN3EACgkQ8F4kYQ4+MpMbYQCgmf6RwCUEo9RRw3hfzNz15B+a MT0An1BqeA6wUOQnIFZJ4mRBjJJw37Gc =ac1p -----END PGP SIGNATURE-----

2 1

Re: [Wikitech-l] Mobile gateway testing
by Chad 23 Feb '09

23 Feb '09

I think for anything other than casual browsing, using native clients would be better. Perfect use of the API. I've been trying to get one for Android into decent shape. -Chad On Feb 19, 2009 6:03 PM, "Brion Vibber" <brion(a)wikimedia.org> wrote: On 2/19/09 4:14 AM, Angela wrote: > On Thu, Feb 19, 2009 at 9:42 PM, David Gerard<dgerard(a)gmail.com>... That depends on how many people have been announcing new mobile platforms. :) In this work we're mainly targeting the popular has-a-good-browser smartphones. These will be able to do decent editing at least for little bits here and there, and creating a decent interface for doing that -- commenting, typo-fixing, slapping up pictures, maybe taking notes for later "serious" editing -- would be great. The first attack surface is a decent read-and-search UI, of course, since that's going to be the biggest use. -- brion _______________________________________________ Wikitech-l mailing list Wikitech-l(a)lists.wikimedia....

2 1

Bugzilla Weekly Report
by reporter＠isidore.wikimedia.org 23 Feb '09

23 Feb '09

MediaWiki Bugzilla Report for February 16, 2009 - February 23, 2009 Status changes this week Bugs NEW : 219 Bugs ASSIGNED : 11 Bugs REOPENED : 22 Bugs RESOLVED : 111 Total bugs still open: 3308 Resolutions for the week: Bugs marked FIXED : 75 Bugs marked REMIND : 0 Bugs marked INVALID : 10 Bugs marked DUPLICATE : 11 Bugs marked WONTFIX : 10 Bugs marked WORKSFORME : 6 Bugs marked LATER : 3 Bugs marked MOVED : 0 Specific Product/Component Resolutions & User Metrics New Bugs Per Component General/Unknown 8 Special pages 5 Site requests 5 Internationalization 4 Page rendering 4 New Bugs Per Product MediaWiki 39 Wikimedia 12 MediaWiki extensions 13 Wikipedia Mobile 2 Top 5 Bug Resolvers innocentkiller [AT] gmail.com 13 niklas.laxstrom [AT] gmail.com 12 Andrew [AT] epstone.net 10 tstarling [AT] wikimedia.org 10 roan.kattouw [AT] home.nl 9

1 0

Wikimania 2009: Call for Participation
by Casey Brown 22 Feb '09

22 Feb '09

Apologies in advanced for the cross-posting. :-) Please circulate this call among Wikimedia communities, researchers and other people that may be interested! This call is also online at http://wikimania2009.wikimedia.org/wiki/Call_for_Participation == Call for Participation == Wikimania is an annual global event devoted to Wikimedia projects around the globe (including Wikipedia, Wikibooks, Wikisource, Wikinews, Wiktionary, Wikiversity, Wikiquote, Wikispecies, and Wikimedia Commons). The conference is a community gathering, giving the editors and users of Wikimedia projects an opportunity to meet each other, exchange ideas, report on research and projects, and collaborate on the future of the projects. The conference is open to the public, and is a chance for educators, researchers, programmers and free culture activists who are interested in the Wikimedia projects to learn more and share ideas about the Wikimedia projects. This year's conference will be held from '''August 26-28''' in Buenos Aires, Argentina at '''San Martín Cultural Center'''. For more information, please visit the official Wikimania 2009 site at http://wikimania2009.wikimedia.org. We are accepting submissions for presentations, workshops, panels, posters, open space discussions, and artistic works related to the Wikimedia projects or free content topics in general. Please carefully follow the submission guidelines below. === Important dates === * '''Submissions will open on:''' March 1 * '''Deadline for submitting workshop, panel, and presentation submissions:''' April 15 * '''Deadline for submitting posters, open space discussions, and artistic works:''' April 30 * '''Notification of acceptance of workshops, panels, presentations:''' May 15 * '''Notification of acceptance of posters, discussions, and artistic works:''' May 31 * '''Conference dates:''' August 26-28 === Themes and tracks === There are two tracks for submission: the '''Casual Track''', for members of wiki communities and interested observers to share their own experiences and thoughts and to present new ideas; and the '''Academic Track''', for research based on the methods of scientific studies exploring the social, content or technical aspects of Wikipedia, the other Wikimedia projects, or other massively collaborative works, as well as open and free content creation and community dynamics more generally. Submissions to either track should address one or more of the following themes: * '''"Wikimedia Communities,"''' including the topics of conflict resolution and community dynamics; reputation and identity; multi-lingualism and languages and cultures. * '''"Free Knowledge,"''' including open access to information; ways to gather and distribute free knowledge, use of the Wikimedia projects in education, journalism, research; ways to improve content quality and usability. * '''"Latin American challenges,"''' centering on efforts and limitations for expanding the reach of Wikimedia projects in Latin America; promotion of projects in Native American languages; specific problems of the Spanish and Portuguese-speaking Wikimedia communities. * '''"Technical infrastructure,"''' including issues related to MediaWiki development and extensions; Wikimedia's technical infrastructure; and new ideas for development. Papers should be of interest to members of the Wikimedia communities, and fit within one of the themes above. === Types of Submissions === We are seeking submissions for: * '''Presentations''' (10–30 minute talks with discussion afterwards) :* This type of submission is appropriate for presenting substantial research or community projects * '''Workshops''' (60–120 minute session with a discussion leader and more audience involvement) :* This type of submission is appropriate for sessions designed to teach a specific subject or explore it in depth * '''Panels''' (group of 2-5 speakers to discuss aspects of a topic with audience questions, 45-90 minute sessions) :* This type of submission is appropriate for discussions on a topic of wide interest among community members, with several participants who may be presenting their work. For less formal discussions of limited interest, consider an open space discussion instead. * '''Open space discussions''' (informal discussion on a specific topic; the discussion leader helps moderate the conversation but the session is open to anyone interested to join in) :* This type of submission is good for a topic that several participants want to discuss or brainstorm about in an informal setting * '''Posters''' (printed visual displays that can stand on their own, with no associated presentation) :* This type of submission is good for presenting research in progress, or smaller community projects * '''Artistic works''' (plays, competitions, comedy, visualizations, displays or other representations of some aspect of the projects) :* This type of submission is good for showing creativity or showcasing beautiful work about the projects. In addition there will be the chance to give lightning talks, which are 5-minute short presentations. Lightning talk sessions will be organized on the Wikimania 2009 wiki shortly before the conference begins, without any need to submit them via the submission system. These talks are best for those who want to quickly present an idea or project without giving a formal presentation. These are informal talks that are open to everyone to participate in. === Submission Guidelines === Wikimania is organized by volunteers, so please help us minimize wasted effort by submitting via the submission system and following these guidelines. All submissions MUST include the following: # '''Event title:''' an English or Spanish title. # '''Abstract:''' a short English or Spanish abstract of your event in 50 to 100 words. The abstract will be used for the public schedule. # '''Themes and track:''' list the track you wish to submit to (Casual or Academic) and the single theme you think your submission fits in best (Wikimedia Communities, Free Knowledge, Latin American challenges, Technical infrastructure). Note that posters and artistic works have their own track in the submission system. # '''Information about the speaker:''' full name, email, and a short biography. # '''Submission file:''' A plain text, PDF or OpenDocument file, in English or Spanish, containing: #* '''A long description of the submission''', in English or Spanish that can be used for reviewing, not to exceed 1000 words. Please give an overview of the areas to be covered or taught. State clearly the relevance to the Wikimedia projects and whether submission concerns a specific wiki project. You can also include links, Include graphics an diagrams if they do not exceed one page. #* '''Event type:''' please state if the event is a presentation, workshop, panel, open space discussion, poster, or artistic work; if a presentation or panel, whether the presentation is expected to be a certain length. #* '''For panel submissions only:''' name of a suggested moderator and short biographies of each suggested panelist #* '''Language:''' list the language you plan to present in. The conference will be bilingual in English and Spanish. #* '''Special requirements:''' list any special requirements, including any equipment. In the "Comments for conference director" field you should tell us whether you will attend to Wikimania (a) surely, (b) probably, (c) only if your submission is accepted, or (d) only if we provide travel and/or accommodation. You can also add yourself to the public list of attendees at the Wikimania 2009 wiki: http://wikimania2009.wikimedia.org/wiki/Attendees Please note that all submissions must be dual licensed under the GNU Free Documentation License version 1.2 or later ''and'' the Creative Commons Attribution-Share Alike 3.0 3.0! By submitting for Wikimania 2009 you agree to this condition. ===Submissions=== Once you are sure you have included all of the required information, please send your submission before the respective deadline through our '''submission system''': http://wikimania2009.wikimedia.org/wiki/Submission If you have further questions, email wikimania-program(a)wikimedia.org (in English or Spanish).

1 0

Norwegian Websites Declare War on Internet Explorer 6
by GerardM 22 Feb '09

22 Feb '09

Hoi, Would this be a model to follow ? Thanks, GerardM Aan u verzonden door GerardM via Google Reader: Norwegian Websites Declare War on Internet Explorer 6 via Wired Top Stories door Michael Calore op 19-2-09 Several prominent websites in Norway are refusing to support the antiquated IE6 browser any longer, and have posted messages to IE6 users urging them to upgrade. The campaign has caught on, and is beginning to spread to other countries. Dingen die u vanaf hier kunt doen: - Abonneren op Wired Top Stories met Google Reader - Aan de slag met Google Reader om eenvoudig al uw favoriete sites bij te houden

10 19

Wikipedia giving 403 Forbidden
by jidanni＠jidanni.org 21 Feb '09

21 Feb '09

$ HEAD -PS http://en.wikipedia.org/ HEAD http://en.wikipedia.org/ --> 403 Forbidden Connection: close Date: Sat, 21 Feb 2009 19:49:14 GMT Via: 1.0 sq29.wikimedia.org:80 (squid/2.7.STABLE6) Server: squid/2.7.STABLE6 Content-Length: 59481 Content-Type: text/html Client-Date: Sat, 21 Feb 2009 19:49:14 GMT Client-Peer: 208.80.152.2:80 Client-Response-Num: 1 X-Cache: MISS from sq29.wikimedia.org X-Cache-Lookup: NONE from sq29.wikimedia.org:80 X-Squid-Error: ERR_ACCESS_DENIED 0 Tried from both California and Taiwan.

2 1

on yesterday's trouble
by Domas Mituzas 21 Feb '09

21 Feb '09

Though the were very interesting hardware fireworks yesterday, the actual reason of slowdown was way way more prosaic. First of all, site didn't crash, it just gradually slowed down. It took us a while to actually notice the slowdown (at least half an hour since the problem started). Second, mostly it wasn't our mediawiki/extensions codebase hitting the issue. Though of course, there were some extensions that could've triggered same behavior, the reason was a little bit more complicated from development perspective (or easier from system administration perspective). PHP calls external programs using 'sh -c', which doesn't simply check current directory by checking getcwd(), but it also gets environment variable $PWD too. This is where interesting part begins, Apache does change current working directory, but doesn't change environment variable, when it is started. We regularly start and stop and start and stop our application servers, and usually that is done while being in ~ (which is on NFS). What happened then, is that sometimes apache children call external programs, so some requests end up blocking on NFS. This consumes more and more of worker processes, until there're none left to serve the site. So, in the end, it is a mixture of unexpected behavior, incomplete behavior, NFS suck, etc. We didn't have strong push to have HA-NFS simply because our application does not rely on it too much anymore. We just didn't know that OS can give us surprises like that ;-) (and the hardware issues were resolved by flashing service processor / BIOS / RAID controller with new firmware, or so it seems, maybe even harder reboot helped - might be that we still have some issues there, but at least they will be more manageable). -- Domas Mituzas -- http://dammit.lt/ -- [[user:midom]]

1 0

← Newer
1
2
3
4
5
6
7
...
11
Older →

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 February 2009