All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eric Blake <eblake@redhat.com>
To: Programmingkid <programmingkidx@gmail.com>,
	"Daniel P. Berrange" <berrange@redhat.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
	qemu-devel qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] my attempt at new QEMU website
Date: Thu, 20 Oct 2016 10:05:58 -0500	[thread overview]
Message-ID: <77f57df1-eee7-e377-e80c-cf6d11f4bbbe@redhat.com> (raw)
In-Reply-To: <0485E6E4-B6E3-48FF-8AA5-BB6A459F2450@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1866 bytes --]

On 10/20/2016 08:57 AM, Programmingkid wrote:
>>> I'm thinking icons and logos for operating systems could be on the
>>> emulator's page that can run that emulator. Maybe a few links to HD
>>> image files of preinstalled operating systems would help the user too.
>>
>> Using official icons/logos from various OS vendors/products is likely to
>> stumble into trademark usage restrictions/problems, whereby you need to
>> get permission for usage from the trademark holder. As such it is best
>> to avoid using any logos unless they're clearly under a trademark rule
>> that allows us to use them.
> 
> So what you are saying is we can't display a Windows logo or an Apple logo? I am sure I have seen plenty of websites with these logos displayed. If we can't use the offical logo/icon, maybe someone could make an unofficial one.

[you may want to teach your mailer to wrap long lines]

You are correct that we don't want to risk displaying someone's logo,
because they could turn around and complain that their logo is only to
be used on products they endorse but that we don't meet their criteria
for endorsing.  In legal matters, it's better to ask permission first,
than to deal with fallout for violating terms, but since permission can
be lengthy to obtain and difficult to document, it's simpler to just
avoid the matter altogether.  But your suggestion to use an unofficial
logo is even worse - drawing one ourselves that is different than the
official logo is legally questionable because it infringes on the
trademark protections of the original.

Just because other sites are taking a legal risk doesn't mean that we
have to follow their ill-advised actions.  Or maybe those sites HAVE
obtained written permission.

-- 
Eric Blake   eblake redhat com    +1-919-301-3266
Libvirt virtualization library http://libvirt.org


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 604 bytes --]

  parent reply	other threads:[~2016-10-20 15:06 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.11411.1476878784.22740.qemu-devel@nongnu.org>
2016-10-19 19:54 ` [Qemu-devel] my attempt at new QEMU website Programmingkid
2016-10-19 20:46   ` Paolo Bonzini
2016-10-20  2:05     ` Fam Zheng
2016-10-20  8:30   ` Daniel P. Berrange
2016-10-20 12:56     ` Paolo Bonzini
2016-10-21  2:10       ` Programmingkid
2016-10-21  5:23         ` Stefan Weil
2016-10-21  9:22           ` Paolo Bonzini
2016-10-20 13:57     ` Programmingkid
2016-10-20 14:02       ` Daniel P. Berrange
2016-10-20 14:47       ` Peter Maydell
2016-10-20 15:05       ` Eric Blake [this message]
2016-10-19 10:53 Paolo Bonzini
2016-10-19 11:02 ` Daniel P. Berrange
2016-10-19 11:36   ` Alexander Graf
2016-10-19 11:46   ` Paolo Bonzini
2016-10-19 12:07 ` Lluís Vilanova
2016-10-19 12:19   ` Paolo Bonzini
2016-10-20  2:14 ` Fam Zheng
2016-10-20 12:06   ` Paolo Bonzini
2016-10-20  6:43 ` Thomas Huth
2016-10-20 12:16   ` Paolo Bonzini
2016-10-20 13:23     ` Daniel P. Berrange
2016-10-21 13:34 ` Daniel P. Berrange

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=77f57df1-eee7-e377-e80c-cf6d11f4bbbe@redhat.com \
    --to=eblake@redhat.com \
    --cc=berrange@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=programmingkidx@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.