From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from list by lists.gnu.org with archive (Exim 4.71) id 1dDQN2-0006EP-Vv for mharc-libreplanet-discuss@gnu.org; Wed, 24 May 2017 03:06:13 -0400 Received: from eggs.gnu.org ([2001:4830:134:3::10]:45248) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1dDQN0-0006Dz-5D for libreplanet-discuss@libreplanet.org; Wed, 24 May 2017 03:06:11 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1dDQMw-0002Je-5L for libreplanet-discuss@libreplanet.org; Wed, 24 May 2017 03:06:10 -0400 Received: from mx.kolabnow.com ([95.128.36.1]:33040 helo=mx-out03.mykolab.com) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1dDQMv-0002I2-LP for libreplanet-discuss@libreplanet.org; Wed, 24 May 2017 03:06:06 -0400 X-Virus-Scanned: amavisd-new at kolabnow.com Received: from mx03.mykolab.com (mx03.mykolab.com [10.20.7.101]) by mx-out03.mykolab.com (Postfix) with ESMTPS id BB1FE207DC; Wed, 24 May 2017 09:06:00 +0200 (CEST) Message-ID: <1495609556.5745.1.camel@nicorikken.eu> From: Nico Rikken To: libreplanet-discuss@libreplanet.org Cc: Aspasia Beneti Date: Wed, 24 May 2017 09:05:56 +0200 In-Reply-To: <11FB4C65-FB77-47F2-80D4-6A14A43C6121@dyne.org> References: <11FB4C65-FB77-47F2-80D4-6A14A43C6121@dyne.org> Content-Type: text/plain; charset="UTF-8" Mime-Version: 1.0 Content-Transfer-Encoding: 7bit X-detected-operating-system: by eggs.gnu.org: GNU/Linux 3.x [fuzzy] X-Received-From: 95.128.36.1 Subject: Re: Can we licence our Clojure (Eclipse Public License 1.0) project with the GNU AFFERO GENERAL PUBLIC LICENSE? X-BeenThere: libreplanet-discuss@libreplanet.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 May 2017 07:06:11 -0000 Hi Aspasia, Great to see you reaching out on this topic. Perhaps you can write on your findings, for all Clojure developers to take note? As you know I'm not developing under a free software license at work, but I did look into this topic as a Clojure developer. I specifically looked into the GPL, not even the AGPL. Let me break down your question to the different topics: JVM It seems the GNU Classpath was used at the start of OpenJDK, but later all was upstreamed to the OpenJDK project.[1] OpenJDK is licensed under the GPL, but with a linking exception for the classpath.[2] So I don't think the JVM blocks AGPL adoption. [1] https://en.wikipedia.org/wiki/OpenJDK#IcedTea_and_inclusion_in_soft ware_distributions [2] https://en.wikipedia.org/wiki/OpenJDK Libraries Going through your dependency list [0], I notice different licenses: EPL 1.0: Clojure, Timbre, Liberator, Autoclave, most others MIT: Ring, Cheshire EPL 1.0 & Apache 2.0: Monger AGPL 3.0: FXC (Dyne.org project) (I didn't look them all up) [0] https://github.com/PIENews/freecoin/blob/master/project.clj If I understand correctly, the linked libraries do effect the license compatibility, so the EPL/AGPL conflict is a real issue here. Macros As a lisp, Clojure uses macro's to modify the code at runtime. Then again, the macro's are code as well, so they'll also have a license attached to them. Maybe issues arise when the code is AGPL, but the macro modifying the code is EPL. To be fair, you shouldn't be using as much macro's anyway ;) The long game would be to have a AGPL-friendly lisp platform, with similar semantics to Clojure. This could be another reason why you'd want to avoid copyleft or dual-license any libraries you put out on Clojure. Projects I have looked into: - GNU Guile: Distant from Clojure, but a GNU project. - hylang.org: MIT-licensed Clojure-inspired lisp based on Python, by modifying the Abstract Syntax Tree. - Pixie: Clojure-inspired lisp based on RPython with C-interop. I hope others can chip in to share their view, as there are probably others asking a similar question. Kind regards, Nico Rikken (NL, FSFE)