Thanks for your interest in contributing to the the Exporter specs! We look forward to engaging with you.
- Read this CONTRIBUTING file
- Read our Code of Conduct
- Submit a pull request or issue. For pull requests, please also:
- Sign the Contributor Licensing Agreement, if you haven't already done so. (You will be prompted if we don't have a signed CLA already recorded.)
Do you have questions or are you experiencing unexpected behaviors after modifying this Open Source Software? Please engage with the “Build on New Relic” space in the Explorers Hub, New Relic’s Forum. Posts are publicly viewable by anyone, please do not include PII or sensitive information in your forum post.
We'd love to get your contributions to improve our Exporter Specs! Keep in mind when you submit your pull request, you'll need to sign the CLA via the click-through using CLA-Assistant. You only have to sign the CLA one time per project. To execute our corporate CLA, which is required if your contribution is on behalf of a company, or if you have any questions, please drop us an email at open-source@newrelic.com.
We use GitHub issues to track public issues and bugs. If possible, please provide a link to an example app or gist that reproduces the issue. When filing an issue, please ensure your description is clear and includes the following information.
- Reason for requesting the change
New Relic is committed to the security of our customers and their data. We believe that providing coordinated disclosure by security researchers and engaging with the security community are important means to achieve our security goals.
If you believe you have found a security vulnerability in this project or any of New Relic's products or websites, we welcome and greatly appreciate you reporting it to New Relic through HackerOne.
Before we can accept a pull request, you must sign our Contributor Licensing Agreement, if you have not already done so. This grants us the right to use your code under the same Apache 2.0 license as we use for this project in general.
The documentation in this repository uses GitHub Flavored Markdown (see: https://github.github.com/gfm/). All contributions to markdown files in this repository must be valid markdown.
It is highly recommended to wrap long lines in markdown files at 80 characters.
Before submitting a pull request, please verify that your contributions render correctly in your own fork.
By contributing to the Exporter Specs, you agree that your contributions will be licensed under the License file in the root directory of this source tree.