The git switch

[ent1ty]

I think I have successfully converted the whole Irrlicht repo to git, preserving branches and tags (see https://github.com/osense/irrlicht-git). I think it would be great if we could create a github organisation and put the repo there (i.e. make it official).
There could be a period of time when both the svn and git repos exist (though code can't move from git to svn, only the other way around). This would be great in the regard that people could already start forking the repo on github and submitting pull requests, even though they'd be merged in only after svn is abandoned (side note: I lost my modified copy of Irrlicht because I didn't bother pasting the patches on forums, seeing it would be ages before they made it in and well... because svn).

I'd be more than happy to set up the github things myself, if any devs okay it.

[endless_dark]

I would love using git.

[ent1ty]

Well, you already can (just clone the github repo), but it's not official, so no merging in pull requests... unless we want to start our own fork of irrlicht

[superpws]

I am in favor of git repo, because I find it so easy to contribute to projects. Patches in the SVN usually go unnoticed. I am sure Irrlicht will get more contribution if it's moved to Github.

[ent1ty]

Exactly - I would really like to make the Irrlicht git repo official on github asap, as I was hoping to create some pull requests myself but want to avoid svn like death. Svn just makes it a lot harder for the community to contribute, especially with github forks and merging in pull requests in the picture. I'm sure more people feel like that - while the svn repo is still being used, we could already start collecting pull requests in the git repo and merge them in when the svn is finally abandoned.
However, it seems CuteAlien has been avoiding this topic I understand you (CA) don't want to be bothered with this right now, as you're trying to get 1.9 out and then switch to git. I guess that's fair enough, only I'm afraid it might take a longer time to do the release and we'll be stuck with svn for another 6 months. No danger in creating an official git copy of the svn repo on github right now though, I don't think - like I said, I can set up everything myself, if that (lack of time) is part of the issue.

[CuteAlien]

Patches in the SVN usually go unnoticed.

It's patches without tests that go unnoticed ;-) Or patch-bombs which put everything together...