From: Dan Williams <dan.j.williams@intel.com>
To: Bart Van Assche <Bart.VanAssche@wdc.com>
Cc: "ksummit-discuss@lists.linuxfoundation.org"
<ksummit-discuss@lists.linuxfoundation.org>
Subject: Re: [Ksummit-discuss] Maintainer's Summit 2017 Feedback Thread
Date: Mon, 30 Oct 2017 09:32:49 -0700 [thread overview]
Message-ID: <CAPcyv4guN0PPdE5tV1i6PN70_uy=xzXSHX6Gy7rjaad5Z+DW2g@mail.gmail.com> (raw)
In-Reply-To: <1509380953.3660.28.camel@wdc.com>
On Mon, Oct 30, 2017 at 9:29 AM, Bart Van Assche <Bart.VanAssche@wdc.com> wrote:
> On Sun, 2017-10-29 at 06:08 -0400, Theodore Ts'o wrote:
>> Please reply to this thread if you have any comments about how we can
>> organize the Maintainer's Summit for next year. Given that Linus
>> seemed fairly happy with how things went, it's likely we will stick
>> with the same format for next year, but if there are any details about
>> how we could do things better, I'd greatly appreciate them.
>
> Hello Ted,
>
> Something that surprised me is although I'm reading Linus' replies to pull
> requests that appear on the LKML mailing list that during the maintainer
> summit I learned more about what Linus expects from maintainers than by
> reading Linus' e-mails. I think this shows that reading Linus' e-mails is
> not enough to learn what Linus expects from maintainers. This made me wonder
> how maintainers are informed about what is expected from them, especially
> new maintainers? Do we perhaps need a document in the kernel tree that
> explains what is expected from maintainers?
Yes, we do. Especially with the number of people that are sending pull
requests directly to Linus. I am taking a look at putting a first
draft of such a document together in the next week or so.
next prev parent reply other threads:[~2017-10-30 16:32 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-29 10:08 Theodore Ts'o
2017-10-30 16:29 ` Bart Van Assche
2017-10-30 16:32 ` Dan Williams [this message]
2017-10-30 18:45 ` Mimi Zohar
2017-10-30 17:42 ` Bart Van Assche
2017-10-30 21:03 ` Theodore Ts'o
2017-10-30 21:20 ` Greg KH
2017-10-30 21:24 ` Konstantin Ryabitsev
2017-10-30 21:27 ` James Bottomley
2017-10-30 21:27 ` Bart Van Assche
2017-10-30 21:43 ` greg
2017-10-30 22:36 ` Julia Lawall
2017-10-30 18:46 ` Takashi Iwai
2017-10-30 23:10 ` Jiri Kosina
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='CAPcyv4guN0PPdE5tV1i6PN70_uy=xzXSHX6Gy7rjaad5Z+DW2g@mail.gmail.com' \
--to=dan.j.williams@intel.com \
--cc=Bart.VanAssche@wdc.com \
--cc=ksummit-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