caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
* [Caml-list] OCaml Forge and Github
@ 2013-09-29 17:13 Dario Teixeira
  2013-09-29 21:53 ` Fabrice Le Fessant
                   ` (2 more replies)
  0 siblings, 3 replies; 11+ messages in thread
From: Dario Teixeira @ 2013-09-29 17:13 UTC (permalink / raw)
  To: OCaml mailing-list

Hi,

I have a number of projects hosted on the OCaml Forge (thank you Sylvain!), 
and the hosting includes the Subversion repository for each project.  It is,
however, harder and harder to resist the allure of Github, particularly when
people sending me patches explicitly mention they would prefer to interact
through it.  I have no complaints about the Forge, though, and I find it a 
very useful service.  However, I would of course also like to accommodate
the Github crowd.

My default approach would be to convert and migrate the SVN repos to Github, 
keeping on the Forge only the webpage, file releases, and news.  But I'm
curious: how did other projects deal with this situation?  Is there some other
approach the community would find preferable?

Thanks for your time + best regards,
Dario Teixeira


^ permalink raw reply	[flat|nested] 11+ messages in thread

* Re: [Caml-list] OCaml Forge and Github
  2013-09-29 17:13 [Caml-list] OCaml Forge and Github Dario Teixeira
@ 2013-09-29 21:53 ` Fabrice Le Fessant
  2013-09-30  0:44   ` Sylvain Le Gall
  2013-09-30 10:36   ` Dario Teixeira
  2013-09-30  0:43 ` Anil Madhavapeddy
  2013-09-30 10:44 ` Paolo Donadeo
  2 siblings, 2 replies; 11+ messages in thread
From: Fabrice Le Fessant @ 2013-09-29 21:53 UTC (permalink / raw)
  To: Dario Teixeira; +Cc: OCaml mailing-list

Do you know if there is support for GIT on OCaml Forge ?

If such a support exists, you can just convert your SVN repo to GIT on
OCaml Forge, and mirror your new repo on GitHub. You can then decide
for example to work on the GIT repo of GitHub, and have a script
automatically update and push any modification on GitHub to OCaml
Forge. Git makes having several such repos very easy to administrate
and synchronise.

--Fabrice


On Sun, Sep 29, 2013 at 1:13 PM, Dario Teixeira <darioteixeira@yahoo.com> wrote:
> Hi,
>
> I have a number of projects hosted on the OCaml Forge (thank you Sylvain!),
> and the hosting includes the Subversion repository for each project.  It is,
> however, harder and harder to resist the allure of Github, particularly when
> people sending me patches explicitly mention they would prefer to interact
> through it.  I have no complaints about the Forge, though, and I find it a
> very useful service.  However, I would of course also like to accommodate
> the Github crowd.
>
> My default approach would be to convert and migrate the SVN repos to Github,
> keeping on the Forge only the webpage, file releases, and news.  But I'm
> curious: how did other projects deal with this situation?  Is there some other
> approach the community would find preferable?
>
> Thanks for your time + best regards,
> Dario Teixeira
>
>
> --
> Caml-list mailing list.  Subscription management and archives:
> https://sympa.inria.fr/sympa/arc/caml-list
> Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
> Bug reports: http://caml.inria.fr/bin/caml-bugs



-- 
Fabrice LE FESSANT
Chercheur en Informatique
INRIA Paris Rocquencourt -- OCamlPro
Programming Languages and Distributed Systems

^ permalink raw reply	[flat|nested] 11+ messages in thread

* Re: [Caml-list] OCaml Forge and Github
  2013-09-29 17:13 [Caml-list] OCaml Forge and Github Dario Teixeira
  2013-09-29 21:53 ` Fabrice Le Fessant
@ 2013-09-30  0:43 ` Anil Madhavapeddy
  2013-09-30 11:18   ` Dario Teixeira
  2013-09-30 10:44 ` Paolo Donadeo
  2 siblings, 1 reply; 11+ messages in thread
From: Anil Madhavapeddy @ 2013-09-30  0:43 UTC (permalink / raw)
  To: Dario Teixeira; +Cc: OCaml mailing-list

On 29 Sep 2013, at 18:13, Dario Teixeira <darioteixeira@yahoo.com> wrote:

> Hi,
> 
> I have a number of projects hosted on the OCaml Forge (thank you Sylvain!), 
> and the hosting includes the Subversion repository for each project.  It is,
> however, harder and harder to resist the allure of Github, particularly when
> people sending me patches explicitly mention they would prefer to interact
> through it.  I have no complaints about the Forge, though, and I find it a 
> very useful service.  However, I would of course also like to accommodate
> the Github crowd.
> 
> My default approach would be to convert and migrate the SVN repos to Github, 
> keeping on the Forge only the webpage, file releases, and news.  But I'm
> curious: how did other projects deal with this situation?  Is there some other
> approach the community would find preferable?

For me, the lure of GitHub is the level of automation and scripting that it
permits, so I prefer having all my packages on there simply so I can write
code to take care of release tedium (using the self-referential bindings at
https://github.com/avsm/ocaml-github).

There's also the network effect of using other people's tools that are built
on top of it.  For instance, I've just been playing with continuous integration
and refreshed Mike Lin's scripts; this lets you hook up executable tests that
run in the cloud (for free, for open source projects) in minutes of work:

http://anil.recoil.org/2013/09/30/travis-and-ocaml.html

An interesting feature of Travis is the post-success hook, which can be used
to trigger further work (such as deeper OCamlot tests, for OPAM).

You may be able to handle the Forge interaction through that mechanism, for
instance by doing an SVN commit from the Git push hook. I'm experimenting
with building ocamldoc for every package and pushing it to the gh-pages
branch (so that it's published on GitHub pages automatically on every push).

Incidentally, the scripts that convert the OCaml SVN to Git are available:
https://github.com/ocaml/ocaml.org-scripts/tree/master/vcs-sync/svn-ocaml

They are a bit smarter than the average SVN->Git convertor and create real
git branches for SVN tags.  This may help you if you wish to migrate from
SVN to Git (even if the Forge supports git, it probably requires this 
conversion process too).

-anil

^ permalink raw reply	[flat|nested] 11+ messages in thread

* Re: [Caml-list] OCaml Forge and Github
  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 10:36   ` Dario Teixeira
  1 sibling, 1 reply; 11+ messages in thread
From: Sylvain Le Gall @ 2013-09-30  0:44 UTC (permalink / raw)
  To: caml-list

On 29-09-2013, Fabrice Le Fessant <Fabrice.Le_fessant@inria.fr> wrote:
> Do you know if there is support for GIT on OCaml Forge ?
>

There is git on the forge.

I have some projects on github and tend to only host the source code on
either github or forge.ocamlcore.org. However for website, bug tracking,
mailing lists and releases I do prefer to continue having them on
forge.ocamlcore.org.

Regards
Sylvain

> If such a support exists, you can just convert your SVN repo to GIT on
> OCaml Forge, and mirror your new repo on GitHub. You can then decide
> for example to work on the GIT repo of GitHub, and have a script
> automatically update and push any modification on GitHub to OCaml
> Forge. Git makes having several such repos very easy to administrate
> and synchronise.
>
> --Fabrice
>
>
> On Sun, Sep 29, 2013 at 1:13 PM, Dario Teixeira <darioteixeira@yahoo.com> wrote:
>> Hi,
>>
>> I have a number of projects hosted on the OCaml Forge (thank you Sylvain!),
>> and the hosting includes the Subversion repository for each project.  It is,
>> however, harder and harder to resist the allure of Github, particularly when
>> people sending me patches explicitly mention they would prefer to interact
>> through it.  I have no complaints about the Forge, though, and I find it a
>> very useful service.  However, I would of course also like to accommodate
>> the Github crowd.
>>
>> My default approach would be to convert and migrate the SVN repos to Github,
>> keeping on the Forge only the webpage, file releases, and news.  But I'm
>> curious: how did other projects deal with this situation?  Is there some other
>> approach the community would find preferable?
>>
>> Thanks for your time + best regards,
>> Dario Teixeira
>>
>>
>> --
>> Caml-list mailing list.  Subscription management and archives:
>> https://sympa.inria.fr/sympa/arc/caml-list
>> Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
>> Bug reports: http://caml.inria.fr/bin/caml-bugs
>
>
>
> -- 
> Fabrice LE FESSANT
> Chercheur en Informatique
> INRIA Paris Rocquencourt -- OCamlPro
> Programming Languages and Distributed Systems
>
> -- 
> Caml-list mailing list.  Subscription management and archives:
> https://sympa.inria.fr/sympa/arc/caml-list
> Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
> Bug reports: http://caml.inria.fr/bin/caml-bugs
>

Cheers,
Sylvain Le Gall
-- 
Website:     http://sylvain.le-gall.net/
OCaml forge: http://forge.ocamlcore.org
OCaml blogs: http://planet.ocaml.org


^ permalink raw reply	[flat|nested] 11+ messages in thread

* Re: [Caml-list] OCaml Forge and Github
  2013-09-29 21:53 ` Fabrice Le Fessant
  2013-09-30  0:44   ` Sylvain Le Gall
@ 2013-09-30 10:36   ` Dario Teixeira
  1 sibling, 0 replies; 11+ messages in thread
From: Dario Teixeira @ 2013-09-30 10:36 UTC (permalink / raw)
  To: Fabrice Le Fessant; +Cc: OCaml mailing-list

Hi,
 

> Do you know if there is support for GIT on OCaml Forge ?
> 
> If such a support exists, you can just convert your SVN repo to GIT on
> OCaml Forge, and mirror your new repo on GitHub. You can then decide
> for example to work on the GIT repo of GitHub, and have a script
> automatically update and push any modification on GitHub to OCaml
> Forge. Git makes having several such repos very easy to administrate
> and synchronise.

Yes, I considered that as well.  However, I reckon it would just add entropy
without much added benefit.  I can easily imagine someone coming across
both repos and wondering if they are indeed kept in sync, or even if they are
from the same entity.  On the other hand, it would be nice if the project's
page on OCaml Forge also had a "SCM" tab, but one which simply linked
to Github.  I'll have to ask Sylvain...

Best regards,
Dario Teixeira

^ permalink raw reply	[flat|nested] 11+ messages in thread

* Re: [Caml-list] OCaml Forge and Github
  2013-09-29 17:13 [Caml-list] OCaml Forge and Github Dario Teixeira
  2013-09-29 21:53 ` Fabrice Le Fessant
  2013-09-30  0:43 ` Anil Madhavapeddy
@ 2013-09-30 10:44 ` Paolo Donadeo
  2013-09-30 10:48   ` Anil Madhavapeddy
  2 siblings, 1 reply; 11+ messages in thread
From: Paolo Donadeo @ 2013-09-30 10:44 UTC (permalink / raw)
  To: OCaml mailing list

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.

I removed the SCM tab from the forge, but I also have a GIT repo on
forge, and that repo is to be considered the "official" one.


-- 
Paolo

^ permalink raw reply	[flat|nested] 11+ messages in thread

* Re: [Caml-list] OCaml Forge and Github
  2013-09-30 10:44 ` Paolo Donadeo
@ 2013-09-30 10:48   ` Anil Madhavapeddy
  2013-09-30 14:20     ` Sylvain Le Gall
  0 siblings, 1 reply; 11+ messages in thread
From: Anil Madhavapeddy @ 2013-09-30 10:48 UTC (permalink / raw)
  To: Paolo Donadeo; +Cc: OCaml mailing list

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...

-anil


^ permalink raw reply	[flat|nested] 11+ messages in thread

* Re: [Caml-list] OCaml Forge and Github
  2013-09-30  0:43 ` Anil Madhavapeddy
@ 2013-09-30 11:18   ` Dario Teixeira
  0 siblings, 0 replies; 11+ messages in thread
From: Dario Teixeira @ 2013-09-30 11:18 UTC (permalink / raw)
  To: Anil Madhavapeddy; +Cc: OCaml mailing-list

Hi Anil,

> (...)

> You may be able to handle the Forge interaction through that mechanism, for
> instance by doing an SVN commit from the Git push hook. I'm experimenting
> with building ocamldoc for every package and pushing it to the gh-pages
> branch (so that it's published on GitHub pages automatically on every push).

Even if I decided to keep a repo on the Forge, I would migrate it to Git anyway.
Not only wouldn't I have to worry about possible issues in the Git -> SVN bridge,
it would be my little contribution to burying SVN...


> Incidentally, the scripts that convert the OCaml SVN to Git are available:
> https://github.com/ocaml/ocaml.org-scripts/tree/master/vcs-sync/svn-ocaml
> 
> They are a bit smarter than the average SVN->Git convertor and create real
> git branches for SVN tags.  This may help you if you wish to migrate from
> SVN to Git (even if the Forge supports git, it probably requires this 
> conversion process too).

I was just looking into tools to ease that process -- thanks!

Best regards,
Dario Teixeira

^ permalink raw reply	[flat|nested] 11+ messages in thread

* Re: [Caml-list] OCaml Forge and Github
  2013-09-30  0:44   ` Sylvain Le Gall
@ 2013-09-30 11:48     ` Dario Teixeira
  2013-09-30 12:39       ` Sylvain Le Gall
  0 siblings, 1 reply; 11+ messages in thread
From: Dario Teixeira @ 2013-09-30 11:48 UTC (permalink / raw)
  To: Sylvain Le Gall, caml-list

Hi Sylvain,

> I have some projects on github and tend to only host the source code on

> either github or forge.ocamlcore.org. However for website, bug tracking,
> mailing lists and releases I do prefer to continue having them on
> forge.ocamlcore.org.

Yeah, I'm also inclined to keep everything on the Forge, except for the
Git repo.  One question though: is it possible to keep the "SCM" tab
on the project's Forge page, but make its content just a small message
stating that the repo is hosted on Github, together with a link?

Best regards,
Dario Teixeira

^ permalink raw reply	[flat|nested] 11+ messages in thread

* Re: [Caml-list] OCaml Forge and Github
  2013-09-30 11:48     ` Dario Teixeira
@ 2013-09-30 12:39       ` Sylvain Le Gall
  0 siblings, 0 replies; 11+ messages in thread
From: Sylvain Le Gall @ 2013-09-30 12:39 UTC (permalink / raw)
  To: Dario Teixeira; +Cc: caml-list

Hi,

2013/9/30 Dario Teixeira <darioteixeira@yahoo.com>:
> Hi Sylvain,
>
>> I have some projects on github and tend to only host the source code on
>
>> either github or forge.ocamlcore.org. However for website, bug tracking,
>> mailing lists and releases I do prefer to continue having them on
>> forge.ocamlcore.org.
>
> Yeah, I'm also inclined to keep everything on the Forge, except for the
> Git repo.  One question though: is it possible to keep the "SCM" tab
> on the project's Forge page, but make its content just a small message
> stating that the repo is hosted on Github, together with a link?
>

I need to write an extension to FusionForge to do that and I don't
have enough time to do it right now. This is on my TODO list but with
low priority. What you can do is to add a link to the description that
points to your github account, best solution for now...

Regards
Sylvain

^ permalink raw reply	[flat|nested] 11+ messages in thread

* Re: [Caml-list] OCaml Forge and Github
  2013-09-30 10:48   ` Anil Madhavapeddy
@ 2013-09-30 14:20     ` Sylvain Le Gall
  0 siblings, 0 replies; 11+ messages in thread
From: Sylvain Le Gall @ 2013-09-30 14:20 UTC (permalink / raw)
  To: caml-list

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


^ permalink raw reply	[flat|nested] 11+ messages in thread

end of thread, other threads:[~2013-09-30 14:25 UTC | newest]

Thread overview: 11+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2013-09-29 17:13 [Caml-list] OCaml Forge and Github 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 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).