From: Jiri Kosina <jikos@kernel.org>
To: "Theodore Y. Ts'o" <tytso@mit.edu>
Cc: ksummit-discuss@lists.linuxfoundation.org
Subject: Re: [Ksummit-discuss] DRAFT Maintainer's Summit Agenda and Attendee List
Date: Thu, 5 Sep 2019 23:58:00 +0200 (CEST) [thread overview]
Message-ID: <nycvar.YFH.7.76.1909052354230.31470@cbobk.fhfr.pm> (raw)
In-Reply-To: <20190905154702.GA21622@mit.edu>
On Thu, 5 Sep 2019, Theodore Y. Ts'o wrote:
> The agenda topics are of course subject to change (and often do, even
> while we're having the discussion :-). Any thoughts or comments are
> of course welcome.
>
> - Ted
>
> Maintainer's Summit
> Ametista Room at the Corinthia Hotel Lisbon
> September 12, 2019
>
>
> 9:00 Hot breakfast and morning refreshments (sponsored by IBM)
> <Room available for hacking and informal discussions>
> 12:00 Lunch (sponsored by Intel)
> 13:00 Agenda Bashing
> 13:30 Dealing with the high volume of automated bug finders (Shuah Kahn)
> 14:00 Stable Kernel Process Automation and Improvement (Sasha Levin)
> 14:30 Depth of the "pull network" (James Bottomley)
> 15:00 Afternoon Break (Sponsored by IBM)
> 15:30 Is Linus Happy?
> 16:30 <Open Slot>
I'd actually like to propose one more topic; last year, we've been
discussing the process around handling of HW security issues [1]. There
have been quite some developments since then (and there are still a few
unresolved companies^Wissues), and I believe it'd be appropriate to give a
brief update and discuss next steps.
People necessary to discuss this are already on the attendee list, so all
is good there.
[1] https://lwn.net/Articles/769417/
Thanks,
--
Jiri Kosina
SUSE Labs
next prev parent reply other threads:[~2019-09-05 21:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-05 15:47 Theodore Y. Ts'o
2019-09-05 15:58 ` Konstantin Ryabitsev
2019-09-05 21:58 ` Jiri Kosina [this message]
2019-09-06 6:16 ` Thomas Gleixner
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=nycvar.YFH.7.76.1909052354230.31470@cbobk.fhfr.pm \
--to=jikos@kernel.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