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.0 required=5.0 tests=AWL,HTML_MESSAGE,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 2E3C3BC6C for ; Thu, 31 Jan 2008 18:48:03 +0100 (CET) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AgAAAKSYoUdIDvb1fGdsb2JhbACCOjaNMgEBCQQECQgTBZdigW8 X-IronPort-AV: E=Sophos;i="4.25,286,1199660400"; d="scan'208";a="22027271" Received: from ag-out-0708.google.com ([72.14.246.245]) by mail4-smtp-sop.national.inria.fr with ESMTP; 31 Jan 2008 18:48:01 +0100 Received: by ag-out-0708.google.com with SMTP id 31so781625aga.3 for ; Thu, 31 Jan 2008 09:48:00 -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:to:subject:in-reply-to:mime-version:content-type:references; bh=b1A6zy1uNRoSbcS7tHR4Aq+sBWPJdo0GWJB7N+OONpk=; b=o+U2Wys5DHzXdpl/gkjvtHQi4VBebudXlz1cl57LWSTo0WsAouVjQ5/xdpUHkFFByZQJrd6dd4FCAxthtOUc7i141GMNscalfVA7duAqDFOiq8vizT/Q6yqEtJZqHtM93FPsevkgm50xdYKvD5TgWd+zRhNf99BCtbseQvZdr6M= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references; b=I+xX+GrX8faDhVHHdKkJMYggeWt8s9Hjt4RVO96RG9bOnBWnP8w5XnxmcRPfAraAfoTDoQ3SkvZN5PuG5id789kNixA0PBg/hfH744eDzo90R7Vi6oyN2ufaKylNrrKlIQUcal8OJhpMHIN0cPcI/hQbn9wsV741KPYgOsc05vk= Received: by 10.141.28.12 with SMTP id f12mr1704643rvj.1.1201801679047; Thu, 31 Jan 2008 09:47:59 -0800 (PST) Received: by 10.141.195.15 with HTTP; Thu, 31 Jan 2008 09:47:58 -0800 (PST) Message-ID: Date: Thu, 31 Jan 2008 12:47:58 -0500 From: "Ashish Agarwal" To: "Caml Mailing List" Subject: Re: [Caml-list] [OSR] Caml Community Code In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_567_6921557.1201801678968" References: X-Spam: no; 0.00; ocaml:01 ocaml:01 camlp:01 syntax:01 syntax:01 parser:01 beginner's:01 bug:01 camlp:01 parser:01 beginner's:01 bug:01 1975:98 functioning:98 cherry:98 ------=_Part_567_6921557.1201801678968 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline > called Caml Community Code ... for community OCaml Is the language called Caml or OCaml? It would be nice to agree on that. 2008/1/31 Jonathan Bryant : > List, > > Despite all the great ideas on the [OSR] threads, we seem to be getting > nowhere and talking ourselves to death bickering about implementation > details of code that hasn't even been written yet. I think the only thing > we can agree on is that tools for use by the community should be written by > the community. Because of that, we need to start writing them: the best way > to find out what works is to try. > > I've created a SourceForge project called Caml Community Code here ( > http://sourceforge.net/projects/camlcode) where we can put any code for > community OCaml tools. The fact that we can't hack the OCaml language > itself (due to French copyright law) seems to have unfortunately caused the > community to not hack together on other tools _for_ the language. With this > project everyone can hack on the tools we'll (hopefully) end up using every > day, rather than having INRIA or one person try to build something that > satisfies everyone. If you have code for tools (I know someone at least has > some code for a package manager), please put it in the repository so we can > all see and work on it _as as community_. > > Regarding the package manager discussion, what we need is a few > functioning prototypes. Later we can go back and cherry pick features we > like and merge them down to just two to develop a little more, and finally > pick one. I also think we should have one CamlP4 grammar with all the > community's agreed upon "standard" syntax extensions (sort of a "new > revised" syntax?), a set of "standard" ocamlbuild plugins, and "standard" > interfaces (XML parser, etc.), all of which can be stored in the project as > well. > > I was waiting for the project to get approved before sending this out (it > just came through this morning), so I'll go ahead and make a temporary > directory layout. > > --Jonathan > > _______________________________________________ > Caml-list mailing list. Subscription management: > http://yquem.inria.fr/cgi-bin/mailman/listinfo/caml-list > Archives: http://caml.inria.fr > Beginner's list: http://groups.yahoo.com/group/ocaml_beginners > Bug reports: http://caml.inria.fr/bin/caml-bugs > > ------=_Part_567_6921557.1201801678968 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline > called Caml Community Code ... for community OCaml

Is the language called Caml or OCaml? It would be nice to agree on that.


2008/1/31 Jonathan Bryant <watersofmemory@gmail.com>:
List,

Despite all the great ideas on the [OSR] threads, we seem to be getting nowhere and talking ourselves to death bickering about implementation details of code that hasn't even been written yet.  I think the only thing we can agree on is that tools for use by the community should be written by the community.  Because of that, we need to start writing them: the best way to find out what works is to try.

I've created a SourceForge project called Caml Community Code here (http://sourceforge.net/projects/camlcode) where we can put any code for community OCaml tools.  The fact that we can't hack the OCaml language itself (due to French copyright law) seems to have unfortunately caused the community to not hack together on other tools _for_ the language.  With this project everyone can hack on the tools we'll (hopefully) end up using every day, rather than having INRIA or one person try to build something that satisfies everyone.  If you have code for tools (I know someone at least has some code for a package manager), please put it in the repository so we can all see and work on it _as as community_.

Regarding the package manager discussion, what we need is a few functioning prototypes.  Later we can go back and cherry pick features we like and merge them down to just two to develop a little more, and finally pick one.  I also think we should have one CamlP4 grammar with all the community's agreed upon "standard" syntax extensions (sort of a "new revised" syntax?), a set of "standard" ocamlbuild plugins, and "standard" interfaces (XML parser, etc.), all of which can be stored in the project as well.

I was waiting for the project to get approved before sending this out (it just came through this morning), so I'll go ahead and make a temporary directory layout.

--Jonathan

_______________________________________________
Caml-list mailing list. Subscription management:
http://yquem.inria.fr/cgi-bin/mailman/listinfo/caml-list
Archives: http://caml.inria.fr
Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
Bug reports: http://caml.inria.fr/bin/caml-bugs


------=_Part_567_6921557.1201801678968--