[SciPy-Dev] Unpacking the mailing list: Discourse, Slack = Mailing list

[Ilhan Polat]

Discourse and emails have the same issue for me that I can't track who said
what to whom; for example
https://discuss.python.org/t/pep-632-deprecate-distutils-module/5134/4 I
spent way too much time following who replied to Matti and then who reacted
back etc. (discourse has this weird habit showing the reply both in reply
window and in the flow later in the page but maybe that's on me) but moving
away from email seems the right thing for me.

Especially when a discussion doesn't converge to a point it is just a
useless pile of text that promotes misunderstanding as can be seen from
many discussion in many places (linux kernel being the notorious) and
starts to have those >>>>>>>>>>> trains. I don't mind the next tech though
I share the same concern for Slack as mentioned. I still think that github
discussions would help a lot in not-so-strategic decisions as I'm seeing it
used within the GitHub beta repos.

Obvious disclosure, this is my personal view on it for what its worth. I
get that there is still a huge dependence on email on different sectors and
academia apparently.






On Fri, May 21, 2021 at 4:57 PM Nicholas McKibben <nicholas.bgp at gmail.com>
wrote:

> > I'm also on the email wagon, but it looks like discourse can import a
> mailing list archive, and if it can be configured to send a email, it may
> be considered as a modern view on a mailing list. I'm 100% fine with that.
>
> +1 what Serge said, maintaining the existing email workflow would reduce
> the barrier of entry for me.
>
> On Thu, May 20, 2021 at 1:16 PM Stefan van der Walt <stefanv at berkeley.edu>
> wrote:
>
>> On Thu, May 20, 2021, at 12:10, Tyler Reddy wrote:
>>
>> - Why don't you just add a read-only mirror for the SciPy mailing list if
>> you really want to use discourse (or whatever) and then add separate
>> channels for the other discussions you want? (looks possible:
>> https://meta.discourse.org/t/creating-a-read-only-mailing-list-mirror/77990
>> )
>>
>>
>> I think that's the way to do it, yes.
>>
>> Stéfan
>>
>> _______________________________________________
>> SciPy-Dev mailing list
>> SciPy-Dev at python.org
>> https://mail.python.org/mailman/listinfo/scipy-dev
>>
> _______________________________________________
> SciPy-Dev mailing list
> SciPy-Dev at python.org
> https://mail.python.org/mailman/listinfo/scipy-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mail.python.org/pipermail/scipy-dev/attachments/20210521/b89ba917/attachment.html>