Dennis Hayes wrote: > Mono uses the vote with code concept. You want it to work one way, you > write code that way. He with the most and best code wins. Typically > there is only one "vote". > Given the small sioze of the overall group, and the very small group > who actually write code, I don't see governance or conflict resolution > as being worth all the time being devoted to it at this point. > Dennis > I cannot agree with this sentiment. There is a lot more to a project, especially such as this one, than code contribution. Further, given multiple conflicting implementations of a piece of code, you'll still end up with the very real possibility of an emotionally-charged stalemate.
Ultimately, it'd be great if the core directors of the project agreed to something informally. That's the best hope for any decision. But when things get heated and a debate gets mired up in itself, there must be some previously agreed-up way that the project members can lay down a hammer and make a final decision, in order to move things along. And that process must have been previously agreed to, otherwise the other parties involved will end up crying foul, attempting to claim bias or other personal prejudice. --S ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ SharpOS-Developers mailing list SharpOS-Developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sharpos-developers
