public inbox for ksummit@lists.linux.dev
 help / color / mirror / Atom feed
From: Randy Dunlap <rdunlap@infradead.org>
To: Olof Johansson <olof@lixom.net>, "Theodore Y. Ts'o" <tytso@mit.edu>
Cc: Bjorn Helgaas <helgaas@kernel.org>,
	"ksummit-discuss@lists.linuxfoundation.org"
	<ksummit-discuss@lists.linuxfoundation.org>
Subject: Re: [Ksummit-discuss] Topics for the Maintainer's Summit
Date: Mon, 2 Sep 2019 20:05:10 -0700	[thread overview]
Message-ID: <d8103fae-1012-bdff-e7bd-4e32ceb26cb2@infradead.org> (raw)
In-Reply-To: <CAOesGMgOhknM8eZDv+Tr+0C6+ekm7DfxU5GdfW8Zop6Ryq-Kyg@mail.gmail.com>

On 9/2/19 7:35 PM, Olof Johansson wrote:
> On Mon, Sep 2, 2019 at 3:22 PM Theodore Y. Ts'o <tytso@mit.edu> wrote:
>>
>> On Tue, Sep 03, 2019 at 06:42:55AM +1000, Dave Airlie wrote:
>>> On Friday, 30 August 2019, Bjorn Helgaas <helgaas@kernel.org> wrote:
>>>
>>>> On Thu, Aug 29, 2019 at 11:17:20PM -0400, Theodore Y. Ts'o wrote:
>>>>> ...
>>>>> Are there some additional topics that you'd like to suggest that we
>>>>> discuss at the maintainer's summit?
>>>>
>>>> I don't have an effective workflow for managing incoming patches.  I
>>>> use a hodge-podge of patchwork, gmail, mutt, and ugly private scripts
>>>> to put patches on topic branches, review them, polish them, merge them
>>>> together into a "-next" branch, generate pull requests, etc.
>>>>
>>>> I wish there were a collection of the workflows and scripts people
>>>> use, maybe even in the kernel sources so they could be shared and
>>>> improved.  Some short screencasts could help visualize and pull things
>>>> together.  I know a lot of this stuff is "out there" somewhere, but
>>>> I'm not aware of any organized collection.
>>>
>>>
>>> These are quite drm specific but they do mean myself and Daniel can operate
>>> seamlessly, and all i915 and drm misc maintainers and committers use the
>>> same enforced workflow. We hope to move to gitlab at some point and may try
>>> and use the same interface or not.
>>>
>>>  https://drm.pages.freedesktop.org/maintainer-tools/index.html
>>>
>>> Happy to give more info at maintainer summit, but we have gotten negative
>>> feedback in the past from some community members who wanted to point out at
>>> length that drm didnt invent group maintainership first, i still have no
>>> idea of the relevancy of the comment.
>>
>> Are there are other people who have interest in sharing their
>> workflow?  I'm wonder if it might be useful to schedule time during
>> the kernel summit, so it's open for more people to benefit from this
>> sharing?  (Also note that Kernel Summit track sessions will be video
>> taped for posterity, while Maintainer Summit discussions are *not*
>> recorded.)
> 
> Sharing workflow sessions are a repeating theme, but I think there's
> still a good amount of interest in them since things change over time,
> and there's always a lot to learn from how others deal with things.
> 
> I've found that sharing exact tool suites tends to be hard, people are
> often comfortable with the pile-of-scripts they have. But there's
> still value in seeing how others have solved things, and borrow ideas
> or pieces of the workflow.
> 
> Steven's ktest that's in the kernel tree is a good example -- I like
> the idea, but it didn't do quite what I needed, and it was easier to
> just roll my own back when I first looked at using it. It doesn't mean
> others won't reuse it 100%, and it doesn't mean it's not a good idea
> to share them.
> 
> I agree that it's probably a great idea to do on the wider KS forum
> instead, for wider audience. Maybe a BoF-style talk with show-and-tell
> and/or others also showing what and how they do it is useful?

Please just make sure that it is recorded for non-attendees to be able
to make use of it.

-- 
~Randy

  reply	other threads:[~2019-09-03  3:05 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
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 [this message]
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=d8103fae-1012-bdff-e7bd-4e32ceb26cb2@infradead.org \
    --to=rdunlap@infradead.org \
    --cc=helgaas@kernel.org \
    --cc=ksummit-discuss@lists.linuxfoundation.org \
    --cc=olof@lixom.net \
    --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