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