<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">Hi Cameron,<br>
<br>
The outstanding issues from the pycsw Provenance Review are:<br>
<br>
1. The OSGeoLive pycsw installer script was maintained in pycsw
source tree before pushing changes to OSGeoLive. Since the license
for the installer is LGPL, there is a conflict. <br>
I just removed the installer from the pycsw tree. It is <b>not</b>
used by pycsw. Problem solved.<br>
<a class="moz-txt-link-freetext" href="https://github.com/geopython/pycsw/issues/302">https://github.com/geopython/pycsw/issues/302</a><br>
<br>
2. The OGC schemas are included in pycsw to validate incoming XML
requests. This discussion started when we pushed pycsw as a
package to Debian. Debian developers identified the license
problem and reported back to us. There is a discussion between
OSGeo, OGC and DebianGIS on standards mailing list and we hope
this will be resolved soon, not only for pycsw but also for
various other OSGeo projects (both graduated and not) that include
OGC schemas in their code tree.<br>
<a class="moz-txt-link-freetext" href="https://github.com/geopython/pycsw/issues/306">https://github.com/geopython/pycsw/issues/306</a><br>
Thanks Sebastiaan for this excellent e-mail with many details on
this issue: <br>
<a class="moz-txt-link-freetext" href="http://lists.osgeo.org/pipermail/standards/2015-February/000842.html">http://lists.osgeo.org/pipermail/standards/2015-February/000842.html</a><br>
<br>
Just to be clear: there is no library conflict in pycsw, the
source code is clean.<br>
<br>
Best,<br>
Angelos<br>
<br>
On 02/15/2015 09:37 PM, Cameron Shorter wrote:<br>
</div>
<blockquote cite="mid:54E0F585.3080802@gmail.com" type="cite">Hi
Angelos,
<br>
I'd suggest that it is ok to have outstanding issues with the
provenance review, so long as each issue has an acceptable
workaround.
<br>
Eg: if there is a conflict with a license of an included library,
then the work around could be to download the library separately.
<br>
There should also be a statement about what the project plans are
around the issue. Maybe you are planning to rewrite the library,
or maybe you are approaching the library authors to get access to
the code under another license.
<br>
<br>
Thanks for addressing the other issues.
<br>
<br>
<br>
</blockquote>
<br>
<br>
<pre class="moz-signature" cols="72">--
Angelos Tzotsos
Remote Sensing Laboratory
National Technical University of Athens
<a class="moz-txt-link-freetext" href="http://users.ntua.gr/tzotsos">http://users.ntua.gr/tzotsos</a></pre>
</body>
</html>