[CZT-Devel] CZT source code migrated to Git

[Andrius V. <an...@ve...>]

Hi everyone,

Thanks for the comments :) It looks like at least the majority of administrators prefer to go with Git. So since there has not been very recent activity in SVN commits, I thought I may just migrate it.

I have added the Git repository to the project and migrated SVN contents to it. If anyone is interested, I used SubGit (http://subgit.com/) to perform the migration, because it has nicer way of handling file ignores and tags than the default git-svn. Afterwards there was some manual tinkering with the tags (converting from lightweight to annotated), but in general the process is quite straightforward.

If you go to https://sourceforge.net/projects/czt/develop there are new links to clone the Git repository. There is a read-only link for public access, as well as developer access via ssh when you log-in.

From there on it looks like there are no specific requirements to use Git within SourceForge. The guidelines and some hints are available in their Git documentation: https://sourceforge.net/apps/trac/sourceforge/wiki/Git . They recommend using the SourceForge e-mail when committing (possibly they would have links to authors in the new platform) - it can be set up in your repository configuration after cloning:

git config user.name "YOUR NAME"
git config user.email "USE...@us..."

I used this convention during migration - everyone's commits are attributed to their SourceForge e-mail.

So I guess from now on Git repository should be the place to commit new code to CZT. To avoid accidental commits to SVN, I have disabled write access to that repository. It is still available as read only though - should we remove it altogether? Or provide some 'transitional' time window as a 'backup' - e.g. remove it when everyone is more or less comfortable with the Git repository?

Git repository write access is currently only available to project administrators. Should it be enabled for all developers? Looking at repository logs a lot of them have not contributed anything for a long time.. Otherwise there may be less incentive to give full write access to occasional contributors. Since Git is distributed version control system, I think the preferred way is for everyone to fork the main repository and then their changes are pulled back by the main repository maintainers..

Thanks for the support! This is the first step - now we can start looking into merging the main branches and releasing a new version sometime. Please report if there are any problems with the migrated repository..

~Andrius