Welcome, and thank you for your interest in contributing to Dynatrace OpenKit!
There are many ways in which you can contribute, beyond writing code. In this document you will find a high level overview how you can contribute.
Before making your first contribution, please read our Code of Conduct.
Your comments, feedback and questions are welcome, and we, the development team, provide answers on multiple channels.
If you do not have access to Dynatrace internal Slack, search for tickets on GitHub issues or report new ones.
If you do have access to Dynatrace internal Slack, you can use the public channel #team-openkit for questions.
In case you found a security issue, please do not file a public ticket, but rather contact us directly via openkit@dynatrace.com and send us your findings.
If you have found an issue with OpenKit, which is not security related, you can send us a bug report either via GitHub issues or via the Dynatrace support portal.
Pull requests are the best way to propose changes to the codebase (we use Github Flow). We actively welcome your pull requests:
- Fork the repo and create your branch.
- If you've added code that should be tested, add tests.
- If you've changed APIs, update the documentation.
- Ensure the changes build and tests are passing.
See Building OpenKit C/C++ for detailed instructions. - Issue that pull request!
Any contributions you make will be under the Apache 2.0 license that covers the project.