Page MenuHomePhabricator

Deploy pilot of Jade to a small set of wikis.
Closed, DeclinedPublic

Description

The Machine-Learning-Team is planning to deploy Jade -- a human judgment tracking system useful for keeping tabs on ORES, helping patrollers coordinate with each other, and generating new data for training ORES. We'd like to start by piloting the system in a small set of interested wiki communities.

Good candidate wikis for deployment are communities who are using ORES for patrolling work. Patrollers in these wikis are interested in giving feedback to ORES predictions.

We'll deploy the MVP to a trial set of wikis.

  • Identify collaborators on 2-4 small wikis to help us communicate about the roll-out of Jade
  • Load the extension on the wikis
  • Work with local patrolling tool developers to add integration to Jade
  • Review results and iterate.

The MVP includes:

  1. A full featured API for creating and modifying Jade entities (useful for tool integration)
  2. An entity page UI for creating and modifying Jade entities directly from MW
  3. Integration with Special:RecentChanges and Special:Watchlist
  4. The ability to search Jade entity pages

For more information about Jade, see https://mediawiki.org/wiki/JADE. To explore what a "Jade entity" looks like, see TODO.

Related Objects

StatusSubtypeAssignedTask
DeclinedNone
DeclinedNone
Declinedcalbon
InvalidNone
InvalidNone
Resolvedawight
Resolvedawight
Resolvedawight
Resolvedawight
ResolvedHalfak
ResolvedNone
InvalidNone
ResolvedHalfak
Resolvedawight
ResolvedHarej
DuplicateNone
DeclinedNone
Resolvedawight
Resolvedawight
DeclinedNone
ResolvedReedy
ResolvedLadsgroup
ResolvedLadsgroup
Resolved mmodell
ResolvedNone
ResolvedNone
Resolvedhashar
ResolvedNone
Resolvedawight
DeclinedNone
DuplicateNone
DeclinedNone
DeclinedNone
DeclinedNone
DuplicateNone
DuplicateNone
DuplicateHarej
InvalidNone
DuplicateHalfak
DuplicateNone
InvalidNone
InvalidNone
Resolved ACraze
Resolved ACraze
Resolved ACraze
Resolved ACraze
DeclinedNone
Duplicate ACraze
ResolvedHalfak
ResolvedHalfak
Resolved ACraze
Resolved ACraze
ResolvedNone
ResolvedHalfak
Resolved ACraze
Resolved ACraze
Resolvedkevinbazira
Resolved ACraze
Resolved ACraze
Resolved ACraze
ResolvedNone
ResolvedHalfak
DuplicateHalfak
Resolvedkevinbazira
Resolved ACraze
Resolved ACraze
Resolved ACraze
ResolvedHalfak
Resolved ACraze
Resolved ACraze
Resolvedkevinbazira
ResolvedHalfak
Resolved ACraze
Resolved ACraze
DeclinedNone
Resolvedkevinbazira
ResolvedHalfak
DuplicateHalfak
Resolvedkevinbazira
Resolvedkevinbazira

Event Timeline

There are a very large number of changes, so older changes are hidden. Show Older Changes

@daniel We're sort of in limbo now, implicitly blocking on potential TechCom discussion. Please let us know if there's a set date to discuss, to help us plan.

@awight In our last session, TechCom decided that we should keep an eye on this, but there is no action required at this point.

JADE si self-contained enough that the only aspect of it that lies within TechCom's responsibility seems to be scalability. If people start to create JADE pages for every new revision (semi-)automatically, we have a serious problem. But at the moment, it seems like supervision by the local communities should be enough to prevent this.


So far the official TechCom position.

Personally, I'd prefer for JADE to get its own separate wiki. Or access to the JADE namespace could at least be severely restricted.
Besides performance, I'm also worried about this being abused to smuggle bad things past edit filters. But then, if nobody sees it anyway...

@daniel Thanks for the helpful notes. We'll probably come back to TechCom for more discussion in a few months, once we see how integrations behave in practice.

Personally, I'd prefer for JADE to get its own separate wiki. Or access to the JADE namespace could at least be severely restricted.

This is an interesting idea, which we've discussed a bit. So far, we think that JADE is something like a structured talk page, and should be governed by the same permissions and communities as create the content on each wiki. For example, an admin on commons who is banned on enwiki should be able to participate in JADE curation on commons, but be excluded from discussion in enwiki JADE. As for restricting permissions, we can always take this step if it proves necessary.

I would like this to wait for a review by the DBA and Traffic teams.

Specifically: how badly would we be affected by a growth of the page table that a massive adoption of this would cause? Should we make all JADE pages uncacheable so that we don't pollute the cache?

I would at least think we should exclude bots from editing/creating such pages.

@jcrespo @BBlack any thoughts?

(Please note that the SRE summit is underway this week, so you will likely need to wait next week for an answer/advice)

See also T196547 where the discussion should probably continue

awight added a subscriber: Harej.
Harej changed the task status from Open to Stalled.Jul 23 2018, 5:02 PM
Harej changed the status of subtask T199520: Determine which wikis will get Jade and when from Open to Stalled.
awight renamed this task from Deploy JADE extension to production to [Blocked] Deploy JADE extension to production.Aug 6 2018, 4:48 PM
awight renamed this task from [Blocked] Deploy JADE extension to production to Deploy JADE extension to production.Aug 28 2018, 10:47 PM
awight changed the task status from Stalled to Open.
awight removed a project: Patch-For-Review.

Unblocking as I have steps to take, then we'll resubmit for another round of technical and community review.

awight moved this task from Inbox to Product on the Jade board.
Harej triaged this task as Medium priority.Nov 14 2018, 11:12 PM
Harej renamed this task from Deploy JADE extension to production to Deploy Jade extension to production.Apr 15 2019, 10:20 PM
Harej removed awight as the assignee of this task.
Harej updated the task description. (Show Details)
Harej removed a subscriber: awight.

Change 440124 abandoned by Awight:
[DNM] Enable Extension:JADE in production

https://gerrit.wikimedia.org/r/440124

Halfak renamed this task from Deploy Jade extension to production to Deploy Jade extension MVP to production.Aug 6 2019, 7:50 PM
Halfak updated the task description. (Show Details)
Halfak renamed this task from Deploy Jade extension MVP to production to Deploy pilot of Jade to a small set of wikis..Feb 28 2020, 8:14 PM
Halfak updated the task description. (Show Details)
calbon claimed this task.
calbon moved this task from Non-Epic to Completed on the Machine-Learning-Team (Active Tasks) board.

@calbon jade doesn't appear to be enabled in production on any wiki. Per InitialiseSettings

'wmgUseJADE' => [
	'default' => false,
],
Ladsgroup changed the task status from Resolved to Declined.Apr 28 2021, 9:49 PM
Ladsgroup added a subscriber: Ladsgroup.

It's not deployed to production and it's going to be undeployed from beta too T281418: Undeploy JADE extension from beta cluster