Skip to content

Latest commit

 

History

History
53 lines (36 loc) · 2.34 KB

CONTRIBUTING.md

File metadata and controls

53 lines (36 loc) · 2.34 KB

Contributing to Trace Server Protocol

Thanks for your interest in the Trace Server Protocol! The following is a set of guidelines for contributing to the protocol.

How to Contribute

In order to contribute, please first open an issue that clearly describes the bug you intend to fix or the feature you would like to add. Make sure you provide a way to reproduce the bug or test the proposed feature.

Once you have your code ready for review, please open a pull request.

A committer will then review your contribution and help to get it merged.

Code of Conduct

This project is governed by the Eclipse Community Code of Conduct. By participating, you are expected to uphold this code.

Eclipse Development Process

This Eclipse Foundation open project is governed by the Eclipse Foundation Development Process and operates under the terms of the Eclipse IP Policy.

Eclipse Contributor Agreement

In order to be able to contribute to Eclipse Foundation projects you must electronically sign the Eclipse Contributor Agreement (ECA).

The ECA provides the Eclipse Foundation with a permanent record that you agree that each of your contributions will comply with the commitments documented in the Developer Certificate of Origin (DCO). Having an ECA on file associated with the email address matching the "Author" field of your contribution's Git commits fulfills the DCO's requirement that you sign-off on your contributions.

For more information, please see the Eclipse Committer Handbook.

Contact

For questions related to the Trace Server Protocol, please open a GitHub issue tracker.

The Trace Server Protocol is part of eclipse-cdt-cloud. If you have any questions regarding CDT Cloud, please refer to the contact options listed on the CDT.Cloud website.