ksummit.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Josh Boyer <jwboyer@fedoraproject.org>
To: Steven Rostedt <rostedt@goodmis.org>, "Theodore Ts'o" <tytso@mit.edu>
Cc: ksummit-discuss@lists.linuxfoundation.org
Subject: Re: [Ksummit-discuss] Reminder for kernel summit nominations
Date: Fri, 9 May 2014 12:35:39 -0400	[thread overview]
Message-ID: <CA+5PVA5F8tK0W+rmoT_scmbdE0TpHqKd=RpmXMKjCqS5_E+3bA@mail.gmail.com> (raw)
In-Reply-To: <CA+5PVA7PHGmVvyq3iuqx=-SFZ3edo1+5UVCVdyFMbU+nLsmcZA@mail.gmail.com>

On Fri, May 9, 2014 at 12:12 PM, Josh Boyer <jwboyer@fedoraproject.org> wrote:
> On Fri, May 9, 2014 at 12:01 PM, Steven Rostedt <rostedt@goodmis.org> wrote:
>> 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.
>
> That was kind of my thinking as well.  Put another way, not having
> their name on any list guarantees they won't get an invite.  I'd
> rather at least allow for the possibility...
>
> If it would be helpful, I can go back through the threads today and
> draft a topic specific nomination list of those not already on the
> list otherwise.

It was easier to just do it before I forgot about it, so I'll send a
new thread shortly.

josh

  reply	other threads:[~2014-05-09 16:35 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
2014-05-09 16:12       ` Josh Boyer
2014-05-09 16:35         ` Josh Boyer [this message]
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='CA+5PVA5F8tK0W+rmoT_scmbdE0TpHqKd=RpmXMKjCqS5_E+3bA@mail.gmail.com' \
    --to=jwboyer@fedoraproject.org \
    --cc=ksummit-discuss@lists.linuxfoundation.org \
    --cc=rostedt@goodmis.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