unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Alexandros Theodotou <alex@zrythm.org>
To: Tobias Geerinckx-Rice <me@tobias.gr>
Cc: "Ludovic Courtès" <ludo@gnu.org>,
	42473@debbugs.gnu.org,
	"GNU Guix maintainers" <guix-maintainers@gnu.org>,
	"Maxim Cournoyer" <maxim.cournoyer@gmail.com>
Subject: [bug#42473] [PATCH] gnu: zrythm: Update to 0.8.694.
Date: Sun, 26 Jul 2020 20:26:32 +0100	[thread overview]
Message-ID: <0f9e1795910b17cdd4d73f3b4848276f5da09889.camel@zrythm.org> (raw)
In-Reply-To: <871rkydx1j.fsf@nckx>

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

Hi,

On Sun, 2020-07-26 at 19:08 +0200, Tobias Geerinckx-Rice wrote:

> So does everyone else.
> 
> This implies that Guix has some special right but AFAICT the 
> linked URL does not grant a single exception to ‘unmodified 
> copies’.  What's the intention behind this hunk? 
>  
> Does the permission to ‘use the […] trademarks’ mean that we can 
> now use them however we want?  Presumably not, but then Guix 
> doesn't need any ‘written permission’ at all.  Your policy applies 
> to everyone.

Let me propose this instead, which is much clearer and gives a lot of
freedom to Guix for further modifications:

```
Guix, as released by the GNU project on 
http://git.savannah.gnu.org/cgit/guix.git, has permission to include
this Zrythm release (cryptographically signed by Alexandros Theodotou)
in its package repositories with any modifications necessary to
integrate Zrythm into Guix, provided that those modifications do not
change any of the intended functionalities of Zrythm or any text or
media presented to the user by the Zrythm user interface (including,
but not limited to URLs, images and message prompts). Alexandros
Theodotou reserves the right to revoke this trademark permission if the
current guidelines are not met, subject to Alexandros Theodotou's sole
discretion.
```

I can add this to the TRADEMARKS.md file (along with permissions for
other distros in the future) and re-release in a couple of days, and as
long as this permission notice is present in future releases, Guix will
have permission to make any of the above changes. The last sentence is
just a failsafe/safeguard for me and seems like it's standard in all
trademark permissions.

What do you think?

> 
> I'd love to see a trademark policy that doesn't mention Guix (or 
> *anyone*) by name but gives us (and *anyone*) the freedom to do 
> what we want to do: responsibly but independently maintain & 
> redistribute a well-integrated, CVE-free ZRythm package.  I'm 
> aware that I might be hoping for too much :-)

While I wish I could do that as well, there are no other similar
examples to follow afaik and IANAL so I don't know how to put that
wording in legal terms that cannot be abused (giving permission to
*anyone* to do things with a trademark beyond what basic trademark law
allows does not sound like a good idea), besides giving specific
permission to trusted projects like GNU Guix, so I try to stay on the
safe side.

Thanks,
Alex

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  reply	other threads:[~2020-07-26 19:28 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-22  8:34 [bug#42473] [PATCH] gnu: zrythm: Update to 0.8.694 Alexandros Theodotou
2020-07-22 22:16 ` Ludovic Courtès
2020-07-23  3:06   ` Maxim Cournoyer
2020-07-26 10:16     ` Alexandros Theodotou
2020-07-26 17:08       ` Tobias Geerinckx-Rice via Guix-patches via
2020-07-26 19:26         ` Alexandros Theodotou [this message]
2020-07-26 22:51           ` Leo Prikler
2020-09-10 10:22           ` Ludovic Courtès
2020-09-10 13:16             ` Alexandros Theodotou
2020-09-11 15:36               ` Ludovic Courtès
2020-09-11 16:52                 ` Alexandros Theodotou
2020-09-13 21:37                   ` bug#42473: " Ludovic Courtès

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

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=0f9e1795910b17cdd4d73f3b4848276f5da09889.camel@zrythm.org \
    --to=alex@zrythm.org \
    --cc=42473@debbugs.gnu.org \
    --cc=guix-maintainers@gnu.org \
    --cc=ludo@gnu.org \
    --cc=maxim.cournoyer@gmail.com \
    --cc=me@tobias.gr \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).