From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail2-relais-roc.national.inria.fr (mail2-relais-roc.national.inria.fr [192.134.164.83]) by sympa.inria.fr (Postfix) with ESMTPS id EA69B7EE51 for ; Wed, 22 May 2013 14:34:29 +0200 (CEST) Received-SPF: None (mail2-smtp-roc.national.inria.fr: no sender authenticity information available from domain of oliver@first.in-berlin.de) identity=pra; client-ip=192.109.42.8; receiver=mail2-smtp-roc.national.inria.fr; envelope-from="oliver@first.in-berlin.de"; x-sender="oliver@first.in-berlin.de"; x-conformance=sidf_compatible Received-SPF: None (mail2-smtp-roc.national.inria.fr: no sender authenticity information available from domain of oliver@first.in-berlin.de) identity=mailfrom; client-ip=192.109.42.8; receiver=mail2-smtp-roc.national.inria.fr; envelope-from="oliver@first.in-berlin.de"; x-sender="oliver@first.in-berlin.de"; x-conformance=sidf_compatible Received-SPF: None (mail2-smtp-roc.national.inria.fr: no sender authenticity information available from domain of postmaster@einhorn.in-berlin.de) identity=helo; client-ip=192.109.42.8; receiver=mail2-smtp-roc.national.inria.fr; envelope-from="oliver@first.in-berlin.de"; x-sender="postmaster@einhorn.in-berlin.de"; x-conformance=sidf_compatible X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AqYBAGa6nFHAbSoIlGdsb2JhbABahnO5DoYmFg4BAQEBCQsJCRQEJIJNehECBSECEQUYiFEEmlaOZpFSFoEQjhGCKzJhA48EiDOUUg X-IPAS-Result: AqYBAGa6nFHAbSoIlGdsb2JhbABahnO5DoYmFg4BAQEBCQsJCRQEJIJNehECBSECEQUYiFEEmlaOZpFSFoEQjhGCKzJhA48EiDOUUg X-IronPort-AV: E=Sophos;i="4.87,719,1363129200"; d="scan'208";a="18491012" Received: from einhorn.in-berlin.de ([192.109.42.8]) by mail2-smtp-roc.national.inria.fr with ESMTP/TLS/DHE-RSA-AES256-SHA; 22 May 2013 14:34:29 +0200 X-Envelope-From: oliver@first.in-berlin.de X-Envelope-To: Received: from first (e178001147.adsl.alicedsl.de [85.178.1.147]) (authenticated bits=0) by einhorn.in-berlin.de (8.13.6/8.13.6/Debian-1) with ESMTP id r4MCYSFk006575 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for ; Wed, 22 May 2013 14:34:28 +0200 Received: by first (Postfix, from userid 1000) id 1855B154066B; Wed, 22 May 2013 14:34:27 +0200 (CEST) Date: Wed, 22 May 2013 14:34:27 +0200 From: oliver To: caml-list@inria.fr Message-ID: <20130522123427.GA1894@siouxsie> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline User-Agent: Mutt/1.5.20 (2009-06-14) X-Scanned-By: MIMEDefang_at_IN-Berlin_e.V. on 192.109.42.8 Subject: [Caml-list] Licenses - Confusion Hello, I did publish one of my tools as GPLv3. It is written in OCaml. Now I saw at another project, that there is the need for an "OCaml exception" regarding linking. If thats true I may have missed a crucial points when thinking about the license for tools written in OCaml. I'm not a lwayer, and all that licenses stuff is rather+ annoying and confusing to me. That OCaml code needs special treatment here, even OCaml is shipped even with Debian, who surely would not accept GPL-violating stuff, is annoying. So, some questions came up now: - Which licenses can be used together with OCaml without changes? - Which licenses can be used together with added exceptions, and which exceptions are that? - In case of needed exceptions, where to find "ready-to-use"-versions of these licenses? - How to handle a project that already was published under a license that does not match 1:1 with OCaml licenses? It's not possible to delete any copy someone did of it already. Also it's not possible to sed all those people a message, to inform them that the license must be modified. Also I'm not sure how this could work, because the license came with the software at one time, and the correction comes later. Regarding the third point: it would be a good idea to provide "ready to use" licenses, which include the exceptions, instead of lawyer-compatible (but not necessarily programmer-compatible) explanations with many if-then-else's. Ciao, Oliver