I'm hesitant to start yet another communication channel without considering all the maintenance work that it entails. It's not just about "let's spin up the server" but we should think about who will moderate and administer it. Since we have tried various platforms in the past, and some just didn't work for whatever reason, it would be good to analyze and find out why we didn't like them, and how to ensure that the next platform will not end up the same fate. I hope we can properly evaluate how the next chosen chatting platform can be used more effectively.
On Fri, May 14, 2021 at 11:07 AM Brett Cannon <br...@python.org> wrote: > > > On Fri, May 14, 2021 at 6:48 AM Senthil Kumaran <sent...@python.org> > wrote: > >> On Fri, May 14, 2021 at 09:36:52AM +0200, Antoine Pitrou wrote: >> > #python-dev on IRC has been wildly successful until perhaps 2015. >> > Personally, I would have no problem using IRC if wanted to connect to a >> chat >> > for CPython at all. >> >> I know, it was useful, and #python is still. The bot, github, buildbot >> made it more alerts only. Looks like Victor and few others still use it. >> >> >> > Similarly, I would have no problem using Zulip. I would even say that >> Zulip >> > is by far the best chat system I've ever used, and the alternatives >> don't >> > come near. Its threading system is really superior to everything else. >> >> With Zulip, I find it hard to understand, why I need two namespaces (for >> lack of better term) before I start writing my text in Zulip chat. >> >> #topic->subtopic [content] >> >> I have not been a part of the community that uses Zulip effectively, so >> I haven't learnt it well. >> >> > The idea that if people don't use IRC and Zulip, then we should try >> another >> > chat system, sounds like magical thought. What kind of properties do >> Slack, >> > Gitter or Discord have that Zulip doesn't? They are actually quite >> annoying >> > in my experience. >> >> Some have community advantage. K8s, Golang people are on Slack. Multiple >> Companies are on Slack, technical barrier is very low. Similar is the >> case with Discord. >> > > Yeah, I don't know if the Python community as a whole has totally settled > on a platform. > > >> >> Community usage, and usability _perhaps_ go hand in hand. General numbers >> could support for this. >> >> That said. If we (a quorum) feel comfortable using anything like IRC, >> Zulip, I agree, we don't need another one. >> > > You could launch a poll on discuss.python.org and see if there's a clear > winner. > > -Brett > > >> >> -- >> Senthil >> _______________________________________________ >> python-committers mailing list -- python-committers@python.org >> To unsubscribe send an email to python-committers-le...@python.org >> https://mail.python.org/mailman3/lists/python-committers.python.org/ >> Message archived at >> https://mail.python.org/archives/list/python-committers@python.org/message/LYK567UL32MQS7IBRFADWM5WIN3AY57Q/ >> Code of Conduct: https://www.python.org/psf/codeofconduct/ >> > _______________________________________________ > python-committers mailing list -- python-committers@python.org > To unsubscribe send an email to python-committers-le...@python.org > https://mail.python.org/mailman3/lists/python-committers.python.org/ > Message archived at > https://mail.python.org/archives/list/python-committers@python.org/message/CG4MJEDHXTKT76DY5UARV4SSFZYX7VQ7/ > Code of Conduct: https://www.python.org/psf/codeofconduct/ >
_______________________________________________ python-committers mailing list -- python-committers@python.org To unsubscribe send an email to python-committers-le...@python.org https://mail.python.org/mailman3/lists/python-committers.python.org/ Message archived at https://mail.python.org/archives/list/python-committers@python.org/message/FXIVKJ7JXGHFW7KWZTPIJHSDKJ25AYBR/ Code of Conduct: https://www.python.org/psf/codeofconduct/
