Making WordPress.org

Changes between Initial Version and Version 4 of Ticket #5961


Ignore:
Timestamp:
11/24/2021 04:57:52 PM (3 years ago)
Author:
ocean90
Comment:

Duplicate of #4171.

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #5961

    • Property Status changed from new to closed
    • Property Resolution changed from to duplicate
    • Property Summary changed from Blacklist a wordpress.org account to Block wordpress.org accounts on translate.wordpress.org
  • Ticket #5961 – Description

    initial v4  
    11Currently 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.
    2 So it would be helpful if we could blacklist such and account, with a message containing the reason of blacklisting and indication to join Slack.
     2So it would be helpful if we could block such an account, with a message containing the reason and indication to join Slack.
    33This will probably need some discussion to do it properly.
    4 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 blacklisting.
     4Suggestion 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.
    55This requires an input field where you can add the reason. Or maybe a dropdown selector with valid reasons.
    66It should be done based on account per locale