Hi all,
For your information, part of the September 2023 datacenter switchover
<https://wikitech.wikimedia.org/wiki/Switch_Datacenter>, the primary
deployment server is now deploy2002.codfw.wmnet.
If you use the alias deployment.eqiad.wmnet, please note that the host key
has changed.You may want to run
wmf-update-known-hosts-production.
Please reach out if you encounter any issue, either by responding to this
email, or by filing a sub-task to https://phabricator.wikimedia.org/T345263.
Thanks,
Kamila Součková (they/them)
Senior SRE
Wikimedia Foundation
The QTE, Cloud Services, and Release Engineering team (collectively known
as DevEx, Developer Experience) are kicking off a new project to create an
advanced prototype of an on-demand test environment provisioner called
Catalyst. This tool is a logical successor to Patch Demo
<https://patchdemo.wmflabs.org/>, which could deploy MediaWikis for testing
but not services, and DUCT
<https://people.wikimedia.org/~kindrobot/duct/presentation.html>, which
could deploy Mediawikis and services for testing in Wikifunctions
<http://wikifunctions.org>, but was not scalable to other teams/projects.
We expect the MVP (minimum viable prototype) to be ready in approximately
two months and would be very interested in input/help from the community,
both with the prototype and with where a generally available product might
look like thereafter. More information on the project, its technology
stack, and how to get involved is at
https://wikitech.wikimedia.org/wiki/Catalyst.
--
*Stef Dunlap* (she/her)
Staff Software Engineer
Wikimedia Foundation <https://wikimediafoundation.org/>
Hi everybody,
In https://phabricator.wikimedia.org/T342116 the Machine Learning team
announces its intention to deprecate the mediawiki.revision-score stream.
For external users, the stream is consumable via the
https://stream.wikimedia.org API and it currently has very few users.
Our idea is to create smaller streams, one for each model type, instead of
having a big aggregator. For example, revision 123456 for enwiki ends up
with several scores from various models in the current revision-score
stream, that is convenient but very hard to manage and maintain for us
(since it is not clear if users are interested in all the data or only a
subset of it). The revision-score stream is also very tightly coupled with
the ORES' architecture, which we are trying to deprecate. In the future we
plan to have smaller streams, in which every revision will get associated
with a single score, from a specific model server:
mediawiki.revision-score-goodfaith
mediawiki.revision-score-damaging
...
...
[ and also new models that will be deployed. ]
To avoid creating unnecessary streams, we'll create the ones that WMF teams
and the community will need and ask during the next months. If you have any
requirement, please follow up with us:
- Email: ml(a)wikimedia.org
- Phabricator: #Machine-Learning-Team tag
- IRC (Libera): #wikimedia-ml
If you are a user of the Mediawiki revision-score stream please follow up
on the task above explaining your use case, we'll try to do our best to
find a good solution for you!
Thanks in advance,
Regards,
Luca
Dear fellow developers! If you don't work on gadgets or Wikimedia code,
feel free to ignore this email!
For some time we've had the Stable interface policy which has been super
helpful for backend-development. I would love us to have an equivalent for
frontend code.
For the past 3 years we have been building one with feedback and
suggestions from gadget developers, WMF staff and Wikimedia volunteers. The
current draft can be found at:
https://www.mediawiki.org/wiki/User:Jdlrobson/Stable_interface_policy/front…
I would like to make this policy official so that we can get the benefits
of having a document and continue to evolve it in a more official capacity.
If anyone wants to veto this, I'd like to hear from you on the talk page or
by a reply to this email (either privately or publicly). When making a veto
please make that explicit and include the text you find problematic and
details about why.
If there is no active veto after one month, this policy will be made
official and moved to
https://www.mediawiki.org/wiki/Stable_interface_policy/frontend.
Thanks in advance for all your help with this important matter!
Jon Robson
PS. This note has also been sent to tech news.
Hi,
I think the email somehow didn't reach wikitech-l and some other mailing
lists (except ambassadors)
Am Mo., 4. Sept. 2023 um 15:46 Uhr schrieb Benoît Evellin (Trizek) <
bevellin(a)wikimedia.org>:
> Hello all,
>
>
> Sorry for cross-posting.
>
> The Technical Decision-Making Forum Retrospective
> <https://www.mediawiki.org/wiki/Technical_decision_making> team invites
> you to join one of our “listening sessions” about the Wikimedia's technical
> decision-making processes.
>
> We are running the listening sessions to provide a venue for people to
> tell us about their experience, thoughts, and needs regarding the process
> of making technical decisions across the Wikimedia technical spaces. This
> complements the survey
> <https://wikimediafoundation.limesurvey.net/885471?lang=en>, which closed
> on August 7.
>
> Who should participate in the listening sessions?
>
> People who do technical work that relies on software maintained by the
> Wikimedia Foundation (WMF) or affiliates. If you contribute code to
> MediaWiki or extensions used by Wikimedia, or you maintain gadgets or tools
> that rely on WMF infrastructure, and you want to tell us more than could be
> expressed through the survey, the listening sessions are for you.
>
> How can I take part in a listening session?
>
> There will be four sessions on two days, to accommodate all time zones.
> The two first sessions are scheduled:
>
> - Wednesday, September 13, 14:00 – 14:50 UTC
> <https://zonestamp.toolforge.org/1694613630>
> - Wednesday, September 13, 20:00 – 20:50 UTC
> <https://zonestamp.toolforge.org/1694635220>
>
>
> The sessions will be held on the Zoom platform.
>
> If you want to participate, please sign up for the one you want to attend:
> <
> https://www.mediawiki.org/wiki/Technical_decision_making/Listening_Sessions>.
> If none of the times work for you, please leave a message on the talk page.
> It will help us schedule the two last sessions.
>
> The sessions will be held in English. If you want to participate but you
> are not comfortable speaking English, please say so when signing up so that
> we can provide interpretation services.
>
> The sessions will be recorded and transcribed so we can later go back and
> extract all relevant information. The recordings and transcripts will not
> be made public, except for anonymized summaries of the outcomes.
>
> What will the Retrospective Team do with the information?
>
> The retrospective team will collect the input provided through the survey,
> the listening sessions and other means, and will publish an anonymized
> summary that will help leadership make decisions about the future of the
> process.
>
> In the listening sessions, we particularly hope to gather information on
> the general needs and perceptions about decision-making in our technical
> spaces. This will help us understand what kind of decisions happen in the
> spaces, who is involved, who is impacted, and how to adjust our processes
> accordingly.
>
> Are the listening sessions the best way to participate?
>
> The primary way for us to gather information about people’s needs and
> wants with respect to technical decision making was the survey
> <https://wikimediafoundation.limesurvey.net/885471?lang=en>. The
> listening sessions are an important addition that provides a venue for free
> form conversations, so we can learn about aspects that do not fit well with
> the structure of the survey.
>
> In addition to the listening sessions and the survey, there are two more
> ways to share your thoughts about technical decision making: You can post
> on the talk page
> <https://www.mediawiki.org/wiki/Talk:Technical_decision_making/Technical_Dec…>,
> or you can send an email to <tdf-retro-2023(a)lists.wikimedia.org>.
>
> Where can I find more information?
>
> There are several places where you can find more information about the
> Technical Decision-Making Process Retrospective:
>
> -
>
> The original announcement about the retrospective from Tajh Taylor:
> https://lists.wikimedia.org/hyperkitty/list/wikitech-l@lists.wikimedia.org/…
> -
>
> The Technical Decision-Making Process general information page:
> https://www.mediawiki.org/wiki/Technical_decision_making
> -
>
> The Technical Decision-Making Process Retrospective page:
> https://www.mediawiki.org/wiki/Technical_decision_making/Technical_Decision…
> -
>
> The Phabricator ticket: https://phabricator.wikimedia.org/T333235
>
>
> Who is running the technical decision making retrospective?
>
> The retrospective was initiated by Tajh Taylor. The core group running the
> process consists of Moriel Schottlender (chair), Daniel Kinzler, Chris
> Danis, Kosta Harlan, and Temilola Adeleye. You can contact us at <
> tdf-retro-2023(a)lists.wikimedia.org>.
>
> Thank you for participating!
>
> --
>
> Benoît Evellin - Trizek (he/him)
>
> Community Relations Specialist
> Wikimedia Foundation <https://wikimediafoundation.org/>
>
> _______________________________________________
> Wikitech-ambassadors mailing list --
> wikitech-ambassadors(a)lists.wikimedia.org
> To unsubscribe send an email to
> wikitech-ambassadors-leave(a)lists.wikimedia.org
>
--
Amir (he/him)
Hello,
The Wikimedia Foundation Research team [0] is committed to serving
Wikimedia volunteer developers so that they can effectively leverage the
expertise of the Wikimedia research community to contribute to Wikimedia
projects.
We refer to a Wikimedia volunteer developer as any person who contributes
to a piece of software in the Wikimedia ecosystem, e.g., MediaWiki
extensions, desktop and mobile apps and services, bots, PAWS notebooks,
user scripts, etc.
If you identify yourself as a Wikimedia volunteer developer, your
participation in this brief survey [1] would be very relevant for our team
to identify existing and suggested research needs and opportunities of the
Wikimedia developer community.
Thank you for your time and consideration.
Kinneret Gordon, Pablo Aragón and Leila Zia
On behalf of the Wikimedia Research team
[0] https://research.wikimedia.org
[1] https://wikimediafoundation.limesurvey.net/developers-research-needs
--
Kinneret Gordon
Lead Research Community Officer
Wikimedia Foundation <https://wikimediafoundation.org/>
Hi,
The GitLab runners in WMCS (both production and the devtools instance) are
experiencing networking issues and are unreachable at the moment. We are
looking into this but will likely not resolve the problem today. The
default for untrusted loads is to use public cloud runners so this should
only impact jobs explicitly set to use WMCS runners. You can follow
https://phabricator.wikimedia.org/T346060 for updates, I will also update
this thread when the runners are available.
--
Lukasz Sobanski
SRE
Hi everybody!
A couple of weeks ago we started switching the backend used by the ORES
extension which is used by the Recent Changes filters.
After fixing the issue that was caused in some wikis (
https://phabricator.wikimedia.org/T343308) the Machine Learning team
started rolling out the change again.
We have already deployed the changes to *fiwiki* and *itwiki* and will
continue with the rest of the wikis starting from next week.
This change is using Lift Wing (
https://wikitech.wikimedia.org/wiki/Machine_Learning/LiftWing) to get
revision scores instead of ORES, and is a necessary step in the process of
deprecating ORES (for more info please refer to the "ORES to Lift Wing
Migration
<https://lists.wikimedia.org/hyperkitty/list/wikitech-l@lists.wikimedia.org/…>"
email).
The purpose of this change is to use *exactly* the same models which are
also deployed on Lift Wing so there shouldn't be anything different for our
users.
If however you see anything out of the ordinary, feel free to contact
the Machine Learning team:
IRC libera: #wikimedia-ml
Phabricator: Machine-Learning-team tag
Thank you!
Ilias (on behalf of the Machine Learning team)
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, September 6, 2023
Time: 15:00-16:00 UTC / 08:00 PT / 11:00 EDT / 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/>