Generally I'm in favor, but I'm kind of missing a bit of structure in the sense of top level topics which then branch off. Right now it looks a pretty loose stream of threads without any structure - the forum does a better job at that imo. Maybe I'm missing something there or maybe we could work with GitHub to get something like that in place.
As an additional platform to try it out I'd generally be in favor, but I think we need a better featureset than a loose list of threads which are not called issues ._. -Marco On Fri, Aug 28, 2020, 21:30 Skalicky, Sam <sska...@amazon.com.invalid> wrote: > +1 for pulling the discussion/questions into closer proximity to the devs > so we can more easily address one of the recent concerns that people asking > questions on discuss aren’t getting responses from devs. > > Sam > > On 8/28/20, 11:41 AM, "Sheng Zha" <zhash...@apache.org> wrote: > > CAUTION: This email originated from outside of the organization. Do > not click links or open attachments unless you can confirm the sender and > know the content is safe. > > > > Dear community, > > I'd like to see what people think in terms of enabling Github > discussions [1] in favor of the detached discuss.mxnet.io. > > The main benefit of Github discussions is that maintainers can easily > move usage questions from Github issues to the discussions forum, and > separate maintenance for the forum will not be necessary. If you'd like to > see what it's like and try it out, you can find its usage online [2] we > also enabled it in GluonNLP [3]. Let me know what you think. > > If the consensus is towards this option, I already signed up for the > beta access for MXNet Github and we just need to request Infra to help > enable this. > > Best, > Sheng > > [1] > https://github.blog/2020-05-06-new-from-satellite-2020-github-codespaces-github-discussions-securing-code-in-private-repositories-and-more/#discussions > [2] https://github.com/vercel/next.js/discussions > [3] https://github.com/dmlc/gluon-nlp/discussions > >
