From: "Daniel P. Berrange" <berrange@redhat.com>
To: "Mike D. Day" <ncmike@us.ibm.com>
Cc: smoser@us.ibm.com, xen-devel@lists.xensource.com,
kvm@vger.kernel.org, virtualization@lists.linux-foundation.org
Subject: Re: Announcing: Open OVF project source code availibility
Date: Tue, 12 Aug 2008 15:46:56 +0100 [thread overview]
Message-ID: <20080812144656.GQ13067@redhat.com> (raw)
In-Reply-To: <20080812143432.GA8431@silverwood.ncultra.org>
On Tue, Aug 12, 2008 at 10:34:33AM -0400, Mike D. Day wrote:
> Announcing the open-ovf project and source code availibility.
>
> Hi folks, we are announcing the availibility of source code for the
> open-ovf project.
Why was the Eclipse Public License chosen ? This license is not
compatible with the GPL[1], so no GPL licensed app can make use of
this code :-( For example it makes it impossible to use this code to
assist in supporting OVF in virt-manager, virt-install or virt-image
http://en.wikipedia.org/wiki/Eclipse_Public_License
"The EPL 1.0 is not compatible with the GPL, and a work created by
combining a work licensed under the GPL with a work licensed under
the EPL cannot be lawfully distributed."
Daniel
--
|: Red Hat, Engineering, London -o- http://people.redhat.com/berrange/ :|
|: http://libvirt.org -o- http://virt-manager.org -o- http://ovirt.org :|
|: http://autobuild.org -o- http://search.cpan.org/~danberr/ :|
|: GnuPG: 7D3B9505 -o- F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 :|
next prev parent reply other threads:[~2008-08-12 14:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-12 14:34 Announcing: Open OVF project source code availibility Mike D. Day
2008-08-12 14:46 ` Daniel P. Berrange [this message]
2008-08-12 15:26 ` Mike Day
2008-08-12 15:42 ` Daniel P. Berrange
2008-08-12 16:59 ` Mike Day
2008-08-13 9:37 ` Ian Jackson
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=20080812144656.GQ13067@redhat.com \
--to=berrange@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=ncmike@us.ibm.com \
--cc=smoser@us.ibm.com \
--cc=virtualization@lists.linux-foundation.org \
--cc=xen-devel@lists.xensource.com \
/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