-----Original Message----- From: Ludovic Dubost [mailto:[email protected]] Sent: mercredi 1 juin 2005 22:23 To: [email protected] Subject: Re: [xwiki-dev] [Process] Decision management
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.
Ok, my email wasn't clear. What you have said is exactly the way it happens at Apache for example. My question was to clarify the "if nobody screams". For example, I can send an email, wait 1 minute and then commit. Nobody has screamed. Then someone says, "hey hold on, I don't agree with this". Taking it back can take time, etc. But ok, I hear you. At this point you don't care too much. I'll continue doing what I've done so far by publishing my intent, wait a few hours and do it. Thanks -Vincent _____________________________________________________________________________ D�couvrez le nouveau Yahoo! Mail : 1 Go d'espace de stockage pour vos mails, photos et vid�os ! Cr�ez votre Yahoo! Mail sur http://fr.mail.yahoo.com