HeartSaVioR edited a comment on pull request #28523: URL: https://github.com/apache/spark/pull/28523#issuecomment-635693470
I think the meaning of "binding" should be consistent - committers can give +1 and merge the code change, because they have "binding vote" for "code change". -1 applies exactly the same. If I understand correctly, the major differences between committers and PMC members mainly come from R&R. Excluding the things which occur in private mailing list, only PMC members have binding vote for "release process" (and maybe decisions for the direction of the project, according to the R&R), but not elsewhere. The role denotes what someone can (should) do, rather than saying someone is more powerful than other one. E.g. there's some unfamiliar case which PMC member is not a committer - I don't think they have binding vote for the code change, according to the guide of committer / PMC member. (Not explicitly documented, but it's straightforward if we focus on R&R) https://www.apache.org/dev/new-committers-guide.html https://www.apache.org/dev/pmc.html ---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
