From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([69.77.167.62] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1KIwvb-0003FT-Jh for garchives@archives.gentoo.org; Wed, 16 Jul 2008 02:39:39 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id D6F46E051B; Wed, 16 Jul 2008 02:39:38 +0000 (UTC) Received: from QMTA01.emeryville.ca.mail.comcast.net (qmta01.emeryville.ca.mail.comcast.net [76.96.30.16]) by pigeon.gentoo.org (Postfix) with ESMTP id 7DF31E051B for ; Wed, 16 Jul 2008 02:39:38 +0000 (UTC) Received: from OMTA08.emeryville.ca.mail.comcast.net ([76.96.30.12]) by QMTA01.emeryville.ca.mail.comcast.net with comcast id qRlC1Z00B0FhH24A1SfdUz; Wed, 16 Jul 2008 02:39:37 +0000 Received: from mail.twi-31o2.org ([24.6.98.17]) by OMTA08.emeryville.ca.mail.comcast.net with comcast id qSfc1Z0010NWACg8USfdMd; Wed, 16 Jul 2008 02:39:37 +0000 X-Authority-Analysis: v=1.0 c=1 a=ni8Frk1T-iwA:10 a=MY_6DjmEkWsA:10 a=D3KxJrk44h4TIrD01l4A:9 a=dBeL1apK46CipIxZXEwA:7 a=Zk0S3h1N2dIYqPZmI2UZbd_qIUMA:4 a=MxZ3bB5I4kYA:10 Received: from localhost (localhost.twi-31o2.org [127.0.0.1]) by mail.twi-31o2.org (Postfix) with ESMTP id 69D1A8B4003 for ; Wed, 16 Jul 2008 02:39:35 +0000 (UTC) X-Virus-Scanned: amavisd-new at twi-31o2.org Received: from mail.twi-31o2.org ([127.0.0.1]) by localhost (gravity.twi-31o2.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rrYpFctLYiDq for ; Wed, 16 Jul 2008 02:39:31 +0000 (UTC) Received: from draco2 (orion.twi-31o2.org [192.168.0.11]) by mail.twi-31o2.org (Postfix) with ESMTP id 68C8C8B4002 for ; Wed, 16 Jul 2008 02:39:31 +0000 (UTC) From: "Chrissy Fullam" To: "'gentoo-council'" References: <20080714063554.GB5982@comet> In-Reply-To: <20080714063554.GB5982@comet> Subject: RE: [gentoo-council] Extent of Code of Conduct enforcement Date: Tue, 15 Jul 2008 19:39:21 -0700 Message-ID: <2c6d01c8e6ed$2d1dbb60$87593220$@org> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-council@lists.gentoo.org MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook 12.0 Thread-Index: Acjle+GsjC4VngLtQwqMbbV02zbUaQBbyOWA Content-Language: en-us X-Archives-Salt: f8193afd-6d22-49c7-a678-f8fab8ff7b91 X-Archives-Hash: f9a3f8be5a6c15374458980f94edcf23 > Can people be entirely banned from Gentoo? By technical merit I'd not say that anything is entirely outside of technical ability if one has that ability to circumvent the system. Doesn't mean we should throw the towel in and just sit back to take abuse though. > - What would such a ban include? Some ideas -- the person could not: > - Post to any gentoo mailing list; > - Post to gentoo bugzilla; > - Participate in #gentoo- IRC channels; > - Contribute to gentoo (hence my corner case of a security fix) except > perhaps through a proxy; Mailing list rights and bugzilla rights for that email address would be revoked; the argument is if they subscribed with a different email address what then? If they are confirmed to be the original person User Rel should talk to them and quite possibly extend the ban to the new accounts - not my decision just an idea; argument being when do we stop because they could keep trying with new accounts? My response is situational, likely I'd consider continuing doing it so long as it was verified to be that person but that is my opinion. Changing your name doesn't make you less of an ass, only you can make yourself less of an ass. Regarding IRC, we should only remove their nick from #gentoo-dev as other channels are moderated and operated by the relevant team. I for one would remove anyone from #gentoo-devrel, but that is my right to do so. Contributions... I'd vote to only accept via a proxy so long as said proxy understands they are vouching 100% for the quality of the code as well. This should be common practice today I suspect. > - Why would we do it? Because we do our developers and users a disservice to allow such repeat offenders the luxury of participating in such a manner while ruining the experience for others. Simply put people quit and drop Gentoo solely as a result of one or several vocal negative and abusive influences. Let's do our jobs and do something about it. > - Under whose authority would it happen? Dev Rel would have removed such a person from being a developer in which case this round of elimination would fall upon User Rel, whom Dev Rel would gladly assist if assistance were requested. > - Would it be reversible? What conditions would cause this? > > Since the banned person couldn't participate in Gentoo, we'd never > know whether anything changed. Life happens, people change. No ban should be 100% forever so let's be realistic here. If User Rel banned someone from participating they could follow the same rule set that Dev Rel uses: a forcibly removed developer may return upon approval of the current Dev Rel lead. That said, if a forcibly removed contributor/participator wanted to come back that person would need to convince the User Rel lead of a darn good reason and such re-joining should be done under a probationary period subject to review. > - How would one appeal this? Would there be a chance to respond before > the ban? Appeal a ban, no. I think if someone is being considered for the ban there should be an exchange of dialog. That said, no person eligible for such an extreme course of action could honestly say they were surprised and caught off guard. Such a person would have a repeated history of conflicts and discussions warning them that they are out of line, be it in a bug or via emails. > - Would moderating the gentoo-dev mailing list obsolete this concept? Nope, just make it less likely to happen as hopefully we'd be able to show people that we are taking this seriously and it must stop or the consequences continue to get more severe. Much like the legal system fmccor references, a jury or judge is less sympathetic to the protests of a repeat offender. Kind regards, Christina Fullam Gentoo Developer Relations Lead | Gentoo Public Relations -- gentoo-council@lists.gentoo.org mailing list