[Live-demo] More ideas on collaborative development
rpinho_eng at yahoo.com.br
Tue Aug 25 05:00:51 PDT 2009
> 1. Write install scripts for each application, and put these scripts into subversion:
> I suggest we create bash install scripts for each application we want on the LiveDVD.
> These scripts will contain all the steps necessary to install a project.
> Ie, we would have one script for geoserver, one for mapserver, one for qgis, etc.
I agree, but it's more easily said then done... ;-)
Because some steps are not easily implemented with scripts. (at least for me!)
I'm thinking about config editing, for example...
> 2. Xubuntu:
> I suggest that we use Xubuntu as a basis for the
GISVM instead of Ubuntu,
> as it is specifically designed to run on a low
> but still runs all the Ubuntu packages.
I agree, no dough about it! ;-)
> 3. Wiki pages:
> There are a few too many LiveDVD wiki pages,
> which makes it hard for a newbie to find out what is current,
> and what is not.
> I suggest that we consolidate down to a few pages,
I agree! Not very skilled on wiki, but I will do my best! (I'm a fast learner!!!)
And who can take the first step into consolidation?
I suppose we will use wiki to discuss and propose changes to it.
Or shell we use this mailling list (Live-Demo)?
> 4. Central VM, which we rsync from:
> As mentioned earlier, I think
that we should set up a central virtual machine,
> probably on OSGeo
hardware, which we can all rsync from in order to
update the same virtual machine.
This is THE big issue! If we use virtual disks files (vmdk), they are 4 GB long...
I'm available for trying rsync with GISVM vmdk files. I've already made one available for Stefan...
Please configure it on the OSGeo box, asap...
But I must also suggest:
a) Amazon S3 engine! Very powerfull and speedy service. But a Payed one!
b) Drobox, a free and multiplataform sync engine (limited to 2-3 GB, for free)
If we 7zip the vmdk file we probably can reduce it under 2 GB...
Other suggestions and opinions are welcome...
And you can count on me!
----- Mensagem original ----
De: Cameron Shorter <cameron.shorter at gmail.com>
Para: live-demo at lists.osgeo.org
Enviadas: Domingo, 23 de Agosto de 2009 23:41:17
Assunto: [Live-demo] More ideas on collaborative development
I've been thinking hard about recent comments from Hamish, Massimo, Richardo and Stefan in relation to collaborative development of GISVM and LiveDVD. I've also been looking over the wiki pages and svn scripts and the GISVM to see what has been done already. After sleeping on this for a few nights, I wonder what people think about the following ideas:
1. Write install scripts for each application, and put these scripts into subversion:
I suggest we create bash install scripts for each application we want on the LiveDVD. These scripts will contain all the steps necessary to install a project. Ie, we would have one script for geoserver, one for mapserver, one for qgis, etc.
I notice that Massimo is part way here, having written the installation steps into the wiki at:
Stefan has created a similar wiki at:
Stefan has also been collecting these steps into scripts stored in subversion:
The key points here is:
* Community engagement: It would be straight forward for projects to write their own installation scripts. They can write them, then copy into svn, then let one of the VM team members apply to the latest virtual machine.
* The scripts will be kept under version control. (Following on from a comment from Hamish about the value of svn)
* If a .deb file exists for a project, all the better. The install script will just be one line long.
* These scripts could be integrated into a greater build script as we progress.
* I expect these bash scripts would eventually become the basis of a .deb file?
I suggest that we use Xubuntu as a basis for the GISVM instead of Ubuntu, as it is specifically designed to run on a low powered environment, but still runs all the Ubuntu packages.
3. Wiki pages:
There are a few too many LiveDVD wiki pages, which makes it hard for a newbie to find out what is current, and what is not.
I suggest that we consolidate down to a few pages, removing content from some pages and just providing a pointer to more recent pages.
4. Central VM, which we rsync from:
As mentioned earlier, I think that we should set up a central virtual machine, probably on OSGeo hardware, which we can all rsync from in order to collaboratively update the same virtual machine.
I'm interested to hear feedback on this, and I'd like to help out on some of these tasks, if they are considered worth following.
-- 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
Live-demo mailing list
Live-demo at lists.osgeo.org
Veja quais são os assuntos do momento no Yahoo! +Buscados
More information about the Osgeolive