After a successful Google Summer of Code, Sumit (@codezee) on irc with
help from Nicolas Raoul of the Wikivoyage editing community and
myself, I am excited to announce that Wikivoyage is now using the
WikidataPageBanner extension .
A bit of back story - the Wwikivoyage community built a template so
articles could display banners to increase engagement with their
content. The implementation had a few problems - for instance,
templates do not allow you to ship different styles for smaller
devices or use media queries, nor do they allow you to serve different
images to different browsers. As a result not only did banners not
render well on mobile but they also would result in a large image
download for a reader.
New features include a drop down table of contents, responsive images
and better mobile support. For the purposes of mobile, we have
introduced a focus parameter called `origin` which allows editors to
define which part of the banner shows on a smaller screen.
To take an example https://en.m.wikivoyage.org/wiki/Seattle before and
after pictures of applying the parameter  and getting banners to
focus on the space needle:
I'm hoping we can write API's and tools to make this easier for
editors to use and I'm hoping other wikis might adopt this interesting
feature (they are very cool for user pages !! :)).
There's still room for improvement. The banners on mobile can be made
even better, I think, and there has been little design input for the
mobile site so far. There are also issues with srcset support on older
browers, and hard problems to think about. Tasks are open for tracking
this work so please dive in .
I welcome any new contributors to help polish it even further by
working on one of those tasks or contributing new tasks. I'll be at
hand to help with code review.
If you have any questions please fire them away and please join me in
congratulating Sumit on his first major contribution to our movement
and building the first mediawiki extension to launch first on
Thanks to everyone who has helped advise, review the extension for
deployment and provided input/discussions on Wikivoyage travellers pub
I remembered how readily "the guys" assumed that any woman there was there
> for more than just networking and learning. I remembered having my butt
> pinched, my breasts "accidentally touched", my questions ignored or laughed
> at. I remember how the buzz of background conversation is always much
> louder when the speaker is a woman than when the speaker is a man.
All of these behaviors fall somewhere on the spectrum from rude to
depraved, but am I correct in thinking that most of them would not actually
be covered by a code of conduct? Ignoring or laughing at someone's
question, for example, is certainly rude, but I can't imagine anyone
getting officially reprimanded for it, unless there's an additional element
of confrontation there. (I don't know if this happened at a talk or during
an outside discussion, but either way I'd think it's the same.) Certainly
neither the Wikimedia code of conduct as currently drafted nor the WMF
Friendly Space Policy cover simple acts of rudeness, even if motivated by
WikiWorks · MediaWiki Consulting · http://wikiworks.com
I want to write an extension for the VisualEditor (great work by the way) and I need a little help. I've browsed through various documentation [1-4](and more) and already learned that using RL module 'ext.visualEditor.desktopArticleTarget.init' and 'mw.lib.ve.addPlugin' method is the way to go. Unfortunately my attempts to hook into the user interface by binding on events provided by the components (like 'save' from 've.ui.MWSaveDialog' or 've.init.mw.Target') have not been successful yet. Maybe you could give me a little push into the right direction.
Are there any HowTos or Tutorials for VisualEditor that cover topics like
1. Adding buttons to the toolbar
2. Accessing the data model (e.g. retrieve all set categories from the Parsoid DOM)
3. Extending/replacing a single tool (e.g. the GalleryInspector)
4. Binding on components events (e.g. the 'save' event, to analyze content and maybe abort saving)
Points 1 and 2 get more or less explained by the docs I've found. But 3 and 4 are very unclear to me. Some hints would be appreciated!
Is it possible in 2015 to rename Wikimedia domains?
The usual domain name structure for a Wikimedia project is
languageCode.project.org: en.wikipedia.org, it.wikisource.org, etc.
In a few projects the language code in the domain is different from the
actual language code: 'als' is a code for Tosk Albanian, but
als.wikipedia.org is written in Alemanic; 'no' is a code for both Bokmal
Norwegian and Nynorsk Norwegian, but no.wikipedia.org is only Bokmal; and
there are several other examples.
In the past when requests to rename such domains were raised, the usual
replies were along the lines of "it's impossible" or "it's not worth the
technical effort", but I don't know the details.
Is this still correct in 2015?
I would love to get that done, because these inconsistent and non-standard
codes repeatedly cause issues in various languages applications, the
current big one being ContentTranslation.
Amir Elisha Aharoni · אָמִיר אֱלִישָׁע אַהֲרוֹנִי
“We're living in pieces,
I want to live in peace.” – T. Moore
Call for Developers
We are planning to create a Digital Library Card Platform for The Wikipedia
Library. We are looking for a developer, or team, with a history of
successfully developing web applications in open development frameworks
(such as Drupal, Angular, Ember, CiviCRM, etc.). Efficient production,
clear communication, and well-structured and secure code are a must.
Additional consideration will go towards applicants who have worked in the
Library and Information Science field, on Open Source projects, or in the
Wikimedia/Mediawiki communities. Our budget currently allows for
$5000-$15,000 for development of a working version within 4- 6 months. We
expect to expand the platform in two later phases to add additional
functionality around standard library services.
The Wikipedia Library helps Wikipedia's top editors receive access to
donations from leading publishers and databases. Now that we have over 3
dozen publishing partners including Elsevier JSTOR, Oxford University
Press, and SAGE, AND nearly a dozen global branches with 2 dozen more
planned for the next year AND commitments to support other TWL programs
across the globe... we need to create a system that will facilitate our
expansion. In the past, manual and separate processes for delivering
access were appropriate, but this year's focus is on scaling and
the Digital Library Card Platform tool is a top priority for us this year.
Qualified and interested applicants should read this project overview and
fill out the form linked on this page:
Please feel free to share this email with friends or colleagues who may
also be interested.
*Head of The Wikipedia Library <https://meta.wikimedia.org/wiki/TWL>*
As part of our goal to reduce the zero results rate
the Discovery Department is currently running an A/B test to try different
parameters for the search suggester. We're hoping that our new parameters
will give users more suggestions without decreasing their quality.
The reason we've chosen to tweak the suggestions is because of our recent
work <https://phabricator.wikimedia.org/T105202> to automatically run
queries for the user if they get zero results but have a suggestion. The
purpose of this A/B test is to determine whether this has significant
impact towards achieving our goal or not.
This is the first A/B test that the Discovery Department has run, so we're
still ironing out the process. We hope to run many more A/B tests in the
For further information on this, please review the associated Phabricator
If you have any questions, I'd be happy to answer them.
Lead Product Manager, Discovery
In the next RFC meeting, we will discuss the following RFC:
* Replace Tidy with HTML 5 parse/reserialize
The meeting will be on the IRC channel #wikimedia-office on
chat.freenode.net at the following time:
* UTC: Wednesday 21:00
* US PDT: Wednesday 14:00
* Europe CEST: Wednesday 23:00
* Australia AEST: Thursday 07:00
-- Tim Starling