Bug 1360207 - adwaita-icon-theme included non-free wireless technology logo.
Summary: adwaita-icon-theme included non-free wireless technology logo.
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: adwaita-icon-theme
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Kalev Lember
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: FE-Legal
TreeView+ depends on / blocked
 
Reported: 2016-07-26 08:55 UTC by mejiko
Modified: 2016-07-29 17:34 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-07-29 17:34:45 UTC


Attachments (Terms of Use)

Description mejiko 2016-07-26 08:55:10 UTC
Hello.

adwaita-icon-theme included non-free content.


File List:

"/usr/share/icons/Adwaita/*/apps/bluetooth-symbolic.symbolic.png"
"/usr/share/icons/Adwaita/*/status/bluetooth-active-symbolic.symbolic.png"
"/usr/share/icons/Adwaita/*/status/bluetooth-disabled-symbolic.symbolic.png"

This icon is Bluetooth icon. but "Bluetooth" is trademark. and I think that this logo is copyrightable, It is non-free.

https://tsdr.uspto.gov/#caseNumber=76054633&caseType=SERIAL_NO&searchType=statusSearch

I suggests that resolve trademark and copyright problem.

Thanks.


Reference:

https://www.bluetooth.com/marketing-branding/brand-best-practices-guidelines?sc_lang=en

Comment 1 Tom "spot" Callaway 2016-07-29 17:34:45 UTC
It's not a copyright issue, really, it's a trademark issue.

Red Hat is a member of the Bluetooth SIG, so our use of the trademark in Fedora is in compliance with their rules. It is unlikely that the Bluetooth SIG would attempt to stop redistribution of Fedora by a downstream user for this.

It is possible that a different consumer of this other than Fedora may have an issue here, but as that is outside the scope of this concern, I cannot address it here. You may wish to file a bug with the adwaita theme upstream.


Note You need to log in before you can comment on or make changes to this bug.