[Live-demo] Request for inclusion in OSGeo Live

Cameron Shorter cameron.shorter at gmail.com
Wed Jun 12 16:01:21 PDT 2013

Thanks for your application for IRIS. The project does seem to have much 
going for it.
The question I'm still unclear on is whether the project is too 
specialised for the vast majority of people who pick up OSGeo-Live, and 
is it seriously used outside of UK Met Office.

A primary focus on OSGeo-Live is to help new users looking for 
established OSGeo projects. (A side benefit of helping new users is that 
we provide a marketing pipeline for the established projects).
We need to be careful that we don't include every project looking for a 
community, as it confuses users, which in turn reduces the value of 
OSGeo-Live for all.

Based upon your explanation below, it seems that IRIS still would need 
to attract users from outside the UK Met Office before it could be 
considered to have an established community?
Is this something you can talk to? Maybe IRIS would be a better 
candidate to join OSGeo-Live in a future release?

On 12/06/2013 6:54 AM, Ian Edwards wrote:
>   * Please describe your application.
>           + What is its name? *Iris*
>           + What is the home page URL? *http://scitools.org.uk/*
>           + Which OSI approved Open Source Licence is used? *LGPL**v3*
>          +
>             What does the application do and how does it add value to
>             the GeoSpatial stack of software?
>             *The Iris python package allows**users to work with large
>             multi-dimensional datasets such as those found in the
>             fields of weather and climate science. Iris builds on the
>             semantics and data model from the Climate and Forecasting
>             conventions for NetCDF (CF-NetCDF) which exist to define
>             the metadata within NetCDF files in order to provide a
>             definitive description of each of the data variables
>             including their spatial and temporal properties. CF-NetCDF
>             is being adopted by the OGC as a WCS payload format.
>             Iris enables users of data from different sources to build
>             applications with powerful extraction, regridding, and
>             display capabilities and export their data to CF compliant
>             NetCDF. The ability to provide data sets of three, four,
>             and higher-dimensions represents a significant expansion
>             of the capabilities of web coverage services**which
>             require tooling to generate the data sets.NetCDF and t**he
>             CF conventions provide extensive capabilities for
>             multidimensional data**,* *Iris can provide an interface
>             to NetCDF data sets. *
>          +
>             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.
>             *This Iris data model follows the CF-NetCDF 1.6
>             conventions **http://www.opengeospatial.org/standards/netcdf**
>             **Current use cases include using Iris to convert data
>             into a format suitable for use with GeoServer to serve
>             slices of multi-dimensional datasets via WMS 1.1.1 and 1.3.0
>             Developers are currently looking at integrating Iris with
>             Zoo-project to allow users to interact with the library
>             via WPS calls.**
>             *
>           + What language is it written in? *Python*
>           + Which version of the application should be included in the
>             next OSGeo-Live release?
>             *- Iris 1.4.0 (https://github.com/SciTools/iris/tags)*
>  *
>     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):
>      o
>         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?
>         *Iris was developed by the UK Met Office (metoffice.gov.uk
>         <http://metoffice.gov.uk>) to provide a more robust, intuitive
>         and standards complaint environment for use across the
>         organisation's research and production systems.  The software
>         was released as open source to ensure easy collaboration with
>         partners and external developers are now also contributing to
>         code base.*
>       o Ohloh <https://www.ohloh.net/> provides metrics to help assess
>         the health of a project. Eg:
>         http://adhoc.osgeo.osuosl.org/livedvd/docs/en/metrics.html
>         Could you please ensure that your project is registered with
>         Ohloh, and Ohloh has been updated to reference the correct
>         code repository(s) for your project. What is the Ohloh URL for
>         your project?
>         *http://www.ohloh.net/p/scitools-iris*
>      o
>         What is the size of the user community? You can often answer
>         this by mentioning downloads, or describing a healthy, busy
>         email list?
>         ***Within the Met Office we have over 250 unique users. 
>         Externally we are in contact with collaborators who also use
>         the software, we would like to use OSGeo Live to increase the
>         user base*
>       o What is the size of your developer community?
>         *  The project currently has 5 full time core developers and
>         an additional 3-6 developers.*
>      o
>         Do you have a bug free, stable release?
>         *   Yes, The Met Office has currently deployed the stable
>         1.4.0 release.*
>      o
>         Please discuss the level of testing that your project has gone
>         through.
>         *The 1.4.0 release has over 1,200 unit tests.  Each pull
>         request must pass peer-review and Travis CI testing before
>         being merged into the project
>            e.g. **https://travis-ci.org/SciTools/iris/builds/7844677*
>       o How long has the project has had mature code.
>         *  Iris has been considered mature since the 1.0 release in
>         October 2012.*
>  *
>     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.)
>     *********No, this is a software library
>     **For examples, see:
>     http://scitools.org.uk/iris/docs/latest/gallery.html*
>   * We give preference to OSGeo Incubated Projects, or Projects which
>     are presented at FOSS4G <http://foss4g.org> conferences. If your
>     project is involved in OSGeo Incubation, or has been selected to
>     be presented at FOSS4G, then please mention it.
>     *  FOSS4G 2013 Workshop:
>     http://2013.foss4g.org/provisional/workshops#W15
>     <http://2013.foss4g.org/provisional/workshops#W15>*
>     *  FOSS4G 2013 Presentation: Cartopy and Iris: Open Source Python
>     Tools for Analysis and Visualisation*
>   * 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.
>     *   Ian Edwards - ian.edwards [ a t ] metoffice.gov.uk
>     <http://metoffice.gov.uk>*
>   * OSGeo-Live is Ubuntu Linux based. Our installation preference is:
>      1. Install from UbuntuGIS or DebianGIS
>      2. Install .deb files from a PPA
>      3. Write a custom install script
>     Can you please discuss how your application will be installed.
>     *   We intend to provide a PPA within the timeframe of OSGeo Live
>     7 development
>     *
>     *   Currently users install from recipes:
>     https://github.com/SciTools/installation-recipes
>     <https://github.com/SciTools/installation-recipes>
>     *
>     ***Automated Ubuntu install:
>     **https://github.com/SciTools/iris/blob/master/.travis.yml*
>   * OSGeo-Live is memory and disk constrained. Can the application run
>     in 512 Meg of RAM?
>     *  Yes*
>  *
>     How much disk space will be required to install the application
>     and a suitable example application?
>     ***The Iris python code is only 3.3 Mb.  The size of the install
>     will depend on which of the dependencies are already available on
>     OSGeo Live, but the final install will still be small, see:
>     **http://scitools.org.uk/iris/docs/latest/installing.html#build-requirements*
>  *
>     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.
>     ***Additional sample* *data, if required, can be downloaded by the
>     user from the web https://github.com/SciTools/iris-sample-data*
>   * Each OSGeo-Live application requires a Project Overview available
>     under a CC By <http://creativecommons.org/licenses/by/3.0/> and a
>     Quickstart available under a CC By-SA
>     <http://creativecommons.org/licenses/by-sa/3.0/> license. (You may
>     release under a second license as well). Will you produce this?
>     *  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?
>     *  Windows support is still in development we currently have a
>     small Mac user group - we certainly would like to be able to
>     provide both in the future, but probably not on this release.*
> _______________________________________________
> Live-demo mailing list
> Live-demo at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/live-demo
> http://live.osgeo.org
> http://wiki.osgeo.org/wiki/Live_GIS_Disc

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

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/osgeolive/attachments/20130613/69f4fbaf/attachment.html>

More information about the Osgeolive mailing list