Hello,
The committee has finished selecting new members and the new committee
candidates are (In alphabetical order):
- Amir Sarabadani
- Kunal Mehta
- Martin Urbanec
- MusikAnimal
- Tony Thomas
And auxiliary members will be (Also in alphabetical order):
- Ariel Glenn
- Effie Mouzeli
- Huji
- Jayprakash12345
- Nuria Ruiz
You can read more about the members in the mediawiki.org page
<https://www.mediawiki.org/wiki/Code_of_Conduct/Committee/Members/Candidates>
.
The changes compared to last term are:
- Kunal Mehta is joining the main CoC committee
- Ariel Glenn is coming back to auxiliary committee
- Effie Mouzeli is joining auxiliary committee for the first time
- Tonina Zhelyazkova is leaving the committee
- Matanya and Tpt are leaving the auxiliary committee
- I won't run for the chair this year.
This is not the final structure. According to the CoC
<https://www.mediawiki.org/wiki/Code_of_Conduct/Committee#Selection_of_new_m…>,
the current committee publishes the new members and calls 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 *26 May 2021* and after that, the new committee
will be in effect and will serve for a year.
Amir, On behalf of the Code of Conduct committee
Best
Hello all,
The Wikimedia hackathon
<https://www.mediawiki.org/wiki/Wikimedia_Hackathon_2021> is coming up in a
few weeks, on May 22-23! We’re very excited to gather online with you all
and hack together.
On top of the informal hacking, we would like to build a light, community
powered program, with sessions and discussions about the technical
environment in the Wikimedia movement. We will have two different “tracks”,
each of them having its own setup:
1.
The main track, a livestream of sessions that will be recorded and
available for replay, hopefully using a fully open source set up. This will
be great for presentations, talks and demos.
2.
The open rooms: two Jitsi rooms will be available to schedule your
sessions. This is perfect for informal discussions, Q&As and workshops.
If you’re interested in running a session in the hackathon’s program, it’s
easy: please create a task on the Phabricator board
<https://phabricator.wikimedia.org/project/board/5303/>, using this template
<https://phabricator.wikimedia.org/maniphest/task/edit/form/1/?title=[Session]%20Provide%20a%20descriptive%20title%20for%20your%20session&description=**Username%20or%20display%20name%20(will%20be%20displayed%20publicly)%3A**%0D%0A%0D%0A**Categories%2FTags%2FKeywords%20(up%20to%205)%3A**%0D%0A%0D%0A%2F%2FList%20some%20tags%20to%20let%20participants%20quickly%20get%20an%20idea%20about%20the%20session%2C%20for%20example%3A%20Documentation%2C%20Maintenance%2C%20Open%20source%20tools%20for%20events%2C%20Wikidata%2C%20Wikipedia%2C%20Gadgets%2C%20etc.%2F%2F%0D%0A%0D%0A**Session%20type%20(select%20one)%3A**%0D%0A%0D%0A-%20%5B%20%5D%20Presentation%20(including%20Q%2FA)%20-%2025%20mins%0D%0A-%20%5B%20%5D%20Discussion%20(including%20Q%2FA)%20-%2055%20mins%0D%0A-%20%5B%20%5D%20Workshop%20(including%20Q%2FA)%20-%2055%20mins%0D%0A-%20%5B%20%5D%20Lightning%20talk%20-%205%20mins%0D%0A%0D%0A**Venue%20(select%20one)%3A**%0D%0A%0D%0A%5B%20%5D%20I%20would%20like%20to%20be%20on%20the%20main%20track%0D%0A%5B%20%5D%20I%20wouldn%27t%20mind%20being%20on%20the%20main%20track%0D%0A%5B%20%5D%20I%20need%20a%20Jitsi%20room%20for%20the%20session%0D%0A%0D%0A**When%20are%20you%20available%20to%20have%20the%20session%3F%20**%0D%0A%0D%0A%2F%2FPlease%20share%20your%20availability%20on%2022%20-%2023%20May%20in%20UTC%20or%20%5B%5B%20https%3A%2F%2Fwww.worldtimebuddy.com%2F%20%7C%20your%20local%20time%20zone%20%5D%5D%2F%2F%0D%0A%0D%0A%23%23%23%20Session%20Details%0D%0A%0D%0A**Short%20description%20of%20the%20session%20(~150%20words)%3A**%0D%0A%0D%0A%2F%2FDescribe%20what%20your%20session%20is%20about%2F%2F%0D%0A%0D%0A**Target%20audience%3A**%0D%0A%0D%0A%2F%2FWho%20is%20this%20session%20most%20relevant%20to%3F%20For%20example%3A%20new%20contributors%2C%20maintainers%2C%20documentarians%2C%20first-time%20attendees%2C%20etc.%2F%2F%0D%0A%0D%0A**What%20will%20participants%20get%20out%20of%20this%20session%3F%20(~50%20words)**%0D%0A%0D%0A%2F%2FThink%20about%20the%20end-goals%20of%20this%20session%2F%2F%0D%0A%0D%0A**(Optional)%20Additional%20resources%3A**%0D%0A%0D%0A%2F%2FShare%20any%20documentation%20or%20links%20where%20participants%20can%20learn%20more%20about%20the%20session%20topics%2F%2F%0D%0A&projects=Wikimedia-Hackathon-2021>,
that will give you all the required information. The coordination team will
come back to you to help you prepare and schedule your session.
You will also find the different formats that we are offering:
presentation, discussion, workshop or lightning talk. All topics are
welcome, as long as they are connected to the technical environment of the
Wikimedia projects. We are particularly interested in sessions that are
useful for newcomers, and connected to the main topics of this year’s
hackathon: open source tools for events, documentation and finding
co-maintainers.
Because we will need some time to schedule the proposed sessions and to
make technical tests with the speakers, please note that the deadline to
submit a session for the main track is May 9th. For the open rooms, you
will have a bit more time, until May 19th.
You will find more information and details about the call for proposals on
the how-to page
<https://www.mediawiki.org/wiki/Wikimedia_Hackathon_2021/How_to>. If you
have any questions, feel free to ask on the discussion page
<https://www.mediawiki.org/wiki/Talk:Wikimedia_Hackathon_2021>. If you want
to brainstorm ideas or find a co-speaker for your session, feel free to ask
the crowd on the hackathon social channels
<https://www.mediawiki.org/wiki/Wikimedia_Hackathon_2021/Discussions>.
Feel free to share the word anywhere you find it useful, and talk about it
with your contacts! Thanks in advance,
For the coordination team,
--
Léa Lacroix
Community Engagement Coordinator
Wikimedia Deutschland e.V.
Tempelhofer Ufer 23-24
10963 Berlin
www.wikimedia.de
Wikimedia Deutschland - Gesellschaft zur Förderung Freien Wissens e. V.
Eingetragen im Vereinsregister des Amtsgerichts Berlin-Charlottenburg unter
der Nummer 23855 Nz. Als gemeinnützig anerkannt durch das Finanzamt für
Körperschaften I Berlin, Steuernummer 27/029/42207.
This is a summary of this week's deployment of the 1.37.0-wmf.3 branch
of MediaWiki and its extensions (also known as "the train"). The
primary person in charge this week was me, Lars Wirzenius, with Jeena
Huneidi as backup, both from the Release Engineering team.
The summary task for this week is
https://phabricator.wikimedia.org/T278347
This week was a little more rocky than usual. I achieved three
personal records: largest number of rollbacks in a week (two), largest
number of errors in logstash after a deployment (63367), and largest
number of deer seen from my window while conducting the train (eight,
in pairs on three different days).
The new version is running all sites. There were a total of six
blockers reported and resolved:
- T281180 - DiscussionTools: Precondition failed: This Title instance
does not represent a proper page, but merely a link target
https://phabricator.wikimedia.org/T281180
- T281184 - PHP Fatal Error: Access level to
CentralAuthPrimaryAuthenticationProvider::$userNameUtils must be
protected (as in class
MediaWiki\Auth\AbstractPasswordPrimaryAuthenticationProvider) or
weaker
https://phabricator.wikimedia.org/T281184
- T281226 - PHP Notice: Only variables should be assigned by reference
https://phabricator.wikimedia.org/T281226
- T281361 - TypeError: Argument 2 passed to
Wikibase\Client\DataAccess\Scribunto\WikibaseLanguageIndependentLuaBindings::trackUsageForSitelink()
must be an instance of Wikibase\DataModel\Entity\ItemId, instance of
Wikibase\MediaInfo\DataMo
https://phabricator.wikimedia.org/T281361
- T281405 - Wikimedia\Rdbms\DBQueryError: Error 1054: Unknown column
'img_actor'
https://phabricator.wikimedia.org/T281405
- T281480 - SqlBlobStore no longer caching blobs (DBConnectionError
Too many connections)
https://phabricator.wikimedia.org/T281480
The last task is still open, as it was worked around quickly, on
Thursday, to avoid a service outage (read: taking down all sites), but
is waiting for a proper fix later.
As usual, a whole bunch of people helped to find, triage, analyze,
fix, or work around problems this. Release Engineering thanks
everyone, without help we wouldn't be able to deploy MediaWiki.
- Aaron Schulz
- Addshore
- Bartosz Dziewoński
- Daimona
- DannyS712
- Gergő Tisza
- Giuseppe Lavagetto
- Jaime Crespo
- Jakob Warkotsch
- James D. Forrester
- Kosta Harlan
- Lucas Werkmeister
- Martin Urbanec
- Pchelolo
- Taavi Väänänen
- Timo Tijhof
- Tim Starling
There may have been other people, and if so, I apologize for not
including them on the list above.
Have a good weekend. Be well. Be safe.
For more information, please see:
- https://phabricator.wikimedia.org/T278347
- https://wikitech.wikimedia.org/wiki/Heterogeneous_deployment/Train_deploys
- https://versions.toolforge.org/
--
WMF release engineering team | he/him or they/them
"Imagine a world in which every single human being can freely share in
the sum of all knowledge."
Hi,
I'm really sorry for sending email to such a large venue but I couldn't
find a better mailing list. Feel free to ignore this email if you don't do
anything with Herald rules.
Herald rules, a set of rules in phabricator to automate the work, are
expensive and slowly making saving any change on phabricator slower and
slower. You can take a look at this ticket.
<https://phabricator.wikimedia.org/T108586>
As the result, we have been migrating these rules to maintenance bot
<https://phabricator.wikimedia.org/p/Maintenance_bot/>. Which means changes
won't be immediately applied anymore (and it'll take up to an hour and they
will be post-change).
If you see your Herald rule has been disabled, please don't enable it. If
you want to change it, you can make a PR in the maintenance bot source code.
<https://github.com/Ladsgroup/Phabricator-maintenance-bot> Please avoid
introducing new Herald rules if there's a similar functionality supported
by the bot. Just add it to the work list of the bot. An exception would be
on time-sensitive tickets. Like handling UBN ones. They will stay as Herald
rules.
Any sort of change to improve documentation, code health, adding new
functionality so we can migrate more Herald rules, or migrating existing
ones would be greatly appreciated. If there are bugs, feel free to create a
ticket for it
<https://phabricator.wikimedia.org/tag/phabricator_maintenance_bot/>.
You can also create email filters to ignore emails triggered by maintenance
bot (which its activity will increase).
Best
--
Amir (he/him)
My use case is this:
I have three alternative access points to the wiki, where some things
are not allowed - e.g. videos. Each access point has different
extensions disabled, and then tags and parser functions show "as is" on
screen, which looks bad.
My goal is to hide those, obviously.
I'm upgrading MW from 1.29 to 1.35; My previous solution is here:
https://github.com/kolzchut/mediawiki-extensions-NoopTags
Basically I hooked ParserFirstCallInitHook and LanguageGetMagic to
dynamically declare empty stubs for those missing function parsers and
tags, using global variables $wgNoopTagsFunctionBlacklist and
$wgNoopTagsBlacklist.
This doesn't work in MW 1.35, because LanguageGetMagic was removed. I
tried bypassing the issue by hooking GetMagicVariableIDsHook, but
apparently that's only for "variables" ({{variable}}), and not parser
functions.
Is there a way to achieve my goal? Either by fixing my extension or
doing something completely different which I haven't thought about?
Thanks in advance
Dror
Hi,
The next datacenter switchover is scheduled for the week of June 28th.
If you're not familiar with why we do this, I'd suggest reading [1].
Starting next week I'll be reaching out to service owners/maintainers to
finalize the list of services that we will be switching over, checking
what work/improvements need to be made from what we learned in the last
switchover.
One notable change this time is that we are still planning to run the
MediaWiki deployment train. This both mimics a real unplanned switchover
situation where the train is running, as well as avoiding the situation
of having three weeks worth of code go out in one train because of other
scheduled train disruptions[2].
The tracking task for this is <https://phabricator.wikimedia.org/T281515>.
[1] https://diff.wikimedia.org/2017/04/18/codfw-temporary-editing-pause/
[2] https://wikitech.wikimedia.org/wiki/Deployments/Yearly_calendar
-- Kunal
Hello all,
I would like to announce the release of MediaWiki Language Extension
Bundle 2021.04. This bundle is compatible with MediaWiki 1.34 or above
and requires PHP 7.2 or above.
Next MLEB is expected to be released in 3 months. If there are very
important bug fixes, we will do an intermediate release. Please give
us your feedback at
[[Talk:MLEB|https://www.mediawiki.org/wiki/Talk:MLEB]].
* Download: https://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2021.04.tar…
* sha256sum: 652b7838b4c87fba80ca46ebd15a106bf3fd4e9cc202417de6ee3ad33d2a8048
* Signature: https://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2021.04.tar…
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 ==
* Fixed Mediawiki requirement. Requires >= 1.34.0.
* Maintenance and localization updates.
== cldr, CleanChanges and LocalisationUpdate ==
* Maintenance and localization updates only.
== Translate ==
* Consider translated optional messages towards meeting the export
threshold ({{Phab|T159122}})
* Do not lock pages indefinitely during translatable page moves
({{Gerrit|661125}})
* Support new HTML-y translation variable syntax ({{Phab|T274881}})
* Limit pages that can be moved from the UI to 500 by default.
({{Phab|T277431}})
** This can be modified by updating the configuration:
<code>$wgTranslatePageMoveLimit</code>
* Add moveTranslatablePage script that can move any number of pages
({{Phab|T275109}})
* Rename Special:SupportedLanguages to Special:ActiveLanguages
externally ({{Gerrit|673007}})
* Add description/summary to Special:PagePreparation ({{Phab|T276911}})
* Add help link to Special:PageMigration | ({{Phab|T277031}})
* (MW >= 1.36) Enable "opt-in" translation aware transclusion for
templates ({{Phab|T47096}})
** This has to be manually enabled for existing translatable pages but
is enabled by default for new pages.
* Add script to cleanup obsolete rows from translate_groupstats
({{Gerrit|673261}})
* Fix metadata handling for translatable page moves and deletions
({{Gerrit|666357}})
* Namespace for classes under the <code>src/</code> folder has been
changed to: <code>MediaWiki\Extension\Translate</code> instead of:
<code>MediaWiki\Extensions\Translate</code>. <code>class_alias</code>
has been used to ensure existing functionality and cached data does
not break. The alias will be removed in the next MLEB release.
== UniversalLanguageSelector ==
* Ensure ULS supports modern Vector ({{Phab|T273232}},{{Phab|T273928}})
* Maintenance and localization updates.
=== Fonts ===
* Update Junicode to 1.002 ({{Phab|T173573}})
--
Kartik Mistry | કાર્તિક મિસ્ત્રી
kartikm.wordpress.com