openbmc.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Patrick Williams <patrick@stwcx.xyz>
To: OpenBMC List <openbmc@lists.ozlabs.org>
Subject: Upcoming TOF elections
Date: Fri, 7 Jan 2022 12:11:30 -0600	[thread overview]
Message-ID: <YdiCUiwh1iD4ycr8@heinlein> (raw)

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

Greetings,

According to this document[1], the TOF should be holding elections starting on
March 1st for seats starting April 1st.  There are activities that the current
TOF is expected to do in order for those elections to be able to be held:

* Jan 15th: Current TOF must publish a list of eligible voting members.
* Jan 30th:	Nominations (self or peer) for TOF seats must be sent to the mailing
            list.
* Jan 30th:	Developers disputing membership eligibility must submit a petition
            request to the current TOF.
* Feb 15th:	Current TOF must publish a final list of eligible voting members
            and upcoming candidates for TOF seats

Since this is the first election there are some tools that needed to be written
in order to accomplish these tasks.  I've now finished the initial draft of the
tools necessary to accomplish the Jan 15th deadline[2].

There are also some process items that the TOF is suppose to agree / publish.
For those I have opened 3 TOF proposals for approval[3]:

- #7: Set "Highly Productive" threshold to 95 points for 2021H2
- #8: Accept tools for election data collection.
- #9: Accept 2022H1 rollcall

TOF members will need to move relative fast at deciding on these in order to
accomplish the Jan 15th deadline.  Please voice any concerns you may have on any
of the TOF proposals to the mailing list (or a TOF member) quickly.

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].  If you are not found on the final
list and believe that you should be you may petition by Jan 30th by opening a
separate issue to the issue list[3] with the evidence for your inclusion.


1. https://github.com/openbmc/docs/blob/master/tof/membership-and-voting.md
2. https://gerrit.openbmc-project.xyz/c/openbmc/openbmc-tools/+/50200
3. https://github.com/openbmc/technical-oversight-forum/issues
4. https://github.com/williamspatrick/openbmc-tof-elections/blob/main/2022H1/rollcall.json

-- 
Patrick Williams

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

             reply	other threads:[~2022-01-07 18:12 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-07 18:11 Patrick Williams [this message]
2022-01-10  1:39 ` Upcoming TOF elections Andrew Jeffery
2022-01-10  1:41   ` Andrew Jeffery
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=YdiCUiwh1iD4ycr8@heinlein \
    --to=patrick@stwcx.xyz \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).