I would like to introduce to the Wikimedia community WikiToLearn, a FOSS
project of which I am a participant and which is lately getting a lot of
contributions and momentum.
It is a KDE project sponsored (among the others) by Wikimedia Italy and
recently joined by institutions such as HEP Software Foundation (CERN,
Fermilab, Princeton...) or Universities such as University of Pisa and Milano-
Bicocca. These institutions are already populating the website with content.
We aim to provide a platform where learners and teachers can complete, refine
and re-assemble lecture notes in order to create free, collaborative and
accessible textbooks, tailored precisely to their needs.
Although the project is quite young (only a few months old), it is already
growing in allure at an unexpected rate. Thanks to this we are now counting on
nearly 40 developers, and growing (including content developers).
We are different from Wikipedia and other WMF projects in several ways, and in
a sense, complementary. Our focus is on creating complete textbooks (and not
encyclopedic articles), drawing from a professor’s or a student’s own notes,
either existing or that have to be written down.
We also have a strong focus on offline use: all the content of WikiToLearn
should be easily printable by any student for offline use and serious
Besides a good team for content development, we can count on a small but
motivated team of developers, and we would like to improve communication with
upstream (a.k.a. you ;-) ), because we found ourselves developing a few
features which could probably be made available to the general public, with
some generalization and polishing. ;-)
Is this a right place to start such a discussion?
We would like to help as much as we can, but we might need some mentoring in
how to best approach MediaWiki development, as many of us are relatively new
to OSS/Web development.
We have decided to officially retire the rest.wikimedia.org domain in
favor of /api/rest_v1/ at each individual project domain. For example,
Most clients already use the new path, and benefit from better
performance from geo-distributed caching, no additional DNS lookups,
and sharing of TLS / HTTP2 connections.
We intend to shut down the rest.wikimedia.org entry point around
March, so please adjust your clients to use /api/rest_v1/ soon.
Thank you for your cooperation,
Principal Engineer, Wikimedia Foundation
we are considering a policy for REST API end point result format
versioning and negotiation. The background and considerations are
spelled out in a task and mw.org page:
Based on the discussion so far, have come up with the following
1) Clearly advise clients to explicitly request the expected mime type
with an Accept header. Support older mime types (with on-the-fly
transformations) until usage has fallen below a very low percentage,
with an explicit sunset announcement.
2) Always return the latest content type if no explicit Accept header
We are interested in hearing your thoughts on this.
Once we have reached rough consensus on the way forward, we intend to
apply the newly minted policy to an evolution of the Parsoid HTML
format, which will move the data-mw attribute to a separate metadata
Google Code-in 2015 has come to an end.
Thanks to our students for resolving 461 Wikimedia tasks. Thanks to our
35 mentors for being available, also on weekends & holidays. Thanks to
everybody on IRC for your friendliness, patience, and help provided to
Some more achievements, apart from those already mentioned in
* The CommonsMetadata extension parses vcards in the src field
* The MediaWiki core API exposes "actual watchers" as in "action=info"
* MediaWiki image thumbnails are interlaced whenever possible
* Kiwix is installable/moveable to the SD card, automatically opens
the virtual keyboard for "find in page", (re)starts with the last
* imageinfo queries in MultimediaViewer are cached
* Twinkle's set of article maintenance tags was audited and its XFD
module has preview functionality
* The RandomRootPage extension got merged into MediaWiki core
* One can remove items from Gather collections
* A new MediaWiki maintenance script imports content from text files
* Pywikibot has action=mergehistory support implemented
* Huggle makes a tone when someone writes something
* Many i18n issues fixed and strings improved
* Namespace aliases added to MediaWiki's export dumps
* The Translate extension is compatible with PHP 7
The Grand Prize winners & finalists will be announced on February 8th.
Again congratulations everybody, and thanks for the hard work.
See you around on IRC, mailing lists, Gerrit, and Phabricator!
Andre Klapper | Wikimedia Bugwrangler
I've been working on a little redesign project for the Main Page on
wikitech  and three key sub pages it points to since 2016-01-01 in
my User space. Tonight I decided that although it is far from perfect
it is better enough. I hope that some of you like it better than the
old page and that none of you hate it with a fiery passion that
compels you to revert it rather than helping me make it better.
Bryan Davis Wikimedia Foundation <bd808(a)wikimedia.org>
[[m:User:BDavis_(WMF)]] Sr Software Engineer Boise, ID USA
irc: bd808 v:415.839.6885 x6855
The public Parsoid endpoint http://parsoid-lb.eqiad.wikimedia.org is
being decommissioned  once we migrate over all straggler references
to that endpoint  possibly as soon as 3 weeks from now.
As far as we know, there are very few requests to that endpoint right
now, but if you have been using that endpoint, please switch over to
using the RESTbase service instead. You can access Parsoid HTML for the
wikimedia wikis via their REST API endpoint. For example,
https://en.wikipedia.org/api/rest_v1/?doc is the REST API url for
English Wikipedia content.
Within the next few weeks, I'll be deploying VisualEditor for 1000+ authors here at Cimpress/Vistaprint, in a wiki with 225,000 articles.
I plan to collect feedback from our users on what works and what doesn't. What would be the best way to communicate this feedback to Wikimedia?
Here are some early, informal comments from our pilot group of 20 users:
"I am in love!"
"TemplateData integration is awesome."
"How do I insert <code> tags?" (He didn't notice the "More" link in the font menu.)
"How do I set the width of a table column?"
"How do I copy and paste table rows?"
"Editing links is fiddly" (https://phabricator.wikimedia.org/T124305)
"I didn't see the editing tools at first because they're white on a white background."
"Can we save the page without having a pop-up?"