New developer concern - why a not Git

[till]

You mean a two way sync, so that all changes made in github are synced back automatically to the correct branches in svn even if they are based on external forks etc? I dont think that this will work reliably.

[cfoe]

you are right. a sync in both directions would be too unreliable and very complicated to setup.
I would only go for a periodic pull to keep the GitHub repo up-to-date

[vStone]

The main problem with using git and svn is that git will rewrite its history when pushing the changes to svn.

A one way sync from svn to git would be an option. Git users can provide patches easy enough if they would want to.

I'd prefer the ispconfig organization to setup a github organization but I could easily set up the svn sync in a cronjob on my server. Or you can do that yourselves too

I'm vStone on github, feel free to poke me for any git relates issues.

[vStone]

You can also map svn author/usernames to proper Names with email address, but that would require somebody to provide that list.

[till]

ISPConfig has already a github account and we might test it in future. At the moment we use svn only and all devs interested in contributing to ispconfig can get access to our svn server.

[cfoe]

@vStone:
How about setting up the GitHub repo with sync from the SVN (one-way)?
I would really like to fork the tags to create install packages for my servers with internal settings (templates, etc.) from the release packages.

I do not see an "ISPConfig" organization on GitHub. You could create it if it really is not existing and later port it to Tills account if need be.

[till]

I will setup a ispconfig organisation on github.

[cfoe]

I have setup a first svn2git mirror and would be happy to setup one for the ispconfig repo. If you like I could push it to https://github.com/ispconfig

[Croydon]

Please don't. I really prefer to stay with svn and I am not interested in digging into git to be able to continue contributing to ispc.

[cfoe]

It is a mirror not a sync