Hello!
The Wikimedia Developer Summit
<https://www.mediawiki.org/wiki/Wikimedia_Developer_Summit> is the annual
meeting to push the evolution of MediaWiki and other technologies
supporting the Wikimedia movement. The next edition will be held in San
Francisco on January 9-11, 2017.
We welcome all Wikimedia technical contributors, third party developers,
and users of MediaWiki and the Wikimedia APIs. We specifically want to
increase the participation of volunteer developers and other contributors
dealing with extensions, apps, tools, bots, gadgets, and templates.
Important deadlines:
- Monday, October 24: This is the last day to request travel
sponsorship. Applying takes less than five minutes.
- Monday, October 31: This is the last day to propose an activity. Bring
the topics you care about!
Subscribe to weekly updates: https://www.mediawiki.org/
wiki/Topic:Td5wfd70vptn8eu4
Please feel free to forward this email to anyone who might be interested in
attending!
Thanks,
Srishti
--
Srishti Sethi
ssethi(a)wikimedia.org
Hi everyone,
are you coming to Esino Lario in June and looking for some interesting
things to do during Wikimania Pre-Conference? Well, perhaps this is for
you: like last year, we plan to host a workshop for creating animated
explainer videos for Wikimedia projects:
https://wikimania2016.wikimedia.org/wiki/Explainer_Video_Workshop
Videos have become a popular format for the dissemination of information
- especially short animated explainer videos which provide a quick
overview over complex topics. The same principle applies to Wikipedia:
videos can enrich exisiting content and provide an entertaining and
easily comprehensible access to free knowledge. Together with experts
from the simpleshow foundation Wikimedia Österreich offers workshops for
Wikimedians which are designed to learn the tricks of the trade of
screenwriting for explainer videos.
The workshop might also be interested for people who attended last year,
as we will also introduce a new freeware, which enables you to produce
the videos yourself!
Like the other submissions we need at least 3-5 interested Wikimedians
to sign up for the workshop. So please do so at the link above if you
are interested :-)
Content of the workshop
* Interested participants will learn the basic skills for creating
plots of explainer videos: how to explain complex topics in a short and
comprehensible way, how to work with cut-out animation, storyboard
conception and visualization.
* The participants can create and refine their scripts and
storyboards together with the simpleshow foundation after the workshop.
* Depending on the topic & previous research participants can turn
their scipts directly into an ilustrated video using
“mysimpleshow”-freeware.
* The realization and production of the finished storyboard could
be done either using the “mysimpleshow”-freeware or by the simpleshow
foundation. The result will be published under the CC-BY-SA license on
Wikimedia Commons.
* The screenwriters can use the videos for Wikipedia articles and
other purposes.
What do you need?
* Interest in storytelling
* A topic for an explainer video
* First research on the topic (Wikipedia article niveau)
* No previous knowledge in screenwriting or video production necessary
Please sign up here:
https://wikimania2016.wikimedia.org/wiki/Explainer_Video_Workshop
Claudia
--
Claudia Garád
Executive Director
Wikimedia Österreich - Verein zur Förderung Freien Wissens
Siebensterngasse 25/15
1070 Wien
0699 141 28615
www.wikimedia.at <http://www.wikimedia.at/>
I've gone ahead and merged these two changes by TheDJ to MwEmbedSupport and
TimedMediaHandler extensions (they are interdependent):
* https://gerrit.wikimedia.org/r/#/c/172556/
* https://gerrit.wikimedia.org/r/#/c/172421/
These clean up how TMH's JavaScript modules get integrated into MediaWiki's
ResourceLoader, and should both reduce weird timing bugs and make it muuuch
easier to refactor things further.
It's worth checking these on the beta cluster; if all is well they can go
out to Wikimedia sites with the next branch point.
As an intermediary step, some weeks ago we merged this change to mark
parser output requiring video modules, so the standard RL caching _should_
mean everything keeps working on cached pages once the newer revs go live:
* https://gerrit.wikimedia.org/r/#/c/230153/
With all these going out, we'll be able to finalize work on integrating the
VideoJS player framework to replace our old hacked-up version of the
Kaltura player, and generally modernize and vastly improve the playback
experience.
-- brion
This may be of interest:
http://aomedia.org/press-release/alliance-to-deliver-next-generation-open-m…
Amazon, Cisco, Google, Intel, Microsoft, Mozilla, and Netflix are pooling
resources to work on hammering out a standard, royalty-free, next-gen open
video codec.
Cisco and Mozilla had already started working together, combining ideas
from Cisco's Thor codec and the Mozilla-sponsored Xiph's Daala codec, but
getting them together with Google's VPx team is a big happy occasion...
getting Intel and Microsoft on board means probably hardware support on
x86_64 chips and support in Windows and MS Edge, while Amazon and Netflix
pump a lot of video volume out both to browsers and devices, so should help
push adoption by ARM SoC makers.
In other words, AWESOME SAUCE!
The only missing major player looks to be Apple... so we'll see if they
eventually join on or if they double down on HEVC and we keep having to
play JavaScript tricks. :P
I'm subscribing to their mailing list for updates; it may be worth looking
into if we can partner in or at least follow along and support stuff on our
end.
-- brion
Thanks to Giuseppe in ops & a bunch of other folks who have helped out,
we've got an updated server configuration for the 'video scalers' that
generate media transcodes, supporting VP9 video and Opus audio.
Initially we have one server updated and in production, and the rest should
follow by tomorrow. (Updated servers are also in place on the beta cluster.)
This should make it possible for WebM files using VP9 video and/or Opus
audio to work as fully first-class citizens in TimedMediaHandler,
generating medium- and low-resolution transcodes in Ogg and WebM VP8.
It should also fix Ogg audio files using the Opus codec to work
consistently.
Support for generating VP9 transcodes as well is in the code and just needs
to be switched on -- I'll tweak that configuration once we've got the rest
of the servers upgraded and have more capacity for batch runs.
(I've got a client-side bot which I'll start once that's ready, to force
all the files to generate over time.)
-- brion
(cross-posting from wikimedia-l)
Hi everyone,
Last year, the Wikimedia Foundation published our first ever video
year-in-review:
https://commons.wikimedia.org/wiki/File:Wikipedia_Edit_2014.webm
Which covered some of the major news events of 2014 through the lens of
Wikipedia. This year, we’re opening up the idea development and
pre-production process of making a video for 2015 to everyone. This is an
opportunity for you to help shape the narrative of the events of 2015:
https://en.wikipedia.org/wiki/User:VGrigas_(WMF)/Edit2015
Last year’s video was made largely by myself and another video editor over
about 8 weeks at the end of 2014. I spent the first half of my 8 weeks
researching news, comparing that to view and edit counts of Wikipedia
pages, and searching for media to illustrate those events. After I had that
media, it was a matter of taste to place them in a video editing timeline.
When we published it, the press and the general population on the Internet
reacted positively. All things considered, I think that #Edit2014 was a
good start, and I’m happy with the final result—but I’d like to improve a
few things for #Edit2015.
Here’s the plan:
Open Collaboration: I’m opening up the whole idea-development and
pre-production process (research, scriptwriting, brainstorming, finding
media, etc.) for making #Edit2015 to on-wiki collaboration. While
experimental, we have #Edit2014 as a guide to show that a final product can
be done; it taught me that year-in-review videos cover international news
events through a brand (in this case Wikipedia) by telling each news story
in about 5 seconds and then cutting to the next one. After being multiplied
by around 20 stories, your video will be upwards of two minutes long when
the credits, logos and titles are included. If you watch other
year-in-review videos (like Google Zeitgeist Year In Search) you’ll see how
each will spend 5 seconds on a topic and then jump to the next.
First drafts of #Edit2014 were half global news and half wiki-world news. I
wanted to showcase as many Wikimedia tools, events and projects as
possible. What I found was that since this is for a wide audience, and it’s
only a few short minutes long, we only have a chance to communicate one or
two new ideas (for an ordinary person who uses the internet), so we had to
be very selective about what was showcased. In this case, it was a chance
to talk about the edit button and Wiki Loves Monuments briefly. Then we
have to get back to those global shared news events that the public may
have experienced. Aspects like ‘going down the rabbit hole,’ clicking link
after link, was something that ordinary people were familiar with, so this
is something we used to bridge stories.
The idea-development and pre-production process does not require any fancy
video equipment—just a wiki page and an internet connection. I used post-it
notes on my wall to organize my ideas. I think that we—that is, the
Wikimedia crowd—can be very good at story development and collaboration.
I’ve been collecting imagery and ideas online, and I’d like to allow anyone
to use this space as a place to collaborate on this project:
https://en.wikipedia.org/wiki/User:VGrigas_(WMF)/Edit2015
An idea I had for this year is to somehow showcase the talk pages about
Wikipedia articles, to show how we arrive at consensus and a
neutral-point-of-view. Finding the right article(s) and talk page quotes to
use to illustrate that would be key. Last year, we showcased the edit
button using the 2014 Israel-Gaza conflict. For that, we see closeups of
‘citation needed’ and ‘disputed-discuss’ then we cut to the different
languages of that article. Imagine if you saw a tiny fraction of the
behind-the scenes talk about an article like that and how it aims for
objectivity?
Rules: These are some basic criteria I made to guide what content got into
#Edit2014:
Has the event made it to the international press or wide regional press?
Does the event have corresponding view or edit counts?
Do we have freely licensed imagery for the event?
Was there a special circumstance about this event per Wikimedia projects?
Does this illustrate some aspect of Wikimedia that the public should know?
Is the media beautiful?
Does the Wikimedia Foundation legal team approve of the media?
Do we have some media and news from every major region of the world?
As for production and post-production – Continuity, music, audio mixing, et
cetera are all things that should ideally be online and in a collaborative
manner but currently there is no system in place to collaborate on those
things using Wikimedia projects. I’d love to develop that system, but I
don’t think that it is practical for this year. I’d also like to aim to
make the video as close to 2 minutes in length as possible.
Schedule: So the logical publication date for #Edit2015 is December 15th
because that’s when the press, who would republish and spread the video on
social media, are still at work and this is an easy story for them to
publish before they go on vacation at the end of December. Getting this in
the press gets more eyeballs on the video. That means that actual video
editing should be well on its way in October and November. This is my
current schedule (for now):
Brainstorm and pre-production: now – October 1st
Production (assemble the footage): October 1st – November 15th
Post-Production (lock all the details): November 15th – December 1st
Distribution (captions and translations, thumbnails, text copy, uploading,
and any last-minute edits): December 1st – December 15th
Internationalism: My biggest problem with #Edit2014 was that so much of it
was in English. While we tried to cover as many regions and languages as
possible, a non-English speaker probably had to watch it with the captions
on—and then your eyes are stuck reading text on the bottom of the screen
rather than viewing the interplay of images and text. I think that opening
up the development and pre-production phase would flatten out the
perspective quite a bit, or at least help to point out flaws and suggest
other ideas. We shouldn’t have to rely on captions to make it universally
understandable, and since we’ll be jumping from one story to the next in 5
seconds, we can express a story in any local language. There may also be
‘universal’ communication media like video, imagery or numbers that are
associated with the text that they can understand.
Media Content: There are a few sources for freely-licensed imagery that we
can use for #Edit 2015: still imagery, video imagery, Wikimedia project
pages, audio, and imagery we make ourselves. I’d love if we could somehow
have more audio/video content for #Edit2015. I looked for freely-licensed
video and .gifs on Wikimedia Commons, Vimeo, Internet Archive and YouTube,
and I know there are many more I could have used. The first few versions of
#Edit2014 incorporated more video than the final cut did, but much was cut
out because it was too busy or complicated to communicate an idea quickly.
Sometimes a still frame of a Wikipedia article or a still photo might
communicate the idea more neutrally or succinctly than portions of
freely-licensed videos could.
For every still image you see in #Edit2014, there’s probably 10 more that
didn’t make the final cut. It took a lot of research to find appropriate
and compelling imagery.
I’m very optimistic that this will be a fruitful initiative, and I can’t
wait to see all the usernames of everyone who contributes. Please share
this link with your friends:
https://en.wikipedia.org/wiki/User:VGrigas_(WMF)/Edit2015
Let’s collaborate and tell the story of Wikipedia and 2015 together.
--
*Victor Grigas*
Storyteller <https://wikimediafoundation.org/wiki/WPZeroPetition> and Video
Content Producer
Wikimedia Foundation
vgrigas(a)wikimedia.org
https://donate.wikimedia.org/