Hello Rob, > Not true, only PMC votes are considered legally binding from an ASF > standpoint but the wider community is always welcome (and should be > encouraged) to review and vote on a release.
That is good to know. I sometimes feel like we lost the energy of our "contributors" when we went TinkerPop went Apache. TinkerPop Contributors was 20+ individuals from various companies and vendor products. Its good to hear that doing the "side votes/recommendations" is considered a good thing. Without the vendors saying "this release works for our product," the VOTE of a PMC really doesn't matter in my opinion. > However please remember that Apache projects are supposed to be vendor > neutral and vendor votes should not be treated any differently from votes > by any other community member. People who work at vendors on products > that use Tinkerpop are always welcome to vote as individual members of the > community, the fact that they happen to work at vendors should not give > their votes any special significance I understand that philosophy and I like it. I love how its all about the individual at Apache. With that said, we do work closely with individuals at vendor companies and their yay or nay is crucial given how much more they are testing a TinkerPop release than, lets say, someone who is excited for feature X in the next release. I guess the distinction is not "vendor vs. consumer" but more "heavily tested vs. excited for a release." > > The general practise that I've seen used in other Apache projects is > simply to report the total number of votes and state how many where > binding in each category. So for your result you might have instead > reported like so: > > +1 - 7 (4 binding) > 0 - 0 > -1 - 0 What does "binding" mean? Isn't every VOTE binding? Thank you for your time Rob, Marko. http://markorodriguez.com
