[Live-demo] Disk Priorities

[Cameron Shorter]

Alex Mandel wrote:
> Brian Hamlin wrote:
>   
>> Hi All-
>>
>>   re-reading the threads from the last days.. I have to say..
>> I'd prefer to see Natural Earth data, Marble add-ons and NASA WorldWind
>> on one disk
>> over Windows and Mac installers.. The WIndows and Mac installers could
>> possibly be a
>> second disk...
>>
>>  btw- I preemptively oppose having *only* windows installers  :-)
>>
>>  best regards from Berkeley, California
>>    -Brian
>>
>> ==
>> Brian Hamlin
>>     
>
> I think we need to do more research into how the disc is being used
> before we can make any such decisions. FYI, keeping the total iso size
> to 3.2-ish GB before adding the Windows/Mac installers actually helps
> ensure it will also fit on a 4GB USB flash drive with enough room to
> save files. I think we need to try our best to add things in the future
> with no net gain in file size, ie remove and clean things as we go, and
> optimize the data options.
>
> Natural Earth +1
> Marble add-ons +0 (not sure what it would add)
> NASA WorldWind -0 (Isn't it a programming api, not an actual
> application, or did people mean to include a sample application? I'm
> concerned it would be a behemoth of uncompiled code)
>
> Thanks,
> Alex
>
>   

+1 to Alex's comments.

For the next release I'd like to see a focus on the following (in no 
particular order):

* Set up one common dataset, and encourage all projects to make use of 
that dataset. The long term goal is to reduce/remove project specific 
datasets on the DVD. Natural Earth looks like a good candidate.

* Only have one version of Java/Tomcat installed. (We should be able to 
save space here)

Docs + Testing:
==========

* General tweaking of docs. Have one person tweak them all so they are 
consistant with a common formula, and emphasis. Also include one 
screenshot in the description page.
* Long term goal: Provide a series of screen shots walking through 
simple example usage of the application.

* Have testing pages increased to cover all core functionality for each 
project. Ie, if the project supports WFS, provide a test which queries 
WFS. (At this point, we don't need to cover the 100s of different ways a 
WFS could be queried.)

* Have projects reference results of internal testing they may have 
done, if it exists. (I expect this to be more of a placeholder for 
future releases)

* Have some cross project comparison information. In particular, make 
use of desktop comparison tables, browser comparison tables etc, which 
already exist, or are being built.

* Develop a powerpoint presentation of the LiveDVD which can be used by 
anyone wanting to show off GeoSpatial Open Source at their local 
conference or workplace. This could be complemented by a Video of the 
same powerpoint.

Infrastructure:
=========
* Formalise our project organisation somewhat, formalising some of our 
processes (similar to OSGeo project requirements). In particular:
** Set up our own svn group. (At the moment we share with general OSGeo 
documentation). We are maintaining Open Source code, and so should put 
in place the formalities required to confirm our packaging code follows 
the LGPL licence we have set down. Ie, get all committers to confirm 
they accept the LGPL licence and will abide by it.

** Set up a web page at: http://live.osgeo.org and copy our 
documentation here

** Formalise our decision making process by setting up a Project 
Steering Committee. We can cut and paste from other projects. Our 
decision making process will be pressured when we have to make hard 
decisions about what doesn't fit onto the DVD. In particular, we will 
likely be questioned by external projects wanting to get on the DVD, or 
wanting to add their large datasets onto the DVD.

-- 
Cameron Shorter
Geospatial Solutions Manager
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