Thanks for raising this topic. I think establishing a basic principle for the Apache Calcite community is necessary. Having multiple reviewers can help contributors double-check their code, which is a good practice. As you mentioned, all of Calcite’s contributors are volunteers, and their time is limited. I believe contributors should be patient throughout the contribution process. I’m not an expert in all areas of Calcite, but I’ll continue learning and try to review more pull requests.
Best regards, Zhen ---- Replied Message ---- | From | Cancai Cai<[email protected]> | | Date | 04/01/2026 21:39 | | To | [email protected] | | Cc | | | Subject | Merge PR principles reminder | I'm not sure if it's appropriate to bring this up, but I feel it's necessary to raise this point. Recently, I've noticed that some pull requests related to Jira issues have been merged without approval from committers and PMCs. Some even only received AI review, without any review from other committers or PMCs. I think this is unreasonable, and I hope this situation can be reduced in the future. Calcite is a project without a commercial company behind it, yet it has still been able to develop healthily for many years, thanks to the efforts of everyone in the community. This also demonstrates that Calcite's community governance policies are sound, and we don't need to break any fundamental principles. Best wishes, Cancai
