Panel Discussion: Finding the Right Comms for Your Community...- Sophia & Dave, Sarah, Nyah, Jocelyn

This panel discussion features four experienced community managers examining platform choices and strategies for open-source and professional communities. The panelists—Naya Macklin (Suborbital), Dave Clements (Condo community), Sarah Kaiser (non-profits), and Jocelyn Matthews (DevRel Collective)—share their experiences with different platform ecosystems.

**Platform Choices and Rationale**

Each panelist uses a different combination of tools reflecting their priorities:

Dave Clements emphasizes openness and history preservation: Matrix/Element for open, no-login chat; Discourse for Q&A discussions; mailing lists for announcements; and a community website. He values the ability to link to discussions as permanent resources.

Naya Macklin prioritizes safety and moderation: Threads for internal asynchronous communication (serving a global team), Discord for external developer engagement, mailing lists, and social media. She stresses fostering organic community conversation while maintaining safety.

Sarah Kaiser chose Discord for newer non-profit communities, citing three reasons: advanced moderation capabilities (especially three years ago), user familiarity reducing onboarding friction, and integrated voice/video/text chat eliminating external Zoom link confusion.

Jocelyn Matthews manages the decade-old DevRel Collective on Slack's free tier, prioritizing free tools and privacy. The community is deliberately private to allow candid conversations among competing professionals.

**Key Decision Factors**

All panelists considered safety and moderation as paramount. Additional factors varied: openness (Dave valued open protocols), cost (critical for volunteer communities), user familiarity (reducing platform friction), and integrated features (Discord's combined communication tools).

**Platform Challenges**

Slack's free tier has 90-day rolling message deletes, complicating moderation pattern tracking and requiring extra documentation. It's also built for required workplace communication, not voluntary communities, creating moderation friction. Customization is limited on the free tier.

Discord's default notification configuration is problematic; new users often rage-quit when overwhelmed. Video channels are limited to 25 people (though Stage channels support 1000+ for presentations). One panelist struggled with users gaining inappropriate @everyone permissions.

Matrix/Element is less polished than Slack or Discord, with a steeper learning curve for notifications. Communities like it but don't love it. One panelist mentioned Zulip as a potential alternative—a threaded chat interface that feels like a chat client. Rust and other communities have migrated to Zulip and "love" it, though it has a learning curve.

One panelist noted Discourse has no complaints, aside from not being open source.

**Automations and Workflows**

Discord automations include: bots for queuing community questions to core teams, Twitch streaming moderation, COC enforcement with automatic warnings and bans, calendar syncing for events, and custom bots connecting Discord forums to GitHub discussions.

Slack automations include: TypeForm-based applicant vetting (filtering recruiters), automatic GitHub issue creation per applicant, welcome bots, and admin shift reminders. DevRel Collective tracks moderator workflows.

Matrix supports plugins and open APIs; they built a Slack-to-Matrix bridge with 98% success during migration.

**Member Engagement and Analytics**

A key challenge emerged: low engagement rates. One panelist reported only ~10% of new Discord members engage beyond joining; many "Discord farm" (keep tabs open as resources without active participation). Panelists recommend understanding *why* members join and asking directly.

They use available analytics ethically: Discord offers 3-month rolling analytics (requiring manual download); Discourse has built-in analytics; Matrix requires custom API implementation. One panelist shifted community call times based on geographic analytics (identifying many India-based members), improving engagement.

For events, Discord Stage channels worked well for hackathon kickoffs (restricted participants, 1000+ audience), while one-on-one video remains limited to 25 people.

**Cross-platform Consolidation**

A panelist asked about consolidating Slack, Discord, Signal, etc. Responses included: Matrix Bridges can permanently connect platforms but face buy-in challenges; custom bots can pipe subset discussions for specific subgroups; no perfect consolidation tool exists. Panelists expressed frustration managing multiple platforms simultaneously.

**Key Takeaways**

1. No single best platform exists; trade-offs between polish vs. openness, cost vs. features, and simplicity vs. flexibility are unavoidable. 2. Modularity works: using multiple platforms for different purposes (chat, Q&A, announcements) is normal. 3. Moderation and safety should drive platform choices. 4. Smooth onboarding and reduced notification friction correlate with member activation. 5. Direct community feedback on what works is invaluable. 6. Automations for moderation, vetting, events, and workflows reduce maintainer burden. 7. Transparent analytics use and data privacy build trust.

Panelists noted no major catastrophes in current setups (though Slack faced one incident with overprivileged admins accessing member DMs during democratization efforts; Condo consolidated fragmented platforms when Slack's 90-day delete limit forced action). They expressed openness to Zulip if starting fresh, but migration costs keep established communities in place.