[GitHub] [incubator-superset] muraiki commented on issue #7160: [HELP!] Please close issues & PRs.

[GitBox <gi...@apache.org>]

muraiki commented on issue #7160: [HELP!] Please close issues & PRs.
URL: https://github.com/apache/incubator-superset/issues/7160#issuecomment-479895186
 
 
   I agree that GitHub issues should not be used for user questions. But personally, I've commented in a few question issues because I couldn't find anywhere to get an answer, particularly regarding questions of great importance to adoption, such as what release candidate to use and the overall status / direction of the project. Furthermore, I commented on a PR that patched a vulnerability stemming from a dependency and still haven't gotten any detail on what the actual vulnerability is, and don't know if the various upgrades required (across release candidates) to merge the changes into my production instance will break my install. The difficulty in getting answers I think causes people to come here for lack of other options, so making a clear statement on where to go for support would be a big help. Sadly, this has led me to have to qualify every instance of my recommendation of this awesome project with negative caveats.
   
   There's some activity on the Slack instance, but from what I've seen and experienced many questions go unanswered. I don't think that it's a good place to handle support, especially since the history limit will cause answers to be lost, resulting in spam as the same questions are asked repeatedly. It's also proprietary and requires signing up just to search.
   
   While Stack Overflow is also proprietary, it does have excellent SEO that makes it easy for people to find answers to existing questions, as it's designed to produce long term support resources. It also doesn't require signing up to view answers (unlike if Slack was the preferred option).
   
   A mailing list is the most open solution, but they tend to devolve into chaos.
   
   Ultimately, an official avenue for support combined with a clear way to understand project status would hopefully reduce the incidence of general questions that have filled up GitHub issues.
   
   I also suggest enabling the GitHub wiki for this project, if only to be a place to collect the top FAQs and perhaps to relay news. This can be edited more easily than constantly committing new README files.
   
   Thank you all for your hard work on this project!

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services

---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org