Hello all,
We are on the last stretch of the grid engine deprecation process[0] and
this means that the grid will be shutting down on Thursday, the 14th of
March.
You can find a reminder of the full timeline here[1]
There's about 30 tools still running on the grid, if you are one of the few
left to migrate,
kindly ensure they are migrated before the 14th or reach out[2] to the team
if you are facing any challenges or need some assistance.
We have also reached out on phabricator and via email to the remaining
maintainers that still have their tools running on the grid to see if we
can help ease the migration or see if there are any blocking issues.
If you have a tool that is still on the grid and you cannot meet the above
deadline, kindly reach out via the tool migration phabricator ticket or our
support channels[2], note that this is a hard deadline and no extensions
would be granted but we might be able to help you do the transition.
We really appreciate all the effort and feedback given on the new platform,
this will help us improve our service and reduce the maintenance burden in
the long term for tool maintainers and toolforge admins alike.
[0]:
https://wikitech.wikimedia.org/wiki/News/Toolforge_Grid_Engine_deprecation
[1]:
https://wikitech.wikimedia.org/wiki/News/Toolforge_Grid_Engine_deprecation#…
[2]:
https://wikitech.wikimedia.org/wiki/Portal:Toolforge/About_Toolforge#Commun…
--
Seyram Komla Sapaty
Developer Advocate
Wikimedia Cloud Services
Hi everyone,
tl;dr The tools we use to document Wikimedia JavaScript code are changing.
In the short term, you can read the complete MediaWiki core JavaScript docs
using the 1.41 version[0] while we migrate to the new system[1]. If you use
JavaScript documentation on doc.wikimedia.org, please share your feedback
on wiki[2].
Wikimedia JavaScript codebases are switching from using JSDuck[3] to
JSDoc[4] for documentation. Started in 2016, this migration is necessary
because JSDuck is currently unmaintained and does not support the ES6
standard[5]. Several Wikimedia JavaScript codebases, including Vector and
GlobalWatchlist, already use JSDoc, while several others, such as
VisualEditor and MediaWiki core, still use JSDuck.
The migration project consists of two parts: changing the codebases to
support JSDoc and improving the usability of the JSDoc WMF theme. For more
information, see phab:T138401[6].
== Migrating MediaWiki core to JSDoc ==
We are migrating MediaWiki core to JSDoc incrementally. While the migration
is in progress, the master branch docs will be incomplete, containing only
those modules that have been migrated. To read the old JSDuck docs, see the
MediaWiki 1.41 docs[0].
To help with migration, choose a module from the list in phab:T352308[7],
and follow the guide on phab:T138401[6] to translate the tags from JSDuck
to JSDoc.
== Migrating other codebases ==
You can find a list of codebases that use JSDuck on phab:T138401[6].
(Please add any that are missing.) To help migrate a codebase that uses
JSDuck, follow the instructions to set up JSDoc[8], and use the guide in
phab:T138401[6] to translate the tags from JSDuck to JSDoc.
== Improving the JSDoc WMF theme ==
One of the biggest differences between JSDuck and JSDoc is the HTML
interface for reading the docs. The WMF theme for JSDoc is not as
full-featured as the JSDuck theme, but to support this migration, the
Wikimedia Foundation Web, Design Systems, and Technical Documentation teams
are working to prioritize and complete a set of improvements to the JSDoc
theme, with the goal of releasing version 1 of jsdoc-wmf-theme in 2024.
If you use JavaScript documentation on doc.wikimedia.org, please leave a
comment on the JSDoc WMF theme talk page[2] and let us know how you use the
docs and which features of the theme are the most important to you.
Thank you for reading!
Alex, Kamil, Jon, Roan, and Anne
[0]: https://doc.wikimedia.org/mediawiki-core/REL1_41/js/
[1]: https://doc.wikimedia.org/mediawiki-core/master/js/
[2]: https://www.mediawiki.org/wiki/Talk:JSDoc_WMF_theme
[3]: https://github.com/senchalabs/jsduck
[4]: https://en.wikipedia.org/wiki/JSDoc
[5] https://en.wikipedia.org/wiki/ECMAScript
[6]: https://phabricator.wikimedia.org/T138401
[7]: https://phabricator.wikimedia.org/T352308
[8]: https://www.mediawiki.org/wiki/JSDoc
--
Alex Paskulin
Technical Writer
Wikimedia Foundation
Good Morning everyone,
As part of task T359594 <https://phabricator.wikimedia.org/T359594>, I
wanted to inform you that we are scheduled to upgrade our production
gitlab-cloud-runners cluster to 1.29 today at 1 PM EST. This process will
be conducted manually through the DigitalOcean Console, and is expected to
complete by 2 PM EST.
Please Note:
1. CI jobs might experience disruptions during this upgrade window.
2. After the upgrade, I will update the Terraform configuration to match
the updated cluster version.
Thank you for your understanding.
--
Sandeep Singh (he/him)
Software Engineer, Release Engineering.
Wikimedia Foundation
Hello all!
The Search Platform Team usually holds an open meeting on the first
Wednesday of each month. Come talk to us about anything related to
Wikimedia search, Wikidata Query Service (WDQS), Wikimedia Commons Query
Service (WCQS), etc.!
Feel free to add your items to the Etherpad Agenda for the next meeting.
Details for our next meeting:
Date: Wednesday, March 6, 2024
Time: 16:00-17:00 UTC / 08:00 PST / 11:00 EST / 17:00 CET
Etherpad: https://etherpad.wikimedia.org/p/Search_Platform_Office_Hours
Google Meet link: https://meet.google.com/vgj-bbeb-uyi
Join by phone: https://tel.meet/vgj-bbeb-uyi?pin=8118110806927
Have fun and see you soon!
Guillaume
--
*Guillaume Lederrey* (he/him)
Engineering Manager
Wikimedia Foundation <https://wikimediafoundation.org/>
Hi there,
The 1.42.0-wmf.21 version of MediaWiki is currently blocked at group0 due
to:
- https://phabricator.wikimedia.org/T359290: ArgumentCountError: Too few
arguments to function
MediaWiki\Extension\Gadgets\GadgetRepo::titleWithoutPrefix(), 1 passed in
[...]/extensions/Gadgets/includes/GadgetResourceLoaderModule.php
Thank you for your help resolving this issue!
-- Your humble train toiler
--
Jaime Nuche
Software Engineer III
Wikimedia Foundation <https://wikimediafoundation.org/>
Hello,
```~/portals$ git pull origin master
ssh: connect to host gerrit.wikimedia.org port 29418: Network is unreachable
fatal: Could not read from remote repository.
Please make sure you have the correct access rights
and the repository exists.```
I am facing this issue .Can anyone suggest me the cure for this
Hello everyone, how are you? I'm writing because of your interest in
Wikimedia technical development.
Community Tech, the team that organizes the Community Wishlist Survey
<https://meta.wikimedia.org/wiki/Community_Wishlist_Survey>, has been
tasked to design a new Wishlist that is continuous, better integrated into
annual planning, and can efficiently run the intake of community-submitted
technical problems.
Our goal is to pilot this new Wishlist in July 2024.
We invite you to have a chat with Jack Wheeler
<https://en.wikipedia.org/wiki/User:JWheeler-WMF>, who has recently joined
the Wikimedia Foundation as the Lead Community Tech Manager and is
responsible for the Future of the Wishlist
<https://meta.wikimedia.org/wiki/Community_Wishlist_Survey/Future_Of_The_Wis…>
.
Jack would like to have a conversation with you, to get input for the
design of the new survey, starting with how to define a "Wish."
Community Tech would appreciate you chatting with him; your input will be
invaluable.
You can check out Jack's first message to the community
<https://meta.wikimedia.org/wiki/Community_Wishlist_Survey/Future_Of_The_Wis…>,
where you can find a link to proceed to book time to talk to him, or share
your ideas directly on the talkpage with him.
Best regards,
Sandister Tei <https://meta.wikimedia.org/wiki/User:STei_(WMF)> (she/her)
Community Relations Specialist (Community Tech & Trust and Safety)
Wikimedia Foundation
I am trying to reach a remote mysql database from a vps using python. The
destination server has created an opening in the firewall for the request,
but I am still getting network unreachable errors. I gave the ip of the
proxy for the vps, obtained with ping, as the expected ip. I now tried
accessing a web site I control from the same vps also in python using
requests.get, and in the web server log I see the request coming from what
looks to be a gateway (xxx.xxx.xxx.1, rather than the proxy
xxx.xxx.xxx.nnn) Is this to be expected and can I rely on the address for
such requests?
Thanks,
Tim