From: "Theodore Y. Ts'o" <tytso@mit.edu>
To: ksummit-discuss@lists.linuxfoundation.org
Subject: [Ksummit-discuss] Video of Dmitry's Kernel Summit talk (Was: Reflections on kernel development processes)
Date: Thu, 12 Sep 2019 06:56:32 -0400 [thread overview]
Message-ID: <20190912105632.GB32631@mit.edu> (raw)
In-Reply-To: <20190911150804.GA10046@mit.edu>
On Wed, Sep 11, 2019 at 11:08:04AM -0400, Theodore Y. Ts'o wrote:
> Hi all,
>
> Many of you attended Dmitry Vyukov's talk at the Kernel Summit track
> today, "Reflections on Kernel Development Process, Quality, and
> Testing". (For those of you who haven't, the slides are available
> here[1].)
>
> [1] https://linuxplumbersconf.org/event/4/contributions/554/attachments/353/584/Reflections__Kernel_Summit_2019.pdf
>
> Greg K-H has suggested, and I strongly agree, that it would be
> worthwhile to add this to the agenda of the Maintainer's Summit. In
> particular, what next steps should we take and what should be the
> criteria and the process for trying to further standardize our tools
> and processes in order to make make our development processes more
> mature and to improve developer productivity and happiness.
The raw video is (temporarily) available at:
https://youtu.be/a2Nv-KJyqPk?t=5239
This will disappear when we can get something which is properly
cropped and edited --- this is basically the "hot wash" video which
was made available this morning, and after I failed my saving throw
against Linux video editing tools' user interfaces, I just uploaded it
straight to YouTube.
- Ted
_______________________________________________
Ksummit-discuss mailing list
Ksummit-discuss@lists.linuxfoundation.org
https://lists.linuxfoundation.org/mailman/listinfo/ksummit-discuss
next prev parent reply other threads:[~2019-09-12 10:56 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-11 15:08 [Ksummit-discuss] [MAINTAINERS SUMMIT] Reflections on kernel development processes Theodore Y. Ts'o
2019-09-12 10:56 ` Theodore Y. Ts'o [this message]
2019-09-12 12:06 ` Konstantin Ryabitsev
2019-09-13 16:22 ` Rob Herring
2019-09-13 16:34 ` Laurent Pinchart
2019-09-22 12:02 ` Dmitry Vyukov
2019-09-23 12:52 ` Daniel Borkmann
2019-09-23 12:52 ` Daniel Borkmann
2019-09-23 14:08 ` Dmitry Vyukov via Ksummit-discuss
2019-09-23 14:08 ` Dmitry Vyukov
2019-09-23 14:57 ` Daniel Borkmann
2019-09-23 14:57 ` Daniel Borkmann
2019-09-30 21:24 ` Konstantin Ryabitsev
2019-09-30 21:24 ` Konstantin Ryabitsev
2019-10-01 21:33 ` Daniel Borkmann
2019-10-01 21:33 ` Daniel Borkmann
2019-10-02 15:04 ` Konstantin Ryabitsev
2019-10-02 15:04 ` Konstantin Ryabitsev
2019-09-30 20:24 ` Konstantin Ryabitsev
2019-10-08 6:46 ` Dmitry Vyukov
2019-10-08 16:51 ` Konstantin Ryabitsev
2019-10-11 2:16 ` Konstantin Ryabitsev
2019-10-11 2:30 ` Steven Rostedt
2019-10-11 8:30 ` Greg Kroah-Hartman
2019-10-11 8:59 ` Dmitry Vyukov
2019-10-11 9:33 ` Dmitry Vyukov
2019-10-11 9:40 ` Christian Brauner
2019-10-11 13:18 ` Steven Rostedt
2019-10-11 13:19 ` Christian Brauner
2019-10-11 13:30 ` Dmitry Vyukov
2019-10-11 13:40 ` Laurent Pinchart
2019-10-11 15:28 ` Jonathan Corbet
2019-10-14 7:42 ` Nicolas Belouin
2019-10-14 7:52 ` Daniel Vetter
2019-10-15 7:31 ` Dmitry Vyukov
2019-10-15 16:17 ` Konstantin Ryabitsev
2019-10-11 10:46 ` Dmitry Vyukov
2019-10-11 13:29 ` Laurent Pinchart
2019-10-11 13:51 ` Theodore Y. Ts'o
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=20190912105632.GB32631@mit.edu \
--to=tytso@mit.edu \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.