Skip to content

Latest commit

 

History

History
73 lines (52 loc) · 3.29 KB

File metadata and controls

73 lines (52 loc) · 3.29 KB

Contribution Guidelines

Thank you for your interest in contributing to the OWASP Machine Learning Security Top 10! We are thrilled that you are interested in improving the quality of our project. By following these guidelines, you can help us maintain a welcoming and collaborative community for everyone.

Code of Conduct

Before you start contributing, please read and abide by our Code of Conduct. We expect all contributors to treat each other with respect and create a positive and inclusive environment.

Ways to Contribute

There are several ways you can contribute to our project:

Participate in Discussions

Our project uses several forms of communication to allow contributors to choose their preference:

Contributors are encouraged to introduce themselves, and ask questions in the discussion groups.

Reporting Document and Website Issues

Issues with documentation and the project website can be reported using the following form and choosing either "Documentation Issue Report" or "Website Issue Report" from the 'Type' dropdown category.

Suggestions for Enhancements

If you have a idea or suggestion for an enhancement, feel free to use the enhancement request form and choosing "Suggestion for Improvement" from the 'Type' dropdown category.

Github Information

Pull Requests

We welcome code contributions! If you want to fix an issue or suggestion a new enhancement, we ask that you follow these steps:

  • Ensure you have configured Github with your signing key and have verified you are signing your Git commits
  • Fork the repository to your GitHub account.
    • You are more than welcome to fork the OWASP Machine Learning Security Top 10, but please abide by the Creative Commons BY-SA 4.0 license.
  • Create a new branch for your fix or enhancement off the 'develop' branch.
  • Make your changes and sign your commit with a concise title and descriptive comment.
  • Push your changes to your repository's fork.
  • Submit a pull request (PR) to our repository's 'develop' branch.

Commit Messages

Write clear and concise commit messages that describe the changes made in the commit.

Code Review

Be open to feedback during the code review process. Address the feedback promptly and make necessary changes if requested.