Closed Bug 493311 Opened 16 years ago Closed 15 years ago

Update AMO Policy Page

Categories

(addons.mozilla.org Graveyard :: Public Pages, defect, P2)

x86
macOS
defect

Tracking

(Not tracked)

VERIFIED WONTFIX

People

(Reporter: rbango, Assigned: clouserw)

Details

Attachments

(1 file)

Attached file Policy page updates
Please update the AMO policy page with the canned responses used by the editors to communicate the review status to an author. Current policy page can be found here: https://addons.mozilla.org/en-US/firefox/pages/policy I've attached an HTML file which includes the edits that should be appended.
Target Milestone: --- → 5.0.7
Assignee: nobody → jbalogh
Priority: -- → P3
Target Milestone: 5.0.7 → 5.0.8
Priority: P3 → P2
Target Milestone: 5.0.8 → 5.0.9
Assignee: jbalogh → clouserw
I just put this on my staging copy to commit and started reading it and I don't understand why this is a part of the policy page. You're listing the canned responses from the dev cp? What type of response should I expect once my add-on has been reviewed? "Looks great - thanks for the update." ^^ Really? Why is that on this page at all? If this section is necessary I think a short paragraph about our workflow or even a link to the sandbox diagram would be more helpful than this. Am I alone?
Hm yea, I can understand that people want to know what to expect, but I kind of agree with Wil that it's a little overkill to throw the canned responses in there. I kind of think, either the canned responses we have are clear enough -- or we should fix the canned responses. But without any additional explanation, I think there's little use putting them on the policy page. Just my 2 cents.
Hi Wil. I looked back through my emails so I could understand the context and it was one of the outcomes of the sandbox meeting we had back in May. The email was sent by Nick to AMo-Drivers it listed a bunch of things we wanted to do to improve communication and understanding of the sandbox. One of those action points was: "Update policy page with most common rejection causes (see boilerplate responses in system and include these in the page) and point Developer FAQ to this page - Rey" I agree with you that fleshing that out could be more useful and if Nick is okay with it, I'd be happy to do so. Nick?
Kicking out of 5.0.9
Target Milestone: 5.0.9 → 5.1
Reopen if there is something for me to do here. ->wontfix
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → WONTFIX
Why isn't this being udpated?
I don't think adding these canned responses is the best way to tackle the problem of users not knowing our policies, and we are redirecting this policy page to the new policy section of dev.AMO anyway (bug not filed yet).
Status: RESOLVED → VERIFIED
Product: addons.mozilla.org → addons.mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: