From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gentoo-project+bounces-3782-garchives=archives.gentoo.org@lists.gentoo.org>
Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80])
	by finch.gentoo.org (Postfix) with ESMTP id C775613877A
	for <garchives@archives.gentoo.org>; Tue,  1 Jul 2014 19:10:39 +0000 (UTC)
Received: from pigeon.gentoo.org (localhost [127.0.0.1])
	by pigeon.gentoo.org (Postfix) with SMTP id A16F9E09F3;
	Tue,  1 Jul 2014 19:10:37 +0000 (UTC)
Received: from mail-vc0-f172.google.com (mail-vc0-f172.google.com [209.85.220.172])
	(using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits))
	(No client certificate requested)
	by pigeon.gentoo.org (Postfix) with ESMTPS id 0844AE08A5
	for <gentoo-project@lists.gentoo.org>; Tue,  1 Jul 2014 19:10:36 +0000 (UTC)
Received: by mail-vc0-f172.google.com with SMTP id hy10so9357890vcb.31
        for <gentoo-project@lists.gentoo.org>; Tue, 01 Jul 2014 12:10:36 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20120113;
        h=mime-version:sender:in-reply-to:references:date:message-id:subject
         :from:to:content-type;
        bh=Wc7yl99H+MXaM7w4+jwpsClOOV0oGDQrGlE8QDFtUuE=;
        b=JefE51Am5sqq01eOsvoFc9HasWUAxUrJbn3gMes/IdPa8yJ09zZ/3Umu/LBlTrYZ+F
         dx1YKAmP3YwW3gV2YCqxKGDShYX6p1kJnd8Ciocogb368huus2QnU6F3fnYQsOTGNs+W
         kKGHyWCIbfRWlS4vQwn4f4eV815e60rOTFvzPILv5wS/2DlznkiPo+rxV9YRyJV+QZlw
         iuE135CgWnLAw0rNdVc0vmHS3D5fFE28WeOAMKqNjR2foAadqxxnHQhV/YX8k5ZegOxL
         m2K4KbV956fr3344BtXTaP5TLmDDYEkTZUIK81xNQYv4T9aM1LVX+gbufR23jsU1zww0
         GGKQ==
Precedence: bulk
List-Post: <mailto:gentoo-project@lists.gentoo.org>
List-Help: <mailto:gentoo-project+help@lists.gentoo.org>
List-Unsubscribe: <mailto:gentoo-project+unsubscribe@lists.gentoo.org>
List-Subscribe: <mailto:gentoo-project+subscribe@lists.gentoo.org>
List-Id: Gentoo Project discussion list <gentoo-project.gentoo.org>
X-BeenThere: gentoo-project@lists.gentoo.org
Reply-To: gentoo-project@lists.gentoo.org
MIME-Version: 1.0
X-Received: by 10.58.219.194 with SMTP id pq2mr1559262vec.71.1404241836261;
 Tue, 01 Jul 2014 12:10:36 -0700 (PDT)
Sender: freemanrich@gmail.com
Received: by 10.52.72.19 with HTTP; Tue, 1 Jul 2014 12:10:35 -0700 (PDT)
In-Reply-To: <53B2FE38.7040508@gentoo.org>
References: <539BD2E2.7030803@gentoo.org>
	<cf579aa9-4b1d-4c56-96cc-ac12a44f63f8@email.android.com>
	<1757239.UAu395ci7F@kailua>
	<53B2E4CA.1080408@gentoo.org>
	<CAGfcS_=D=aP_Y2s9Pbwsm1=rr=C7KfEPZVmOt3uaoUeynGB1YA@mail.gmail.com>
	<53B2FE38.7040508@gentoo.org>
Date: Tue, 1 Jul 2014 15:10:35 -0400
X-Google-Sender-Auth: DA-lUYubO55aRetdhUvHou3sRsA
Message-ID: <CAGfcS_mJSFLDidDQ2sC+0JtOv5TuuyhBo1J6gciistVcUcYfOA@mail.gmail.com>
Subject: Re: [gentoo-project] Gentoo Council 2014 / 2015 election
From: Rich Freeman <rich0@gentoo.org>
To: gentoo-project@lists.gentoo.org
Content-Type: text/plain; charset=UTF-8
X-Archives-Salt: 821d57e4-849e-432c-a63b-9bc8f9873192
X-Archives-Hash: c3ca69799c4aa72f743c4906b8ef74d9

On Tue, Jul 1, 2014 at 2:30 PM, hasufell <hasufell@gentoo.org> wrote:
> So you are basically saying a conflict of interest can happen and when
> it does, everyone will actually realize it and also act appropriately.
>

Well, if people don't do that, then you're up the creek no matter what
system of governance you come up with.

SOMEBODY has to make the final decision, and they can always have a
conflict of interest.

Unless half the council is in on the original offense, it really only
makes a difference if it is a close call.  So, avoid doing things that
would tick off half the council and you should be fine.  :)

This is no different than a majority of trustees being able to sell
the Foundation to your least favorite IT vendor.  If you're going to
vote a bunch of untrustworthy individuals into office, then you might
not like the result.

I don't see a practical alternative.  The kinds of skills that you
need to be a decent Trustee, Council member, or Comrel member overlap
significantly.  We aren't exactly a huge organization.  So, we either
have to accept overlap, or put people into these roles that we might
otherwise not want to.  There is also QA and Infra to consider - do we
not allow anybody to be on more than one of these teams?

Ridh