From: Corey Shields <cshields@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] The Gentoo Developer Handbook - Quis custodiet ipsos custodes?
Date: Mon, 19 Jul 2004 15:22:58 -0500 [thread overview]
Message-ID: <200407191522.58101.cshields@gentoo.org> (raw)
In-Reply-To: <20040719192024.12ae4a5e@snowdrop.home>
On Monday 19 July 2004 01:20 pm, Ciaran McCreesh wrote:
> I'm sure devrel aren't actively out to set themselves up as the new
> spanish inquisition. However, it seems I'm not the only one that's
> noticed them moving from a "helping developers" role to "policing
> developers" instead, and I'd like to know what devrel's stance on this
> is. Come to think of it, I remember a certain former manager bringing
> this exact point up shortly before he left.
Nobody on the devrel team is getting their jollies from "policing developers",
and if there wasn't a need for it then you wouldn't see it. The problem is
that some people have acted or said some pretty offensive things while acting
on behalf of Gentoo in the eyes of the victim. That can't be put up with,
and personally I'm not open to be persuaded otherwise. Whether developers
realize it or not, there are corporations and large organizations watching,
and some of them migrating to Gentoo. As a distribution, we can't tolerate
developers being jerks to other people, especially our users. I know this
first hand, because my place of employment was about to pack up and walk away
from Gentoo altogether after one such altercation between one of our
employees and a dev.
I don't think it is asking too much of people to treat each other
appropriately. If that is the case, then you won't see devrel's involvement
and there is no problem.
Cheers,
-Corey
--
Corey Shields - Gentoo Linux Infrastructure Team
http://www.gentoo.org/~cshields
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2004-07-19 20:23 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 [this message]
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
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=200407191522.58101.cshields@gentoo.org \
--to=cshields@gentoo.org \
--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