It's real hard to do, I know, I fail at it all the time, but if we pull off this centralized code management thing, we're gonna need some code standards.
This includes things like comments and indentation for readability, as well as slew of technical things, but I figure we can start with comments and readability.
As you make you changes, look at the quality and quantity of the comments that exist thruout the code. From the VSS comments at the top, that offer a brief description of a new change marked with a time stamp, to the per fucntion and per variable comments about what the function does (or how your change makes it different) and what each variable does, sometimes with even what the ranges do.
Also, pay close attention to the indentation they used, it makes it pretty readable, and any centralized repository will want to follow similar conventions.
Finally, look at the readme. If you make any changes to the Workspace or project files, make sure there is a short text file describing those changes.
We have a pretty damn cool codebase here, with good comments. When we get CVS, we'll want to be able to integrate some of the best stuff sooner rather than later.
Easiest and least pain free way of doing THAT, is to make it well documented. For both the best practice approach and general continuity of the codebase, but also so that whoever is in charge of "approving" the code for inclusion into the over all code base can EASILY see what you have been doing.