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: <CAMuHMdVSxS1R2osYJh29aKGaqMw3NkTRgqgRWuhu4euygAAXVg@mail.gmail.com>
Date:   Fri, 13 Mar 2020 11:16:36 +0100
From:   Geert Uytterhoeven <geert@...ux-m68k.org>
To:     Greg KH <greg@...ah.com>
Cc:     Vlastimil Babka <vbabka@...e.cz>, "Bird, Tim" <Tim.Bird@...y.com>,
        "ksummit-discuss@...ts.linuxfoundation.org" 
        <ksummit-discuss@...ts.linuxfoundation.org>,
        "tech-board-discuss@...ts.linuxfoundation.org" 
        <tech-board-discuss@...ts.linuxfoundation.org>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [Ksummit-discuss] [Tech-board-discuss] Linux Foundation Technical
 Advisory Board Elections -- Change to charter

Hi Greg,

On Fri, Mar 13, 2020 at 11:08 AM Greg KH <greg@...ah.com> wrote:
> On Fri, Mar 13, 2020 at 10:41:57AM +0100, Vlastimil Babka wrote:
> > On 3/13/20 10:35 AM, Greg KH wrote:
> > >> Not that I'm saying there's an easy solution, but obviously kernel.org
> > >> account is not as problem free as you might think.
> > >
> > > We are not saying it is "problem free", but what really is the problem
> > > with it?
> >
> > IIUC there is no problem for its current use, but it would be rather restrictive
> > if it was used as the only criterion for being able to vote for TAB remotely.
>
> 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?

Obviously the next step beyond "has a kernel.org account" is "is listed
in MAINTAINERS".  All of these can be assumed to be real humans, too.
However, that's still more restrictive than before, as it rules out people
who are not maintainers.

So next step would be developers/maintainers with an SoB.  I think it's still
safe to assume they are real humans, too.
Add a minimum number of commits[*] to raise the bar a little bit, and avoid
the whitespace-fixers who just want to vote.

[*] And e.g. count commits more than one year ago half, more than N years
    ago 1/2^N.  Perhaps add another penalty for staging cleanups ;-)

Gr{oetje,eeting}s,

                        Geert

-- 
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@...ux-m68k.org

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
                                -- Linus Torvalds

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ