<div dir="ltr"><div dir="ltr">I think there is a MOU between OSGeo and OGC to handle this sort of thing, see website (<a href="https://www.osgeo.org/partners/ogc/">https://www.osgeo.org/partners/ogc/</a>), OSGeo also has interoperability as one of the groups goals (so it is a good activity to request funding for).<br clear="all"><div><div dir="ltr" class="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div>--</div><div>Jody Garnett</div></div></div></div></div></div><br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Fri, 23 Oct 2020 at 09:05, Régis Haubourg <<a href="mailto:president@osgeo.asso.fr">president@osgeo.asso.fr</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);padding-left:1ex">Hi all,<br>
<br>
During the last two years, I have been in running the official<br>
certification process for QGIS.org and QGIS server.<br>
<br>
We have certified [0] QGIS server for WMS 1.3 and more recently the OGC<br>
APIF 1.0.<br>
<br>
Up to now, the OGC team has been very helpful by kindly giving us the<br>
reference implementation status, which implies no fees to pay.<br>
<br>
But this changed just now with a more strict policy - see the response<br>
below [4] - which ends up in having to pay 300 euros for each<br>
certification process and yearly renewal process.<br>
<br>
QGIS.org could eventually afford this budget, but I'm not sure smaller<br>
OSGeo project can.<br>
<br>
Furthermore, this manual process is already time consuming, a bit<br>
bureaucratic, and given that we run continuous integration with OGC<br>
compliance tests [1], we will probably not struggle to get certified so<br>
often under these new conditions. That is a bit sad since open source<br>
really go together with public standards.<br>
<br>
Do we have any agreement at the OSGeo level that would ease this part ? <br>
(I checked the wiki [2] first of course)<br>
<br>
<br>
Thanks for your inputs,<br>
<br>
Best regards<br>
<br>
Régis<br>
<br>
---<br>
<br>
President of the french local Chapter / QGIS contributor<br>
<br>
<br>
[0]<br>
<a href="https://www.ogc.org/resource/products?display_opt=1&org_match=QGIS.org%20(OSGEO%20project)" rel="noreferrer" target="_blank">https://www.ogc.org/resource/products?display_opt=1&org_match=QGIS.org%20(OSGEO%20project)</a><br>
<br>
[1] <a href="https://github.com/qgis/QGIS/pull/38644" rel="noreferrer" target="_blank">https://github.com/qgis/QGIS/pull/38644</a><br>
<br>
[2] <a href="https://wiki.osgeo.org/wiki/OGC_Certification_Services" rel="noreferrer" target="_blank">https://wiki.osgeo.org/wiki/OGC_Certification_Services</a><br>
<br>
<br>
[4]<br>
<br>
On 22/10/2020 11:25, Gobe Hobona wrote:<br>
> We appreciate the work done by the QGIS and OSGeo community in<br>
> supporting OGC standards. Please note however that we are guided by<br>
> our policies, agreed on by the OGC Membership.<br>
><br>
> Please see Sections 5.5 and 6.3 of the Compliance Testing Policy<br>
> [<a href="https://portal.opengeospatial.org/files/?artifact_id=55234" rel="noreferrer" target="_blank">https://portal.opengeospatial.org/files/?artifact_id=55234</a>].<br>
><br>
> The fee is only waived for:<br>
><br>
> * The first three implementations to pass 100% of the compliance<br>
> procedure, while the test is in beta. We refer to these as Early<br>
> Implementers.<br>
> * The first two Reference Implementations that pass the test related<br>
> to a conformance class within a version of an Implementation Standard.<br>
><br>
<br>
_______________________________________________<br>
Discuss mailing list<br>
<a href="mailto:Discuss@lists.osgeo.org" target="_blank">Discuss@lists.osgeo.org</a><br>
<a href="https://lists.osgeo.org/mailman/listinfo/discuss" rel="noreferrer" target="_blank">https://lists.osgeo.org/mailman/listinfo/discuss</a></blockquote></div>