From: Sasha Levin <sashal@kernel.org>
To: Jani Nikula <jani.nikula@intel.com>
Cc: "Bird, Tim" <Tim.Bird@sony.com>,
"ksummit-discuss@lists.linuxfoundation.org"
<ksummit-discuss@lists.linuxfoundation.org>,
"tech-board-discuss@lists.linuxfoundation.org"
<tech-board-discuss@lists.linuxfoundation.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [Ksummit-discuss] [Tech-board-discuss] Linux Foundation Technical Advisory Board Elections -- Change to charter
Date: Fri, 13 Mar 2020 09:05:36 -0400 [thread overview]
Message-ID: <20200313130536.GD1349@sasha-vm> (raw)
In-Reply-To: <877dzolf7n.fsf@intel.com>
On Fri, Mar 13, 2020 at 12:30:20PM +0200, Jani Nikula wrote:
>On Fri, 13 Mar 2020, Greg KH <greg@kroah.com> wrote:
>There is no way of knowing whether you're eligible to vote until you
>apply for a kernel.org 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?
Personally, I think that our definition of who can vote should be "any
member of our community", but it's not practical, right?
This process will take years, and each year I would expect us to
increase the voting pool by a significant amount. Maybe we should focus
too much on what restrictions are in affect in the current year, but
rather on trying to learn how well these restrictions worked and which
of them we can lift.
--
Thanks,
Sasha
_______________________________________________
Ksummit-discuss mailing list
Ksummit-discuss@lists.linuxfoundation.org
https://lists.linuxfoundation.org/mailman/listinfo/ksummit-discuss
next prev parent reply other threads:[~2020-03-13 13:05 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-12 0:19 [Ksummit-discuss] Linux Foundation Technical Advisory Board Elections -- Change to charter Laura Abbott
2020-03-12 0:34 ` 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 ` [Ksummit-discuss] [Tech-board-discuss] " Greg KH
2020-03-13 9:41 ` 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 ` Steven Rostedt
2020-03-13 14:10 ` Jani Nikula
2020-03-13 14:52 ` Theodore Y. Ts'o
2020-03-13 15:08 ` Jani Nikula
2020-03-13 15:26 ` James Bottomley
2020-03-13 17:14 ` Bird, Tim
2020-03-13 17:36 ` Steven Rostedt
2020-03-13 15:18 ` James Bottomley
2020-03-13 10:30 ` Jani Nikula
2020-03-13 13:05 ` Sasha Levin [this message]
2020-03-13 15:42 ` Steven Rostedt
2020-03-13 14:59 ` 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=20200313130536.GD1349@sasha-vm \
--to=sashal@kernel.org \
--cc=Tim.Bird@sony.com \
--cc=jani.nikula@intel.com \
--cc=ksummit-discuss@lists.linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tech-board-discuss@lists.linuxfoundation.org \
/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
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).