So I see that User:Grunny, User:Rtnf and Dessalegn Yehuala were appointed.
Respectfully, given the criteria was someone with +2 rights, I would
question the decision to appoint Dessalegn Yehuala, who not only has never
contributed to MediaWiki, but also appears to have never edited any
Wikimedia project, or even have an account.
On Thu, Oct 6, 2022 at 1:58 AM Technical Decision Forum Support <
> Hi Brian,
> We have our representatives but we are always looking for some more as we
> rotate throughout the year. My apologies for the late updates to the
> forum. The lists are here
> <https://www.mediawiki.org/wiki/Technical_decision_making/Forum>. The
> community representatives have completed one feedback to the IP Masking
> Proposal and next week we should have "Modern user interfaces for all
> users" proposal out to the representatives for their feedback. You can see
> it on the TDF <https://phabricator.wikimedia.org/project/board/5179/>
> Thank you,
> On Wed, Oct 5, 2022, 5:46 PM Brian Wolff <bawolff(a)gmail.com> wrote:
>> Out of curiosity, what happened? Aug 12 has come and gone. More to the
>> point, i was wondering if TDF is even still a thing?
>> On Tuesday, August 2, 2022, Erica Litrenta <elitrenta(a)wikimedia.org>
>>> Hi everyone.
>>> This is a reminder that the search for community representatives for the
>>> Technical Decision Forum is still OPEN.
>>> There are a few weeks left to apply and/or recommend someone who would
>>> be a great fit for the role (learn more at
>>> Please let us know if there are any questions we can answer before you
>>> submit your application, or a friend's name! Email us at
>>> TDFSupport(a)wikimedia.org by Aug 12, 2022.
>>> Looking forward to hearing from you soon…
>>> The Technical Decision Forum.
>>> On Tue, Jul 12, 2022 at 11:17 AM Erica Litrenta <elitrenta(a)wikimedia.org>
>>>> *(This email may not be written in your native language, and/or may be
>>>> a crosspost: our apologies.)*
>>>> Greetings, everyone.
>>>> The Technical Decision Forum, or TDF (1), is seeking community
>>>> representatives. Please visit the TDF Community Representation (2)
>>>> page for more information, and email TDFSupport(a)wikimedia.org by Aug
>>>> 12, 2022 to be considered for selection.
>>>> Don't worry about the requirements listed on wiki, they are not set in
>>>> stone; just provide your name, name of the group you "represent" if any,
>>>> and a short sentence or two explaining your interest.
>>>> For any questions, please post at *MediaWiki.org (3)*, or on the
>>>> related Movement Strategy Forum topic (4), or simply email
>>>> The Technical Decision Forum.
>>>> (1) https://www.mediawiki.org/wiki/Technical_decision_making/Forum
>>>> (3) https://www.mediawiki.org/wiki/Talk:Technical_decision_making/Forum
>>>> Erica Litrenta (she/her)
>>>> Senior Manager, Community Relations Specialists (Product)
>>>> Wikimedia Foundation
>>> Erica Litrenta (she/her)
>>> Senior Manager, Community Relations Specialists (Product)
>>> Wikimedia Foundation <https://meta.wikimedia.org/wiki/User:Elitre_(WMF)>
Just a reminder that there are 7 days left to submit your Coolest Tool Award
Please recommend your favorite tools by October 12.
Komla, for the Coolest Tool Academy 2022
Seyram Komla Sapaty
Wikimedia Cloud Services
The eighth workshop on the topic of "How to interact with Wikidata via
Pywikibot" is coming up - it will take place on Friday, October 7th at
16:00 UTC. You can find more details on the workshop and a link to join
This workshop will summarise how to access and save information to
Wikidata, including through page generators and queries*, using Pywikibot.
It will also cover the Wikidata conventions about the bot editing,
including the bot approvals process (*queries not included, please bring
your own!). This session will be run by Mike Peel.
To participate in this workshop, you would need basic familiarity with
Wikidata and Pywikibot installation.
We look forward to your participation!
On behalf of the SWT Workshops Organization team
Senior Developer Advocate
Wikimedia Foundation <https://wikimediafoundation.org/>
This email is a summary of the Wikimedia production deployment of
* Conductor: Brennen Bearnes
* Backup Conductor: Jaime Nuche
* Blocker Task: T314192 <https://phabricator.wikimedia.org/T314192>
* Current Status <https://versions.toolforge.org>
Sparklines comparing with the last 5 trains.
* 208 Patches ██▇▁▃
* 1 Rollbacks ▁▄█▁▄
* 1 Days of delay ▁██▁█
* 1 Blockers ▄▄█▄▁
🌈 Traintastic Folks ✨
Thanks to folks who reported or resolved blockers:
* revi | 레비
* Amir Sarabadani
This is a heads-up message about upcoming changes to MediaWiki-Vagrant.
With MediaWiki master now requiring PHP 7.4, MediaWiki-Vagrant is now completely unusable with MediaWiki. Currently, MediaWiki-Vagrant still uses Debian Stretch, for which custom PHP 7.2 packages were compiled. These are the same that were previously used in production. Stretch is now out of support completely, and no PHP 7.4 packages are available for it. Production already switched to Buster and has only compiled PHP 7.4 for that distro. As a result, switching to Debian Buster is the only remaining option. Because the buster-migration branch is out of date and equally broken, it will be abandoned and its patches cherry-picked onto master. A stretch-compat branch will be created but is basically useless unless you're trying to run older wmf release branches.
The phabricator task for the buster migration is https://phabricator.wikimedia.org/T256822.
The perennial discussion about ways to provide logged-out users with
persistent customization of their reading experience in the browser has
cropped up again in the context of the pending deployment of Vector 2022.
Can a cookie-based width toggle
be offered without splitting the cache or otherwise making the toggler
regret their tog?
The answers currently range from "*shouldn't be very complicated or hacky,
just toggling a class*..." and "*can be delivered to logged-out users on
top of the cached parser output*.." to "*impossible*".
Could someone clarify the challenges and costs of trying to toggle css
classes in this way?
Samuel Klein @metasj w:user:sj +1 617 529 4266