Phabricator (phabricator.wikimedia.org) will be down tomorrow sometime
during the 15:00–17:00 UTC[0] maintenance window[1].
We're deploying updates during that time, and we'll stop Phabricator
briefly to run database migrations.
I'm sorry if the timing of the upgrade window is inconvenient for
anyone. But having more folks around at the time of the upgrade
mitigates some of the risks, too.
Thank you!
Tyler Cipriani (he/him)
Engineering Manager, Release Engineering
Wikimedia Foundation
[0]: <https://zonestamp.toolforge.org/1655305257>
[1]: <https://wikitech.wikimedia.org/wiki/Deployments#deploycal-item-20220615T1500>
The 1.39.0-wmf.16 version of MediaWiki is blocked[0].
The new version is currently being deployed to testwikis, but can
proceed no further until this issue is resolved or triaged as irrelevant:
* Investigate McRouter GET request spike from wmf.15
- https://phabricator.wikimedia.org/T310532
Once these issues are resolved train can resume.
Thank you for your help resolving these issues!
-- Your humble train toilers
[0]. https://phabricator.wikimedia.org/T308069
[1]. https://versions.toolforge.org/
Hello all - I wanted to share the news about the Wikimedia Foundation's new
Chief Product and Technology Officer, Selena Deckelmann. Please see below
for the note I sent to wikimedia-l yesterday about Selena and her response,
and join me in welcoming her to the movement.
Maryana
*****
Hi all,
When I started in January, I shared with you that one of my top priorities
<https://meta.wikimedia.org/wiki/Wikimedia_Foundation_Chief_Executive_Office…>
coming to the Wikimedia Foundation was to actively step in and support the
Foundation’s product and technology teams while we recruited executive
leadership of these mission critical functions with a new Chief Product and
Technology Officer.
I am delighted to introduce you to Selena Deckelmann
<https://wikimediafoundation.org/news/2022/06/13/wikimedia-foundation-welcom…>,
who will be joining the Wikimedia Foundation on August 1. She is based in
Portland, Oregon in the United States.
Selena is currently the Senior Vice President at Mozilla, where she has
been for the last nine years. She leads the Firefox organization of more
than 400 people responsible for all Firefox product and technology
functions including desktop, mobile, web platform, and browser services.
I have gotten to know Selena over several months and also learned from
people who have worked with her over many years. She is known for
successfully driving change by getting stakeholders aligned around what’s
needed, and being seen as a trusted partner. Selena has built strong
credibility over many years with colleagues and also with a broader
developer community. She is described as a leader who can make the tough
decisions, develop skills, grow diverse contributors, and inspire teams.
She also has a great laugh and looks for joy in her work!
As context for the recruitment process: given the critical need to get this
right, we used two firms with global search expertise who specialized in
product/technology executive leadership roles. This meant double the work,
but allowed us to more quickly build a large, globally diverse pool of over
500 candidates. Once we identified a smaller number of finalists, they
participated in real-life case studies of some of our current challenges
and met with Wikimedia stakeholders over the course of many months.
As you all know, we have a highly unique and sometimes difficult
environment with a multifaceted mission, complex structure, and often
competing stakeholders. This is going to be a challenge for anyone,
especially given the steep learning curve at Wikimedia (which I can confirm
from my own experience!). I hope you will sign up to help me successfully
onboard Selena as she gets started!
Selena shares her own message with you below, and she can be reached
directly at sdeckelmann(a)wikimedia.org.
Maryana
Maryana Iskander
Wikimedia Foundation CEO
*****
*From Selena:*
Hello!
I’m so excited to join you all, and I am grateful to Maryana and the many
people I’ve met on my journey to today’s announcement. Thank you for this
opportunity to introduce myself!
My grandfather was a TV repairman and I grew up watching him tinker and fix
things, but college was when I decided to explore electronics and
computers. I started college thinking that I would play jazz violin and
maybe get a chemistry degree! A year later, I’d learned about the Internet
which resulted in skipping classes to install Linux from floppy disks, and
landing a job at a help desk.
My first programming language was TI-Basic
<https://en.wikipedia.org/wiki/TI-BASIC>, and my second was C++. I spent
many years with Perl (I’ve had dreams in Perl!), SQL
<https://www.reddit.com/r/SQL/comments/doukj2/is_sql_considered_codingprogra…>
and later Python, and I’ve dabbled with wikis, including Federated Wiki and
MediaWiki. I admire Ursula Franklin
<https://en.wikipedia.org/wiki/Ursula_Franklin> and love her book The Real
World of Technology.
As I explored computers back in college, I felt compelled to share. The
experience didn’t feel complete if I was alone. I vividly remember the
people I connected with – who mentored me, who I wrote software with and
who just listened. My love for the internet, its freedoms and
connectedness, came from discovering a world of knowledge freely shared
beyond anything I had imagined before.
During my interviews with Wikimedia, I felt that strong connection again. I
heard each person share their reasons for joining this movement and their
hopes for its future – often in the form of very challenging questions!
In the last few years, I’ve worked on problems at the intersection of
Mozilla’s mission to help create an internet for the benefit of
individuals, and its business. Very recently, this work resulted in
shipping Total Cookie Protection, making several major changes to the UX of
Firefox and launching a small advertising business called Firefox Suggest,
designed with lean data practices from the start. I loved doing this work
because of the difficulty of it, how intensely those involved had to work
to understand one another and the communities they served, and that my
pragmatic optimism had a part to play in getting things shipped.
I also reflected on this moment in my own life: I grew up in Montana
<https://en.wikipedia.org/wiki/Montana>, where I attended public school. I
love talking about, reading about
<https://www.caseyjohnston.net/ask-a-swole-woman-archive/2021/10/23/how-do-i…>
and sometimes doing weightlifting. I’m hapa
<https://www.janm.org/exhibits/hapa-me>, and I met the Chinese part of my
family as an adult. I think privacy and freedom
<https://papers.ssrn.com/sol3/papers.cfm?abstract_id=2175406> are
intimately connected, and that exercising freedoms is a good way to keep
them. I’m married to a high school teacher, and I have two kids who love to
crash video meetings, including my interviews with the Wikimedia
Foundation.
All of that, together, is why I’m joining the Foundation. Wikipedia is the
promise of collaboration on the internet and the movement for free
knowledge made good on, in practice not in theory. I believe that Wikimedia
projects have successfully demonstrated a model that produces trustworthy
knowledge, and have created a home on the internet that the world
profoundly trusts. I want to help make and ship things to advance free
knowledge using the skills I have, while also continuing to learn from this
ever expanding community of people all around the world.
I plan to follow Maryana’s lead, and will start by meeting many people to
really understand what we collectively need to create a global, equitable
and inclusive future for free knowledge.
Although I will join officially in August, I would love to hear from
anyone interested in sharing directly with me at sdeckelmann(a)wikimedia.org.
-selena
🚂🌈Summary of 1.39.0-wmf.14 train deployment
This email is a summary of the Wikimedia production deployment of
1.39.0-wmf.14
- Conductor: Jeena Huneidi
- Backup Conductor: Ahmon Dancy
- Blocker Task: T308067 <https://phabricator.wikimedia.org/T308067>
- Current Status <https://versions.toolforge.org>
🔢 Stats
Sparklines comparing with the last 5 trains.
- 259 Patches ▂▁█▆▄
- 0 Rollbacks ▁█▁▁▁
- 0 Days of delay ▁█▁▁▁
- 4 Blockers ▁█▃▂▂
🎉 Trainbow Love 🎉 Thanks to folks who reported or resolved blockers:
- Derk-Jan Hartman
- Amir Sarabadani
- Samuel
- Lucas Werkmeister (WMDE)
- Jon Robson
--
Jeena Huneidi
Software Engineer, Release Engineering
Wikimedia Foundation
Hi folks -
*TL;DNR:* Can MediaWiki encode URL fragments in its API responses?
The iOS team noticed the MediaWiki Notifications API
<https://www.mediawiki.org/wiki/Notifications/API> returns partially
encoded URLs - the paths look to be encoded, but the fragments are not.
This causes issues with user talk page notifications with topic title
fragments in certain languages:
...
"legacyPrimary": {
"url": "//
ar.wikipedia.org/wiki/%D9%86%D9%82%D8%A7%D8%B4_%D8%A7%D9%84%D9%85%D8%B3%D8%…
غير_جيد",
"label": "اعرض الرسالة"
}
...
Our Swift URLs (which are based on RFC 1808) fail to instantiate with these
unencoded fragments. This led to some cross-team discussion on T307603
<https://phabricator.wikimedia.org/T307603> about where and how to fix
this. Does this seem like something that could (or should) be fixed deeper
within MediaWiki? Can we encode the fragments of urls in the response of
any MediaWiki API?
@matmarex did some excellent investigation in this comment
<https://phabricator.wikimedia.org/T307603#7955104>, and it sounds like the
original Chrome bug that led to this unencoded fragment need within
MediaWiki is no longer an issue. We're open to fixing it client-side if
this proposal is a no-go, but I wanted to make sure we weren't putting in a
client-side workaround for a server-side workaround that is no longer
needed. I appreciate any thoughts!
*Toni Sevener*
iOS Software Engineer
Wikimedia Foundation <https://wikimediafoundation.org/>
Hi,
I've recently discovered that namespace names may have an ambiguity with
interlanguage links: If a namespace name is the same as a language code,
using it in wikitext poses all kinds of challenges.
Actual example: In the Tyap language (code kcg), the Wikipedia in which was
created a few days ago, the Category namespace is called "Sa:", which is
also the language code and, hence, the interlanguage link code for Sanskrit.
So, "Sa" is usable in wikitext, but has all kinds of little issues. For
example, old-style non-Wikidata interlanguage links to Sanskrit from the
Tyap Wikipedia are probably impossible. They are not very likely to be
inserted into articles, but still, it's somewhat conceivable. I also
noticed that it confuses Pywikibot in some ways. And I can imagine other
subtle bugs that it will cause.
I've asked Tyap speakers whether it's possible to change the word for
"Category" to something else. No—they want to use "Sa". It's legitimate not
to want to change the word for a technical reason.
So what can be done?
The editors there told me that it's OK for them to use "[[Category:" in
wikitext, but they would like to see "Sa:" in the title of category pages.
I'm not sure that it's possible: as far as I know, the namespace name
definition in MessagesKcg.php will be used for both things, and if Visual
editor is used to add categories, it will add "[[Sa:". Bots or gadgets can
be used to replace it to "Category", but is looks like an ugly hack.
Does anyone have better ideas for a robust, comprehensive solution?
--
Amir Elisha Aharoni · אָמִיר אֱלִישָׁע אַהֲרוֹנִי
http://aharoni.wordpress.com
“We're living in pieces,
I want to live in peace.” – T. Moore