> Simplistic standards like "> 51% of the ACTIVE committership from a > different company" might work for making simplistic decisions. They are > not appropriate for a decision to accept a new project into Apache, which > should be based on the quality of the proposed code and the proposed > initial committers, not on the email addresses of the proposed initial > committers. >
Maybe thatıs not a candidate for policy however it is required for MY vote. If your boss came and said "Craig, if you don't vote X then you're fired" and said this to a number of committers... While some might quit or whatever, I suspect the vote would be decided supposing they dominate the project. Furthermore, the interests of a set of employees of a company using a project for a particular purpose will tend to have homogenous interests. Thus will *tend* to vote similarly (if not the same way). It is my experience that developers who counter their employers interest do not stay employed for long. Lastly, developers who work together at work tend to communicate directly versus on community resources more frequently. In a NEW project it is my opinion that diversity should be settled up front so that no one company controls any new project. This is MY criteria for certain and required for my vote -- perhaps its not yours. -Andy > Craig McClanahan > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > -- Andrew C. Oliver http://www.superlinksoftware.com/poi.jsp Custom enhancements and Commercial Implementation for Jakarta POI http://jakarta.apache.org/poi For Java and Excel, Got POI? --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
