From debbugs-submit-bounces@debbugs.gnu.org Sun Jul 26 15:27:04 2020 Received: (at 42473) by debbugs.gnu.org; 26 Jul 2020 19:27:04 +0000 Received: from localhost ([127.0.0.1]:53524 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1jzmIa-0006zP-FF for submit@debbugs.gnu.org; Sun, 26 Jul 2020 15:27:04 -0400 Received: from mout01.posteo.de ([185.67.36.141]:49929) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1jzmIY-0006ys-2x for 42473@debbugs.gnu.org; Sun, 26 Jul 2020 15:27:03 -0400 Received: from submission (posteo.de [89.146.220.130]) by mout01.posteo.de (Postfix) with ESMTPS id B7D65160062 for <42473@debbugs.gnu.org>; Sun, 26 Jul 2020 21:26:55 +0200 (CEST) Received: from customer (localhost [127.0.0.1]) by submission (posteo.de) with ESMTPSA id 4BFCcD1nLHz6tmG; Sun, 26 Jul 2020 21:26:51 +0200 (CEST) Message-ID: <0f9e1795910b17cdd4d73f3b4848276f5da09889.camel@zrythm.org> Subject: Re: [bug#42473] [PATCH] gnu: zrythm: Update to 0.8.694. From: Alexandros Theodotou To: Tobias Geerinckx-Rice Date: Sun, 26 Jul 2020 20:26:32 +0100 In-Reply-To: <871rkydx1j.fsf@nckx> References: <0e6300fea9caa1f9d7645c968a7c5b50d89f7b5c.camel@zrythm.org> <87k0yvfb60.fsf@gnu.org> <87wo2vdj6d.fsf@gmail.com> <871rkydx1j.fsf@nckx> Content-Type: multipart/signed; micalg="pgp-sha256"; protocol="application/pgp-signature"; boundary="=-Vjo3oZ2rAyOl3AYHpIkx" User-Agent: Evolution 3.34.2 MIME-Version: 1.0 X-Spam-Score: -2.3 (--) X-Debbugs-Envelope-To: 42473 Cc: Ludovic =?ISO-8859-1?Q?Court=E8s?= , 42473@debbugs.gnu.org, GNU Guix maintainers , Maxim Cournoyer X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: debbugs-submit-bounces@debbugs.gnu.org Sender: "Debbugs-submit" X-Spam-Score: -3.3 (---) --=-Vjo3oZ2rAyOl3AYHpIkx Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hi, On Sun, 2020-07-26 at 19:08 +0200, Tobias Geerinckx-Rice wrote: > So does everyone else. >=20 > This implies that Guix has some special right but AFAICT the=20 > linked URL does not grant a single exception to =E2=80=98unmodified=20 > copies=E2=80=99. What's the intention behind this hunk?=20 > =20 > Does the permission to =E2=80=98use the [=E2=80=A6] trademarks=E2=80=99 m= ean that we can=20 > now use them however we want? Presumably not, but then Guix=20 > doesn't need any =E2=80=98written permission=E2=80=99 at all. Your polic= y applies=20 > 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=20 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? >=20 > I'd love to see a trademark policy that doesn't mention Guix (or=20 > *anyone*) by name but gives us (and *anyone*) the freedom to do=20 > what we want to do: responsibly but independently maintain &=20 > redistribute a well-integrated, CVE-free ZRythm package. I'm=20 > 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 --=-Vjo3oZ2rAyOl3AYHpIkx Content-Type: application/pgp-signature; name="signature.asc" Content-Description: This is a digitally signed message part Content-Transfer-Encoding: 7bit -----BEGIN PGP SIGNATURE----- iQEzBAABCAAdFiEESBMjhK0999huJUuDAi6uQjE9cPMFAl8d2OgACgkQAi6uQjE9 cPMs0AgAgOTsTtohhsUmbhnKsLvgAPLUkCjYduIG8xzQUu+fnohNO9oJgRj1TapG 3H1/L8pvuVxibFdjre+f9LJUA9ZK5ydrzy23XvYATl2b63HPNiE3bVaM1KXr9YA/ ccvr3PQRoXlWTMc+BJwPOwAmbMMY7SRGfmiLoso5PmWTxzzGOZRB5Bxisc+AtITi 6p2WlSWjXK0dDhb1w/WkSAsdyr/Zdiv0buSHipUGtSc+70ZMsA/wrJ6XEWnOxBVI uf5IqO2JXASvLtuUfv5bU4M1+jh1zlgoco1tcXXvIA4NwVDvUni5qxb1pa9qKM8S HRFMQg4e5sWOVW8/80h5ofYADeGSPg== =vA85 -----END PGP SIGNATURE----- --=-Vjo3oZ2rAyOl3AYHpIkx--