Hi Chris & ML team, Good to see LiftWing is finally becoming a reality. There are a few things in the documentation that I would like to clarify.
1. In [1], the bot owner is encouraged to move to the revertrisk score. However, in [2], it's explicitly mentioned that the model should not be used for "Auto-removing edits that a user makes without another editor in the loop". So, should bot owners currently reverting based on goodfaith and damaging scores explore the new models? If so, do you have any suggestions on how to automatically match thresholds between the old and new models? 2. I could not find any reference regarding the ores scores exposed through other APIs (specifically the RC API [3]). Will those be available going forward? Under which names? 3. Will it still be possible to (re-)train existing and new model for a specific wiki? How and when? Thanks, Strainu [1] https://wikitech.wikimedia.org/wiki/ORES#Example:_migrating_a_Bot_from_ORES_to_Lift_Wing [2] https://meta.wikimedia.org/wiki/Machine_learning_models/Proposed/Language-agnostic_revert_risk#Users_and_uses [3] https://ro.wikipedia.org/w/api.php?action=query&format=json&list=recentchanges&rcnamespace=0%7C4%7C6%7C8%7C10&; *rcprop=*title%7Ctimestamp%7Cids%7C*oresscores* %7Ctags%7Cpatrolled&rcshow=unpatrolled&rclimit=50&rctype=edit%7Cnew%7Ccategorize În joi, 3 aug. 2023 la 17:16, Chris Albon <cal...@wikimedia.org> a scris: > 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: m...@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@lists.wikimedia.org > To unsubscribe send an email to wikitech-l-le...@lists.wikimedia.org > https://lists.wikimedia.org/postorius/lists/wikitech-l.lists.wikimedia.org/
_______________________________________________ Wikitech-l mailing list -- wikitech-l@lists.wikimedia.org To unsubscribe send an email to wikitech-l-le...@lists.wikimedia.org https://lists.wikimedia.org/postorius/lists/wikitech-l.lists.wikimedia.org/
