Gerhard Killesreiter wrote:
What we coud do (as long as the relevant backend for the project module exists) is to move core development to git. There we are free of social reasons.
This sounds like an excellent idea! The only problem is having to maintain two seperate version control systems at the same time. On a related point: if this works for core, would it not make sense to allow contrib maintainers the option to use Git instead of CVS? Make Git optional and contrib maintainers can move over at their own speed. If/when a Windows GUI client becomes available for example. It would also be interesting to see how many people stick with CVS, if nearly everyone switches their modules/themes to Git, CVS could be deprecated pretty quickly. Just throwing some ideas around. Sorry if this has all been said before. :) Kind Regards, Liam McDermott.