When he submitted it, I told him that it would cause this problem, but he didn't care. In other words, nobody had the authority to veto submissions, even when they knew it wouldn't work. At the time, I refused to rewrite my code to get around their bug, and Linus Torvalds, who later found a problem in the egcs C compiler that prevented him from compiling the Linux kernel, announced the same attitude. With the egcs attitude, any project will eventually fail due to an accumulation of bugs that never get fixed. Even Microsoft projects have died from this, and they have historically been able to ram almost anything down their customers' throats.
Every project needs somebody who has the authority to say no and is willing to use it.
Unfortunately, picking the leader can be a problem. When one person initiates a project and does all the development leading up to the beginning of the bazaar, then picking that person as the leader is obvious. Bickering between leaders can easily lead to chaos, and accountability is lost because each can easily blame the other. One possibility, which is used by the developers of the Apache web server, is for each person to have a vote and to simply let the majority win. Unfortunately, this only works as long as everybody is well informed about all the relevant issues and is willing to accept the result of the voting.