From: Chris Gianelloni <wolf31o2@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] council and proctors
Date: Tue, 17 Jul 2007 12:09:58 -0700 [thread overview]
Message-ID: <1184699398.8603.15.camel@inertia.twi-31o2.org> (raw)
In-Reply-To: <20070717074133.GB10105@superlupo.rechner>
[-- Attachment #1: Type: text/plain, Size: 1057 bytes --]
On Tue, 2007-07-17 at 09:41 +0200, Wernfried Haas wrote:
> So the way i read it devrel would like to do something if requested,
> but isn't supposed to enforce the CoC, nor has the authority?
Considering that the Code of Conduct is a subset of the regular Gentoo
developer policies that Developer Relations already enforces, I would
say that they are definitely enforcing the CoC and have the authority.
What DevRel currently doesn't have is authority to exercise over users,
rather than just developers. Basically, we're back to where we were
before we had the Proctors, except we have a more succinct document on
what is expected behavior. There are several proposals out now (you've
seen the enormous thread, I'm sure) dealing with possible alternative
solutions to the Proctors. One of them will likely be implemented some
time soon. We'll just have to wait and see.
--
Chris Gianelloni
Release Engineering Strategic Lead
Alpha/AMD64/x86 Architecture Teams
Games Developer/Council Member/Foundation Trustee
Gentoo Foundation
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2007-07-17 19:14 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-15 0:59 [gentoo-dev] council and proctors Ferris McCormick
2007-07-15 15:11 ` Timothy Redaelli
2007-07-16 15:08 ` Wernfried Haas
2007-07-16 16:22 ` [gentoo-dev] " Steve Long
2007-07-16 16:23 ` Petteri Räty
2007-07-16 23:21 ` [gentoo-dev] " Ferris McCormick
2007-07-16 23:58 ` Chrissy Fullam
2007-07-17 7:41 ` Wernfried Haas
2007-07-17 19:09 ` Chris Gianelloni [this message]
2007-07-17 19:19 ` Wernfried Haas
2007-07-15 15:25 ` Ioannis Aslanidis
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=1184699398.8603.15.camel@inertia.twi-31o2.org \
--to=wolf31o2@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