From: Xavier Leroy <xavier.leroy@inria.fr>
To: Diego Olivier Fernandez Pons
<Diego-Olivier.FERNANDEZ-PONS@cicrp.jussieu.fr>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] Project Proposals
Date: Tue, 30 Apr 2002 11:16:57 +0200 [thread overview]
Message-ID: <20020430111657.A18782@pauillac.inria.fr> (raw)
In-Reply-To: <Pine.A32.3.95.1020422145838.119556A-100000@ibm1.cicrp.jussieu.fr>; from Diego-Olivier.FERNANDEZ-PONS@cicrp.jussieu.fr on Mon, Apr 22, 2002 at 03:07:17PM +0200
Some answers for Diego's questions about the new "Project proposals"
section of the Caml Hump:
- Nature of the proposed work: I think everything goes, from short
projects (a few modules) to more ambitious, long-term developments
(interfaces with large libraries, design and implementation of
complete frameworks, etc). Still, it's better if the project is
relatively self-contained and can be described relatively precisely.
E.g. "implementing the TLS protocol" is fine, but "design and
implement a new protocol for authentication and confidentiality over
the Web" is perhaps too imprecise (and too ambitious :-).
- Who can make proposals and how they are selected: everyone is
welcome to make proposals, either on this list or by mailing
hump@pauillac.inria.fr. Maxence Guesdon maintains the Humps,
and asks us (the Caml team) if there are questions on the
appropriateness of a topic.
- How to make a proposal: a one-liner plus a link to relevant
documentation or specification is fine, e.g. "a library to handle MIME
encoding and mailbox parsing" with a link to the relevant RFC. If you
wish to provide more details, you're most welcome to write a more
complete description on a Web page, and send us the URL.
- Should we include links to projects already in progress
(e.g. Bedouin): why not, if the organizers of these projects wish to
(maybe they have enough volunteers already).
Hope this answers your questions,
- Xavier Leroy
-------------------
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
next prev parent reply other threads:[~2002-04-30 9:17 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-22 13:07 Diego Olivier Fernandez Pons
2002-04-30 9:16 ` Xavier Leroy [this message]
2002-04-30 13:28 ` [Caml-list] OCaml packaging problems Vitaly Lugovsky
2002-04-30 15:08 ` Remi VANICAT
2002-04-30 18:04 ` Sven
2002-05-14 8:54 ` Xavier Leroy
2002-05-14 10:45 ` Stefano Zacchiroli
2002-05-14 15:46 ` Xavier Leroy
2002-05-14 11:39 ` Jacques Garrigue
2002-05-14 13:54 ` Michal Moskal
2002-05-14 23:28 ` Jacques Garrigue
2002-05-15 12:10 ` Sven Luther
2002-05-14 13:49 ` Michal Moskal
2002-05-14 22:52 ` Gerd Stolpmann
2002-05-15 1:18 ` Jacques Garrigue
2002-05-15 12:05 ` Sven Luther
2002-05-15 17:39 ` Vitaly Lugovsky
2002-05-16 7:11 ` Sven Luther
2002-05-16 10:24 ` Vitaly Lugovsky
2002-05-16 18:52 ` Stefano Zacchiroli
2002-05-17 16:05 ` Sven Luther
2002-05-17 19:31 ` Vitaly Lugovsky
2002-05-18 10:39 ` Michal Moskal
2002-05-21 19:54 ` Sven Luther
2002-06-13 15:50 ` Sven Luther
2002-06-18 12:57 ` Xavier Leroy
2002-06-18 13:32 ` Sven Luther
2002-06-18 20:04 ` Gerd Stolpmann
2002-06-19 6:33 ` Sven Luther
2002-06-19 11:09 ` Markus Mottl
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=20020430111657.A18782@pauillac.inria.fr \
--to=xavier.leroy@inria.fr \
--cc=Diego-Olivier.FERNANDEZ-PONS@cicrp.jussieu.fr \
--cc=caml-list@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