From: Stefano Zacchiroli <zack@upsilon.cc>
To: caml-list@inria.fr
Subject: Re: [Caml-list] OCaml maintenance status / community fork
Date: Tue, 6 Dec 2011 13:02:46 +0100 [thread overview]
Message-ID: <20111206120246.GA23773@upsilon.cc> (raw)
In-Reply-To: <CAPFanBEJhuvkex-HHT_kk_kDbC9fv9+vt8QXDLt902j9ovK2jg@mail.gmail.com>
On Tue, Dec 06, 2011 at 12:40:07PM +0100, Gabriel Scherer wrote:
> I would consider Ocamlforge, with code hosting disabled and a central
> Gitorious repository as a very good choice for any OCaml free software
> project.
I concur. That said, Gitorious being Free Software, it is also possible
to set it up on alternative locations. I'm still an admin of OCamlForge,
although a *very* dormant one. But if there are enthusiastic volunteers
to work on the idea, I'll be happy to support them in an attempt to
install a Gitorious instance as part of the OCamlForge.
It that will prove to be feasible, we can ask FusionForge upstream to
add support for self-hosted Gitorious instances, as the current
FusionForge for Git is hardly useful at all (no support for multiple Git
repositories, no support for pull request, etc.). I believe this could
benefit the OCamlForge, as well as a very valuable addition to
FusionForge in general. (We can even dare asking the Caml Consortium to
sponsor the last part of the plan, but first we need to show the plan is
feasible ant that it has potential.)
Cheers.
--
Stefano Zacchiroli zack@{upsilon.cc,pps.jussieu.fr,debian.org} . o .
Maître de conférences ...... http://upsilon.cc/zack ...... . . o
Debian Project Leader ....... @zack on identi.ca ....... o o o
« the first rule of tautology club is the first rule of tautology club »
next prev parent reply other threads:[~2011-12-06 12:02 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-06 8:25 Benedikt Meurer
2011-12-06 9:17 ` Goswin von Brederlow
2011-12-06 10:08 ` Gaius Hammond
2011-12-06 9:31 ` rixed
2011-12-06 12:10 ` Benedikt Meurer
2011-12-06 9:42 ` Kakadu
2011-12-06 9:48 ` Joel Reymont
2011-12-06 10:51 ` Fabrice Le Fessant
2011-12-06 10:58 ` Stefano Zacchiroli
2011-12-06 16:12 ` Fabrice Le Fessant
2011-12-06 19:24 ` Mehdi Dogguy
2011-12-06 10:00 ` Gerd Stolpmann
2011-12-06 12:20 ` Benedikt Meurer
2011-12-06 10:35 ` Gabriel Scherer
2011-12-06 11:31 ` Gerd Stolpmann
2011-12-06 12:34 ` Benedikt Meurer
2011-12-15 18:49 ` Jérôme Benoit
2011-12-06 13:09 ` Goswin von Brederlow
2011-12-06 22:48 ` oliver
2011-12-07 7:23 ` Adrien
2011-12-06 11:40 ` Gabriel Scherer
2011-12-06 12:02 ` Stefano Zacchiroli [this message]
2011-12-06 12:16 ` Joel Reymont
2011-12-06 12:43 ` Stefano Zacchiroli
2011-12-06 12:27 ` François Bobot
2011-12-06 13:01 ` Benedikt Meurer
2011-12-06 13:52 ` ivan chollet
2011-12-06 14:42 ` Alexandre Pilkiewicz
2011-12-06 15:10 ` Gerd Stolpmann
2011-12-06 15:14 ` Yitzhak Mandelbaum
2011-12-06 15:24 ` Pierre-Alexandre Voye
2011-12-07 9:36 ` Goswin von Brederlow
2011-12-06 22:07 ` oliver
2011-12-07 9:39 ` Goswin von Brederlow
2011-12-07 20:42 ` oliver
[not found] <201112071100.pB7B0N8J020839@walapai.inria.fr>
2011-12-07 13:59 ` tools
2011-12-07 14:37 ` Jérémie Dimino
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=20111206120246.GA23773@upsilon.cc \
--to=zack@upsilon.cc \
--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;
as well as URLs for NNTP newsgroup(s).