Closed
Bug 1216533
Opened 9 years ago
Closed 8 years ago
Rename "full review" for listed add-ons to "Promoted and/or bundled"
Categories
(addons.mozilla.org Graveyard :: Developer Pages, defect)
addons.mozilla.org Graveyard
Developer Pages
Tracking
(Not tracked)
RESOLVED
INVALID
People
(Reporter: magopian, Unassigned)
References
(Blocks 1 open bug)
Details
For bug 1203953 we want to rename "full review" to "promoted and/or bundled".
Comment 1•9 years ago
|
||
Did we agree on this term? I have strong feelings about it.
Flags: needinfo?(adora)
Comment 2•9 years ago
|
||
Hi Andreas,
What are some of your concerns about calling it “Review for Promoted Mozilla-Hosted Add-ons” and “Review for Bundled Add-ons”, depending on the situation? We still imply that it is a full review in a sense that we will alert developers that it will take approximately 10 days.
Comment 3•9 years ago
|
||
I am fine with "bundled" for unlisted add-ons.
"Promoted" on the other hand sounds too similar to "featured" which we use on some add-ons, like https://addons.mozilla.org/en-US/firefox/addon/adblock-plus/
Comment 4•9 years ago
|
||
Let’s rename that review to “Review for Featured Mozilla-Hosted Add-ons” or “Review for Featured AMO Add-ons”. We do this to contrast it with “Review for Experimental AMO Add-ons”.
The name is a bit long, but it’s designed so that developers don’t feel like they’re missing out on stuff if they don’t ask for a full review.
Comment 5•9 years ago
|
||
Bram, "featured" is independent from the review process, it is just a flag for already fully reviewed listed add-ons that shows a badge on the add-on page, as you can see on the adblock-plus link above.
Comment 6•9 years ago
|
||
Right. So there are two problems that causes this terminology confusion:
* An add-on can have a yellow button, or a green button
* Any add-on that has a green button is eligible to have a green flag
The solution that I would propose is to call the “green button” option a baseline. By making it a baseline, we can avoid calling it “promoted”. By not calling it “promoted”, developers won’t confuse it with “featured”.
So instead of calling it:
* Review for Promoted Mozilla-Hosted Add-ons
* Review for Unpromoted/Experimental Mozilla-Hosted Add-ons
We call it:
* Review for Mozilla-Hosted Add-ons
* Review for Mozilla-Hosted Add-ons – Unpromoted
The logic diagram also happens to solve our “sideload” naming problem, and you can see it here:
http://f.cl.ly/items/0r1k1a252j1p0b1q1k2O/Add-on%20submission%20wireframes%20-%20Distribution%20explanation.png
Thoughts?
Flags: needinfo?(awagner)
Comment 7•9 years ago
|
||
I briefly talked to Lisa about this and we agreed that we should have another meeting to discuss and explain the details.
Setting Lisa on needinfo to remind her.
Flags: needinfo?(awagner)
Assignee | ||
Updated•9 years ago
|
Product: addons.mozilla.org → addons.mozilla.org Graveyard
Comment 8•8 years ago
|
||
Since we no longer make the distinction between sideloaded and non-sideloaded, this has become obsolete.
Status: NEW → RESOLVED
Closed: 8 years ago
Flags: needinfo?(adora)
Resolution: --- → INVALID
You need to log in
before you can comment on or make changes to this bug.
Description
•