[Ksummit-discuss] Topics for the Maintainer's Summit

["Theodore Y. Ts'o" <tytso@mit.edu>]

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"

* 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".
    
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