be kind. be curious. assume good intentions.
we're all here because we care about building something great. that means treating each other with respect — even (especially) when we disagree.
be generous with context. not everyone has the same background. if someone asks a question that seems obvious, remember that you once didn't know the answer either. explain things patiently. link to docs. share what you've learned.
give feedback on the work, not the person. "this approach might have a race condition" is helpful. "you clearly don't understand concurrency" is not. we review code, not people.
make space for others. if you notice someone being talked over or ignored, bring them back into the conversation. great ideas come from unexpected places.
ask questions before making assumptions. if a PR or comment confuses you, ask for clarification. most misunderstandings are just that — misunderstandings.
own your mistakes. everyone ships bugs. everyone writes code they later regret. say "my bad, here's the fix" and move on. no shame in that.
- harassment, intimidation, or personal attacks — in any form
- discriminatory language or behavior based on identity, background, or experience level
- deliberately destructive behavior (trolling, derailing, sustained negativity)
- publishing others' private information without consent
these aren't gray areas. if you see this happening, say something.
conflicts happen in any community. most of the time, a direct and honest conversation resolves things. if you're uncomfortable addressing it yourself, or if the behavior continues:
- reach out privately to a maintainer — we'll listen
- email conduct@emberdb.com for sensitive issues
- we'll investigate, keep your report confidential, and take appropriate action
we'd rather hear about a concern that turns out to be nothing than miss something that's making someone feel unwelcome.
maintainers will address violations with a response proportional to the behavior:
- a private conversation — for first-time or minor issues. most things are resolved here.
- a public note — if the behavior happened in public and the community needs to see it addressed.
- temporary suspension — for repeated or serious violations.
- permanent ban — for behavior that makes the community unsafe.
we don't enjoy enforcing rules. we'd much rather spend our time writing code and helping people. but keeping this community safe and welcoming is non-negotiable.
this applies everywhere ember lives — GitHub issues, pull requests, discussions, Discord, and any other space where you're representing or participating in the project.
rules can't cover every situation. what matters more than any specific guideline is the culture we build together: one where people feel safe to ask questions, make mistakes, and grow as engineers.
if you're here, you belong here. let's build something great.