Re: Switching to Discourse

Barry Warsaw <[email protected]> Fri, 15 Jul 2022 10:59:14 -0700
Newsgroups gmane.comp.python.devel
Message-ID <[email protected]>
This might seem odd coming from me, but I’ve come around to supporting this move.  Discourse is not without its issues, but then again, the same can be said about email.  Without going into too much of my own personal preferences, I agree that the experiment has proven successful enough that there’s more value at this point in consolidating discussions.

Thank you for reaching out to see if there are any usability or workflow issues that might impact this decision.  There aren’t too much for me, but I wonder if there are accessibility or native language concerns that might unduly affect other users.

One thing I didn’t see mentioned is the question of identity.  There’s one side which is how folks self identify themselves on the mailing list or forum.  We don’t have any prohibitions against alias or nicknames, which IMHO is totally fine.  The flip side is more important, ensuring that folks identities can’t be spoofed or hijacked.  In email at least, I can digitally sign my messages (such as this one), and while it’s probably true that fewer and fewer folks use any kind of email digital signature verification, at least *I* can prove whether or not I wrote something.  What similar kinds of protections do we have on Discourse?

-Barry

> On Jul 15, 2022, at 04:18, Petr Viktorin <[email protected]> wrote:
> 
> The discuss.python.org experiment has been going on for quite a while, and while the platform is not without its issues, we consider it a success. The Core Development category is busier than python-dev. According to staff, discuss.python.org is much easier to moderate.. If you're following python-dev but not discuss.python.org, you're missing out.
> 
> The Steering Council would like to switch from python-dev to discuss.python.org.
> Practically, this means:
> - Moving the required PEP announcements to discuss.python.org
> - Moving discuss.python.org up in the devguide communications page (https://devguide.python.org/communication/)
> - And that's it?
signature.asc (application/pgp-signature, 833 B)
-----BEGIN PGP SIGNATURE-----

iQIzBAEBCAAdFiEEhBcVftvnPZ6sHlObEm61Y6dLBr8FAmLRqvIACgkQEm61Y6dL
Br/bXxAAgslir09zl56zPKt8jTp9rBan+08kDQxSAK/H1QgXPVRY6dwaN+toT3zl
qBFVGlgrjjG5IG7Q55iLsSCRL/or9ZafJI/vAO28Q6tx7kR23nr8KaQ4qzMINSE0
WD32SLCQarkWla0c8NeGZ6ICjdxYXA8Cfj9OTvpyFnuoJguZlXcOin0DU3yLB45x
cm/DqstNOrAxzEAtqQTtU1P2OSBBcjjznBSYZkcmHQ7pWPorgoc/gwWLEe+NqfmT
nC6be1oNY1C0AV8Uk+jlpnKVOlAFOEqNtEXlbs//jnJ189bDQGouwBITd3K5W4Z7
oMIe7odpF83QG6zUZtLJM3T+gRD8Xl+q8BgY2hqzFH1eOLXQKuJVCfvDwd0CFZvo
hn++uOcj6FIKNCrrvflVq3VmfD5xGsnc+hgUzg/Q/UTzxFM95o0oBKgeAvn+UF53
fArurv4Q0pfhzTVHWSzQAZIi9FIoMnBdqeQulgtbL7z7JUGU0yihIhT+K9rHOf2q
eTp6rgdifmxWoE9Mgd3vrdpQ8RGSKdbAJGAmppnD6TbteCwIICjKisK303Mae9+P
17/LOA2k5/YLGuGG/8FF0NwNPDehZ4iyj3QrJt7HCdlijZca0ejX9Qh7rURNDOC7
SCR5Vxg9xhSbgQJ6Je7w7KZqykJpogbe0zYwRrhbxPNyINekRkI=
=9tcA
-----END PGP SIGNATURE-----