All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Andrew Jeffery" <andrew@aj.id.au>
To: "Patrick Williams" <patrick@stwcx.xyz>,
	"OpenBMC List" <openbmc@lists.ozlabs.org>
Subject: Re: Upcoming TOF elections
Date: Mon, 10 Jan 2022 12:11:49 +1030	[thread overview]
Message-ID: <eacc4cdf-467e-4f98-8254-a530c1145203@www.fastmail.com> (raw)
In-Reply-To: <70ab9923-a976-46b0-8ec3-bbdd689c50a8@www.fastmail.com>



On Mon, 10 Jan 2022, at 12:09, Andrew Jeffery wrote:
> On Sat, 8 Jan 2022, at 04:41, Patrick Williams wrote:
> ...
>> The most important data that people will want to see is the list of individuals
>> who qualify for voting in the upcoming election.  The current draft (for
>> approval with issue #9) is found here[4].
> ...
>> 4. https://github.com/williamspatrick/openbmc-tof-elections/blob/main/2022H1/rollcall.json
>
> How are the following terms derived?
>
> * highly-productive
> * active
> * emertius (sic? emeritus?)
>
>  I didn't see mention of these terms in the tof-voters patches.
>
> Maybe I didn't read the associated documentation closely enough?

Ah, as soon as I send that I see [1]. Still, it defines 'Normal' and 'Highly-Productive' but not 'active' and 'emertius'.

[1] https://gerrit.openbmc-project.xyz/c/openbmc/docs/+/50202/1/tof/membership-and-voting.md

  reply	other threads:[~2022-01-10  1:42 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-07 18:11 Upcoming TOF elections Patrick Williams
2022-01-10  1:39 ` Andrew Jeffery
2022-01-10  1:41   ` Andrew Jeffery [this message]
2022-01-10 14:25     ` Patrick Williams
2022-01-14 22:16 ` Patrick Williams
2022-01-14 22:31   ` TOF Nominations Patrick Williams
2022-01-19 23:30     ` Andrew Jeffery
2022-01-24 19:56     ` Ed Tanous
2022-01-26 11:10       ` Lei YU
2022-01-28 21:10         ` Patrick Williams
2022-01-29  0:27     ` Terry Duncan
2022-02-07 17:36       ` Khetan, Sharad
2022-01-15  3:09   ` Upcoming TOF elections Patrick Williams
2022-02-14 23:01 ` Patrick Williams

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=eacc4cdf-467e-4f98-8254-a530c1145203@www.fastmail.com \
    --to=andrew@aj.id.au \
    --cc=openbmc@lists.ozlabs.org \
    --cc=patrick@stwcx.xyz \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.