From: Anthony Liguori <anthony@codemonkey.ws>
To: qemu-devel@nongnu.org
Cc: Frank Mehnert <Frank.Mehnert@Sun.COM>
Subject: Re: [Qemu-devel] Merging improvements from VirtualBox OSE into qemu?
Date: Mon, 05 Jan 2009 17:58:22 -0600 [thread overview]
Message-ID: <49629E9E.4000303@codemonkey.ws> (raw)
In-Reply-To: <200901052212.06947.frank.mehnert@sun.com>
Frank Mehnert wrote:
> On Wednesday 24 December 2008, Anthony Liguori wrote:
>
>> Sharing implies a two-way exchange. In reality, VirtualBox has taken a
>> bunch of QEMU code and AFAIK has not shared any of their changes back
>> with the QEMU community. They are completely entitled to do this of
>> course based on the licensing of QEMU.
>>
>
> Sorry, that is not true.
As I said, sharing implies a two-way exchange. The VirtualBox
development was not done publicly and to the best of my knowledge, no
attempt has been made by the VirtualBox developers to push any of their
changes back into QEMU. All other virtualization projects (Xen and it's
variants, KVM, etc.) have made an attempt to push changes back to QEMU.
Yes, you have a public SVN that appeared long after your development
started. Are we supposed to troll through it looking for changes that
may or may not be applicable to upstream? It's extraordinarily
difficult because you've made a huge number of changes to your QEMU fork
that have nothing to do with bug fixes.
This is not how Open Source development works. You don't make a bunch
of changes private, put out a repo after the fact, and make no attempt
to work with any of the projects you took the majority of your code
from. You can call it open all you want but it simply isn't. We won't
even get into the whole contributor agreement non-sense.
>> Some of their most interesting changes (like SATA emulation, rewritten
>> USB emulation) remain available only in their closed source version. I
>> find that extremely unfortunate because that would be some of the
>> easiest and most useful code to try to merge from their project.
>>
>
> Some of these parts might be available under GPL in the future.
>
That would be nice but I'm not going to hold my breathe.
Regards,
Anthony Liguori
> Kind regards,
>
> Frank
>
next prev parent reply other threads:[~2009-01-05 23:58 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-24 12:48 [Qemu-devel] Merging improvements from VirtualBox OSE into qemu? Liraz Siri
2008-12-24 13:17 ` Samuel Thibault
2008-12-24 13:26 ` Alexey Eremenko
2008-12-24 13:31 ` Alexey Eremenko
2008-12-24 13:36 ` Paul Brook
2008-12-24 14:33 ` Liraz Siri
2008-12-24 14:51 ` Jernej Simončič
2008-12-24 15:02 ` Paul Brook
2008-12-24 15:29 ` Liraz Siri
2008-12-24 15:40 ` Anthony Liguori
2008-12-24 20:52 ` Liraz Siri
[not found] ` <E71DFB2B-0B73-46AE-B423-0BF605A9D679@hotmail.com>
2008-12-25 4:37 ` C.W. Betts
2008-12-25 7:06 ` Avi Kivity
2008-12-25 7:07 ` Avi Kivity
2008-12-25 7:08 ` Avi Kivity
2008-12-25 14:51 ` Liraz Siri
2008-12-25 16:14 ` Avi Kivity
2008-12-24 23:18 ` Jamie Lokier
2008-12-25 7:11 ` Avi Kivity
2008-12-24 15:23 ` Anthony Liguori
2008-12-24 20:21 ` Liraz Siri
2008-12-24 20:55 ` Liraz Siri
2009-01-05 21:12 ` Frank Mehnert
2009-01-05 22:03 ` Stefan Weil
2009-01-05 23:58 ` Anthony Liguori [this message]
2009-01-06 7:41 ` Frank Mehnert
2009-01-06 15:46 ` Blue Swirl
2009-01-06 17:33 ` Anthony Liguori
2009-01-06 20:40 ` Frank Mehnert
2009-01-06 22:17 ` Jamie Lokier
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=49629E9E.4000303@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=Frank.Mehnert@Sun.COM \
--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).