ksummit.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Shuah Khan <skhan@linuxfoundation.org>
To: "Theodore Y. Ts'o" <tytso@mit.edu>,
	ksummit-discuss@lists.linuxfoundation.org
Subject: Re: [Ksummit-discuss] Topics for the Maintainer's Summit
Date: Fri, 30 Aug 2019 07:58:25 -0600	[thread overview]
Message-ID: <757b2868-5ac6-5da7-a064-0b8393e1aa41@linuxfoundation.org> (raw)
In-Reply-To: <20190830031720.GA7490@mit.edu>

On 8/29/19 9:17 PM, Theodore Y. Ts'o wrote:
> The following topics have been proposed for the maintainer's summit on
> this list:
> 
> * Squashing Bugs!   (Shuah Kahn)
>      How do we deal with the high volume of bugs reported (especially
>      by automated systems like syzbot)
> 
> * Depth of the "pull network"	     (James Bottomley)
>      Should we be encouraging more people to send pull requests
>      to maintainers and sub-maintainers (and sub-sub-maintainers),
>      versus a more "flat tree" model where people send pull requests
>      directly to Linus?
> 
> * Stable Kernel Process Automation and Improvement (Sasha Levin)
>      What remaining pain points are there?  How can we make it better?
> 
> * Talking in Code or talking Code (Shuah Kahn)
>      This was a suggestion about a specific LPC proposal; the core
>      suggestion was talkinig about our e-mail conversation styles
>      on the mailing list.   We have a similar KS track talk:
>      "The list is our process: An analysis of the kernel's
>      email-based development process"

Let's drop this topic. I asked the researcher to focus on clarity of
communication for this talk. Researcher has been looking for tools
that can help analyze clarity of communication in our emails, and
hasn't been successful. More like the analysis too noisy to make
sense of it. As a result, there hasn't been much progress in the
research in the clarity of communication.

> 
> * Patch version changes in commit logs?   (Shuah Kahn)
>      How to make information about how commit has changed while being
>      developed.  (A solution which has already been adopted by some
>      maintainers is to use the Link: tag in the commit discussion).
>      There have been a more recent discussion in this past week under
>      subject line "Allowing something Change-Id (or something like it)
>      in kernel commits".
>   

Looks like this has been resolved with adapting the Link: tag. I would
say we can summarize this and provide a link to the script to share
more easily than digging through the ksummit-discuss threads.

> Some of these topics have already been mostly resolved via e-mail
> discussion.  Which topics do people deserves more discussion?
> 
> Are there some additional topics that you'd like to suggest that we
> discuss at the maintainer's summit?
> 
> 					- Ted
> _______________________________________________
> Ksummit-discuss mailing list
> Ksummit-discuss@lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/ksummit-discuss
> 

  parent reply	other threads:[~2019-08-30 13:58 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-30  3:17 [Ksummit-discuss] Topics for the Maintainer's Summit Theodore Y. Ts'o
2019-08-30 12:01 ` Wolfram Sang
2019-08-30 13:58 ` Shuah Khan [this message]
2019-08-30 14:36   ` shuah
2019-08-30 13:58 ` Bjorn Helgaas
2019-09-02 15:09   ` Shuah Khan
2019-09-02 20:42   ` Dave Airlie
2019-09-02 22:22     ` Theodore Y. Ts'o
2019-09-03  2:35       ` Olof Johansson
2019-09-03  3:05         ` Randy Dunlap
2019-09-03 13:29       ` Laura Abbott
2019-09-03 16:07         ` Linus Torvalds
2019-09-03 17:27           ` Konstantin Ryabitsev
2019-09-03 17:40             ` Bjorn Helgaas
2019-09-06 10:21               ` Rob Herring
2019-09-19  1:47                 ` Bjorn Helgaas
2019-09-19 20:52                   ` Rob Herring
2019-09-20 13:37                     ` Mark Brown
2019-09-03 17:57             ` Mark Brown
2019-09-03 18:14             ` Dan Williams
2019-09-03 21:59             ` Wolfram Sang
2019-09-04  8:34             ` Jan Kara
2019-09-04 12:08             ` Laurent Pinchart
2019-09-04 13:47               ` Konstantin Ryabitsev
2019-09-05  8:21                 ` Jani Nikula
2019-09-06 10:50                   ` Rob Herring
2019-09-06 19:21                     ` Linus Torvalds
2019-09-06 19:53                       ` Olof Johansson
2019-09-09  8:40                         ` Jani Nikula
2019-09-09  9:49                           ` Geert Uytterhoeven
2019-09-09 10:16                             ` Konstantin Ryabitsev
2019-09-09 10:59                               ` Geert Uytterhoeven
2019-09-09 12:37                                 ` Konstantin Ryabitsev
     [not found]                     ` <20190911095305.36104206A1@mail.kernel.org>
2019-09-11 11:03                       ` Christoph Hellwig
2019-09-13  8:19                       ` Matthias Brugger
2019-09-05  7:01           ` Jani Nikula
2019-09-05 15:26             ` 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=757b2868-5ac6-5da7-a064-0b8393e1aa41@linuxfoundation.org \
    --to=skhan@linuxfoundation.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;
as well as URLs for NNTP newsgroup(s).