public inbox for gentoo-project@lists.gentoo.org
 help / color / mirror / Atom feed
From: Ulrich Mueller <ulm@gentoo.org>
To: gentoo-project@lists.gentoo.org, gentoo-dev@lists.gentoo.org
Cc: Michael Orlitzky <mjo@gentoo.org>
Subject: [gentoo-project] Re: [gentoo-dev-announce] Gentoo metastructure update (GLEP 39) voting now open - 7 days left
Date: Wed, 03 May 2023 08:58:54 +0200	[thread overview]
Message-ID: <uwn1p295d_-_@gentoo.org> (raw)
In-Reply-To: <d43987ddf5371b1b883cfe0b712e683baec62379.camel@gentoo.org> (Michael Orlitzky's message of "Tue, 02 May 2023 20:16:01 -0400")

[-- Attachment #1: Type: text/plain, Size: 1115 bytes --]

>>>>> On Wed, 03 May 2023, Michael Orlitzky wrote:

[Please keep this thread in -project.]

>> This is a friendly reminder that we're nearing (at the end of the day) 
>> the half-period for this election voting.

> My options are "yes" and "no" but there's no indication of what I'm
> saying yes/no to.

> I'd wager that "yes" means update the GLEP but I'd really rather have
> it in writing before voting.

Quoting from my original posting, Message-ID: <u354pabaq_-_@gentoo.org>
(you can see it on marc.info [1], our own archives are currently down):

| Voting for the update of the Gentoo metastructure document (GLEP 39)
| is now open. The election is named "metastructure-2023".

Not sure why you think they wouldn't be clear, but the options mean:

- "yes" means that you vote for the update of the Gentoo metastructure
  document (GLEP 39).

- "no" means that you vote against it.

- "blank" means blank ballot. (And let's not start a discussion whether
  a ballot with the word "blank" on it is blank. :)

Ulrich

[1] https://marc.info/?l=gentoo-project&m=168232784705569&w=2

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 507 bytes --]

  parent reply	other threads:[~2023-05-03  6:59 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-29  3:43 [gentoo-project] Council Meeting 2023-04-09: Call for Agenda Items John Helmert III
2023-03-29  5:14 ` Ulrich Mueller
2023-03-29  5:29 ` Ulrich Mueller
2023-03-29 14:41   ` Rich Freeman
2023-03-29 16:11     ` Ulrich Mueller
2023-04-10 17:37   ` [gentoo-project] Update of Gentoo metastructure document aka GLEP 39 (was: Re: Council Meeting 2023-04-09: Call for Agenda Items) Ulrich Mueller
2023-04-10 18:48     ` Robin H. Johnson
2023-04-10 21:28       ` [gentoo-project] Update of Gentoo metastructure document aka GLEP 39 Ulrich Mueller
2023-04-11 16:24         ` Ulrich Mueller
2023-04-15  9:33           ` Roy Bamford
2023-04-16  8:24     ` [gentoo-project] " Ulrich Mueller
2023-04-24  9:18       ` [gentoo-project] Gentoo metastructure update (GLEP 39) voting now open Ulrich Mueller
2023-04-25  7:15         ` Ulrich Mueller
2023-04-30 16:30         ` [gentoo-project] Re: [gentoo-dev-announce] Gentoo metastructure update (GLEP 39) voting now open - 7 days left Jorge Manuel B. S. Vicetto
     [not found]           ` <d43987ddf5371b1b883cfe0b712e683baec62379.camel@gentoo.org>
2023-05-03  6:58             ` Ulrich Mueller [this message]
2023-05-03 11:59               ` Michael Orlitzky
2023-03-31 17:02 ` [gentoo-project] Re: Council Meeting 2023-04-09: Call for Agenda Items Andreas K. Huettel

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=uwn1p295d_-_@gentoo.org \
    --to=ulm@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    --cc=gentoo-project@lists.gentoo.org \
    --cc=mjo@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