From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:58621) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WEHuw-0007Hw-PM for qemu-devel@nongnu.org; Fri, 14 Feb 2014 07:30:59 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1WEHur-0003AJ-Q6 for qemu-devel@nongnu.org; Fri, 14 Feb 2014 07:30:54 -0500 Received: from mail-we0-x230.google.com ([2a00:1450:400c:c03::230]:58622) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WEHur-0003A7-JL for qemu-devel@nongnu.org; Fri, 14 Feb 2014 07:30:49 -0500 Received: by mail-we0-f176.google.com with SMTP id q58so8503639wes.7 for ; Fri, 14 Feb 2014 04:30:48 -0800 (PST) Date: Fri, 14 Feb 2014 13:30:45 +0100 From: Stefan Hajnoczi Message-ID: <20140214123045.GB17391@stefanha-thinkpad.redhat.com> References: <52EF8F6B.8080800@ilande.co.uk> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <52EF8F6B.8080800@ilande.co.uk> Subject: Re: [Qemu-devel] Improving patch tracking - something like gerrit? List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Mark Cave-Ayland Cc: qemu-devel , Anthony Liguori On Mon, Feb 03, 2014 at 12:45:31PM +0000, Mark Cave-Ayland wrote: > Is it time for QEMU to start looking at tools such as gerrit to help > manage this process? This has been addressed by Daniel Berrange but I just wanted to add my vote *against* gerrit. Instead, look at tools that correlate mailing list emails with git commits. They complement the mailing list and don't force people to use them. The options that I'm aware of are Patchwork and Anthony's "patches" tool. Both have limitations and I haven't found them good enough - but hopefully that can be fixed. http://jk.ozlabs.org/projects/patchwork/ https://github.com/aliguori/patches > There seems to be an increasing number of ping > requests for outstanding patches (including my own) which don't get > applied for weeks, and often even months because they target less > popular platforms/subsystems and so don't always get the attention > of the committers. The answer isn't tooling, IMO. Send "ping" emails but also be vocal when the development process isn't working. Point out specific cases where more maintainership bandwidth is needed. Then new maintainers can volunteer to fill in gaps. Existing maintainers can reflect on their performance and try to improve things (I've been guilty of poor responsiveness many times myself). Stefan