From: Ranjit Singh <ranjit@sukhisoft.com>
To: gentoo-proctors@lists.gentoo.org
Subject: Re: [gentoo-proctors] Proctors - An RFC about their role/powers
Date: Sun, 10 Jun 2007 09:16:09 +0100 [thread overview]
Message-ID: <200706100916.36937.ranjit@sukhisoft.com> (raw)
In-Reply-To: <466888DC.8090606@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 2454 bytes --]
On Thursday 07 June 2007 23:38, Jorge Manuel B. S. Vicetto wrote:
> The following document is part of a mail I've sent to the proctors@
> alias 6 weeks ago and that was my contribution to a discussion we were
> having about the CoC and the proctors.
Thanks for sharing the info. It's nice to see some transparency (although Mr
Marples' attempts to be transparent shows the difficulty.)
> At the time I didn't submit that document here, because there was no
> such ml and we were still having an initial internal discussion.
Understood and perfectly reasonable.
> Since the team has yet to publish any document on this due to a variety
> of reasons and that we've been accused of not working on this issue (I
> say we, as a former member of the team), I think it's important to show
> that claim to be false.
Er ok, although that makes the above a bit less of a given ;) Wrt to
detractors, I have a feeling that many of those will be people who would be
affected by the work of the team, and their cohorts. In my opinion all mail
to proctors should be publically accessible. After all, it is sent in clear
text to an official complaints address.
> ----------------------------------------------------------------
> Gentoo Proctors
>
> General Applicability / Enforcement Questions (to be answered by council?)
>
> What medium/channels?
Any and all with gentoo in the name. (R) anyone?
> What powers?
Equivalent to forum admin.
> What philosophy: punishments/preventive action?
Ditto.
> What are the available options for the different mediums (we need the
> input from infra)
FFS you're programmers!
> Do we want/accept penalties/remedies crossing mediums? (Do we want a ban
> from forums to extend to bugzilla?)
Yes.
> Do we want/accept permanent bans?
>
Yes.
> What audience?
> Do we address users and devs? (council said everyone)
++
> What powers can/will the proctors have over devs?
What? As above.
> Do proctors act on devs directly or through devrel?
>
Directly with input from kloeri and g2boojum
> What proctors?
Er.
> Are proctors elected or appointed and by whom?
Elected from pool: forum admins, devrel and council.
> Are members elected/appointed for a mandate or for ad-eternum?
Mandate. wtf asked that?
> Who controls the proctors? (who watches the watchman?)
Er we do. Got it? :)
<snip blah>
Thanks for some sanity :)
Flame on paludis minions!
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2007-06-10 8:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-07 22:38 [gentoo-proctors] Proctors - An RFC about their role/powers Jorge Manuel B. S. Vicetto
2007-06-10 8:16 ` Ranjit Singh [this message]
2007-06-10 9:47 ` Wulf C. Krueger
2007-06-11 13:25 ` Ranjit Singh
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=200706100916.36937.ranjit@sukhisoft.com \
--to=ranjit@sukhisoft.com \
--cc=gentoo-proctors@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