From: Darren Hart <dvhart@infradead.org>
To: Daniel Vetter <daniel.vetter@ffwll.ch>
Cc: Grant Likely <grant.likely@linaro.org>,
Dave Airlie <airlied@linux.ie>,
Linus Torvalds <torvalds@linux-foundation.org>,
"Nikula, Jani" <jani.nikula@linux.intel.com>,
"ksummit-discuss@lists.linuxfoundation.org"
<ksummit-discuss@lists.linuxfoundation.org>
Subject: Re: [Ksummit-discuss] [CORE TOPIC] (group) maintainership models
Date: Tue, 26 Jul 2016 09:22:38 -0700 [thread overview]
Message-ID: <20160726162238.GE3703@f23x64.localdomain> (raw)
In-Reply-To: <CAKMK7uEeNuts2FzUAS7NzWjP_yYhOAgT4Q-QtVixm0CozOf0AQ@mail.gmail.com>
On Mon, Jul 25, 2016 at 07:57:04AM +0200, Daniel Vetter wrote:
> On Fri, Jul 22, 2016 at 10:02 PM, Darren Hart <dvhart@infradead.org> wrote:
> > On Wed, Jul 20, 2016 at 02:11:58PM +0200, Daniel Vetter wrote:
> >> In my very first KS I found the maintainership model presentations
> >> (x86-tip & armsoc) rather interesting. And last year we've had an
> >> ad-hoc discussion about group maintainership again. I think drm&i915
> >> would be an interesting case since over the past year I've done some
> >> changes which are at the edge of what's common in the kernel, and it
> >> seems to work (at least for us) fairly well. I discussed this a bit
> >> with a few folks at ELC San Diego too.
> >>
> >> Short summary: i915 has now a two-level maintenance model with 2
> >> maintainers (who take the blame) and 15 people who can push patches.
> >> In a way a rather big group, but not so big that people don't all know
> >> each another any more personally. We have some detailed docs about the
> >> patch flow and expectations:
> >>
> >> https://01.org/linuxgraphics/gfx-docs/maintainer-tools/drm-intel.html
> >>
> >> and about the dim tool used to support this all
> >>
> >> https://01.org/linuxgraphics/gfx-docs/maintainer-tools/dim.html
> >>
> >> But I think the more interesting bits are why I decided to try this
> >> out, what I hoped would happen, what I feared might happen. And with 1
> >> year of experience, what actually happens and what I think is needed
> >> to make this work and an actual benefit over more traditional
> >> maintainer models. And of course I'd like to compare notes with other
> >> group maintainers.
> >
> > I'd be interested in the discussion. I think having it would also serve to
> > minimize the differences between policies across subsystems (which is a common
> > topic people have raised with me).
>
> Not sure I'm helping, since I think this new i915 model makes the
> spread in different policies worse ;-) What do you have in mind here?
Just talking about what maintainers are doing, which is always evolving, will
help keep us in sync, and adopting improved methods.
--
Darren Hart
Intel Open Source Technology Center
next prev parent reply other threads:[~2016-07-26 16:22 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-20 12:11 Daniel Vetter
2016-07-22 20:02 ` Darren Hart
2016-07-25 5:57 ` Daniel Vetter
2016-07-26 16:22 ` Darren Hart [this message]
2016-07-28 22:13 ` Bjorn Helgaas
2016-07-26 16:45 ` Olof Johansson
2016-07-27 3:04 ` Vinod Koul
2016-07-27 5:34 ` Wolfram Sang
2016-07-27 7:53 ` Arnd Bergmann
2016-07-27 12:57 ` Vinod Koul
2016-07-27 14:22 ` Mark Brown
2016-07-27 17:15 ` Vinod Koul
2016-07-28 8:44 ` Arnd Bergmann
2016-07-28 23:48 ` Alexandre Belloni
2016-07-29 0:06 ` Stephen Rothwell
2016-07-31 17:57 ` Vinod Koul
2016-08-01 6:56 ` Arnd Bergmann
2016-08-01 7:36 ` Laurent Pinchart
2016-08-01 14:10 ` Arnd Bergmann
2016-08-02 4:46 ` Vinod Koul
2016-08-02 6:48 ` Peter Ujfalusi
2016-08-02 7:27 ` Arnd Bergmann
2016-08-02 8:29 ` Peter Ujfalusi
2016-08-02 8:33 ` Laurent Pinchart
2016-08-02 9:49 ` Tony Lindgren
2016-08-02 8:41 ` Russell King - ARM Linux
2016-08-02 9:21 ` Laurent Pinchart
2016-08-02 9:27 ` Russell King - ARM Linux
2016-09-02 10:46 ` Vinod Koul
2016-09-02 17:25 ` Linus Torvalds
2016-09-02 20:06 ` Arnd Bergmann
2016-09-02 20:26 ` Linus Torvalds
2016-09-02 20:43 ` Julia Lawall
2016-09-02 20:50 ` Linus Torvalds
2016-09-02 22:16 ` Benjamin Herrenschmidt
2016-09-03 14:02 ` Michael Ellerman
2016-09-02 23:35 ` Arnd Bergmann
2016-09-04 17:45 ` Geert Uytterhoeven
2016-09-04 17:59 ` Linus Torvalds
2016-09-03 0:07 ` Mark Brown
2016-07-27 12:59 ` Daniel Vetter
2016-07-27 13:03 ` Daniel Vetter
2016-08-01 14:42 ` Jani Nikula
2016-09-07 5:03 Leon Romanovsky
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=20160726162238.GE3703@f23x64.localdomain \
--to=dvhart@infradead.org \
--cc=airlied@linux.ie \
--cc=daniel.vetter@ffwll.ch \
--cc=grant.likely@linaro.org \
--cc=jani.nikula@linux.intel.com \
--cc=ksummit-discuss@lists.linuxfoundation.org \
--cc=torvalds@linux-foundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox