S Page | 28 Aug 23:43 2015

Office Hour about mediawiki.org API pages Tuesday Sept 1

Tuesday 2015-09-01T18:00 UTC [1] (11am San Francisco time) we will be
having an IRC office hour [2] about the mw.org API: namespace.

* As Wikimedia adds other APIs such as Wikidata Query Service and RESTBase,
the structure and navigation needs to evolve.
* Also, as you may know we are writing pages to encourage third-party
developers to use Wikimedia data and APIs, and eventually want this "Web
APIs hub" [3] to become the "front door" rather than API:Main_page.
** and presented with a different appearance to new developers  [4]

If you have thoughts, opinions, or needs from the API pages, I hope you can
attend. The last bullet point is challenging and controversial, so it helps
to share ideas and approaches.

The Phab task https://phabricator.wikimedia.org/T110108 links to related
tasks. It's also a Phab event https://phabricator.wikimedia.org/E50 and on
the internal WMF Engineering calendar.

See you in irc:freenode.net#wikimedia-office

[2] https://meta.wikimedia.org/wiki/IRC_office_hours#Upcoming_office_hours
[3] https://www.mediawiki.org/wiki/API:Web_APIs_hub
[4] http://devhub.wmflabs.org/wiki/API:Web_APIs_hub


=S Page  WMF Tech writer, and Quim Gil Engineering Community manager
Wikitech-l mailing list
(Continue reading)

Jon Robson | 28 Aug 21:46 2015

Wikivoyage now has extension driven page banners

After a successful Google Summer of Code, Sumit ( <at> 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 [1].

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 [2] 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 [3]!! :)).

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
(Continue reading)

Gilles Dubuc | 28 Aug 13:49 2015

Firrre: free IRC bouncer for FOSS projects

Title says it all: https://firrre.com/ They're ZNC instances.

I've signed up and it works as advertised. It took a couple of days for
them to review my application.

It supports a bunch of ZNC modules too ( https://firrre.com/modules/ ),
configurable via the usual znc commands or through a web interface.
Including fancy things like push notifications.
Wikitech-l mailing list
Wikitech-l <at> lists.wikimedia.org
Legault, Phillip [ITSUS] | 26 Aug 21:38 2015

Saving MediaWiki:common.js

I ran into an issue trying to save MediaWiki:Common.js I get this page not available (index.php?title=MediaWiki:Common.js&action=submit)

MediaWiki:Common.css save fine

Any Idea what I'm doing wrong?

Thank you!

Wikitech-l mailing list
Wikitech-l <at> lists.wikimedia.org
Grace Gellerman | 26 Aug 20:17 2015

2015-08-26 Scrum of Scrums notes

Wikitech-l mailing list
Wikitech-l <at> lists.wikimedia.org
Quim Gil | 26 Aug 11:28 2015

Engineering Community quarterly goals for October-December 2015

Hi, the Engineering Community team is starting to plan our goals for

Your feedback at https://phabricator.wikimedia.org/T109829 is welcome. If
there is a task you want us to push in the next quarter, now is the right
time to discuss it.

Your involvement is also welcome. If there is a task related with
Engineering Community that you want to own, and you want to handle it as
part of our lightweight project management process, you can join us.

You can learn more about ECT's roadmap and future plans at
https://phabricator.wikimedia.org/T101099 and


Quim Gil
Engineering Community Manager  <at>  Wikimedia Foundation
Wikitech-l mailing list
Wikitech-l <at> lists.wikimedia.org
Tim Starling | 26 Aug 10:41 2015

RFC meeting this week

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

Wikitech-l mailing list
Wikitech-l <at> lists.wikimedia.org
Robert Vogel | 26 Aug 08:30 2015

Tutorials / HowTos for VisualEditor

Hi everybody!

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!

[1] https://www.mediawiki.org/wiki/VisualEditor_gadgets#Gadget_-_Registering_VE_plugin
[2] https://en.wikipedia.org/wiki/User:%D7%A2%D7%A8%D7%9F/veReplace.js
[3] https://doc.wikimedia.org/VisualEditor/master
[4] https://www.mediawiki.org/wiki/OOjs_UI/Toolbars

Robert Vogel
(Continue reading)

Amir E. Aharoni | 26 Aug 07:20 2015

renaming Wikimedia domains


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‬
(Continue reading)

Andre Klapper | 25 Aug 17:56 2015

Defining and marking inactive/unmaintained code repositories

Hi everybody,

one requirement for the Gerrit Cleanup Day planned for September 23rd
([1], I still need to send a proper announcement, sorry for that) is to
allow marking code repositories as inactive.

This requires agreeing on criteria what's "inactive", after which time
span, and on a process that allows people to mark projects as such.

There is a proposal in 
concentrating on what's feasible currently with our given tools. 

It welcomes more feedback. If you're interested I kindly ask you to
take a look at the Phabricator task and add your comments there.

Thanks in advance!

[1] https://phabricator.wikimedia.org/T88531

Andre Klapper | Wikimedia Bugwrangler

Wikitech-l mailing list
Wikitech-l <at> lists.wikimedia.org
Giuseppe Lavagetto | 25 Aug 13:05 2015

Evaluation of clustering solutions (continued)

Hi all,

as previously announced, we've been evaluating a "clustering solution"
for use as an alternative to GridEngine for toollabs


Our goal is also to find a suitable, modern, stable tool to run not
only toollabs webservices, but also - on a longer term - to find a
modern, easier, more convenient way to run our microservices in
production: a clusterized environment that will allow us to enhance
single service availalbility and also to apply easier scaling of
applications, reducing further the friction surface and the direct ops
involvement in the day-to-day setup and deployment of services.

Our evaluation of the available solutions is ongoing, and while we're
mostly done filling up an "evaluation spreadsheet"
we would welcome and we encourage further involvement/suggestions. You
can provide these easily on the tracking ticket for the evaluation,

We received some interesting feedback already, and we look forward
incorporating more!

 We are considering two solutions - mesospheres' Marathon (which is
based on Mesos) - https://mesosphere.github.io/marathon/ and Google's
Kubernetes https://kubernetes.io.

Now let us summarize a bit our findings so far:
(Continue reading)