Mike Taylor wrote:
I have to agree with Philippe here - #3 seems like the best of the 3, and I think #1 simply isn't an option because otherwise the owner could just always reject the reviewer's opinions.1. Owner's opinion prevails 2. Reviewer's opinion prevails3. It's put to a vote before an impartial body - most of the time that body will be the dev list4. <insert alternative solution here>
I think it really comes down to basic decision making, and that seems like a good use of dev. I don't even think it always has to be a formal vote, just more of a discussion.. I mean if two people disagree seriously on any decision in chandler, its going to have to be hashed out either between those people or (preferably) in the public realm to set a precedent for future decisions on similar topics.
Alec
thanks, --- Bear Build and Release Engineer Open Source Applications Foundation (OSAF) [EMAIL PROTECTED] http://www.osafoundation.org [EMAIL PROTECTED] http://code-bear.com PGP Fingerprint = 9996 719F 973D B11B E111 D770 9331 E822 40B3 CD29 ------------------------------------------------------------------------ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ Open Source Applications Foundation "Dev" mailing list http://lists.osafoundation.org/mailman/listinfo/dev
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ Open Source Applications Foundation "Dev" mailing list http://lists.osafoundation.org/mailman/listinfo/dev
