public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Chrissy Fullam" <musikc@gentoo.org>
To: <gentoo-dev@lists.gentoo.org>
Subject: RE: [gentoo-dev] Monthly Gentoo Council Reminder for October
Date: Mon, 1 Oct 2007 07:33:54 -0700	[thread overview]
Message-ID: <800B72070D0242638ECF9900D0D3C847@draco2> (raw)
In-Reply-To: <1191244531.6890.96.camel@liasis.inforead.com>

> From: Ferris McCormick [mailto:fmccor@gentoo.org] 
> Subject: Re: [gentoo-dev] Monthly Gentoo Council Reminder for October
> 
> Substantive
> -----------
> It is not clear whether or not Gentoo currently has a Code of 
> Conduct or even if the Council wishes it to.  
> (1) whether the Code of Conduct is in effect; 
> (2) if so, how we enforce it.  
> (3) Code of Conduct explicitly calls out a Proctors group as its
> executive arm, but previous Council disbanded the proctors.  
> (4) If we are not serious about having a Code of Conduct, I'd 
> like Council to explain why not.  

I think these are best addressed by Council members and look forward to that
discussion. We can clearly see where Council disbanded the Proctors project
(http://www.gentoo.org/proj/en/council/meeting-logs/20070712-summary.txt),
but it does not answer how the CoC would be enforced or if it should be
rolled into a more general policy, enforced by existing teams (DevRel or
UserRel come to mind.) I'm sure assumptions were made, however, they were
not documented.

> I will mention that devrel does receive complaints on 
> occasion which would properly fall under the Code of Conduct 
> and proctor control --- either because any policy violation 
> complained of falls under the Code of Conduct better than 
> under a devrel problem,

Developer Relations has had no problem, reported or otherwise discussed,
with addressing these issues.

> or because it is a user/developer issue, 

Requests that are user/developer issue in nature should currently either go
through User Relations or Developer Relations, depending on the nature,
though we work together fine.

> or because by the time it gets to us it's stale, 

I'm not aware of any issue escalated to Developer Relations that was stale
by the time we were made aware, though I suppose the term stale is subject
to interpretation.
 
> Anyway, Code of Conduct status needs clarification and action.

It seems that there is some confusion and that would certainly call for
documented clarification.
 
> Procedural
> ----------
> 
> The election for this Council and its aftermath shows that we 
> are not sure how to handle a situation in which it appears a 
> candidate will not be able to serve if elected.  As a more 
> extreme example than the one we faced this time, suppose a 
> candidate resigns or is suspended.  I am still not sure, for 
> example, who are actually Council members right now.

The current council is located on the Council page.
http://www.gentoo.org/proj/en/council/

Flameeyes did send an email, that vapier resent for those who didn't get it,
where flameeyes agreed that jokey would be his proxy while he focused on
getting better and getting back to Gentoo work.

In the past we have had Council members leave and be replaced, though I
don't see the policy for that. Perhaps that should be included in the
discussion of what to do when a Council member, even if they have a proxy,
is away for an extended period or undetermined period of time.

Maybe I've shed some insight, maybe I've confused some of you more, however
I think these are good topics for discussion in the upcoming Council
meeting.

Kind regards,
Christina Fullam
Gentoo Developer Relations Lead | Gentoo Public Relations 


-- 
gentoo-dev@gentoo.org mailing list



  reply	other threads:[~2007-10-01 14:47 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-01  5:30 [gentoo-dev] Monthly Gentoo Council Reminder for October Mike Frysinger
2007-10-01 13:15 ` Ferris McCormick
2007-10-01 14:33   ` Chrissy Fullam [this message]
2007-10-01 21:34     ` Chris Gianelloni
2007-10-01 22:12     ` [gentoo-dev] " Duncan
2007-10-02  0:38       ` Chris Gianelloni
2007-10-02  9:00         ` Duncan
2007-10-02 10:20   ` [gentoo-dev] " Mike Frysinger
2007-10-01 21:54 ` Jorge Manuel B. S. Vicetto
2007-10-02  0:34   ` Chris Gianelloni
2007-10-02  2:08     ` Jorge Manuel B. S. Vicetto
2007-10-02  8:51       ` [gentoo-dev] " Steve Long
2007-10-02 10:17         ` Mike Frysinger
2007-10-02 19:23       ` [gentoo-dev] " Chris Gianelloni
2007-10-02 19:35         ` Chris Gianelloni
2007-10-02 10:21   ` Mike Frysinger
2007-10-02  9:15 ` Dennis Nienhüser
2007-10-09 22:32 ` Wernfried Haas
2007-10-11 10:00 ` [gentoo-dev] New projects (was: Monthly Gentoo Council Reminder...) Torsten Veller
2007-10-11 13:46   ` Alec Warner
2007-10-11 14:06     ` [gentoo-dev] New projects Doug Goldstein
     [not found]       ` <b41005390710111845q2218c810rbba949c9ce3db9b6@mail.gmail.com>
2007-10-12  2:10         ` Alec Warner
2007-10-12  2:54           ` Doug Goldstein
2007-10-12  6:52             ` Roy Marples
2007-10-12 10:59               ` Richard Freeman
2007-10-12 10:39             ` Alec Warner
2007-10-12 11:17           ` Petteri Räty
2007-10-12 13:55             ` Alec Warner
  -- strict thread matches above, loose matches on Subject: below --
2009-10-01  5:30 [gentoo-dev] Monthly Gentoo Council Reminder for October Mike Frysinger
2008-10-01  5:30 Mike Frysinger
2008-10-09 14:25 ` Donnie Berkholz
2008-10-09 18:55   ` Ciaran McCreesh
2008-10-09 19:11     ` Zac Medico
2008-10-09 19:16       ` Ciaran McCreesh
2008-10-09 19:22         ` Andrew Gaffney
2008-10-10  7:02     ` Alec Warner
2006-10-01  6:18 Mike Frysinger
2006-10-03 13:28 ` Mike Frysinger

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=800B72070D0242638ECF9900D0D3C847@draco2 \
    --to=musikc@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