Point to Discourse instead of mailing lists as the nominal core dev discussion venue #945
Conversation
332d604 to
ee35ee7
Compare
|
Thanks! I added this to the SC agenda. |
developer-workflow/lang-changes.rst
Outdated
| small percentage of Python developers then the change will not be made. A good | ||
| way to see if your idea would work for a large portion of the Python community | ||
| is to ask on :ref:`python-list or python-ideas <communication>`. You can also | ||
| is to ask in the `Ideas category`_ on the `Python Discourse`_. You can also |
There was a problem hiding this comment.
This sounds a bit weird to me -- why not just saying the `Ideas category on Discourse`_.?
The second link doesn't seem particularly useful, and it's probably better avoiding two links side by side.
The same applies to several other instances below.
There was a problem hiding this comment.
Besides re-using existing link targets and being consistent between usages (which are not very convincing reasons), IIRC the main reason for this was to link the internal ref to the section explaining Discourse, but in the end I didn't end up doing that in most cases. In any case, I've revised the various instances to follow the form you suggest here.
726417e to
23a17be
Compare
|
The switch was announced, so I'll merge. |
As a followup to #938 , updates a number of additional references to and discussions of the mailing lists to prefer Discourse instead. In the process, as it particularly updated sections related to the PEP process, it elided a substantial amount of out of date material that duplicated both PEP 1 and between devguide documents describing mailing list/Discourse posting around such, focusing on the material unique/specific to each section while referring the rest to either the communication channels doc or the canonical source, PEP 1.
As part of this, this also clarifies, updates and improves existing references to Discourse, and revised its existing "Getting Help" section to avoid duplicating a fair amount of the material in the communication channels doc and focus on, well, "getting help" as the title would suggest.
Fix #944