[OSGeoLive] Application to include the ETF testing framework software in the OSGeoLive distribution
Angelos Tzotsos
gcpp.kalxas at gmail.com
Thu Apr 28 23:37:51 PDT 2022
Dear Jose,
Thank you for your application.
We will process during our next project meeting and provide feedback.
Best regards,
Angelos
On 4/20/22 17:53, José Enrique Soriano Sevilla wrote:
> Dear OSGeoLive team,
>
> we contact you to kindly propose the inclusion of the ETF testing
> framework in the OSGeoLive distribution.
> Following the requirements, please find below the answer to the
> required questions.
> Please let us know if any additional clarification is needed.
>
> Thank you in advance
>
> * *Please describe your application. *
> o *What is its name? *
> + ETF
> o *What is the home page URL? *
> + http://etf-validator.net
> <https://urldefense.com/v3/__http://etf-validator.net/__;!!DOxrgLBm!UvR1kftQcLgI0pIHnKKusY23bweSMhF9CdWZjAsWPgY49H9cK9Rs5HIqNIO4Ob1On0UqAiU$> andhttps://github.com/etf-validator
> <https://github.com/etf-validator>
> o *Which OSI approved Open Source Licence
> <https://urldefense.com/v3/__http://opensource.org/licenses__;!!DOxrgLBm!UvR1kftQcLgI0pIHnKKusY23bweSMhF9CdWZjAsWPgY49H9cK9Rs5HIqNIO4Ob1OXB4gFIA$>
> is used? *
> + TheETF testing framework isan open source project licensed
> under EUPL v.1.2, please see it in the main webpage
> <https://urldefense.com/v3/__http://etf-validator.net/__;!!DOxrgLBm!UvR1kftQcLgI0pIHnKKusY23bweSMhF9CdWZjAsWPgY49H9cK9Rs5HIqNIO4Ob1On0UqAiU$>and
> in the source code
> <https://urldefense.com/v3/__https://github.com/etf-validator/etf-webapp/blob/master/LICENSE__;!!DOxrgLBm!UvR1kftQcLgI0pIHnKKusY23bweSMhF9CdWZjAsWPgY49H9cK9Rs5HIqNIO4Ob1OzRXGAWQ$>.
>
> o *What does the application do and how does it add value to the
> GeoSpatial stack of software? *
> + It is an open source testing framework that allows
> validating spatial data, metadata and web services in
> Spatial Data Infrastructures (SDIs) according to defined
> Abstract Test Suites and Executable Test Suites. Executing
> these validations may increase the level of interoperability
> of SDIs by improving the compliance of geospatial data,
> metadata and services.
> o *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. *
> + The ETF testing framework allows GIS data providers and
> solution providers to check whether data sets, network
> services and metadata meet the requirements defined on
> specific Abstract and Executable Test Suites. The concepts
> in ETF are based on ISO 19105 and the OGC Specification
> Model which underpin the standards used in SDIs.
> + Validation capabilities span a wide range of OGC standards.
> For example, tests to validate WMS, WMTS, WFS, WCS, SOS and
> CSW are available, which are also partially reusing the OGC
> TEAM Engine suite.
> o *What language is it written in? *
> + Java, HTML, JavaScript, CSS
> o *Which version of the application should be included in the next
> OSGeo-Live release? *
> + ETF 2.0
>
> * *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? *
> + European Commission, Joint Research Centre (use of the ETF
> testing framework as the core component of the INSPIRE
> Reference Validator)
> + Organisations in several EU Member States at the national
> and regional level (using the ETF testing framework to
> replicate the tests of the INSPIRE Reference Validator
> and/or extending these tests to include tests to check
> compliance with national requirements)
> o *Open HUB
> <https://urldefense.com/v3/__https://www.openhub.net/__;!!DOxrgLBm!UvR1kftQcLgI0pIHnKKusY23bweSMhF9CdWZjAsWPgY49H9cK9Rs5HIqNIO4Ob1OtMqComw$>
> provides metrics to help assess the health of a project. Eg:
> http://adhoc.osgeo.osuosl.org/livedvd/docs/en/metrics.html
> <https://urldefense.com/v3/__http://adhoc.osgeo.osuosl.org/livedvd/docs/en/metrics.html__;!!DOxrgLBm!UvR1kftQcLgI0pIHnKKusY23bweSMhF9CdWZjAsWPgY49H9cK9Rs5HIqNIO4Ob1OvPpGSUg$>
> Could you please ensure that your project is registered with
> Open HUB, and Open HUB has been updated to reference the correct
> code repository(s) for your project. What is the Open HUB URL
> for your project? *
> + https://www.openhub.net/p/etf-validator
> o *What is the size of the user community? You can often answer
> this by mentioning downloads, or describing a healthy, busy
> email list? *
> + There is a mature user community developed around the main
> implementations of the ETF testing framework. For example,
> the number of downloads of the INSPIRE Reference Validator
> (the most popular implemetation of the ETF) is approximately
> between 1 and 3 hundreds for each release (see
> https://hanadigital.github.io/grev/?user=etf-validator&repo=etf-webapp
> <https://hanadigital.github.io/grev/?user=etf-validator&repo=etf-webapp>)
> and the discussions in the issue tracker demonstrate the
> healthy and busy user community (see
> https://github.com/INSPIRE-MIF/helpdesk-validator/issues/
> <https://github.com/INSPIRE-MIF/helpdesk-validator/issues/>).
> o *What is the size of your developer community? *
> + Currently, the developer community is mainly limited to the
> two organisations which are funding the development of the
> ETF, i.e. the European Commission and interactive
> instruments (https://www.interactive-instruments.de/en
> <https://www.interactive-instruments.de/en>). Sometimes,
> developers from organisations deploying the ETF at their
> premise contribute code with ad hoc pull requests. Funding
> to improve the developer community is currently available
> and the submission of the ETF to the OSGeoLive is one of the
> steps to increase such community.
> o *Do you have a bug free, stable release? *
> + Yes, ETF 2.0 is the latest stable release:
> https://github.com/etf-validator/etf-webapp/releases/tag/2.0.0
> <https://github.com/etf-validator/etf-webapp/releases/tag/2.0.0>
> o *Please discuss the level of testing that your project has gone
> through. *
> + The ETF has a continuous integration cycle established in
> the GitHub repository, where contributions to the source
> code (which have to adhere to the contribution guidelines
> <https://github.com/etf-validator/governance/blob/master/TOR/Contribution.md>)
> pass through automatic validations. Subsequently, the
> changes are manually reviewed and approved by the ETF
> Technical Committee
> <https://github.com/etf-validator/governance/blob/master/TOR/Technical_Committee.adoc>.
> o *How long has the project has had mature code. *
> + The project is active since 2007 (see
> https://github.com/etf-validator/etf-webapp/releases
> <https://github.com/etf-validator/etf-webapp/releases>); the
> latest stable release (v.2.0) was released in 2019.
>
> * *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.) *
> o Yes, the ETF testing framework has a user interface.
>
> * *We give preference to OSGeo Incubated Projects, or Projects which
> are presented at FOSS4G
> <https://urldefense.com/v3/__http://foss4g.org__;!!DOxrgLBm!UvR1kftQcLgI0pIHnKKusY23bweSMhF9CdWZjAsWPgY49H9cK9Rs5HIqNIO4Ob1OHj1k4aA$>
> conferences. If your project is involved in OSGeo Incubation, or has
> been selected to be presented at FOSS4G, then please mention it. *
> o The ETF was already presented at FOSS4G conferences:
> + FOSS4G 2019:INSPIRE Reference Validator: status and next
> steps by Marco Minghini, Michael Lutz, Clemens Portele, Jon
> Herrmann, Enrique Soriano, Carlos Palma, Iñaki Díaz de Cerio
> Paniagua, Belén Sáez, Lorena Hernandez, Daniele Francioli,
> Fabio Vinci
> + FOSS4G 2021: *Open source geospatial software powering
> policy implementation: the INSPIRE central infrastructure
> components* by Marco Minghini, Alexander Kotsev, Vlado Cetl,
> Lorena Hernandez, Michael Lutz, Daniele Francioli, Davide
> Artasensi, Emanuela Epure, Fabio Vinci, Fabiano Spinelli,
> Lukasz Ziemba
> (https://callforpapers.2021.foss4g.org/foss4g2021/talk/ZKRWYN/
> <https://callforpapers.2021.foss4g.org/foss4g2021/talk/ZKRWYN/>)
> + FOSS4G 2022: *ETF testing framework: past, present and
> future *by Jon Herrmann, Marco Minghini, Clemens Portele,
> Michael Lutz (submitted and currently under review)
>
> * *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. *
> o Enrique Soriano (jenriquesoriano at guadaltel.com) and José
> Barrero (josebarrero at guadaltel.com)
>
> * *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<=== preferred option*
> *
> *Can you please discuss how your application will be installed. *
> o Write a custom install script
> * *OSGeo-Live is memory and disk constrained. Can the application run
> in 512 Meg of RAM? *
> o No. A machine with at least 4 GB Ram (8GB are recommended, 16 GB
> and more if a large set of XML files are tested)
> * *How much disk space will be required to install the application and
> a suitable example application? *
> o It depends on the tests executed, but 1 GB HDD can be enough.
> * *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: *
> * *Each OSGeo-Live application requires a Project Overview available
> under a CC By
> <https://urldefense.com/v3/__http://creativecommons.org/licenses/by/3.0/__;!!DOxrgLBm!UvR1kftQcLgI0pIHnKKusY23bweSMhF9CdWZjAsWPgY49H9cK9Rs5HIqNIO4Ob1OYJp5E24$>
> and a Quickstart available under a CC By-SA
> <https://urldefense.com/v3/__http://creativecommons.org/licenses/by-sa/3.0/__;!!DOxrgLBm!UvR1kftQcLgI0pIHnKKusY23bweSMhF9CdWZjAsWPgY49H9cK9Rs5HIqNIO4Ob1OtUoN0gs$>
> license. (You may release under a second license as well). Will you
> produce this? *
> o 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? *
> o No
>
>
> _______________________________________________
> osgeolive mailing list
> osgeolive at lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/osgeolive
--
Angelos Tzotsos, PhD
President
Open Source Geospatial Foundation
http://users.ntua.gr/tzotsos
More information about the osgeolive
mailing list