Proposal: Real-time Communication Channel for Devs

[SkinnnyJay]

I’ve been trying to contribute and find places to add value/clean up code, and wanted to surface an idea. @qalandarov has been great at responding to PRs. Still, I wonder if there would be value in having a chat / mailing group / real-time communication channel to help crowdsource questions and coordinate between developers.

Proposal

Currently, everything is managed entirely through GitHub, which works—but turnaround times can sometimes be 24–72 hours. I think an additional layer of real-time communication could help us:

• Unblock PRs faster
• Coordinate on design/architecture questions
• Share quick context that doesn’t need to live in issues/PRs

I'm not suggesting we move discussions away from GitHub, but rather that we complement it with something lighter-weight for developer collaboration.

Open question:

• Would folks prefer to keep everything async here in GH, or do we see value in experimenting with a dedicated dev chat/mailing list?

[SkinnnyJay]

Some examples that come to mind are:

0. Head contributors are usually extremely busy ASYNC, and questions can go unanswered, leaving PR to rot vs. iteratively gaining clarity.
1. What do you think we should address in the next version?
2. What issues should be prioritized?
3. Emergency bug fixes
4. Internal communications and discussions that pollute the repo (issues/discussion/PR)