Block wordpress.org accounts on translate.wordpress.org

[psmits1567]

Currently if an account on wordpress.org delivers wrong translations, there is no method to contact this account. If the account adds lots of wrong translations via import, you cannot tell him to stop doing this. The method to use currently is to bulk reject those suggestions. But that is a lot of work and corrupts the database.
So it would be helpful if we could block such an account, with a message containing the reason and indication to join Slack.
This will probably need some discussion to do it properly.
Suggestion is to add a function to maintain the wordpress.org account by a GTE or locale manager, with which you can blacklist the account. At the time this function is fired, the user will get a message with the reason of block.
This requires an input field where you can add the reason. Or maybe a dropdown selector with valid reasons.
It should be done based on account per locale

[NekoJonez]

QQ: what about locales like ours? nl_NL which has a default and formal. Should we look at nl_NL and nl_NL-formal as separate locales?

[tobifjellner]

I agree with parts of this suggestion.

The number of cases will probably not be that big, so we should aim for a solution that is lean on resources, both in development hours and in execution time.

• There's really no need to try and have fine-grained blocking per locale.
• And it may be OK to have one and the same system-wide message to blocked accounts. But if it's ok implementation-wise to add a personal "blocking reason", then that would be great, as a way to indicate to the user whom they could contact to have the blocking removed.
• The list of blacklisted accounts could be edited/maintained for instance by either users with global access on translate.. or by editors on make/polyglots.

[ocean90]

Duplicate of #4171.