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.
Discuss staff connected with APIM.
Ask questions about Zowe CLI, propose new ideas, and interact with the Zowe CLI community.
Expand upon the base technologies being contributed to the project.
Zowe development discussions.
Develop the material and supporting activities for onboarding developers and users.
This channel is for users to ask questions, look for help and interact with each other.
Register an account with Slack at https://slack.openmainframeproject.org/
Community Mailing Lists:
There are three mailing lists for Zowe open to anyone who is interested in subscribing.
Allows developers and contributors to discuss feature ideation.
Allows users to provide feedback and submit inquiries.
Allows anyone to submit questions related to project governance, outlined in our charter.
The community calendar shows all of the scheduled meetings. All meetings are an open invitation for any community member to join.
Community Meeting Minutes and Recording:
Several of the squads will record and track important discussion and post meeting minutes and recordings here.
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:
- GitHub: https://github.com/zowe/docs-site
Create an issue here that relates to any Zowe documentation.
- Waffle (Backlog):https://waffle.io/zowe/community
Check here to see what the Onboarding squad is currently working on.
Web UI and File Editor
The top-level superproject for zLUX. zLUX includes the Zowe Desktop framework in addition to several built-in apps and an example server implementation.
zLUX Framework components for management of zLUX Apps. Used for window managers or web layouts.
A simple editor in a browser.
A collection of build, deploy, and run scripts & configuration files for running a simple zLUX server.
Contains essential zLUX proxy server components including SSO and service catalogs.
- Waffle (Backlog): https://waffle.io/zowe/zlux
Check here to see what the Web UI and File Editor squad is currently working on.
A command-line interface that lets application developers interact with z/OS remotely. Create an issue here for anything related to Zowe CLI.
A plug-in for Zowe CLI that lets you interact with IBM CICS.
A plug-in for Zowe CLI that lets you interact with IBM Db2.
Visual Studio Code Plug-in for Zowe, which lets users interact with z/OS data sets on a remote mainframe instance. Powered by Zowe CLI.
A sample plug-in for Zowe CLI. Includes tutorials for extenders who want to contribute to the Zowe CLI project or build plug-ins.
The Imperative CLI Framework on which Zowe CLI is built. Use the framework when contributing to Zowe CLI or developing CLI plug-ins.
- Waffle (Backlog): https://waffle.io/zowe/zowe-cli
Check here to see what the CLI squad is currently working on.
API Mediation and Security
- GitHub: Coming Soon
- Waffle (Backlog): Coming Soon
The JES Explorer application in the Zowe Web UI.
The Explorer server model project.
The MVS Explorer application in the Zowe Web UI.
Explorer Server component contribution.
An SSO plugin for the explorers.
Functional test of the Explorer server's API.
The USS Explorer application in the Zowe Web UI.
Explorer shared utilities project.
Packaging repository for the Zowe install scripts and files.
Perform Zowe installation and run smoke/integration tests.
- Waffle (Backlog): https://waffle.io/zowe/zowe-install-packaging
Check here to see what the Foundation (CI/CD) squad is currently working on.
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: firstname.lastname@example.org .
A member of the ZLC will reply to acknowledge receipt of the vulnerability and coordinate remediation with the affected project.