Collaboration and Communication
Collaboration and Communication tests the channels, artifacts, and conventions that let distributed contributors work together - questions here often read as "what should you do first".
Match the channel to the job
- Mailing lists - asynchronous, archived, the place for decisions that must be quotable later.
- Chat (IRC, Matrix, Slack) - real time and ephemeral; summarize outcomes back into a persistent thread.
- Issue trackers - one problem per issue, searchable and linkable; the system of record for work.
- Pull/merge requests - inline code review tied to CI results.
- Wikis and documentation - durable reference material.
- Video calls - nuanced disagreement; publish notes afterwards.
Writing that gets action
A useful bug report contains version or commit, environment, minimal reproduction steps, expected versus actual behaviour, logs, and whether the problem is consistent. State what you already tried and which existing issues you searched. Code review comments should address the code, separate blocking objections from nits, and explain the reasoning. Security problems never go into the public tracker: use the private security contact or security.txt, coordinate disclosure, request a CVE, and keep an embargo until a fix ships.
Community health
Adopt a Code of Conduct with named enforcement contacts, default to asynchronous communication across time zones, use inclusive language, and record decisions where everyone can find them. Assume competence and patience: many "obvious" answers sit in the documentation, and many "naive" questions expose real documentation gaps.
Worked example
A report saying "it crashes on startup" is closed as unreproducible. Rewritten: version 2.4.1 from the distribution package, Fedora 40, Python 3.12; three numbered steps; expected window opens, actual KeyError: 'theme' traceback; reproduces with a fresh default profile; log attached; issues #812 and #905 searched and found unrelated. The reasoning is visible - maintainers triage on reproducibility and uniqueness, and this version supplies both.
Traps
- Filing security vulnerabilities in the public tracker.
- Deciding in direct messages, leaving no trace for future contributors.
- Treating chat history as documentation.
- Reporting bugs without a version or reproduction steps.