Mailing list for all users of the OCaml language and system.
 help / color / mirror / Atom feed
From: "Jonathan Bryant" <jtbryant@valdosta.edu>
To: caml-list@yquem.inria.fr
Subject: [OSR] Caml Community Code
Date: Thu, 31 Jan 2008 10:57:24 -0500	[thread overview]
Message-ID: <b256a4c50801310757n4a9b3b48ja8738c0f4dd3a475@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1806 bytes --]

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

[-- Attachment #2: Type: text/html, Size: 2045 bytes --]

             reply	other threads:[~2008-01-31 15:57 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-31 15:57 Jonathan Bryant [this message]
2008-01-31 16:08 ` [Caml-list] " Romain Beauxis
2008-01-31 16:23   ` 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 21:38 ` [Caml-list] " 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 15:50         ` Sylvain Le Gall

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=b256a4c50801310757n4a9b3b48ja8738c0f4dd3a475@mail.gmail.com \
    --to=jtbryant@valdosta.edu \
    --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