Hi, If someone submits what you think is poor quality code just point it out to them and ask them to fix it or even better fix it yourself to show them what is expected. Vetoing something list that seems a little heavy handed and is not the best way to encourage community growth. It’s better to improve the quality of others contributions rather than blocking them from contributing. Vetos in practice are very rare, how many have actually occurred in this project? Wouldn't it be better to focus on practical ways to get people involved and increase contribution rather than hypothetical situations of when to veto a code change?
Thanks, Justin
