From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1NFYIS-0003xv-W5 for qemu-devel@nongnu.org; Tue, 01 Dec 2009 14:22:01 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1NFYIO-0003xL-2Q for qemu-devel@nongnu.org; Tue, 01 Dec 2009 14:22:00 -0500 Received: from [199.232.76.173] (port=49285 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NFYIN-0003xI-Rq for qemu-devel@nongnu.org; Tue, 01 Dec 2009 14:21:55 -0500 Received: from mail-yx0-f188.google.com ([209.85.210.188]:38326) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1NFYIN-0006CQ-MZ for qemu-devel@nongnu.org; Tue, 01 Dec 2009 14:21:55 -0500 Received: by yxe26 with SMTP id 26so4326791yxe.4 for ; Tue, 01 Dec 2009 11:21:55 -0800 (PST) MIME-Version: 1.0 In-Reply-To: <4B1565AD.10503@codemonkey.ws> References: <4B1565AD.10503@codemonkey.ws> From: Blue Swirl Date: Tue, 1 Dec 2009 19:21:28 +0000 Message-ID: Subject: Re: [Qemu-devel] Unclear committer situation Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Anthony Liguori Cc: Alexander Graf , qemu-devel@nongnu.org On Tue, Dec 1, 2009 at 6:51 PM, Anthony Liguori wro= te: > 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 doe= sn't >> work that way. > > The general problem is that someone has to step up to maintain these > subsystems. =C2=A0For some of them, there just isn't really a lot of inte= rest. Getting a decent test setup for each architecture is a bit of work too. >> So could we please assign a committer for every subsystem around? Even i= f >> the committer doesn't know the architecture inside out, it's still valua= ble >> to have soneone feel responsible at all. Committer and maintainer also d= on't >> have to be the same person. I'll gladly maintain S390 without having com= mit >> rights - as long as I have someone to CC and know the patches will get >> merged. > > git pulls have been working really well for linux-user. =C2=A0I'd like to > continue that for new architectures. > >> 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. > > PPC is tough because we lost our previous maintainer. =C2=A0It's generall= y in > pretty bad shape. =C2=A0No one really has stepped up to seriously improve= it > either. The design approach was often different from other architectures, which makes things like qdev conversion less trivial (see macio.c). Otherwise IMHO the situation has improved a lot, we even have a working BIOS. Only PREP has rotten.