public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Jason Rhinelander <jason@gossamer-threads.com>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] The Gentoo Developer Handbook - Quis custodiet ipsos custodes?
Date: Tue, 20 Jul 2004 11:07:17 -0700	[thread overview]
Message-ID: <40FD5F55.9010408@gossamer-threads.com> (raw)
In-Reply-To: <20040720002322.GL18023@mail.lieber.org>

Kurt Lieber wrote:
> On Mon, Jul 19, 2004 at 07:20:24PM +0100 or thereabouts, Ciaran McCreesh wrote:
>>* The ability to impose arbitrary restrictions upon what developers are
>>and are not allowed to say on IRC and the mailing lists.
> 
> I have seen this and I strongly disagreed with it then and now.  I don't
> believe it is *ever* appropriate for devrel to censor devs, whether it be
> temporarily or permanently. As long as it is done professionally and
> courteously, devs should be able to express themselves freely imo. 

That appears to be what the recently posted documents laid out.  It 
seems to me from those documents that the only time censorship would 
come into play would be when devs are _not_ expressing themselves 
professionally and courteously.  I didn't see anything that talked about 
or indicated "arbitrary restrictions" - the restrictions seemed clearly 
laid out for cases where devs are acting inappropriately.

> 
> --kurt


-- Jason Rhinelander
-- Gossamer Threads, Inc.

--
gentoo-dev@gentoo.org mailing list


  parent reply	other threads:[~2004-07-20 18:07 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-19  9:20 [gentoo-dev] The Gentoo Developer Handbook - Now with FREE* extra mojo! Tim Yamin
2004-07-19 13:14 ` Daniel Armyr
2004-07-19 13:58 ` Spider
2004-07-19 15:27   ` Joshua Brindle
2004-07-19 18:20     ` [gentoo-dev] The Gentoo Developer Handbook - Quis custodiet ipsos custodes? Ciaran McCreesh
2004-07-19 20:22       ` Corey Shields
2004-07-19 20:35         ` Ciaran McCreesh
2004-07-19 20:55           ` Corey Shields
2004-07-19 21:03             ` Ciaran McCreesh
2004-07-19 20:47         ` fmouse-gentoo
2004-07-19 20:57         ` Jason Rhinelander
2004-07-19 21:02           ` Corey Shields
2004-07-19 21:14           ` Tim Yamin
2004-07-19 20:44       ` Stuart Herbert
2004-07-19 21:06         ` Ciaran McCreesh
2004-07-19 21:12           ` Stuart Herbert
2004-07-19 21:44             ` Spider
2004-07-19 22:03               ` Stuart Herbert
2004-07-20  0:31                 ` Dylan Carlson
2004-07-20  5:10               ` [gentoo-dev] " Duncan
2004-07-19 22:30         ` [gentoo-dev] " Grant Goodyear
2004-07-19 23:03         ` Tom Knight
2004-07-19 22:19       ` Grant Goodyear
2004-07-19 23:46         ` Deedra Waters
2004-07-20  0:23       ` Kurt Lieber
2004-07-20  1:38         ` Jon Portnoy
2004-07-20 10:15           ` Chris Bainbridge
2004-07-20 12:36             ` Dylan Carlson
2004-07-20 15:43               ` Stuart Herbert
2004-07-20 17:55                 ` Kurt Lieber
2004-07-20 21:13                 ` Deedra Waters
2004-07-20 21:43                   ` Stuart Herbert
2004-07-20 21:50           ` Donnie Berkholz
2004-07-20 18:07         ` Jason Rhinelander [this message]
2004-07-19 21:49 ` [gentoo-dev] The Gentoo Developer Handbook - Now with FREE* extra mojo! Stuart Herbert
2004-07-22  9:27 ` Stuart Herbert

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=40FD5F55.9010408@gossamer-threads.com \
    --to=jason@gossamer-threads.com \
    --cc=gentoo-dev@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox