Hello all,
I would like to announce the release of MediaWiki Language Extension
Bundle 2017.10. This bundle is The bundle is compatible with MediaWiki
1.28 and 1.29 or above and requires PHP 5.5.9 or above.
Next MLEB is expected to be released in 3 months. If there are major
changes or important bug fixes, we will do intermediate release.
Please give us your feedback at
[[Talk:MLEB|https://www.mediawiki.org/wiki/Talk:MLEB]].
* Download: https://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2017.10.tar…
* sha256sum: 75eefff3bbf50f1f84232f45ab169d2eedea5f7a18994f85b43237f2145403b1
Quick links:
* Installation instructions are at: https://www.mediawiki.org/wiki/MLEB
* Announcements of new releases will be posted to a mailing list:
https://lists.wikimedia.org/mailman/listinfo/mediawiki-i18n
* Report bugs to: https://phabricator.wikimedia.org/
* Talk with us at: #mediawiki-i18n @ Freenode
Release notes for each extension are below.
-- Kartik Mistry
== Highlights and upgrade notes ==
== Babel ==
=== Noteworthy changes ===
* Style updates.
== cldr ==
=== Noteworthy changes ===
* Localisation and maintenance updates only.
== CleanChanges ==
=== Noteworthy changes ===
* Localisation and maintenance updates only.
== LocalisationUpdate ==
=== Noteworthy changes ===
* Localisation and maintenance updates only.
== Translate ==
=== Noteworthy changes ===
* Special:Translate now accepts showMessage URL parameter that allows
linking to specific messages. This will be better accessible in a
future release.
* Special:LanguageStats and Special:MessageGroupStats now show the
total number of shown languages.
* Special:LanguageStats and Special:MessageGroupStats now handle the
sortable parameter correctly.
* Numerious compatibility and stability fixes:
** Translation editor shortcuts were not showing up in recent version
of MediaWiki.
** Compatibility fix for PHP 7.1.
** Compatibility fix for translatable pages and Visual Editor wikitext
editing mode.
** Compatibility fix for Elastica that broke translation memory.
** Compatibility fix for CxserverWebService which changed API.
* Style updates.
== UniversalLanguageSelector ==
=== Noteworthy changes ===
* Language searching is improved with new language name data and
better "no results found" view.
* Popup positioning should now work better in various skins.
* Style updates.
--
Kartik Mistry/કાર્તિક મિસ્ત્રી | IRC: kart_
{kartikm, 0x1f1f}.wordpress.com
Hi,
I just moved the npm jobs in the MediaWiki queue over to the new,
faster, docker based CI system. Instead of requiring building a fresh VM
for each 20-30 second job, it uses a docker container. I'm expecting
this to make a noticeable improvement in CI response times.
For the most part everything should just work, if something doesn't,
please file a bug in the #ci-config project and CC me (legoktm).
If something has gone terribly wrong and I'm not around, you can ask a
CI team member in #wikimedia-releng to revert [1] to put everything back
to the way it was.
[1] https://gerrit.wikimedia.org/r/#/c/387500/
-- Legoktm
# Who 👨💻
Željko Filipin, Engineer (Contractor) from Release Engineering team. That's
me! 👋
# What 📆
Selenium tests in Node.js. We will write a new simple test for a MediaWiki
extension. An example: https://www.mediawiki.org/wiki/Selenium/Node.js/Write
# When ⏳
Tuesday, October 31, 16:00 UTC
# Where 🌍
The internet! The event will be streamed and recorded. Details coming soon.
# Why 💻
We are deprecating Ruby Selenium framework:
https://phabricator.wikimedia.org/T173488
See you there!
Željko Filipin
Hi,
As I feel I didn't gathered enough information to create a phabricator
ticket, I send that here in order to obtain some guidance about what
would be interesting to provide and how to get it. I can say that most
of the time, I'm currently under Fedora 26 with Firefox 56, but that's
probably not much relevant information.
So the problem is: when I edit a module, sometimes, but not
systemically, the window at some point become sloooow. Like, there are
large latency between typing and displaying of the resulting action. And
indeed, for some reason, one processor core is around 100% due to a
firefox thread.
As a side note, I would be interested with any advice to ease my module
edit process, as the direct in-wiki edition and test become quickly
frustrating. When I edit a basic wiki text, I often use "it's all text"
which enable to edit in my usual text editor. But even this option won't
work with the widget of code edition (the same problem occurs with
"syntax highlight" extension).
Cheers
Hello,
As mentioned a few months ago there has been a significant update to
the design and layout of printed articles.[0] [1] This impacts both
PDF's created from the "Download as PDF" feature and from printing
directly from the web browser.
The feedback and discussion have been incredibly helpful. The team is
now ready to enable these styles as default across all projects. The
deployment is scheduled for Monday, October 9th. If you have used the
feature recently, not much has changed. If you haven't used it
recently we encourage you to check out the new styles. A few features:
* New layout to reduce paper usage
* Clear printing of tables and infoboxes
* Better headings
* Project-specific branding
For more information, please visit the project page on MediaWiki.org.
Comments and feedback can be left on the talk page there.
[0] https://lists.wikimedia.org/pipermail/wikitech-l/2017-August/088565.html
[1] https://www.mediawiki.org/wiki/Reading/Web/Projects/Print_Styles#Desktop_Pr…
Yours,
Chris Koerner
Community Liaison
Wikimedia Foundation
As announced in April[0], we are replacing Selenium tests written in Ruby
with tests in Node.js. Now is the last responsible moment to make the move.
There will be two more reminders, in September and October. In the
meantime, only critical problems will be resolved in the Ruby stack. After
October we will no longer maintain it. You can follow task T139740[1] for
more information. Extensive documentation is available at mediawiki.org[2].
If you need help with the migration, I am available for pairing and code
review (zfilipin in Gerrit, zeljkof in #wikimedia-releng).
Željko Filipin
--
0: https://lists.wikimedia.org/pipermail/wikitech-l/2017-April/087888.html
1: https://phabricator.wikimedia.org/T139740
2: https://www.mediawiki.org/wiki/Selenium/Node.js
Wikimedia has been accepted as one of 25 organizations in Google Code-
in (GCI) 2017!
GCI is a contest for 13-17 year old students to work on smaller tasks
on your To-Do list. It starts on Nov 28th. We need at least 75 tasks by
then. Code, docs, research, design, QA, anything (except translations)!
What you should do:
BECOME A MENTOR:
1. Go to https://www.mediawiki.org/wiki/Google_Code-in/2017
2. Add yourself to the mentor's table.
3. Get an invitation email to register on the contest site.
IDENTIFY AND PROVIDE SMALL TASKS:
1. Create a Phabricator task (which would take you 2-3h to complete)
or pick an existing Phabricator task you'd mentor.
2. Add the "Google-Code-In-2017" project tag.
3. Add a comment "I will mentor this in #GCI2017".
Feel free to directly create tasks on the GCI website yourself once
you've registered. (We can also import them for you.) If your project
does not use Phabricator: Just create tasks directly on the GCI site.
Looking for task ideas? Check the "easy" tasks in Phabricator:
https://www.mediawiki.org/wiki/Annoying_little_bugs offers links.
Make sure to cover expectations and deliverables in your task.
And once the contest starts on Nov 28, be ready to answer and review
contributions quickly (within 36 hours).
Any questions? Just ask, we're happy to help.
Thank you for your help to get young people into FOSS projects!
andre
--
Andre Klapper | Wikimedia Bugwrangler
http://blogs.gnome.org/aklapper/
Sent from my iPhone
Begin forwarded message:
> From: wikitech-l-bounces(a)lists.wikimedia.org
> Date: October 29, 29 Heisei at 7:29:59 PM GMT+7
> To: kimsovan79(a)gmail.com
> Subject: Mailman privacy alert
>
> An attempt was made to subscribe your address to the mailing list
> wikitech-l(a)lists.wikimedia.org. You are already subscribed to this mailing list.
>
> Note that the list membership is not public, so it is possible that a bad
> person was trying to probe the list for its membership. This would be a
> privacy violation if we let them do this, but we didn't.
>
> If you submitted the subscription request and forgot that you were already
> subscribed to the list, then you can ignore this message. If you suspect that
> an attempt is being made to covertly discover whether you are a member of this
> list, and you are worried about your privacy, then feel free to send a message
> to the list administrator at wikitech-l-owner(a)lists.wikimedia.org.
Hi. FYI: There were a lost of my own edits in the past week that were
marked as unseen in watchlist (and [0]). I can't open a phab ticket,
because it's not reproduceable. So if you know what to do with this, please
do, otherwise just ignore this letter. Thank you.
Igal (User:IKhitron)
[0]:
https://he.wikipedia.org/w/api.php?action=query&list=watchlist&wlshow=unrea…
Hello all!
Here are the minutes from this week's meeting:
* Outcome of this week’s IRC discussion: Usage of FauxRequest in production code
is discouraged and should be considered technical debt.
<https://phabricator.wikimedia.org/T169266>.
* Ongoing Last Call: Target PHP 5.6 for MW 1.31
<https://phabricator.wikimedia.org/T178538>. If no pertinent issues remain
unaddressed by November 1st, this RFC will be approved for implementation.
Related: Target PHP 7 for MW 1.32 <https://phabricator.wikimedia.org/T172165>.
* Next week’s IRC: Allowing extensions to override preferences
<https://phabricator.wikimedia.org/T178449>. Beware Daylight Confusion Week!
The discussion will take in #wikimedia-office, at 2pm PDT as usual for
Americans, but for Europeans it will be one hour earlier, at 22:00 CET.
The following week, we will be back on the regular schedule for both America and
Europe.
* Active discussion: Heredoc arguments for templates (aka "hygienic" or "long"
arguments) <https://phabricator.wikimedia.org/T114432>
* TechCom to revise outdated policy pages until the end of the year.
You can also find our meeting minutes at
<https://www.mediawiki.org/wiki/Wikimedia_Technical_Committee/Minutes>
See also the TechCom RFC board
<https://phabricator.wikimedia.org/tag/mediawiki-rfcs/>.
--
Daniel Kinzler
Principal Platform Engineer
Wikimedia Deutschland
Gesellschaft zur Förderung Freien Wissens e.V.