Addons-frontend: Report this add-on for abuse

[EffPeh]

Describe the problem and steps to reproduce it:

Today I reported an add-on abuse for the first time. I wasn't sure if a popup with advertising text and a link to a website (it's spam for me) violated the policies. So I clicked the link to _Mozilla's add-on policies_

What happened?

Even the first paragraph is irritating for normal users:

Mozilla is committed to ensuring an excellent experience for both our users and developers of add-ons. Please review the policies below before submitting your add-on.

What? I'm here to report abuse. So what's this now?

The first and the third link will take you to a 404-page.
Developer Agreement
Featured Add-ons

The linked page of _Review Process_ is too technical for normal users and doesn't offer any information about spam. I think. My English isn't the best either.

What did you expect to happen?

I expect a uncluttered single page that explains clearly what Mozilla means by abuse. And preferably not only in English. In many cases, anything else could lead to frustration and abandonment of the action.

Anything else we should know?

_Mozilla's add-on policies_
_Review Process_

Broken Links:
Developer Agreement
Featured Add-ons

[jvillalobos]

Broken Links:
Developer Agreement
Featured Add-ons

Those links work for me. Can you check again? Can you look at the URL of the 404 pages and make sure they're the same you posted here?

As for linking to the policies, the idea is that add-ons that don't meet those policies should be reported, which seems clear from what's stated when you click on the Report Abuse button. Maybe @caitmuenster or @MeridelW have other opinions on this point.

[EffPeh]

Those links work for me. Can you check again? Can you look at the URL of the 404 pages and make sure they're the same you posted here?

Yes, I'm sure. Have a look... :)


Maybe it's a locale problem. I'm from Germany.

As for linking to the policies, the idea is that add-ons that don't meet those policies should be reported, which seems clear from what's stated when you click on the Report Abuse button. Maybe @caitmuenster or @MeridelW have other opinions on this point.

Okay. Are you sure this is the view of any inexperienced user? ;)
And what about spam? The extension I reported was just advertising. No benefit for a user.

[willdurand]

Maybe it's a locale problem. I'm from Germany.

Yes, it is indeed a locale issue. What is weird is that on some pages, there are redirections to English content, but your screenshots show nothing...

[EffPeh]

If I go to the English version of the extension page, I have the same problem.
Let's say I'm on _https: // addons.mozilla.org/en-US/firefox/addon/extension-I-want-to-report/_
If I click the link to _Mozilla's add-on policies_ there, I will be directed to the English version.
But if I click on the link to _Developer Agreement_ there, I also get to the German 404 page.

[jvillalobos]

We're linking to the en-US version of the policy index page directly, probably because that's the only version we know is up-to-date. I suppose MDN throws a 404 when it figures out your browser wants a different language and the page doesn't exist in it...

Maybe we should just link directly to the policy page (in English), which is more useful in this context, and should bypass the bad link issue. @caitmuenster, what do you think?

[EffPeh]

Maybe we should just link directly to the policy page (in English), which is more useful in this context, and should bypass the bad link issue.

Maybe. But the pages in other languages should have the same content. That's not the case here. If I follow your link and change the language to German, I get a different content - in English. ;)

[caitmuenster]

Thanks for reporting this issue, @EffPeh! I agree that linking to https://developer.mozilla.org/en-US/Add-ons/AMO/Policy from the abuse report box was pretty clunky.

The AMO Policy Page seems more focused on developers and doesn't look like a good place for users to land. I'd prefer to have them land directly on the Review Policies page, which makes sense given the prompt when a user goes to report abuse.

We updated the policy page in English in April, and it looks like those changes did not carry over to the localization pages. I can copy/paste the updated English text over to the other pages and request localization on the updates. I'm not entirely sure how we can account for this in the future but happy to investigate.

[wagnerand]

@caitmuenster Maybe it makes sense to create a dedicated page about user reviews policy. I agree with the statement in the original comment that "The linked page of Review Process is too technical for normal users and doesn't offer any information about spam." The policies page is targeted to add-on developers.

I can copy/paste the updated English text over to the other pages and request localization on the updates.

I would prefer if we instead deleted the localized page content and redirected those to en-US. The localized pages will often be out of date, and we cannot verify that their content is accurate. Both can have a significant negative effect on developers, trying to submit their add-on.
(Remember that the official policy went through extensive review from various departments inside Mozilla, including Security, Privacy and Legal. I learned that every word in there needs to be reviewed because some general statements can imply liability, for example.)

I can understand that developers would like to read the policies in their language. We could potentially allow localized versions, but they would have to start with a very prominent disclaimer that the localized version is not authoritative and link to the en-US version. And if developers are told not to rely on the localized version, I am wondering how much sense it makes to have them at all.

[EffPeh]

Thank you all for looking at the problem. :)
I also think that linking to _review policies_ is the best solution. At the moment. ;)
But I also hope that a German translation will be available as soon as possible, because I know that many, especially older Germans have problems with the English language.

Maybe it makes sense to create a dedicated page about user reviews policy.

I agree with that.
_Review Policies_ is okay for the moment, but there are still many points incomprehensible to the normal user. Sometimes the user cannot judge the situation at all.

[caitmuenster]

@wagnerand, I'm onboard with creating a user-facing page about the review and abuse reporting process. I'll add it to the project list. @MeridelW and @jenniferdavidson, is this something you might be interested in?

I can investigate concerns around the localization of the policies. I would like to have this information be accessible to non-English speakers :) so let's see what the Powers May Be say.

In the meantime, I'm going to flag this as a maybe-good-first-bug to update the link to the current en-US page for the add-on review policies.

[jvillalobos]

Wrong button, sorry.

[caitmuenster]

Summary:
Currently, the "report abuse" link goes to https://developer.mozilla.org/en-US/Add-ons/AMO/Policy.

Good First Bug - Abuse Report .pdf

We want to change this link to go to https://developer.mozilla.org/en-US/Add-ons/AMO/Policy/Reviews (note: we want to direct link to the en-US link)

Mentor: @willdurand

If this is If this is your first contribution, please refer to https://wiki.mozilla.org/Add-ons/Contribute/Code on how to get started.

[Gabbyjose]

Hi there, I'm interested in helping out with this if it's still available!

[caitmuenster]

Hey @Gabbyjose! Go for it! If you need any help, please feel free to ping @willdurand. :)

[Gabbyjose]

Thanks @caitmuenster! @willdurand, what's the best way to reach you? should i sign up for IRC? i'm reading the docs now and i've never used Docker before so i want to get that set up first

[willdurand]

@Gabbyjose you can write here or email me at < my github username >@mozilla.com.

You do not need docker I think, only node 8 and yarn. Once you have both, you can run yarn followed by yarn amo:dev in the project root directory. After a while, you'll have the website running at http://127.0.0.1:3000/.

[willdurand]

Thanks for your first contribution @Gabbyjose!

[ioanarusiczki]

Verified fixed on AMO dev and AMO stage with FF60(Win10).

I've noticed for the Report user - new pages- an issue on AMO dev https://github.com/mozilla/addons-frontend/issues/5230