Yes I agree with Alexis.. The way I see it: Rule 1: do not break tests. Only case is if you break it because of external stuff (build process, stuff like that). In this case it's allowed but should be fixed. Rule 2: ask for forgivness better than permission. It's good to inform and ask for other people's opinion because it educates the group about the development process and the code itself. Now it should not slow us down too much. We are not at a size where 3 votes is absolutely necessary. Of course I have the most experience with the code base, so there is a good chance other people won't yet see problems that could occur because of certain changes. But generally speaking I trust the judgement of the fine people in the group. If they would like something change I guess there are good reasons and it is a progress, so unless I see a big problem I'm ok with it. So I would say.. let's vote when we feel it is necessary to vote.. let's not make this mandatory. When you ask for opinions, if nobody screams, let's go ahead. Ludovic Alexis KARTMANN a écrit :
Hi Vincent, Most of us are new members, that I think the reason why we all wait for Ludovic advices and follow his decision. If we still want to follow eXtreme programming principles as Ludovic wanted in the beginning of the project, according to collective code ownership principle you should be able to commit your change as soon as they don't break existing tests and that you pair programmed them. As pair programming is not possible, and because we are too few to wait for 3 yes vote, I think that 1 or 2 vote should be enough.
-- Ludovic Dubost XPertNet: http://www.xpertnet.fr/ Blog: http://www.ludovic.org/blog/ XWiki: http://www.xwiki.com Skype: ldubost AIM: nvludo Yahoo: ludovic