Contributors are free to contribute in any way they can/see fit and I wouldn't impose any constraint to that.
What is being discussed is what a contributor can do to eventually be invited as committer. For the latter, I agree that filing quality tickets, participating in design discussions in the ML/Jira, and provide meaningful reviews to others are fair requirements on top of code contributions, this could be clearly marked in the page you mention. Best regards, Alessandro On Tue, Jun 23, 2026, 20:50 Mihai Budiu <[email protected]> wrote: > So perhaps we can raise the bar for committer invitations a little by > requiring new contributors not only to file issues, but to participate in > code review as well? > > Or is this too high a bar to expect for newcomers? > > If we decide to do so, we should probably say it explicitly in the > "contributing" section. > > Mihai > > ________________________________ > From: Yu Xu <[email protected]> > Sent: Tuesday, June 23, 2026 1:44 AM > To: [email protected] <[email protected]> > Subject: Re: promoting committers > > Hello everyone, I personally think everyone's points are very nice! > > In my opinion, Calcite is actually quite difficult for beginners to learn > because it requires a high level of abstract thinking. However, once > mastered, it allows for better utilization of one's imagination (this > imagination can manifest in many ways, such as the ability to identify > problems and propose effective features), which is especially crucial in > the AI era. > > I'd like to share my perspective based on my own experience: > > 1. Integrating into the community's style and management, and respecting > the project's history and habits, is a prerequisite for becoming a > committer, such as managing and standardizing Jira and discussion sessions; > > 2. Being able to close the task loop, such as proposing Jira from a > reasonable perspective, and then confirming the solution and merging the PR > through reasonable and standardized discussions. I believe it's difficult > to propose and solve reasonable Jira if you're not familiar with Calcite; > > 3. Helping others, through various forms of code review, and even coaching > users, is very helpful. Helping Calcite be implemented in more scenarios > should also be considered a plus for committers. > > These are some of my views since participating in open source > contributions. In short, it's about doing as much as possible to positively > advance the project. > > Best regards! > > Yu Xu > > On 2026/06/18 16:57:27 Mihai Budiu wrote: > > Hello all, > > > > Today we invite a developer to become a committer after they make > several useful non-trivial contributions to the project. But these days, > using agents, the barrier of entry for contributing to a project has been > lowered substantially, and one can write useful code without a real > understanding of the structure of a project. This is not a Calcite issue, I > expect all open-source projects have to grapple with this. Does our > committer selection process need adjustment? If so, how? > > > > Mihai > > >
