public inbox for gentoo-project@lists.gentoo.org
 help / color / mirror / Atom feed
From: Alec Warner <antarus@gentoo.org>
To: gentoo-nfp <gentoo-nfp@lists.gentoo.org>
Cc: gentoo-project <gentoo-project@lists.gentoo.org>,
	"Michał Górny" <mgorny@gentoo.org>,
	"Gentoo Elections" <elections@gentoo.org>
Subject: Re: [gentoo-project] Re: [gentoo-nfp] Gentoo Foundation: A second election
Date: Mon, 23 Aug 2021 16:04:27 -0700	[thread overview]
Message-ID: <CAAr7Pr_AaL7EK0k3cmMY3FYDFMyT+TVhtxwzTu4hySJNe_iBEQ@mail.gmail.com> (raw)
In-Reply-To: <CAGfcS_=g4iSTmeKArKtc0hzoPFv6vwXpV0ujeF8zn=6dfr=g1g@mail.gmail.com>

On Mon, Aug 23, 2021 at 8:22 AM Rich Freeman <rich0@gentoo.org> wrote:
>
> On Mon, Aug 23, 2021 at 10:42 AM Ulrich Mueller <ulm@gentoo.org> wrote:
> >
> > If Trustees can fill the vacancies, then there's no point in omitting
> > _reopen_nominations. They could still pick any candidates from below.
> >
> > So, I think the procedure as announced by antarus makes sense.
>
> If the election itself fails to actually elect anybody, they can
> actually appoint anybody they wish I believe.  (ie, if the reopen
> option wins they could just appoint drobbins or a cousin or whatever,
> though obviously it would make more sense to just appoint somebody on
> the ballot, preferably the one with the most votes.)

I don't believe it is permissible to appoint 'a cousin.' Trustees must
be Gentoo Foundation members and probably also must be active
developers (per section 5.2 of the bylaws.)

>
> They actually can do that right now without another election, though I
> do think the course they're taking is a sensible one.

It seems rather pointless to add a reopen_nominations option to the
election, then have a tie and not reopen_nominations. Hence my
preferences for this solution.

>
> We could spend a lot of time debating the ideal election process, but
> in the end if you have only three volunteers for three slots, it is a
> bit of a moot argument...

This is my biggest challenge overall; the community spends significant
time debating the 'best' way to do some things, but honestly I'm not
sure we always need the 'best' way; we just need *a* way. If the
crappy way and the best way generate the same outcome; I'm not super
eager to devote hours and hours of discussion to generate the same
output; I think there are better ways to spend our time.

-A

>
> --
> Rich
>


  reply	other threads:[~2021-08-23 23:04 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-23  3:11 [gentoo-project] Gentoo Foundation: A second election Alec Warner
2021-08-23  3:11 ` [gentoo-project] " Alec Warner
2021-08-23  5:26   ` Alice
2021-08-23  6:35 ` [gentoo-project] Re: [gentoo-nfp] " Michał Górny
2021-08-23 12:00   ` Ulrich Mueller
2021-08-23 12:27     ` Michał Górny
2021-08-23 14:42       ` Ulrich Mueller
2021-08-23 15:22         ` Rich Freeman
2021-08-23 23:04           ` Alec Warner [this message]
2021-08-23 23:19             ` Rich Freeman
2021-08-23 18:09         ` Jorge Manuel B. S. Vicetto
2021-08-23 18:17           ` Rich Freeman
2021-08-23 14:20 ` Aaron Bauman
2021-08-23 14:22   ` Rich Freeman
2021-08-23 17:04   ` Ulrich Mueller
2021-08-23 17:06   ` David Seifert
2021-08-23 17:16   ` Michał Górny
2021-08-24 21:11   ` Andreas K. Huettel
2021-08-25 18:05   ` Matt Turner
2021-08-30  4:14 ` Robin H. Johnson
2021-08-30 11:27   ` Roy Bamford
2021-08-30 19:06   ` Jorge Manuel B. S. Vicetto
2021-08-30 19:13   ` David Abbott
2021-08-30 19:44     ` Ben Kohler

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAAr7Pr_AaL7EK0k3cmMY3FYDFMyT+TVhtxwzTu4hySJNe_iBEQ@mail.gmail.com \
    --to=antarus@gentoo.org \
    --cc=elections@gentoo.org \
    --cc=gentoo-nfp@lists.gentoo.org \
    --cc=gentoo-project@lists.gentoo.org \
    --cc=mgorny@gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox