Re: Python list code of conduct

Date	2013-07-03 15:18 +0100
From	Steve Simmons <square.steve@gmail.com>
Subject	Re: Python list code of conduct
References	(7 earlier) <kqum9j$bsu$1@ger.gmane.org> <a3704f85-2ef1-41e7-8fd1-8d7191f3fddb@email.android.com> <g7n6t8pqn01cj39lbrr067902c520fbvva@4ax.com> <mailman.4142.1372812005.3114.python-list@python.org> <55c93426-5c25-4641-89c7-1396baeb6a67@googlegroups.com>
Newsgroups	comp.lang.python
Message-ID	<mailman.4171.1372861458.3114.python-list@python.org> (permalink)

Show all headers | View raw

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 <link>
> - 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

Back to comp.lang.python | Previous | Next — Previous in thread | Find similar | Unroll thread

Thread

OSError [Errno 26] ?!?! Νίκος <nikos@superhost.gr> - 2013-07-02 06:37 +0300
  Re: OSError [Errno 26] ?!?! Cameron Simpson <cs@zip.com.au> - 2013-07-02 15:15 +1000
    Re: OSError [Errno 26] ?!?! Νίκος <nikos@superhost.gr> - 2013-07-02 08:57 +0300
      Re: OSError [Errno 26] ?!?! Cameron Simpson <cs@zip.com.au> - 2013-07-02 17:21 +1000
        Re: OSError [Errno 26] ?!?! Νίκος <nikos@superhost.gr> - 2013-07-02 12:40 +0300
          Re: OSError [Errno 26] ?!?! Chris “Kwpolska” Warrick <kwpolska@gmail.com> - 2013-07-02 12:06 +0200
          Re: OSError [Errno 26] ?!?! Dave Angel <davea@davea.name> - 2013-07-02 08:00 -0400
            Re: OSError [Errno 26] ?!?! Νίκος <nikos@superhost.gr> - 2013-07-02 15:39 +0300
              Re: OSError [Errno 26] ?!?! Chris “Kwpolska” Warrick <kwpolska@gmail.com> - 2013-07-02 15:00 +0200
              Re: OSError [Errno 26] ?!?! Robert Kern <robert.kern@gmail.com> - 2013-07-02 14:58 +0100
                Re: OSError [Errno 26] ?!?! Steven D'Aprano <steve+comp.lang.python@pearwood.info> - 2013-07-03 00:19 +0000
                Re: Persistence of CGI (was: OSError [Errno 26] ?!?!) Tim Chase <python.list@tim.thechases.com> - 2013-07-02 19:57 -0500
              Python list code of conduct Steve Simmons <square.steve@gmail.com> - 2013-07-02 16:51 +0100
                Re: Python list code of conduct Steven D'Aprano <steve+comp.lang.python@pearwood.info> - 2013-07-03 00:42 +0000
              Re: Python list code of conduct Joshua Landau <joshua.landau.ws@gmail.com> - 2013-07-02 20:48 +0100
              Re: Python list code of conduct Skip Montanaro <skip@pobox.com> - 2013-07-02 15:33 -0500
              Re: Python list code of conduct Ned Deily <nad@acm.org> - 2013-07-02 13:52 -0700
                Re: Python list code of conduct Roy Smith <roy@panix.com> - 2013-07-02 19:46 -0400
                Re: Python list code of conduct Ned Deily <nad@acm.org> - 2013-07-02 17:07 -0700
                Re: Python list code of conduct Cameron Simpson <cs@zip.com.au> - 2013-07-03 10:10 +1000
                Bug reports [was Re: Python list code of conduct] Steven D'Aprano <steve+comp.lang.python@pearwood.info> - 2013-07-03 00:52 +0000
                Re: Bug reports [was Re: Python list code of conduct] Joshua Landau <joshua.landau.ws@gmail.com> - 2013-07-03 02:12 +0100
                Re: Bug reports [was Re: Python list code of conduct] Chris Angelico <rosuav@gmail.com> - 2013-07-03 18:02 +1000
                Re: Bug reports [was Re: Python list code of conduct] Roy Smith <roy@panix.com> - 2013-07-03 10:03 -0400
                Re: Bug reports [was Re: Python list code of conduct] Chris Angelico <rosuav@gmail.com> - 2013-07-04 00:15 +1000
                Re: Bug reports [was Re: Python list code of conduct] Roy Smith <roy@panix.com> - 2013-07-03 10:23 -0400
                Re: Bug reports [was Re: Python list code of conduct] Chris Angelico <rosuav@gmail.com> - 2013-07-04 00:52 +1000
                Re: Bug reports [was Re: Python list code of conduct] Grant Edwards <invalid@invalid.invalid> - 2013-07-03 20:11 +0000
                Re: Bug reports [was Re: Python list code of conduct] Roy Smith <roy@panix.com> - 2013-07-03 16:31 -0400
                Re: Bug reports [was Re: Python list code of conduct] Grant Edwards <invalid@invalid.invalid> - 2013-07-03 21:52 +0000
                IPv6 deployment by ISPs (was: Bug reports) Ben Finney <ben+python@benfinney.id.au> - 2013-07-04 11:15 +1000
                Re: Python list code of conduct Terry Reedy <tjreedy@udel.edu> - 2013-07-03 02:18 -0400
                Re: Python list code of conduct Roy Smith <roy@panix.com> - 2013-07-03 10:10 -0400
                Re: Python list code of conduct Steven D'Aprano <steve+comp.lang.python@pearwood.info> - 2013-07-03 17:24 +0000
              Re: Python list code of conduct Ben Finney <ben+python@benfinney.id.au> - 2013-07-03 08:39 +1000
                Re: Python list code of conduct Steven D'Aprano <steve+comp.lang.python@pearwood.info> - 2013-07-03 06:18 +0000
              Re: Python list code of conduct Dennis Lee Bieber <wlfraed@ix.netcom.com> - 2013-07-02 19:15 -0400
                Re: Python list code of conduct Neil Hodgson <nhodgson@iinet.net.au> - 2013-07-03 19:50 +1000
              Re: Python list code of conduct Ben Finney <ben+python@benfinney.id.au> - 2013-07-03 10:39 +1000
                Re: Python list code of conduct rusi <rustompmody@gmail.com> - 2013-07-03 04:50 -0700
                Re: Python list code of conduct Steve Simmons <square.steve@gmail.com> - 2013-07-03 15:18 +0100

csiph-web