From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from lists.gentoo.org ([140.105.134.102] helo=robin.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1IrUks-00073l-2a for garchives@archives.gentoo.org; Mon, 12 Nov 2007 08:34:50 +0000 Received: from robin.gentoo.org (localhost [127.0.0.1]) by robin.gentoo.org (8.14.2/8.14.0) with SMTP id lAC8Ybcc024790; Mon, 12 Nov 2007 08:34:37 GMT Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) by robin.gentoo.org (8.14.2/8.14.0) with ESMTP id lAC8YawE024785 for ; Mon, 12 Nov 2007 08:34:37 GMT Received: from localhost (localhost [127.0.0.1]) by smtp.gentoo.org (Postfix) with ESMTP id 619B4653E0 for ; Mon, 12 Nov 2007 08:34:36 +0000 (UTC) X-Virus-Scanned: amavisd-new at gentoo.org X-Spam-Score: 1.001 X-Spam-Level: * X-Spam-Status: No, score=1.001 required=5.5 tests=[AWL=-1.067, BAYES_50=0.001, RCVD_NUMERIC_HELO=2.067] Received: from smtp.gentoo.org ([127.0.0.1]) by localhost (smtp.gentoo.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zQkYVYPWxGN6 for ; Mon, 12 Nov 2007 08:34:30 +0000 (UTC) Received: from ciao.gmane.org (main.gmane.org [80.91.229.2]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by smtp.gentoo.org (Postfix) with ESMTP id 3B48A657EF for ; Mon, 12 Nov 2007 08:34:29 +0000 (UTC) Received: from list by ciao.gmane.org with local (Exim 4.43) id 1IrUkO-00040O-C8 for gentoo-project@gentoo.org; Mon, 12 Nov 2007 08:34:20 +0000 Received: from 82.152.248.68 ([82.152.248.68]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 12 Nov 2007 08:34:20 +0000 Received: from slong by 82.152.248.68 with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 12 Nov 2007 08:34:20 +0000 X-Injected-Via-Gmane: http://gmane.org/ To: gentoo-project@lists.gentoo.org From: Steve Long Subject: [gentoo-project] Re: CoC enforcement proposal Date: Mon, 12 Nov 2007 08:38:21 +0000 Message-ID: References: <20071108120507.GJ5516@supernova> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Project discussion list X-BeenThere: gentoo-project@gentoo.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7Bit X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: 82.152.248.68 User-Agent: KNode/0.10.4 Sender: news X-Archives-Salt: 44bd5dd7-052b-41d4-9f14-13d67f1ba6dd X-Archives-Hash: 119dc83662ec12e8e82cf52062bf0f5c Donnie Berkholz wrote: > This is a bit later than I intended because of real life interference, > but here's some ideas for how to enforce the CoC. It's a little long, > sorry about that; we can push off the vote again if we don't have a > majority of people prepared for it by the meeting. > > I separated it into problem, conceptual solution, and implementation so > you can decide which levels you like and which could use tweaking. > Firstly, thanks (from a user) for your hard work on this. Personally I like the mechanisms discussed for implementation, both the time periods envisaged and the move to behind-the-scenes. I feel less comfortable with the following: 1) "a strong lead to ensure the team's actions fit the council's CoC interpretation." While I agree the team needs to act consistently, and in a united manner (ie speak with one voice, as it were) I do not think placing emphasis on one individual is a wise move. It places greater onus on that person, and often leads to more stress followed by burnout, with all the attendant problems which are much more difficult precisely because the individual has greater authority. A strong team, made of strong personalities who are mature enough to reach collective decisions, is better both for the appearance of impartiality and longer-term consistency. 2) "It is expected that membership on this team will be highly selective and not all who wish to join will make the cut. The team will be limited to 3 people for a probationary period so we don't get dumped in the deep end right away, and it will never have more than 5 people." I don't think it should really be a job given to people who want to do it for the sake of it. The last team appeared to be the right set, based on their experience, and seemed to take the job because it needed to be done, not because it was seen as some sort of elite team. Maybe I'm being a bit sensitive to the nuance of the language, but I think the tone matters. The numbers others have commented on; I concur that it seems a bit limited (in the longer-term) to cover the timezones and ensure timely coverage. Expanding on that a bit, I think it would be good to stipulate some sort of cross-cultural mix: a team made up of purely North Americans or Anglophones is not going to be as attuned to the sensitivities of the diverse user base as is needed, imo. Wernfried Haas wrote: > This is quite similar to how warnings andbans are done on the forums, > we always document who warned/banned whom and for what reason and it > has worked quite well so far there. ++ to documentation, and the points others raised about an appeals mechanism. Amne also mentioned discussion with the "offender" before sanctions are imposed. While I agree that you don't want to get into an argument with people, I think you're going to have to accept that people *will* argue about it (even more so given that it's techies) and your team needs to be ready to justify their decisions. I have no issue with a mute being imposed first (for a few hours) and the discussion taking place at that point. But there does need to be that discussion, and the earlier the better, so that people are brought into line with community expectations at an early stage, when the conflict is less. The proposal to review monthly for the first 3 months seems sound too. Thanks for the proposal so far; the actual details of the day-to-day implementation are just right imo. -- gentoo-project@gentoo.org mailing list