851082 - Create dashboards for users interested in providing reviews

Status: RESOLVED WONTFIX

(developer.mozilla.org Graveyard :: General, defect)

Description

[Eric Shepherd [:sheppy]]

What problems would this solve?
===============================
Some reviewers will want to see their queue of review requests using an RSS feed (in fact, this appears to be the most popular option, judging from conversations I've had with developers). We should offer this.

Who would use this?
===================
Reviewers that prefer RSS feeds for notification of articles they should review.

What would users see?
=====================
A feature in their profile to subscribe to RSS feeds for the types of reviews they agree to assist with.

What would users do? What would happen as a result?
===================================================
Subscribe to the feed(s). Each entry would include information on the article that's changed with a link to it, the size of the change (so they can judge how much time they need to devote to the review), etc.

Is there anything else we should know?
======================================

Comment 1

[Eric Shepherd [:sheppy]]

Note that each user would need to be able to sign up for a customized technical review feed that includes all the technologies they agree to review for; for example, if a user has specified that they can review JavaScript, HTML, and CSS documentation, they should get an RSS feed of articles tagged with one or more of those tags which are also flagged for tech review, but should not see any other articles that are flagged for review.

They shouldn't need to subscribe to separate feeds for each technology they can review (or does anyone see a reason someone might want to have to do that?).

Comment 2

[ali spivak]

Do we have metrics on how many people are using the RSS feed? I'd like to get concrete numbers before we put more effort into this...

Comment 3

[Eric Shepherd [:sheppy]]

(In reply to ali spivak from comment #2)
> Do we have metrics on how many people are using the RSS feed? I'd like to
> get concrete numbers before we put more effort into this...

The problem is these feeds are so lousy right now that this metric would not be useful.

Comment 4

[Luke Crouch [:groovecoder]]

Ali, which RSS feed? Per Sheppy, there's no rss feed for reviewers *yet*.

Comment 5

[Eric Shepherd [:sheppy]]

Yeah, this feed doesn't exist at all yet. Developers, who are a primary target audience for review notification requests, have very specifically requested the ability to subscribe to RSS feeds.

Comment 6

[Luke Crouch [:groovecoder]]

To clarify, this would be like a person's needinfo? list in bugzilla? I.e., the list of action items that the person needs to do?

Comment 7

[Eric Shepherd [:sheppy]]

(In reply to Luke Crouch [:groovecoder] from comment #6)
> To clarify, this would be like a person's needinfo? list in bugzilla? I.e.,
> the list of action items that the person needs to do?

More or less. This would be a feed of items flagged for review that match the criteria specified in their profile (that is, editorial vs technical reviews, or both, as well as topic areas). That would let them be able to use an RSS reader to watch for new articles that match their criteria for articles they should review.

This would be fantastic, for both developers that want to be engaged with us and for us. Consider this scenario:

1. We write a new article about WebGL, setting the "technical review requested" flag on it.
2. Someone whose profile says they're willing to tech review WebGL content sees a new item in their review notification RSS feed.
3. The feed entry includes information about what's changed (ideally some kind of easy to read "before and after" presentation). They review.
4. The entry includes a few links:

 -- "Approve this change" (Link goes to a page to confirm removing the tech review request from the page)
 -- "Edit this article" (Opens the page in an editor)
 -- "Reply to the writer" (Sends email to the contributor that wrote the change; used to comment on the change and make suggestions, etc -- this would eventually be replaced with a link to use our in-site messaging system once that's available)
 -- "Read on MDN" (Opens the page in the browser)
 -- "Email an MDN admin" (Opens an email to the MDN admin team -- useful if the update is spam or if help is needed)

5. The reviewer clicks whatever they need to click, either reviewing and accepting, editing to fix, or letting the writer know something's wrong.

This will help draw more developers into the process by making it easier for them to pull reviews into their daily workflow.

Comment 8

[Luke Crouch [:groovecoder]]

Great details, :sheppy! Will make it easier to start this bug when we select it.

Comment 9

[Eric Shepherd [:sheppy]]

There should also be a "Page History" link, in case the change is one that needs to be reverted.

Comment 10

[ali spivak]

would it make sense to put the feed in the profile???

Comment 11

[Eric Shepherd [:sheppy]]

(In reply to ali spivak from comment #10)
> would it make sense to put the feed in the profile???

You mean the link to the feed? Probably, yes. "Feed of your review suggestions" sort of link/button.

Comment 12

[Luke Crouch [:groovecoder]]

In Paris we pointed out that a "profile" and a "personal dashboard" should be separate pages. The profile page should showcase a user to others. And the personal dashboard should guide a user towards activities they should do.

So, "Items to review" seems more like a feature for the personal dashboard page.

Comment 13

[Eric Shepherd [:sheppy]]

(In reply to Luke Crouch [:groovecoder] from comment #12)
> In Paris we pointed out that a "profile" and a "personal dashboard" should
> be separate pages. The profile page should showcase a user to others. And
> the personal dashboard should guide a user towards activities they should do.
> 
> So, "Items to review" seems more like a feature for the personal dashboard
> page.

Fair enough. Yes, we do need to set up a project for the personal dashboard and see what we can make happen there.

Comment 14

[Eric Shepherd [:sheppy]]

(In reply to Eric Shepherd [:sheppy] from comment #13)
> (In reply to Luke Crouch [:groovecoder] from comment #12)
> > In Paris we pointed out that a "profile" and a "personal dashboard" should
> > be separate pages. The profile page should showcase a user to others. And
> > the personal dashboard should guide a user towards activities they should do.
> > 
> > So, "Items to review" seems more like a feature for the personal dashboard
> > page.
> 
> Fair enough. Yes, we do need to set up a project for the personal dashboard
> and see what we can make happen there.

I have created an initial page proposing the personal dashboard project: https://wiki.mozilla.org/MDN/Development/Personal_dashboard

Comment 15

[John Whitlock [:jwhitlock]]

We currently have pages showing all the pages for a locale that request review:

https://developer.mozilla.org/en-US/docs/needs-review/
https://developer.mozilla.org/en-US/docs/needs-review/technical
https://developer.mozilla.org/en-US/docs/needs-review/editorial

There are feeds for RSS, Atom, and JSON that provide the same data. They've been around since 2011. It is possible that we don't advertise them for performance reasons. The links in these feeds are tracked in Google Analytics using the campaign 'feed', and get about 500 clicks per month. They are used, but barely.

https://developer.mozilla.org/en-US/docs/feeds/json/needs-review
https://developer.mozilla.org/en-US/docs/feeds/atom/needs-review/technical
https://developer.mozilla.org/en-US/docs/feeds/rss/needs-review/editorial

We've added a feature to watch pages, and to watch a tree of pages.

The personal dashboard project as described is huge, and I'm not sure it belongs in the Kuma codebase. It may be better for Kuma to provide the data and interfaces as APIs, and let the community build the dashboard tools. I'm not sure there are enough people interested in review to justify the project.

I'm tempted to close WONTFIX, but I'm limiting to changing the bug title to more accurately reflect how the discussion evolved.

Comment 16

[BMO Automation]

MDN Web Docs' bug reporting has now moved to GitHub. From now on, please file content bugs at https://github.com/mdn/sprints/issues/ and platform bugs at https://github.com/mdn/kuma/issues/.