Page MenuHomePhabricator

Deploy Jade extension to production
Open, NormalPublic

Description

Check that basic functionality is working on the beta cluster and that our extension isn't causing any problems:

  • Jade namespaces appear in RecentChanges
  • Jade edits can be suppressed

Initial extension review and testing:

  • Complete extension review, T188307
  • Beta cluster deployment
  • Extension:Jade code in production extensions dir.
  • Further technical and DBA review of T200297

We'll deploy in phases, with increasing commitment and reach:

  • Load the extension on 1-3 medium-sized wikis.
  • Integrate an existing patrolling or review workflow.
  • Review results and iterate to more wikis and workflows.

Related Objects

StatusAssignedTask
OpenNone
OpenNone
InvalidNone
InvalidNone
Resolvedawight
Resolvedawight
Resolvedawight
Resolvedawight
OpenNone
ResolvedNone
InvalidNone
OpenNone
Resolvedawight
ResolvedHarej
OpenNone
OpenNone
Resolvedawight
OpenHarej
Resolvedawight
Resolvedawight
OpenNone
OpenNone
OpenNone
OpenHarej
ResolvedReedy
ResolvedLadsgroup
ResolvedLadsgroup
Resolvedmmodell
ResolvedNone
ResolvedNone
Resolvedhashar
ResolvedNone
Resolvedawight
OpenNone
OpenNone
OpenNone
OpenNone
OpenNone
OpenNone
OpenNone
DuplicateHarej
InvalidNone
OpenHarej
OpenNone
ResolvedNone
OpenNone
OpenNone
OpenNone
OpenNone
OpenNone
OpenNone
OpenNone
OpenNone

Event Timeline

There are a very large number of changes, so older changes are hidden. Show Older Changes
Restricted Application added a subscriber: Aklapper. · View Herald TranscriptDec 20 2017, 3:57 PM
awight renamed this task from Deploy JADE MVP to production to Deploy JADE extension to production.Apr 3 2018, 9:05 PM
awight removed a project: Epic.
awight updated the task description. (Show Details)
awight updated the task description. (Show Details)Apr 4 2018, 5:58 PM
awight updated the task description. (Show Details)Apr 4 2018, 9:58 PM
daniel added a subscriber: daniel.

Tagging for internal techcom discussion. Is the documentation on the implementation of JADE somewhere?

Note to self:

awight added a comment.Jun 6 2018, 4:02 PM

@daniel Thanks for taking a look. The implementation is quite simple at the moment, it's just a namespace "JADE" with validation to enforce a schema and some business logic. See https://phabricator.wikimedia.org/diffusion/EJAD/

The hope is that curation and patrolling tools like Huggle will be integrated so they create a JADE page where all patrolling decisions made on a wiki entity are collected. As you saw, revisions can be assessed as a "Diff" or as a snapshot of the page, "Revision". There's also a path for judgments about a "Page", and only one will be created, e.g. https://en.wikipedia.beta.wmflabs.org/wiki/JADE:Page/188553

My napkin currently shows that an upper bound success case in which all patrolling goes through JADE will result in c. 2.5M new JADE: pages per year. We don't expect success to come quickly, of course. The current plan is to deploy our first iteration now, and consider how to store data in a more scalable form in the longer term, so that's the question we'd like to receive advice about.

Thanks!

awight added a comment.Jun 6 2018, 4:09 PM

@daniel Oops, I didn't realize which task we were in. Here's the discussion about scalability so far: T196547: [Epic] Extension:JADE scalability concerns

Joe added a subscriber: Joe.

Change 440124 had a related patch set uploaded (by Awight; owner: Awight):
[operations/mediawiki-config@master] [DNM] Enable Extension:JADE in production

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

daniel moved this task from Inbox to Watching on the TechCom board.Jun 13 2018, 8:22 PM

@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.

Joe added a subscriber: BBlack.EditedJun 18 2018, 10:43 AM

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)

Joe added a subscriber: jcrespo.Jun 18 2018, 10:44 AM
Joe added a comment.Jun 18 2018, 10:46 AM

See also T196547 where the discussion should probably continue

awight claimed this task.
awight moved this task from Pending deployment to Review on the Scoring-platform-team (Current) board.
awight updated the task description. (Show Details)Jul 3 2018, 10:16 AM
awight added a subscriber: Harej.
Harej moved this task from Inbox to Blocked on the Jade board.Jul 5 2018, 10:02 PM
Harej changed the status of subtask T199520: Determine which wikis will get Jade and when from Open to Stalled.Jul 23 2018, 5:02 PM
Harej changed the task status 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 added a project: Epic.
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 updated the task description. (Show Details)Aug 28 2018, 11:10 PM
awight changed the status of subtask T199520: Determine which wikis will get Jade and when from Stalled to Open.Nov 1 2018, 5:22 PM
awight moved this task from Radar to Inbox on the Jade board.Nov 14 2018, 11:02 PM
awight moved this task from Inbox to Product on the Jade board.
Harej triaged this task as Normal priority.Nov 14 2018, 11:12 PM
SPoore added a subscriber: SPoore.Dec 14 2018, 8:20 PM
Zache added a subscriber: Zache.Jan 15 2019, 1:11 PM
ElanHR added a subscriber: ElanHR.Feb 13 2019, 6:47 PM
Halfak moved this task from Untriaged to Epic on the Scoring-platform-team board.Apr 2 2019, 9:31 PM
Harej renamed this task from Deploy JADE extension to production to Deploy Jade extension to production.Apr 15 2019, 10:20 PM
Harej updated the task description. (Show Details)
Harej removed awight as the assignee of this task.
Harej removed a subscriber: awight.

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

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