Page MenuHomePhabricator

Extend the GUI for ORES
Open, LowPublic

Description

What we want to get out of this extended reference UI:

  • Demonstrate what information we're making available.
  • Educational tool to explain what all the numbers mean.
  • Example implementation to serve as a starting point for other projects.
  • Debugging aid for us and others.

Potential views:

  • Scores from all models for a given revision.
  • Evolution of article quality over time.
  • Model metadata.
  • List of models.

Implementation

Provide additional routes which emit an HTML template plus revscoring data object, and populate the template using JavaScript. Reusability would be a big plus, whatever we do should be easy to adapt using new templates or architectures.

Event Timeline

awight created this task.Aug 2 2015, 10:57 PM
awight updated the task description. (Show Details)
awight raised the priority of this task from to Needs Triage.
awight added a subscriber: awight.
Restricted Application added a subscriber: Aklapper. · View Herald TranscriptAug 2 2015, 10:57 PM
awight updated the task description. (Show Details)Dec 4 2015, 4:04 AM
awight set Security to None.
Restricted Application added a subscriber: StudiesWorld. · View Herald TranscriptDec 4 2015, 4:04 AM
awight renamed this task from Provide a reference GUI for ORES to Write a reference GUI for ORES.Dec 4 2015, 4:06 AM
awight updated the task description. (Show Details)Dec 4 2015, 4:13 AM
He7d3r awarded a token.Dec 4 2015, 7:04 AM
Halfak added a subscriber: Halfak.Dec 4 2015, 8:26 PM

Yes. Been thinking about this for a while. It seems like we could do something very simply. This is also why ORES does scores beneath the "/scores/" endpoint so that we can have "/gui/" or whatever to host something like this.

Halfak added a comment.EditedDec 4 2015, 8:26 PM

See also T119271

Halfak assigned this task to Ladsgroup.Mar 12 2016, 3:57 PM
Halfak added a project: ORES.

I would be curious to poke at this feature if it was implemented, but I'm not sure what Open+Done means...

See http://ores.wmflabs.org/ui/

I marked this *done*, but it seems that there is more to the write-up than we have implemented now, so I'm going to great a new task for the minimal implementation that we have and rename this to be about extending the current UI.

Halfak renamed this task from Write a reference GUI for ORES to Extend the GUI for ORES.Mar 14 2016, 3:30 PM
Halfak updated the task description. (Show Details)
Halfak moved this task from Done to Active on the Scoring-platform-team (Current) board.
Halfak removed Ladsgroup as the assignee of this task.
Halfak added a subscriber: Ladsgroup.

Looks like we already had one in the (Done) column. See T123933

Halfak triaged this task as Low priority.Aug 4 2016, 2:15 PM
Restricted Application added a subscriber: TerraCodes. · View Herald TranscriptNov 1 2017, 5:23 PM

@awight: good first bug tasks are self-contained, non-controversial issues with a clear approach and should be well-described with pointers to help the new contributor. Given the current task description with its huge unclear scope only listing "potential views" I am removing the good first bug tag. Please re-add the tag once the task description has been polished and provides sufficient information for a new contributor. Thanks!

awight added a comment.Jan 9 2018, 2:38 PM

@Aklapper Thank you for combing through the tasks and cleaning. However, we spent some time finding tasks that would be appropriate for new contributors, and I'd rather not lose that work. Can you suggest something like a "Easy-TODO" tag that we can use to mark tasks which would be good first bug if we put the effort into adding documentation and so on?

@awight: Maybe patch-welcome as that has a more vague definition?

awight added a comment.Jan 9 2018, 2:45 PM

@Aklapper Great, we appreciate the suggestion.

awight removed a subscriber: awight.Mar 21 2019, 3:59 PM