unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Leo Prikler <leo.prikler@student.tugraz.at>
To: Alexandros Theodotou <alex@zrythm.org>,
	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: Mon, 27 Jul 2020 00:51:47 +0200	[thread overview]
Message-ID: <ff27a6e71d304c303df55cf96ed4be100062a208.camel@student.tugraz.at> (raw)
In-Reply-To: <0f9e1795910b17cdd4d73f3b4848276f5da09889.camel@zrythm.org>

Am Sonntag, den 26.07.2020, 20:26 +0100 schrieb Alexandros Theodotou:
> > 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.
IANAL either, but instead of
```
You may distribute unaltered copies of Zrythm that include the Zrythm
trademarks without express permission from Alexandros Theodotou.
```
and
```
However, if you make any changes to Zrythm, you may not redistribute
that product using any Zrythm trademark without Alexandros Theodotou’s
prior written consent.
```
you should write something like
```
You may distribute unaltered copies of Zrythm that include the Zrythm
trademarks without express permission from Alexandros Theodotou.
You may further distribute altered copies of Zrythm that include the
Zrythm trademarks, provided that alterations solely serve the purposes
of:
- porting Zrythm to a platform or free software distribution not
already supported by Zrythm as-is, OR
- fixing a bug in Zrythm, that has already been acknowledged by
Alexandros Theodotou or [a bigger authority, e.g. there's a CVE], OR
- ...
In any case, you must preserve [bla bla bla], also you must provide (a
link to)? the original sources.  If you make any other changes, you may
not redistribute that product...
```

Roughly meaning: If it already works on Ubuntu, you shan't patch it to
make it work on Ubuntu.  If it doesn't work on Gentoo, you can patch it
until it works on Gentoo and no further.  If Alexandros Theodotou has a
bugfix for something already published in Git, but you need to backport
that fix, you can do it.  If there's a CVE you can patch it.  If any of
those patches goes beyond integration/bugfixing, that's a violation.  I
personally believe, that this should be clear enough in most cases, but
it needs slightly better legalese.

Regards, Leo





  reply	other threads:[~2020-07-26 22:52 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
2020-07-26 22:51           ` Leo Prikler [this message]
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=ff27a6e71d304c303df55cf96ed4be100062a208.camel@student.tugraz.at \
    --to=leo.prikler@student.tugraz.at \
    --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).