1# Discord Rules 2 31. This community works together to build an Open Source BMC firmware. It's a 4 community expectation that you will provide access to your code in the course 5 of discussions. We are unable to build together if you are unable to share 6 your code. The community is not a substitute for a support contract. 7 82. OpenBMC community members are volunteering their time to answer your 9 questions. Please keep this in mind if you are waiting for a response. 10 113. All support questions must be asked in public channels. Do not send uninvited 12 private messages to other community members. Private requests for help place 13 an unfair burden of expectation on people volunteering their time. Further, 14 others in the community cannot help if they cannot see the question. 15 164. Don't post the same question in multiple channels. Doing so fragments the 17 conversation. If you're unsure of which channel to use, ask your question in 18 `#general` and we may redirect you elsewhere. 19 205. Reflect on whether your standing in the community is appropriate for the help 21 you are requesting. If you are new to the community, you will likely have the 22 most success by asking detailed, specific questions about detailed, specific 23 problems. Vague questions by unfamiliar people often go unanswered 24 256. Do not discuss undisclosed bugs that may have a security impact in Discord. 26 Instead, email `openbmc-security@lists.ozlabs.org` and follow the [documented 27 directions][1] 28 29[1]: 30 https://github.com/openbmc/docs/blob/master/security/how-to-report-a-security-vulnerability.md 31