<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">Hi all,<br>
<br>
This is interesting:<br>
<br>
SourceForge is now moving its projects to a new open platform
called OpenForge or Allure and it is something similar to github
BUT completely open source :)<br>
<br>
<a class="moz-txt-link-freetext" href="https://sourceforge.net/p/allura/wiki/Allura%20Wiki/">https://sourceforge.net/p/allura/wiki/Allura%20Wiki/</a><br>
<br>
One can upgrade an existing project with one click! The new
platform supports Git, Mercurial, Subversion, Bazaar and can be
hosted in a private server. \o/<br>
<br>
So basically I propose to stay on github, since all the work has
been done, but at the same time upgrade the SF project and switch
to git there too. People will be able to clone from SF too...<br>
<br>
Thoughts?<br>
Angelos<br>
<br>
<br>
<br>
On 06/22/2012 03:30 AM, Tom Kralidis wrote:<br>
</div>
<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 sf.net svn repo.
I propose the following:
- issue tracker: port tickets from sf.net 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>
</body>
</html>