4 ms·
Lately, I've seen a few open source projects go this way: GitHub issues, this gets unwieldy so they create a Discord, this descends into chaos so they nominate
by zikzak 5y ago
Lately, I've seen a few open source projects go this way: GitHub issues, this gets unwieldy so they create a Discord, this descends into chaos so they nominate a community volunteer, issues are then filtered by thier preferences, etc.
I like Discord, especially in the early days, you can reach out to the principal dev, etc. But it soon seems like they either disappear to get work done (good) or spend all thier time on it (bad). Either way you end up with chaos.
- derefr 5y agoOur company has a Discord, but we employ a professional Community Manager for it. When community members bring issues up: 1. they're encouraged to do so in public, so that other community members can help if possible, and/or so bots can reply with suggested FAQ answers; 2. the Community Manager will answer with the company line for questions the company has set answers to (e.g. "when are you releasing X?" or "why is [abusive DoS-like pattern of requests to your service] not working?"); 3. otherwise, if the Community Manager knows the answer for sure off the top of their head, they'll give the answer; 4. and if not, the Community Manager relays the question to an engineer in our Slack, where we either have an answer off the top of our heads, or we file it as an issue. Seems to work just fine for us so far. Some of the engineers are also sometimes in the Discord (and we're all registered to it), but other than the Community Manager, it's not our job to be in there.