<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">+1 Totally agree!<div><br></div><div>-Adam</div><div><br><div><div>On Jun 22, 2012, at 10:44 AM, Angelos Tzotsos wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite">
<meta content="text/html; charset=ISO-8859-1" http-equiv="Content-Type">
<div bgcolor="#FFFFFF" text="#000000">
Hi Tom,<br>
<br>
+1 on moving to github now. <br>
It has been a quiet period on svn and this is great opportunity.<br>
<br>
OWSLib should be used outside of pycsw as a dependency. This is why
I am now creating packages for OWSLib on all major platforms, in
order to have this in place for 1.4.0.<br>
Also +1 on pip, easy_install solution :)<br>
<br>
Regards,<br>
Angelos<br>
<br>
<br>
On 06/22/2012 03:30 AM, Tom Kralidis wrote:
<blockquote cite="mid:BAY151-W30A204FBF7090642E4E29ABAFC0@phx.gbl" type="cite">
<pre wrap="">
All: there has been discussion in migrating the codebase from svn to git, which will gives us all the benefits of using git, as well as using github as the platform, with its many features.
Currently, we have pycsw on github (<a class="moz-txt-link-freetext" href="http://github.com/geopython/pycsw">http://github.com/geopython/pycsw</a>) which is a mirror of our <a href="http://sf.net">sf.net</a> svn repo.
I propose the following:
- issue tracker: port tickets from <a href="http://sf.net">sf.net</a> trac to github issues. I've tested this with success at <a class="moz-txt-link-freetext" href="https://github.com/tomkralidis/pycsw-trac-test/issues">https://github.com/tomkralidis/pycsw-trac-test/issues</a>
- codebase: I've updated the github mirror to include all branches/tags
- wiki: we don't have too much content, so this will not be much porting
- website: unchanged, since we use OSGeo infrastructure
The one issue we will need to investigate is the OWSLib dependency, which is currently an svn external (OWSLib has migrated to github, so we have to update this regardless), so we could use either a setup.py install_requires parameter or use pip.
I will take care of the migration and update the release packaging steps. The codebase is quiet right now so it would be a good time to migrate.
Thoughts/comments/objections?
Thanks
..Tom
</pre>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
pycsw-devel mailing list
<a class="moz-txt-link-abbreviated" href="mailto:pycsw-devel@lists.osgeo.org">pycsw-devel@lists.osgeo.org</a>
<a class="moz-txt-link-freetext" href="http://lists.osgeo.org/mailman/listinfo/pycsw-devel">http://lists.osgeo.org/mailman/listinfo/pycsw-devel</a>
</pre>
</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>
</div>
_______________________________________________<br>pycsw-devel mailing list<br><a href="mailto:pycsw-devel@lists.osgeo.org">pycsw-devel@lists.osgeo.org</a><br>http://lists.osgeo.org/mailman/listinfo/pycsw-devel<br></blockquote></div><br></div></body></html>