<div dir="ltr"><div class="gmail_default" style="font-family:arial,helvetica,sans-serif">+1<br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Sat, Jul 2, 2022 at 7:42 AM Angelos Tzotsos <<a href="mailto:gcpp.kalxas@gmail.com">gcpp.kalxas@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Hi all,<br>
<br>
This is the voting status for this motion:<br>
<br>
Angelos_Tzotsos +1<br>
Brian M Hamlin +1<br>
Alex Mandel<br>
Johan Van de Wauw<br>
Bas Couwenberg<br>
Massimo De Stefano<br>
Astrid Emde<br>
Nicolas Roelandt +1<br>
Vicky Vergara<br>
Enock Seth Nyamador +1<br>
<br>
Dear PSC members, please vote. We are still missing more than 50% of the <br>
votes.<br>
<br>
Best regards,<br>
Angelos<br>
<br>
On 6/28/22 19:58, Angelos Tzotsos wrote:<br>
> Hi all,<br>
><br>
> This is the voting status for this motion:<br>
><br>
> Angelos_Tzotsos +1<br>
> Brian M Hamlin +1<br>
> Alex Mandel<br>
> Johan Van de Wauw<br>
> Bas Couwenberg<br>
> Massimo De Stefano<br>
> Astrid Emde<br>
> Nicolas Roelandt<br>
> Vicky Vergara<br>
> Enock Seth Nyamador<br>
><br>
> Dear PSC members, please vote.<br>
><br>
> Best regards,<br>
> Angelos<br>
><br>
> On 6/14/22 23:47, Angelos Tzotsos wrote:<br>
>> Hi all,<br>
>><br>
>> This is a motion to include ETF testing framework to OSGeoLive.<br>
>> I will start with my +1<br>
>> Angelos<br>
>><br>
>> On 4/20/22 17:53, José Enrique Soriano Sevilla wrote:<br>
>>> Dear OSGeoLive team,<br>
>>><br>
>>> we contact you to kindly propose the inclusion of the ETF testing <br>
>>> framework in the OSGeoLive distribution.<br>
>>> Following the requirements, please find below the answer to the <br>
>>> required questions.<br>
>>> Please let us know if any additional clarification is needed.<br>
>>><br>
>>> Thank you in advance<br>
>>><br>
>>> * *Please describe your application. *<br>
>>> o *What is its name? *<br>
>>> + ETF<br>
>>> o *What is the home page URL? *<br>
>>> + <a href="http://etf-validator.net" rel="noreferrer" target="_blank">http://etf-validator.net</a><br>
>>> <<a href="https://urldefense.com/v3/__http://etf-validator.net/__;!!DOxrgLBm!UvR1kftQcLgI0pIHnKKusY23bweSMhF9CdWZjAsWPgY49H9cK9Rs5HIqNIO4Ob1On0UqAiU$" rel="noreferrer" target="_blank">https://urldefense.com/v3/__http://etf-validator.net/__;!!DOxrgLBm!UvR1kftQcLgI0pIHnKKusY23bweSMhF9CdWZjAsWPgY49H9cK9Rs5HIqNIO4Ob1On0UqAiU$</a>> andhttps://<a href="http://github.com/etf-validator" rel="noreferrer" target="_blank">github.com/etf-validator</a> <br>
>>><br>
>>> <<a href="https://github.com/etf-validator" rel="noreferrer" target="_blank">https://github.com/etf-validator</a>><br>
>>> o *Which OSI approved Open Source Licence<br>
>>> <<a href="https://urldefense.com/v3/__http://opensource.org/licenses__;!!DOxrgLBm!UvR1kftQcLgI0pIHnKKusY23bweSMhF9CdWZjAsWPgY49H9cK9Rs5HIqNIO4Ob1OXB4gFIA$" rel="noreferrer" target="_blank">https://urldefense.com/v3/__http://opensource.org/licenses__;!!DOxrgLBm!UvR1kftQcLgI0pIHnKKusY23bweSMhF9CdWZjAsWPgY49H9cK9Rs5HIqNIO4Ob1OXB4gFIA$</a>> <br>
>>><br>
>>> is used? *<br>
>>> + TheETF testing framework isan open source project licensed<br>
>>> under EUPL v.1.2, please see it in the main webpage<br>
>>> <<a href="https://urldefense.com/v3/__http://etf-validator.net/__;!!DOxrgLBm!UvR1kftQcLgI0pIHnKKusY23bweSMhF9CdWZjAsWPgY49H9cK9Rs5HIqNIO4Ob1On0UqAiU$" rel="noreferrer" target="_blank">https://urldefense.com/v3/__http://etf-validator.net/__;!!DOxrgLBm!UvR1kftQcLgI0pIHnKKusY23bweSMhF9CdWZjAsWPgY49H9cK9Rs5HIqNIO4Ob1On0UqAiU$</a>>and <br>
>>><br>
>>> in the source code<br>
>>> <<a href="https://urldefense.com/v3/__https://github.com/etf-validator/etf-webapp/blob/master/LICENSE__;!!DOxrgLBm!UvR1kftQcLgI0pIHnKKusY23bweSMhF9CdWZjAsWPgY49H9cK9Rs5HIqNIO4Ob1OzRXGAWQ$" rel="noreferrer" target="_blank">https://urldefense.com/v3/__https://github.com/etf-validator/etf-webapp/blob/master/LICENSE__;!!DOxrgLBm!UvR1kftQcLgI0pIHnKKusY23bweSMhF9CdWZjAsWPgY49H9cK9Rs5HIqNIO4Ob1OzRXGAWQ$</a>>. <br>
>>><br>
>>><br>
>>> o *What does the application do and how does it add value to the<br>
>>> GeoSpatial stack of software? *<br>
>>> + It is an open source testing framework that allows<br>
>>> validating spatial data, metadata and web services in<br>
>>> Spatial Data Infrastructures (SDIs) according to defined<br>
>>> Abstract Test Suites and Executable Test Suites. Executing<br>
>>> these validations may increase the level of interoperability<br>
>>> of SDIs by improving the compliance of geospatial data,<br>
>>> metadata and services.<br>
>>> o *Does the application make use of OGC standards? Which versions<br>
>>> of the standards? Client or server? You may wish to add comments<br>
>>> about how standards are used. *<br>
>>> + The ETF testing framework allows GIS data providers and<br>
>>> solution providers to check whether data sets, network<br>
>>> services and metadata meet the requirements defined on<br>
>>> specific Abstract and Executable Test Suites. The concepts<br>
>>> in ETF are based on ISO 19105 and the OGC Specification<br>
>>> Model which underpin the standards used in SDIs.<br>
>>> + Validation capabilities span a wide range of OGC standards.<br>
>>> For example, tests to validate WMS, WMTS, WFS, WCS, SOS and<br>
>>> CSW are available, which are also partially reusing the OGC<br>
>>> TEAM Engine suite.<br>
>>> o *What language is it written in? *<br>
>>> + Java, HTML, JavaScript, CSS<br>
>>> o *Which version of the application should be included in the next<br>
>>> OSGeo-Live release? *<br>
>>> + ETF 2.0<br>
>>><br>
>>> * *Stability is very important to us on OSGeo-Live. If a new user<br>
>>> finds a bug in one application, it will tarnish the reputation of<br>
>>> all other OSGeo-Live applications as well. (We pay most attention to<br>
>>> the following answers): *<br>
>>> o *If risk adverse organisations have deployed your application<br>
>>> into production, it would imply that these organisations have<br>
>>> verified the stability of your software. Has the application<br>
>>> been rolled out to production into risk (ideally risk adverse)<br>
>>> organisations? Please mention some of these organisations? *<br>
>>> + European Commission, Joint Research Centre (use of the ETF<br>
>>> testing framework as the core component of the INSPIRE<br>
>>> Reference Validator)<br>
>>> + Organisations in several EU Member States at the national<br>
>>> and regional level (using the ETF testing framework to<br>
>>> replicate the tests of the INSPIRE Reference Validator<br>
>>> and/or extending these tests to include tests to check<br>
>>> compliance with national requirements)<br>
>>> o *Open HUB<br>
>>> <<a href="https://urldefense.com/v3/__https://www.openhub.net/__;!!DOxrgLBm!UvR1kftQcLgI0pIHnKKusY23bweSMhF9CdWZjAsWPgY49H9cK9Rs5HIqNIO4Ob1OtMqComw$" rel="noreferrer" target="_blank">https://urldefense.com/v3/__https://www.openhub.net/__;!!DOxrgLBm!UvR1kftQcLgI0pIHnKKusY23bweSMhF9CdWZjAsWPgY49H9cK9Rs5HIqNIO4Ob1OtMqComw$</a>> <br>
>>><br>
>>> provides metrics to help assess the health of a project. Eg:<br>
>>> <a href="http://adhoc.osgeo.osuosl.org/livedvd/docs/en/metrics.html" rel="noreferrer" target="_blank">http://adhoc.osgeo.osuosl.org/livedvd/docs/en/metrics.html</a><br>
>>> <<a href="https://urldefense.com/v3/__http://adhoc.osgeo.osuosl.org/livedvd/docs/en/metrics.html__;!!DOxrgLBm!UvR1kftQcLgI0pIHnKKusY23bweSMhF9CdWZjAsWPgY49H9cK9Rs5HIqNIO4Ob1OvPpGSUg$" rel="noreferrer" target="_blank">https://urldefense.com/v3/__http://adhoc.osgeo.osuosl.org/livedvd/docs/en/metrics.html__;!!DOxrgLBm!UvR1kftQcLgI0pIHnKKusY23bweSMhF9CdWZjAsWPgY49H9cK9Rs5HIqNIO4Ob1OvPpGSUg$</a>> <br>
>>><br>
>>> Could you please ensure that your project is registered with<br>
>>> Open HUB, and Open HUB has been updated to reference the correct<br>
>>> code repository(s) for your project. What is the Open HUB URL<br>
>>> for your project? *<br>
>>> + <a href="https://www.openhub.net/p/etf-validator" rel="noreferrer" target="_blank">https://www.openhub.net/p/etf-validator</a><br>
>>> o *What is the size of the user community? You can often answer<br>
>>> this by mentioning downloads, or describing a healthy, busy<br>
>>> email list? *<br>
>>> + There is a mature user community developed around the main<br>
>>> implementations of the ETF testing framework. For example,<br>
>>> the number of downloads of the INSPIRE Reference Validator<br>
>>> (the most popular implemetation of the ETF) is approximately<br>
>>> between 1 and 3 hundreds for each release (see<br>
>>> <a href="https://hanadigital.github.io/grev/?user=etf-validator&repo=etf-webapp" rel="noreferrer" target="_blank">https://hanadigital.github.io/grev/?user=etf-validator&repo=etf-webapp</a><br>
>>> <<a href="https://hanadigital.github.io/grev/?user=etf-validator&repo=etf-webapp" rel="noreferrer" target="_blank">https://hanadigital.github.io/grev/?user=etf-validator&repo=etf-webapp</a>>) <br>
>>><br>
>>> and the discussions in the issue tracker demonstrate the<br>
>>> healthy and busy user community (see<br>
>>> <a href="https://github.com/INSPIRE-MIF/helpdesk-validator/issues/" rel="noreferrer" target="_blank">https://github.com/INSPIRE-MIF/helpdesk-validator/issues/</a><br>
>>> <<a href="https://github.com/INSPIRE-MIF/helpdesk-validator/issues/" rel="noreferrer" target="_blank">https://github.com/INSPIRE-MIF/helpdesk-validator/issues/</a>>).<br>
>>> o *What is the size of your developer community? *<br>
>>> + Currently, the developer community is mainly limited to the<br>
>>> two organisations which are funding the development of the<br>
>>> ETF, i.e. the European Commission and interactive<br>
>>> instruments (<a href="https://www.interactive-instruments.de/en" rel="noreferrer" target="_blank">https://www.interactive-instruments.de/en</a><br>
>>> <<a href="https://www.interactive-instruments.de/en" rel="noreferrer" target="_blank">https://www.interactive-instruments.de/en</a>>). Sometimes,<br>
>>> developers from organisations deploying the ETF at their<br>
>>> premise contribute code with ad hoc pull requests. Funding<br>
>>> to improve the developer community is currently available<br>
>>> and the submission of the ETF to the OSGeoLive is one of the<br>
>>> steps to increase such community.<br>
>>> o *Do you have a bug free, stable release? *<br>
>>> + Yes, ETF 2.0 is the latest stable release:<br>
>>> <a href="https://github.com/etf-validator/etf-webapp/releases/tag/2.0.0" rel="noreferrer" target="_blank">https://github.com/etf-validator/etf-webapp/releases/tag/2.0.0</a><br>
>>> <<a href="https://github.com/etf-validator/etf-webapp/releases/tag/2.0.0" rel="noreferrer" target="_blank">https://github.com/etf-validator/etf-webapp/releases/tag/2.0.0</a>><br>
>>> o *Please discuss the level of testing that your project has gone<br>
>>> through. *<br>
>>> + The ETF has a continuous integration cycle established in<br>
>>> the GitHub repository, where contributions to the source<br>
>>> code (which have to adhere to the contribution guidelines<br>
>>> <<a href="https://github.com/etf-validator/governance/blob/master/TOR/Contribution.md" rel="noreferrer" target="_blank">https://github.com/etf-validator/governance/blob/master/TOR/Contribution.md</a>>) <br>
>>><br>
>>> pass through automatic validations. Subsequently, the<br>
>>> changes are manually reviewed and approved by the ETF<br>
>>> Technical Committee<br>
>>> <<a href="https://github.com/etf-validator/governance/blob/master/TOR/Technical_Committee.adoc" rel="noreferrer" target="_blank">https://github.com/etf-validator/governance/blob/master/TOR/Technical_Committee.adoc</a>>. <br>
>>><br>
>>> o *How long has the project has had mature code. *<br>
>>> + The project is active since 2007 (see<br>
>>> <a href="https://github.com/etf-validator/etf-webapp/releases" rel="noreferrer" target="_blank">https://github.com/etf-validator/etf-webapp/releases</a><br>
>>> <<a href="https://github.com/etf-validator/etf-webapp/releases" rel="noreferrer" target="_blank">https://github.com/etf-validator/etf-webapp/releases</a>>); the<br>
>>> latest stable release (v.2.0) was released in 2019.<br>
>>><br>
>>> * *OSGeo-Live is targeted at applications that people can use rather<br>
>>> than libraries. Does the application have a user interface (possibly<br>
>>> a command line interface) that a user can interact with? (We do make<br>
>>> an exception for Incubated OSGeo Libraries, and will include Project<br>
>>> Overviews for these libraries, even if they don't have a user<br>
>>> interface.) *<br>
>>> o Yes, the ETF testing framework has a user interface.<br>
>>><br>
>>> * *We give preference to OSGeo Incubated Projects, or Projects which<br>
>>> are presented at FOSS4G<br>
>>> <<a href="https://urldefense.com/v3/__http://foss4g.org__;!!DOxrgLBm!UvR1kftQcLgI0pIHnKKusY23bweSMhF9CdWZjAsWPgY49H9cK9Rs5HIqNIO4Ob1OHj1k4aA$" rel="noreferrer" target="_blank">https://urldefense.com/v3/__http://foss4g.org__;!!DOxrgLBm!UvR1kftQcLgI0pIHnKKusY23bweSMhF9CdWZjAsWPgY49H9cK9Rs5HIqNIO4Ob1OHj1k4aA$</a>> <br>
>>><br>
>>> conferences. If your project is involved in OSGeo Incubation, or has<br>
>>> been selected to be presented at FOSS4G, then please mention it. *<br>
>>> o The ETF was already presented at FOSS4G conferences:<br>
>>> + FOSS4G 2019:INSPIRE Reference Validator: status and next<br>
>>> steps by Marco Minghini, Michael Lutz, Clemens Portele, Jon<br>
>>> Herrmann, Enrique Soriano, Carlos Palma, Iñaki Díaz de Cerio<br>
>>> Paniagua, Belén Sáez, Lorena Hernandez, Daniele Francioli,<br>
>>> Fabio Vinci<br>
>>> + FOSS4G 2021: *Open source geospatial software powering<br>
>>> policy implementation: the INSPIRE central infrastructure<br>
>>> components* by Marco Minghini, Alexander Kotsev, Vlado Cetl,<br>
>>> Lorena Hernandez, Michael Lutz, Daniele Francioli, Davide<br>
>>> Artasensi, Emanuela Epure, Fabio Vinci, Fabiano Spinelli,<br>
>>> Lukasz Ziemba<br>
>>> (<a href="https://callforpapers.2021.foss4g.org/foss4g2021/talk/ZKRWYN/" rel="noreferrer" target="_blank">https://callforpapers.2021.foss4g.org/foss4g2021/talk/ZKRWYN/</a><br>
>>> <<a href="https://callforpapers.2021.foss4g.org/foss4g2021/talk/ZKRWYN/" rel="noreferrer" target="_blank">https://callforpapers.2021.foss4g.org/foss4g2021/talk/ZKRWYN/</a>>)<br>
>>> + FOSS4G 2022: *ETF testing framework: past, present and<br>
>>> future *by Jon Herrmann, Marco Minghini, Clemens Portele,<br>
>>> Michael Lutz (submitted and currently under review)<br>
>>><br>
>>> * *With around 50 applications installed on OSGeo-Live, us core<br>
>>> packagers do not have the time to liaise with every single project<br>
>>> email list for each OSGeo-Live release. So we require a volunteer<br>
>>> (or two) to take responsibility for liaising between OSGeo-Live and<br>
>>> the project's communities. This volunteer will be responsible for<br>
>>> ensuring the install scripts and English documentation are updated<br>
>>> by someone for each OSGeo-Live release. Also test that the installed<br>
>>> application and Quickstart documentation works as expected on<br>
>>> release candidate releases of OSGeo-Live. Who will act as the<br>
>>> project's liaison person. *<br>
>>> o Enrique Soriano (jenriquesoriano at <a href="http://guadaltel.com" rel="noreferrer" target="_blank">guadaltel.com</a>) and José<br>
>>> Barrero (josebarrero at <a href="http://guadaltel.com" rel="noreferrer" target="_blank">guadaltel.com</a>)<br>
>>><br>
>>> * *OSGeo-Live is Ubuntu Linux based. Our installation preference is: *<br>
>>> 1. Install from UbuntuGIS or DebianGIS<br>
>>> 2. Install .deb files from a PPA<br>
>>> 3. Write a custom install script<=== preferred option*<br>
>>> *<br>
>>> *Can you please discuss how your application will be installed. *<br>
>>> o Write a custom install script<br>
>>> * *OSGeo-Live is memory and disk constrained. Can the application run<br>
>>> in 512 Meg of RAM? *<br>
>>> o No. A machine with at least 4 GB Ram (8GB are recommended, 16 GB<br>
>>> and more if a large set of XML files are tested)<br>
>>> * *How much disk space will be required to install the application and<br>
>>> a suitable example application? *<br>
>>> o It depends on the tests executed, but 1 GB HDD can be enough.<br>
>>> * *We aim to reduce disk space by having all applications make use of<br>
>>> a common dataset. We encourage applications to make use of the<br>
>>> example datasets already installed: *<br>
>>> * *Each OSGeo-Live application requires a Project Overview available<br>
>>> under a CC By<br>
>>> <<a href="https://urldefense.com/v3/__http://creativecommons.org/licenses/by/3.0/__;!!DOxrgLBm!UvR1kftQcLgI0pIHnKKusY23bweSMhF9CdWZjAsWPgY49H9cK9Rs5HIqNIO4Ob1OYJp5E24$" rel="noreferrer" target="_blank">https://urldefense.com/v3/__http://creativecommons.org/licenses/by/3.0/__;!!DOxrgLBm!UvR1kftQcLgI0pIHnKKusY23bweSMhF9CdWZjAsWPgY49H9cK9Rs5HIqNIO4Ob1OYJp5E24$</a>> <br>
>>><br>
>>> and a Quickstart available under a CC By-SA<br>
>>> <<a href="https://urldefense.com/v3/__http://creativecommons.org/licenses/by-sa/3.0/__;!!DOxrgLBm!UvR1kftQcLgI0pIHnKKusY23bweSMhF9CdWZjAsWPgY49H9cK9Rs5HIqNIO4Ob1OtUoN0gs$" rel="noreferrer" target="_blank">https://urldefense.com/v3/__http://creativecommons.org/licenses/by-sa/3.0/__;!!DOxrgLBm!UvR1kftQcLgI0pIHnKKusY23bweSMhF9CdWZjAsWPgY49H9cK9Rs5HIqNIO4Ob1OtUoN0gs$</a>> <br>
>>><br>
>>> license. (You may release under a second license as well). Will you<br>
>>> produce this? *<br>
>>> o Yes<br>
>>> * *In past releases, we have included Windows and Mac installers for<br>
>>> some applications. It is likely we won't have space for these in<br>
>>> future releases. However, if there is room, would you be wishing to<br>
>>> include Windows and/or Mac installers? *<br>
>>> o No<br>
>>><br>
>>><br>
>>> _______________________________________________<br>
>>> osgeolive mailing list<br>
>>> <a href="mailto:osgeolive@lists.osgeo.org" target="_blank">osgeolive@lists.osgeo.org</a><br>
>>> <a href="https://lists.osgeo.org/mailman/listinfo/osgeolive" rel="noreferrer" target="_blank">https://lists.osgeo.org/mailman/listinfo/osgeolive</a><br>
>><br>
>><br>
><br>
><br>
<br>
<br>
-- <br>
Angelos Tzotsos, PhD<br>
President<br>
Open Source Geospatial Foundation<br>
<a href="http://users.ntua.gr/tzotsos" rel="noreferrer" target="_blank">http://users.ntua.gr/tzotsos</a><br>
<br>
_______________________________________________<br>
osgeolive mailing list<br>
<a href="mailto:osgeolive@lists.osgeo.org" target="_blank">osgeolive@lists.osgeo.org</a><br>
<a href="https://lists.osgeo.org/mailman/listinfo/osgeolive" rel="noreferrer" target="_blank">https://lists.osgeo.org/mailman/listinfo/osgeolive</a><br>
</blockquote></div><br clear="all"><br>-- <br><div dir="ltr" class="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><pre>Georepublic UG (haftungsbeschränkt)
Salzmannstraße 44,
81739 München, Germany
Vicky Vergara
Operations Research
eMail: vicky@<a href="http://georepublic.de" target="_blank">georepublic.de</a>
Web: <a href="https://georepublic.info" target="_blank">https://georepublic.info</a>
Tel: +49 (089) 4161 7698-1
Fax: +49 (089) 4161 7698-9
Commercial register: Amtsgericht München, HRB 181428
CEO: Daniel Kastl
<span></span></pre></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div>