Hi, > Usually one committer is enough, the only different is that, if the patch > is proposed by a committer, then you need another committer to approve it. > We need to make sure that a patch has to be reviewed by a committer other > than the author.
This depends on the projects, some don’t have reviews and the committer can commit straight to master. It’s going to vary project by project. > But other committers have the rights to revert the > patch/PR This is referred to a a veto and all projects allow this that I’m aware of. They are however very rare or non-existent, as changes are usually discussed and agree on before hand. They must have a valid technical reason or they are invalid. >> Once all questions get the resonable answer, we can make a vote. >> If anyone has a new idea(e.g. submodule, dev/pr/release branch, >> backport, LTS) send your proprosal to dev list and let community >> discuss and vote. I would try to reduce the amount of voting for things like this, just discuss and reach consensus rather than voting. Voting can make winners and looser and split communities. Thanks, Justin
