Votes are not the issue. Building community and building consensus in that community is the issue.
To specifically answer your questions: It depends on the vote. For project technical issues, project committers are usually the voters. For project management issues, the voters are project management committee (PMC) members. Management issues include naming new committers and PMC members. Apache members are a separate class and they vote for new members and the board. All of this is documented on-line. The copyright owner is the Apache Software Foundation. If you are worried about power politics around your software, Apache is the wrong place to be. If you are interested in building up a community and giving up ownership to that community, Apache might be the right place for your work. But note, the software is not the central thing. The community is. On Wed, May 13, 2015 at 2:24 PM, Stefan Reich < stefan.reich.maker.of....@googlemail.com> wrote: > Hi again! > > I was silent because I am thinking... :) (Also I am making releases of my > software.) > > I am trying to understand Apache. > > It seems the voting processes are of big importance. I would like to know > who exactly gets to vote. All members of a mailing list? If yes, it seems > like an easily manipulatable process... > > Also, who is officially the copyright owner on the Apache products? Because > that is a tremendous power position it seems to me. > > All the best, > Stefan >
