From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.1.3 (2006-06-01) on yquem.inria.fr X-Spam-Level: * X-Spam-Status: No, score=1.2 required=5.0 tests=AWL,SPF_NEUTRAL autolearn=disabled version=3.1.3 Received: from mail4-relais-sop.national.inria.fr (mail4-relais-sop.national.inria.fr [192.134.164.105]) by yquem.inria.fr (Postfix) with ESMTP id 1AFA3BC6C for ; Tue, 29 Jan 2008 20:28:35 +0100 (CET) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AgAAACQNn0fRVYTwkmdsb2JhbACQJQEBAQEHBAQJChaXVIcm X-IronPort-AV: E=Sophos;i="4.25,271,1199660400"; d="scan'208";a="21950372" Received: from an-out-0708.google.com ([209.85.132.240]) by mail4-smtp-sop.national.inria.fr with ESMTP; 29 Jan 2008 20:28:34 +0100 Received: by an-out-0708.google.com with SMTP id b15so633036ana.102 for ; Tue, 29 Jan 2008 11:28:30 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:user-agent:mime-version:to:cc:subject:references:in-reply-to:content-type:content-transfer-encoding; bh=rQc/DgsFbEBX1aFckNcKe+U/07UijfZHRCpvZyiwNkQ=; b=rLrPxeP7jJzAFuRTKeCJYZugwHOX3EYWEoBBmLbOnW6KOJ6u7/kiIMSG2GFctrsOVNKoZ3N9h39mdSn9jx479JfLeTTGA4dwByyX26Gq7v4NgwZXIPXe2thlMFVPmoAQ2lQQC7T4qKOyjmPRb3A0h1XjO5msPF3fo6IeMu4XRh8= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject:references:in-reply-to:content-type:content-transfer-encoding; b=MtsZ557t7iZgMf28eilRaESoKvPlutShIb5QhQUm7HkVO+uqq2vTIgvVLusb48DXgYxjmyxzaOaNMjLkP6oAIapsyWIT1EEZojlBB4bnqXUn3F++1s9UgZ3bJc7BTw9NZQ43m30FZ/Avw4FiORog9odhjPk8aVQ85y5y+rUXuJA= Received: by 10.100.248.9 with SMTP id v9mr15547481anh.19.1201634910866; Tue, 29 Jan 2008 11:28:30 -0800 (PST) Received: from ?192.168.0.16? ( [70.242.64.39]) by mx.google.com with ESMTPS id d24sm11144715and.12.2008.01.29.11.28.28 (version=TLSv1/SSLv3 cipher=RC4-MD5); Tue, 29 Jan 2008 11:28:29 -0800 (PST) Message-ID: <479F7E59.1080207@gmail.com> Date: Tue, 29 Jan 2008 13:28:25 -0600 From: Edgar Friendly User-Agent: Thunderbird 2.0.0.6 (X11/20071022) MIME-Version: 1.0 To: "Grundy, Jim D" Cc: caml-list@yquem.inria.fr Subject: Re: [Caml-list] [OSR] Suggested Topic - License References: <5389061B65D50446B1783B97DFDB392D0894F5AE@orsmsx411.amr.corp.intel.com> In-Reply-To: <5389061B65D50446B1783B97DFDB392D0894F5AE@orsmsx411.amr.corp.intel.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Spam: no; 0.00; ocaml:01 lgpl:01 ocaml:01 stdlib:01 lgpl:01 stdlib:01 edgar:98 liberal:98 liberal:98 wrote:01 exception:01 exception:01 caml-list:01 minor:01 caml:02 Grundy, Jim D wrote: > One issue to be considered in a an external library standardization > process is the license under which libraries accepted to the standard > are made available. > > The obvious choice here is the same license as the OCaml standard > libraries themselves (LGPL V2 + linking exception). Except that this > isn't quite the same as the libraries distributed by INRIA. For those > libraries companies have the option of joining the Caml Consortium, in > which case they may license the standard libraries under a more liberal > (for my intended meaning of the word) 4-clause BSD-like license, which > is probably more appealing to many corporations. For example, you may > wish to consider if you would like ported versions of the libraries > released with F# and how the choice of license might make that possible > or not. It may be worth investigating simply adopting a more liberal > (again, for my intended meaning of the word) BSD-like (3 clause version > perhaps) to spur wider corporate adoption of the proposed standard. > > Just something to think about. > > Jim You have an interesting point. It seems quite reasonable that the licensing of extensions to the OCaml stdlib have at least as permissive license as LGPL V2 + linking exception. For those (7?) companies in the Caml Consortium, the difference comes down to... having to distribute source to modifications to the extended stdlib if they distribute code using those modifications. (Correct me if I'm wrong on this, IANAL.) I hear of most companies seriously using OCaml re-implementing their own standard libraries anyway, and the "cost" of sharing some of their improvements to community-developed extensions of stdlib seems quite minor to me. The easy workaround for these companies looks like not modifying the extended stdlib, but to use their own stdlib replacements (which they have license to) and to make the internal stdlib sufficient. That said, I hope these companies will not adopt such an adversarial relationship with the community developing an extended stdlib. I hope they contribute the gems of code they have in their internal stdlib to the community one, and gain benefits themselves when others using the community stdlib contribute their changes back to the community. E.