Howto engage Python contributors in the long term?


(Terry Jan Reedy) #61

Help review issues and PRs.


(Jeroen Demeyer) #62

But non-core developers cannot make any decisions. Even if a non-core developer reviews something, it still requires an additional review by a core developer. So the review by the non-core developers feels pointless.

I would certainly feel much more motivated to review if I knew that my review would count for something.


(Guido van Rossum) #63

Make no mistake – reviews from outsiders are very valuable! These can take many forms, e.g. suggesting improvements, pointing out subtle bugs, flagging style issues, requesting additional docs or tests to be written, discussing the right API, debugging test failures, and more.

What’s not valuable is reviews from outsiders that simply say “LGTM”. At the very least you should say how thoroughly you have reviewed the code and what things you looked for (e.g. items from the above list).

If you simply want to express your desire to have the proposed feature or bugfix, use GitHub’s emoji support and add a heart or thumbs-up to the issue.


Github: "awaiting core review" even if changes requested
#64

I have started this PR in devguide:


(Brett Cannon) split this topic #65

3 posts were split to a new topic: Growing the Python user base