06-23-2026, 11:38 PM
This is not a rulebook. It is a description of how good members behave here naturally. Read the rules first, then read this.
On tone and disagreement
Disagreeing with someone is fine. Dismissing them is not. You can say "I think that approach has a significant downside" without saying "that is a terrible idea." The first invites discussion. The second ends it.
If you find yourself writing something you would not say to someone in person at a technical meetup, reconsider.
On asking for help
Before posting in Help & Troubleshooting, spend 20 minutes trying to solve it yourself. Not because we do not want to help, but because the attempt will give you context that makes the question better and the answer more useful. When you do post, include what you tried, the exact error, and your environment.
On giving help
If someone is asking a beginner question, answer the question they asked. Save the "you should really be using X instead" for after you have answered what they actually wanted to know. Unsolicited architecture advice in response to a basic question is demoralizing.
On thread quality
Search before posting. If a thread already exists on the topic, reply to it rather than starting a new one. A forum with 10 threads on the same question is worse for everyone than one thread with 10 good replies.
If a thread helped you and you found the solution elsewhere, post the solution. "Fixed it, thanks" with no explanation wastes everyone's time including yours.
On self-promotion
Sharing something you built is welcome in Project Showcase or Tutorials. Dropping links to your products in unrelated threads is not. The difference is whether you are contributing to the conversation or interrupting it.
On sensitive topics
Politics and religion are off-topic here. Not because we are afraid of difficult conversations but because they derail technical forums reliably and predictably. Keep it to tech.
This document will be updated as the community evolves.
On tone and disagreement
Disagreeing with someone is fine. Dismissing them is not. You can say "I think that approach has a significant downside" without saying "that is a terrible idea." The first invites discussion. The second ends it.
If you find yourself writing something you would not say to someone in person at a technical meetup, reconsider.
On asking for help
Before posting in Help & Troubleshooting, spend 20 minutes trying to solve it yourself. Not because we do not want to help, but because the attempt will give you context that makes the question better and the answer more useful. When you do post, include what you tried, the exact error, and your environment.
On giving help
If someone is asking a beginner question, answer the question they asked. Save the "you should really be using X instead" for after you have answered what they actually wanted to know. Unsolicited architecture advice in response to a basic question is demoralizing.
On thread quality
Search before posting. If a thread already exists on the topic, reply to it rather than starting a new one. A forum with 10 threads on the same question is worse for everyone than one thread with 10 good replies.
If a thread helped you and you found the solution elsewhere, post the solution. "Fixed it, thanks" with no explanation wastes everyone's time including yours.
On self-promotion
Sharing something you built is welcome in Project Showcase or Tutorials. Dropping links to your products in unrelated threads is not. The difference is whether you are contributing to the conversation or interrupting it.
On sensitive topics
Politics and religion are off-topic here. Not because we are afraid of difficult conversations but because they derail technical forums reliably and predictably. Keep it to tech.
This document will be updated as the community evolves.