On Sun, Jun 2, 2019 at 12:44 PM Dashamir Hoxha <dashoho...@gmail.com> wrote:
> > > On Sun, Jun 2, 2019 at 12:12 PM Ralf Gommers <ralf.gomm...@gmail.com> > wrote: > >> >>>> Would it be useful if we could integrate the documentation system with >>>> a discussion forum (like Discourse.org)? Each function can be linked to its >>>> own discussion topic, where users and developers can discuss about the >>>> function, upvote or downvote it etc. This kind of discussion seems to be a >>>> bit more structured than a mailing list discussion. >>>> >>> >>> A more modern forum is nice indeed. It is not strictly better than >>> mailing lists though. So what I would like is a Discourse like interface on >>> top of the mailing list, so we get the features you're talking about >>> without a painful migration and breaking all links to threads in the >>> archives. Mailman 3 does provide this (example: >>> https://lists.fedoraproject.org/archives/list/de...@lists.fedoraproject.org/). >>> I'm keeping an eye on what's going on with Mailman 3 migration of the >>> python.org provided infrastructure. I think we can do this in the near >>> to medium future. I don't want us to be the guinea pig though:) >>> >> >> To save anyone else the trouble of posting this link, here's Guido's >> thumbs down on Discourse (and he's not the only one) as a replacement for >> Python mailing lists: >> https://discuss.python.org/t/disappointed-and-overwhelmed-by-discourse/982. >> Tastes vary:) >> > > I did not suggest replacing the mailing lists with Discourse. > > I suggested integrating documentation with Discourse, so that for each > function there is a separate discussion topic for this function. For each > function on the documentation page there can be a "Feedback" or "Comment" > link that goes to the corresponding discussion topic for that function. > This way Discourse can be used like a commenting system (similar to > Disqus). In the discussion page of the function people can upvote the > function (using the "like" feature of Discourse) and can also explain why > they think it is important. > Oh okay, I misunderstood you. I don't think that's desirable; it's too complicated and has too much overhead in setting up and maintaining. Between looking at libraries like Dask and Xtensor, tooling to measure actual API usage ( https://labs.quansight.org/blog/2019/05/python-package-function-usage/), and just using our own knowledge, we have enough information to make choices. Ralf
_______________________________________________ NumPy-Discussion mailing list NumPy-Discussion@python.org https://mail.python.org/mailman/listinfo/numpy-discussion
