Here are some snippets of the emails I got from TFS Migration Blog owner: "Unfortunately, in the case of SVN, our team cannot develop a migration tool for TFS. The reasons behind this are legal in origin, and it has our team's hands tied. Believe me, if we could build it, we would - I get requests from customers all the time."
"Legal reasons was not an accurate term... it is about intellectual property protection. We can't bring the SVN source in house to develop a migration tool without risking IP taint to our own product. However, we are taking another look at our options here to provide a tool." That was February 2008. On Tue, Jan 20, 2009 at 8:54 AM, David Kean <[email protected]>wrote: > (By the way, I made a mistake below, ASP.NET MVC is not actually > 'open-source' according to the OSI guidelines) > > > > I'm not a lawyer, so take anything I say with a grain of salt. I also can't > speak with regards to the SVN -> TFS converter issue itself. > > > > I also wasn't trying to turn it into a flame way, I was just trying to get > across that at Microsoft there is a big difference between releasing code as > open source*, and looking at and using non-Microsoft developed open source > software in a product. > > > > > How did you prevent "ideas" leaking across then? > > Microsoft has a bunch of lawyers that make sure that we don't infringe on > copyrights, patents, etc. > > > > And of course we use already existing ideas – there wouldn't be any > innovation by anyone if ideas weren't borrowed and extended upon. ;) > > > > * Unfortunately, even releasing open-source products today at Microsoft is > tough. My team, the Managed Extensibility > Framework<http://www.codeplex.com/MEF>, > is trying to break the mold, one library at a time. > > > > *From:* [email protected] [mailto:[email protected]] *On Behalf Of *Richard > Banks > *Sent:* Monday, January 19, 2009 1:56 PM > *To:* [email protected] > *Subject:* RE: Source code migration from SVN to TFS > > > > Hi David, > > > > Don't take this the wrong way... but you're worried about "ideas" from the > open source world ending up in TFS? Or is it just ideas backed up by patent > lawyers? J > > > > It's a very weak argument you are making. I'm pretty sure the open source > world (CVS, SVN, et al) gave us proper branching & merging in source control > before TFS. And I'm also pretty sure that CruiseControl gave us the idea of > CI/Build systems before Team Build turned up. I'm also pretty sure that > NUnit was around before MSTest turned up – in Microsoft hired one of the > guys who invented NUnit (Jim Newkirk). How did you prevent "ideas" leaking > across then? > > > > Anyway, I don't want to turn this into a flame war, since it adds little > value to the community so I'll drop the discussion. Though I will finish by > saying that I still believe that integration with SVN requires neither ideas > or code to be (inadvertently or otherwise) in TFS, yet I also realise that > you won't be adding any support for it. > > > > Regards, > > *Richard Banks > *CSM | CSP | http://richardsbraindump.blogspot.com | > http://twitter.com/rbanks54 > > > > *From:* [email protected] [mailto:[email protected]] *On Behalf Of *David Kean > > *Sent:* Tuesday, 20 January 2009 6:23 AM > *To:* [email protected] > *Subject:* RE: Source code migration from SVN to TFS > > > > There's a difference between looking at competing product's source code and > solely developing an open source product such as ASP.NET MVC. The former > can lead to what we call 'taint'. If code or ideas inadvertently (whether > deliberately or not) end up in a product such as TFS, and that code or ideas > ended up infringing on someone else's copyright or patent, Microsoft now > leaves itself open to be sued. > > > > *From:* [email protected] [mailto:[email protected]] *On Behalf Of *Richard > Banks > *Sent:* Sunday, January 18, 2009 3:37 PM > *To:* [email protected] > > *Subject:* RE: Source code migration from SVN to TFS > > > > >> We contacted Microsoft, but they will not write a migration path for > SVN due to legal issues of having SVN source in house, compromising TFS. > > Pfft. SVN is open source. You don't need to bring it in house to see the > source, you can just browse it on the web ( > http://svn.collab.net/viewvc/svn/trunk/). Also, the license for SVN is > hardly restrictive (http://subversion.tigris.org/license-1.html) so they > could do just about anything they like with it and it wouldn't "infect" TFS. > > > > > My guess is that SVN to TFS migration just isn't anywhere near being a > priority and being worth development dollars. Blaming it on licensing issues > is just a marketing ploy. ScottGu and the ASP.NET MVC team seem to be > dealing with the legality issues of integrating with open source just fine. > > > > Not that this helps you, of course :-( > > > > Regards, > > *Richard Banks > *CSM | CSP | http://richardsbraindump.blogspot.com | > http://twitter.com/rbanks54 > > *From:* [email protected] [mailto:[email protected]] *On Behalf Of *Matthew > Rowan > > *Sent:* Monday, 19 January 2009 10:09 AM > *To:* [email protected] > *Subject:* Re: Source code migration from SVN to TFS > > > > We went down this path, and I believe tried out that product also, but it > was so riddled with bugs, it just wasted our time. TFS Migration toolkit was > also disappointing, but maybe the later version is better. We contacted > Microsoft, but they will not write a migration path for SVN due to legal > issues of having SVN source in house, compromising TFS. > > We ended up unfortunately abandoning our history and starting clean in TFS. > We have just left SVN live, if people really need to see the older history > they can go to SVN. Although, we generally haven't really found a need for > it. > > > > On Fri, Jan 16, 2009 at 1:58 AM, Dave Zimmerman <[email protected]> > wrote: > > Have you investigated Kryosoft's tool: SVN-2-TFS? > > > > http://www.kyrosoft.com/ > > > > > > _________________________ > > Dave Zimmerman > > office: 651.994.8558 x32 > > mobile: 651.246.2378 > > [email protected] > http:// <http://www.intertech.com/> > ------------------------------ > <http://www.intertech.com/> > Support procedure: <http://www.intertech.com/> > https://www.codify.com/lists/support > List address: [email protected] > Subscribe: [email protected] > Unsubscribe: [email protected] > List FAQ: > http://www.codify.com/lists/oztfs > < > > ------------------------------ > Support procedure: https://www.codify.com/lists/support > List address: [email protected] > Subscribe: [email protected] > Unsubscribe: [email protected] > List FAQ: http://www.codify.com/lists/oztfs > Other lists you might want to join: http://www.codify.com/lists > /span>Other lists you might want to join: http://www.codify.com/lists > > www.intertech.com/ > > *Instructors** Who Consult. | **Consultants** Who Teach.™* > > *Come join us at the vstsMN User Group > *(*http://vstsmn.net*<http://vstsmn.net/> > *)* > > > > *From:* [email protected] [mailto:[email protected]] *On Behalf Of *Dylan > Tusler > *Sent:* Wednesday, January 14, 2009 9:13 PM > *To:* [email protected] > *Subject:* Source code migration from SVN to TFS > > > > I'm sure this comes up from time to time. I was googling on the subject, > and there appear to have been a number of small apps developed in the past > to assist with migrating code from Subversion to TFS, but I didn't see any > stand-outs, and some that I checked seem to be completely dead now. > > > > Has anyone done this kind of migration recently? And have any input? What > (apart from cracking open the TFS Migration Toolkit and DIYing it) are the > best options? > > > > We are amalgamating with another council that has some of their source code > in SVN, and it would be nice to migrate it. > > > > Ta, > > Dylan Tusler > Team Leader - Development, Data and Integration Unit > Information Technology > Sunshine Coast Regional Council > ph: +61 (0)7 5441 8202 > "Your Technology Solutions Partner" > > > > > ------------------------------------------------------------------------------------------------- > The Sunshine Coast Regional Council is now open for business. There is > nothing you need to do as we have taken care of everything for you to ensure > it is business as usual. Please continue to do business with your local > Council office where you will still find the same friendly faces and the > same great service. For further information head to the Sunshine Coast > Regional Council website: www.sunshinecoast.qld.gov.au > > This email, together with any attachments, is intended for the named > recipient(s) only. Any form of review, disclosure, modification, > distribution and or publication of this email message is prohibited without > the express permission of the author. Please notify the sender immediately > if you have received this email by mistake and delete it from your system. > Unless otherwise stated, this email represents only the views of the sender > and not the views of the Sunshine Coast Regional Council. > > maile 2_7_5 > ------------------------------ > > Support procedure: https://www.codify.com/lists/support > List address: [email protected] > Subscribe: [email protected] > Unsubscribe: [email protected] > List FAQ: http://www.codify.com/lists/oztfs > Other lists you might want to join: http://www.codify.com/lists > ------------------------------ > > Support procedure: https://www.codify.com/lists/support > List address: [email protected] > Subscribe: [email protected] > Unsubscribe: [email protected] > List FAQ: http://www.codify.com/lists/oztfs > Other lists you might want to join: http://www.codify.com/lists > > > ------------------------------ > > Support procedure: https://www.codify.com/lists/support > List address: [email protected] > Subscribe: [email protected] > Unsubscribe: [email protected] > List FAQ: http://www.codify.com/lists/oztfs > Other lists you might want to join: http://www.codify.com/lists > ------------------------------ > > Support procedure: https://www.codify.com/lists/support > List address: [email protected] > Subscribe: [email protected] > Unsubscribe: [email protected] > List FAQ: http://www.codify.com/lists/oztfs > Other lists you might want to join: http://www.codify.com/lists > ------------------------------ > > Support procedure: https://www.codify.com/lists/support > List address: [email protected] > Subscribe: [email protected] > Unsubscribe: [email protected] > List FAQ: http://www.codify.com/lists/oztfs > Other lists you might want to join: http://www.codify.com/lists > -------------------------------------------------------------------------------- Support procedure: https://www.codify.com/lists/support List address: [email protected] Subscribe: [email protected] Unsubscribe: [email protected] List FAQ: http://www.codify.com/lists/oztfs Other lists you might want to join: http://www.codify.com/lists
