And, importantly, among the "more developers that already use it" are
all the active OpenLayers core committers.
On 3/8/11 5:30 AM, christopher.schm...@nokia.com wrote:
On Mar 8, 2011, at 2:36 AM, ext Rodolphe Quiedeville wrote:
Le 08/03/2011 08:10, Eric Lemoine a écrit :
[...]
Thank you C
On Mar 8, 2011, at 2:36 AM, ext Rodolphe Quiedeville wrote:
> Le 08/03/2011 08:10, Eric Lemoine a écrit :
> [...]
>>
>> Thank you Chris. Moving the trunk to Github sounds great to me. But we
>> indeed need to find a solution for the sandboxes. Keeping them in the
>> current SVN repo, and having
Le 08/03/2011 08:10, Eric Lemoine a écrit :
[...]
>
> Thank you Chris. Moving the trunk to Github sounds great to me. But we
> indeed need to find a solution for the sandboxes. Keeping them in the
> current SVN repo, and having some doc/tutorial explaining a working
> workflow for sandbox developm
On Saturday, February 26, 2011, wrote:
> Hi,
>
> This week, when working with OpenLayers, I found myself several
> times wishing that I had been more amenable to a switch to git as
> the primary revision control for OpenLayers. After some discussion
> with other developers, it seems we may be in
Hi Volker,
On Feb 27, 2011, at 14:33 , Volker Mische wrote:
> Hi,
>
> On 27.02.2011 08:20, christopher.schm...@nokia.com wrote:
>> The primary problem with Gitorious is that maintaining a list of actively
>> developed forks in a way that others can see it requires active core
>> developer mainte
Hi,
On 27.02.2011 08:20, christopher.schm...@nokia.com wrote:
The primary problem with Gitorious is that maintaining a list of actively
developed forks in a way that others can see it requires active core
developer maintenence (or even non-core developer maintenance). Anything
that we can get ri
On Feb 27, 2011, at 3:15 AM, ext Greg Troxel wrote:
> writes:
>
>> 1. It's all sharp edges. Anyone who uses git can probably tell
>>you horror stories of how they've cut themselves before on
>>some corner of git. This affects new developers who are unfamiliar
>>with OpenLayers and git
writes:
> 1. It's all sharp edges. Anyone who uses git can probably tell
> you horror stories of how they've cut themselves before on
> some corner of git. This affects new developers who are unfamiliar
> with OpenLayers and git the most, and other developers somewhat.
True, but by
Hi,
This week, when working with OpenLayers, I found myself several
times wishing that I had been more amenable to a switch to git as
the primary revision control for OpenLayers. After some discussion
with other developers, it seems we may be in a position where
a potential shift might be the rig
