LinkBack URL
About LinkBacks
Re: Subversion Repository David,
Your offer is most welcome. I think we will be sticking with google code for our repository, as that lowers the overhead of the operation significantly. If I find that it falls short of expectations, we can always set up our own server.
Regarding structure, I want to maintain pretty tight control over branches and merges to the trunk. Since everyone that gets write access to the repository will be trusted to follow rules regarding trunk commits, I don't think that will be too much of an issue.
We do need to start mapping out the development future of osCMax in more detail though.
JPF has taken the lead on code change documentation and has really made great strides in keeping changes consistently documented. I agree, though, we will need some published framework that all developers can reference when working on branches.
Regarding a hook script for our bugtracker, that is the next thing on my list. I checked out SCMBUG, but it is not really an option with google code from what I have read (correct me if I am wrong!). I am definitely interested in your thoughts on how to accomplish this. Let me know your ideas and what you would need to take the lead on this type of project.
Reply With Quote
Bookmarks