@PantheRedEye you’ve mentioned:
I would keep that in mind in any further discussions ;), but RW is the only community I’m on with Discord.
I feel like the topic of moderation is an important one for RedwoodJS, as its community is such a vital part of what Redwood actually is. Discourse is a great choice to build a community but it also lacks the energy and accessibility Discord has. They would definitely benefit from one another’s defining traits, so as a member of RedwoodJS I’d always look for what helps its community grow with the values it’s intended to have, and on a more global scope I’d be looking for a Discourse-Discord bot that supports the strengths of both tools.
This being said, we also aim at avoiding bottlenecks and the topic of moderation has come up in some occasions. Whatever solution we might come up with would be better if it didn’t require Core Team members’ dedication & time: efforts would be preferred in other things to help RW grow.
But this is somewhat a bit early to discuss, as it’s kinda very theoretical at the moment. I think what we really need to figure out is what we want to share and why, this should help us a lot more to understand what we can afford to do or not.
Migrating messages to build a new Discourse thread of question/answers/solution-s or migrating threads from the quick-help section to maintain a knowledge base would be very valuable and would also echo @dthyresson 's efforts on Discourse, who created posts at such effect.
I would definitely start with this and create a private Discourse category for the bot to bump up those knowledge bits - trial phase!
I would focus on migrating threads when a solution is found - and leave a last message posting the link to the Discourse newly created Knowledge base element/thread. In an effort to encourage a migration of the discussion, I would also simply close the thread in Discord ( is that possible? I see there are some options, like archiving a thread or changing its permissions to prevent new messages ). The OP of the thread and anyone with the core-team discord role could have a “Solution found” button. To think of it, if only the core-team role has that button, moderation would be there already.
Also, could we clean up threads with a solution found after some time? This could help with keeping things clean in Discord and making sure that no stone is left unturned.
If we can feed our Discourse Knowledge base with complete Question/answer/solution-s, that would be great. Any further discussion around the issue at hand, that could be healthy and necessary, would benefit from happening where the knowledge is stored and where the moderation is reinforced.
That’s where I’d begin thinking about it, as it seems to be a concrete, simple goal to define with clear immediate benefits. When we need more it will build up around this initial work.
Finishing thoughts FWIW: it seems to me that a Discord-Discourse bot should be thought of in regard to the community’s editorial line more than in terms of information events. RW’s Discord had a change in editorial line this year to simplify it, each community would have their own organization and purpose of content. But all those willing to use a Discourse-Discord bot will do it because they care for their community and want to keep track of meaningful content. The trap though is to get to a point where Discord and Discourse duplicate each others, where would be the point in living with/in those two?
Oh, and, I like your idea of being able to search Discourse from Discord.
I was hoping to use that and not have to make one. He had to slow development. I believe the ruby api library was outdated and it would not work inside of threads… the js library is actively maintained and has a large discord community. Questions and answers are plentiful there, which helps.