On 5/12/21 4:10 PM, Terry Reedy wrote:
On 5/12/2021 5:14 PM, Antoine Pitrou wrote:
On Wed, 12 May 2021 17:05:03 -0400
Terry Reedy <tjre...@udel.edu> wrote:
Yet you always see it: new people not knowing where to start,
highly skilled contributors drowning and
intermediate contributors moving slowly
I have multiple times strongly recommended that people review issues and
PRs, and sometimes given details, but most won't or don't.
I don't know who "people" are in your sentence, but reviewing issues
and PRs generally requires a high familiarity with a project, and
Much can be done without what I think you mean by 'high familiarity'.
Bug issues:
bpo: "On macOS with 3.8.3 I see this buggy behavior" If not enough
info to reproduce, ask for it. If there is, try to reproduce on lastest
release or even better, repository build. Sometimes, trying on a
different OS is helpful.
PR: make local PR branch and test whether proposed fix works.
Enhancement issues:
bpo: if proposal is for core python or a module one has used, does
proposal seem like an actual improvement? enough to be worth the likely
bother?
PR: does the PR work as promised? Do you like it?
PR Python code: read it. See any possible improvements?
In addition, starting by working in other's issues and PRs will build a
degree of familiarity with how the Python development works - what sorts
of questions get asked, what changes to a PR tend to get asked for, etc.
_______________________________________________
Python-Dev mailing list -- python-dev@python.org
To unsubscribe send an email to python-dev-le...@python.org
https://mail.python.org/mailman3/lists/python-dev.python.org/
Message archived at
https://mail.python.org/archives/list/python-dev@python.org/message/7TVT56IK54YZOACMD4LYERV3BW23RF7G/
Code of Conduct: http://python.org/psf/codeofconduct/
