- Why should we give and get community support?
- Always be respectful of the conversation.
- Don’t forget that everybody is coming from where they are coming from. There are many layers of knowledge and understanding required to understand some thing.
- Try to get the question-asker to give full information:
- Full output of the problem
ddev debug test
- DON’T be afraid that you’re not smart enough or experienced enough to answer the question
- DO learn as you help the person by trying to recreate the problem they’re having.
- Try to give people tools, not just answers. So help them find the place in the docs or Stack Overflow where their question is dealt with. Remember we’re trying to make them members of the community who can support others
- Try to make it so every conversation improves the community over the long term. Capture the problem in docs or improvements.
- When you receive an answer, be respectful of the community by trying to capture the answer. Remember that someone spent time with you. For free. And you’re saying you don’t have the time to write up an issue or a Stack Overflow?
- Be respectful of language differences. Try not to use metaphors or slang that may not be easy to understand for people following along who may not have the same language background.
- If someone gives you an answer, make sure to let them know that you received it (and whether it worked)
Venues:
- Issue queue: I love it when people subscribe to all issues and try to help out there.
- Discord: Try to use #support where possible, try to use threads elsewhere
- Stack Overflow is a great place for long-term storage of obscure answers or difficult questions. When somebody figures out the answer to an important question, try to get it written up there. (Of course, for basic questions, the docs are the place, but super complex ones don’t work there.)