From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: 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 5B23B158013 for ; Sat, 28 Aug 2021 19:07:42 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id DEC28E0867; Sat, 28 Aug 2021 19:07:40 +0000 (UTC) Received: from mail-ot1-f43.google.com (mail-ot1-f43.google.com [209.85.210.43]) (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 C3451E0855 for ; Sat, 28 Aug 2021 19:07:40 +0000 (UTC) Received: by mail-ot1-f43.google.com with SMTP id v33-20020a0568300921b0290517cd06302dso12504215ott.13 for ; Sat, 28 Aug 2021 12:07:40 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=8ix+Js3BAuysNpwJpTgHTE1Ci5XGA2SGwalNZZEuV+I=; b=Uh+RTnyYDuxSO2jbasJlx0wZcvDBxk1D3a+6P0+SeTu5u5CBy4kIZCdKaa/3cr10rD wXq90CAF3nSMW5cgMyjU7EUnhDtalZn14htxZGJqi3F2RvPX8pwW3L2Q5FoY5CWKyuUx Tpg1PKV+Uq07ipwfcfkZNQX6X3z4PFgYdPzVs+YFwtGmA2kkmRzKsx0AyM33Qo8VWisZ fvurRLXbBSs7C/0Pd6tXtbYdGPNxlRhOmcy5fxSfGOwjZ75VZ+ijK/F42rPbWCh1lhtO w9iNa+k1M7PsDukRtFV+cg8EN7VUGv7/DmTOWLZUpaxSdYcUWlgyAroKsiJ7b4raBAUI D6kQ== X-Gm-Message-State: AOAM5321VCHRFLTTt+ezEJbmZNpC8iSacjNZnfG1BLKEdsq2GWwotIvX lxNabl2jji8ksm47rI4du1eDxARCUbpM8Fx6us8Gy9Hj X-Google-Smtp-Source: ABdhPJyIUbICFJ34lyP9Jmd+ZOmCVdS+AsRuLnwsrnPoXfQ6+pxkRtrbly6evDhi+RNeTzqHBjGedAY5bXfTiwx6PBY= X-Received: by 2002:a05:6830:411f:: with SMTP id w31mr13999657ott.338.1630177659666; Sat, 28 Aug 2021 12:07:39 -0700 (PDT) Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Project discussion list X-BeenThere: gentoo-project@lists.gentoo.org Reply-To: gentoo-project@lists.gentoo.org X-Auto-Response-Suppress: DR, RN, NRN, OOF, AutoReply MIME-Version: 1.0 References: In-Reply-To: From: Rich Freeman Date: Sat, 28 Aug 2021 15:07:28 -0400 Message-ID: Subject: Re: [gentoo-project] [pre-GLEP] Secrecy-respecting voting mechanism for Gentoo projects To: gentoo-project Content-Type: text/plain; charset="UTF-8" X-Archives-Salt: b4460759-13f8-4e5e-8197-5f749b3ab478 X-Archives-Hash: e9c689e35d36bf8aae66f7ee4a1b5ada On Sat, Aug 28, 2021 at 3:01 PM Aaron Bauman wrote: > > Given what we have seen in the security election this year, what > determines *who* can start an election? Maybe some clarity in GLEP 39? > IMO if there is really a dispute over something like this for a project election there are some serious issues. However, if we MUST have rules I'd suggest that it is the responsibility of the project lead to call for the next project lead election. If there is no lead or if the lead has failed to do so in the last 12 months then anybody should be able to do so. Obviously it is best to just nudge the lead or work via consensus. IMO, formal ballots/etc for project leads is also overkill. I get the value for Council/Trustees, but I'm not sure it really adds value for regular projects. -- Rich