LKML Archive on
help / color / mirror / Atom feed
From: Konstantin Ryabitsev <>
To: Jani Nikula <>
Cc: Greg KH <>, "Bird, Tim" <>,
	"" <>
Subject: Re: [Ksummit-discuss] [Tech-board-discuss] Linux Foundation Technical Advisory Board Elections -- Change to charter
Date: Fri, 13 Mar 2020 10:59:03 -0400	[thread overview]
Message-ID: <20200313145903.vwdpawgcve73hdmj@chatter.i7.local> (raw)
In-Reply-To: <>

[-- Attachment #1: Type: text/plain, Size: 2640 bytes --]

On Fri, Mar 13, 2020 at 12:30:20PM +0200, Jani Nikula wrote:
> There is no way of knowing whether you're eligible to vote until you
> apply for a account and either get approved or rejected.
> The current "obvious" requirement levels are not obvious to me. How many
> contributions is enough? Is everyone in MAINTAINERS eligible, or do you
> have to be a high-profile maintainer/developer? What is a high-profile
> developer? How many people in the web of trust must you have met in
> person?

Anyone listed in MAINTAINERS is eligible to get an auto-approved account 
on, but they *must* satisfy the web of trust requirement:

- their key is signed by 2 other people who already have a 
  account (marginal trust), OR
- their key is signed by one of the following people (full trust):

  - H. Peter Anvin
  - Greg Kroah-Hartman
  - Ted Ts'o
  - Linus Torvalds
  - Dirk Hohndel
  - James Bottomley

Anyone who is not in MAINTAINERS but feel they should have an account on can still apply if they provide a reason behind their 
request. Such cases are fairly rare and usually include collaboration on 
non-kernel projects that are also hosted on (there aren't 
that many, but there are a few). The web of trust requirement is exactly 
the same, but the final approval is not automatic. I forward these 
requests to the above 6 people and it is sufficient for at least one 
person to say "aye" for the account to be approved.

It is also important to highlight a distinction between "having an 
account" and having a email forwarding address. For this 
particular case I was requested to provide a list of people with *active 
accounts* on, meaning that they have performed a git+ssh 
operation within the past 12 months.

> And it actually seems like you think it's a good thing the admin team
> can make a subjective decision on the above.

The LF IT admin team does not make any decisions -- all decisions are 
taken by the above 6 people (unless the person is in MAINTAINERS, in 
which case their approval is implicit).

> It may seem completely transparent and fair and objective on the
> *inside*, but it does not look that way on the *outside*. Which is kind
> of the definition of transparent. Or lack of.

I hope I helped clarify the procedure. Of course, as the person actually 
creating accounts I'm the final arbiter of all decisions. If I had any 
malicious intents, I could totally subvert the whole process -- so in 
the end you just have to trust me to be on the side of "lawful good."


[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

  parent reply	other threads:[~2020-03-13 14:59 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
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             ` Konstantin Ryabitsev [this message]
2020-03-13 15:07               ` [Ksummit-discuss] [Tech-board-discuss] " 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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20200313145903.vwdpawgcve73hdmj@chatter.i7.local \ \ \ \ \ \ \ \
    --subject='Re: [Ksummit-discuss] [Tech-board-discuss] Linux Foundation Technical Advisory Board Elections -- Change to charter' \

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