From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org [172.17.192.35]) by mail.linuxfoundation.org (Postfix) with ESMTPS id 9D324CB6 for ; Mon, 2 Sep 2019 20:42:58 +0000 (UTC) Received: from mail-lj1-f196.google.com (mail-lj1-f196.google.com [209.85.208.196]) by smtp1.linuxfoundation.org (Postfix) with ESMTPS id B55747DB for ; Mon, 2 Sep 2019 20:42:57 +0000 (UTC) Received: by mail-lj1-f196.google.com with SMTP id l14so13923899lje.2 for ; Mon, 02 Sep 2019 13:42:57 -0700 (PDT) MIME-Version: 1.0 In-Reply-To: <20190830135857.GF7013@google.com> References: <20190830031720.GA7490@mit.edu> <20190830135857.GF7013@google.com> From: Dave Airlie Date: Tue, 3 Sep 2019 06:42:55 +1000 Message-ID: To: Bjorn Helgaas Content-Type: multipart/alternative; boundary="000000000000409a690591980417" Cc: "ksummit-discuss@lists.linuxfoundation.org" Subject: Re: [Ksummit-discuss] Topics for the Maintainer's Summit List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , --000000000000409a690591980417 Content-Type: text/plain; charset="UTF-8" On Friday, 30 August 2019, Bjorn Helgaas 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. Dave. --000000000000409a690591980417 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable

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 wro= te:
> ...
> Are there some additional topics that you'd like to suggest that w= e
> discuss at the maintainer's summit?

I don't have an effective workflow for managing incoming patches.=C2=A0= 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.=C2=A0 Some short screencasts could help visualize and pull things=
together.=C2=A0 I know a lot of this stuff is "out there" somewhe= re, but
I'm not aware of any organized collection.

<= div>These are quite drm specific but they do mean myself and Daniel can ope= rate seamlessly, and all i915 and drm misc maintainers and committers use t= he same enforced workflow. We hope to move to gitlab at some point and may = try and use the same interface or not.


<= /div>
Happy to give more info at maintainer summit, but we have gotten = negative feedback in the past from some community members who wanted to poi= nt out at length that drm didnt invent group maintainership first, i still = have no idea of the relevancy of the comment.

Dave= .
--000000000000409a690591980417--