From #drupal-contribute (CDT):
(06:01:00 PM) ksenzee: Who closed comments on http://drupal.org/node/140783 ?
(06:01:01 PM) Druplicon: http://drupal.org/node/140783 => A select list without #default_value always passes form validation => Drupal core, forms system, critical, needs review, 120 comments, 7 IRC mentions
(06:01:04 PM) ksenzee: Without announcing it?
(06:01:17 PM) ksenzee: Unless I missed the announcement, that is an abuse.

At one point a Drupal.org webmaster had inappropriately locked comments and should be considered an abuse of power. As there are no revisions on the node, I can't see who actually did it, but let this hopefully serve as a warning that this behavior will not or ever be acceptable and I'll leave it at that.

Comments

rfay’s picture

IMO this is a serious problem and should be dealt with directly.

gerhard killesreiter’s picture

We can see from the activity log who locked the node.

However, locking a node is easily reversible, so this was done.

If we'd kick people out every time somebody throws a temper tantrum we'd have a much worse Drupal, so I am leaving it at that for now.

rfay’s picture

@killes, I agree, and I think we all came to the same conclusion in IRC last night.

rfay’s picture

One thing that comes to mind here: Have we made it clear to everyone with privileges on drupal.org that privileges are to be used for the site's benefit and the community's benefit, not for personal purposes? I suspect we have some socialization to be done in that area. I suspect we could state this principle concisely and maybe even have a short handbook page about it.

It's obvious, but not always obvious.

gerhard killesreiter’s picture

I think it is so very obvious that I do not think a handbok page is neccessary, however, if you are so inclined, feel free to create one.

nevets’s picture

Status: Fixed » Needs review

Instead of opening a new issue I thought I would add to this one, http://drupal.org/node/927624 had it's comments also locked (I unlocked them). Comments where disabled even before someone could respond to the persons question.

rfay’s picture

@killes, I completely agree with you that this should not be necessary, but we have a large community.

I propose adding this at the top of the Drupal.org Site Maintainer's Guide
I believe there are other common-sense things that should be mentioned here as well. But these are the two principles I thought of:

---

Responsibilities of privileged users on Drupal.org

In addition to the "work" responsibilities of privileged users, there are some practical and ethical responsibilities also:

  • You are responsible to use your privileges in a way that benefits the community and the site, and not for personal reasons. If you have a question about whether your action is appropriate for the community and the site, you should file an issue in the webmasters queue or find other privileged users to consult with, in accordance with the Drupal Code of Conduct. It's best to defer action and involve others if you're angry or frustrated or otherwise emotional. In the vast majority of cases there is no need for immediate action.
  • You are responsible to protect your account in a way that befits you enhanced privileges. Please make sure to use a secure password and in all other ways protect your account as you would your online banking account (or better, if you don't care for that one :-)
tvn’s picture

Status: Needs review » Closed (fixed)

Closing old issues. Please re-open if necessary.