Disclaimer - I'm not a direct contributor. But I have: - transitioned from Visual-Source-Safe (Ugh!!!) to SVN; - Mercurial to Git; - TFS to Git; And I have lead («led») 2 teams through Git adoption, one very successfully, one still undergoing with very little success.
This is what I want to say about that: #1 - Welcome to the 21st century... This is exactly what Git was built for, with pull requests and what not. #2 - SVN is becoming a dying art, it might become harder over time to get new people interested in interacting with SVN projects. #3 - Most importantly, I have to support sebb's answer - such change is somewhat impactful on the developers, due to the habits that they've grown, the ways they are used to working in, etc. «Old habits die hard» is the reason my most recent adoption project is struggling to gain traction - it's easy'ish but not trivial to learn Git (though using it wrapped up around a tool like TortoiseGit helps tons) and sometimes people are quite resistant to change their ways. This clearly qualifies as a risk, as there's the potential for people to use it incorrectly if they lack knowledge and experience (doing git "rebase" comes to mind :D ). Regards, Paulo Augusto Maia Borges WWVzLCBJJ20gZ2Vla3kuIEJ1dCBzbyBhcmUgeW91IQ== The information in this e-mail and any attachments is confidential and may be legally privileged. It is intended solely for the addressee or addressees. Any use or disclosure of the contents of this e-mail/attachments by a not intended recipient is unauthorized and may be unlawful. If you have received this e-mail in error please notify the sender. Please note that any views or opinions presented in this e-mail are solely those of the author and do not necessarily represent those of TEMENOS. We recommend that you check this e-mail and any attachments against viruses. TEMENOS accepts no liability for any damage caused by any malicious code or virus transmitted by this e-mail.
