<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
</head>
<body bgcolor="#FFFFFF" text="#000000">
Hi all,<br>
<br>
we hereby propose "actinia" for inclusion in OSGeo-live:<br>
<br>
<br>
<i><b>Describe of the application:</b></i><br>
<br>
What is its name? <br>
<b>actinia<br>
</b><br>
<i>What is the home page URL?</i><br>
<ul>
<li><a class="moz-txt-link-freetext" href="https://actinia.mundialis.de/">https://actinia.mundialis.de/</a></li>
<li><a class="moz-txt-link-freetext" href="https://github.com/mundialis/actinia_core/">https://github.com/mundialis/actinia_core/</a></li>
</ul>
<i>Which </i><i><a rel="nofollow" class="external text"
href="http://opensource.org/licenses">OSI approved Open Source
Licence</a></i><i> is used?</i><br>
<ul>
<li>GPL-3</li>
</ul>
<i>What does the application do and how does it add value to the
GeoSpatial stack of software?</i><br>
<ul>
<li>actinia is an open source REST API for scalable, distributed,
high performance processing of geographical data that uses
mainly GRASS GIS for computational tasks. Besides that, also
further OSGeo related software and other open source analysis
tools can be used.</li>
</ul>
<i>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.</i><br>
<ul>
<li>actinia core offers the possibility to extend it with plugins.
The actinia-gdi plugin
(<a class="moz-txt-link-freetext" href="https://github.com/mundialis/actinia-gdi/">https://github.com/mundialis/actinia-gdi/</a>) helps integrating
actinia-core in an existing GDI, e.g. to communicate with
GeoNetwork.</li>
</ul>
<i>What language is it written in?</i><br>
<ul>
<li>Python-3</li>
</ul>
<i>Which version of the application should be included in the next
OSGeo-Live release?</i><br>
<ul>
<li>The current "latest".</li>
</ul>
<br>
<i> 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):
</i><br>
<br>
<i>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?</i><br>
<ul>
<li>At time a major German telekommunication company is using
actinia in a cloud based massive data processing roll-out. At
FOSS4G 2019 in Bucharest some related presentations will be
given.</li>
<li>Besides that, actinia is the backend of the openEO GRASS GIS
driver (<a class="moz-txt-link-freetext" href="https://openeo.org/">https://openeo.org/</a>, a H2020 EU project |
<a class="moz-txt-link-freetext" href="https://github.com/Open-EO/openeo-grassgis-driver">https://github.com/Open-EO/openeo-grassgis-driver</a>).<br>
</li>
</ul>
<i>What is the Open HUB URL for your project?</i><br>
<ul>
<li><a class="moz-txt-link-freetext" href="https://www.openhub.net/p/actinia_core/">https://www.openhub.net/p/actinia_core/</a></li>
</ul>
<i>What is the size of the user community? You can often answer this
by mentioning downloads, or describing a healthy, busy email list?</i><br>
<ul>
<li>The actinia community is very young and yet hard to measure.
Some stats are available from
<a class="moz-txt-link-freetext" href="https://github.com/mundialis/actinia_core/graphs/traffic">https://github.com/mundialis/actinia_core/graphs/traffic</a></li>
</ul>
<i>What is the size of your developer community?</i><br>
<ul>
<li>Three core devs + some infrequent contributors.</li>
</ul>
<i>Do you have a bug free, stable release?</i><br>
<ul>
<li>There is no bugfree software :-)<br>
Yes, a stable release is available from
<a class="moz-txt-link-freetext" href="https://github.com/mundialis/actinia_core/tags">https://github.com/mundialis/actinia_core/tags</a><br>
</li>
</ul>
<i>Please discuss the level of testing that your project has gone
through.</i><br>
<ul>
<li>A notable test set is included, see
<a class="moz-txt-link-freetext" href="https://github.com/mundialis/actinia_core/tree/master/tests">https://github.com/mundialis/actinia_core/tree/master/tests</a> .</li>
<li>The deployment of actinia has been tested with Openstack as
well as CI/CD pipelines in Openshift. Furthermore several
deployments are running with docker-swarm. Dockerfiles for
development and for production are available from
<a class="moz-txt-link-freetext" href="https://github.com/mundialis/actinia_core/tree/master/docker">https://github.com/mundialis/actinia_core/tree/master/docker</a></li>
<li>Importantly, we use CI/CD pipelines for testing during
deployment.<br>
</li>
</ul>
<i>How long has the project has had mature code.</i><br>
<ul>
<li>The core of actinia has been used in production since end of
2016 (back then named GRaaS - GRASS GIS as a Service) as a
backend in a Sentinel-2 metadata processor operated for ESA
(<a class="moz-txt-link-freetext" href="https://sentinel.esa.int/web/sentinel/-/filter-sentinel-2a-scenes-with-the-new-release-of-eo-me">https://sentinel.esa.int/web/sentinel/-/filter-sentinel-2a-scenes-with-the-new-release-of-eo-me</a>).</li>
</ul>
<i>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.)</i><br>
<ul>
<li>Since actinia offers a REST API, there is no interactive user
interface per se. However, a few options are there (see also the
actinia docs):</li>
<ul>
<li>use curl (yes, cmd line is also a nice user interface,
<a class="moz-txt-link-freetext" href="https://actinia.mundialis.de/tutorial/">https://actinia.mundialis.de/tutorial/</a>)<br>
</li>
<li>Postman extension for Chrome</li>
<li>actinia command execution (ace,
<a class="moz-txt-link-freetext" href="https://github.com/mundialis/actinia_core/blob/master/scripts/">https://github.com/mundialis/actinia_core/blob/master/scripts/</a>)</li>
<li>more to come<br>
</li>
</ul>
</ul>
<i>
We give preference to OSGeo Incubated Projects, or Projects which
are presented at </i><i><a rel="nofollow" class="external text"
href="http://foss4g.org">FOSS4G</a></i><i> conferences. If your
project is involved in OSGeo Incubation, or has been selected to
be presented at FOSS4G, then please mention it.</i><br>
<ul>
<li>actinia is an OSGeo community project since 2019:
<a class="moz-txt-link-freetext" href="https://www.osgeo.org/projects/actinia/">https://www.osgeo.org/projects/actinia/</a></li>
</ul>
<i><b>
</b></i><i>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.</i><br>
<ul>
<li>Markus Neteler<br>
</li>
</ul>
<i>Can you please discuss how your application will be installed:</i><br>
<ul>
<li>We have developed an installer script: The pull request of
installer script is at<br>
<a class="moz-txt-link-freetext" href="https://github.com/OSGeo/OSGeoLive/pull/266">https://github.com/OSGeo/OSGeoLive/pull/266</a><br>
</li>
</ul>
<i>
OSGeo-Live is memory and disk constrained. Can the application run
in 512 Meg of RAM?</i><br>
<ul>
<li>No problem.<br>
</li>
</ul>
<i>
How much disk space will be required to install the application
and a suitable example application?</i><br>
<ul>
<li>The Python scripts are consuming 17MB. The backend GRASS GIS +
GDAL + dependencies are already present on OSGeo-live.<br>
</li>
</ul>
<i>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:</i><i><a rel="nofollow"
class="external free"
href="http://wiki.osgeo.org/wiki/Live_GIS_Add_Project#Example_Datasets"><br>
http://wiki.osgeo.org/wiki/Live_GIS_Add_Project#Example_Datasets</a></i><i>
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.</i><br>
<ul>
<li>The North Carolina dataset is fine.<br>
</li>
</ul>
<i>
Each OSGeo-Live application requires a Project Overview available
under a </i><i><a rel="nofollow" class="external text"
href="http://creativecommons.org/licenses/by/3.0/">CC By</a></i><i>
and a Quickstart available under a </i><i><a rel="nofollow"
class="external text"
href="http://creativecommons.org/licenses/by-sa/3.0/">CC By-SA</a></i><i>
license. (You may release under a second license as well). Will
you produce this?</i><br>
<ul>
<li>Sure: <a class="moz-txt-link-freetext" href="https://github.com/OSGeo/OSGeoLive-doc/pull/455">https://github.com/OSGeo/OSGeoLive-doc/pull/455</a><br>
</li>
</ul>
<i>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?</i><br>
<ul>
<li>No thanks, not needed here.</li>
</ul>
<p>best regards,</p>
<p>Markus</p>
<p>(on behalf of the actinia team)</p>
<p>-- <br>
Markus Neteler<br>
<a class="moz-txt-link-freetext" href="https://www.mundialis.de">https://www.mundialis.de</a> - free data with free software<br>
<a class="moz-txt-link-freetext" href="https://grass.osgeo.org">https://grass.osgeo.org</a><br>
<br>
</p>
</body>
</html>