[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Qemu-devel] Qemu development schedule?

From: Mike Tremoulet
Subject: Re: [Qemu-devel] Qemu development schedule?
Date: Wed, 1 Sep 2004 15:34:20 -0500

If I may, I'd like to make some suggestions to keep this discussion productive.

Some good points have been raised and discussed about the mode of
development for qemu.  At this point, it does become a "religious
debate", where two sides both believe they are right and no correct
answer is actually called for - it's just two different styles of
working.  I can't see much more productive coming from that
discussion, so I respectfully suggest we let that rest.

The idea of a front-end, or minimally a "configurator" to generate the
command line, is interesting.  I'd happily welcome something that gave
me some check boxes and text fields to select from, and set up the
command line switches for me to save for use.  I suspect that, unless
it is built in to the application window (see the OSD part of the
thread, or something like PearPC's choice of boot device), the graphic
form will be platform specific.  Work is already being done in this
area, but I'm not holding my breath for the all-in-one GUI.

However, the real reason I was writing was to gauge interest in some
of the ideas this thread gave me:

- Would there be interest in a bugtrack of sorts for qemu?  My
suspicion is that the platform isn't quite so stable to warrant this,
but it is something I could help set up.  Or promote the use of the
tracker on the Savannah project page?

- Similarly, what about a feature list/request tracker?  Something a
little more focused to capture the wishlist items?

- Finally, a request.  One of the more daunting tasks for me as a
new-to-qemu developer is to read and discover the design of the
system.  What I'd like to do is prepare a brief catalog of each of the
pieces of code, so interested people can more quickly find where to
tie in with the existing code.  In order to produce this quickly,
then, I'm asking that list members please email either myself or the
list with a quick one or two sentence description of each code file
that they touch.  This should only take a couple of seconds, but would
greatly help me compile a table of contents, if you will, of the code.
 An example that I *think* is correct (let me know if I'm off):
NE2000.c - Emulates an NE 2000 NIC in the guest OS.  Sends packets
to/from the QEMU engine.

[Also, if there's a list to be compiled of configure or make options,
or of existing command line switches, I'll be happy to pull those
together as you present them to me.]

-- Mike

reply via email to

[Prev in Thread] Current Thread [Next in Thread]