Search · Index

Migration from CVS to GIT

Tools to consider for the migration (?):

• GIT includes a tool for the migration of CVS repositories called git-cvsimport.
• The cvs2svn project provides support for converting a CVS repository into GIT. The tool is called cvs2git

Structure of the GIT Repository (?):

• One git repository hosting the entire code base of openacs ( including contrib and all packages ). 
• Provide separate git repositories; one hosting the core packages and independent repositories for each of the other packages. 

Where could the repositories live (?):

• Official repositories on openacs.org machine? (Perhaps setting up git.openacs.org)  and having remote-mirrored repositories on github so developers can clone and share patches using github. -- jiml: many tools which could get similar function to github (forking, pull requests),,, what would be required to get a git.openacs.org?  can we put up a gitorious on a test site with maybe 50gb of repo space so all the committers can have their own?
  
• Using github.com as our official nest. (jiml says: there's a 300mb limit, and a full repo is over that, jcdny says: asked the github admins and they said limit is "soft, and only enforced to prevent abuse")

Points to consider before | when migrating to GIT: 

• Application for voting on oct-elections depends on commits history ( most likely this will transparent since we use fisheye.openacs.org  for fetching information about commit history , and fisheye provides one and one only interface for querying data, so the fact that the code is being controlled by cvs or git is irrelevant)
• Installing-software-from-repository code is based on channels and cvs-tags in order to define which channels are available to users ( http://openacs.org/repository/) and to provide the recent packages for that channel.  The same tags can be used in git as well, but the code retrieving this information has to be rewritten.
• It is necessary to provide git-guidelines similar to cvs-guidelines