Open Source
OSS Community Etiquette
There's no HR in OSS, no manager, no contract. Everything runs on voluntary trust. One toxic participant can poison the atmosphere for hundreds of people - which is why communities take their Codes of Conduct very seriously.
- Node.js was forked into io.js in 2014 partly due to governance and culture issues - later reunified
- Rust community is known as the most inclusive in systems programming
- Homebrew developer dismissed for refusing to adopt a CoC - public controversy in 2018
- Django has a dedicated CoC enforcement team that handles reported violations
Code of Conduct and Communication Channels
A **Code of Conduct (CoC)** is not a formality. It's the set of rules that makes participation safe for everyone. Most large projects use the Contributor Covenant. Violating the CoC means a ban - even for technically correct content.
**Search before asking in Discord.** Maintainers and active contributors are tired of «it doesn't work / how do I do X». These questions have already been answered 50 times. Searching Discord history + GitHub Discussions + documentation - that's how you respect the community.
You disagree with a maintainer's architectural decision and believe it's technically wrong. How do you proceed?
Async Communication Across Time Zones
OSS operates asynchronously. A Vue.js maintainer in Shanghai, a React contributor in Berlin, a user in San Francisco. **Patience is a skill**, not just a virtue. Standard expectation: wait 2 weeks for a response on a PR/issue before pinging.
**How NOT to burn bridges:** Maintainers remember people. Someone who was rude in issues in 2021 is the same person asking for review of their library in 2023. The OSS community is small. Reputation takes years to build and can be destroyed by one bad comment.
You opened an important PR three weeks ago. No comments at all. What do you do?
Key Ideas
- CoC is not a formality: violations lead to bans even for technically correct content
- Issues for bugs and proposals, Discussions for questions, Discord for quick things
- 2-3 weeks of waiting is normal; a polite ping after that is standard etiquette
- English is the language of almost all international OSS projects
- OSS reputation takes years to build and can be destroyed by one bad comment
Related Topics
Etiquette understood - next: how to work effectively with maintainers.
- Next Lesson — Logical continuation
Вопросы для размышления
- Read the Contributor Covenant at contributorcovenant.org. Which points do you find most important and why?
- You see a question in GitHub Discussions written in your native language (not English). How do you respond?