This comes from #938458: Warn Amazon for abuse of webmaster privileges -

In the Drupal Code of Conduct, we currently have placeholder text for conflict resolution: http://drupal.org/dcoc#conflict-resolution.

From http://drupal.org/node/759522#comment-2819652 :

Process 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.

This can provide a starting point for describing how the process of blocking users is managed, but this doesn't get us very far on the process for resolving conflicts. This ticket will (hopefully) provide a place to collect ideas around and clarify the larger conflict resolution process.

Comments

bonobo’s picture

http://groups.drupal.org/node/73238 - this page has some good ideas culled from the conflicts that arose in the NYC group; these ideas/phrasing could be adapted here.

gerhard killesreiter’s picture

I just want to point out that I never considered these "dcoc" rules of any relevance for the drupal.org website. I consider them meta-rules for the project as such.

tvn’s picture

Status: Active » Closed (won't fix)

Closing old issues. Please re-open if necessary.