From: Romain Beauxis <toots@rastageeks.org>
To: caml-list@yquem.inria.fr
Subject: Re: [Caml-list] Re: The OCaml Community (aka back from the Developer Days)
Date: Mon, 28 Jan 2008 16:39:57 +0100 [thread overview]
Message-ID: <200801281639.57684.toots@rastageeks.org> (raw)
In-Reply-To: <slrnfprqe7.hmr.sylvain@gallu.homelinux.org>
Le Monday 28 January 2008 15:42:15 Sylvain Le Gall, vous avez écrit :
> On 28-01-2008, Romain Beauxis <toots@rastageeks.org> wrote:
> > Le Sunday 27 January 2008 14:09:22 David Teller, vous avez écrit :
> >
> > Another question is who will provide machines and means to acheive it.
> > In particular, a repository à la CPAN for modules would be a great thing,
> > but it would have to be supported by some structure...
>
> Indeed, you miss one point: my company will provide resource, if needed
> for it.
>
> For now, the computer is hired (OVH SuperPlan 08) but i don't have
> enough time to set it up.
>
> I only plan to provide a GForge/planets/SCM repository for now. But in
> the future, if anything else is required, i will be able to provide more
> things to it.
Wouldn't it be better to define a real structure where your company and others
may take part ?
For instance, kernel.org is run by a non-profit organisation, see:
http://www.kernel.org/nonprofit.html
The fact is that, if we don't setup strong and clear definitions of who's in
charge of what or don't define a common head for the community, what will
happen if any of the involved company/hacker/.... decide to split and
continue alone, or simply to shutdown one machine, or claim copyright, etc...
Again, I don't suspect any bad intention, but this is the only way to prevent
them, isn't it ?
Romain
next prev parent reply other threads:[~2008-01-28 15:40 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-27 13:09 David Teller
2008-01-28 0:38 ` [Caml-list] " Oliver Bandel
2008-01-28 11:27 ` David Teller
2008-01-28 13:42 ` Sylvain Le Gall
2008-01-28 16:38 ` [Caml-list] " Andrej Bauer
2008-01-29 0:26 ` Markus Mottl
2008-01-29 13:45 ` Gerd Stolpmann
2008-01-29 20:07 ` Markus Mottl
2008-01-30 13:04 ` Kuba Ober
2008-01-30 13:26 ` Jon Harrop
2008-01-30 14:17 ` Kuba Ober
2008-01-30 15:14 ` Jon Harrop
2008-01-30 16:26 ` Kuba Ober
2008-01-30 17:41 ` [Caml-list] Re: The OCaml Community (aka back fromthe " David Allsopp
2008-01-30 21:32 ` Kuba Ober
2008-01-30 13:10 ` [Caml-list] Re: The OCaml Community (aka back from the " Vincent Hanquez
2008-01-30 9:22 ` Sylvain Le Gall
2008-01-28 17:25 ` [Caml-list] " Peng Zang
2008-01-28 13:35 ` Sylvain Le Gall
2008-01-28 15:25 ` [Caml-list] " Jon Harrop
2008-01-28 15:43 ` Sylvain Le Gall
2008-01-28 19:49 ` [Caml-list] " Jon Harrop
2008-01-28 20:16 ` Hezekiah M. Carty
2008-01-28 20:35 ` Jon Harrop
2008-01-28 20:48 ` Hezekiah M. Carty
[not found] ` <6f9f8f4a0801281235s136f53b4qae8ec2c928f931c@mail.gmail.com>
2008-01-28 20:46 ` Hezekiah M. Carty
2008-01-28 21:29 ` Alterlib? (was "Re: The OCaml Community") Dario Teixeira
2008-01-28 21:48 ` [Caml-list] " blue storm
2008-01-28 13:52 ` [Caml-list] The OCaml Community (aka back from the Developer Days) Romain Beauxis
2008-01-28 14:42 ` Sylvain Le Gall
2008-01-28 15:39 ` Romain Beauxis [this message]
2008-01-28 15:49 ` Sylvain Le Gall
2008-01-28 15:56 ` [Caml-list] " Romain Beauxis
2008-01-29 15:23 ` Stefano Zacchiroli
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=200801281639.57684.toots@rastageeks.org \
--to=toots@rastageeks.org \
--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