1
edit
Changes
m
→Created New Committing Discussion
= Open Discussions =
Current open discussions
== Committing Practices ==
When many people work together on the same project, ideally only a couple of them are responsible for committing the code. Although our team has only 8 members, it is probably a good idea to give the committing responsibility to only one or two members at once. Fardad has suggested that we rotate this responsibility, and I think we should try that. To make it possible, I have thought of a way to make it work.
* Each week two of us are responsible for committing. The order we alternate this role could be random, or we could go down the team member list as we did for dividing the simple functions among us.
* Join our IRC room before committing. Even with svn's merging capabilities, it is easier if two people can talk to each other if they happen to be committing at the same time.
* If you finished something in your branch that is worth committing but it's not your turn to commit yet, create a discussion on this page with your name and the files you worked on. That way we can all check your work on your branch and comment possible changes here. Once everyone has looked at it, one of the committers can finish the job.
* Always document your commits, so we have some control in case something goes wrong.
Please add you comments to this suggestion.
= Old Discussions =
