The Zowe community is divided up into teams (or squads) that have specific missions and goals. Like any open source project, each team/squad is made up of contributors and committers. Communication is important for a healthy community and each squad uses similar tools to foster collaboration and promote transparency.

All code contributed to the Zowe project is licensed under the Eclipse Public License 2.0


Community Slack Channels:

The Zowe community uses Slack as the primary means of interacting to facilitate active collaboration through the following channels.

  • #zowe-api
    Discuss staff connected with APIM.
  • #zowe-cli
    Ask questions about Zowe CLI, propose new ideas, and interact with the Zowe CLI community.
  • #zowe-core
    Expand upon the base technologies being contributed to the project.
  • #zowe-dev
    Zowe development discussions.
  • #zowe-onboarding
    Develop the material and supporting activities for onboarding developers and users.
  • #zowe-user
    This channel is for users to ask questions, look for help and interact with each other.
  • #zowe-zlc
    Leadership Committee.


Register an account with Slack at

Community Mailing Lists:

There are three mailing lists for Zowe open to anyone who is interested in subscribing.


Community Calendar:


Community Meeting Minutes and Recording:


Contribute Code, Issues or Bugs, Designs, Comments, Questions, Security Issues etc.

In general, Zowe uses GitHub to submit issues. If you are unsure of which repo to submit an issue to you can use the community waffle board to create a "card" and track your question, comment or concern there. However, we always try to keep the issues as close to the code as possible. See the specific squad Github repos and Waffle boards below:



Web UI and File Editor




API Mediation and Security
  • GitHub: Coming Soon
  • Waffle (Backlog): Coming Soon


Foundation (CI/CD)
Reporting Security Issues

Security issues should not be reported through the Git Issues process due to the sensitive nature of the information.

Please direct all security issues to the Zowe Leadership Comittee using the following e-mail address: .

A member of the ZLC will reply to acknowledge receipt of the vulnerability and coordinate remediation with the affected project.

  Code Guidelines

Learn the coding guidelines that you should follow while contributing to Zowe Project.

Read the Guidelines

  GitHub Repo

View or contribute to the project through Zowe GitHub.