Re: [Gwt-openlayers-devl] moving to Bitbucket

[Farrukh N. <fa...@we...>]

First thanks Edwin for the valuable leadership you have provided to this 
project.
Sorry that I have been unable to contribute more to the project in a 
long time.

I never quite liked googlecode for my OS projects. So -1 on googlecode.
No direct experience with BitBucket but your arguments make sense.



On 02/14/2011 05:59 PM, Edwin Commandeur wrote:
> That's a fast response :)
>
> Google Code would be a no-go, because it is Subversion based and the
> GWT-OpenLayers code is now in a Mercurial repository. Since Bitbucket
> focuses on services around Mercurial, it seems like a natural choice.
> Also, Mercurial is far easier to use than SF for developers, and it is
> more social and easier for people to get involved.
>
> Greetings,
> Edwin Commandeur
>
> On 14 February 2011 23:50, Dave Koberstein<da...@da...>  wrote:
>> Sounds like a good plan.  I've been developing a lot of TODOs that I need to
>> implement one of these days.  So I can stay with std gwt-openlayers I've
>> taken to poking JSObject from my code with //TODO markers to clean up
>> later.  These are almost all just pulling up existing openlayers parameters
>> to gwt-openlayers.  So shouldn't be any surprises or controversy.  :)
>>
>> We might consider google code since there are many gwt projects there
>> already.  But if you prefer bitbucket, it will be nice to try out something
>> new.
>>
>> Dave
>>
>> On 2/14/2011 2:45 PM, Edwin Commandeur wrote:
>>
>> Dear GWT OpenLayers developers,
>>
>> In order to make better use of the distributed version control system
>> we are using I would like to propose to move the code over to
>> Bitbucket. I would see the following advantages:
>>
>> - Easy workflow for code contributions: Any Bitbucket user can fork,
>> submit code to their fork, and issue a pull request (versus the mails
>> with patches we get now)
>> - Hg repo works over https (which is easier to get going than SSH and
>> uses a port that is unlikely to be blocked by enterprise firewalls)
>> - Nicer online code browsing interface (whole Bitbucket interface is
>> clean and simple)
>> - Nice features like follow commits via RSS, of follow on Bitbucket
>> - Might attract even more developers, as Bitbucket is a social coding site.
>>
>> The static web pages, issue tracker, and downloadable artifacts can
>> all remain at SourceForge. Downloads could be offered both at SF and
>> Bitbucket.
>>
>> I have already made a fork that is on BitBucket to try stuff out:
>> https://bitbucket.org/ecommandeur/gwt-openlayers
>>
>> We might want to make a user gwtopenmaps on bitbucket and place
>> gwt-openlayers under that user. If everybody (at least al admins)
>> agree, then I will do that.
>>


-- 
Regards,
Farrukh Najmi

Web: http://www.wellfleetsoftware.com