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=0.0 required=5.0 tests=AWL autolearn=disabled version=3.1.3 Received: from mail3-relais-sop.national.inria.fr (mail3-relais-sop.national.inria.fr [192.134.164.104]) by yquem.inria.fr (Postfix) with ESMTP id 9DAECBC6C for ; Wed, 30 Jan 2008 11:07:51 +0100 (CET) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: Ao8CAMbbn0fUnw6FhWdsb2JhbACCNo1xAQEBCAQGBwgTB59S X-IronPort-AV: E=Sophos;i="4.25,276,1199660400"; d="scan'208";a="8529955" Received: from pih-relay06.plus.net ([212.159.14.133]) by mail3-smtp-sop.national.inria.fr with ESMTP; 30 Jan 2008 11:07:51 +0100 Received: from [80.229.56.224] (helo=beast.local) by pih-relay06.plus.net with esmtp (Exim) id 1JK9rB-0000a1-Ko for caml-list@yquem.inria.fr; Wed, 30 Jan 2008 10:07:49 +0000 From: Jon Harrop Organization: Flying Frog Consultancy Ltd. To: caml-list@yquem.inria.fr Subject: Re: [Caml-list] Re: [OSR] OCaml Standard Recommandation Process Date: Wed, 30 Jan 2008 10:02:32 +0000 User-Agent: KMail/1.9.7 References: <1201440183.6302.27.camel@Blefuscu> <479F590D.6020706@gmail.com> In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200801301002.32738.jon@ffconsultancy.com> X-Plusnet-Relay: 25b9637f683bd887d1042f5bff22abc9 X-Spam: no; 0.00; ocaml:01 ocaml:01 model:01 inria's:01 frog:98 wrote:01 caml-list:01 center:95 upstream:04 fix:05 problem:05 anyway:05 inria:06 inria:06 standard:07 On Wednesday 30 January 2008 08:52:08 Sylvain Le Gall wrote: > I am not sure that i understand you. "Community distribution" should > just be "INRIA-Ocaml" + some others libraries. That is the current situation. > I am really not sure that anyone talk about anything else. Several people (including me) have been talking about other ideas because we can't fix OCaml without leaving that model. > In other word, what have been talked about is that ocaml INRIA distribution > will stay as is, but people can take it to put it into the center of a > larger distribution. That is the current situation. The problem is that INRIA's core OCaml distribution has many issues that we could address. To address them, we must create a new upstream that the community can maintain. > If i read you well, you are thinking that we can change things inside > ocaml INRIA distribution. That is not true. Which is why forking is our only option. > And anyway, if such a thing should happen, you will see a change in INRIA > license, that will permit you to do so. For now, this is not the case. INRIA cannot accept our contributions. -- Dr Jon D Harrop, Flying Frog Consultancy Ltd. http://www.ffconsultancy.com/products/?e