> > > If you prefer modlib, please reply with -1. > > > If you recommend libelf, please reply with +1.
Rules for voting are a little different for code changes. The required Apache voting process is here: https://www.apache.org/foundation/voting.html For code changes, that document says: "Votes on code modifications follow consensus approval<https://www.apache.org/foundation/glossary.html#ConsensusApproval>. In this scenario, a negative vote constitutes a veto<https://www.apache.org/foundation/voting.html#Veto>, which the voting group (generally the PMC of a project) cannot override. Again, this model may be modified by a lazy consensus<https://www.apache.org/foundation/voting.html#LazyConsensus> declaration when the request for a vote is raised, but the full-stop nature of a negative vote does not change. Under normal (non-lazy consensus) conditions, the proposal requires three +1 votes and no -1 votes in order to pass; if it fails to garner the requisite amount of support, it doesn't. Then the proposer either withdraws the proposal or modifies the code and resubmits it, or the proposal simply languishes as an open issue until someone gets around to removing it." And "For code-modification votes, +1 votes are in favour of the proposal, but -1 votes are vetos<https://www.apache.org/foundation/voting.html#Veto> and kill the proposal dead until all vetoers withdraw their -1 votes. Unless the proposer declares that the vote is using lazy consensus<https://www.apache.org/foundation/voting.html#LazyConsensus>, three +1 votes are required for a code-modification proposal to pass."
