From: Tobias Geerinckx-Rice via Guix-patches via <guix-patches@gnu.org>
To: Alexandros Theodotou <alex@zrythm.org>
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 19:08:08 +0200 [thread overview]
Message-ID: <871rkydx1j.fsf@nckx> (raw)
In-Reply-To: <db4aa86c1499e0c191777694e9986612ebfd9162.camel@zrythm.org>
[-- Attachment #1: Type: text/plain, Size: 1199 bytes --]
Alexandros,
Thanks for discussing this!
+ ;; Zrythm contains trademarks and comes with a trademark policy
found in
+ ;; TRADMARKS.md inside the release distribution.
^^^^^^^^^
Typo.
Guix has
written
+ ;; permission to use the Zrythm trademarks:
+ ;; https://debbugs.gnu.org/cgi/bugreport.cgi?bug=42473
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.
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 :-)
Kind regards,
T G-R
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 227 bytes --]
next prev parent reply other threads:[~2020-07-26 17:09 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 [this message]
2020-07-26 19:26 ` Alexandros Theodotou
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=871rkydx1j.fsf@nckx \
--to=guix-patches@gnu.org \
--cc=42473@debbugs.gnu.org \
--cc=alex@zrythm.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).