From: Jamie Lokier <jamie@shareable.org>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] An organizational suggestion
Date: Tue, 3 Jun 2008 11:00:37 +0100 [thread overview]
Message-ID: <20080603100036.GA25740@shareable.org> (raw)
In-Reply-To: <18501.3725.422151.796839@mariner.uk.xensource.com>
Ian Jackson wrote:
> Of course in a Free Software project people tend to do the work that
> they enjoy, and there's a risk that by cricising maintainers for not
> taking patches we'll just make the work of dealing with patches less
> enjoyable.
Perhaps they are simply too busy or doing other things.
>From MAINTAINERS:
x86 Fabrice Bellard (new maintainer needed)
pc.c Fabrice Bellard (new maintainer needed)
Dynamic translator Fabrice Bellard (new maintainer needed)
Main loop Fabrice Bellard (new maintainer needed)
IDE device ?
PCI layer ?
USB layer ?
Block layer ?
Graphic layer ?
Character device layer ?
Network device layer ?
GDB stub ?
Linux user ?
Darwin user ?
SLIRP ?
To which I would add, from using it:
Documentation ? (maintainer needed)
Built-in help ? (maintainer needed)
Command-line / config ? (maintainer needed)
Perhaps it's simply not enough people are paid to do this and
volunteers have other interests. From what I've seen elsewhere, patch
tracking doesn't help much if there's nobody actively working on
integration and setting overall vision/direction.
Fabrice has indicated that there's room for a new maintainer (or
presumably more than one, if they cooperate). It'll be interesting to
see if anyone steps forward, and if they can agree with Fabrice on
direction for the project. If there are any companies out there
commercially dependent on QEMU and it's sister projects (KVM, Xen),
consider hiring for it.
I do suspect this project could now benefit from a more "open" style
of development - as in open to fresh ideas and more open discussion,
not just of specific patches.
-- Jamie
next prev parent reply other threads:[~2008-06-03 10:00 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-03 5:42 [Qemu-devel] An organizational suggestion Balazs Attila-Mihaly (Cd-MaN)
2008-06-03 9:27 ` Ian Jackson
2008-06-03 10:00 ` Jamie Lokier [this message]
2008-06-03 10:19 ` Ian Jackson
2008-06-03 11:03 ` Jamie Lokier
2008-06-03 12:32 ` Ian Jackson
2008-06-03 13:01 ` [Qemu-devel] " Jan Kiszka
2008-06-03 14:26 ` Jamie Lokier
2008-06-03 22:24 ` [Qemu-devel] " Anthony Liguori
2008-06-03 13:45 ` Johannes Schindelin
2008-06-03 14:02 ` Ian Jackson
2008-06-03 14:35 ` Paul Brook
2008-06-03 14:41 ` Jamie Lokier
2008-06-03 14:55 ` Paul Brook
2008-06-03 15:14 ` Jamie Lokier
2008-06-03 14:54 ` Laurent Vivier
2008-06-03 15:04 ` Ian Jackson
2008-06-03 15:17 ` Jamie Lokier
2008-06-03 15:27 ` Ian Jackson
2008-06-03 16:54 ` Anthony Liguori
2008-06-03 19:26 ` Jamie Lokier
2008-06-03 15:24 ` Laurent Vivier
2008-06-03 20:37 ` Anthony Liguori
2008-06-03 20:27 ` Anthony Liguori
2008-06-03 10:23 ` Andreas Färber
2008-06-03 11:09 ` [Qemu-devel] " Jan Kiszka
2008-06-03 12:36 ` Ian Jackson
2008-06-03 12:48 ` Daniel P. Berrange
-- strict thread matches above, loose matches on Subject: below --
2008-06-03 10:11 [Qemu-devel] " Balazs Attila-Mihaly (Cd-MaN)
2008-06-03 15:36 Balazs Attila-Mihaly (Cd-MaN)
2008-06-03 16:59 ` Andreas Färber
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20080603100036.GA25740@shareable.org \
--to=jamie@shareable.org \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).