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 A1D539C for ; Tue, 26 Jul 2016 16:45:37 +0000 (UTC) Received: from mail-it0-f66.google.com (mail-it0-f66.google.com [209.85.214.66]) by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 13364233 for ; Tue, 26 Jul 2016 16:45:37 +0000 (UTC) Received: by mail-it0-f66.google.com with SMTP id u186so993426ita.1 for ; Tue, 26 Jul 2016 09:45:37 -0700 (PDT) MIME-Version: 1.0 In-Reply-To: References: From: Olof Johansson Date: Tue, 26 Jul 2016 09:45:35 -0700 Message-ID: To: Daniel Vetter Content-Type: text/plain; charset=UTF-8 Cc: Grant Likely , Dave Airlie , Linus Torvalds , "Nikula, Jani" , "ksummit-discuss@lists.linuxfoundation.org" Subject: Re: [Ksummit-discuss] [CORE TOPIC] (group) maintainership models List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Hi, On Wed, Jul 20, 2016 at 5:11 AM, 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. Very interested in participating here, for obvious reasons -- learning from others how we can do things even better as well as sharing how things are working for us, 5 years into the endeavor. One thing we're low on for arm-soc is tooling, I know the x86 guys have quite a bit more than we do in this area, so ideas on what we can do to make our own lives easier is valuable. -Olof