Proposal: Build a dedicated Discord server for contributors and developers

[Shashank-Tripathi-07]

Background

In the celebration thread (#1603), @profvjreddi raised the question of how to improve communication and reduce the notification gap between contributors. I suggested that a dedicated Slack or Discord server for contributors could help -- one focused specifically on the development ecosystem (TinyTorch, MLSysim, Labs, Kits, StaffML) rather than the broader community server that serves many purposes at once.

This is a formal proposal to build and maintain that server.

What I'm proposing

A contributor-focused Discord server for developers actively working on the cs249r ecosystem. Not a general learner/reader community -- a dev space.

Suggested channels:

• #announcements -- maintainer broadcasts (releases, PRs merged, breaking changes)
• #tinytorch -- TinyTorch dev discussion
• #mlsysim -- MLSysim dev discussion
• #labs -- Lab content bugs, answer key issues, new lab ideas
• #kits -- Kit development
• #staffml -- StaffML discussion
• #prs-and-reviews -- PR coordination, reviewer requests
• #dev-meetings -- agenda, notes, and follow-ups from periodic sync calls
• #off-topic -- general dev chat

What I'd own:

• Server setup, channel structure, roles, permissions
• Bot configuration (GitHub webhook for new issues/PRs, if wanted)
• Moderation and keeping it focused on dev work
• Ongoing maintenance

Ownership model

I'd like to propose co-ownership with @profvjreddi rather than just handing over admin. Concretely:

• @profvjreddi holds Owner role -- final say on structure, membership, and direction
• I hold Admin role -- day-to-day build, moderation, and maintenance work
• Any core maintainer can be elevated to Moderator as the server grows

This way the server stays under the project's authority while I carry the operational load.

Dev meetings

One thing a Discord server enables that GitHub doesn't: periodic contributor sync calls. A short voice/video standup (even 30 minutes every few weeks) where active contributors can:

• Sync on what's in-flight across sub-projects
• Unblock PRs that have been stuck in review
• Discuss direction for upcoming milestones (Vol. 2 labs, TinyTorch modules, etc.)
• Onboard new contributors faster than async comments allow

The #dev-meetings channel would hold agendas beforehand and written summaries after, so async contributors stay in the loop.

Why Discord beats GitHub Discussions for a dev team

GitHub Discussions were built for community Q&A, not active development coordination. Discord is purpose-built for exactly this:

• Notifications that actually work -- no more missed threads; Discord pings are reliable and instant
• Real-time unblocking -- a 2-minute chat in #prs-and-reviews resolves what would take 3 days of async comment threads
• Threaded conversations per sub-project -- TinyTorch, MLSysim, Labs each get their own focused space instead of everything collapsing into one feed
• Built-in voice/video -- dev meetings, pair debugging, onboarding calls without needing a separate Zoom/Meet link
• Search that works for devs -- Discord's search is fast and scoped per channel; good enough for "what did we decide about X last week"
• Better contributor onboarding -- new contributors can ask quick questions without opening a formal issue; reduces friction significantly
• Roles and permissions -- maintainers, contributors, and readers can have different access levels, something GitHub Discussions can't do

GitHub Discussions still has value for formal decisions that need a permanent public record. The hybrid works well: Discord for coordination and speed, Discussions only when something needs to be documented for posterity.

Ask

@profvjreddi -- if you're open to this, I can have the server set up and ready to share within a day. You'd hold Owner, I'd hold Admin, and we build it together from there. Happy to adjust the structure or ownership model to whatever fits your constraints.

[profvjreddi]

Did ya guys set this up?

I do agree it'd be nice to have some sort of Discord server or something, but I just worry about maintenance. As you saw, we have the new LinkedIn page for MLSystems. I feel like we could get a lot of industry people to buy into this kind of thematic topic as a starter. One thing is that I'd really like to make sure people can contribute posts and so forth, so I'm thinking maybe we can link to a method for opening a GitHub issue if they want to submit something. Here's what you think.

[Shashank-Tripathi-07]

I thought I fumbled up so I closed this.

Sure we can do this, What we can do is you, me and whosoever you want can be made the moderator of the server and in there we can have a section wherein people can contribute blogs that can be featured on the LinkedIn page after your approval and everything. I'll set up a preview server that you can see before other join. Expect that to be messaged here in approx. 4 hours from now :)

[Shashank-Tripathi-07]

Here is the server link, please try it out and let's have an initial meet there to discuss whatever additions/subtractions you want in the server 🚀

@profvjreddi

https://discord.gg/MGF7cPM8

[profvjreddi]

Thanks for setting this up. I'll check it out.

[Shashank-Tripathi-07]

Currently, our workflow is quite good with the Github repo and Emails part, setting up a discord server would be good if we have a huge community of people wanting to interact on a daily basis and not at the scale at which we are right now. Later on, if justified we can build a server and run it but not now as the work required to return ratio doesn't look good enough to me. Closing this to remove this from active issues because of the reasons stated above.