On Fri, Apr 21, 2023, 10:30 potiuk (via GitHub) <g...@apache.org> wrote:
> > +PMC are binding on the outcome. Other community members may vote as > +well, but those votes are advisory only, and not binding. > + > +A PMC member may veto a technical decision, such as a proposed patch. > > Review Comment: > Comment here. I am not sure how it is in other projects, but we never > thought PMC members have more "voting" or "veto" rights in case of > technical decisions than committers have. At least in our cases PMC members > have no more power to decide if a certain - even big - change in the > direction of the project should happen. The only "binding" decisions that > only PMC members have are release votes, all other votes in our case - > including voting on big "Airflow Improvement Proposals", commiters have > binding votes, and also committers have veto powers for those. > > I wonder if this is normal/expected - in the light of this comment, I > believe it could be up to the project to decide who has the voting powers > and it is also - I think - reflected here > https://www.apache.org/foundation/voting.html > > So maybe worth to mention that thos voting powers can be also - if the > PMC members decide - passed to regular committers? > > Or maybe we are doing it wrongly ? > Not wrong. I'd say your project is being more inclusive than it is strictly required to be. One should of course take the opinions of committers into consideration but only the PMC is the final word on disagreements. >
