From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from [140.186.70.92] (port=42930 helo=eggs.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1OsDFm-0004VH-Ha
	for qemu-devel@nongnu.org; Sun, 05 Sep 2010 07:19:19 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69)
	(envelope-from <avi@redhat.com>) id 1OsDFj-0001OY-Q8
	for qemu-devel@nongnu.org; Sun, 05 Sep 2010 07:19:17 -0400
Received: from mx1.redhat.com ([209.132.183.28]:64563)
	by eggs.gnu.org with esmtp (Exim 4.69)
	(envelope-from <avi@redhat.com>) id 1OsDFj-0001OT-I7
	for qemu-devel@nongnu.org; Sun, 05 Sep 2010 07:19:15 -0400
Message-ID: <4C837CAF.4080200@redhat.com>
Date: Sun, 05 Sep 2010 14:19:11 +0300
From: Avi Kivity <avi@redhat.com>
MIME-Version: 1.0
Subject: Re: [Qemu-devel] Unmaintained QEMU builds
References: <4C62825A.6000903@mail.berlios.de>	<AANLkTinXC8r+13q5y9K+mvyNZPNbvycRq8p4FU5T+J1K@mail.gmail.com>	<4C685F5D.2090707@codemonkey.ws>	<AANLkTimr4qwxTJx0kD2-QXKp3dFdMi28Ypf5YEK2DdaY@mail.gmail.com>	<4C69A29F.5000606@codemonkey.ws>	<AANLkTimpGt3v8Qk5SfCHAWznDaGeMnpbwhtBnC3Sq=ZP@mail.gmail.com>	<4C6AE96C.2040907@codemonkey.ws>
	<B6E113F3-6DD5-401F-A5A8-328374CEAA06@web.de>
In-Reply-To: <B6E113F3-6DD5-401F-A5A8-328374CEAA06@web.de>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: quoted-printable
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.nongnu.org/archive/html/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: =?ISO-8859-1?Q?Andreas_F=E4rber?= <andreas.faerber@web.de>
Cc: QEMU Developers <qemu-devel@nongnu.org>

  On 09/04/2010 04:56 PM, Andreas F=E4rber wrote:
>
> Maybe it's time to rethink the relation between QEMU and its frontends=20
> / management tools? If we want to compete with the commercial products=20
> (sic), we might agree on some "official" frontend per GUI-centric=20
> platform, with a Git-based repository (like qemu-kvm.git) and=20
> synchronized releases that may call themselves "QEMU", linked from=20
> qemu.org, rather than having a variety of (outdated) Q* frontends per=20
> platform of which most are nothing more than a configuration window to=20
> spawn the regular qemu[-system-x86_64].=20

There is also virt-manager which is quite rich at this time.

> Currently what QEMU can point with is richer machine and hardware=20
> emulation and its license; if we want more users than that, we'll need=20
> to deliver what users usually want the most - stability, performance=20
> and ease of use... and good marketing.

They may as well be merged into qemu.git directly, so long as:

- the GUI has its own maintainer
- the prepackaged GUI doesn't get access to internal APIs, compared to=20
external tools

--=20
error compiling committee.c: too many arguments to function