There is a bug (or a feature, depends on how you see it) in mediawiki
extension namespace registration . If an extension registers a
namespace, there is no way to override that. It can be problematic in cases
when there is a conflict of IDs between two installed extensions or one
extension and custom-defined namespaces. We want to change that but there
are several approaches and each of them has benefits and issues:
One (suggested by me) is to make IDs of namespaces registered by extension
configurable using LocalSettings.php. This allows us to easily "move" a
namespace without needing to touch other configurations related to that
namespace but it also adds a global variable and also can't handle conflict
in names of namespaces.
Another approach (suggested by legoktm) is to skip registering a namespace
from extensions when the namespace constant is already defined. This
doesn't have problems that the first approach has but you need to duplicate
the configuration when there is a conflict.
Please contribute at the discussion and add your comments/concerns. Also
feel free to suggest a new approach.
Amir Sarabadani Tafreshi
Software Engineer (contractor)
Wikimedia Deutschland e.V. | Tempelhofer Ufer 23-24 | 10963 Berlin
Wikimedia Deutschland - Gesellschaft zur Förderung Freien Wissens e.V.
Eingetragen im Vereinsregister des Amtsgerichts Berlin-Charlottenburg unter
der Nummer 23855 B. Als gemeinnützig anerkannt durch das Finanzamt für
Körperschaften I Berlin, Steuernummer 27/681/51985.
Hello! The CREDIT showcase video and notes from earlier this month have
been posted. Enjoy!
Here's what was covered:
* Stephen Niedzielski, localized Android app independent of system language
* Gergő Tisza, Developer Wishlist
* Gergő Tisza, PsySH (much of the credit is due to Antoine Musso who could
* Jan Drewniak - 'Explore Similar' feature for search results
I am Egbe Eugene. I come from Cameroon and i am quite new to the movement
as a developer. My thought towards contributing to the community is driven
by the impact which the foundation could bring to my country and Africa and
also what i will do in order that the movement be heard around the ends of
I will also wish to enhance my engineering skills while contributing to the
movement by working on the foundation's projects.
Hope to get more help to get started soonest.
Starting in April 2017, MediaWiki will end Grade A support for browsers that
and others using very old mobile browsers.  Users with these browsers
still be able to browse and contribute to the projects. Enhanced features
become unavailable. For example, the enhanced edit toolbar will not appear,
and notification buttons will take you to a page rather than open a pop-out.
This change will affect roughly 0.59% of page views to Wikimedia wikis (as
February 2017 ). Internet Explorer 9 (0.27%), mobile users on iOS 4
Safari 5 — 0.02% of traffic), and Android 2 (0.1%). For comparison, 0.3% of
maintenance burden. It also hinders site speed for all users. Microsoft
its official support for Internet Explorer 9 and 10 in January 2016. 
Users unable to upgrade from IE 9 or Android 2 will have a faster experience
going forward, based on well-tested and more stable code.
This change will land in the development branch used on all Wikimedia wikis
this April, to be released as part of MediaWiki 1.29 around May 2017.
Please help carry this message into your communities.
(Tech News has announced this change as well)
 http://caniuse.com/#feat=use-strict Browser support for ES5 (strict)
 https://phabricator.wikimedia.org/T128115#3066522 Breakdown of
Wikimedia page views from pre-ES5 browsers
(Note: Filter date to last 2-3 months only!)
Due to an outage on enwiki earlier today caused by Special:AllPages, it has temporarily been disabled on all wikis pending further investigation.
To this extent a public tracking task  has been created, and updates will be put there to keep people in the loop.
Proper incident should appear on Wikitech at a later date, after the problem has been resolved.
"Fantastic MediaWikis and How to Maintain Them" is a one-day conference track designed for people who work with the open source software MediaWiki in their organisation, company or business . The conference track is curated by the MediaWiki Stakeholders Group and hosted by Wikimedia Austria.
The track is part of Wikimedia's biggest annual tech-event, the Wikimedia Hackathon : For three days each year, about 200 developers come together to improve MediaWiki. Among the participants are coders from the Wikimedia Foundation as well as volunteers from all over the world.
We're using this opportunity to connect the people who work with MediaWiki in their enterprise, company, or organisation to the people who actually develop the code. We invite all MediaWiki stakeholders - power-users, maintainers, and service providers, who have a professional or semi-professional interest in the software - to join us for a day full of MediaWiki knowledge and networking!
This is a call for participation. We are specifically looking for contributions of your experience in running MediaWikis. These include but are not confined to:
* Use Cases. Tell us how and why you use MediaWiki in a specific area or to solve a specific problem.
* Best Practices. Talk about the most effective way you have found to use particular MediaWiki features.
* Enhancements. Have you improved MediaWiki to fit your needs? Show us your solution.
* Challenges. How can we all add to MediaWiki functionality? Do you have specific ideas you want to collaborate on?
Share your experience and submit a presentation here:
* 20th March 2017: Call for Participation opens
* 5th April 2017: Submission deadline
* 10th April 2017: Notification of acceptance
* 19th - 21st May 2017: Vienna Hackathon
We are looking forward to your submissions!
MediaWiki Stakeholders' Group
I'd like to plead for advice on testing Recitation-bot to demonstrate we
have resolved a bug that resulted in a ban for splitting image pages into
two separate incomplete pages last month.
The log of attempts to test the fix is in this bug
Here are the key points / open questions:
- Each wiki I have successfully tried to test on, including the
production wikis, test.wikipedia.org, and testwiki.wiki, seems to
redirect the bot to a page with information about permissions / blocks,
something I had never seen prior to the block.
- What is the appropriate place to test? Seems to be www.thetestwiki.org
- Could we appeal the block on the strength of the apparent correctness
of the edit to fix the bug, at least temporarily so as to be able to
demonstrate the fix on a wiki we were running successfully on in the recent
past? Who would be best to approach with such a request?
Thanks any and all for any advice you can offer.