Amazing, TYSM Bartosz!! Discussing now with Haley and will get back to you ASAP

Yayyy thank you so much Bartosz!!

Ok based on the discussion in the Slack thread I think we should use "edited in the last 24 hours" as a proxy for editing volatility. I'll update the ticket details at the top to capture this, but please let me know if you disagree with this approach or have any questions - totally happy to try it a different way!

Thank you so much Bartosz!!!

In T418832#11906759, @kostajh wrote:

In T418832#11905970, @Sucheta-Salgaonkar-WMF wrote:

Hi friends! Should this ticket be closed or is there remaining work needed for the CoPE-A-9B model?

The next step is deploying the CoPE-b-12b model, but we are still working on resolving the Coupa BAR for this.

Hi friends! Should this ticket be closed or is there remaining work needed for the CoPE-A-9B model?

Cross-posting some thoughts that @Dbrant shared on Slack:

@OKarakaya-WMF could you please add a weekly summary for me to pull into Asana?

Shell ticket for @SherryYang-WMF to fill out

Shell ticket for @SherryYang-WMF to fill out

@elukey you seriously rock, thank you so much you just unlocked a dashboard that I *really* needed to access today, feels so good to have it :) tysm

@OKarakaya-WMF thanks soo much for the analysis you provided above re: opportunity sizing for case sensitivity! I'm curious if we have anything comparable for named entity recognition. I have two questions:
(1) Re: In enwiki, 5% of the recommendations are not exact matches between the link and the target page, regardless of case sensitivity. - I'm wondering how much of that 5% can be attributed to lack of named entity recognition.
(2) Do we have data to suggest that this might be an even more pervasive problem in non-English wikis, as (I believe) was the case for country and continent names?

@elukey I thought I hadn't set it up, but I guess I must have done so at some point in my onboarding and totally forgot... sorry about that :) Just signed the doc!

Thanks so much @elukey and Chris!! I attempted to sign https://phabricator.wikimedia.org/L3 but am asked for MFA credentials in the form of an App Code. Do you know where I can find this code?

@KStoller-WMF, regarding the timeline, I'd like to confirm whether these results meet the Growth team's requirements. If so, I'll proceed with the necessary changes to the Revise Tone Task Generator in LiftWing, which I expect to complete in the first week of January.

@OKarakaya-WMF is it okay if I turn this into a Goal ticket on our board and move it to the Goals column? You can still use it for all the same updates that you would use it for otherwise, but then it can also be a home for our Friday weekly updates. Otherwise, I can create a separate parent ticket to be the Goal ticket and I'll make this a child ticket under that. Please lmk whatever you prefer! TYSM

@OKarakaya-WMF if you have time on Monday morning your time could you please write an update for me to post in Asana? No worries at all if you don't have time!

--

@gkyziridis Could you please write an update here about the overall status of this work, that I can use in Asana reporting? I have to submit these every Friday. I can write the sections about how many reviews we have per language right now, but would really appreciate your updates on the investigation and the overall ticket

@Samwalton9-WMF could you please keep me in the loop about timing for switching over to the other model? I don't think you need anything from us, but I just want to make sure we're available in case of issues

Besides Teahouse, another useful resource could be the enwiki Reference Desk: https://en.wikipedia.org/wiki/Wikipedia:Reference_desk

@AikoChou Great question, and great thinking! I'll start a thread for this in the WE1.1 channel so we can propose this and get feedback from Kirsten, Lauren, and Peter.

@KStoller-WMF @DMburugu just chiming in to say that the prioritization of T392012 is blocked until we confirm whether this task is a priority under WE1.1. We started to talk about this prioritization decision here and I'm happy to continue the conversation whenever it makes sense!

I've created Annotool instances for most of the additional languages in which we want to evaluate the model. Project numbers, translations, and labels for each of these languages can be found in this doc.

@Trizek-WMF good question! We still ideally want to have 5+ evaluators per language, like we did last time, but we don't want this to be a blocker to moving forward if we have a strong and consistent signal about the model's performance in that language. I believe that the number of samples per evaluator is the same as last time. cc @ppelberg

This is kind of a unique case for us, since most of our hosting requests come from the Research team, so I'm sorry that we don't have a process built around this yet!

Hey @derenrich, sorry for the delayed follow-up. This is on me personally; I'm balancing a few time-sensitive items right now and a bit behind on the things that are non-blocking (as I understand this request to be - please correct me if I've misunderstood).

@Miriam yes totally, sorry for not doing that sooner! I'll do a quick pass of our board to see if there are other places where y'all are unnecessarily tagged

@Miriam hi!! yes this is! I don't think anticipate that we'll need support from Research, other than pinging @diego with occasional questions in the #structured-task-improve-tone channel. Is that okay?

We met on Friday to discuss Ilias' questions above and talk through some potential solutions. See meeting notes and meeting recording for more.