[pycsw-devel] migration to github

[Tom Kralidis]

Angelos: thanks for the info.  I'm -0 here on this one, as I'm not sure of the value for the level of effort.

Having said this, I will check the sf.net svn access logs to see how much access the old SVN repo has.

Date: Fri, 13 Jul 2012 02:42:46 +0300
From: gcpp.kalxas at gmail.com
To: pycsw-devel at lists.osgeo.org
Subject: Re: [pycsw-devel] migration to github


  
    
  
  
    Hi all,

      

      This is interesting:

      

      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 :)

      

      https://sourceforge.net/p/allura/wiki/Allura%20Wiki/

      

      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/

      

      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...

      

      Thoughts?

      Angelos

      

      

      

      On 06/22/2012 03:30 AM, Tom Kralidis wrote:

    
    
      
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 (http://github.com/geopython/pycsw) 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 https://github.com/tomkralidis/pycsw-trac-test/issues
- 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

 		 	   		  

      

      
      

      _______________________________________________
pycsw-devel mailing list
pycsw-devel at lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/pycsw-devel

    
    

    

    -- 
Angelos Tzotsos
Remote Sensing Laboratory
National Technical University of Athens
http://users.ntua.gr/tzotsos
  


_______________________________________________
pycsw-devel mailing list
pycsw-devel at lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/pycsw-devel 		 	   		  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/pycsw-devel/attachments/20120717/a8d066bb/attachment.html>