Thanks for the excellent advice! I think you have raised a very important point - why do users come to the conversation? It feels to me that chat platform is t

Thanks for the excellent advice! I think you have raised a very important point - why do users come to the conversation? It feels to me that chat platform is then only a good fit where it is more conversational and not necessarily that much technical help. Storybook has done a great job to build their community on discord, and meteor has done a great job by using Discourse, however as a past storybook and meteor user I had a much better time finding help or how to answers in past conversation with meteor on discord than storybook. But I can imagine that if you need quick help with fast response chat is preferred, but only initially, when its too big / busy a ticketing solution can be a better alternative if it is only the maintainers providing help. ———— Your investigation skills are on point. We created a low code solution for building internal tools in yaml, and we really like open source and are playing with the idea of making it all open. At the moment we are making sure we do as much research as possible to make sure we best understand the implications of this decision. Check us out, lowdefy.com - I’m busy redesigning the website and defining our gtm strategy, so that will all change, visit docs.lowdefy.com (also built with lowdefy) to get the best idea for what it is.