Mailing list for all users of the OCaml language and system.
 help / color / mirror / Atom feed
From: Pierre Weis <pierre.weis@inria.fr>
To: sgoldgaber@yahoo.com (Sergey Goldgaber)
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] Our shrinking Humps
Date: Wed, 2 Apr 2003 23:52:40 +0200 (MET DST)	[thread overview]
Message-ID: <200304022152.XAA12855@pauillac.inria.fr> (raw)
In-Reply-To: <20030331140430.57766.qmail@web11002.mail.yahoo.com> from Sergey Goldgaber at "Mar 31, 103 06:04:30 am"

> The Caml Humps are just a list of links.  There seems to be no real
> archive of contributed OCaml code.  Because of this the community is
> losing these contributions as linked web pages disappear (either
> because of web-site reorganization, or because the people maintaining
> those personal web sites have moved on to something else).
[...]
> I know there has been talk of a CPAN-like service, and think that would
> be great as well.  However, nothing so complex is needed for a simple
> centralized archive.  And it is an archive that is needed more. 
> Otherwise the community loses code.
> 
> I wish I had a server and bandwidth to donate, or I would just do this
> myself.  As it is I'm making an appeal to the community for solutions. 
> If there are no individuals or corporate entities in the OCaml
> community who are willing/able to provide the required resources,
> perhaps we could look at something like ibiblio http://ibiblio.org/ 
> Does anyone have any experience with this service?
> 
> 
>   --Sergey

INRIA can donate a server and the associated bandwidth. The problem is
then to find people that take care of this archive, since INRIA cannot
donate the additional man power to set up and maintain it.

Is there any volunteers ?

Best regards,

Pierre Weis

INRIA, Projet Cristal, Pierre.Weis@inria.fr, http://pauillac.inria.fr/~weis/


-------------------
To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr
Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/
Beginner's list: http://groups.yahoo.com/group/ocaml_beginners


  reply	other threads:[~2003-04-02 21:52 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-31 14:04 Sergey Goldgaber
2003-04-02 21:52 ` Pierre Weis [this message]
2003-04-02 22:42   ` Erik Arneson
2003-04-02 23:43   ` [Caml-list] the Komprehensive Objective caml Archive Network? art yerkes
2003-04-03  6:47     ` [Caml-list] " sylvain.le-gall
2003-04-04 19:06   ` [Caml-list] Our shrinking Humps Stefano Zacchiroli
2003-04-04 19:50     ` Alexander V. Voinov
2003-04-05  6:03       ` Sven Luther
2003-04-05  6:34         ` Sergey Goldgaber
2003-04-05  6:34         ` Sergey Goldgaber
2003-04-05 21:06         ` Pierre Weis
2003-04-06 12:25           ` Stefano Zacchiroli
2003-04-06 17:20           ` Fred Yankowski
2003-04-07  0:23             ` Jacques Garrigue
2003-04-07  7:15               ` Ed L Cashin
2003-04-08  9:21                 ` Martin Weber
2003-04-06  0:20         ` Vitaly Lugovsky
2003-04-06 14:01           ` Sergey Goldgaber
2003-04-05 22:00       ` Maxence Guesdon
2003-04-05  4:20     ` Sergey Goldgaber

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=200304022152.XAA12855@pauillac.inria.fr \
    --to=pierre.weis@inria.fr \
    --cc=caml-list@inria.fr \
    --cc=sgoldgaber@yahoo.com \
    /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