[OpenLayers-Dev] GitHub straw poll

[Bouiaw]

Just a quick advise since we (OpenScales developers) have tested a lot
3 alternatives : Git, Mercurial or SVN : please test 3 solutions,
don't make your choice based on other people feedbacks only !

Before testing both DVCS tools in detail, I was clearly in favor of
Git. Github is widely used and sexy, big projects like Eclipse are
moving on it, I was sure that this should be the right choice for us.

Since we have Mercurial pushers, we decided to test both solutions
with same developers on a sample project. At the beginning, it was
difficult to admit but Mercurial was clearly the winner.

Reasons for our choice :
 - Simplicity
 - Subversion users learning curve
 - Windows support
 - Eclipse integration quality (hgEclipse)
 - HTTP proxy compliance for push

We also use used last release of SVN (1.6.9) but Git/Mercurial are a
magnitude of order better.

Regards,
Bouiaw

On Tue, Apr 20, 2010 at 2:57 PM, Bart van den Eijnden <bartvde at osgis.nl> wrote:
> Hey Tim,
>
> since I don't have any hands-on experience with Git, I can't really form a good opinion on this.
>
> For me the current model has no limitations, but I can assume that for some people new to OpenLayers it has.
>
> Best regards,
> Bart
>
> On Apr 17, 2010, at 1:22 AM, Tim Schaub wrote:
>
>> Hey-
>>
>> In advance of our infrastructure meeting (time TBD), I thought I'd take
>> a poll for the heck of it.
>>
>> Would people be in favor of or opposed to moving the OpenLayers
>> repository to GitHub?
>>
>> If the developers are interested in a change like this (even if it is
>> not until 3.0) we could create a PSC managed account called openlayers
>> and put whatever projects (e.g. website, openlayers) under that.
>> Anybody could fork.  "Core" committers would become collaborators on the
>> openlayers account.
>>
>> If we go with GitHub, we may or may not want to use their issue tracker.
>>  This is a separate topic for discussion (the github-trac plugin can
>> allow some integration of Trac and GitHub).
>>
>> If we go with GitHub, we could also discuss using their wiki and GitHub
>> pages for a static website (still hosted from http://openlayers.org).
>> These are also separate topics for discussion.
>>
>> I'm interested mainly to hear if people are generally in favor or
>> opposed to the idea of a repository move - and a move specifically to
>> GitHub for hosting.
>>
>> Tim
>>
>>
>> --
>> Tim Schaub
>> OpenGeo - http://opengeo.org
>> Expert service straight from the developers.
>> _______________________________________________
>> Dev mailing list
>> Dev at openlayers.org
>> http://openlayers.org/mailman/listinfo/dev
>>
>
> _______________________________________________
> Dev mailing list
> Dev at openlayers.org
> http://openlayers.org/mailman/listinfo/dev
>