Not so much of a trouble a the Trac side. There is FOSS everywhere, a lot of modularity and flexibility. No quite the same at the other side.
I've read about the trouble even with one-time migration from SVN to TFS. Despite the source is all open and well documented, there no evidence of good support, that should tell you much about the chance for getting even more - constant synchronization.
Not so much of a trouble a the Trac side. There is FOSS everywhere, a lot of modularity and flexibility. No quite the same at the other side.
I've read about the trouble even with one-time migration from SVN to TFS. Despite the source is all open and well documented, there no evidence of good support, that should tell you much about the chance for getting even more - constant synchronization. Facts: MS SQL server is the base for TFS.No connector available for MS SQL server as a Trac db backend, although there are several python bindings to MS SQL server available, or the option to connect via ODBC.
But just an option, nothing ready AFAIK. I'm not aware of any well documented open TFS API as foundation for migration and integration. And I'm not convinced this will ever change.
At Redmont they are reportedly only considering what seems important to themselves: "helping customers with IBM Rational ClearCase and ClearQuest tools. " And most probably it this behavior will persist and SVN/Trac keeps very low on the ToDo for them. Edit2 While TFS has some support for bidirectional communication, these scenarios are not recommended.
It mostly aims at integration, read: sucking information in, not communicating with other information systems like Trac. Edit Just for sub-task of repository browsing you could try to write code to push a duplicate of changes to another (SQLite|MySQL|PostgreSQL) repo that Trac supports right now. But I consider this is rather wasteful and ugly, and fact remains, that it's hard, if possible at all, to do the same tracking without such big code duplication.
Ultimately, if you want to live without the actual check-in source changes you must at the very least send information about the meta-data like resource ID's (for link generation) to find the data in TFS. I'm looking into that right now.So take the following as half-educated advise to the best of my knowledge and feel free to correct/discuss.
I don't really need Trac to integrate with TFS's work item tracking. If all it did was track check-ins with their associated comments, I'd call it good enough. What we're really trying to achieve is a development-friendly wiki/milestone tracker.
I just don't like Sharepoint's implementation of a Wiki and I don't feel like asking for a PO for the tools out there to make it more like a Wiki. – villecoder Nov 21 at 14:50 I see, but how would you do tracking without access to the check-ins? That has been one of my major concerns, but I've added more thoughts to answer your comment.
– hasienda Nov 21 at 20:59 2 Maybe you could de-ramble this a wee bit and have a bit less rumour/speculation? – Kev? Dec 7 at 1:54 Not an easy task, but I'll try.
Thanks for asking. – hasienda Dec 7 at 21:36 For what it's worth, the TFS API for migration and synchronization is available, the TFS Integration Platform: tfsintegration.codeplex. Com – Edward Thomson Dec 7 at 21:59.
I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.