From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Original-To: caml-list@sympa.inria.fr Delivered-To: caml-list@sympa.inria.fr Received: from mail3-relais-sop.national.inria.fr (mail3-relais-sop.national.inria.fr [192.134.164.104]) by sympa.inria.fr (Postfix) with ESMTPS id EA0B17EE6B for ; Wed, 4 Dec 2013 07:14:31 +0100 (CET) Received-SPF: None (mail3-smtp-sop.national.inria.fr: no sender authenticity information available from domain of berenger@riken.jp) identity=pra; client-ip=134.160.33.162; receiver=mail3-smtp-sop.national.inria.fr; envelope-from="berenger@riken.jp"; x-sender="berenger@riken.jp"; x-conformance=sidf_compatible Received-SPF: Pass (mail3-smtp-sop.national.inria.fr: domain of berenger@riken.jp designates 134.160.33.162 as permitted sender) identity=mailfrom; client-ip=134.160.33.162; receiver=mail3-smtp-sop.national.inria.fr; envelope-from="berenger@riken.jp"; x-sender="berenger@riken.jp"; x-conformance=sidf_compatible; x-record-type="v=spf1" Received-SPF: Pass (mail3-smtp-sop.national.inria.fr: domain of postmaster@postman.riken.jp designates 134.160.33.162 as permitted sender) identity=helo; client-ip=134.160.33.162; receiver=mail3-smtp-sop.national.inria.fr; envelope-from="berenger@riken.jp"; x-sender="postmaster@postman.riken.jp"; x-conformance=sidf_compatible; x-record-type="v=spf1" X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AnUEAC7HnlKGoCGih2dsb2JhbABagz+5R4E0DgEBAQoLCQcWKIIlAQEFOEARCxgJFg8JAwIBAgFFEwgBARCHbQ3BPo8FFoQdA4lAjlSBMIUVhhiIbg X-IPAS-Result: AnUEAC7HnlKGoCGih2dsb2JhbABagz+5R4E0DgEBAQoLCQcWKIIlAQEFOEARCxgJFg8JAwIBAgFFEwgBARCHbQ3BPo8FFoQdA4lAjlSBMIUVhhiIbg X-IronPort-AV: E=Sophos;i="4.93,822,1378850400"; d="scan'208";a="39199950" Received: from postman2.riken.jp (HELO postman.riken.jp) ([134.160.33.162]) by mail3-smtp-sop.national.inria.fr with ESMTP; 04 Dec 2013 07:14:30 +0100 Received: from postman.riken.jp (postman2.riken.jp [127.0.0.1]) by postman.riken.jp (Postfix) with SMTP id DEEF712606DB for ; Wed, 4 Dec 2013 15:14:26 +0900 (JST) Received: from [172.27.98.103] (rikad98.riken.jp [134.160.214.98]) by postman.riken.jp (Postfix) with ESMTPA id 9BA271270051 for ; Wed, 4 Dec 2013 15:14:26 +0900 (JST) Message-ID: <529EC842.7080702@riken.jp> Date: Wed, 04 Dec 2013 15:14:26 +0900 From: Francois Berenger User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.1.1 MIME-Version: 1.0 To: caml-list@inria.fr References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-PMX-Version: 6.0.0.2142326, Antispam-Engine: 2.7.2.2107409, Antispam-Data: 2013.12.4.60016 Subject: Re: [Caml-list] Licensing Camel and related Projects Under a Permissive License On 12/04/2013 02:30 PM, Suminda Dharmasena wrote: > Hi, > > Many of the major tools and implementation (tools within the > implementation also) have different licensing like QPL, GPL, LGPL. > > I am wondering if you community can discuss about perhaps using more > permissive licensing and come to a consensus on licensing guideline. > (Ultimately is it up to the IP holder how they license.) But some > discussion of re licensing would be beneficial to bring the many > projects under a permissive license. Maybe related to what you are asking: members of the Caml Consortium benefit from a special license. Cf. http://caml.inria.fr/consortium/license.en.html and http://caml.inria.fr/consortium/ -- Best regards, Francois Berenger.