Contributing
There are many ways you can contribute to the SCAP Security Guide project:
- Providing feedback
- Fix a bug
- Implement a new feature
- Write XCCDF content
- Write OVAL content
- Test SSG content and report any bugs that you find.
- Write unit tests for SSG.
- Review pull requests, give feedback to the pull request authors, and merge approved pull requests.
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 package in which the issue appears.
Read more guidelines for filing bug reports here.
Feature Requests
Please first check our Enhancements to see if the feature request already exists. If not, request a new feature.
Before you start coding, join the SCAP Security Guide mailing list, introduce yourself, and let us know what you would like to work on.
To initiate a pull request, see Contributing Code below.
Before submitting any pull request, please make sure to:
- Create a fork of the OpenSCAP/scap-security-guide repository.
- Discuss any major changes or questions in the OpenSCAP mailing list.
- Test your changes of new XCCDF or OVAL content.
- Validate that the OVAL or XCCDF content is valid content.
- If needed, rebase your local repository to keep it up-to-date with the
masterand prevent any merge conflicts. - Follow the Pull Request Guide.
SSG project 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 SCAP 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!