> Mark, how would you rate TFS if your process included allowing third parties > to contribute source?
Define third-party... if you mean "joe public", then TFS is not going to work at all, as they (rightly) expect indentifiable users (both from a licensing and ownership standpoint). If you mean "distributed users", the TFS has great support for setting up a "cache server" at a remote site that coordinates and caches file downloads (e.g. Microsoft's Atlanta campus gets zippy access to the Redmond campus repository because the TFS cache in Atlanta insures that the check-in/check-out file only crosses the WAN link once). This, of course, requires a VPN connection between the remote office and the main store. If you want access to the TFS stuff outside DevStudio, you could use the SourceGear (Vault people) TeamPrise client (which works from Macs Unix and inside the Eclipse IDE. If you need "joe public" access, you need to build your own front end, which is probably not worth the effort... just go Subversion. Now if all you need is public read-only access to the source, you can easily publish the source to any old web-server :) Hope that helps, Marc -- "Under capitalism, man exploits man. Under communism, it's just the opposite." –John Kenneth Gailbraith Marc C. Brooks mailto:[EMAIL PROTECTED] http://musingmarc.blogspot.com
