Hi Sean,

Would be glad to collaborate.  Doing some process work now for a small development team.

We are using GITHub but theres nothing specific in the process to GitHub.

So far I have tackled:

Brand New Database - putting it under source control, creating the remote repo, doing multiple commits, creating readme.textile documents (that might be GIT specific) and pushing to the remote rep.  We are using the readme as the control to indicate if the application is currently under development.  I know theoretically that doesn't matter.

Existing Database not currently under source control - this is probably the most common initially.  I covered the things above but also creating a Master Baseline version then creating a DEV or BUG branch, working on those branches and then merging them back to the master once changes are live and tested.  Other things came up = if you create the new branch you should push immediately to the remote - this way theres an indicator that a team member is working on a new branch.  Also commit messages - the visual whats changed view doesn't really work for Design elements so the commit messages should include descriptions.

Existing Database under source control - similar to the above but in this case no Master baseline required - instead straight into a new branch, slight change here is the local working version for this developer would be in the own working folder on the Dev server.  Rather than having 1 development version on the box, theres now a working version per developer.

Still a newbie when it comes to source control - I haven't looked at Patches, rebasing, roll backs etc, I intend to ;-)

Theres also gotchas around DDE - for instance if your using working sets then the on disk version doesn't get added and the default view doesn't allow you to add it - switching to the properties view does.

Trying to work on some interesting diagrams.

Mark