936800 - Reviewing tools suggestions.

Status: RESOLVED WONTFIX

(Marketplace Graveyard :: Reviewer Tools, defect)

Description

[Adrian Crespo]

User Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Ubuntu Chromium/28.0.1500.71 Chrome/28.0.1500.71 Safari/537.36

Steps to reproduce:

I can review privileged apps and I find difficult to follow their updates.

I suggest the following improvements:
A quick button to filter the privileged apps in the queue list.
A quick button to follow our previous reviews or any way to check if there is any update (just a warning message or something like that).
Adding a new tag in the subject for emails related to privileged apps. Something like "[PRIV] Submission update: {appname}".
Adding a regex tool when inspecting the content of an app, similar to the diff tool.

Improve the incentive points or the privileged revie. It takes more effort to review their code, so I suggest to raise the incentive points for volunteers.



Expected results:

Don't hesitate to contact me for further information or if there is any question.

Comment 1

[Adrian Crespo]

And auto prettify all the content. It's hard to review minified codes using the reviewer tools.

Comment 2

[Matt Basta [:basta]]

Please file a bug for each of the features you requested. It'd be easier to implement if each is tracked on its own.

Comment 3

[Adrian Crespo]

Okay, thanks!

Comment 4

[Andrew Williamson [:eviljeff]]

> A quick button to follow our previous reviews or any way to check if there
> is any update (just a warning message or something like that).
> Adding a new tag in the subject for emails related to privileged apps.
> Something like "[PRIV] Submission update: {appname}".

fwiw, the comms dashboard should cover these problems when its live  - bug 855776 - by sending you notifications on replies to your reviews only.

> Adding a regex tool when inspecting the content of an app, similar to the
> diff tool.

And hopefully the reviewer tool enhancements that :cr has proposed would cover the same use case - i.e. highlighting privileged API usage.

Comment 5

[Rob Hudson [:robhudson]]

Based on comment #4 it's unclear to me what needs to be done here. Can we file separate bugs for those that are missing?

Comment 6

[Andrew Williamson [:eviljeff]]

to quote Rob in comment #5:

> Based on comment #4 it's unclear to me what needs to be done here. Can we
> file separate bugs for those that are missing?

Comment 7

[Andrew Williamson [:eviljeff]]

I'm closing this bug.  Separate bugs should be filed for missing features.