<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 10pt;
font-family:Tahoma
}
--></style></head>
<body class='hmmessage'><div dir='ltr'>
<br><br><div><div id="SkyDrivePlaceholder"></div>> Date: Sun, 29 Jan 2012 12:11:33 -0800<br>> From: hamish_b@yahoo.com<br>> Subject: Re: [Live-demo] pycsw in OSGeo Live.<br>> To: gcpp.kalxas@gmail.com; cameron.shorter@gmail.com<br>> CC: live-demo@lists.osgeo.org<br>> <br>> Last April Cameron wrote:<br>> > My initial feeling is that it would be great to<br>> > include pywcs in a future release of OSGeo-Live,<br>> <br>> (for the record we did ship it with the 5.0 release,<br>> just didn't list it on the contents page.)<br>> <br>> > but as pywcs is still only at a 0.1 release,<br>> <br>> version numbers are meaningless. ignore and forget<br>> them and judge the app on the app instead.<br>> <br><br>FYI pycsw is at 1.0.0 (which is what looks like is included with 5.0), with 1.2.0 scheduled for April 2012. What's the timeline for the next livedvd release?<br><br>> > without wide uptake yet,<br>> <br>> for FOSS that metric is rather impossible to know,<br>> but anyway if it is good, hence a great reason to<br>> include it on the disc- to get it wide exposure!<br>> chickens and eggs...<br>> <br><br>Agreed, we do know pycsw is being tested/prototyped in various environments, and that exposure on the livedvd would be beneficial for those looking for a Python CSW (many CSWs are Java-based).<br><br>> > it is premature to include pywcs into the next<br>> > OSGeo-Live release.<br>> <br>> If it's buggy or incomplete that's one thing. If<br>> it is just unknown that's a very different matter,<br>> and something we can help with.<br>> <br>> <br><br>pycsw makes a point of passing OGC CITE and it's own testing framework as enhancements/fixes are commited. We feel is complete enough for a user to stand up an operational CSW catalogue (with transactions if desired as well).<br><br>> I suggest to review and improve the overview and<br>> quickstart reST pages, then make the final call on<br>> whether to keep it listed on the contents page once<br>> we get feedback from our beta testers. (a great<br>> incentive to make the overview page clear about<br>> what the user should expect, and to make the<br>> quickstart clear about how to go about doing it)<br>> <br>> <br><br>We would be glad to update these pages as appropriate. Thanks!<br><br>..Tom<br><br><br></div> </div></body>
</html>