-
-
Notifications
You must be signed in to change notification settings - Fork 23
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
How to submit documents relating to a PEP for consideration by the SC? #41
Comments
You can always send a link to any documentation to |
I would like to note that everyone sending us personal notes also doesn't scale for the SC. If there are duplicate concerns that are sent in privately then we duplicated what we have to sift through. Plus we then have to potentially care out multiple, separate conversations. This isn't to say that people can't or shouldn't contact us privately, but I don't think it should be the primary way people typically discuss PEPs with us. And if you suffered personal abuse, Mark, then please report it to the Conduct WG so it can be handled appropriately. |
Closing as the SC agrees with the response Barry and I left. |
Just to clarify, sending an email to |
@markshannon yep |
Currently there is no way to submit comments or documentation relating to a particular PEP to the SC for consideration.
Posting to python-dev can easily degenerate into a shouting matching or worse.
I was subjected to personal abuse when making a purely technical objection to PEP 526.
Discussion relating to PEP 622 and PEP 634 is much better, but can still be quite wearing.
It also seems unreasonable to expect the SC to review in detail every email sent to python-dev, but a superficial analysis merely encourages more shouting, as 10 "me too" emails will drown any attempt as reasoned debate or formal analysis.
What is the best way to submit documents?
The text was updated successfully, but these errors were encountered: