1. Switch to SVN to git.
The biggest question is, given the size of our team, would we get enough benefit to make it worth the time and effort to convert ?
With our current approach each dev/prospect/contributor essentially takes an informal branch to build their local environment then the changes are merged back in manually by the reviewing dev. I'm not sure how formal branching would change things and my experiences with anything other than manual merges have been disastrous.
One final consideration, admittedly minor : we get a lot more project starts than completions. If we did a formal branch for each project we'd have a great many dead branches. I guess that's not really an issue for any source control system. It just feels untidy to me.
2. Separate repositories for client / server applications, libraries (like Cal3D), game content (restricted?), website, related projects (dev tools, default skins, etc.) - the smaller, the better.
Considering the high degree of sharing betweent the client, server and npcserver...how would we accomplish this without creating more work for ourselves?
Something I neglected to mention in my last post is that we do have seperate repositories for art, content, GM console, dev console, and other assets that are not open.
As for the libraries we depend on I think I addressed that in last post, but yes, what eonwind said:
Remember we're a little team and there's no way we can maintain forks of CS, we have PS devs with commit accesses in the CS repository and that's all we need right now.
3. Issue tracker, integrated with code repositories.
This would be very nice. I have begun referring to the flyspray issue number associated with the bug in commit notes. It's a poor substitute. Do you know of anything that integrates with SVN ? Better yet, would you be interested in investigating the possibility of tying our current bug track to our current sourc control system?
4. Unit tests, at least for some code parts.
This could be very helpful in detecting and preventing new bugs as well as driving stability into the code base. It is also an area in which I am very weak. If you would like to help us implement this, please, please, please apply as a prospect. I will be overjoyed to enable your work on it.
5. Automatic build system for main development platforms (simplifies testing).
(addressed in my last post)
So of the 5 issues: agree and already moving on 1, agree and open to help on 2 others, lack resources and recognition of benefits on the final 2. Hey, we agree on 3/5, that's a winning score!
It's not as good as the first writeup I did (and lost) but I think that's a pretty thorough basis for further conversation. Thoughts?