[Development] New Chief Maintainer

André Somers andre at familiesomers.nl
Fri May 20 05:43:15 CEST 2022

Hi Volker,

On 19-05-2022 22:42, Volker Hilsheimer wrote:
>> On 18 May 2022, at 11:23, André Somers <andre at familiesomers.nl> wrote:
>> On 18-05-2022 11:19, André Somers wrote:
>>> As I understand it [1], this needs a formal vote. However, the QUIP 
>>> does not specify a full procedure. I would suggest:
>> And then I forget the actual link:
>> https://quips-qt-io.herokuapp.com/quip-0002.html#how-to-become-chief-maintainer
> Thanks André.
> The QUIP asks for a simple-majority vote of all Maintainers. Either way, let’s see what other nominations we get.
> May I propose that until end of Wednesday 25th, Maintainers can nominate other candidates (including themselves), and then we can have a vote amongst those candidates nominated (the simple majority is enough as per QUIP). The QUIP doesn’t explicitly require the candidate to be a Maintainer.
> If we have only one candidate by end of Wednesday, then we can use lazy consensus, i.e. as long as none of the maintainers object to the candidate, that candidate becomes chief maintainer. Although I’d expect that whoever has an objection to one candidate also nominates another candidate.

The procedure outlined in the linked QUIP is substantially different 
from the procedure outlined for becoming a Maintainer. The wording to me 
suggest we need an actual vote in this case, not a lazy consensus. The 
"simple majority" refers to the needed number of votes out of the quorum 
(simple majority meaning >50%), not the simplicity of the voting 
procedure IMO.

So no, I don't think a lazy consensus will do. And no, I don't think 
it's having an objection to a candidate means that you also know a good 
other candidate willing to take up the baton instead.



> Volker

More information about the Development mailing list