I believe a healthy ecosystem isn’t built for a community. It’s built with them.
That’s why the DevRel team at Midnight is thrilled to debut the Community Board, a new GitHub-based hub designed to make collaboration more transparent, inclusive, and efficient.
Just this week, a longtime partner and contributor shared feedback that struck a chord:
“The real frustration hasn’t been the number of channels. It’s not knowing what happens to our ideas or feedback once they’re shared. Without transparency into follow-up, it feels like issues just disappear.”
The Community Board is our solution to that exact problem. It gives developers, partners, and community members visibility into what’s happening with their feedback. And more importantly, a seat at the table to help shape priorities and the opportunity to pick up work themselves.
How the Community Board Works
Submission Flow
- Anyone in the community can open an issue in the GitHub Community Hub repository.
- Issues cover a range of categories:
- Content Development (blogs, videos, docs, etc.)
- dApp Development (example apps, new features)
- Feature Demo Ideas (including i18n/localization)
- Feature Requests and Suggestions
- Bug Tracking
- Midnight Improvement Proposals (MIPs)
Triage Process
- An arbiter committee (currently DevRel, expanding over time to include dApp devs, SPOs, partners, and wallet holders) reviews submissions.
- Submissions are given clear statuses: Needs Discussion, Triaged, Rejected.
- Triage happens transparently, either live during Fireside Hangs or asynchronously on GitHub.
Grab-and-Go Board
- Triaged issues move into the Grab-and-Go Board, a curated space for vetted ideas.
- From here, contributors can claim work:
- DevRel team members
- Partners
- Ambassadors
- Ecosystem builders and developers
Community Voting
- Issues on the Grab-and-Go Board can be upvoted with emoji reactions.
- Voting provides constituency-driven signals, helping us prioritize based on real demand.
Execution and Integration
- Picked-up issues flow through columns:
To Do → In Progress → Needs Review → Done.
- Where needed, issues flagged for internal ownership move to the engineering teams' Jira board.
- Over time, the Community Board could become a central part of the Midnight Improvement Proposal (MIP) process.
Automation
- GitHub Actions automatically label issues, move them into the right boards, and reduce manual overhead, keeping the workflow fast and efficient.
Why this matters
- Ends fragmentation: One place for all community ideas and feedback
- Provides visibility: Everyone can see what stage a submission is in
- Enables contribution: Community members can pick up vetted tasks directly
- Democratizes prioritization: Voting ensures the roadmap reflects community demand
- Broadens our builder base: Reduces pressure on core teams and grows a contributor ecosystem
- Streamlines collaboration: Clear swimlanes, automation, and transparent triage keep the process efficient
This is still a work in progress, and we’ll continue refining it. But it’s a big step toward making Midnight a truly builder-driven ecosystem.
👉 Watch an overview/explainer video
👉 Explore the Community Board on GitHub
A huge thank you to Stevan Lohja and the DevRel team for building this, and to our community members for not just sharing feedback but leaning in to build alongside us. Together, we’re proving that privacy-first technology can be built in public, by and for the builders who believe in it. 🌱
Top comments (0)