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]
Message-ID: <20200313081216.627c5bdf@gandalf.local.home>
Date:   Fri, 13 Mar 2020 08:12:16 -0400
From:   Steven Rostedt <rostedt@...dmis.org>
To:     Geert Uytterhoeven <geert@...ux-m68k.org>
Cc:     Greg KH <greg@...ah.com>,
        "tech-board-discuss@...ts.linuxfoundation.org" 
        <tech-board-discuss@...ts.linuxfoundation.org>,
        "ksummit-discuss@...ts.linuxfoundation.org" 
        <ksummit-discuss@...ts.linuxfoundation.org>,
        Vlastimil Babka <vbabka@...e.cz>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [Tech-board-discuss] [Ksummit-discuss] Linux Foundation
 Technical Advisory Board Elections -- Change to charter

On Fri, 13 Mar 2020 11:50:45 +0100
Geert Uytterhoeven <geert@...ux-m68k.org> wrote:

> > > > Given that before now, there has not be any way to vote for the TAB
> > > > remotely, it's less restrictive :)  
> > >
> > > But people without kernel.org accounts could still vote in person before,
> > > right?  
> >
> > Yes, and they still can today, this is expanding the pool, not
> > restricting it.  
> 
> Oh right, assumed we'll still have a conference in person, and unrestricted
> travel.

Correct. But if we don't change the voting requirements, and the conference
is canceled, or people are restricted from traveling, then those people
will not be able to vote with the current charter.

We are trying to extend who can vote beyond those that the charter allows.
We are not preventing those that can vote under the current rules from
voting.  IIUC, we are trying to create absentee voting which we never had
before. Thus, you can either vote the current way by getting travel to
wherever Kernel Summit is and attending the conference, or we can extend
the charter so that if you can not come for whatever reason, you have an
option to vote remotely, if you satisfy the new requirements. Remember, not
attending means you do not satisfy the current requirements.

The TAB has bikeshed this a bit internally, and came up with the conclusion
that kernel.org accounts is a very good "first step". If this proves to be
a problem, we can look at something else. This is why we are being a bit
vague in the changes so that if something better comes along we can switch
to that. After some experience in various methods (if we try various
methods), we could always make whatever method works best as an official
method at a later time.

But for now, we need to come up with something that makes it hard for
ballot stuffing, and a kernel.org account (plus activity in the kernel)
appears to be the best solution we know of.

-- Steve

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ