On 24.02.2020 8:30, Kyle Stanley wrote:
> (What is it with typos anyway? Why do people feel the need to invoke megabytes if not gigabytes of internet traffic to correct a word
that every reader can easily correct in their mind?)
Speaking from personal experience to some degree, my first PR was an incredibly minimal documentation enhancement:
https://github.com/python/cpython/pull/14069. It's not exactly a typo fix, but in retrospect, I'd consider it to be about equally
impactful. I can't speak for everyone, but my own motivation was to do something very mildly helpful just to get a feel for the workflow.
It eventually led to increasingly involved contributions. (:
I think some people might also consider grammatical corrections to be helpful for bolstering the "professionalism" of the documentation a
bit, but it's hard to say for sure.
I can affirm that. Nothing says "amateurish" and "neglectful" like glaring grammatical errors. It shows that the author doesn't care about
their users' convenience and likes to waste their time (the text _can_ be read but it's significantly _harder_ to read and otherwise use),
and that other aspects of the work are likely similarly chaotic.
It's not even uncommon when they make the meaning unclear. Or e.g. typos or inconsistency in a term make it hard to locate other references
to it or deduce if the phrase is being used as a term or as a common phrase.
_______________________________________________
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/DDKRNSHJFQUDB5OU2D5KMARMRLQRXXX5/
Code of Conduct: http://python.org/psf/codeofconduct/
