qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Jamie Lokier <jamie@shareable.org>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] An organizational suggestion
Date: Tue, 3 Jun 2008 12:03:47 +0100	[thread overview]
Message-ID: <20080603110346.GC25740@shareable.org> (raw)
In-Reply-To: <18501.6823.92589.960622@mariner.uk.xensource.com>

Ian Jackson wrote:
> > 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.
> 
> Well, I'm certainly willing.  Perhaps I haven't made my availability
> clear enough.

A private mail to Fabrice may be in order, if you're interested in
core maintenance.  Try to involve KVM folks too, that way lies sanity.

Given the commercial tension at present between Citrix (Xen) and
Qumranet (KVM) perhaps neither of you should be the sole primary
maintainer of core systems :-)

> Xen (the whole ecosystem) is indeed very dependent on Qemu and the
> divergence between our tree and the upstream one is far too great.
> Many of our changes are entirely applicable to upstream.

I agree, and the same applies to KVM's QEMU branch, but perhaps that
diverges less than Xen's.

> I was hired by Xensource (now Citrix) specifically to work on the open
> source Xen project.  I think one of the biggest tasks for that project
> is trying to make some kind of sanity in our relationship (both code
> and people) with Qemu upstream.  So we (specifically, I) have effort
> available to help Qemu in general if this means that I can spend less
> time trying to reconcile incompatible changes to our different
> codebases.

Good plan.  I suggest not just reducing code divergence, but
clarifying QEMU's future vision with Fabrice would help too.

-- Jamie

  reply	other threads:[~2008-06-03 11:03 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
2008-06-03 10:19     ` Ian Jackson
2008-06-03 11:03       ` Jamie Lokier [this message]
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=20080603110346.GC25740@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).