I'm happy to announce a Gerrit Cleanup Day on Wed, September 23.
It's an experiment to reduce Wikimedia's code review backlog which
hurts growing our long-term code contributor base.
Development/engineering teams of the Wikimedia Foundation are supposed
to join and use the day to primarily review recently submitted open
Gerrit changesets without a review, focussing on volunteer
contributions. And developers of other organizations and individual
developers are of course also very invited to join and help! :)
https://phabricator.wikimedia.org/T88531 provides more information,
steps, links. Note it's still work in progress.
Your questions and feedback are welcome.
Thanks,
andre
--
Andre Klapper | Wikimedia Bugwrangler
http://blogs.gnome.org/aklapper/
In the next RFC meeting, we will discuss the following RFC:
* Improving extension management
<https://www.mediawiki.org/wiki/Requests_for_comment/Improving_extension_man…>
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
Are there any stable APIs for an application to get a parse tree in
machine-readable format, manipulate it and send the result back without
touching HTML?
I'm sorry if this question doesn't make any sense.
Is there any easy way to find all of citations of specified academic
articles on Wikipedias in all languages, and the text that is supported by
those references, so that the citations of questionable articles can be
removed and the article texts can be quickly reviewed for possible changes
or removal?
See
https://www.washingtonpost.com/news/morning-mix/wp/2015/08/18/outbreak-of-f…
If we don't have easy ways to deal with this (and I believe that we don't),
I'd like to suggest that the Community Tech team work on tools to help when
these situations happen.
Thanks,
Pine
There's a pretty hilarious American police procedural TV show in 2015
called "CSI: Cyber", featuring mostly cybercrime. Obviously they have to
dredge up snippets of code from places for screenshots on the show.
Episode 4 happened to include a tidbit from MediaWiki 1.25/wmf3. Supposedly
the code was a hack to make your printer blow up.
Original lulz and screenshots via
http://moviecode.tumblr.com/post/114815574587/this-is-from-csi-cyber-s01e04…
Hi all!
We have some breaking API changes that will soon be deployed to wikidata.org.
The deployment date should be: 9th September 2015 (just under 2 weeks)
The change making the breaks an be found at:
https://gerrit.wikimedia.org/r/#/c/227686/
The breaking changes are:
- XML output aliases are now grouped by language
- XML output may no longer give elements when they are empty
- XML any claim, qualifier, reference or snak elements that had an
'_idx' element will no longer have it
- ALL output may now give empty elements, ie. labels when an entity has none
If you want to see a wikipage explaining these changes take a look at:
https://www.wikidata.org/wiki/User:Addshore/API_Break_September_2015
If you have any questions regarding these breaking changes please ask!
Addshore
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.
Hello all,
I would like to announce the release of MediaWiki Language Extension
Bundle 2015.08. This bundle is compatible with MediaWiki 1.23.x and
MediaWiki 1.24.x releases.
Next MLEB is expected to be released in 3 months. We are trying less
frequent releases due to low number of changes per month in the
included extensions. 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-2015.08.tar…
* sha256sum: 21cb43509d1e6da3cadc7e594866215d430e110aea5d04857e5cffd2a69db031
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
== Babel ==
* Localisation updates only.
== CleanChanges and LocalisationUpdate ==
* Supports extension registration now.
== CLDR ==
* Fix names and translations for Northern Luri, Southern Luri,
Shawiya, Laki, Jinyu (cjy) and Cham.
== Translate ==
* Special:SearchTranslations has acquired lots of new features, such
as cross language search. To take advantage of all the new features,
you need to reindex the index with "php scripts/ttmserver-export.php
--reindex". You also need to update ruflin/elastica to 2.2.0 or later,
or recent version of CirrusSearch which bundles it.
* Translatewiki.net specific message group descriptions have been removed.
* ApiHardMessage has been removed.
* The hidden, deprecated non-TUX translation view is being phased out
and many non-essential features have been removed.
* Web service queries to machine translation and remote translation
memory services are now done parallel.
* Some improvements to cache handling so that some caches are
regenerated instead of just purged when content changes.
* The appearance of workflow state selector on Special:Translate has
been improved.
* Breaking change: The output format of ApiQueryMessageGroups has
changed regarding to workflow states.
* The code no longer checks for the presence of the long deprecated
"revtag_type" database table. Things like proofread messages might
appear as unproofread. If this is the case, run "php
scripts/migrate-schema2.php"
== UniversalLanguageSelector ==
* ULS will use jQuery.i18n from MediaWiki core if available.
* Updated the default geoiplookup URL.
* ULS supports extension registration now.
* Fonts:
** Added Gothic font.
* Input Methods:
** Add Northern Luri keyboard layout.
** Add Southern Kurdish keyboard layout.
** Add South Azerbaijani keyboard layout.
** Add Arabic keyboard layout for Western Baluchi (bgn) (Only for
MediaWiki > 1.25).
** Improvement in many keyboard layouts.
--
Kartik Mistry/કાર્તિક મિસ્ત્રી | IRC: kart_
{kartikm, 0x1f1f}.wordpress.com
Hi,
I have enabled a Gadget on Fa Wikipedia (if you go to
https://fa.wikipedia.org/wiki/Special:Preferences#mw-prefsection-gadgets it
is the second one from the top) which depends on ext.gadgets.morebits (as
defined on https://fa.wikipedia.org/wiki/MediaWiki:Gadgets-definition). It
adds a portlet menu labeled "تذکر" which shows only on user talk pages. The
menu contains a number of links, some of which start with "+".
These "+" links are supposed to open a dialog using morebits. If you use
*debug=true* to bypass ResourceLoader, they work fine (feel free to try on my
talk page <https://fa.wikipedia.org/wiki/User_talk:Huji?debug=true> after
enabling the gadget for your account on Fa WP). However, if you don't
bypass ResourceLoader, the "+" links won't work and an error is thrown
reading "SimpleWindow is not defined" (try on my talk page without
bypassing RL <https://fa.wikipedia.org/wiki/User_talk:Huji>). Note that
SimpleWindow is defined in morebits.js
My questions are as follows:
1) How come it works when you bypass ResourceLoader? Note that nothing else
has changed recently (including the morebits.js code on that Wiki)
2) Is it safe to assume that just by listing ext.gadgets.morebits as a
dependency, morebits will be properly loaded by ResourceLoader?
3) Unless 1 or 2 answers it already: how would I fix this problem and make
the gadget work?
Thanks,
Huji
Hello Folks,
Many apologies for cross-posting. We have got a page with reading team
updates for August [0]. The brief for those is:
[1]. The team is doing more efforts in order better understand user
behaviors and patterns, and has a survey tool in place
[2] There are discussions around possible alternatives for article layout
on mobile
On a side note: If you are interested in helping the apps team understand
what users want, get in touch with me, please. We need more OTRS
volunteers to help with handling users and community questions
As usual, comments and questions feel more at home on the talk page of
their relevant topic than they are on this email thread. :)
Happy Weekend!
Moushira
[0] https://www.mediawiki.org/wiki/Reading/Reading_team_updates_August,_2015
[1]https://www.mediawiki.org/wiki/Extension:QuickSurveys/Documentation
[2] https://www.mediawiki.org/wiki/Talk:Reading/Features/Article_lead_image