Working around an empty TFS deployment is useless. Ultimately the whole point of setting up such infrastructure is to support our software development projects. That means we need to be working on an active project in order to witness the benefits that VSTS can really offer. There are two ways about it:
I tend to favour the latter option. Not only does this give us a sizable chunk of code base (which works), we even get to read and study the coding styles and patterns of other developers. One thing that can make us better developers is to actively seek out good code and read it. Of course, that will become more of a maintenance and enhancement project rather than a brand-new project.
Of course, there is no stopping us from simultaneously doing both ;-) But let us take it easy and do things a step at a time.
I'd like to hear your ideas and suggestions of what projects out there is piquing your interest.
The melody of logic will always play out the truth. ~ Narumi Ayumu, Spiral
Notable projects
Community Server 2008.5 (SP2)
ScrewTurn wiki
DotNetNuke 5
CS 2008.5
microlau Blog: http://community.sgdotnet.org/blogs/microlau
Did you all progress?
Best Regards, Kit Kai, MVP (SharePoint Portal Server)
I have already stored some of the project source into VSS and did conversion exercises over to TFS.
Not thoroughly meaningful, as the VSS database essentially carried zero history of changes.