<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8" data-hsystem="true"></head>
<body><style>p{margin: 0;padding: 0;}
</style>
<p>pyWPS +1<br><br>On Fri, 13 May 2016 06:18:31 -0400, Tom Kralidis
<tomkralidis@gmail.com> wrote:</p>
<blockquote style="border-left: 2px solid #000000; padding-right: 0px;
padding-left: 5px; margin-left: 5px; margin-right: 0px;">Hi all: below is the
application for PyWPS for inclusion into OSGeo Live. If<br> it helps, the below
can also be found at [1].<br><br> If you have any questions or comments, feel
free to contact me.<br><br> Thanks<br><br> ..Tom<br><br> [1]
https://github.com/geopython/pywps/wiki/OSGeoLiveApplication<br><br><br> Please
describe your application.<br><br> What is its name? PyWPS<br><br> What is the
home page URL? http://pywps.org<br><br> Which OSI approved Open Source Licence
is used? GPL for PyWPS 3.x.<br> Note that PyWPS 4 (in development) is a rewrite
and will be available<br> under MIT<br><br> What does the application do and how
does it add value to the<br> GeoSpatial stack of software? PyWPS provides an OGC
WPS server<br> implementation written in Python. PyWPS allows for processes to
be<br> exposed, discovered and executed in support of geospatial
workflows<br><br> Does the application make use of OGC standards? Which versions
of the<br> standards? Client or server? You may wish to add comments about
how<br> standards are used. PyWPS implements OGC WPS 1.0.0 (2.0.0 in<br>
development)<br><br> What language is it written in? Python<br><br> Which
version of the application should be included in the next<br> OSGeo-Live
release? 3.2.5<br><br> Stability is very important to us on OSGeo-Live. If a new
user finds a<br> bug in one application, it will tarnish the reputation of all
other<br> OSGeo-Live applications as well. (We pay most attention to the<br>
following answers):<br><br> If risk adverse organisations have deployed your
application into<br> production, it would imply that these organisations have
verified the<br> stability of your software. Has the application been rolled out
to<br> production into risk (ideally risk adverse) organisations? Please<br>
mention some of these organisations? The Meteorological Service of<br> Canada,
the WMO WOUDC project, Department of Earth Observation at the<br>
Friedrich-Schiller University Jena (Germany), International Union of<br> Soil
Sciences, NASA (JPL), UNEP/GRID, Luxembourg Institute of Science<br> and
Technology (LIST)<br><br> Open HUB provides metrics to help assess the health of
a project. Eg:<br> http://adhoc.osgeo.osuosl.org/livedvd/docs/en/metrics.html
Could you<br> please ensure that your project is registered with Open HUB, and
Open<br> HUB has been updated to reference the correct code repository(s)
for<br> your project. What is the Open HUB URL for your project?<br>
https://www.openhub.net/p/PyWPS<br><br> What is the size of the user community?
You can often answer this by<br> mentioning downloads, or describing a healthy,
busy email list? In<br> 2016 the PyWPS mailing list received 250 messages,
averaging almost 2<br> messages per day. So far, 17 different individuals have
subscribed the<br> contribution agreement. The pywps-3 repository has been
forked 43<br> times and the pywps-4 repository has 17 forks.<br><br> What is the
size of your developer community (5-6 core developers)<br><br> Do you have a bug
free, stable release? yes<br><br> Please discuss the level of testing that your
project has gone<br> through. PyWPS has regression testing. Bugs/issues are
managed via<br> GitHub and triaged accordingly<br> How long has the project has
had mature code. Started in 2006, PyWPS<br> has had stable releases since 2008
with PyWPS 3.0.0<br><br> OSGeo-Live is targeted at applications that people can
use rather than<br> libraries. Does the application have a user interface
(possibly a<br> command line interface) that a user can interact with? (We do
make an<br> exception for Incubated OSGeo Libraries, and will include
Project<br> Overviews for these libraries, even if they don't have a user<br>
interface.). PyWPS is configurable via the command line and<br> configuration
files. PyWPS does not have a graphical user interface<br><br> We give preference
to OSGeo Incubated Projects, or Projects which are<br> presented at FOSS4G
conferences. If your project is involved in OSGeo<br> Incubation, or has been
selected to be presented at FOSS4G, then<br> please mention it. PyWPS is
currently working through the OSGeo<br> incubation process<br><br> With around
50 applications installed on OSGeo-Live, us core packagers<br> do not have the
time to liaise with every single project email list<br> for each OSGeo-Live
release. So we require a volunteer (or two) to<br> take responsibility for
liaising between OSGeo-Live and the project's<br> communities. This volunteer
will be responsible for ensuring the<br> install scripts and English
documentation are updated by someone for<br> each OSGeo-Live release. Also test
that the installed application and<br> Quickstart documentation works as
expected on release candidate<br> releases of OSGeo-Live. Who will act as the
project's liaison person.<br> Tom Kralidis<br> OSGeo-Live is Ubuntu Linux based.
Our installation preference is:<br> Install from UbuntuGIS or DebianGIS Install
.deb files from a PPA or<br> Write a custom install script. Can you please
discuss how your<br> application will be installed. via UbuntuGIS and install
script with<br> configuration<br><br> OSGeo-Live is memory and disk constrained.
Can the application run in<br> 512 Meg of RAM? Yes<br><br> How much disk space
will be required to install the application and a<br> suitable example
application? ~ 250KB<br><br> We aim to reduce disk space by having all
applications make use of a<br> common dataset. We encourage applications to make
use of the example<br> datasets already installed:<br>
http://wiki.osgeo.org/wiki/Live_GIS_Add_Project#Example_Datasets If<br> another
dataset would be more appropriate, please discuss here. Is it<br> appropriate,
to remove existing demo datasets which may already be<br> included in the
standard release.<br> Each OSGeo-Live application requires a Project Overview
available<br> under a CC By and a Quickstart available under a CC By-SA
license.<br> (You may release under a second license as well). Will you
produce<br> this? Yes<br><br> In past releases, we have included Windows and Mac
installers for some<br> applications. It is likely we won't have space for these
in future<br> releases. However, if there is room, would you be wishing to
include<br> Windows and/or Mac installers? Yes, this is feasible given the
very<br> nature of Python<br>
_______________________________________________<br> Live-demo mailing list<br>
Live-demo@lists.osgeo.org<br>
http://lists.osgeo.org/mailman/listinfo/live-demo<br> http://live.osgeo.org<br>
http://wiki.osgeo.org/wiki/Live_GIS_Disc<br>
</blockquote>
<p><br><br></p>
<p><br> --<br>Brian M Hamlin<br> OSGeo California Chapter<br>
blog.light42.com<br></p>
<p> </p>
</body>
</html>