Mr. Newkirk, if you're listening, here are my suggestions:
- Support automation. GDN currently has no good ways to automatically check in/out. As an NUnit guy, I can imagine this is high on your list. :)
- Switch to a edit/merge/commit source control model. The SourceSafe lock/edit/checkin model has no place on teams where people sit more than three feet from each other. I'm pretty sure I know what you're using on the back end for source control, and it's awesome. Expose it.
- If you absolutely must support lock/edit/checkin (to pander to all those frightened by the word “merge“), for the love of all that is technical, make it something I can turn off.
That would be an excellent start. If you can additionally
- Provide an interface for automating releases.
- Provide built-in continuous integration with excellent integration points.
- Provide well-integrated bug and feature tracking.
Then you'll be a leg up on SourceForge, and I might consider switching.
One piece of advice: avoid the Microsoft trap of thinking you have to write the whole thing from scratch. That's one of the reasons GDN sucks now. There are tons of good bits out there that already do a lot of what we need (e.g. CruiseControl.NET). Note: I will be highly suprised if this actually happens. Microsoft culture is pretty bad on this count - I think you get sprayed with NIH spores when you walk through the door.
In any event, I wish you the best of luck. The worst-case scenario for me here is that SourceForge steals some of your ideas and makes my experience even better. So I win either way. :)