-
Notifications
You must be signed in to change notification settings - Fork 698
Contributing
For bugs be sure to search existing issues [bug fixes] first. Include steps to consistently reproduce the problem, actual vs. expected results, any output from your terminal, your OS version, and the version of scap-security-guide that the issue appears.
Read more guidelines for filing bugs...
For feature requests please first check our Enhancements to see if it already exists.
Before you start coding, join the OpenScap Security Guide mailing list, introduce yourself, and what you would like to work on.
To initiate a pull request, see Contributing Code below.
There are many ways you can contribute to the OpenScap Security Guide project:
- Fix a bug
- Implement a new feature
- Write XCCDF content
- Write OVAL content
- Test OpenSCAP Security Guide content and report bugs you find.
- Write unit tests for OpenSCAP Security Guide.
- Review pull requests, give feedback to the pull request authors, and merge approved pull requests.
Before submitting any pull request, please make sure to:
- Discuss any major changes or questions in the OpenSCAP mailing list.
- Test your changes or new XCCDF or OVAL content.
- Follow the Pull Request Guide.
OpenSCAP committers are responsible for reviewing all pull requests, providing feedback, and
ultimately merging code into the master branch.
Once you've opened a pull request, a committer will respond with an initial set of comments or merge your code. If no one reviews or responds to your pull request, please email the OpenSCAP mailing list.
Once your pull request is merged, it will appear in the next release of the OpenSCAP Security Guide!
Interested in becoming a committer? See the OpenSCAP Committer Guide for details. Committers are expected to review pull requests and providing feedback and suggestions on the direction of the project.
Even if you're not a committer, you're still welcome to give feedback on any pull request!