Before we can begin with any unified container concept, we need to come to agreement on how we can agree on design issues. I want to make it clear that no-one has a hidden agenda to steamroll their viewpoints, but we have had problems with vetos thrown around without much thought or backup to them.
The proposal is that any design decisions be done by simple majority of the _committers_. That means that all -1s are counted as a vote, and *not* a veto.
It is the only way I can think of to ensure that we can progress without spending a month deciding whether a method should be called "init" or "initializable". We have problems to solve, not theses to write.
That also means that you cannot bitch and moan if the community doesn't choose your path. There will be no "I told you so's" to be said (if you have one, keep it to yourself).
This proposal is strictly for agreeing how to agree on design decisions, and that it is by majority vote and not veto. In another email, I will outline my thoughts on moving forward.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
