Hello Nothing Community!
I’m Kuber Mehta, a fellow Nothing enthusiast and college student who actively maintains the “Nothing OS Bugs and Things that keep me up at night” thread on the Nothing Discord, but Discord threads are hard to manage for things like these, so I wanted to share an idea with you all and get your thoughts.
The Problem
I’ve noticed how challenging it can be to track bug reports across Discord, forums, and various feedback channels. We’ve all experienced the frustration of:
Not knowing if a bug has already been reported
Searching through multiple threads to find workarounds
Uncertainty about whether issues are being tracked
Difficulty following up on previously reported problems
My Proposal
I’d like to develop a dedicated, open-source bug tracking website-repository (potentially at bugs.nothing.community) that would:
Create a structured, searchable database of reported issues
Allow community contributions through a moderated system
Categorize bugs by device, OS version, and severity
Track resolution status over time
Provide a single reference point for all community-reported bugs
Community Benefits
This would help us all by:
Making it easier to check if others experience the same issues
Creating a knowledge base of workarounds and solutions
Providing clear visibility on which bugs are most widespread
Establishing a more organized feedback channel to Nothing
My Background
I’ve built similar systems before - my personal blog (kuberwastaken.github.io/blog) runs on markdown parsed into a stylized, feature rich Web Page. You can check out my work at kuberwastaken.github.io.
The Ask
Community Input: Do you think this would be valuable? What features would you want to see?
Nothing Team Attention: If there’s enough community interest, I’d love to develop this as part of a summer internship with Nothing, bringing this tool to life with official support.
I love building useful tools for communities I care about, and I believe this could significantly improve our collective experience with Nothing products as well as make it easier for the team!
What do you all think? Would this be useful to you? Any suggestions or feedback?
