ksummit.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Laura Abbott <laura@labbott.name>
Cc: ksummit@lists.linux.dev,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"tech-board-discuss@lists.linuxfoundation.org"
	<tech-board-discuss@lists.linuxfoundation.org>
Subject: Re: Reminder: Voting procedures for the Linux Foundation Technical Advisory Board
Date: Wed, 15 Sep 2021 19:13:50 +0300	[thread overview]
Message-ID: <YUIbvmPUEUtf/BDU@pendragon.ideasonboard.com> (raw)
In-Reply-To: <90e00588-3596-01f5-e5a0-73516224b883@labbott.name>

Hi Laura,

On Wed, Sep 15, 2021 at 12:07:13PM -0400, Laura Abbott wrote:
> On 9/15/21 10:46, Laurent Pinchart wrote:
> > On Wed, Sep 15, 2021 at 10:36:45AM -0400, Laura Abbott wrote:
> >> On 9/15/21 10:07, Laurent Pinchart wrote:
> >>> On Wed, Sep 15, 2021 at 09:58:32AM -0400, Laura Abbott wrote:
> >>>> On 9/9/21 12:49, Laura Abbott wrote:
> >>>>> Hi,
> >>>>>
> >>>>> Reminder that the Linux Foundation Technical Advisory Board (TAB) annual
> >>>>> election will be held virtually during the 2021 Kernel Summit and Linux
> >>>>> Plumbers Conference. Voting will run from September 20th to September
> >>>>> 23rd 16:00 GMT-4 (US/Eastern). The voting criteria for the 2021 election
> >>>>> are:
> >>>>>
> >>>>> There exist three kernel commits in a mainline or stable released
> >>>>> kernel that both
> >>>>> - Have a commit date in the year 2020 or 2021
> >>>>> - 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
> >>>>>
> >>>>> If you have more than 50 commits that meet this requirement you will
> >>>>> receive a ballot automatically.
> >>>>>
> >>>>> If you have between 3 and 49 commits that meet this requirement please
> >>>>> e-mail tab-elections@lists.linuxfoundation.org to request your ballot.
> >>>>> We strongly encourage everyone who meets this criteria to request a
> >>>>> ballot.
> >>>>>
> >>>>> We will be using Condorcet Internet Voting
> >>>>> Service (CIVS) https://civs1.civs.us/ . This is a voting service
> >>>>> focused on security and privacy. There are sample polls on the
> >>>>> website if you would like to see what a ballot will look like.
> >>>>>
> >>>>> If you have any questions please e-mail
> >>>>> tab-elections@lists.linuxfoundation.org.
> >>>>>
> >>>>> Thanks,
> >>>>> Laura
> >>>>>
> >>>>> P.S. Please also consider this another reminder to consider running for
> >>>>> the TAB as well
> >>>>
> >>>> Final reminder: please remember to request your ballot for the TAB
> >>>> elections. If you know others who are eligible please encourage
> >>>> them to request a ballot as well.
> >>>
> >>> When are the ballots supposed to be sent ? It would be nice to avoid
> >>> requiring everybody to check whether they're below or above the 50
> >>> commits threshold manually :-)
> >>
> >> The ballots will be sent sometime after Monday September 20th
> >> 9:00am GMT-4 (US/Eastern).
> >>
> >> I did make an attempt to send e-mails to the > 50 commits individuals
> >> but there is a chance my e-mail got eaten by spam filters or just
> >> didn't get sent out. I discovered Google Apps' e-mail limits and
> >> that you should not attempt to bcc too many people. This is something
> >> I'd like to handle in a more automated fashion next year to make
> >> it easier for both voters and those running the elections.
> > 
> > Does it mean I should ask for a ballot after the 20th if I don't get
> > one, or request one *before* ? I meet the above criteria but haven't
> > received any ballot yet, so I was unsure whether I should ask or wait.
> 
> The intention was that if you were in the range of between 3-49 commits
> you would ask for a ballot now.

Would it be possible to share the script that you are using to check in
which category a developer is, to avoid the criteria being applied in
slightly different ways ?

-- 
Regards,

Laurent Pinchart

  reply	other threads:[~2021-09-15 16:14 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-09 16:49 Reminder: Voting procedures for the Linux Foundation Technical Advisory Board Laura Abbott
2021-09-15 13:58 ` Laura Abbott
2021-09-15 14:07   ` Laurent Pinchart
2021-09-15 14:36     ` Laura Abbott
2021-09-15 14:39       ` James Bottomley
2021-09-15 14:46       ` Laurent Pinchart
2021-09-15 16:07         ` Laura Abbott
2021-09-15 16:13           ` Laurent Pinchart [this message]
2021-09-15 19:34             ` [Tech-board-discuss] " Shuah Khan
2021-09-15 20:42               ` Laura Abbott
2021-09-15 21:11                 ` Shuah Khan
2021-09-15 21:20                   ` Laura Abbott
2021-09-15 15:49       ` Johannes Berg
2021-09-15 16:11         ` Laura Abbott
2021-09-15 16:12           ` Johannes Berg

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=YUIbvmPUEUtf/BDU@pendragon.ideasonboard.com \
    --to=laurent.pinchart@ideasonboard.com \
    --cc=ksummit@lists.linux.dev \
    --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;
as well as URLs for NNTP newsgroup(s).