-
-
Notifications
You must be signed in to change notification settings - Fork 794
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Document the @proofreaders team #886
Comments
We should probably add a section/page to document the existing teams, their purpose, and the process to join them. This came up in python/core-workflow#458 (comment) too. |
I might also suggest refining the team description a touch, perhaps along the lines of "Mention [...] for help with the finer points of English technical writing," to avoid sounding like its just for people who need basic help with English and to reduce any shame someone might feel asking us for help. Indeed, while some may need it more and others less, almost anyone's writing could potentially benefit from a second look by a proofreader—English technical writing may happen to be an area of strength for me, but I certainly still make plenty of mistakes and typos, and could word things more clearly. |
FTR there is also a section in the devguide about proofreading that should mention the team: https://devguide.python.org/documentation/help-documenting/#proofreading |
Please see PR #1229. |
A question from #1229 (comment):
Good question! Are there any restrictions? I guess some of the people in the team (https://github.com/orgs/python/teams/proofreaders) were added to the org to be able to add them to the team. I don't think future applicants would need to be already in the org, but we should take care in accepting applications. |
At the moment, there aren't any restrictions. (Of course, that might change if people start abusing this somehow.) |
(I don't know who else has privileges to add members to the team.)
@ezio-melotti, would you like to add this?
The text was updated successfully, but these errors were encountered: