The reason why I mentioned GH discussions is that literally everybody who is engaged with the code, is familiar with the format, included in the codebase product and has replies in built unlike the Discourse (opinion is mine) useless flat discussion design where replies are all over the place just like the mailing list in case you are not using a tree view supporting client. Hence topic hijacking is one of the main usability difficulties of emails.
The goal here is to have a coherent engagement with everyone not just within a small circle, such that there is indeed a discussion happening rather than a few people chiming in. It would be a nice analytics exercise to have how many active users using these lists. I'd say 20-25 max for contribs and team members which is really not much. I know some people are still using IRC and mailing lists but I wouldn't argue that these are the modern media to have proper engaging discussions. "Who said to whom" is the bread and butter of such discussions. And I do think that discourse is exactly the same thing with mailing lists with a slightly better UI while virtually everyone else in the world is doing replies. I would be willing to help with the objections raised since I have been using GH discussions for quite a while now and there are many tools available for administration of the discussions. For example, https://github.blog/changelog/2021-09-14-notification-emails-for-discussions/ is a recent feature. I don't work for GitHub obviously and have nothing to do with them but the reasons I'm willing to hear about. On Fri, Oct 1, 2021 at 3:07 PM Matthew Brett <matthew.br...@gmail.com> wrote: > Hi, > > On Fri, Oct 1, 2021 at 1:57 PM Rohit Goswami <rgosw...@quansight.com> > wrote: > > > > I guess then the approach overall would evolve to something like using > the mailing list to announce discourse posts which need input. Though I > would assume that the web interface essentially makes the mailing list > almost like discourse, even for new users. > > > > The real issue IMO is still the moderation efforts and additional > governance needed for maintaining discourse. > > Yes - that was what I meant. I do see that mailing lists are harder > to moderate, in that once the email has gone out, it is difficult to > revoke. So is the argument just that you *can* moderate on Discourse, > therefore you need to think about it more? Do we have any reason to > think that more moderation will in fact be needed? We've needed very > little so far on the mailing list, as far as I can see. > > Chers, > > Matthew > _______________________________________________ > NumPy-Discussion mailing list -- numpy-discussion@python.org > To unsubscribe send an email to numpy-discussion-le...@python.org > https://mail.python.org/mailman3/lists/numpy-discussion.python.org/ > Member address: ilhanpo...@gmail.com >
_______________________________________________ NumPy-Discussion mailing list -- numpy-discussion@python.org To unsubscribe send an email to numpy-discussion-le...@python.org https://mail.python.org/mailman3/lists/numpy-discussion.python.org/ Member address: arch...@mail-archive.com
