[Live-demo] Re: Dropbox on GISVM for script sharing

[Ricardo Pinho]

Cameron,

Thats another perspective. I suppose you pretend to create a sync-update of GISVM.
I see it to become a very heavy network activity solution, and a very complex thing to implement and work!

For that I guess we can alternately create  an Ubuntu Synaptic package  repository at OSGeo...

We could also use rsync instead of Dropbox for sync the script folder.
But it lacks GUI and user friendly interface!!

There is also Ubuntu One, new product.
https://ubuntuone.com/

Limited to Ubuntu Machines! Windows and MAC excluded?!


Cheers,
Ricardo


----- Mensagem original ----
De: Cameron Shorter <cameron.shorter at lisasoft.com>
Para: Hamish <hamish_b at yahoo.com>
Cc: "live-demo at lists.osgeo.org" <live-demo at lists.osgeo.org>; Ricardo Pinho <rpinho_eng at yahoo.com.br>
Enviadas: Quarta-feira, 2 de Setembro de 2009 8:53:53
Assunto: Re: [Live-demo] Re: Dropbox on GISVM for script sharing

My hope is that we can use dropbox, (or rsync+server or similar), to 
syncronise all directories where applications are installed.

Ie:
/usr
/etc
/home
etc.

It is of little value to use dropbox for the install_<project>.sh 
scripts, which as hamish points out is much better handled by 
subversion, as we are doing already.


Hamish wrote:
> Ricardo wrote:
>  
>> I really think that we should implement a synchronized
>> folder inside GISVM so that we could easily share and update
>> the install scripts we are making.
>>
>> The idea is to use the multi-platform engine: Dropbox.
>> http://www.getdropbox.com/
>>    
>
> I have no problem with adding a dropbox per se, it's a fine idea.
> But for the script development specifically, IMO the most sane approach
> it to keep it in a single dedicated place.
>
> The whole point of SVN is to handle distributed source code management
> without it becoming fragmented and out of sync. Also the revision control
> and logs it gives are really really important when you are trying to
> untangle some bug at some point in the future when short term memory
> has faded. (everyone is supplying useful commit comments, yes? :)
>
> I would suggest to keep a single SVN repository (either hosted at OSGeo
> or at GISVM's server, I don't really care as long as we don't dilute
> focus*) and make sure that everyone has write access to it. Public access
> from the internet with no accountability log is a no-go. Simply too many
> moronic vandals out there to deal with. All anyone has to do to get write
> access on the OSGeo livedvd SVN is create yourself an OSGeo ID and let us
> know what it is, it's very easy to add people.
>
> [*] this is the "divide" part of "divide and conquer", it's a trap.
>
>
> Keep an up to date copy on the GISVM side with
>   svn checkout https://svn.osgeo.org/osgeo/livedvd/gisvm/trunk/ osgeo_scripts
>
> then keep it in sync with
>   cd osgeo_scripts
>   svn up
>
> If you wish to develop some here, develop some there, then merge the two
> later, there are other SCM systems such as Mercurial and Git which are
> very good at that. Subversion is geared to the single central host +
> multiple local development copies model.
>
> SCM is a wonderful wonderful thing and is well worth the learning curve.
> We should not abandon or nullify its best features. The payoff is huge,
> the pitfalls of not using it are many. made my point yet? :)
>
>
> cheers,
> Hamish
>
>
>
>      
>
> _______________________________________________
> Live-demo mailing list
> Live-demo at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/live-demo
>  


-- 
Cameron Shorter
Geospatial Systems Architect
Tel: +61 (0)2 8570 5050
Mob: +61 (0)419 142 254

Think Globally, Fix Locally
Geospatial Solutions enhanced with Open Standards and Open Source
http://www.lisasoft.com


      ____________________________________________________________________________________
Veja quais são os assuntos do momento no Yahoo! +Buscados
http://br.maisbuscados.yahoo.com