From: skaller <skaller@users.sourceforge.net>
To: Xavier Leroy <Xavier.Leroy@inria.fr>
Cc: Brian Hurt <bhurt@spnz.org>,
tmp123@menta.net, ocaml ml <caml-list@inria.fr>
Subject: Re: [Caml-list] Sorted list
Date: Mon, 06 Aug 2007 09:47:23 +1000 [thread overview]
Message-ID: <1186357643.6523.76.camel@rosella.wigram> (raw)
In-Reply-To: <46B5FA25.7090001@inria.fr>
On Sun, 2007-08-05 at 18:26 +0200, Xavier Leroy wrote:
> In reply to Brian Hurt's comment:
> In reply to John Skaller's request:
>
> > Well, I would like to see a community process for selecting,
> > implementing, documenting and maintaining a set of good algorithms
>
> Why not. Care to start such a process yourself? Or more modestly
> joining one of the existing efforts for building additional OCaml
> libraries, like Extlib?
I am actually an extlib developer :)
> No way. Neither you nor us want to deal with our (admittedly slow)
> release cycle, with copyright assignments, etc. Moreover, we
> definitely do not have the time and manpower to build such an
> infrastructure, decide between conflicting proposals, etc. If a
> community is willing to make such an effort, it will have to
> self-organize.
The community can self-organise, but that won't get extra
components in the standard distro.
In the case of adding functions to existing modules,
a separate distribution isn't even possible.
Extlib tried both these things already. It may be a good
or bad library, but it failed in its goals; none of it
has got into the standard distro, not even the ideas.
> Bazaars are not run by priests.
No, but the priests let the people use their courtyard
to run them, happily accept contributions, and provide
blessings occasionally :)
--
John Skaller <skaller at users dot sf dot net>
Felix, successor to C++: http://felix.sf.net
next prev parent reply other threads:[~2007-08-05 23:49 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-04 9:35 tmp123
2007-08-04 10:00 ` [Caml-list] " Jon Harrop
2007-08-04 10:29 ` Philippe Wang
2007-08-04 11:22 ` skaller
2007-08-04 12:23 ` Philippe Wang
2007-08-04 13:39 ` skaller
2007-08-04 14:01 ` Philippe Wang
2007-08-04 14:45 ` skaller
2007-08-04 14:27 ` tmp123
2007-08-04 20:33 ` Christophe TROESTLER
2007-08-04 14:37 ` tmp123
2007-08-04 15:09 ` Brian Hurt
2007-08-04 15:42 ` skaller
2007-08-04 16:21 ` Richard Jones
2007-08-04 17:17 ` Brian Hurt
2007-08-04 18:24 ` skaller
2007-08-04 17:54 ` skaller
2007-08-04 19:16 ` Richard Jones
2007-08-05 16:22 ` David Allsopp
2007-08-05 16:41 ` Xavier Leroy
2007-08-05 17:01 ` David Allsopp
2007-08-04 17:35 ` Julien Moutinho
2007-08-04 18:04 ` skaller
2007-08-05 1:47 ` Jon Harrop
2007-08-05 11:44 ` Erik de Castro Lopo
2007-08-05 12:03 ` Jacques GARRIGUE
2007-08-05 12:31 ` Erik de Castro Lopo
2007-08-05 13:22 ` Richard Jones
2007-08-05 20:47 ` Erik de Castro Lopo
2007-08-05 13:17 ` Richard Jones
2007-08-05 16:26 ` Xavier Leroy
2007-08-05 23:47 ` skaller [this message]
2007-08-04 15:36 ` skaller
2007-08-04 15:17 ` tmp123
2007-08-12 12:05 ` Andrej Bauer
2007-08-04 12:15 ` Brian Hurt
2007-08-04 12:36 ` Brian Hurt
2007-08-04 13:49 ` skaller
2007-08-04 12:16 ` Daniel Bünzli
2007-08-04 12:58 ` Oliver Bandel
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=1186357643.6523.76.camel@rosella.wigram \
--to=skaller@users.sourceforge.net \
--cc=Xavier.Leroy@inria.fr \
--cc=bhurt@spnz.org \
--cc=caml-list@inria.fr \
--cc=tmp123@menta.net \
/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