thank you. confirm kill then, @JArguello-WMF

i believe so. we can check with ML team if not. @KMontalva-WMF ... on the list for the next rearchitecture chat then, too. @JArguello-WMF - migrate :)

great :) let's keep this ticket for now and we can discuss if it might fit in our next architecture update - @JArguello-WMF - migrate :)

yea you're right @E.Enabulele - @JArguello-WMF - please kilL!

Decision - given the better results, we're going to move forward with productionizing at the current standard. We expect our reusers want higher speed to depend on, but we will, as they say, "cross that bridge when we get there".

@JArguello-WMF - kill?

@JArguello-WMF - kill

@JArguello-WMF - kill

@Htriedman is this still relevant?

@JArguello-WMF - kill

@JArguello-WMF - kill

@JArguello-WMF - kill, this is a duplicate

@JArguello-WMF - migrate

@JArguello-WMF - kill

@JArguello-WMF - kill

@JArguello-WMF - kill, this is done

@JArguello-WMF - migrate

@JArguello-WMF - kill

@JArguello-WMF - kill. this is done

@JArguello-WMF - kill

@JArguello-WMF - migrate

@JArguello-WMF - migrate

@JArguello-WMF - kill

@JArguello-WMF - migrate

@JArguello-WMF - kill

@JArguello-WMF - migrate

@JArguello-WMF - migrate

@JArguello-WMF - no need to migrate this stays here but no delete

@Htriedman relevant to @HCoplin-WMF correct?

@KMontalva-WMF - something we can discuss for rearch scope?

@JArguello-WMF - kill

@JArguello-WMF - migrate

@JArguello-WMF - migrate

@JArguello-WMF - no need to migrate but no need to kill eitehr

@Sucheta-Salgaonkar-WMF - this may be more useful for your team than mine (to discuss around modeling)

@Sucheta-Salgaonkar-WMF - before your time we wanted to look into this but just stopped - perhaps we should discuss?

What
Research has a built and tested a model for judging an article's quality, which is now in production via Liftwing.

@SGupta-WMF - keep correct? (cc @JArguello-WMF)

@JArguello-WMF - keep

@@JArguello-WMF - keep

@KMontalva-WMF - too crazy of a concept to consider for upcoming re-arch? overscope? slack me?!

@LDlulisa-WMF - we should kill this ticket, it's duplicate because of your current investigation correct? (cc @JArguello-WMF )

@KMontalva-WMF - given lakehouse this would not be an issue so we can kill this ticket correct? (cc @JArguello-WMF)

@@JArguello-WMF - keep

@@JArguello-WMF - keep

@JArguello-WMF - kill

@E.Enabulele this one is done as part of another ticket so we can close right?

noting that I added a point to in-scope that we agreed on was necessary.

no need to publish on a certain date, only when possible. feel free to bother me whenever for review.

this is now documented in an internal google doc, including a decision to NOT make any engineering changes but changes and explanation in our documentation. new ticket for @JWuyts-WMF ?

@KMontalva-WMF could you add the license as per @Robertsky

@Robertsky here is the github - https://github.com/wikimedia-enterprise/breaking-news-poc

we're going to deploy the open source version of this very soon, which will mean we need to deprecate hosting it on our side around March 1. Do you think that's enough time for anyone using it to deploy their own version? Open sourcing will, of course, give folks the space to adjust it as it useful to them and they can host it on toolforge.

@kevinbazira thank you.

so sorry! yes sub-milisecond is incorrect. Half a second, 500ms. The P90s is NOT a typo.

https://meta.wikimedia.org/wiki/Which_projects_are_active%3F

Results from @SGupta-WMF 's test --