Community
darwinOS happens where the contributors gather — the repos, the chat, the weekly office hours, the RFC documents. Here's how to find us.
Real-time chat
The fastest way to talk to another contributor. Channels for kernel work, userland, hardware bring-up, website, and everything else. Lurkers welcome — lots of people lurk first and contribute later.
Weekly office hours
An open video call every week for questions, bring-up help, and planning. No agenda is required to show up; if you want to present something, drop a line in chat beforehand.
Getting unstuck
Asking for help
Stuck on a build error, a port, or an unfamiliar piece of the code? The #help channel and GitHub discussions are both good. Nobody gets shamed for asking.
Reporting a bug
A reproducible bug report with a minimal test case is the most useful thing you can file. If you're not sure whether something is a bug, ask in chat first.
Proposing a change
Small changes go straight to a pull request. Larger ones should start with an RFC so the design gets scrutiny before you write code nobody ends up using.
Reporting a security issue
Don't file public issues for anything that looks like a vulnerability. Use the private disclosure channel in the security policy — we'll follow up within 48 hours.