Closed (fixed)
Project:
Drupal.org site moderators
Component:
User account problem
Priority:
Normal
Category:
Task
Assigned:
Unassigned
Reporter:
Created:
1 Apr 2010 at 15:52 UTC
Updated:
22 Apr 2010 at 08:40 UTC
Dragging http://drupal.org/node/604720 into http://groups.drupal.org/node/58143#comment-168598 is so obvious trolling that it should be rewarded aplenty.
Comments
Comment #1
robloachAlthough I don't really like the idea of blocking someone from an open source community, I am not a fan of all the flaming.
Comment #2
kbahey commentedWas he warned?
Let us warn him him first, then block him if he re-offends.
Comment #3
litwol commentedI have linked Darryl to this initiative. Setting this to postponed, giving him fair chance to clean up his act.
Comment #4
chx commentedWhat warning? He got away with his previous outbreak, that was quite enough. He did not change since October, what more do you want?
Comment #5
jackalope commentedWhat is the official process for blocking users from D.o and g.d.o? I've looked around for site usage policies and haven't been able to find any for either site; would appreciate if someone could point them out if they exist. Thanks!
Comment #6
jackalope commentedI didn't actually mean to change the status of this issue; posted my comment after chx had posted, so I'm switching it back to "reviewed & tested by the community" since that's what chx had set it to.
Comment #7
aaron commentedmorbidly curious about the process myself. subscribe.
Comment #8
tomsherlock commentedGenerally, in my experience and in my opinion, the best solution is to simply focus your attention on the non-flamers, on the non-flames. Flamers are generally looking for a reaction, to get a rise out of us. Starting a thread on a flamer (I don't know the history) is feeding the fire (no pun intended).
I have been a member of a forum totally destroyed by multiple flamers flaming each other and everybody else. However, currently I am a member of a forum with a very open usage policy in which ignored flamers eventually leave. I've also been a moderator of a forum in which offending posters are put on moderation and have (reluctantly) voted repeat offenders off the forum. But that forum had a clear site usage policy and a body of past decisions to reference. Those last two forums dealt with hot button issues on a regular basis.
In addition to discussing a site usage policy, this might also be an opening for reviewing the governance/organization model.
Comment #9
tom_o_t commentedI agree with TomSherlock & jackaponte's concerns about this.
As a member of the NYC community alongside litwol and ghettoprodigy, I've certainly been a recipient of his many promotions of his project, and aware of his conflict with litwol. However banning him from this open source community seems a bit drastic. Unless I've missed something, this is the first time he's brought up this issue in months, and although I agree that he took things off-topic, it was at least slightly related initially. His words were offensive, but can we not just deal with this through discussion rather than resorting to a ban?
Are there any previous examples of someone being banned from DO/GDO?
Is there a written policy about this that's been debated openly by the wider community?
If banning is/becomes a policy of DO/GDO, then we should certainly have a clear procedure along the lines that TomSherlock outlined, rather than only taking action if the aggrieved party has an influential position in the community.
Comment #10
winston commentedI agree with tom_o_t et al. I think this is unnecessarily severe in this particular case. ghetto_prodigy is not a frequent poster to the group in any case.
If he were "constantly" side-tracking or making inappropriate posts then I might have a different opinion.
I think a warning is appropriate though. Whatever issues ghetto_prodigy may have had in the past with a specific member of the nyc community, his grievance was aired and resolved (not to his satisfaction, but you can't please everyone). A warning might make it clear that directing attacks at individuals by responding on unrelated threads is inappropriate and will result in a future ban.
ghetto_prodigy is very passionate about his cause, but his cause is not drupal. We can be big enough to understand his passion, while making it very clear that gdo and drupal meetups are about drupal and nothing else.
Comment #11
ezra-g commentedFor the record here, all 900+ DrupalNYC members got this in their inbox today: http://groups.drupal.org/node/58143#comment-176008
In my view, he continues to escalate after being warned.
Comment #12
kbahey commentedHe contacted me via the Drupal.org contact form, pasting in the whole tirade again.
It was prefaced by "Thought you may want to read my next post before I put it up... it gets pulled down, and I get banned."
When I pointed out to him that this is annoying, and continuing to do this will get him blocked, his reply was:
Me: "If you don't stop emailing people like that, you will be blocked. You continue to do what annoys others."
Him: "I know... but u should really read the whole message... u will understand the conflict..."
Me: "Your passion for your cause is blinding you to the fact that you are annoying others."
Me: "Your passion for your cause is blinding you to the fact that you are annoying others."
Him: "I've gotten 3 compliments and well wishes so far about my last post.... maybe you should read it all the way through...."
I think he has been warned not to do that, yet he still does it. If someone knows him personally, please give him a last warning ... He is not gaining friends, nor helping his cause by pushing it so much ...
Comment #13
litwol commentedI absolutely forbid the use of my name by this person in his posts. First he falsely accuses me and then he tries using my name to accredit his goal because "i have seen" his presentation. I want the post either removed or my name edited out from it (at least the part where he uses my name to accredit himself).
Comment #14
morbus ifflitwol: that's the stupidest thing I've ever heard.
Comment #15
aaron commentedComment #16
Amazon commentedProcess for blocking Drupal.org and Groups.drupal.org user account:
One of the admins on drupal.org or groups.drupal.org warns the user about their activity on the sites. The user does it again and they get blocked for a time period as a cool out.
After the cool out period, the user's account is unblocked. If they repeat the behavior their account is permanently blocked, as well as any subsequent accounts they create.
Has this been done before, yes. I've done it twice. One time the user was blocked permanently for spamming the hosting forums. The second time the account was blocked because the users mail account was hacked. They regained control and I unblocked the account.
I will say that wasting Drupal.org and groups.drupal.org admin time is not something that should be taken lightly. So it's better to block someone's account and see if they want to be respectful of the community norms rather than waste valuable community management time.
Comment #17
litwol commentedmoar: http://groups.drupal.org/node/60603
Comment #18
gerhard killesreiter commentedI've blocked his account.
Comment #19
gerhard killesreiter commented