As per the MediaWiki version lifecycle [1], I would like to announce the
formal end of life (EOL) of MediaWiki 1.33 as of next week, Tuesday June
30, 2020.
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.
Thanks!
Sam Reed
[1] https://www.mediawiki.org/wiki/Version_lifecycle
Hi everyone,
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:
https://betweenthebrackets.libsyn.com/episode-63-tom-oneill
-Yaron
--
WikiWorks · MediaWiki Consulting · http://wikiworks.com
[To all Wikimedia projects, minus mailing lists with an active
discussion already.]
On August 2020, the Wikimedia Foundation board of trustees may decide a
rename to "Wikipedia Foundation" and various other things.
<https://meta.wikimedia.org/wiki/Wikimedia_Foundation_Board_noticeboard/Boar…>
Following a community meeting, a proposed open letter was written:
<https://meta.wikimedia.org/wiki/Community_open_letter_on_renaming>
«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.)
Cheers,
Federico aka Nemo
Hi all,
Tomorrow we will be issuing a security and maintenance release to all
supported branches of MediaWiki.
The new releases will be:
- 1.34.2
- 1.33.4
- 1.31.8
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 [1], 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.
[1] https://www.mediawiki.org/wiki/Version_lifecycle
Thanks!
Sam
Hi, all. According to [1], "within reason, it is acceptable" to post MediaWiki-related job openings here (thanks to Reedy for pointing this out in IRC). I assume that making one posting is "within reason", so here it is:
We have contract work openings for PHP+Python programmers with experience customizing and extending MediaWiki. This work is open source [2]. Here's a link to the job posting:
https://www.fossjobs.net/job/10221/phppython-programmer-at-open-tech-strate…
And here is the text, for your convenience:
| We seek software developers to fill contract positions in free
| software projects for various clients. Our current need is for PHP
| and Python coders interested in contributing to projects in the
| non-profit and philanthropy space. Familiarity with customizing and
| extending MediaWiki would be helpful, but is not required.
|
| This role is for projects scheduled to last 6 months to a year, with
| the possibility of follow-on work. We anticipate 15-20 hours per
| week of work, though that might change as we take on new projects.
|
| If interested, please email jobs {_AT_} opentechstrategies.com.
|
| OTS is based in Chicago and New York. We are open to remote
| applicants (within 3 hours of either U.S. Central or U.S. Eastern
| time zone), and we negotiate rates based on experience and skills.
| We value having a diverse team and we strongly encourage members of
| groups that are underrepresented in software development to apply.
|
| Open Tech Strategies is committed to free software philosophically
| and as a business strategy. We work in public repositories, using
| free and open source tools. If you have a visible open source
| profile -- an account on a project hosting site, a trail of
| participation in some projects, etc -- please mention it in your
| email, CV, or résumé.
If you are interested or know someone who might be, please let us know, and feel free to forward this announcement to wherever you think it would be appropriate.
Best regards,
-Karl Fogel
Partner, Open Tech Strategies, LLC
[1] https://www.mediawiki.org/wiki/Jobs
[2] https://github.com/opentechstrategies/torque/ is one of the projects.
Hello,
The committee has finished selecting new members and the new committee
candidates are (In alphabetical order):
- Amir Sarabadani
- Martin Urbanec
- MusikAnimal
- Tonina Zhelyazkova
- Tony Thomas
And auxiliary members will be (Also in alphabetical order):
- Huji
- Jayprakash12345
- Matanya
- Nuria Ruiz
- Tpt
You can read more about the members in [0]
The changes compared to last term are:
* Lucie has resigned in September 2019. Tpt (as one of auxiliary members)
filled her seat in the meantime and now Tpt is moving to be an auxiliary
member again.
* Martin Urbanec is joining the main committee to fill Lucie/Tpt seat
* Jay Prakash is joining auxiliary members
* Rosalie is leaving the auxiliary members.
This is not the final structure. According to the CoC [1], the current
committee publishes the new members and call for public feedback for *six
weeks* and after that, the current committee might apply changes to the
structure based on public feedback.
Please let the committee know if you have any concern regarding the members
and its structure until *09 June 2019* and after that, the new committee
will be in effect and will serve for a year.
[0]:
https://www.mediawiki.org/wiki/Code_of_Conduct/Committee/Members/Candidates
[1]:
https://www.mediawiki.org/wiki/Code_of_Conduct/Committee#Selection_of_new_m…
Amir, On behalf of the Code of Conduct committee
Best
Hi,
There's a new episode out of the MediaWiki podcast "Between the Brackets";
this one is a (very interesting) discussion with Sarah Rodlund and
Alexandra Paskulin, both of whom are technical writers for the Wikimedia
Foundation. You can listen to the episode here:
https://betweenthebrackets.libsyn.com/episode-62-sarah-rodlund-and-alexandr…
-Yaron
--
WikiWorks · MediaWiki Consulting · http://wikiworks.com
As the last release of Python 2 is finally out, the July release of
Pywikibot is going to be the **last release that supports Python 2**.
Support of Python 3.4 and MediaWiki older than 1.19 is also going to be
dropped. After this release, Pywikibot is not going to receive any further
patches and bug fixes related to those Python and MediaWiki versions.
Functions and other stuff specific to Python 3.4, Python 2.x or MediaWiki
older than 1.19 will be removed.
For your convenience, this release is marked with a "python2"
git tag and it is also the last 3.0.x release. In case you really need it,
the Pywikibot team created /shared/pywikibot/core_python2 repository in
Toolforge and a python2-pywikibot package in software repositories of some
operating systems.
The Pywikibot team strongly recommends that you migrate your scripts from
Python 2 to Python 3. The migration steps were described in the previous
message, which can be found here:
https://lists.wikimedia.org/pipermail/pywikibot/2020-January/009976.html
Detailed
plan of Python 2 deprecation with dates is described here:
https://www.mediawiki.org/wiki/Manual:Pywikibot/Compatibility
If you encounter any problems with the migration, you can always ask us
here: https://phabricator.wikimedia.org/T242120
Best regards,
Pywikibot team