This is an automated archive made by the Lemmit Bot.

The original was posted on /r/opensource by /u/TiloRC on 2025-01-29 21:45:09+00:00.

Lately, I’ve been reviewing lots of PR for first-time contributors to SymPy, a Python-based computer algebra system. I think for the most part they’re trying to meet the bug fix requirement for Google Summer of Code and strengthen their GSoC applications.

I’m trying to figure out the best way to give them feedback. In many cases, I could probably fix the bug myself in less time than it takes to guide them through it. When I see code that’s inefficient or difficult to understand, I’m tempted to rewrite it and suggest they use my version. But I know that’s not necessarily the best way to help them learn.

Rightly or wrongly, I’m sometimes left with the impression that they’re somewhat entitled. They @ me quite frequently—immediately after they respond to my comments. If it takes me longer than 24 hours to review their PR, they @ me again. Some of them don’t know very good English, and leave messages that I have to spend a long time deciphering. Often, it feels like they ask for the solution instead of thinking through the problem themselves.

I’m a college student and am very busy. I am helping them because I care about SymPy and find helping people fulfilling — not because I have any obligation to.

That said, I do my best to be encouraging. I know how tough it is to contribute for the first time, so when I merge a PR, I leave messages like “great job” to acknowledge their effort. I try not to assume bad intentions because it’s impossible to know the intentions of each individual. Things that seem obvious to me might not seem obvious to new contributors and those with less Python and programming experience.

I want to make contributing more welcoming and accessible, but I also don’t want to end up doing most of the work for them. How do you handle this kind of situation?