From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gentoo-project+bounces-8016-garchives=archives.gentoo.org@lists.gentoo.org>
Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80])
	(using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
	(No client certificate requested)
	by finch.gentoo.org (Postfix) with ESMTPS id E080C138334
	for <garchives@archives.gentoo.org>; Mon,  2 Jul 2018 15:03:42 +0000 (UTC)
Received: from pigeon.gentoo.org (localhost [127.0.0.1])
	by pigeon.gentoo.org (Postfix) with SMTP id A779DE09C6;
	Mon,  2 Jul 2018 15:03:40 +0000 (UTC)
Received: from mail-oi0-x22e.google.com (mail-oi0-x22e.google.com [IPv6:2607:f8b0:4003:c06::22e])
	(using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits))
	(No client certificate requested)
	by pigeon.gentoo.org (Postfix) with ESMTPS id 70659E09C4
	for <gentoo-project@lists.gentoo.org>; Mon,  2 Jul 2018 15:03:40 +0000 (UTC)
Received: by mail-oi0-x22e.google.com with SMTP id w126-v6so9660512oie.7
        for <gentoo-project@lists.gentoo.org>; Mon, 02 Jul 2018 08:03:40 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20161025;
        h=sender:date:from:to:subject:message-id:mail-followup-to:references
         :mime-version:content-disposition:in-reply-to:user-agent;
        bh=9ViwDTy5vlqzeLEN7EY+HIGBLt2YTj1dAYbktwBHHvc=;
        b=jhWIkhTl0lt5sJrrxQIgU6TOg8FwM/CwlGJQ4iiMEu91GfGmlf1EJAlWOH5lEJ1+x6
         t6VVQ2onFx2qCRGORIWPe17akNO37EC8TAYt2yoiixj+R2BqYYlH7AWNqSDI4ofwTYUS
         pSWX9AcsJQqHKfk0zDN9XE5/DiXP3J397AoFaq5CNR0Hj8RFylHw8Xd+DYVNxT0d3+En
         6LAv5ndXhsJik0X19kIFTxlKsNwTnBwbQFy/hrL9gM8c4kyfBewp6OpsZkocu7rMkE9t
         CPECq5X1vs1rrKkgbVAX/ux2afEEFth70AhUSG6yeA1QMNqPBU5cB6CFk+4naqLxk8lJ
         8MMw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=1e100.net; s=20161025;
        h=x-gm-message-state:sender:date:from:to:subject:message-id
         :mail-followup-to:references:mime-version:content-disposition
         :in-reply-to:user-agent;
        bh=9ViwDTy5vlqzeLEN7EY+HIGBLt2YTj1dAYbktwBHHvc=;
        b=tL7tSc4YYionA9FoF5TVBBpc96Zz9rULMrCVQFp07EoXJC5AY6/rp0cLZaUq8ciRnr
         H2Y1DRDRQkb8Uydj7LKLfxheVzUwNRys8yae3erIe47DEfvZGFcO68qKRI64d4e23xPP
         Tfi5VqQKvCvHQHi0KqKARTDTdVmP+Xt4r2wwIVLeAKqDIDQL8UwieMwh3qwezUL8Cugl
         eUdQ1Dm5PO83uOwR5eLuVUxslWNuCTAjUh0AGECrsyadVejphooIf857K/sEsQ7lS89Q
         P4Hp2aWSQp5rulHEWrnFCDyLFLZhMBFJ5aViXTpY2V4jRAScCgYnLZIMeyO8D2/DH72c
         /CWw==
X-Gm-Message-State: APt69E25UqWpHB87JllfatCsTRieNUlTeeRzhA7iTYtD0KCYP6E5u0TP
	jdURZWja6xzZNri0KwGsGRR6qw==
X-Google-Smtp-Source: AAOMgpfQJmTPqEUFa3lLs1hInA6w220YS72LBjaPuQn120q7zycbiHYBHxsR8EFyKU9hIz706mQyhA==
X-Received: by 2002:aca:728f:: with SMTP id p137-v6mr17017662oic.335.1530543819391;
        Mon, 02 Jul 2018 08:03:39 -0700 (PDT)
Received: from linux1 (cpe-66-68-34-247.austin.res.rr.com. [66.68.34.247])
        by smtp.gmail.com with ESMTPSA id u5-v6sm8075428otc.1.2018.07.02.08.03.38
        for <gentoo-project@lists.gentoo.org>
        (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256);
        Mon, 02 Jul 2018 08:03:38 -0700 (PDT)
Sender: William Hubbs <w.d.hubbs@gmail.com>
Received: (nullmailer pid 16011 invoked by uid 1000);
	Mon, 02 Jul 2018 15:03:37 -0000
Date: Mon, 2 Jul 2018 10:03:37 -0500
From: William Hubbs <williamh@gentoo.org>
To: gentoo-project@lists.gentoo.org
Subject: Re: [gentoo-project] Gentoo Council nominee 2018/19 questions
Message-ID: <20180702150337.GA15912@linux1.home>
Mail-Followup-To: gentoo-project@lists.gentoo.org
References: <1529997071.2250.6.camel@gentoo.org>
 <1530087907.849.13.camel@gentoo.org>
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
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature"; boundary="k+w/mQv8wyuph6w0"
Content-Disposition: inline
In-Reply-To: <1530087907.849.13.camel@gentoo.org>
User-Agent: Mutt/1.9.4 (2018-02-28)
X-Archives-Salt: 2bdb51f4-873f-48a1-8c0a-1c39d93afe55
X-Archives-Hash: 0ac41feeda7a23684c8a76ebdb47e188


--k+w/mQv8wyuph6w0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Wed, Jun 27, 2018 at 10:25:07AM +0200, Micha=C5=82 G=C3=B3rny wrote:
> Three more questions from me:
>=20
>=20
> 1. Do you believe that Council members should respect the requests of
> the developer community even if they disagree with them?  Or should
> Council members decide based on their own judgment of arguments
> presented?
>=20
> Example: there's a heated debate, and the majority of respondents
> request that X is implemented.  However, after reading all the arguments
> you don't think that X is a good idea but you haven't managed to
> convince others.  Would you vote for X (as your electorate demands)
> or against it (as you believe is better for the distro)?
=20
In my experience, most of the time, things are not as clear-cut as
this; there can be many things to consider.

For example, suppose that the people demanding x are not part of the
team that maintains the packages that would make x happen, and suppose
that making x happen requires custom patches which get rejected by
upstream developers.  In this case, is it really better to force
maintainers to do custom work or vote against x?

I think this type of decision should be made on a case-by-case basis.

> 2. Do you believe that the Council should proactively research the state
> of affairs and make decisions whenever they believe the direction
> of the distribution needs to be adjusted?  Or should it be passive
> and avoid involvement unless developers explicitly request Council's
> intervention?
=20
 I feel that most of the time the council should intervene only at the
 request of developers. The developers know their packages better than
 we do, and I think we should trust them. Innovation tends to come from
 the developers, not the council.

> 3. Do you believe the developer community should hold the power
> to veto or dissolve the Council at any point?  Provided there's a global
> developer vote agreeing on that.
=20
 Yes, the developers already have the ability to disband the council if
 they want to do this. They could replace glep 39 at any point.

Also, I am not opposed to the idea of a general resolution.

William


--k+w/mQv8wyuph6w0
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature

-----BEGIN PGP SIGNATURE-----

iF0EARECAB0WIQTVeuxEZo4uUHOkQAluVBb0MMRlOAUCWzo+xAAKCRBuVBb0MMRl
OOzbAKCMm9JMMBr1EU6F1AIVmr6/AtUGnACcDr9Q4xDkzDp1aHgiU38D8eR3X9M=
=QTAq
-----END PGP SIGNATURE-----

--k+w/mQv8wyuph6w0--