From: Steven Rostedt <rostedt@goodmis.org>
To: Theodore Ts'o <tytso@mit.edu>
Cc: Josh Boyer <jwboyer@fedoraproject.org>,
ksummit-discuss@lists.linuxfoundation.org
Subject: Re: [Ksummit-discuss] Reminder for kernel summit nominations
Date: Fri, 9 May 2014 12:01:44 -0400 [thread overview]
Message-ID: <20140509120144.3ce5657e@gandalf.local.home> (raw)
In-Reply-To: <20140509154035.GE15523@thunk.org>
On Fri, 9 May 2014 11:40:35 -0400
Theodore Ts'o <tytso@mit.edu> wrote:
> -linux-kernel
>
> I deliberately didn't include lists of names of "people that would be
> useful if we're going to have discussion X", since we that presupposes
> that we are definitely going to have a particular discussion. If you
> see someone who you think should attend regardless of whether we
> decide to include topic X, please send a separate nomination.
I don't know why not. Even if we do not decide to talk about discussion
X, it does not hurt to add people that are useful to the discussion in
the nomination list. Just because they were mentioned, means they
probably have some importance to the kernel and should be considered.
That doesn't mean that we are going to invite them, any more than we
would invite others on the list.
>
> (Also note that we can't necessarily include everyone listed on a
> "useful for topic X" list even if we are going to include that topic
> on the agenda. We'll try to use some good judgement, but some kind of
> priority listing or annotation of why someone was included, i.e., "we
> need at least one of Foo and Bar from the glibc community, and either
> Quux or Baz from the systemd community, etc.)
For now just acquiring a list for us to start the process is important.
The first round usually just includes major developers that are not
being invited for any specific topic. For the choosing of those for
topics (around when we figure out what topics we want to include),
having a list of "most influential to the topic" would definitely be
helpful.
-- Steve
next prev parent reply other threads:[~2014-05-09 16:01 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-09 15:23 Theodore Ts'o
2014-05-09 15:28 ` Josh Boyer
2014-05-09 15:38 ` Steven Rostedt
2014-05-09 15:40 ` Theodore Ts'o
2014-05-09 16:01 ` Steven Rostedt [this message]
2014-05-09 16:12 ` Josh Boyer
2014-05-09 16:35 ` Josh Boyer
2014-05-09 17:31 ` josh
2014-05-10 9:03 ` Catalin Marinas
2014-05-09 21:44 ` Thomas Gleixner
2014-05-09 23:05 ` tytso
2014-05-13 15:16 ` Michal Hocko
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=20140509120144.3ce5657e@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=jwboyer@fedoraproject.org \
--cc=ksummit-discuss@lists.linuxfoundation.org \
--cc=tytso@mit.edu \
/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