<html>
<head>
</head>
<body style="margin-bottom: 1px; line-height: normal; margin-right: 4px; margin-left: 4px; font-variant: normal; margin-top: 4px">
<p style="margin-top: 0; margin-bottom: 0">
<font size="3" face="Comic Sans MS">All,</font> </p>
<br>
<p style="margin-top: 0; margin-bottom: 0">
<font size="3" face="Comic Sans MS">As I understand thing I need to fill out this questionaire:</font> </p>
<br>
<p style="margin-top: 0; margin-bottom: 0">
<i>Please email answers to these questions if you wish to propose including a new application on the OSGeo-Live distribution. The email should be sent to the OSGeo-Live list: <font color="#0000ff"><u><a href="http://lists.osgeo.org/mailman/listinfo/live-demo">http://lists.osgeo.org/mailman/listinfo/live-demo</a></u></font></i> </p>
<ul>
<li>
Please describe your application.
<ul>
<li>
What is its name?<font size="3" face="Comic Sans MS">GeoMoose</font> </li>
<li>
What is the home page URL?<font size="3" face="Comic Sans MS"></font><font size="3" color="#0000ff" face="Comic Sans MS"><u><a href="http://www.geomoose.org"><i>www.geomoose.org</i></a></u></font><font size="3" face="Comic Sans MS"></font> </li>
<li>
Which OSI approved Open Source Licence is used?<font size="3" face="Comic Sans MS"></font><font size="3" color="#0000ff" face="Comic Sans MS"><u><a href="http://www.geomoose.org/info/license.html"><i>http://www.geomoose.org/info/license.html</i></a></u></font><font size="3" face="Comic Sans MS"></font> </li>
<li>
What does the application do and how does it add value to the GeoSpatial stack of software?<font size="3" face="Comic Sans MS">It's intended as a Geo data oriented discovery tool. Any data, geo and/or tabluar, that needs to be referenced or looked up via a spatial context, is a candidate for being published via the GeoMoose interface. The data sources are all abstracted as well as any tools or other services that are attached to the interface. This allows each service or data source to be administered by an independent owner/author. Because of this abstraction design, the owner/author has complete control over how, when, and how often their data is published, and how all of it's cartographic features are presented. The abstraction also isolates each layer from every other, and one dead layer doesn't bring the whole system down, only that layer or service is broken.</font> </li>
</ul>
</li>
</ul>
<ul>
<li>
Stability is very important to us on OSGeo-Live. If a new user finds a bug in one application, it will tarnish the reputation of all other OSGeo-Live applications as well. Do you have a bug free, stable release, which has been rolled out to production in a number of locations? Please discuss the level of testing that your project has gone through, the size of the community that uses the application, and how long the project has had mature code.<font size="3" face="Comic Sans MS">Lot's of supposition to be inserted here. This question is a bit strict in some aspects and vague in others. The project has been on the incubation list at OSGEO since shortly after becoming Open-Sourced, See Ticket #147 (4 years ago).There exist a Dev and User email lists for the project. Bugs are generally reported via the lists and a trac system is in place if a formal bug needs to be reported. The GeoMoose product s in use in hundreds of locations, mainly in the US, but also worldwide. It's primarily been used in small local government installations, because of it's unique customization abilities, which were born from a local goverment, but recently has been implemented at some state level mapping sites. Other uses are being found for the application as well and it has become a well know application in it's own right.I'm not sure what "mature code" is supposed to mean exactly. The GeoMoose product is current at version 2.4 in stable form and has gone through regular release cycles as it has aged. Each release cycle has added functionality and also fixed bugs that were identified from previous cycles. Not application is complete bug free, and the Web environment also throws it's own curves into the mix. The new browser versions are a good example here. Not everything works in the new browsers as they used. Add in the fact that some browsers are mobile based, and the question of BUGs seems to lose some clarity. Is not having a capability in a certain browser a bug, or ?? Before the GeoMoose product went Open Source, it was a mature product. We've been using the same Version (v0.98) of the product in our office for 6 years now, and are planning on upgrading to the latest release as well as adding in some new functionality.</font> </li>
</ul>
<ul>
<li>
OSGeo-Live is targeted at applications that people can use rather than libraries. Does the application have a user interface (possibly a command line interface) that a user can interact with?<font size="3" face="Comic Sans MS">GeoMoose is a Map based User interface that is configured for Web Browser use. One note here, because of it's compact foot print and lack of dependencies on services, it can also be run a standalone fashion with no network available completely from a local storage location.</font> </li>
</ul>
<ul>
<li>
We give preference to OSGeo Incubated Projects, or Projects which are presented at <a class="external text" rel="nofollow" title="http://foss4g.org" href="http://foss4g.org">FOSS4G</a> conferences. If your project is involved in OSGeo Incubation, or has been selected to be presented at FOSS4G, then please mention it.<font size="3" face="Comic Sans MS">A Workshop on the GeoMoose product has been accepted for the FOSS4G in Denver.</font> </li>
</ul>
<ul>
<li>
With around 50 applications installed on OSGeo-Live, us core packagers do not have the time to liaise with every single project email list for each OSGeo-Live release. So we require a volunteer (or two) to take responsibility for liaising between OSGeo-Live and the project's communities. This volunteer will be responsible for ensuring the install scripts and English documentation are updated by someone for each OSGeo-Live release. Also test that the installed application and Quickstart documentation works as expected on release candidate releases of OSGeo-Live. Who will act as the project's liaison person.<font size="3" face="Comic Sans MS">Bob Basques</font> </li>
</ul>
<ul>
<li>
OSGeo-Live is Ubuntu Linux based. Our installation preference is:
<ol>
<li>
Install from UbuntuGIS or DebianGIS </li>
<li>
Install .deb files from a PPA </li>
<li>
Write a custom install script </li>
</ol>
</li>
</ul>
<p style="margin-top: 0; margin-bottom: 0">
Can you please discuss how your application will be installed.<font size="3" face="Comic Sans MS"></font> </p>
<br>
<p style="margin-top: 0; margin-bottom: 0">
<font size="3" face="Comic Sans MS">Base files for the GeoMoose product, either use an existing MapServer instance or include one of it's own, While MapServer is not a required component, it will provide far more variety potential in the uses of the interface than implementation without. I've scanned the LiveDVD install and see most other packages that GeoMoose might interact with as already being present. The bigger task will be in setting up the data sources for the LiveDVD sactioned data. Because of GeoMoose hertiage, that being originally written for a Local government, a corresponding demo should also be included with a cursory set of data. These already exist in operable for on the GeoMoose project page and should/could be ported to the LiveDVD for use along side of the DVD included datasets.</font> </p>
<ul>
<li>
We include Windows and Mac installers for some applications. Would you be wishing to include Windows and/or Mac installers?<font size="3" face="Comic Sans MS">I'm not entirely sure here, the Windows side of the quation has been to use MS4W, there are already installers on the GeoMoose site for MS4W. This will depend on how the workshop will be put together in the near term, but I anticipate that a windows installer will be included at some point.</font> </li>
</ul>
<ul>
<li>
OSGeo-Live is memory and disk constrained. Can the application run in 512 Meg of RAM?<font size="3" face="Comic Sans MS">Yes, very small footprint, very low on reseource usage.</font> </li>
</ul>
<ul>
<li>
How much disk space will be required to install the application and a suitable example application?<font size="3" face="Comic Sans MS">30 MG will install the V2.4 of GeoMoose with two local demos. Some slight increase in size to add in the LiveDVD data resources as well. </font> </li>
</ul>
<ul>
<li>
We aim to reduce disk space by having all applications make use of a common dataset. We encourage applications to make use of the example datasets already installed: </li>
</ul>
<p style="margin-top: 0; margin-bottom: 0">
<font color="#0000ff"><u><a href="http://wiki.osgeo.org/wiki/Live_GIS_Add_Project#Example_Datasets"><i>http://wiki.osgeo.org/wiki/Live_GIS_Add_Project#Example_Datasets</i></a></u></font> If another dataset would be more appropriate, please discuss here. Is it appropriate, to remove existing demo datasets which may already be included in the standard release.<font size="3" face="Comic Sans MS"></font> </p>
<br>
<p style="margin-top: 0; margin-bottom: 0">
<font size="3" face="Comic Sans MS">Every attempt will be made to utilize the included datasets. I see this as a longer term tweaking process as I would like to include examples of many different types of data sources, SHP files, Database, WMS/WFS, etc. over time.</font> </p>
<br>
<p style="margin-top: 0; margin-bottom: 0">
<font size="3" face="Comic Sans MS">Thanks</font> </p>
<br>
<p style="margin-top: 0; margin-bottom: 0">
<font size="3" face="Comic Sans MS">bobb</font> </p>
<br> <br>
</body>
</html>