>>
>>
>> 1 to Cameron's concise summary of the importance of simplifying and
>> coalescing around a single identity
>>
>> Outside of our small well informed community there is confusion re 2 brands,
>> one of which, FOSS4G, we don't even own apparently!
>>
>>
Cheers
Steven
>> On 12 Oct
Hi Jeff,
Thanks for information.
2015-10-12 21:18 GMT+09:00 Jeff McKenna :
> Watch the talks from earlier today at FOSS4G Tokyo, including Prof Rajan
> from OSGeo-India's keynote talk: http://t.co/KPinRUTDH4 Great to hear about
> OSGeo India chapter and its long history since 2007/2008.
Also, Y
I prefer to have the name FOSS4G. We can say it is the OSGeo conference..
On Mon, Oct 12, 2015 at 6:21 PM, Barry Rowlingson <
b.rowling...@lancaster.ac.uk> wrote:
> On Mon, Oct 12, 2015 at 4:11 PM, Marco Negretti
> wrote:
>
> > I think that rename the conference is the worst thing that we can do
On Mon, Oct 12, 2015 at 4:11 PM, Marco Negretti
wrote:
> I think that rename the conference is the worst thing that we can do:
> ten years of history trashed!
I now regret not putting "please refrain from hyperbole" in my
original posting. It's clearly not "the worst thing we could do". It
woul
Il 12/10/2015 01:00, Cameron Shorter ha scritto:
>
> I suggest the OSGeo board invite the OSGeo charter members to vote on:
>
> /Should future FOSS4G international conferences be called:/
> /1. FOSS4G/
> /2. OSGeo Conference/
> /
I think that rename the conference is the worst thing that we
Watch the talks from earlier today at FOSS4G Tokyo, including Prof Rajan
from OSGeo-India's keynote talk: http://t.co/KPinRUTDH4 Great to hear
about OSGeo India chapter and its long history since 2007/2008.
-jeff
___
Discuss mailing list
Discuss@
On Mon, Oct 12, 2015 at 01:06:09PM +0200, thomas bonfort wrote:
> Sandro,
> Both mapserver and proj.4 were migrated from trac/svn to git(hub). The
> plain git (not github) part can be done by "git svn" and the following
> script that creates a lookuptable that matches svn revisions with git
> shas.
Sandro,
Both mapserver and proj.4 were migrated from trac/svn to git(hub). The
plain git (not github) part can be done by "git svn" and the following
script that creates a lookuptable that matches svn revisions with git
shas. From that lookuptable you can update your trac db to replace
r1234 instan
I'm evaluating the cost of moving PostGIS code from SVN to GIT and
wondering how other projets (if any) dealt with this.
I think it would involve:
1) import SVN repo into a GIT one.
2) rewrite TRAC ticket references to point to corresponding GIT
hashes.
Did anyone do any of the above targe
Dear all,
After changing conference name, losing long-lasted brand value will be very
immediate and clear. However gaining the popularity of another firm brand will
take time and the effect will be vague.
Sometimes branding strategy doesn’t work as we imagine in our brain. Branding
is more a
10 matches
Mail list logo
