A brief note to talk about the progress and status of the share  and
embed  features of MultimediaViewer, why they're taking so bloody long,
and what's left to sort out.
I've written out the interfaces, most of the code handling thumbnail URL
fetching, size determinations, and (en|dis)abling various interface things
depending on what the selections are currently. You can currently open
the panel and get HTML that works, Wikitext that works, and a link that
The problems that remain are basically making sure you can get the embed
codes that you want, instead of ones you don't, and making sure the stuff
you select is what actually gets applied to the code.
We also are looking towards having tests available for all of these things
so it's not terribly difficult to maintain, and I also want to split the
code into multiple different files so I don't have to maintain a single,
intractable 800+ line file with all different parts of the panel in it.
Those parts may be split off and merged later in the week, though.
If you're curious about the work currently being done on these features,
you can look at the open WIP patchset on Gerrit , ask questions here,
or corner the developers on IRC .
 #wikimedia-multimedia on irc.freenode.net 
 'Play "stomp the developers" live on irc://irc.freenode.net/#mediawiki!' 
Software Engineer, Multimedia
We’d like to give you a quick update on Media Viewer and get your feedback on next steps, as we get ready to release it more widely.
We have been making good progress with beta version v0.2 of Media Viewer (1), with a focus on a better user interface, faster image load, more file info and attributions -- as well as improved 'Use this file' tools (e.g.: share, embed, download).
2. Release Plan
In coming weeks, we plan to release this version v0.2 gradually out of beta, starting with limited tests on a few pilot sites at the end of this quarter. Based on pilot test results, we plan a wider release of Media Viewer v0.2 next quarter. We’d appreciate your comments on our proposed release plan (2). Is there anything we could do to improve it? Anything missing? Note that this version only supports the most widely used image file formats — other media types such such as audio, video or PDF slides will be supported in future releases.
We would be grateful if you could help us test the latest beta version, by following our simple testing tips (3). Note the latest features can be found on our beta site, but it is very slow. For better performance, you can test last week’s features on MediaWiki.org. We release every Thursday on MediaWiki.org, then Monday on Commons and sister sites, then the following Thursday on all wikis.
After you’ve tried the latest version, we would love to hear your feedback on our Media Viewer discussion page (4), so we can address the most critical issues before wider deployment. Note that we still have a lot of work to do, so we may not be able to address all your suggestions right away.
5. Pilot sites
We are now approaching a few pilot sites to test Media Viewer by default at the end of March. Would you recommend pilot sites that you think would be open to experimenting with this feature early? We are looking for small sites with tech-savvy communities that are open to new features. So far, we’ve reached out to French, Hungarian, Korean, Polish, Swedish and Vietnamese community members who expressed interest in this project. Anyone else we should be contacting? (e.g. non-Wikipedia site)
6. Key features
Are there any key features you think are needed before we turn on Media Viewer by default for all users? For example, do you think we need to offer an opt-out preference for people who don't want this feature? (We’re not sure this preference is needed, because you can already shift-click or control-click to bypass Media Viewer and open files directly on Commons — but we would like to hear what you and others think.) Anything else that you consider a must-have feature for wider deployment?
We are grateful to all the community members who helped create this tool. This product was developed in discussions held throughout 2013 (5) — and we then received invaluable feedback (6) from some of the 12,000+ beta testers who enabled Media Viewer around the world since November. The suggestions they kindly gave us have helped improve this tool and many of them are now being implemented, as part of our current release plan (7).
We really appreciate your wonderful contributions and look forward to our next steps together — so we can all bring a better multimedia experience to our users!
Fabrice, on behalf of the Multimedia Team
(1) About Media Viewer:
(2) Media Viewer Release Plan:
(3) How to test Media Viewer
(4) Media Viewer Discussion Page:
(5) Multimedia Roundtables:
(6) Community Feedback:
(7) Current Release Tasks (Mingle):
Product Manager, Multimedia
the Multimedia team had some discussions recently about how to make our
work more transparent and more open to volunteers, and we decided to try
using an open subscription mailing list for team discussions, instead of
the current practice of cc-ing each member manually. These discussions are
about day-to-day details of our work; sometimes feature requirements or
design, sometimes technical details. The volume is typically one or two new
threads per day.
We weren't sure how much members of this list would be interested in such
conversations and didn't want to flood this list with mails that are not
useful for most members, but we also do not want to split conversation
channels unnecessarily. Please help us by telling whether you would be
interested in the topics mentioned above, or would prefer if we created a
new mailing list for them.
In case anybody's interested but not on wikitech-l; looking for some
feedback on possible directions for fallback in-browser video players.
---------- Forwarded message ----------
From: Brion Vibber <bvibber(a)wikimedia.org>
Date: Sun, Feb 23, 2014 at 6:43 AM
To: Wikimedia-tech list <wikitech-l(a)lists.wikimedia.org>
Just an update on this weekend project, see the current demo in your
browser or watch a video of Theora video playing on an iPhone 5s!
* Got some fixes and testing from one of the old Cortado maintainers --
* Audio/video sync is still flaky, but everything pretty much decodes and
plays properly now.
* IE 10/11 work, using a Flash shim for audio.
* OS X Safari 6.1+ works, including native audio.
* iOS 7 Safari works, including native audio.
Audio-only files run great on iOS 7 devices. The 160p video transcodes we
experimentally enabled recently run *great* on a shiny 64-bit iPhone 5s,
but are still slightly too slow on older models.
The Flash audio shim for IE is a very simple ActionScript3 program which
accepts audio samples from the host page and outputs them -- no proprietary
or patented codecs are in use. It builds to a .swf with the open-source
Apache Flex SDK, so no proprietary software is needed to create or update
I'm also doing some preliminary research on a fully Flash version, using
the Crossbridge compiler for the C codec libraries. Assuming it performs
about as well as the JS does on modern browsers, this should give us a
fallback for old versions of IE to supplement or replace the Cortado Java
player... Before I go too far down that rabbit hole though I'd like to get
peoples' opinions on using Flash fallbacks to serve browsers with open
As long as the scripts are open source and we're building them with an open
source toolchain, and the entire purpose is to be a shim for missing
browser feature support, does anyone have an objection?
On Mon, Oct 7, 2013 at 9:01 AM, Brion Vibber <bvibber(a)wikimedia.org> wrote:
> TL;DR SUMMARY: check out this short, silent, black & white video:
> https://brionv.com/misc/ogv.js/demo/ -- anybody interested in a side
> project on in-browser audio/video decoding fallback?
> One of my pet peeves is that we don't have audio/video playback on many
> systems, including default Windows and Mac desktops and non-Android mobile
> devices, which don't ship with Theora or WebM video decoding.
> The technically simplest way to handle this is to transcode videos into
> H.264 (.mp4 files) which is well supported by the troublesome browsers.
> Unfortunately there are concerns about the patent licensing, which has held
> us up from deploying any H.264 output options though all the software is
> ready to go...
> While I still hope we'll get that resolved eventually, there is an
> alternative -- client-side software decoding.
> We have used the 'Cortado <http://www.theora.org/cortado/>' Java applet
> to do fallback software decoding in the browser for a few years, but Java
> applets are aggressively being deprecated on today's web:
> * no Java applets at all on major mobile browsers
> * Java usually requires a manual install on desktop
> * Java applets disabled by default for security on major desktop browsers
> years, and performance is getting well in line with what Java applets can
> As an experiment, I've built Xiph's ogg, vorbis, and theora C libraries
> draws the frames into a <canvas> element:
> * demo: https://brionv.com/misc/ogv.js/demo/
> * code: https://github.com/brion/ogv.js
> * blog & some details:
> It's just a proof of concept -- the colorspace conversion is incomplete so
> it's grayscale, there's no audio or proper framerate sync, and it doesn't
> really stream data properly. But I'm pleased it works so far! (Currently it
> breaks in IE, but I think I can fix that at least for 10/11, possibly for
> 9. Probably not for 6/7/8.)
> Performance on iOS devices isn't great, but is better with lower
> resolution files :) On desktop it's screaming fast for moderate
> resolutions, and could probably supplement or replace Cortado with further
> Is anyone interested in helping out or picking up the project to move it
> towards proper playback? If not, it'll be one of my weekend "fun" projects
> I occasionally tinker with off the clock. :)
> -- brion
We invite you to join our IRC chat about Media Viewer (1), today at 18:00 UTC on #wikimedia-office (2)
We will discuss new features for this multimedia browser, which we developed based on feedback from community and team members like you. Here’s what we’re working on now: faster image load, better user interface, more meta-data, attribution and permissions -- and an improved ‘use this file’ tool with share, embed and download options.
Even if you can’t join the IRC chat, we encourage you to participate on our discussion page for Media Viewer (3), where new features are regularly updated. We would love it if you could try the ones labeled ‘ready for testing’. You can also review our specifications for features that are ‘coming soon’ — and hope you can help test them as well later this month (we release new code every Thursday).
In coming weeks, we will be completing the main features of beta version v0.2, and aim to release it on a few pilot sites at the end of the quarter — with a wider release next quarter. We are also starting design work on the next version v0.3, which will support more media file formats such as audio and video, to be developed next quarter. (4)
We look forward to discussing this project with you via IRC in an hour — and on our discussion page on an ongoing basis. This is a good opportunity to improve these features together — so we can provide a better experience for all our users.
All the best,
on behalf of the Multimedia Team (5)
(1) About Media Viewer:
(2) Media Viewer Chat on IRC:
(3) Media Viewer Discussion page:
(4) Media Viewer Next Version v0.3:
(5) Multimedia Project Hub:
Product Manager, Multimedia
HelloI would give to propose a discussion for the Allow smoother and easier Wikimedia Commons pictures discovery as a part of GSOC-2014 entry the link to the proposal is :https://www.mediawiki.org/wiki/Allow_smoother_and_easier_Wikimedia_Commons_pictures_discovery
I therefore request all the members to please go through the proposal and give your valuable suggestions to improve the proposal
Thank YouAalekh Nigam