Did you find a bug?
-
Do not open up a GitHub issue if the bug is a security vulnerability in Open Enclave, and instead refer to our security policy.
-
Ensure the bug was not already reported by searching on GitHub under Issues.
-
If you're unable to find an open issue addressing the problem, open a new one. Be sure to include a title and clear description, as much relevant information as possible, and a code sample or an executable test case demonstrating the expected behavior that is not occurring.
Did you write a patch that fixes a bug?
Open a new GitHub pull request with the patch.
-
Ensure the PR description clearly describes the problem and solution. Include the relevant issue number if applicable.
-
Before submitting, please read the Contributing to Open Enclave guidelines to know more about coding conventions and benchmarks.
Do you intend to add a new feature or change an existing one?
- See the Contributing to Open Enclave guidelines regarding design discussion.
Additional References
- Explanation of the Open Enclave governance structure
- Explanation of Roles
- List of current Committers
- List of Community Governance Committee members