unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: Alexandros Theodotou <alex@zrythm.org>
Cc: 42473@debbugs.gnu.org, GNU Guix maintainers <guix-maintainers@gnu.org>
Subject: [bug#42473] [PATCH] gnu: zrythm: Update to 0.8.694.
Date: Thu, 23 Jul 2020 00:16:23 +0200	[thread overview]
Message-ID: <87k0yvfb60.fsf@gnu.org> (raw)
In-Reply-To: <0e6300fea9caa1f9d7645c968a7c5b50d89f7b5c.camel@zrythm.org> (Alexandros Theodotou's message of "Wed, 22 Jul 2020 09:34:45 +0100")

Hi Alexandros,

Alexandros Theodotou <alex@zrythm.org> skribis:

> This is actually 2 patches. The first updates libcyaml and the 2nd
> Zrythm. Note that I (Zrythm author) have added a trademark policy to
> Zrythm that says modified versions that include the trademarks require
> permission (as discussed on IRC with a few people):
> https://www.zrythm.org/en/trademarks.html
>
> I am not 100% sure if patching the xdg-open path counts as a modified
> version, but in any case this email is signed using the same key used
> to sign the release, so it can be interpreted as "written permission"
> to redistribute this.

OK.  Perhaps right above the ‘name’ field of the package, you could add
a link to the trademark policy above and state that Guix has a written
permission to use it, with a link to your message?  That way we’ll have
an audit trail.

> The FSDG allows trademarks from what I understand:

Your interpretation seems correct to me.

> So it is up to the maintainers to decide if they want to keep Zrythm as
> it is or rename it. Either way, I am happy with either decision,
> although I would prefer if you were OK with keeping the "Zrythm" name
> (as long as there's no patches to remove/add functionality or links to
> the Zrythm website or things like that).

I don’t see any reason not to keep “Zrythm” as things stand.

Thoughts anyone?  (Cc: maintainers.)

Apart from that, the patches LGTM!

Thank you,
Ludo’.




  reply	other threads:[~2020-07-22 22:17 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 [this message]
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
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=87k0yvfb60.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=42473@debbugs.gnu.org \
    --cc=alex@zrythm.org \
    --cc=guix-maintainers@gnu.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.
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).