Skip to content

Latest commit

 

History

History
63 lines (40 loc) · 2.81 KB

CONTRIBUTING.md

File metadata and controls

63 lines (40 loc) · 2.81 KB
Raw

Contributing guide

Want to contribute? Great! We try to make it easy, and all contributions, even the smaller ones, are more than welcome. This includes bug reports, fixes, documentation, examples... But first, read this page (including the small print at the end).

Legal

All original contributions to RedHat projects are licensed under the ASL - Apache License, version 2.0 or later, or, if another license is specified as governing the file or directory being modified, such other license.

All contributions are subject to the Developer Certificate of Origin (DCO). The DCO text is also included verbatim in the dco.txt file in the root directory of the repository.

Reporting an issue

This project uses GitHub issues to manage the issues. Open an issue directly in GitHub.

If you believe you found a bug, and it's likely possible, please indicate a way to reproduce it, what you are seeing and what you would expect to see.

Before you contribute

To contribute, use GitHub Pull Requests, from your own fork.

Also, make sure you have set up your Git authorship correctly:

git config --global user.name "Your Full Name"
git config --global user.email [email protected]

If you use different computers to contribute, please make sure the name is the same on all your computers.

We may use this information to acknowledge your contributions!

Code reviews

All submissions, including submissions by project members, need to be reviewed by at least one RedHat committer before being merged.

GitHub Pull Request Review Process is followed for every pull request.

Coding Guidelines

  • We primarily use the Git history to track authorship. GitHub also has this nice page with your contributions.
  • Please take care to write code that fits with existing code styles.
  • Commits should be atomic and semantic. Please properly squash your pull requests before submitting them. Fixup commits can be used temporarily during the review process but things should be squashed at the end to have meaningful commits.
  • We typically squash and merge pull requests when they are approved. This tends to keep the commit history a little bit more tidy without placing undue burden on the developers.

The small print

This project is an open source project, please act responsibly, be nice, polite and enjoy!