It's possible that I'm very out of touch, but I'll ask anyway :)
As far as I know, the main place where editors of Wikimedia's wiki sites
actually see ORES in action is the filtering and highlighting functionality
on Recent Changes. This functionality is enabled in a limited number of
wikis, but at least in some of those wikis, it works pretty well; I've just
done a quick and informal poll on the Hebrew Wikipedia village pump, and
the responses till now were that this is a good feature that helps with
patrolling.
The email says that "All ML models currently accessible on ORES are also
currently accessible on Lift Wing", and if I understand correctly, this
means that this feature in Recent Changes will keep working. Do I
understand correctly? :)
In addition, I have some followup questions:
1. The MediaWiki extension that implements the frontend in Recent Changes
is itself named "ORES". It's an internal name that isn't seen much by
wiki
editors except if they go to Special:Version or to translatewiki.
Nevertheless, as the time goes by, seeing the old name may start getting
weird. So what's the plan about it? Will this extension remain as is? Will
it be renamed? Will it be replaced with a new frontend extension in the
foreseeable future?
2. Back when ORES was originally developed and deployed around 2017,
several wiki editors' communities participated in the development by
adapting the product to the needs of their wikis and languages by
translating the ORES extension's user interface and, more importantly, by
labelling a sample of several thousands of diffs from their wiki using the
Wikilabels tool. The communities that did that whole process were, more or
less, the communities to which this Recent Changes enhancement was
deployed. Will anything like that have to be done again along with the move
away from ORES?
3. Will this change open up the possibility of deploying this Recent
Changes enhancement, or a newer version thereof, to more wikis and
languages?
If you think that my questions show a wrong understanding of something,
please let me know—as I said in the beginning, its quite possible :)
Thanks!
בתאריך יום ה׳, 3 באוג׳ 2023, 17:16, מאת Chris Albon <calbon(a)wikimedia.org>rg>:
Hi everybody,
TL;DR We would like users of ORES models to migrate to our new open source
ML infrastructure, Lift Wing, within the next five months. We are available
to help you do that, from advice to making code commits. It is important to
note: All ML models currently accessible on ORES are also currently
accessible on Lift Wing.
As part of the Machine Learning Modernization Project (
https://www.mediawiki.org/wiki/Machine_Learning/Modernization), the
Machine Learning team has deployed a Wikimedia’s new machine learning
inference infrastructure, called Lift Wing (
https://wikitech.wikimedia.org/wiki/Machine_Learning/LiftWing). Lift Wing
brings a lot of new features such as support for GPU-based models, open
source LLM hosting, auto-scaling, stability, and ability to host a larger
number of models.
With the creation of Lift Wing, the team is turning its attention to
deprecating the current machine learning infrastructure, ORES. ORES served
us really well over the years, it was a successful project but it came
before radical changes in technology like Docker, Kubernetes and more
recently MLOps. The servers that run ORES are at the end of their planned
lifespan and so to save cost we are going to shut them down in early 2024.
We have outlined a deprecation path on Wikitech (
https://wikitech.wikimedia.org/wiki/ORES), please read the page if you
are a maintainer of a tool or code that uses the ORES endpoint
https://ores.wikimedia.org/). If you have any doubt or if you need
assistance in migrating to Lift Wing, feel free to contact the ML team via:
- Email: ml(a)wikimedia.org
- Phabricator: #Machine-Learning-Team tag
- IRC (Libera): #wikimedia-ml
The Machine Learning team is available to help projects migrate, from
offering advice to making code commits. We want to make this as easy as
possible for folks.
High Level timeline:
**By September 30th 2023: *Infrastructure powering the ORES API endpoint
will be migrated from ORES to Lift Wing. For users, the API endpoint will
remain the same, and most users won’t notice any change. Rather just the
backend services powering the endpoint will change.
Details: We'd like to add a DNS CNAME that points
ores.wikimedia.org to
ores-legacy.wikimedia.org, a new endpoint that offers a almost complete
replacement of the ORES API calling Lift Wing behind the scenes. In an
ideal world we'd migrate all tools to Lift Wing before decommissioning the
infrastructure behind
ores.wikimedia.org, but it turned out to be really
challenging so to avoid disrupting users we chose to implement a transition
layer/API.
To summarize, if you don't have time to migrate before September to Lift
Wing, your code/tool should work just fine on
ores-legacy.wikimedia.org
and you'll not have to change a line in your code thanks to the DNS CNAME.
The ores-legacy endpoint is not a 100% replacement for ores, we removed
some very old and not used features, so we highly recommend at least test
the new endpoint for your use case to avoid surprises when we'll make the
switch. In case you find anything weird, please report it to us using the
aforementioned channels.
**September to January: *We will be reaching out to every user of ORES we
can identify and working with them to make the migration process as easy as
possible.
**By January 2024: *If all goes well, we would like zero traffic on the
ORES API endpoint so we can turn off the ores-legacy API.
If you want more information about Lift Wing, please check
https://wikitech.wikimedia.org/wiki/Machine_Learning/LiftWing
Thanks in advance for the patience and the help!
Regards,
The Machine Learning Team
_______________________________________________
Wikitech-l mailing list -- wikitech-l(a)lists.wikimedia.org
To unsubscribe send an email to wikitech-l-leave(a)lists.wikimedia.org
https://lists.wikimedia.org/postorius/lists/wikitech-l.lists.wikimedia.org/