From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on dcvr.yhbt.net X-Spam-Level: X-Spam-ASN: AS14061 206.189.176.0/20 X-Spam-Status: No, score=-3.6 required=3.0 tests=AWL,BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,SPF_HELO_PASS,SPF_PASS shortcircuit=no autolearn=ham autolearn_force=no version=3.4.2 Received: from box.jasonyundt.email (box.jasonyundt.email [206.189.182.84]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by dcvr.yhbt.net (Postfix) with ESMTPS id 1BBD01F4D7 for ; Sun, 24 Apr 2022 22:01:58 +0000 (UTC) Received: from authenticated-user (box.jasonyundt.email [206.189.182.84]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) (No client certificate requested) by box.jasonyundt.email (Postfix) with ESMTPSA id 7EFD67EA6C for ; Sun, 24 Apr 2022 18:01:55 -0400 (EDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=jasonyundt.email; s=mail; t=1650837716; bh=M1IrGgEXgk+uz1wwA8b3SLtN5QRf7bqyCJW2Hz9EgG0=; h=From:To:Subject:Date:From; b=k3ufV1k2bgmEoK9B3wARex845ZRPi/yU33Dr5120knlOWlhYup7dcBK+kFakPjCqI umfm8Cekcxr3tsKwzS5hhVW81IWwc8uRQ3C5v/HpUK4eGDmkGXKDlUPYQ4hZ2FD2Y8 NVjkmOYW1Mvddow/eLHM+TX8A1vP7gBUmdd6GaJq+usPle551wKKqKTp6p5PhX6uQ4 bVc6q6ABiO/P4ZkYVphk4defcCwF38e1lN7dKNLNzQFdbU3/ofsP2TTyvySO1O52cE ovOloJhP0CWvNMjYYCoGp6n10GGuaBHALvBY2CDqTT7/oulfLPxKvfKSosCqe2+2dN 88ugTC5/iTnng== From: Jason Yundt To: meta@public-inbox.org Subject: Difficulty following the AGPL for example systemd units Date: Sun, 24 Apr 2022 18:01:54 -0400 Message-ID: <2827814.e9J7NaK4W3@jason-lemur-pro> MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="UTF-8" List-Id: Hello=C2=B8 I=E2=80=99m trying to set up public-inbox-httpd on my Web site [1], and I w= ould like=20 to use the public-inbox-httpd systemd units from the examples folder [2] [3= ].=20 They don=E2=80=99t exactly fit my needs, so I would like to modify them bef= ore=20 deploying them. Here=E2=80=99s where I run into a problem: Section 0 of the GNU AGPL says =E2=80=9C"The Program" refers to any copyrig= htable work=20 licensed under this License.=E2=80=9D [4] For public-inbox, I think that th= e Program=20 is the entire public-inbox source tree [5]. In other words, I think that th= ose=20 two systemd units [2] [3] are part of the Program. Section 1 says =E2=80=9CThe Corresponding Source for a work in source code = form is=20 that same work.=E2=80=9D [6] I think that the work in this case is the enti= re public- inbox source tree. This means that the Corresponding Source is the entire=20 public-inbox source tree which in turn means that those two systemd units a= re=20 part of the Corresponding Source. Section 13 says =E2=80=9C[=E2=80=A6]if you modify the Program, your modifie= d version must=20 prominently offer all users interacting with it remotely through a computer= =20 network (if your version supports such interaction) an opportunity to recei= ve=20 the Corresponding Source of your version by providing access to the=20 Corresponding Source from a network server at no charge, through some stand= ard=20 or customary means of facilitating copying of software.=E2=80=9D [7] Since those two systemd units are part of the Program, when I modify them I= =E2=80=99m=20 modifying the Program. In other words, when I modify those two systemd unit= s,=20 I=E2=80=99ll have to follow that section 13 requirement. In other words, = =E2=80=9C[my] modified=20 version must prominently offer all users interacting with it remotely throu= gh a=20 computer network [=E2=80=A6] an opportunity to receive the Corresponding So= urce of=20 [my] version=E2=80=9D. The right way to do this would be to create a Git repo for my soft fork of= =20 public-inbox and change the mirror page [8]. The mirror page says =E2=80=9CAGPL code for this site: git clone https://public-inbox.org/public-inbox.git=E2=80=9D As far as I can tell, the only way for me to change that URL is to edit lib/ PublicInbox/WwwStream.pm. If I did that, then I would no longer be able to= =20 rely on my distro=E2=80=99s public-inbox packages. I would have to create m= y own=20 system for updating public-inbox. This makes using those example units annoyingly complicated. Here=E2=80=99s= some ideas=20 that I have for improving this situation: 1. Release those systemd units under something other than the GNU AGPL. 2. Add a public-inbox source tree option to config files. This option would= =20 allow you to override the =E2=80=9CAGPL code for this site=E2=80=9D URL. Either option would work and both are definitely not necessary. =46rom, Jason Yundt [1]: [2]: [3]: [4]: [5]: [6]: [7]: [8]: