From: "Bird, Tim" <Tim.Bird@sony.com>
To: Laura Abbott <laura@labbott.name>,
"tech-board-discuss@lists.linuxfoundation.org"
<tech-board-discuss@lists.linuxfoundation.org>,
"ksummit-discuss@lists.linuxfoundation.org"
<ksummit-discuss@lists.linuxfoundation.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [Ksummit-discuss] Linux Foundation Technical Advisory Board Elections -- voting procedures
Date: Mon, 27 Jul 2020 22:43:45 +0000 [thread overview]
Message-ID: <CY4PR13MB1175DCFB41F2FB2F47E43A9CFD720@CY4PR13MB1175.namprd13.prod.outlook.com> (raw)
In-Reply-To: <ade3420c-89fd-bed0-52e3-a0396eaeda2d@labbott.name>
> -----Original Message-----
> From: Laura Abbott
>
> On behalf of the Linux Foundation Technical Advisory Board (TAB), I'd
> like to announce the voting procedures for the 2020 TAB elections.
> The pool of eligible voters will consist of the following:
>
> 1) All attendees of the Linux Plumbers conference (i.e. kernel summit)
>
> 2) Anyone who is not a kernel summit attendee will also be eligible to
> vote if the following criteria are met:
> -- There exists three kernel commits in a mainline or stable released
> kernel that
> --- Have a commit date in the year 2019 or 2020
> --- Contain an e-mail address in one of the following tags or merged
> tags (e.g. Reviewed-and-tested-by)
> ---- Signed-off-by
> ---- Tested-by
> ---- Reported-by
> ---- Reviewed-by
> ---- Acked-by
>
> We will be using the electronic voting method that we used in 2019. All
> Linux Plumbers Attendees will automatically receive a ballot. Anyone
> who is otherwise eligible to vote should e-mail
> tab-elections@lists.linuxfoundation.org to request a ballot. The deadline
> for requesting a ballot is August 17, 00:00 UTC (one week before
> Linux Plumbers)
>
> For those who would like to know the thought process behind this:
>
> Last year, we successfully used electronic voting for the TAB
> elections. Given the circumstances of this year, we have no other
> reasonable option for voting. While we could continue to limit voting to
> kernel summit attendees, one of the goals of moving away from in person
> voting was to potentially expand the voter pool. Since kernel summit is
> not being held in person this year, it makes sense to expand the voting
> pool at the same time.
>
> We will be sending a call for nominations and announcements about
> when voting will start at a later date.
>
> If you have any questions, feel free to reach out to the tab at
> tab@lists.linuxfoundation.org
I know it's a lot of work to put this together. Thanks very much for this
new process. I think it's a great change.
Regards,
-- Tim
_______________________________________________
Ksummit-discuss mailing list
Ksummit-discuss@lists.linuxfoundation.org
https://lists.linuxfoundation.org/mailman/listinfo/ksummit-discuss
next prev parent reply other threads:[~2020-07-27 22:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-27 21:31 Laura Abbott
2020-07-27 22:43 ` Bird, Tim [this message]
2020-07-28 13:49 ` Daniel Vetter
2020-08-13 14:18 ` Laura Abbott
2020-08-13 14:31 ` Johannes Berg
2020-08-13 14:35 ` Laura Abbott
2020-08-13 14:37 ` Johannes Berg
-- strict thread matches above, loose matches on Subject: below --
2019-09-03 11:13 Laura Abbott
2019-09-05 17:08 ` Laura Abbott
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=CY4PR13MB1175DCFB41F2FB2F47E43A9CFD720@CY4PR13MB1175.namprd13.prod.outlook.com \
--to=tim.bird@sony.com \
--cc=ksummit-discuss@lists.linuxfoundation.org \
--cc=laura@labbott.name \
--cc=linux-kernel@vger.kernel.org \
--cc=tech-board-discuss@lists.linuxfoundation.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