> Once a decision had been made, the change would have been explained, and if necessary > opinions would have been asked. > Shouldn't it be the other way around? Shouldn't opinions be asked and considered > before the change gets implemented?
asked to who? what I was suggesting was that the team should try to get to an agreement about a "proposal for change" first
, then the larger base of contributors should be involved: if you can't have agreement among 100 people, you'll never have agreement among thousands...
and I stress about the "proposal" part. no matter how much Haze likes to complain, the discussion has not really been about forcing a new license against other devs' will