From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.1.3 (2006-06-01) on yquem.inria.fr X-Spam-Level: X-Spam-Status: No, score=0.2 required=5.0 tests=AWL autolearn=disabled version=3.1.3 Received: from mail3-relais-sop.national.inria.fr (mail3-relais-sop.national.inria.fr [192.134.164.104]) by yquem.inria.fr (Postfix) with ESMTP id A5CE2BC6C for ; Mon, 28 Jan 2008 14:52:41 +0100 (CET) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: Ao8CAEZtnUdYvxGE/2dsb2JhbACqdw X-IronPort-AV: E=Sophos;i="4.25,260,1199660400"; d="scan'208";a="8449403" Received: from www.rastageeks.org (HELO mail.rastageeks.org) ([88.191.17.132]) by mail3-smtp-sop.national.inria.fr with ESMTP; 28 Jan 2008 14:52:38 +0100 Received: from [192.168.112.144] (sphinx.lix.polytechnique.fr [129.104.11.1]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.rastageeks.org (Postfix) with ESMTP id 8EEA69D186 for ; Mon, 28 Jan 2008 14:52:37 +0100 (CET) From: Romain Beauxis To: caml-list@yquem.inria.fr Subject: Re: [Caml-list] The OCaml Community (aka back from the Developer Days) Date: Mon, 28 Jan 2008 14:52:26 +0100 User-Agent: KMail/1.9.7 References: <1201439362.6302.15.camel@Blefuscu> In-Reply-To: <1201439362.6302.15.camel@Blefuscu> MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Message-Id: <200801281452.26192.toots@rastageeks.org> X-Spam: no; 0.00; ocaml:01 ocaml:01 tarball:01 camomile:01 lablgtk:01 installers:01 cpan:01 wiki:01 interacts:01 cpan:01 binaries:01 caml-list:01 modules:02 groups:02 supported:02 Le Sunday 27 January 2008 14:09:22 David Teller, vous avez =C3=A9crit=C2=A0: > =C2=A0 =C2=A0 Dear list, Hi ! > =C2=A0During yesterday's OCaml Developer Day, a few important points have > been discussed. First and foremost, due to extremely limited manpower, > Inria does not intend to expand on the current OCaml distribution, nor > even to be in charge of an end-user distribution. Rather, Inria would > concentrate on the core language, in a distribution possibly smaller > than the current tarball, while the community should be in charge of > things such as > * a standard library distribution (e.g. ExtLib + Camomile + LablGtk > + ... ) > * binaries & installers > * testing > * code repositories (=C3=A0 la CPAN) > * deciding standard practices (e.g. Unicode) > * expanding the platform (e.g. development environments, DSLs) > * maintaining FAQs and tutorials > * evangelism... > > =C2=A0How and when all this should happen needs to be discussed. One tool= for > these discussions is the current mailing-list. Another tool is the Cocan > Wiki ( http://www.cocan.org ). > > =C2=A0One important thing: every task needs manpower. So please consider > volunteering. Sorry I couldn't attempt to the meeting, so perhaps my point has already be= en=20 discussed.. While I agree it's generally a good idea to rely on the community for=20 improvements, I think there's a wide difference between the lack of manpowe= r=20 and a community driven organisation. In particular, if the work are to be joined together, there shall be at som= e=20 point a concrete collaboration between INRIA and the communauty. It does not mean hiring people, but letting contributors participate in the= =20 core code too.=20 Because, if we say extensions are to be maintained by a community and then = we=20 need to wait and be confirmed by INRIA for each change that interacts with= =20 the core, then it might be a loss of energy for both groups, including=20 frustration... Another question is who will provide machines and means to acheive it. In particular, a repository =C3=A0 la CPAN for modules would be a great thi= ng, but=20 it would have to be supported by some structure... Not that I suspect any problem for now, but I think this has to be stated=20 clearly somewhere. Romain