linux-kernel - Re: [Tech-board-discuss] Reminder: Voting procedures for the Linux Foundation Technical Advisory Board

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Wed, 15 Sep 2021 15:11:10 -0600
From:   Shuah Khan <skhan@...uxfoundation.org>
To:     Laura Abbott <laura@...bott.name>,
        Laurent Pinchart <laurent.pinchart@...asonboard.com>
Cc:     ksummit@...ts.linux.dev,
        "tech-board-discuss@...ts.linuxfoundation.org" 
        <tech-board-discuss@...ts.linuxfoundation.org>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
        Johannes Berg <johannes@...solutions.net>,
        Shuah Khan <skhan@...uxfoundation.org>
Subject: Re: [Tech-board-discuss] Reminder: Voting procedures for the Linux
 Foundation Technical Advisory Board

On 9/15/21 2:42 PM, Laura Abbott wrote:
> On 9/15/21 15:34, Shuah Khan wrote:
>> On 9/15/21 10:13 AM, Laurent Pinchart wrote:
>>> 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@...ts.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@...ts.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 ?
>>>
>>
>> Same request. Is this the same script that gets used to determine candidate
>> eligibility before they get added to the ballot?
>>
>> thanks,
>> -- Shuah
> 
> You can thank Kees for the script
> 
> https://github.com/kees/kernel-tools/blob/trunk/identity-canonicalizer
> 
> This is the same script for both voting and nomination
> 
> The set generated is
> 
> # Find people participating in 50+ commits since 2020-01-01:
> git log --since=2020-01-01 | ~/bin/identity-canonicalizer | sort -g > contributors.txt
> cat contributors.txt | awk '{if ($1 > 2) {print $0}}' >eligible.txt
> cat eligible.txt | awk '{if ($1 > 49) {print $0}}' >ballots.txt

So people that this script spits out are the ones that are
eligible for the following:

-- get added to the ballot if they sent in the nomination
-- get sent a ballot by Sept 20th for voting

Also does this criteria get applied to TAB Chair/co-Chair election
going forward?

thanks,
-- Shuah