mxnet-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Sheng Zha <zhash...@apache.org>
Subject Re: Use Github Discussions?
Date Sat, 29 Aug 2020 23:54:00 GMT
Hi Chai,

Thanks for bringing up the concern. Indeed, over the years the forum built up a good amount
of reference for usage questions that are valuable to the project. Read-only mode sounds like
a good solution and I agree we should at least keep the existing forum running that way.

Best,
Sheng

On 2020/08/29 00:19:01, Chaitanya Bapat <chai.bapat@gmail.com> wrote: 
> +1 for Consolidation of dev experience & bringing Q&A closer to code.
> 
> However, I could think of 1 downside. Hence posting it here:
> 
> Persona: Data Scientist/Model Builder
> MXNet Expertise Level: Novice
> Scenario: Has a question related to cuda malloc in mxnet model he/she is
> building
> Action: Quick search on a search-engine
> Results [currently]
> -
> https://discuss.mxnet.io/t/cudamalloc-and-cpu-memory-allocation-also-failed-on-asnumpy/3551
> - https://github.com/apache/incubator-mxnet/issues/13114
> -
> https://discuss.mxnet.io/t/cudamalloc-failed-out-of-memory-when-replaying-the-train-ssd-py-example/4254
> 
> This is just 1 example of user experience of Q&A related to MXNet.
> 
> With discuss.mxnet.io in place since since Oct '17, it has been a place for
> answering many usability questions among other things. Inadvertently, lots
> of questions users will have would be already answered on discuss.mxnet.io
> & hence would pop up in results from the search-engine.
> 
> Question then is: What's the upside that github discussions gives to merit
> driving users away from already established website for discussions?
> 
> Would it confuse users into
> 1. Whether I should continue using discuss.mxnet.io for asking doubts?
> 2. Is there a distinction b/w what's to be asked on Github discussions?
> 
> Possible solution to this could be
> - Make discuss.mxnet.io "read-only". So while we hold onto the classic
> questions & their answers, we don't add onto them.
> - Add a banner on discuss.mxnet.io that states Github discussions as a new
> de-facto for Q&A
>     - This would make it easy for users to navigate to Github discussion
> from discuss.mxnet.io [in case if their question isn't already asked]
> 
> Thanks,
> Chai
> 
> 
> On Fri, 28 Aug 2020 at 16:01, Sheng Zha <zhasheng@apache.org> wrote:
> 
> > Hi Marco
> >
> > Thanks for the comment. I requested to have discussion categories feature
> > enabled. Currently the categories are fixed to be the following:
> > - Everything
> > - General
> > - Help
> > - Ideas
> > - Show and tell
> > - Thanks
> > - TIL (today I learned)
> >
> > I think Github is also working on enabling customization for categories
> > and we should have feature parity in terms of organizing threads by then.
> > For now I will treat your comment as a "yes" to enable discussions and "not
> > yet" for deprecating existing forum.
> >
> > Best,
> > Sheng
> >
> > On 2020/08/28 19:46:09, Marco de Abreu <marco.g.abreu@gmail.com> wrote:
> > > 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 <sskalic@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" <zhasheng@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
> > > >
> > > >
> > >
> >
> 
> 
> -- 
> *Chaitanya Prakash Bapat*
> *+1 (973) 953-6299*
> 
> [image: https://www.linkedin.com//in/chaibapat25]
> <https://github.com/ChaiBapchya>[image: https://www.facebook.com/chaibapat]
> <https://www.facebook.com/chaibapchya>[image:
> https://twitter.com/ChaiBapchya] <https://twitter.com/ChaiBapchya>[image:
> https://www.linkedin.com//in/chaibapat25]
> <https://www.linkedin.com//in/chaibapchya/>
> 

Mime
View raw message