Hi, Julian There is no doubt that you are the most prolific contributors on the project. People often hope to hear professional advice from you because you are the Calcite project authority. However people may didn't realize that you are suffering from more and more requests. I want to sincerely apologize because I often disturb you too. I'm really glad to hear your feelings. At the same time, I want to thank you because I got many professional advices from you. The suggestions are very helpful.
Back to this topic, having an efficient mechanism to merge contributors' PR is very important to the long-term development of open source projects. I would like to share my thoughts, hope it helps. 1. It might helpful to know which members are proficient in which modules. For example, introduce each member's familiar module on the website[1]. There may be many requests sent to other members. 2. For some modules, perhaps only very few members are familiar. (For example, when it comes to modifying the parser grammar, someone may want to hear from Julian, and when it comes to hints, someone may want to hear from Danny.) Maybe it's just my bias. But if this is the real situation, is it possible to develop more than one members on each module? 3. It could be helpful to assign reviewers for a new pull request. [1] https://calcite.apache.org/community/#project-members Best, Jing Zhang Julian Hyde <[email protected]> 于2022年2月4日周五 02:18写道： > I make many contributions to this project, in the form of code, > answering questions, leading design discussions, and clarifying bugs > and feature requests. I review more changes than any other project > member. My reward is that I am pestered, daily, with people pleading > for me to review their changes. > > It's moderately annoying for me - I just delete the emails (because I > have 200 other emails to delete before I can start productive work). > But it's awful for both the contributors and the project. > > Getting PRs reviewed is this project's biggest problem, and has been for > years. > > Many of you are team leads, engineering managers, directors of > engineering. This is a process problem. Solving problems like this is > what you do. Fix it. > > Julian >
