LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@intel.com>
To: "Theodore Y. Ts'o" <tytso@mit.edu>, "Bird\, Tim" <Tim.Bird@sony.com>
Cc: "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 -- Change to charter
Date: Fri, 13 Mar 2020 10:58:00 +0200	[thread overview]
Message-ID: <87d09gljhj.fsf@intel.com> (raw)
In-Reply-To: <20200313031947.GC225435@mit.edu>

On Thu, 12 Mar 2020, "Theodore Y. Ts'o" <tytso@mit.edu> wrote:
> So that means we need to be smart about how we pick the criteria.
> Using a kernel.org account might be a good approach, since it would be
> a lot harder for a huge number of sock puppet accounts to meet that
> criteria.

Per [1] and [2], kernel.org accounts "are usually reserved for subsystem
maintainers or high-profile developers", but apparently it's at the
kernel.org admins discretion to decide whether one is ultimately
eligible or not. Do we want the kernel.org admin to have the final say
on who gets to vote? Do we want to encourage people to have kernel.org
accounts for no other reason than to vote?

Furthermore, having a kernel.org account imposes the additional
requirement that you're part of the kernel developers web of trust,
i.e. that you've met other kernel developers in person. Which is a kind
of awkward requirement for enabling electronic voting to be inclusive to
people who can't attend in person.

Seems like having a kernel.org account is just a proxy for the criteria,
and one that also lacks transparency, and has problems of its own.

Not that I'm saying there's an easy solution, but obviously kernel.org
account is not as problem free as you might think.

BR,
Jani.


[1] https://www.kernel.org/faq.html
[2] https://korg.wiki.kernel.org/userdoc/accounts

-- 
Jani Nikula, Intel Open Source Graphics Center

  reply	other threads:[~2020-03-13  8:57 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-12  0:19 Laura Abbott
2020-03-12  0:34 ` [Ksummit-discuss] " Laurent Pinchart
2020-03-12  2:20   ` Laura Abbott
2020-03-12 21:28   ` Bird, Tim
2020-03-12 22:58     ` Laura Abbott
2020-03-13  3:19     ` Theodore Y. Ts'o
2020-03-13  8:58       ` Jani Nikula [this message]
2020-03-13  9:35         ` [Tech-board-discuss] " Greg KH
2020-03-13  9:41           ` [Ksummit-discuss] [Tech-board-discuss] " Vlastimil Babka
2020-03-13 10:07             ` Greg KH
2020-03-13 10:16               ` Geert Uytterhoeven
2020-03-13 10:37                 ` Greg KH
2020-03-13 10:50                   ` Geert Uytterhoeven
2020-03-13 12:12                     ` [Tech-board-discuss] [Ksummit-discuss] " Steven Rostedt
2020-03-13 14:10                       ` [Ksummit-discuss] [Tech-board-discuss] " Jani Nikula
2020-03-13 14:52                         ` [Tech-board-discuss] [Ksummit-discuss] " Theodore Y. Ts'o
2020-03-13 15:08                           ` Jani Nikula
2020-03-13 15:26                             ` [Ksummit-discuss] [Tech-board-discuss] " James Bottomley
2020-03-13 17:14                               ` Bird, Tim
2020-03-13 17:36                                 ` [Tech-board-discuss] [Ksummit-discuss] " Steven Rostedt
2020-03-13 15:18                         ` [Ksummit-discuss] [Tech-board-discuss] " James Bottomley
2020-03-13 10:30           ` [Tech-board-discuss] [Ksummit-discuss] " Jani Nikula
2020-03-13 13:05             ` [Ksummit-discuss] [Tech-board-discuss] " Sasha Levin
2020-03-13 15:42               ` [Tech-board-discuss] [Ksummit-discuss] " Steven Rostedt
2020-03-13 14:59             ` [Ksummit-discuss] [Tech-board-discuss] " Konstantin Ryabitsev
2020-03-13 15:07               ` Jani Nikula

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=87d09gljhj.fsf@intel.com \
    --to=jani.nikula@intel.com \
    --cc=Tim.Bird@sony.com \
    --cc=ksummit-discuss@lists.linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tech-board-discuss@lists.linuxfoundation.org \
    --cc=tytso@mit.edu \
    --subject='Re: [Ksummit-discuss] Linux Foundation Technical Advisory Board Elections -- Change to charter' \
    /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

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).