Closed (fixed)
Project:
Drupal.org site moderators
Component:
User account
Priority:
Normal
Category:
Task
Assigned:
Unassigned
Reporter:
Created:
21 Apr 2022 at 19:34 UTC
Updated:
12 Nov 2022 at 06:49 UTC
Jump to comment: Most recent
The user https://www.drupal.org/user/1928228 marked many issues as won't fix that should not have been marked won't fix.
...
I blocked them to stop the damage, but something more likely needs to be done. I (greggles) do not have time to do more.
more stuff
reach out to them?
clean up the issues
clean up any other changes they made
Comments
Comment #2
gisleRemaining tasks:
Since the user is blocked, most site moderators don't have any access to the account.
I.e. we cannot contact the user, nor review list of issues to clean up.
To determine what to do in the long term, someone also needs to review the user's history here.
If this is a new user, with no history of making useful contributions, I think the account can stay blocked.
If this is a user that in the past has contributed, we need to reach out to him/her, explain why this is disruptive behaviour, and that he/she should stop doing it, restore access, and the site moderators should monitor behaviour and intervene if he/she continues to disrupt.
I think apaderno has elevated access to user accounts, and is best positioned to reach out, clean up and review the account's history, so I hope he is able to do this.
Comment #3
avpadernoI contacted the user, explaining that closing so many issues as "won't fix" is wrong and suggesting what should instead be done.
Comment #4
joseph.olstadthis users landing page is a 403
https://www.drupal.org/user/1928228
Comment #5
joseph.olstadI think @stephencamilo is a bot account or a malicious user
Comment #6
avpadernoThe user account has been temporary blocked. Only user administrators can access a blocked account profile.
Comment #7
simgui8 commentedI looked into @stephencamilo profile before the ban yesterday, and he has made some contributions in the past.
(I looked after he closed issue 2905295)
Comment #8
avpadernoYes, the user contributed in the past. The account has been created almost ten years ago.
Comment #9
hestenetWe are communicating with @stephencamilo via Drupal.org's help@drupal.org email address.
Comment #10
avpadernoThe account is still blocked. Should not it be unblocked, now?
Comment #11
avpadernoI apologize for bumping this issue, but six months are passed since this issue has been open.
The user has been contacted and it was explained that what he did was wrong. The account should be unblocked now, except in the case he declined to follow what told him to do, which isn't the case, as far as I know.
Given that what done can be easily reverted, I don't see any reason to keep the account blocked.
Comment #12
greggles@appaderno thanks for thinking of that. I agree if they responded favorably in private email conversations we should unblock. In #3 you said you started a conversation. How did your conversation go with them?
Given the Drupal Association reached out to them I'd love for Hestenet or another DA person involved to have input on the decision to unblock or keep blocked.
Comment #13
avpadernoI don't have access to my email from the computer I am using now, but I I can say that stephencamilo didn't object to what I said he should not do. He just asked what he should instead do and I explained it was better to leave a comment asking about the issue status, instead of unilaterally setting those issues to won't fix.
Comment #14
hestenetThat sounds good apaderno, in that case I'm certainly in favor of unblocking.
Comment #15
gregglesOK, the account is now active again. Thanks everyone for their help.
Comment #16
avpaderno