From: Sylvain Le Gall <sylvain@le-gall.net>
To: caml-list@inria.fr
Subject: Re: [Caml-list] OCaml Forge and Github
Date: Mon, 30 Sep 2013 14:20:32 +0000 (UTC) [thread overview]
Message-ID: <slrnl4j25p.ntq.sylvain@le-gall.net> (raw)
In-Reply-To: <8688F3A2-B981-4CD1-BF4D-6B2D2FF39EE0@recoil.org>
On 30-09-2013, Anil Madhavapeddy <anil@recoil.org> wrote:
> On 30 Sep 2013, at 11:44, Paolo Donadeo <p.donadeo@gmail.com> wrote:
>
>> On Sun, Sep 29, 2013 at 7:13 PM, Dario Teixeira <darioteixeira@yahoo.com> wrote:
>>> But I'm curious: how did other projects deal with this situation?
>>
>> I decided to host my project on the Forge, because I like the idea of
>> a community around a site/domain. So the home page is on the forge,
>> news and official downloads are there.
>>
>> But I also value the easy to use of GitHub, so the "working" repo is
>> on GitHub, and I also use the issue tracker.
>
> Note that these aren't mutually exclusive. In the Real World OCaml
> commenting system, we "hid" the GitHub backend from the user via some
> simple Javascript, and the same could potentially be done for the Forge.
>
> I'm afraid I have no idea how hackable the Forge software is, though...
>
It is somehow hackable but you need to do PHP programming, which seems
not like a popular choice among OCaml users ;-)
Cheers,
Sylvain Le Gall
--
Website: http://sylvain.le-gall.net/
OCaml forge: http://forge.ocamlcore.org
OCaml blogs: http://planet.ocaml.org
prev parent reply other threads:[~2013-09-30 14:25 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-29 17:13 Dario Teixeira
2013-09-29 21:53 ` Fabrice Le Fessant
2013-09-30 0:44 ` Sylvain Le Gall
2013-09-30 11:48 ` Dario Teixeira
2013-09-30 12:39 ` Sylvain Le Gall
2013-09-30 10:36 ` Dario Teixeira
2013-09-30 0:43 ` Anil Madhavapeddy
2013-09-30 11:18 ` Dario Teixeira
2013-09-30 10:44 ` Paolo Donadeo
2013-09-30 10:48 ` Anil Madhavapeddy
2013-09-30 14:20 ` Sylvain Le Gall [this message]
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=slrnl4j25p.ntq.sylvain@le-gall.net \
--to=sylvain@le-gall.net \
--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).