From: Patrick Williams <patrick@stwcx.xyz>
To: Andrew Jeffery <andrew@aj.id.au>
Cc: OpenBMC List <openbmc@lists.ozlabs.org>
Subject: Re: Upcoming TOF elections
Date: Mon, 10 Jan 2022 08:25:01 -0600 [thread overview]
Message-ID: <YdxBvR4ZbFn7WDJp@heinlein> (raw)
In-Reply-To: <eacc4cdf-467e-4f98-8254-a530c1145203@www.fastmail.com>
[-- Attachment #1: Type: text/plain, Size: 2573 bytes --]
On Mon, Jan 10, 2022 at 12:11:49PM +1030, Andrew Jeffery wrote:
>
>
> 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?)
It is quite probable that I've messed up spelling somewhere. I'll get to the
bottom of where. (Should be 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
It not in that change, but in the original part of the document:
https://github.com/openbmc/docs/blob/master/tof/membership-and-voting.md
> Membership is determined using data from the previous 6 months of development
> contributions. Using this data, the TOF will publish a list of Active Members
> of the two tiers. An individual who was an Active Member of a tier in the
> preceding 6 months, but does not qualify in the most recent 6 months, will be
> listed as an Member Emeritus for 6 months. Both Active and Emertius members
> are eligible for elections.
So more specifically there are the following states:
- Non-Member
- Emeritus Member
- Active Member - Normal Status
- Active Member - Highly Productive Status
Non-members are individuals who did not contribute enough points in either of
the last two 6 month periods. Emeritus members contributed enough in the
previous 6 month period to qualify, but not the current 6 month period.
Active members contributed enough in the 6 month period to qualify for
elections. Depending on the amount of their contributions they are either
"normal" or "highly productive".
In the roll-call JSON I used the following:
- Non-Members are left out.
- Emeritus should be "emeritus"
- Active Member - Normal Status is simply "active"
- Active and Highly Productive is "highly-productive"
--
Patrick Williams
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2022-01-10 14:25 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
2022-01-10 14:25 ` Patrick Williams [this message]
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=YdxBvR4ZbFn7WDJp@heinlein \
--to=patrick@stwcx.xyz \
--cc=andrew@aj.id.au \
--cc=openbmc@lists.ozlabs.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 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.