recently some changes were merged to Wikipedia that broke some math
rendering for almost 2 days.
I'm highly interested to avoid that this will happen again.
As a reaction my goal is to develop the changes in a new branch called
math2_0_0 that get's reviewed according to the WMF standards and is
tested in a production like environment and reviewed by the community,
before the changes are merged to the master branch. Is there a
production like environment that could be used for that? Of course I
could try to create a production like environment for Math by myself
like I did with
http://math-test2.instance-proxy.wmflabs.org/wiki/Main_Page ... but I
want to avoid double work and I'm a volunteer... so my time is very
Mit freundlichen Grüßen
Telefon (Büro): +49 30 314 22784
Telefon (Privat):+49 30 488 27330
(http://instantclick.io/). Basically, it's based on the principle that
latency is responsible for a lot of the Web's slowness. It also
considers that there are about 250ms between hovering over and
clicking on a link. Therefore, it starts pre-loading the page on
hover, and then switches to it via AJAX when the user clicks the link.
It can also do this on mousedown only, which causes no additional
server load and still provides a performance boost, according to its
website, similarly to Rails' turbolinks functionality.
Is there any chance this could work on MediaWiki?
On one of my wikifarms I only have one local patch to MediaWiki core
left. I'm hoping to have that merged as well, so let me bring this to
your attention: https://gerrit.wikimedia.org/r/#/c/98078/
On a related note, I'm using html templates and I am in need of a way
to deliver them with resource loader. Max Semenik has already made a
patch for that, so please have a look at that too:
bugzilla.wikimedia.org will be unavailable due to maintenance work on
Wednesday, February 12th from 22:00 UTC until max. Thursday, February
13th 01:00 UTC.
* upgrading Bugzilla to newer version
* moving Bugzilla to new server
* depending on how smooth things go, doing admin maintenance work
while bugmail is switched off for a moment, like
** merging the numerous 1.20.x version field entries into one
** mass-removing "wikibugs-l@" from CC lists of reports (see bug
47013) as it's set as a globalwatcher anyway
** maybe restructuring the taxonomy of Mobile components
(currently still discussed in the Mobile team)
Andre Klapper | Wikimedia Bugwrangler
Google Summer of Code 2014 has started.
(Thank you Raylton for creating this page)
The first step is to apply as Wikimedia organization before February 14.
I can do this, with your help:
* We need another org admin ready to work. I was the primary org admin
in GSoC 2013 and I'm also primary/only org admin in FOSS OPW and
Facebook Oen Academy. Google Code-in was different, with Andre and me
really sharing the org admin role. This brought better and more reliable
program administration, plus useful knowledge shared by more people for
future editions. Interested? Please reply.
* We need to add proposals with mentors and community buy-in under the
"Featured project ideas" section at
. Either you step in now, or you wait at least six months until the next
call. Interested? Just edit the page. The sooner the better.
PS: I will be offline on holidays next week. I will submit the Wikimedia
application before leaving, almost week before the deadline. You will be
able to keep improving our proposal by improving the related wiki pages.
-------- Original Message --------
Subject: [GSoC Mentors Announce] Now Accepting Applications for
Mentoring Organizations for GSoC 2014
Date: Mon, 3 Feb 2014 11:01:15 -0800
From: Carol Smith <carols(a)google.com>
To: GSoC Mentors Announce <gsoc-mentors-announce(a)googlegroups.com>
We're pleased to announce that applications for mentoring organizations
for Google Summer of Code 2014 are now being accepted . If you'd like
to apply to be a mentoring organization you can do so now via Melange
. If you have questions about how to use Melange, please see our
User's Guide . Please note that the application process has changed a
bit from previous years: to apply you must now create your individual
profile and then an organization profile before submitting your
Please note that the application period  closes on 14 February at
19:00 UTC . *We will not accept any late applications for any reason.*
 - http://www.google-melange.com
 - http://en.flossmanuals.net/melange/
 - http://www.google-melange.com/gsoc/events/google/gsoc2014
 - http://goo.gl/bYYgV3
You received this message because you are subscribed to the Google
Groups "Google Summer of Code Mentors Announce List" group.
To unsubscribe from this group and stop receiving emails from it, send
an email to gsoc-mentors-announce+unsubscribe(a)googlegroups.com.
Visit this group at http://groups.google.com/group/gsoc-mentors-announce.
For more options, visit https://groups.google.com/groups/opt_out.
For some time, work has been ongoing on a merge of the Poem extension into MediaWiki
core  . (For those not aware, this extension  implements a simple <poem>
tag which, among other things, preserves newlines.)
Several developers have expressed the desire for an alternative name for this tag,
alongside <poem> (which of course will be kept for backward compatibility). This is
because the tag is sometimes used for various other uses besides poetry.
There were many suggestions (see the bug report ), but it was eventually agreed
to use Michael M.'s suggestion of <lines>. This name puts the focus on the
individual "lines" of the content, which is exactly what the tag is doing.
We almost had a collision with a previous proposal (<verbatim> conflicted with a tag
in use on Wikia), so we wish to ensure that no-one else is using <lines>. No-one is
yet aware of any MediaWiki extensions or other code using a tag named <lines> in
If you think the name <lines> will be an issue, or if you have any other concerns
with this merge, please speak up, either here or at the bug report.