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 3222F99F for ; Wed, 20 Jul 2016 12:12:00 +0000 (UTC) Received: from mail-oi0-f68.google.com (mail-oi0-f68.google.com [209.85.218.68]) by smtp1.linuxfoundation.org (Postfix) with ESMTPS id B0B5F17E for ; Wed, 20 Jul 2016 12:11:59 +0000 (UTC) Received: by mail-oi0-f68.google.com with SMTP id w143so4622412oiw.2 for ; Wed, 20 Jul 2016 05:11:59 -0700 (PDT) MIME-Version: 1.0 From: Daniel Vetter Date: Wed, 20 Jul 2016 14:11:58 +0200 Message-ID: To: "ksummit-discuss@lists.linuxfoundation.org" Content-Type: text/plain; charset=UTF-8 Cc: Grant Likely , Dave Airlie , Linus Torvalds , "Nikula, Jani" Subject: [Ksummit-discuss] [CORE TOPIC] (group) maintainership models List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , 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. Cheers, Daniel -- Daniel Vetter Software Engineer, Intel Corporation +41 (0) 79 365 57 48 - http://blog.ffwll.ch