X-Original-To: alpine-devel@lists.alpinelinux.org Received: from pb-smtp2.pobox.com (pb-smtp2.pobox.com [64.147.108.71]) by lists.alpinelinux.org (Postfix) with ESMTP id A5DEEF8146D for ; Thu, 18 Apr 2019 22:07:39 +0000 (UTC) Received: from pb-smtp2.pobox.com (unknown [127.0.0.1]) by pb-smtp2.pobox.com (Postfix) with ESMTP id CE544139AE8 for ; Thu, 18 Apr 2019 18:07:38 -0400 (EDT) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=pobox.com; h=subject:to :references:from:message-id:date:mime-version:in-reply-to :content-type:content-transfer-encoding; s=sasl; bh=iLNL3xN/r+oD wYLED8g9ED1kiC8=; b=JNjXP7epE8UwPtvgFNZ1Oqfk/3JUMrmtzlGZxElwFYVq UAsMaWlAIVKYv0eshHWJYqwIJ1dzvYRbl7FE4bEeIB/tbXgMROz+yB1cY5H4SFK6 wmkELLtZiVbaLCaGjz2oLPWVy9m5YE1X+8rF3fPVHPXWg58tUesBrVzcwhcaBC0= Received: from pb-smtp2.nyi.icgroup.com (unknown [127.0.0.1]) by pb-smtp2.pobox.com (Postfix) with ESMTP id BC98A139AE7 for ; Thu, 18 Apr 2019 18:07:38 -0400 (EDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed; d=lohutok.net; h=subject:to:references:from:message-id:date:mime-version:in-reply-to:content-type:content-transfer-encoding; s=2018-11.pbsmtp; bh=amvN40RV54m72umzVDHBHntBytEn5IdfB8Z9TY71ZEg=; b=JCvs+mTckK5dHPA/ARlfz4N/otel5d22H8ssYchB8Zoajom6NG9mqLiM7Ikl1o0uqQM8Laq9H52ayFXOyyLmQoBMJNSSJvdPvPi6JArlZ6qXVUSZzags9pkB8gMwaG/Q/vOlDSX34fRdH4e1TWMmVpIWAfue49O0SCkp564izMQ= Received: from [10.0.0.75] (unknown [24.47.52.80]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by pb-smtp2.pobox.com (Postfix) with ESMTPSA id 0D4DB139AE6 for ; Thu, 18 Apr 2019 18:07:38 -0400 (EDT) Subject: Re: [alpine-devel] Stripping down the governance model proposal To: alpine-devel@lists.alpinelinux.org References: <20190415152330.GG1179@homura.localdomain> From: Allison Randal Message-ID: <0fdde07c-b505-fb2a-cff2-bba494c781e3@lohutok.net> Date: Thu, 18 Apr 2019 18:07:37 -0400 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.5.1 X-Mailinglist: alpine-devel Precedence: list List-Id: Alpine Development List-Unsubscribe: List-Post: List-Help: List-Subscribe: MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit X-Pobox-Relay-ID: 60A14BDA-6226-11E9-BE5C-DF19F34BB12D-44123303!pb-smtp2.pobox.com On 4/17/19 7:24 PM, Chloe Kudryavtsev wrote: > On 4/15/2019 11:23 AM, Drew DeVault wrote: > >> There is a general sense of dissatisfaction with the governance proposal >> under discussion. It's too big and makes a lot of changes at once. > > The issue with the dissatisfaction is that it reduces the odds of > passing it through. > If a proposal that fixes all the issues does not pass through, it fixes > no issues. > This is the other end of the spectrum. > It is simple to make a proposal that passes, but actually fixes nothing. > However, if a proposal that fixes nothing passes, nothing was fixed. > These two scenarios are effectively identical. There is a third possibility that's worse than those two: a proposal that fixes a large number of issues passes, but is generally not accepted by the community because they aren't comfortable with it. It becomes official, but no one respects or abides by it, and you effectively end up with no governance model at all, and a lot of confusion and disruption to the project. I can't say how likely that is to happen here, but it is definitely a common risk when considering such substantial changes. So, it's worth taking the time to carefully consider changes, make them incrementally, and ensure that the currently active governance body always leads changes to the governance model. Trust takes time. Allison --- Unsubscribe: alpine-devel+unsubscribe@lists.alpinelinux.org Help: alpine-devel+help@lists.alpinelinux.org ---