Recently, tirkarthi (xtreak) works on finding and fixing typos.
And I (18z) came up with the idea of creating a spellcheck bot to improve
the quality of cpython.
We had discussion in https://github.com/python/cpython/pull/13749
And it is summarized below:
Reducing typo in a constructive way.
To be Solved:
Even after reducing the code checked, there will still be mostly false
High frequency of updating dictionary.txt (false positive typo).
Interfacing the filter with aspell to get some numbers.
The report could be made optional with a spellcheck label.
Code for reducing .py files to strings and comments.
Command line for spellcheck.
There are problems to be solved.
But I think we can always find a better solution.
So, I’ll be working on interfacing the filter with aspell to get some
Looking forward to hearing more opinions. :D
🍝 copy-pasta from core-mentorship mailing list.
There is now a “newcomer friendly” keyword in bpo.
My hope is that going forward, we can tag issues that are suitable for
first time contributors with this keyword.
It would be great for experienced contributors already familiar with our
workflow to not work on issues tagged with newcomer friendly and leave that
to new contributors.
I’ve added the keyword to Devguide’s Triaging section, with additional
guideline of what can be tagged as newcomer friendly. Typically it should
be straightforward, well-defined issue, and low-risk.