# Contribute to Zowe

You are welcome to contribute to Zowe in many forms and help make this project better! We want to make it as easy as possible for you to become a Zowe contributor. This topic outlines the different ways that you can get involved and provides some of the resources that are available to help you get started. All feedback is welcome.

# Report bugs and enhancements

If you have an issue that is specific to a sub-project or community team, feel free to submit an issue against a specific repo.

# Fix issues

# Send a Pull Request

All code in Zowe aligns with the established licensing and copyright notice guidelines (opens new window).

Before submitting a Pull Request, review the general Zowe Pull Request Guidelines (opens new window) and make sure that you provide the information that is required in the Pull Request template in that specific repo.

All Zowe commits need to be signed by using the Developer’s Certificate of Origin 1.1 (DCO) (opens new window), which is the same mechanism that the Linux® Kernel and many other communities use to manage code contributions. You need to add a Signed-off-by line as a part of the commit message. Here is an example Signed-off-by line, which indicates that the submitter accepts the DCO:

Signed-off-by: John Doe <john.doe@hisdomain.com>

You can find more information about DCO signoff in the zlc repo (opens new window).

# Report security issues

Please direct all security issues to zowe-security@lists.openmainframeproject.org. A member of the security team will reply to acknowledge receipt of the vulnerability and coordinate remediation with the affected project.

# Contribution guidelines

Check out the contribution guidelines for different components and squads to learn how to participate.

# Promote Zowe

# Helpful resources