Thu, Oct 1
I've got everything noted in an etherpad for now: https://etherpad.wikimedia.org/p/labels
@calbon I took a pass through and made a couple of suggestions. Overall, I think this looks great!
Wed, Sep 30
Fri, Sep 25
@Aklapper we already have solid unit and integration tests in place for Wikilabels. This ticket is proposing adding an additional testing framework (which has a large number of dependencies) for UI testing only, which I just don't see the value in right now. Additionally, we have plans to deprecate Wikilabels in the near future over concerns with the UI. Both of these reasons are why which is why this ticket was declined.
Thu, Sep 24
Invalid now due to major changes in the codebase.
Marking this as resolved. Draft Quality/Draft Topic/Article Topic are all included now on https://www.mediawiki.org/wiki/ORES
Marking this as resolved as we understand the limitations that celery brings with the current design of ORES and it will not be included during the next iteration.
Going to mark this as resolved since we have good idea of what is needed to migrate and will not be moving ORES in it's current form to k8s.
Adding some notes:
ORES CI-tests on Travis were introduced in https://github.com/wikimedia/ores/pull/253
This issue is no longer valid after moving to Prometheus
Wed, Sep 23
This is certainly do-able by hooking in to our custom EntityDiffBuilder class. We would just need to develop an algorithm and corresponding JS components.
Declining as Jade has changed quite a bit since this ticket was written and there is not a ton of value in implementing this for now.
@kevinbazira did the "badwords" and "informals" lists ever get merged?
Marking this as invalid as the codebase has changed considerably over the past year.
We have project-level documentation here: https://www.mediawiki.org/wiki/ORES
Declining this as we've discovered ORES will not fit on k8s in it's current design