After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 671253 - Include details about the "explicit permission from trademark owners"
Include details about the "explicit permission from trademark owners"
Status: RESOLVED FIXED
Product: gnome-boxes
Classification: Applications
Component: general
3.3.x (unsupported)
Other Linux
: Normal normal
: --
Assigned To: GNOME Boxes maintainer(s)
GNOME Boxes maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2012-03-03 13:33 UTC by Frederic Peters
Modified: 2016-03-31 13:54 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
configure option to disable logos (1.69 KB, patch)
2012-03-05 20:33 UTC, Zeeshan Ali
none Details | Review
Make non-free nature of logo files more explicit (1.12 KB, patch)
2012-03-05 20:33 UTC, Zeeshan Ali
committed Details | Review
configure option to disable logos (1.64 KB, patch)
2012-03-05 22:01 UTC, Zeeshan Ali
none Details | Review
configure option to disable logos (1.68 KB, patch)
2012-03-05 22:23 UTC, Zeeshan Ali
none Details | Review
configure option to disable logos (1.68 KB, patch)
2012-03-05 23:26 UTC, Zeeshan Ali
committed Details | Review

Description Frederic Peters 2012-03-03 13:33:00 UTC
COPYING.logos has this note:

  Unlike rest of the Boxes contents, product logos are not licensed under LGPLv2+
  Boxes has acquired explicit permission from trademark owners for the usage and
  shipment of their logos[1]. Following are the owners for each logo:

It has more indications about the usage of the Debian logo (free) and the Fedora logo (restrictions listed) but doesn't say anything about the other included logos (Ubuntu and openSUSE).

What are the explicit permissions? Would they also apply to forks? etc. it would be nice to clarify this.
Comment 1 Zeeshan Ali 2012-03-03 16:16:48 UTC
(In reply to comment #0) 
> What are the explicit permissions? Would they also apply to forks? etc. it
> would be nice to clarify this.

The explicit permission is for their usage and shipment in Boxes *only*. I should make that very clear in this file, yes! Do you think we should also provide a '--disable-logos' configure option that disables use and distribution of logos?
Comment 2 Frederic Peters 2012-03-03 17:40:13 UTC
Thinking about Debian, if the tarball ships with non free files, they will have to repack things to exclude those. In that sense a --disable-nonfree-logos would probably be considered useful. (but I do not know for sure).
Comment 3 Marc-Andre Lureau 2012-03-03 17:45:47 UTC
Zeeshan, wouldn't it make sense to download the logos with permissions when needed, like you used to propose instead of shipping them?
Comment 4 Zeeshan Ali 2012-03-03 17:50:48 UTC
(In reply to comment #3)
> Zeeshan, wouldn't it make sense to download the logos with permissions when
> needed, like you used to propose instead of shipping them?

Perhaps but that requires internet connection and I would hate to assume that when there is no need. We have permission to ship the logos as well so I think we are good with:

a. Making sure that license of logos is very clear stated
b. Providing easy options to remove the logos for distros (I'll add that soon).
Comment 5 Zeeshan Ali 2012-03-03 17:52:14 UTC
(In reply to comment #4)
> (In reply to comment #3)
> > Zeeshan, wouldn't it make sense to download the logos with permissions when
> > needed, like you used to propose instead of shipping them?
> 
> Perhaps but that requires internet connection and I would hate to assume that
> when there is no need. We have permission to ship the logos as well so I think
> we are good with:
> 
> a. Making sure that license of logos is very clear stated
> b. Providing easy options to remove the logos for distros (I'll add that soon).

Oh and if this gets hairy somehow, I'll go for the 'dynamic download' option (shouldn't be that hard to re-implement).
Comment 6 Zeeshan Ali 2012-03-05 20:33:45 UTC
Created attachment 209029 [details] [review]
configure option to disable logos

Provide a configure option to disable installation and build of non-free
logos.
Comment 7 Zeeshan Ali 2012-03-05 20:33:48 UTC
Created attachment 209030 [details] [review]
Make non-free nature of logo files more explicit
Comment 8 Zeeshan Ali 2012-03-05 22:01:23 UTC
Created attachment 209034 [details] [review]
configure option to disable logos

Provide a configure option to disable installation and build of non-free
logos.
Comment 9 Zeeshan Ali 2012-03-05 22:23:05 UTC
Created attachment 209035 [details] [review]
configure option to disable logos

Provide a configure option to disable installation and build of non-free
logos.
Comment 10 Christophe Fergeau 2012-03-05 22:47:28 UTC
Review of attachment 209035 [details] [review]:

Looks good apart from 2 minor comments

::: configure.ac
@@ +99,3 @@
+              AS_HELP_STRING([--enable-logos],
+                             [Enable distribution of non-free logos]),
+              [enable_logos=$enableval],

I don't think this is needed, but this doesn't hurt

@@ +100,3 @@
+                             [Enable distribution of non-free logos]),
+              [enable_logos=$enableval],
+              [enable_logos=true])

=yes would be more consistent with what autoconf does under the hood
Comment 11 Zeeshan Ali 2012-03-05 23:26:27 UTC
Created attachment 209040 [details] [review]
configure option to disable logos

Provide a configure option to disable installation and build of non-free
logos.
Comment 12 Zeeshan Ali 2012-03-05 23:33:40 UTC
Attachment 209030 [details] pushed as 9e5b274 - Make non-free nature of logo files more explicit
Attachment 209040 [details] pushed as b15944c - configure option to disable logos