mxnet-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Henri Yandell <>
Subject Re: Integrating a forum with the mailing lists for better usability
Date Sat, 16 Sep 2017 04:23:00 GMT
I'd like to see the user@ list setup first; currently we don't have this
medium that you say we're losing engagement on.

Typically the Apache approach to forums has been to use Nabble ( for
example ); which
iirc is a forum interface to the user list.

I think you can also sign in (via Google, or Apache if a committer) to for the same 'wrap the list' experience.

It looks like this came up historically: +

I also wonder how forums and stackoverflow compare. They seem to hit the
same topic, so is in
essence the forum?

I'll ask on general@incubator as to whether there has been discussion in
recent years on projects running forums, and whether the direction was to
self-host at Apache or use a third party (which means someday you will be
dealing with having to migrate off of that third party).


On Thu, Sep 14, 2017 at 11:17 PM, Seb Kiureghian <> wrote:

> Hi dev@,
> I am glad to see more open discussion on the dev@ and user@ mailing
> lists. However, I also want to make sure that our website visitors can
> view, ask, or respond to questions from the community, in a user-friendly
> manner. I suspect that by relying only on mailing lists, we are losing
> engagement from users who don't like email and prefer other mediums, such
> as a Discourse forum <>. Other open source
> projects that have seen a recent sharp rise in popularity provide forums
> that see a ton of engagement, and provide user-friendly search and
> personalization tools that benefit users.
> Henri, John and community - what are your thoughts on setting up a forum
> on the Apache MXNet site and integrating it with the mailing lists, so that
> every forum post triggers an email and vice versa? Everything gets
> documented as usual, but we boost engagement and reach of our content.
> Seb

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message