Path: csiph.com!usenet.pasdenom.info!news.albasani.net!newsfeed.freenet.ag!news2.euro.net!newsgate.cistron.nl!newsgate.news.xs4all.nl!post.news.xs4all.nl!not-for-mail Return-Path: X-Original-To: python-list@python.org Delivered-To: python-list@mail.python.org X-Spam-Status: OK 0.030 X-Spam-Evidence: '*H*': 0.94; '*S*': 0.00; 'feedback.': 0.04; 'subject:Python': 0.06; 'puts': 0.07; 'sized': 0.07; 'stops': 0.07; 'subject:code': 0.07; 'wednesday,': 0.07; 'steve': 0.09; 'already.': 0.09; 'host,': 0.09; 'thread': 0.14; 'finney': 0.16; 'footnote': 0.16; 'ideally,': 0.16; 'informal': 0.16; 'received:192.168.8': 0.16; 'reminding': 0.16; 'said.': 0.16; 'sins': 0.16; 'suggestion.': 0.16; 'all.': 0.16; 'fix': 0.17; 'wrote:': 0.18; '>>>': 0.22; 'saying': 0.22; 'header:User- Agent:1': 0.23; 'certainly': 0.24; 'lets': 0.24; "shouldn't": 0.24; 'tells': 0.24; 'posts': 0.26; 'header:In-Reply-To:1': 0.27; 'subject:list': 0.30; "i'm": 0.30; 'code': 0.31; "skip:' 10": 0.31; 'that.': 0.31; 'enforce': 0.31; 'idea,': 0.31; 'writes:': 0.31; 'probably': 0.32; 'front': 0.32; 'community': 0.33; 'everyone': 0.33; 'guess': 0.33; 'sense': 0.34; "can't": 0.35; 'etc': 0.35; 'but': 0.35; 'received:google.com': 0.35; 'there': 0.35; 'conduct': 0.36; 'thanks': 0.36; 'should': 0.36; 'list.': 0.37; 'message-id:@gmail.com': 0.38; 'problems': 0.38; 'ben': 0.38; 'convention': 0.38; 'to:addr:python-list': 0.38; 'expect': 0.39; 'bad': 0.39; "couldn't": 0.39; 'to:addr:python.org': 0.39; 'enough': 0.39; 'read': 0.60; 'healthy': 0.61; 'first': 0.61; 'making': 0.63; 'july': 0.63; 'our': 0.64; 'more': 0.64; 'reply': 0.66; 'header:Reply-To:1': 0.67; 'prompt': 0.68; 'social': 0.69; 'mail.': 0.69; 'reply-to:no real name:2**0': 0.71; 'now:': 0.74; 'reply-to:addr:gmail.com': 0.80; 'avoid.': 0.84; 'enforcement': 0.84; 'fragments': 0.84; 'guidelines.': 0.84; 'homework': 0.84; 'simmons': 0.84; 'standing': 0.84; 'rusi': 0.91; 'responses': 0.93; 'tomorrow': 0.95; '2013': 0.98 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:reply-to:user-agent:mime-version:to:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=OSrKZI+W6LNSWJ9fktxCuJYczEvbk1YqIS45K4i3FFU=; b=NHTX8S1bpnOQyD9+AMCnMKt8DEVJFPC8Cnf8qi2bL8GUdWicufadYOMuUDYwWpSS2I Sf+Sb7NDR8+0+m14zpWyXrP87T+KAO8Wy5M/cnJCyjKwYcz/f09jTn8wyxzcZAfiIUKl BB+bhji1jnpHM4iRZoW5z14SFZDMunqbb8zXvOAiQA3jbltxMzkmkIH4zNxYCGyKySye AtulT+tVhcxHOzlpk17/nWBorEk5NRn4KxDPuujc9w+FOunCK10DeFpnhmruy3ZV049V uaP+z0e3jzWUb7mtwpg2wHggnqM/7xEhd9OEPirCWfuuPUwyZD9+fgmj8FwdTCfK6FMI Xiqw== X-Received: by 10.14.209.197 with SMTP id s45mr1338904eeo.108.1372861090541; Wed, 03 Jul 2013 07:18:10 -0700 (PDT) Date: Wed, 03 Jul 2013 15:18:06 +0100 From: Steve Simmons User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130620 Thunderbird/17.0.7 MIME-Version: 1.0 To: python-list@python.org Subject: Re: Python list code of conduct References: <55c93426-5c25-4641-89c7-1396baeb6a67@googlegroups.com> In-Reply-To: <55c93426-5c25-4641-89c7-1396baeb6a67@googlegroups.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: python-list@python.org X-Mailman-Version: 2.1.15 Precedence: list Reply-To: square.steve@gmail.com List-Id: General discussion list for the Python programming language List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Newsgroups: comp.lang.python Message-ID: Lines: 48 NNTP-Posting-Host: 2001:888:2000:d::a6 X-Trace: 1372861458 news.xs4all.nl 15874 [2001:888:2000:d::a6]:46182 X-Complaints-To: abuse@xs4all.nl Xref: csiph.com comp.lang.python:49743 On 03/07/2013 12:50, rusi wrote: > On Wednesday, July 3, 2013 6:09:35 AM UTC+5:30, Ben Finney wrote: >> Dennis Lee Bieber writes: >> >>> So who would enforce any rules? >> Ideally, this community is healthy enough for us to enforce the code of >> conduct of our host, through social convention among us all. > Thanks Ben for that. > Lets not stymie Steve Simmons original suggestion for a CoC by making it into a formal CoC and then saying its impossible. > > There is a good deal of informal enforcement already. Consider eg: > - Mark's footnote reminding about GG problems and their solutions > - Steven's brusque 'cut-the-crap' type responses > - Your own prompt STOPs to racist/sexist etc posts > etc > > So we may take and welcome Steve Simmons' call to expand that list. > I certainly welcome the suggestion. Thanks Rusi - and everyone else that provided feedback. I understand (and had already anticipated) that this type of group can't and probably shouldn't be moderated in the more draconian sense of the word but there's no reason why we couldn't create some behavioural and technical guidelines. I had it in mind to move to a few (?!) paragraphs that read well when considered as a single document but that were also suitable to cut'n'paste into a response - much as Mark puts his GG warning in every mail. The aim would be to put a considered response in a first reply that tells the OP 'this is what you need to do to get a sensible answer'. We have this for GG & code fragments and I see no reason why we can't have it for bad language; bad attitude; unreasonable expectations; thread high-jacking; top posting; and all the other sins we expect Noobs (and some long standing members!) to avoid. I guess I should have said this up front but let me say it now: I completely 'get' that this won't fix the Trolls or the dyed-in-the-wool pedants or recidivist high-jackers but it may put some buffering between: Newb: "I want you to do my homework and I have to give it in tomorrow morning" and Pythonista: "you're a dick" If there's enough support for the general idea, I'm happy to make a decent sized contribution but if there isn't - Nuff said. Steve