Gregory P. Smith writes: > We feel it too. We've been finding Discourse more useful from a community > moderation and thread management point of view as well as offering markdown > text and code rendering. Ideal for PEP discussions.
The specific mention of "community moderation" and "thread management" makes me suspect that part of that effect is due to increased cost of participation for casual observers. That's not necessarily a bad thing (except for us dilettantes :-), but please make sure that there's some convenient way for affected non-core communities (PyPy, SciPy, Django, random PyPI package owners, and Victor ;-) to stay abreast of proposed changes that (a) may affect them or (b) they may have relevant expertise in the matter they could contribute. Suggestion for PEP monitoring: AIUI the PEP process at a high level view is fairly well monitored by a certain set of GitHub commits: the proto-PEP "PEP-9999" commit, the commit that assigns it a PEP number, and commits that change status. How about a GitHub bot that does nothing but post PEP commit logs to a dedicated Discourse channel? It should be possible to remove typo fixes and the like by posting any that change title, number, or status, and from the rest exclude any commits that change less than a dozen lines or something like that. Or perhaps PEP committers could be asked to include some kind of tag like "#trivial" to distinguish them. Steve _______________________________________________ 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/ICUEAAGSR4EMUTZ7WKX2MAYLLOGIRKBF/ Code of Conduct: http://python.org/psf/codeofconduct/
