[OWSLib-devel] [owslib-devel] OWSLib in OSGeoLive 6.5

Tue Nov 6 16:35:01 PST 2012

> Date: Thu, 1 Nov 2012 22:58:13 +0200
> From: gcpp.kalxas at gmail.com
> To: owslib-devel at lists.osgeo.org
> Subject: [OWSLib-devel] [owslib-devel] OWSLib in OSGeoLive 6.5
> 
> Hi all,
> 
> In the latest alpha build of OSGeoLive, OWSLib is included as a 
> dependency for pycsw.
> I proposed that it should be officially included in the disk (with 
> documentation) and this was welcomed by the core OSGeoLive team.
> For this we need to answer some questions as described in the wiki:
> 
> http://wiki.osgeo.org/wiki/Live_GIS_Disc_Apply
> 
> Thoughts?
> 

Thanks for the info, I think this is a good idea.  I've answered the questions (answers prefixed by TK:) below, for review and comment?

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: http://lists.osgeo.org/mailman/listinfo/live-demo

 Please describe your application.
 What is its name? TK: OWSLib
 What is the home page URL? TK: http://geopython.github.com/OWSLib
 Which OSI approved TK: Open Source Licence is used? BSD What does the application do and how does it add value to the GeoSpatial stack of software? 
TK: OWSLib is a Python package for client programming with Open Geospatial Consortium
 (OGC) web service (hence OWS) interface standards, and their related 
content models.  OWSLib is a building block for Python applications to 
integrate OGC standards
 Does the application make use of OGC standards?  Which versions
 of the standards? Client or server? You may wish to add comments about 
how standards are used. TK: WMS,WFS,WCS,CSW,WPS,ISO,Dublin Core,FGDC,NASA DIF, etc.
 What language is it written in? TK: Python
 Which version of the application should be included in the next OSGeo-Live release? TK: 0.5.1 (currently)

 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. (We pay most attention to the 
following answers):
 If risk adverse organisations have deployed your application 
into production, it would imply that these organisations have verified 
the stability of your software. Has the application been rolled out to 
production into risk (ideally risk adverse) organisations? Please 
mention some of these organisations? TK: yes, OWSLib is used in CKAN, 
GeoNode, pycsw, and QGIS.  These packages support production 
applications
 What is the size of the user community? You can often answer 
this by mentioning downloads, or describing a healthy, busy email list? TK: both a -users and -devel email list exist
 What is the size of your developer community? 3-4 active developers
 Do you have a bug free, stable release?TK: yes

 Please discuss the level of testing that your project has gone 
through.TK: Python unit tests exist, the testing framework is being 
migrated to work on travis-ci.org
 How long has the project has had mature code.TK: over 5 years

 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? (We 
do make an exception for Incubated OSGeo Libraries, and will include 
Project Overviews for these libraries, even if they don't have a user 
interface.)TK: OWSLib is primarily a library, although there are some utilities/examples as part of the codebase

 We give preference to OSGeo Incubated Projects, or Projects which are presented at FOSS4G
 conferences. If your project is involved in OSGeo Incubation, or has 
been selected to be presented at FOSS4G, then please mention it.

 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.TK: myself initially

 OSGeo-Live is Ubuntu Linux based. Our installation preference is:
 Install from UbuntuGIS or DebianGIS
 Install .deb files from a PPA
 Write a custom install script

Can you please discuss how your application will be installed.TK: Angelos Tzotsos has built packages for OWSLib

 OSGeo-Live is memory and disk constrained. Can the application run in 512 Meg of RAM? TK: yes

 How much disk space will be required to install the application and a suitable example application? ~1MB

 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:

http://wiki.osgeo.org/wiki/Live_GIS_Add_Project#Example_Datasets
 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.

 Each OSGeo-Live application requires a Project Overview available under a CC By and a Quickstart available under a CC By-SA license. (You may release under a second license as well). Will you produce this?TK: yes

 In past releases, we have included Windows and Mac installers 
for some applications. It is likely we won't have space for these in 
future releases. However, if there is room, would you be wishing to 
include Windows and/or Mac installers?TK: no

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/owslib-devel/attachments/20121106/cc3f7a24/attachment.html>