From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([209.51.188.92]:56645) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1hNFAd-0001se-Bg for guix-patches@gnu.org; Sun, 05 May 2019 07:19:04 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1hNFAc-0007Va-IH for guix-patches@gnu.org; Sun, 05 May 2019 07:19:03 -0400 Received: from debbugs.gnu.org ([209.51.188.43]:39561) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1hNFAc-0007VO-Eo for guix-patches@gnu.org; Sun, 05 May 2019 07:19:02 -0400 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1hNFAc-0005GO-5C for guix-patches@gnu.org; Sun, 05 May 2019 07:19:02 -0400 Subject: [bug#35545] [PATCH] Add josm. Resent-Message-ID: Date: Sun, 5 May 2019 13:18:38 +0200 From: =?UTF-8?Q?Bj=C3=B6rn_?= =?UTF-8?Q?H=C3=B6fling?= Message-ID: <20190505131838.2ea2c6d9@alma-ubu> In-Reply-To: <20190503145820.606f37db@sybil.lepiller.eu> References: <20190503145820.606f37db@sybil.lepiller.eu> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; boundary="Sig_/=jSrgodNbtuf6K/JptOmVbV"; protocol="application/pgp-signature" List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-patches-bounces+kyle=kyleam.com@gnu.org Sender: "Guix-patches" To: Julien Lepiller Cc: 35545@debbugs.gnu.org --Sig_/=jSrgodNbtuf6K/JptOmVbV Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On Fri, 3 May 2019 14:58:36 +0200 Julien Lepiller wrote: > Hi guix! >=20 > this patch series adds josm, the Java OpenStreetMap editor, and its > dependencies. Hi Julien! This is great news to have a package for josm available! Thanks. I reviewed 1-5 until now and would need about a week to review the rest, if noone else gives an OK earlier. I know JOSM has plugins. Do you know anything about the licenses of these plugins? Should we/do we need to compile all of them from sources? Can we stick with the default Plugin-Repository? I'm thinking about FSDG-compatibility. Bj=C3=B6rn --Sig_/=jSrgodNbtuf6K/JptOmVbV Content-Type: application/pgp-signature Content-Description: OpenPGP digital signature -----BEGIN PGP SIGNATURE----- iF0EARECAB0WIQQiGUP0np8nb5SZM4K/KGy2WT5f/QUCXM7GjgAKCRC/KGy2WT5f /fkNAKCbK33/2RIPzlu0fdOZUnGlxYfqHQCdFk+vEW3Ufe+qLzt3bQrmLY0UEoc= =v4da -----END PGP SIGNATURE----- --Sig_/=jSrgodNbtuf6K/JptOmVbV--