From: Takashi Iwai <tiwai@suse.de>
To: Theodore Ts'o <tytso@mit.edu>
Cc: ksummit-discuss@lists.linuxfoundation.org
Subject: Re: [Ksummit-discuss] Maintainer's Summit 2017 Feedback Thread
Date: Mon, 30 Oct 2017 19:46:05 +0100 [thread overview]
Message-ID: <s5h60awfp8y.wl-tiwai@suse.de> (raw)
In-Reply-To: <20171029100816.pmq5dpmck4cclmdw@thunk.org>
On Sun, 29 Oct 2017 11:08:16 +0100,
Theodore Ts'o wrote:
>
> Hi,
>
> 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.
I find such a small group is suitable for discussions, too, as the
atmosphere there was a kind of extended hallway sessions. Especially
I felt it after the tables were gathered and the mic got off. A
slightly more attendees would still work, too, though.
But the room assignment needs more consideration: not only pillars in
the middle, the room was too large for a small group, and the constant
noise for preparing the lunch was a bit annoying.
With my distro maintainer hat on, I believe that it would have been
better if we had an open session for things like "bash distro kernels
(or vice versa)" before the maintainers summit. The "regression
tracking" and "bash kernel maintainers" topics went well in the
maintainers summit since we had sorted out the focused points
beforehand. Otherwise the discussion will be blurred.
thanks,
Takashi
next prev parent reply other threads:[~2017-10-30 18:46 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
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 [this message]
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=s5h60awfp8y.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--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