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 ESMTP id AA83B6FC for ; Tue, 13 May 2014 13:27:54 +0000 (UTC) Received: from mx2.suse.de (cantor2.suse.de [195.135.220.15]) by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 5C09D201D6 for ; Tue, 13 May 2014 13:27:54 +0000 (UTC) Received: from relay1.suse.de (charybdis-ext.suse.de [195.135.220.254]) by mx2.suse.de (Postfix) with ESMTP id BE82BAC7A for ; Tue, 13 May 2014 13:27:52 +0000 (UTC) Date: Tue, 13 May 2014 15:27:52 +0200 Message-ID: From: Takashi Iwai To: ksummit-discuss@lists.linuxfoundation.org MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: text/plain; charset=US-ASCII Subject: [Ksummit-discuss] [TOPIC] Guidance for subsystem maintainers List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , ... aka parent guide to healthy community care. While posting to different subsystem areas, I noticed various ways of responses and communications. Some picks up quick, some urges more reviews, sometimes a patch gets merged silently after months later, etc. Although the variety is one strength of OSS development, it made me also wonder whether we need some baseline guidance for subsystem maintenance in order to give a better appeal to casual developers. Is such a thing too much burden to maintainers? Or, is it just a bikeshedding? thanks, Takashi