Skip to content

Point to Discourse instead of mailing lists as the nominal core dev discussion venue #945

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

Merged
merged 8 commits into from
Sep 20, 2022

Conversation

CAM-Gerlach
Copy link
Member

@CAM-Gerlach CAM-Gerlach commented Aug 31, 2022

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

@CAM-Gerlach CAM-Gerlach force-pushed the update-python-dev-to-discourse branch from 332d604 to ee35ee7 Compare August 31, 2022 03:56
@CAM-Gerlach CAM-Gerlach changed the title Revise PEP sections to reduce duplication, & point to PEP 1 & Discourse Point to Discourse instead of mailing lists as the nominal core dev discussion venue Aug 31, 2022
@encukou
Copy link
Member

encukou commented Sep 1, 2022

Thanks! I added this to the SC agenda.

@@ -23,7 +23,7 @@ Because of the seriousness that language changes carry, any change must be
beneficial to a large proportion of Python users. If the change only benefits a
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
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.

@CAM-Gerlach CAM-Gerlach marked this pull request as draft September 2, 2022 00:14
@CAM-Gerlach CAM-Gerlach self-assigned this Sep 2, 2022
@CAM-Gerlach CAM-Gerlach force-pushed the update-python-dev-to-discourse branch from 726417e to 23a17be Compare September 2, 2022 03:06
@encukou encukou marked this pull request as ready for review September 20, 2022 09:42
@encukou
Copy link
Member

encukou commented Sep 20, 2022

The switch was announced, so I'll merge.

@encukou encukou merged commit a530e82 into python:main Sep 20, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Update main PEP discussion venue from Python-Dev to Discourse
3 participants