Hi,
The JSON i18nj files in MediaWiki extensions are getting filled by apihelp
messages. They are usually added to the end of the files.
In addition to docs internationalization, which is pretty awesome by
itself, this happens to have another somewhat useful side effect on the
i18n files themselves. Most messages that are added to the JSON files are
not apihelp messages. When messages are added to the end of the file, a
comma must be added to the last JSON line, even if the message on that line
doesn't actually change. This change is not really meaningful, but it adds
one more line to the diff in review.
Keeping the apihelp messages in the end and adding all other messages
before them prevents this comma-adding and shortens the diff by one line.
It is, of course, a small thing, but it saves a few moments when reviewing
code or doing git blame or git bisect.
I suggest adopting this as a good practice.
--
Amir Elisha Aharoni · אָמִיר אֱלִישָׁע אַהֲרוֹנִי
http://aharoni.wordpress.com
“We're living in pieces,
I want to live in peace.” – T. Moore
Hello and welcome to the latest edition of the WMF Engineering Roadmap
and Deployment update.
The full log of planned deployments next week can be found at:
<https://wikitech.wikimedia.org/wiki/Deployments#Week_of_November_10th>
A quick list of notable items...
== All Week ==
* Fundraising tests throughout the week (on-going through the rest of
the yearly fundraising)
== Monday ==
* New Search (Cirrus) to Chinese Wikipedia
** <https://www.mediawiki.org/wiki/Search>
== Tuesday ==
* MediaWiki deploy
** group1 to 1.25wmf7: All non-Wikipedia sites (Wiktionary, Wikisource,
Wikinews, Wikibooks, Wikiquote, Wikiversity, and a few other sites)
** <https://www.mediawiki.org/wiki/MediaWiki_1.25/wmf7>
== Wednesday ==
* New Search (Cirrus) to German Wikipedia
** <https://www.mediawiki.org/wiki/Search>
* MediaWiki deploy
** group2 to 1.25wmf7 (all Wikipedias)
** group0 to 1.25wmf8 (test/test2/testwikidata/mediawiki)
== The Following Week ==
Heads up that on November 19th, new search (Cirrus) will be deployed
to English Wikipedia.
Thanks and as always, questions and comments welcome,
Greg
--
Greg Grossmeier
Release Team Manager
Over the last few days I have seen a number of emails with no subject and
just an email address in the content of the message. Can these please get
blocked?
TL;DR: Should we merge https://gerrit.wikimedia.org/r/#/c/165979/ and
release it with MediaWiki 1.24?
A lot of sites have used MediaWiki:Common.js and MediaWiki:Common.css to
customize the appearance of their site.
In a recent security release[1], support for JS and CSS with on-wiki
origins was removed from being displayed on the Special:Login and
Special:Preferences page.
Because of how the on-wiki MediaWiki:Common.* pages are used and the
access restrictions on them, I think it is reasonable to allow JS and
CSS from them while continuing to disallow individual's JS and CSS on
the Special:Preferences and Special:Login page.
Alexia filed a bug[2] and Kunal (Legoktm) has provided a patch[3] to allow
site-wide styling back on those pages.
I'd like to merge this, but I want some input from the community and
security people before I do that.
Thanks,
Mark.
(Reply-to set to mediawiki-l.)
Footnotes:
[1] https://bugzilla.wikimedia.org/70672
[2] https://bugzilla.wikimedia.org/71621
[3] https://gerrit.wikimedia.org/r/#/c/165979/
--
Mark A. Hershberger
NicheWork LLC
717-271-1084
All,
New hardware is in place and we've got plenty of breathing room to wrap up
the migration to
the new search engine. The only wikis not already on it are: frwiki,
zhwiki, dewiki and enwiki.
We're planning to switch frwiki next Wednesday, Nov. 5th.
If all goes well with that, I'd like us to do zhwiki the following Monday,
Nov 10th.
Then if things are still ok, let's do dewiki on Wednesday, Nov 12th.
I think we'll be fine at this point and then we can talk about a proposed
date for enwiki by the
end of November.
Of course this is all tentative on us throwing more load at Elasticsearch
and it continuing to
behave well. But that's why we got more hardware ;-)
As always: I thank the many *many* beta testers we've had throughout this
process. Your
feedback has been invaluable. Feedback is still welcome and appreciated
even as we get
into the home stretch too...please file bugs or find us on IRC if something
just isn't right.
I already left notice on frwiki's bistro yesterday, will do the same for
zhwiki and dewiki today.
If someone could forward this to wikitech-ambassadors for me, I'd be
grateful.
-Chad
Hi, I found that someone created
https://www.mediawiki.org/wiki/Arcanist but it contains obsolete
information. If you have access to phabricator and knowledge, please
update this page.
Most needed are now working examples of how arcanist can be used on
wikimedia installation, especially review (arc diff) and landing (arc
patch).
I do have some knowledge, but I have no idea how wikimedia
installation is configured, so I can't update it that much.
Thanks
[x-posted announcement]
Hello,
The next monthly IRC office hour of the Wikimedia Language Engineering team
will be on Wednesday, November 12, 2014 at 1700 UTC on #wikimedia-office.
We will be taking questions and also discussing about the availability of
the new version of the Content Translation tool[1][2] and upcoming plans.
Please see below for event details and local time
Thank you.
Runa
[1] https://www.mediawiki.org/wiki/Content_translation
[2]
http://blog.wikimedia.org/2014/11/03/announcing-the-second-version-of-the-c…
Monthly IRC Office Hour:
==================
# Date: November 12, 2014 (Wednesday)
# Time: 1700 UTC (Check local time:
http://www.timeanddate.com/worldclock/fixedtime.html?iso=20141112T1700)
# IRC channel: #wikimedia-office
# Agenda:
1. Content Translation project updates and plans
2. Q & A (Questions can be sent to me before the event)
--
Language Engineering - Outreach and QA Coordinator
Wikimedia Foundation