From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([140.186.70.92]:60396) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RQJP7-0008Vy-Ut for qemu-devel@nongnu.org; Tue, 15 Nov 2011 08:50:27 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1RQJP0-0002sA-Em for qemu-devel@nongnu.org; Tue, 15 Nov 2011 08:50:25 -0500 Received: from e37.co.us.ibm.com ([32.97.110.158]:39183) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RQJP0-0002s6-5q for qemu-devel@nongnu.org; Tue, 15 Nov 2011 08:50:18 -0500 Received: from /spool/local by e37.co.us.ibm.com with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted for from ; Tue, 15 Nov 2011 06:50:16 -0700 Received: from d03av02.boulder.ibm.com (d03av02.boulder.ibm.com [9.17.195.168]) by d03relay01.boulder.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id pAFDo4Sp123330 for ; Tue, 15 Nov 2011 06:50:05 -0700 Received: from d03av02.boulder.ibm.com (loopback [127.0.0.1]) by d03av02.boulder.ibm.com (8.14.4/8.13.1/NCO v10.0 AVout) with ESMTP id pAFDo4pv011821 for ; Tue, 15 Nov 2011 06:50:04 -0700 Message-ID: <4EC26E0B.9000408@us.ibm.com> Date: Tue, 15 Nov 2011 07:50:03 -0600 From: Anthony Liguori MIME-Version: 1.0 References: <1321114074-3681-1-git-send-email-aliguori@us.ibm.com> <4EC18349.20203@us.ibm.com> <4EC232A1.9080703@redhat.com> In-Reply-To: <4EC232A1.9080703@redhat.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [PATCH] migration: add a MAINTAINERS entry for migration List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Kevin Wolf Cc: qemu-devel@nongnu.org, quintela@redhat.com On 11/15/2011 03:36 AM, Kevin Wolf wrote: > Am 14.11.2011 22:08, schrieb Anthony Liguori: >> On 11/14/2011 11:40 AM, Juan Quintela wrote: >>> Anthony Liguori wrote: >>>> I think this is an accurate reflection of the state of migration today. This >>>> is the second release in a row where we're scrambling to fix a critical issue >>>> in migration. >>> >>> We need to make our mind about it. >> >> Ultimately, we need to make migration a priority. That's what I'm trying to do >> here. > > When you make everything a priority, being a priority doesn't have much > of a meaning any more. Our current priorities are changing the entire > device model, the monitor, migration, turning the block layer upside > down - what's left? Okay, maybe vvfat and slirp. Well, think of it as employment insurance :-) > >> The first step is to be open about the state of migration today. I personally >> don't have the bandwidth to invest a lot of effort in migration, but I can >> invest time in trying to find more people to work on migration, and help put >> together a proper roadmap. >> >> We need to outline and document what we support and what we don't support. We >> need to invest in a test infrastructure. We need a roadmap that we can >> reasonably execute on. In short, we need to turn migration into a first class >> subsystem. >> >> It's not about any single person or any single patch series. It's about >> deciding that migration is an important feature and deserves more focus and >> attention. > > I don't doubt that everyone will agree with this. The harder question is > who should concentrate less on which other feature to have time to spend > for migration. I don't think it's a question of trading patches in one subsystem for patches in another subsystem. I think it's more about having a planned, concerted effort, that systematically tackles the problems we're facing in migration. By spending more time planning, it makes it much easier for people to contribute. There's a lot of interest in migration. If we made it easier to participate in improving it, I'm sure we would attract at least a few more people to working on it. Regards, Anthony Liguori > > Kevin >