DomainKey-Signature: a=rsa-sha1; c=nofws; d=toastin.space; h=subject:to
	:references:cc:from:message-id:date:mime-version:in-reply-to
	:content-type:content-transfer-encoding; q=dns; s=ml; b=c9+jZ4Q0
	MLVO3ZtjmV2RKVPLMAajnWGCTVfldwhUBYrhSOPsyLZSxcTxUnSnoujpE2P4exyS
	kG63K2hl+Itnn1RfGYC0tTvetjPRGBAvsMOy2Lc8ao4VCRUnsvGcsodt1UD9anPW
	SEP4+Hw3Fhl/hWnFwpMniABKa2qbvEJctQixmf0wBRRB0qa5FEqwCP1/5p+ZEQYR
	hvIK1regfeuHhRcV0bl7dNPTS40RL/o4+IhtcWXv6Kf1xkDfcqie9fDsaJ903NVW
	b1iO/CQoU2Uu0CflYxycYz5KkgKoz1jfaGvJttkEfleM47J5D316DxgxEAQTb3GB
	pMMG91Lrgv9yNw==
Subject: Re: [alpine-devel] [PATCH 2/2] Rework the base team description
To: alpine-devel@lists.alpinelinux.org
References: <20190409050210.20217-3-sir@cmpwn.com>
 <F2137E1D-EF43-4109-9015-17199BBFC2D8@yahoo.com>
 <20190409133140.GB21799@homura.localdomain>
 <6B5C3246-C8D8-4CE8-8A56-8ECBADE4654B@yahoo.com>
 <20190409175838.GE21799@homura.localdomain>
 <20190410203624.35719561@ncopa-desktop.copa.dup.pw>
 <9ab6d193-4671-1786-1214-65daad959aed@toastin.space>
 <20190411152723.32e38e16@ncopa-desktop.copa.dup.pw>
 <f3449b8c-2e02-2068-da26-6bd396ca0dda@toastin.space>
 <20190411172622.3978cc04@ncopa-desktop.copa.dup.pw>
 <20190411152735.GB25237@homura.localdomain>
Cc: Drew DeVault <sir@cmpwn.com>
From: Chloe Kudryavtsev <toast@toastin.space>
Message-ID: <57141430-858c-6afd-ecfb-891a1817c6f5@toastin.space>
Date: Thu, 11 Apr 2019 11:34:38 -0400
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:67.0) Gecko/20100101
 Thunderbird/67.0
Precedence: list
MIME-Version: 1.0
In-Reply-To: <20190411152735.GB25237@homura.localdomain>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 7bit

On 4/11/2019 11:27 AM, Drew DeVault wrote:
> I've also been unsure about forced rotation. Why don't we compromise and
> eliminate the restriction about serving consecutive terms?

You actually brought up one of the reason forced rotation has to exist 
in one of our talks previously.
Allow me to quote myself with the relevant examples:

On 4/11/2019, I wrote:
> This is also why you cannot be re-elected immediately.
> When elections are coming up, the person about to end their term would have significant amounts of influence, and if they were bad they could use those to try to pressure people into re-electing them.
> Similarly, a good person that's about to end their term would be vulnerable to bad external actors pressuring people into not re-electing them (for instance, someone could go through everything you have ever said, and tried to dig up something embarrassing).
> Both of these types of events are unneeded strain on the project, and both are effectively eliminated by enforcing a one-year-break between being in power. 

If we were to eliminate the restriction about serving consecutive terms, 
we would have to make sure we are prepared for well-known real scenarios 
like the above.
I think forced rotation is an adequate method of preventing them 
inherently, and also gives the base member the opportunity to see the 
world from the position of everyone else - refreshing their perspective 
and enabling them to serve better.

If we can come out with ways to have both of the above that is not 
forced rotation, I would be onboard, but I'm not really seeing any 
acceptable approach.
Do you have one? :)


---
Unsubscribe:  alpine-devel+unsubscribe@lists.alpinelinux.org
Help:         alpine-devel+help@lists.alpinelinux.org
---