The current logo of MediaWiki was adapted slightly more than fifteen years
ago and hasn’t changed since. This logo despite having the nice concept of
sunflower, is old. The sunflower represents the diversity, the constant
growth and also the wildness.
Among its biggest issues I can point out that it’s a bitmap picture so it’s
unusable in large sizes (like large posters) and it’s too realistic making
it unusable in small sizes.
Most, virtually all, software products use a simpler and more abstract
form. For example, docker, kubernetes, Ubuntu, VueJs, React, Apache Kafka,
and many more. It’s a good time for MediaWiki to follow suit.
My request is for changing the logo of MediaWiki and I have no plans or
interest in changing logo of any other project.
Please show your support, oppose or your comments in the discussion page.
You can also add more suggestions.
The discussion page:
On March 30, we announced that we were temporarily pushing back the release
of MediaWiki 1.35 due to uncertainty resulting from the COVID-19 pandemic.
We are now ready to begin the process of moving forward with the release.
The first step is cutting the release branch, REL1_35, which will occur on
Monday, July 13.
We will then be in "pencils down" mode: developers will stop targeting
MediaWiki 1.35 for new features. Instead, any new features would continue
to be applied to master and would target MediaWiki 1.36 or later. The only
work that would continue towards MediaWIki 1.35 would be blockers -
critical bug fixes or features close to completion that need to make it
into the release. This would happen by merging those patches into master
and then backporting them to the REL1_35 branch.
We anticipate that MediaWiki 1.35 will be released at the beginning of
We appreciate your patience in these difficult times. Wishing you safety
I'm pleased to announce a new extension: Page Exchange (PX). This extension
serves as a sort of "package manager" (like yum or apt, if you've heard of
those), but where the "packages" are collections of wiki pages and files
(such as images). Packages are defined in JSON files, so that anyone can
publish a package by just creating a file in the relevant JSON syntax and
putting it online (plus putting online the wikitext and files that it
includes). Then, any wiki that has PX installed can download such a package
by just adding the URL for that package file to LocalSettings.php.
Once downloaded, a package can then be updated (if there have been changes
to the remote package definition), or deleted.
There's another interesting feature of Page Exchange, which is that, if you
install a package containing file(s) named "MediaWiki:XXX.js" or
"MediaWiki:XXX.css" (assuming you have the necessary permissions to do so),
any such file will get automatically loaded on every page view for that
functionality to the wiki.
Page Exchange can have a variety of uses, from providing a pre-generated
data structure for wikis to use, to allowing for easy copying of text and
images from one wiki to another - to even enabling lightweight alternatives
to extensions, or even skins.
You can read more about the extension, and download it here:
WikiWorks · MediaWiki Consulting · http://wikiworks.com
I upgraded to Mediawiki 1.34.2 on a CentOS 7 x86_64 server.
The composer update produced some noise:
Package wikimedia/password-blacklist is abandoned, you should avoid
using it. Use wikimedia/common-passwords instead.
Package jakub-onderka/php-parallel-lint is abandoned, you should avoid
using it. Use php-parallel-lint/php-parallel-lint instead.
Package jakub-onderka/php-console-color is abandoned, you should avoid
using it. Use php-parallel-lint/php-console-color instead.
Package jakub-onderka/php-console-highlighter is abandoned, you should
avoid using it. Use php-parallel-lint/php-console-highlighter instead.
Package phpunit/phpunit-mock-objects is abandoned, you should avoid
using it. No replacement was suggested.
The server information is located at
As per the MediaWiki version lifecycle , I would like to announce the
formal end of life (EOL) of MediaWiki 1.33 as of next week, Tuesday June
This means that MediaWiki 1.33 will no longer receive maintenance or
security backports (barring an unforseen issues with the 1.33.4 release
today). It is therefore strongly discouraged that you continue to use it.
It is recommended to upgrade to MediaWiki 1.34 (due to become EOL in
November 2020). The current Long Term Support (LTS) version of MediaWiki,
MediaWiki 1.31, is however older (and downgrading is not supported. The
delayed next LTS (MediaWiki 1.35) is currently due to be released in early
August 2020, and will be supported until at least June 2023.
MediaWiki 1.34 bumps the required PHP version from 7.0 in 1.33 (which is
unsupported upstream), to PHP 7.2.9 or later.
There's a new episode out of the MediaWiki podcast "Between the Brackets":
this one is an interview with Tom O'Neill, who runs the U.S. Department of
Energy's internal wiki, Powerpedia. He also runs "MediaWiki in Government",
the informal group/mailing list for MediaWiki users and enthusiasts within
the U.S. government. You can listen to the episode here:
WikiWorks · MediaWiki Consulting · http://wikiworks.com
[To all Wikimedia projects, minus mailing lists with an active
On August 2020, the Wikimedia Foundation board of trustees may decide a
rename to "Wikipedia Foundation" and various other things.
Following a community meeting, a proposed open letter was written:
«We ask the Wikimedia Foundation to pause or stop its current movement
renaming activities, due to persistent shortcomings in the current
rebranding process. Future work should be restarted only in a way that
ensures equitable decision-making.»
(Sorry for the crossposting. When replying, be mindful of cc. Do
consider forwarding to language-specific discussion venues with a short
translated introduction, or translate the pages on Meta.)
Federico aka Nemo
Tomorrow we will be issuing a security and maintenance release to all
supported branches of MediaWiki.
The new releases will be:
This will resolve one minor issue in MediaWiki core, and also includes some
fixes previously committed to git, including minor security and hardening
patches along with bug fixes included for maintenance reasons.
We've noted that these issues are minor, and as such you don't need to
apply them as quickly as with other security releases, if you're unable to
do so. We therefore decided to continue with getting the security (and
maintenance) release out for this quarter as planned, even with the global
situation as is.
We will make the fixes available in these respective release branches, and
also master. Tarballs will be available for the above mentioned point
releases as well.
A summary of some of the security fixes that have gone into non-bundled
MediaWiki extensions will also follow.
As per the MediaWiki Version lifecycle , June 2020 is the scheduled EOL
date for the REL1_33. 1.33.4 will therefore be the final release of the
MediaWiki 1.33 branch, barring any unforeseen issues.