qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Patrick Schleizer <adrelanos@riseup.net>
To: qemu-devel@nongnu.org
Subject: [Bug 1864955] Re: bundle QEMU installer with HAXM accelerator for Windows
Date: Thu, 27 Feb 2020 08:52:37 -0000	[thread overview]
Message-ID: <158279355744.19252.5850362454839178636.malone@chaenomeles.canonical.com> (raw)
In-Reply-To: 158278309128.18853.6534515173893863136.malonedeb@chaenomeles.canonical.com

I think licensing is a non-issue.

That is probably a quote from the github license summary at
https://github.com/intel/haxm/blob/master/LICENSE

> A permissive license similar to the BSD 2-Clause License, but with a
3rd clause that prohibits others from using the name of the project or
its contributors to promote derived products without written consent.

I would ignore whatever github says "This is not legal advice. Learn
more about repository licenses." Their summary might have good
intentions but cause confusion. Only github mentions "project". The
actual license text does not.

The actual text of the third clause in the license being:

> Neither the name of the copyright holder nor the names of its
contributors may be used to endorse or promote products derived from
this software without specific prior written permission.

This should be easy to comply with.

One could would wrap that clause into quotes (") to put it into a google
search engine.

This clause is OSI approved since included in BSD-3-Clause license:

https://opensource.org/licenses/BSD-3-Clause

Debian takes being Free / Libre / Open Source very serious too. Search
term:

> site:debian.org "Neither the name of the copyright holder nor the
names of its contributors may be used to endorse or promote products
derived from this software without specific prior written permission."

https://ftp-master.debian.org/licenses/good/bsd/

FSF also does not have an issue with it.

> site:fsf.org "Neither the name of the copyright holder nor the names
of its contributors may be used to endorse or promote products derived
from this software without specific prior written permission."

3 authorities don't have an issue with modified BSD license (without
advertising clause).

Rather, the QEMU installer doesn't need to have HAXM in its file name.

It may or may not be good idea to make HAXM an opt-in or opt-out in the
installer. I'd argue opt-out if anything. But ideally for usability
there is no need to mention HAXM. Things would just work out of the box.

As a role model for usability I'd recommend VirtualBox. Their installer
also doesn't ask/show "enable acceleration" or "VirtualBox includes
QEMU" or other components in prominent places.

-- 
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1864955

Title:
  bundle QEMU installer with HAXM accelerator for Windows

Status in QEMU:
  New

Bug description:
  As you probably know HAXM is an accelerator for Windows.

  https://www.qemu.org/2017/11/22/haxm-usage-windows/

  Currently it is required to first install QEMU and then install HAXM.

  For a better out of the box user experience on the Windows platform it
  would be nice if QEMU and HAXM would be installed by the same
  installer.

To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1864955/+subscriptions


  parent reply	other threads:[~2020-02-27  9:01 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-27  5:58 [Bug 1864955] [NEW] bundle QEMU installer with HAXM accelerator for Windows Patrick Schleizer
2020-02-27  8:08 ` [Bug 1864955] " Philippe Mathieu-Daudé
2020-02-27  8:52 ` Patrick Schleizer [this message]
2021-05-06  5:50 ` Thomas Huth

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=158279355744.19252.5850362454839178636.malone@chaenomeles.canonical.com \
    --to=adrelanos@riseup.net \
    --cc=1864955@bugs.launchpad.net \
    --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).