caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Romain Beauxis <toots@rastageeks.org>
To: caml-list@yquem.inria.fr
Subject: Re: [Caml-list] [OSR] Caml Community Code
Date: Thu, 31 Jan 2008 17:08:06 +0100	[thread overview]
Message-ID: <200801311708.06613.toots@rastageeks.org> (raw)
In-Reply-To: <b256a4c50801310757n4a9b3b48ja8738c0f4dd3a475@mail.gmail.com>

Le Thursday 31 January 2008 16:57:24 Jonathan Bryant, vous avez écrit :
> List,

	Hi !

> 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_.

It's a good idea, but it seems a duplicate of the ocamlcore.org on-going 
server announced by Sylvain..

So rather than creating another instance, it should be better to join efforts 
together, don't you think ?


Romain


  reply	other threads:[~2008-01-31 16:08 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-31 15:57 Jonathan Bryant
2008-01-31 16:08 ` Romain Beauxis [this message]
2008-01-31 16:23   ` [Caml-list] " Jonathan Bryant
2008-01-31 17:24     ` Sylvain Le Gall
2008-01-31 17:28       ` Sylvain Le Gall
2008-01-31 17:49       ` [Caml-list] " Jonathan Bryant
  -- strict thread matches above, loose matches on Subject: below --
2008-01-31 14:28 Jonathan Bryant
2008-01-31 16:25 ` [Caml-list] " blue storm
2008-01-31 20:53   ` Stefano Zacchiroli
2008-01-31 21:38     ` Jon Harrop
2008-02-01  8:13       ` Stefano Zacchiroli
2008-02-01  9:14         ` Jon Harrop
2008-02-01 13:56           ` Christopher L Conway
2008-02-01 18:07             ` Jon Harrop
2008-02-01 19:00               ` Jonathan Bryant
2008-02-01 19:49                 ` Vincent Hanquez
2008-02-01 20:41               ` Christopher L Conway
2008-02-04 14:35               ` Jean-Marc EBER
2008-02-04 17:35                 ` Jon Harrop
2008-01-31 17:47 ` Ashish Agarwal
2008-01-31 18:12   ` Jonathan Bryant
2008-02-01 17:26 ` David Allsopp
2008-02-01 18:27   ` Jonathan Bryant
2008-02-01 18:25     ` Jon Harrop
2008-02-03 12:21       ` David Teller

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200801311708.06613.toots@rastageeks.org \
    --to=toots@rastageeks.org \
    --cc=caml-list@yquem.inria.fr \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).