A note that after a difficult end of last week and some further
complications today, we're abandoning the 1.36.0-wmf.28 train,
rolling all wikis back to wmf.27, and proceeding with wmf.29 once
unblocked during this week's usual train windows.
This is a somewhat unusual step, but hopefully it will simplify the
process this week.
We're treating the following outstanding issues as blockers for wmf.29:
* ApiEchoUnreadNotificationPages.php PHP Notice: Undefined index: query
* MemcachedPeclBagOStuff: Serialization of 'Closure' is not allowed
* Accessing WikiPage that cannot exist as a page: w:Help:Books/Book
creator text. [Called from WikiPage::exists]
* MimeAnalyzer::improveTypeFromExtension() must be of the type string,
Thanks in advance for any help resolving these issues. Also thanks to
Urbanecm and Pchelolo for work over the weekend clearing some obstacles
for the wmf.28 version, and all who helped out late last week.
-- Brennen, on behalf of your faithful train crew
we are planning to change how Cloud VPS instances and Toolforge tools contact
WMF-hosted wikis, in particular the source IP address for the network connection.
The new IP address that wikis will see is 188.8.131.52.
The change is scheduled to go live on 2021-02-08.
More detailed information in wikitech:
If you are a Cloud VPS user or Toolforge developer, check your tools after that
date to make sure they are properly running. If you detect a block, a rate-limit
or similar, please let us know.
If you are a WMF SRE or engineer involved with the wikis, be informed that this
address could generate a significant traffic volume, perhaps about 30%-40% total
wiki edits. We are trying to smooth the change as much as possible, so please
send your feedback if you think there is something we didn't account for yet.
Thanks, best regards.
Arturo Borrero Gonzalez
SRE / Wikimedia Cloud Services
I have upgraded our Gerrit instances from v3.2.5 to v3.2.7 today at
10:00 UTC. There should be barely any user facing changes.
The upgrade addresses a memory leak I have found on Christmas which was
forcing us to restart our Gerrit on a monthly basis. For reference:
If you find a regression please do file a new task in Phabricator
Antoine "hashar" Musso
The Search Platform Team
<https://www.mediawiki.org/wiki/Wikimedia_Search_Platform> usually holds
office hours the first Wednesday of each month. Come talk to us about
anything related to Wikimedia search, Wikidata Query Service, Wikimedia
Commons Query Service, etc.!
Feel free to add your items to the Etherpad Agenda for the next meeting.
Details for our next meeting:
Date: Wednesday, February 3rd, 2021
Time: 16:00-17:00 GMT / 08:00-09:00 PST / 11:00-12:00 EST / 17:00-18:00 CET
Google Meet link: https://meet.google.com/vyc-jvgq-dww
Join by phone in the US: +1 786-701-6904 PIN: 262 122 849#
Hope to talk to you Wednesday!
Sr. Computational Linguist, Search Platform
UTC-5 / EST
Hey folks, this is an occasional reminder about how to spread basic
information about technical changes to the Wikimedia communities. There are
enough new people coming into the Wikimedia technical spaces that I send
this out every now and then. If it's not relevant to you, or you know
everything about Tech News, you can stop reading now.
Tech News is the technical newsletter for the Wikimedia wikis. It’s not the
only way to reach our communities, and major projects will reach out in
many ways, but it is our main way of keeping them informed of changes big
Here is the latest issue of the newsletter:
ABOUT TECH NEWS
a) What is Tech News?
Tech News is a newsletter for reaching out with technical updates to the
general Wikimedia editor communities, to make sure they can keep track of
what’s happening. Most items talk about changes from the Foundation, but
many items are about work done by volunteer developers or Wikimedia
Deutschland staff. It’s typically distributed in 18–24 languages, reaching
roughly 100 community pages (Village Pumps etc) in addition to those who
read it on Meta, see it included in the Signpost, get it in their email
inbox, or are among the 850 individual subscribers. Typically, this is how
we tell our editors we are changing or planning to change something.
b) How is Tech News written?
Simplification is key. Technical news for non-technical readers. Should be
easy to translate as well as be written with en-1 and en-2 readers in mind.
A couple of sentences per item, then a link to a Phabricator task, wiki
page or email if they need more information. Too long and we put an
unreasonable burden on the translators. This doesn’t mean you should avoid
adding things because all of this seems difficult – we’ll edit it, if
necessary. It’s a wiki, after all.
c) I’ve done something technical. The communities should know. How do I add
Just add it. This is the best and simplest way.
https://meta.wikimedia.org/wiki/Tech/News/Next will take you to the
relevant issue. Remember to link to a relevant Phabricator task, wiki page
or archived mailing list email.
(You can also add the “user-notice” tag in Phabricator together with a
simple 1–3 sentence explanation of what this is and how it affects editors.
Don’t worry about polish; we’ll take care of that. Or if you’re not sure if
it fits the newsletter – we’ll take a look, and if it doesn’t, we’ll just
remove the tag.)
d) When is it distributed?
Weekly, each Monday afternoon/evening UTC. The deadlines for additions are
several days prior to that to give the translators time to do their work.
for when to add things to have them included in the next newsletter.
This is typically earlier than people tend to assume.
e) What is Tech News not?
* A general Wikimedia newsletter. Everything in the Wikimedia world is at
most one step removed from being technical. This doesn’t mean Tech News is
the best place. Typical items are new or upcoming features or potential
* The way to reach the Wikimedia technical community. If you want to reach
Wikimedia developers, an email to wikitech-l is usually better than an item
in Tech News. Tech News is a way to keep Wikimedia contributors up-to-date
with technical changes.
* A way to talk about all the important things that happen in the
background. They’re often awesome and we should talk more about them, but
if they don’t affect how contributors interact with the sites, then this is
not the place.
* A place for updates about one wiki. If it’s just relevant for English or
German Wikipedia, you should inform English or German Wikipedia, not the
entire Wikimedia community. Exceptions to this rule are Commons and
Wikidata, because they’re used by so many other Wikimedia wikis.
The best time to do this for minor things is typically the week they go
out, i.e. you add it by Thursday the week before the change we’re talking
about, which means it’s in the newsletter delivered on the Monday before
the train goes out Tuesday through Thursday, but anything major should
probably be flagged under “future news” much earlier – preferably while
it's still possible to act on relevant community feedback.
1.36.0-wmf.28 had to be rolled back entirely on Friday due to a faulty
hard deprecation of some of MediaWiki interfaces.
Backport patches have/are being merged right now. I will push the train
to group 0 as soon as that has completed.
I will push to group 1 13:00 UTC / 14:00 CET
(just after the backport window).
The rest of wikis will be done later tonight, at 20:00 UTC which is the
usual American train slot.
Train blocker task: https://phabricator.wikimedia.org/T271342
Antoine "hashar" Musso
Hi Community Metrics team,
This is your automatic monthly Phabricator statistics mail.
Accounts created in (2021-01): 322
Active Maniphest users (any activity) in (2021-01): 1043
Task authors in (2021-01): 540
Users who have closed tasks in (2021-01): 288
Projects which had at least one task moved from one column to another on
their workboard in (2021-01): 301
Tasks created in (2021-01): 2416
Tasks closed in (2021-01): 2180
Open and stalled tasks in total: 46706
* Only open tasks in total: 45856
* Only stalled tasks in total: 850
Median age in days of open tasks by priority:
Unbreak now: 11
Needs Triage: 625
(How long tasks have been open, not how long they have had that priority)
Active Differential users (any activity) in (2021-01): 3
To see the names of the most active task authors:
* Go to https://wikimedia.biterg.io/
* Choose "Phabricator > Overview" from the top bar
* Adjust the time frame in the upper right corner to your needs
* See the author names in the "Submitters" panel
TODO: Numbers which refer to closed tasks might not be correct, as
described in https://phabricator.wikimedia.org/T1003 .
Fab Rick Aytor
(via community_metrics.sh on phab1001 at Mon 01 Feb 2021 12:00:17 AM UTC)