Please figure on list.
You're such a control freak.
You can have some faith in me. Things propresses so much faster that way. If you trust me to do the right thing, and that I'll correct any mistakes I make, life is simpler and progress faster.
I understand that this requires a leap of faith, but hey, I trust you to make good decisions on your own in your area, and I believe I'm capable of doing the same in mine. I have a good understanding of the common needs for the project, and everytime I'm in a grey area, I will figure on the list.
But some decisions are uncontroversial. That's why they have an obvious rule in gcc.
May I propose the following code of operation:
- Red decisions: Those decisions should be discussed in advance on the list, and nothing committed before it has been reviewed. This includes things like adding a Lout backend, or changing to an XML format.
- Yellow decisions: Decisions you can make on your own, but you can develop on your own, as long as the result is reviewed on the list before committed. These are changes that might break other platforms or features, or have some other risk element in them.
- Green decisions: Decisions you can make on your own and commit on your own, without prior review. Use the commit message to explain what is going on. These are for things, which are local in nature (i.e. low risk), and where the person doing the work has shown to be responsible and capable of handling that. If you make a mistake, and one of your commits was in fact yellow, you loose street credit, and depending on the severity, you have to prove that you understand what is what, you loose your green card.
For all things, you have a responsibility to make a best effort to correct any mistakes you make.
Sometimes, it will not be clear what color a decision is. In that case, it's best to be precautious, but on the other hand, it is clear that progress will be faster the more is judged green.
Regards. Asger
