From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1NGiT9-0003Cq-0N
	for qemu-devel@nongnu.org; Fri, 04 Dec 2009 19:25:51 -0500
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1NGiT4-00037J-Ak
	for qemu-devel@nongnu.org; Fri, 04 Dec 2009 19:25:50 -0500
Received: from [199.232.76.173] (port=41784 helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1NGiT3-00037A-Rz
	for qemu-devel@nongnu.org; Fri, 04 Dec 2009 19:25:45 -0500
Received: from mail.valinux.co.jp ([210.128.90.3]:59474)
	by monty-python.gnu.org with esmtp (Exim 4.60)
	(envelope-from <yamahata@valinux.co.jp>) id 1NGiT3-0006C3-DQ
	for qemu-devel@nongnu.org; Fri, 04 Dec 2009 19:25:45 -0500
Date: Sat, 5 Dec 2009 09:25:28 +0900
From: Isaku Yamahata <yamahata@valinux.co.jp>
Subject: Re: [Qemu-devel] Unclear committer situation
Message-ID: <20091205002528.GD3670@valinux.co.jp>
References: <D2A964B8-EC17-4F48-B778-5A6E1F205E3C@suse.de>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <D2A964B8-EC17-4F48-B778-5A6E1F205E3C@suse.de>
List-Id: qemu-devel.nongnu.org
List-Unsubscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/pipermail/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: Alexander Graf <agraf@suse.de>
Cc: Blue Swirl <blauwirbel@gmail.com>, qemu-devel@nongnu.org

BTW what happened to qemu-commit?
It deosn't seem to be working.

On Tue, Dec 01, 2009 at 12:47:36PM +0100, Alexander Graf wrote:
> Hi,
>
> Could someone with commit rights please stand up to feel responsible for 
> PPC?
>
> Usually, when I send a patch to qemu-devel, I know who to address to  
> increase chances of it getting committed. For kvm/vnc/block I just CC  
> Anthony, for Audio I just CC malc, etc.
>
> There are some subsystems where nobody feels responsible though,  
> apparently hoping 'someone else' will tske on it. Well, turns out it  
> doesn't work that way.
>
> So could we please assign a committer for every subsystem around? Even  
> if the committer doesn't know the architecture inside out, it's still  
> valuable to have soneone feel responsible at all. Committer and  
> maintainer also don't have to be the same person. I'll gladly maintain  
> S390 without having commit rights - as long as I have someone to CC and 
> know the patches will get merged.
>
> Of course, my main unclear subsystems are PPC and S390.
>
> I'd recommend the following committers:
>
> PPC: Blue Swirl
> S390: Aurelien
>
> If you have other subsystems you feel uncertain on responsibilities,  
> please add them to the list incl. committer recommendation.
>
> Alex
>
>
>
>

-- 
yamahata