Wikitech-l January 2009

wikitech-l@lists.wikimedia.org

94 participants
87 discussions

download the whole wiki with one click
by jidanni＠jidanni.org 11 Jan '09

11 Jan '09

Gentlemen, let's say one is afraid one day the forces of evil will confiscate one's small wiki, so one wants to encourage all loyal users to keep a backup of the whole wiki (current revisions fine, no need for full history). OK, we want this to be as simple as possible for our loyal users, just one click needed. (So forget Special:Export!) And, we want this to be as simple as possible for our loyal administrator, me. I.e., use existing facilities, no cronjobs to run dumpBackup.php (or even mysqldump, which would be giving up too much information) and then offering a link to what they produce. The format desired is for later making a new wiki via Special:Import, so indeed the Special:Export or dumpBackup.php --current outputs are the desired format. I just can't figure out the right http://www.mediawiki.org/wiki/API URL recipe... api.php ? action=query & generator=allpages & format=xmlfm & ...? Could it be that the API lacks the "bulk export of XML formatted data" capability of Special:Export? If one click is not enough, then at least one click per Namespace. I would just have the users backup Main: and Category:, for example. Embedding the API URL would be no problem, I would just use [{{SERVER}}/api.php?... Backup this whole site to your disk]

2 1

Now hiring for Wikipedia Usability Initiative
by Brion Vibber 09 Jan '09

09 Jan '09

I'm very happy to announce that the Wikimedia Foundation is now opening hiring for the Wikipedia Usability Initiative! Realized by a grant from the Stanton Foundation, the goal of this initiative is to measurably increase the usability of Wikipedia for new contributors by improving the underlying software on the basis of user behavioral studies, thereby reducing barriers to public participation. We have three positions open, all local in San Francisco. See the linked pages for details and how to submit your CV: http://wikimediafoundation.org/wiki/Job_openings/Interaction_Designer_(proj… http://wikimediafoundation.org/wiki/Job_openings/Sr._Software_Developer_(pr… http://wikimediafoundation.org/wiki/Job_openings/Software_Developer_(projec… The new team will be lead by project manager Naoko Komura, who was very helpful in organizing localization and translations for our recent fundraiser, and will coordinate closely with me and the rest of Wikimedia's core developers. Also joining the project will be Wikimedia staff developer Trevor Parscal. As always, all of Wikimedia's software development is open-source, and we expect to be able to roll improvements into the live Wikipedia environment and general MediaWiki releases over the course of the project. -- brion vibber (brion @ wikimedia.org) CTO, Wikimedia Foundation San Francisco

7 10

enable $wgAllowCopyUploads on wikimedia projects?
by Michael Dale 09 Jan '09

09 Jan '09

Can we look into enabling $wgAllowCopyUploads on Wikimedia projects? This will let Wikimedia work a lot better with external archives especial around large video files that are cumbersome for users to download and then upload over our POST upload interface on home Internet connections. In particular archive.org huge repository of public domain and free licensed footage now support temporal urls for video: http://metavid.org/blog/2008/12/08/archiveorg-ogg-support/ not to mention adding some clips from metavid's public domain legislative collection to relevant articles ;) As I understand we need to set up a proxy for the internal apache nodes to access the outside web? Who can look at enabling this? peace, --michael

2 2

Exposing uselang to CSS
by Remember the dot 09 Jan '09

09 Jan '09

Would it be possible to make MediaWiki expose the intended user interface language via CSS? Being able to do something like html.uselang-de #p-navigation h5 { text-transform: none; } would make it easy to solve bug 1553, "Navigation headings should not be lower-cased in German": https://bugzilla.wikimedia.org/show_bug.cgi?id=1553 -- Remember the dot http://en.wikipedia.org/wiki/User:Remember_the_dot

3 3

api file uploading
by Michael Dale 09 Jan '09

09 Jan '09

For use in both the external media wizard http://lists.wikimedia.org/pipermail/wikitech-l/2009-January/040858.html and the firefogg in-browser transcoder & up-loader /with progress bar/: https://bugzilla.wikimedia.org/show_bug.cgi?id=16927 http://lists.wikimedia.org/pipermail/wikitech-l/2008-December/040524.html We could really use the addition of file uploading support to the API. This would also be helpful for cell phone image type applications no? Is there anyone actively looking into such a development? Any tips if I take that on? peace, --michael

7 7

nstab-main caching
by Remember the dot 08 Jan '09

08 Jan '09

Hello, The discussion about nstab-main and the main page has flared up again: http://en.wikipedia.org/wiki/MediaWiki_talk:Common.js#Main_Page_tab It was suggested in bug 14267 that the contents of nstab-main could be cached with the page title, so that we could include a ParserFunctions workaround in it without having the parser function execute on every page load. What are your opinions on this? See https://bugzilla.wikimedia.org/show_bug.cgi?id=14267#c5 -- Remember the dot http://en.wikipedia.org/wiki/User:Remember_the_dot

7 10

Fw: StringFunctions
by Jason Schulz 08 Jan '09

08 Jan '09

-------------------------------------------------- From: "Greg L" <greg_l_at_wikipedia(a)comcast.net> Sent: Thursday, January 08, 2009 2:43 PM To: "Voice of All" <jschulz_4587(a)msn.com> Subject: StringFunctions > JSchulz: > > Have you read the link here: > http://en.wikipedia.org/wiki/Wikipedia_talk:Manual_of_Style_(dates_and_numb… > > …describing a scientific notation-formatting template? It could use a > character-counting parser function that StringFunction could handle if it > worked well (which it doesn’t). > > I ran this by Jimbo and he thought having a character-counting parser > function for Wikipedia made sense. He said he couldn’t pressure Wikipedia’s > paid developers to make it and I should run it by Erik to see how he > would like to have it handle. Erik referred me to wikitech. > > Do you have a volunteer developer in mind who might be interested in > making StringFunction bullet-proof? > > Greg

1 0

Character-counting parser function
by Greg L 08 Jan '09

08 Jan '09

Hi, I’m new to this venue so please have patience with me. Jimbo suggested I contact Erik and Erik said I should post here. Wikipedia authors of magic words and templates could really use a character-counting parser function. All the background information can be found here: http://en.wikipedia.org/w/index.php?title=User_talk:Jimbo_Wales&oldid=26081… - Developer_support_for_parser_function In a nutshell though, there is currently a template on en.Wikipedia called {{val}} that delimits numbers (places what appears to be thinspaces very three characters in scientific notation). It currently must use math-based techniques to parse the value and this results in rounding errors 5–10% of the time. A character-counting parser function would accept interrogations such as “Are there more than four characters remaining in the string when counting right from the decimal point?” And “If so, feed me three more characters.” Such a parser function would be very handy for many other purposes. With a good, bullet-proof parser function, our small army of template authors could produce some nice new tools. I can be reached at Greg_L_at_Wikipedia(a)comcast.net Greg

6 9

Bugzilla Weekly Report
by reporter＠isidore.wikimedia.org 08 Jan '09

08 Jan '09

MediaWiki Bugzilla Report for December 29, 2009 - January 05, 2009 Status changes this week Bugs NEW : 0 Bugs ASSIGNED : 0 Bugs REOPENED : 0 Bugs RESOLVED : 0 Total bugs still open: 3167 Resolutions for the week: Bugs marked FIXED : 0 Bugs marked REMIND : 0 Bugs marked INVALID : 0 Bugs marked DUPLICATE : 0 Bugs marked WONTFIX : 0 Bugs marked WORKSFORME : 0 Bugs marked LATER : 0 Bugs marked MOVED : 0 Specific Product/Component Resolutions & User Metrics New Bugs Per Component New Bugs Per Product Top 5 Bug Resolvers

5 4

Re: [Wikitech-l] [Commons-l] default quality for ogg content?
by Michael Dale 08 Jan '09

08 Jan '09

You would not want to hard code the |high quality or |low quality version to the article / wiki syntax. The idea is that you just put something like [[Stream:my_movie]] or [[File:my_movie.ogg]] (in your example) and then based on the client bandwidth, client supported codecs, local language, and client player preference and the available streams on the server the javascript player choses the appropriate set of video, audio, and text streams to playback. Its not quite the same problem as existing File namespace transformations system. Same temporal meaning files are not _only_ files programmability transcoded from a single my_video.ogg source. Its different from the thumbnails or flattened SVGs derivatives. Aside from the issue of associating dubbed audio tracks, Users will never upload their original HD footage because of bandwidth constraints and for maximum quality on the low-end version we want to create the low bandwidth derivatives from the original footage so the derivatives will not really be a "temporary file" that can easily be regenerated. We can certainly overload the File namespace as you suggest to enable such associations but the minimal hierarchy of a Stream namespace to associate specific identical temporal meaning files seems cleaner/worthwhile to me. It will mean that a single File: page will be associated with many actual "files" that may have different licenses etc. The stream namespace also contains interfaces for associated layers of timed text putting all those associations into the File namespace may complicate things but we can go that way if its the consensus. peace, --michael Platonides wrote: > Michael Dale wrote: > >> If we want to support multiple quality settings for a single "stream" >> this will require a bit more infrastructure. Specifically I propose we >> add another namespace for temporal media called Stream: and have it >> directly map to ROE xml something like: http://tinyurl.com/72x57r more >> info on ROE http://wiki.xiph.org/index.php/ROE >> >> File:my_movie_low_quality.ogg and File:my_movie_high_quality.ogg would >> soft redirect to Stream:my_movie and all the meta info would be stored >> there. The Stream namespace also allows us to group other media tracks >> that share a temporal meaning such as multiple language audio dubbing >> and multilingual transcripts/ subtitles. The javascript player can then >> dynamically select audio language and or subtitles based on the user >> language. >> > > No need. Users would use [[File:my_movie.ogg|high]] or > [[File:my_movie.ogg|low]] > The actual ROE file would be at > upload/thumb/f/fa/my_movie.ogg/my_movie-ROE.ogg (or > Special:MvExportStream as metavidwiki does) as other types do. Same for > the other temporary files. > > > _______________________________________________ > Commons-l mailing list > Commons-l(a)lists.wikimedia.org > https://lists.wikimedia.org/mailman/listinfo/commons-l >

1 0

← Newer
1
2
3
4
5
6
7
8
9
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 January 2009