Wanted to do a quick mention of the updated mwEmbed gadget and subtitles
support on the email list(s) in case people have missed its mention on
the village pump [1] or other venues.
* On commons the "Commons:Timed_Text" and "Template:Closed_cap" have
been started.
* oggHandler has been patched to support "itext" [2], [3] output so that
it would not need to hit the api to get the list of available subtitles
when we are embedding locally. Remote embedding outside of wikimedia
domain grabs the up-to-date list of available tracks via an api call.
* A basic "Add timed text" interface is accessible from the "cc" button
letting you "upload" an srt file.
* If you enable the mwEmbed gadget on English wikipedia ( or other
wikipedias ) it will display commons subtitles in the respective
wgUserLanguage. ( Interface translations are temporarly dissabled per
bug 21947 which should be "resolvable" as soon as the release is branched.
* Even with extremely limited exposure the number of subtitle files is
starting to grow: [4]
* The timedText display supports inline "wiki-text" so persons names,
subjects and place of interest can be linked to their respective
wikpedia articles in their respective languages from the srt text. [5]
* Gadget feedback has been very good. Big thanks to all that have helped
test and especially User:84user with his very detailed reports ;)
And finally .. I imagine it ~may~ take some time before the mwEmbed
stuff makes its way through code review and on by default deployment
because of release branching and mwEmbed includes quite a few other
components ... But similar to usability beta, and other gadgets we could
let people do a much easier opt in. Which I will continue to look into
in the mean time.
peace,
michael
[1]
http://commons.wikimedia.org/wiki/Commons:Village_pump#Improved_Close_Capti…
[2] http://www.annodex.net/~silvia/itext/
[3] http://www.mediawiki.org/wiki/Special:Code/MediaWiki/60458
[4]
http://commons.wikimedia.org/w/index.php?title=Special%3AAllPages&from=&to=…
[5]
http://commons.wikimedia.org/wiki/File:Yochai_Benkler_-_On_Autonomy,_Contro…
**
One of these days mailman will learn to reject these
things :)
-Chad
On Dec 27, 2009 11:44 PM, "Soxred93" <soxred93(a)gmail.com> wrote:
*facepalm*
On Dec 27, 2009, at 10:08 PM, Naresh.Kumar.Nayyar(a)us.elster.com wrote: > > I
am out of the office...
I am out of the office until 12/29/2009.
Hi,
I am on vacation till 12/29/09.
For any queries please contact Vinod Gundelli / Sean M Scoggins.
Thanks
Naresh Nayyar
Note: This is an automated response to your message "[Wikitech-l] Bugzilla
Weekly Report" sent on 12/27/2009 10:00:02 PM.
This is the only notification you will receive while this person is away.
What ideas have been tried or suggested in using
visualization as an aid in Wikipedia? For example,
could the articles of a category be summarized as
an image that would provide new insights to the
user, either encyclopedia reader or writer?
When scanned books are proofread in Project Runeberg
(runeberg.org, a website similar to Wikisource),
a horizontal bar graph is used to indicate which
pages have been proofread or not, with one pixel
for each page of the book (so 500 pixels wide for
a 500 page book), with green pixels for proofread
pages and red pixels for not yet proofread pages.
Here is an example of a partially proofread 2 volume
work, at the bottom, http://runeberg.org/bokogbib/
Could something similar be useful in Wikipedia?
Perhaps for overview of maintenance categories?
Are there any tools at the toolserver that do
such things? Has that been tried?
The various (humorous) Size-of-Wikipedia pictures
come to mind,
http://commons.wikimedia.org/wiki/File:Size_of_English_Wikipedia_broken_dow…http://commons.wikimedia.org/wiki/File:Size_of_Wikipedia_broken_down.svg
--
Lars Aronsson (lars(a)aronsson.se)
Aronsson Datateknik - http://aronsson.se
Hi all,
With the Foundation's support, I've spent the last few months churning
away at LiquidThreads [1], a new discussion system that is proposed for
use on Wikimedia projects.
Essentially, it's an attempt to marry the radical openness of the wiki
paradigm with the usability and practicality of a forum-like system. As
the name implies, LiquidThreads is designed to allow any user to easily
refactor discussions while maintaining edit history, to edit other
users' comments, and to collaborate on a summary of an ongoing
discussion. LiquidThreads also brings many standard communication
features lacking from wiki discussion pages, such as watching and
protecting individual discussion threads, RSS feeds of comments in a
discussion or on a discussion page. In the world of online
communication, its approach is entirely unique.
LiquidThreads has been in alpha testing on Wikimedia Labs [2] for
several months, and, more recently, it's been used in a production
context on the strategy wiki, where it has been quite well-received.
It's been easy to run these smaller trials, as the extension allows the
activation and deactivation of LiquidThreads discussions on individual
pages with a simple parser function.
While there are still some issues remaining before wider trials, I
believe I can resolve most of them quite quickly (within a few weeks
when my vacation finishes at the end of next month), and I'd like to get
the ball rolling in proposing small-scale trials on some of the larger
wikis, so that a full discussion can be had, and so that adjustments can
be made on the basis of ongoing feedback. I'd especially like to see
LiquidThreads used on some of the higher-traffic discussion pages on
English Wikipedia (such as the technical village pump), and progressive
rollout on some of our mid to large sized wikis.
So, I'd like to encourage you to have a play with LiquidThreads, either
on the strategy wiki or on the test site (which generally runs a newer
version). Tell me what you like about it, and (far more importantly)
what improvements you think it needs before we can expand our trials to
wider parts of the Wikimedia Universe, and perhaps move towards a full
rollout of this very exciting technology.
I should give the following caveats about LiquidThreads as it stands.
These are all issues that I intend to address before any trial expansion
occurs.
* Presently the system is somewhat vulnerable to abuse. I intend to make
changes to the way signatures work, and improve tracking and listing of
thread actions by specific users.
* While LiquidThreads allows for thread summaries and discussion
headers, the system does not currently have support for
collaboratively-edited posts which are unsigned or signed by a group of
people. These are a key piece of any decision-making framework, and I
intend to make adjustments to make this possible.
* There is no support for embedding LiquidThreads discussion pages on
other pages.
* There are plenty of minor interface issues which I intend to clean up.
Feedback is best directed to the dedicated Feedback page [3], or,
alternatively, to bugzilla [4] (although before filing a bug, you should
check the list of existing LiquidThreads bugs [5]).
[1] http://www.mediawiki.org/wiki/Extension:LiquidThreads
[2] http://liquidthreads.labs.wikimedia.org
[3] http://liquidthreads.labs.wikimedia.org/wiki/Feedback
[4]
https://bugzilla.wikimedia.org/enter_bug.cgi?product=MediaWiki%20extensions…
[5]
https://bugzilla.wikimedia.org/buglist.cgi?product=MediaWiki%20extensions&c…
--
Andrew Garrett
agarrett(a)wikimedia.org
http://werdn.us
Hello all,
I'm very pleased to welcome Priyanka Dhanda to the Wikimedia
Foundation as Code Maintenance Engineer. Priyanka joins us from
SourceForge Inc., where she worked since 2002 as a software developer
and also was involved in operations, working on most pieces of the
infrastructure, and integrating third party software with the
SourceForge platform (including MediaWiki). Priyanka holds a Master's
Degree in Computer Science from the University of Toledo, Ohio, and a
Bachelor of Technology in Computer Science and Engineering from the
Pondicherry Engineering College in India.
She is starting today and will work in the San Francisco office.
Priyanka will be a key interface between software developers and the
operations team, helping us to catch up with our code and bug review
backlog, to mentor new developers, to push projects to completion, and
to improve testing and automation. Please don't swamp her immediately
with requests as she'll need some time to get more deeply oriented in
the MediaWiki codebase. :-) You'll be seeing her in the IRC channels,
on SVN, Code Review, BugZilla, wikitech-l, and so forth.
Please join me in welcoming Priyanka to the Wikimedia team! :-)
All best,
Erik
--
Erik Möller
Deputy Director, Wikimedia Foundation
Support Free Knowledge: http://wikimediafoundation.org/wiki/Donate
Hi all,
I have to restrict, in my corporate lan networtk, the rights.
I have mediawiki 1.13.2 and, by now, I can't upgrade it.
I don't need a hacker proof system to handle user rights, but
something easy to install and use.
group1 (user1+user2+ .. +userk)
read and write on all mediawiki
group2 ( user(k+1) .. userN )
read and write on a subset of documents inside the same mediawiki.
namespace is the right tecnology?
any suggestion?
Thx
--
www.opensurf.it
Guess this problem might be asked several (many) times before...but
I tried to download the pages-articles.xml.bz2 file which is approximately
5.xGB. However, all versions I tried failed at about 1.5GB. I noticed
someone posted a Python code online as a workaround, but it did not work for
me.
My machine is Windows Server 2008 64 bit. Any idea how to get this huge
file?
Appreciated.
Rob
