This guide will help you navigate the Zowe community, and learn more on how to contribute and provide feedback. If you look for more information please take a look at Zowe.org, if you are user looking for help the documentation for the project lives here
- Zowe Community
All community activities are scheduled on the Zowe Community calendar. All meetings are an open invitation for any community member to join.
You can also engage fellow community members through these channels
The Zowe community uses Slack as the primary means of interacting to facilitate active collaboration through the following channels.
Register an account with Slack at https://slack.openmainframeproject.org
- #zowe-user - This channel is for users to ask questions, look for help and interact with each other.
- #zowe-dev - Zowe development discussions.
- #zowe-ux - Zowe user experience discussions.
- #zowe-doc - Discuss or ask questions about the documentation.
- #zowe-onboarding - Develop the material and supporting activities for onboarding developers and users.
- #zowe-zlc - Ask questions or discuss topics with the Zowe Advisory Council.
- #zowe-tsc = Ask questions or discuss topics with the Technical Steering Committee
Sub-project specific channels:
- #zowe-api - Collaborate with channel members on the API Mediation Layer, propose new ideas, or interact with the squad.
- #zowe-cli - Collaborate with channel members on Zowe CLI, propose new ideas, and interact with the Zowe CLI community.
- #zowe-explorer - Collaborate with channel members on Zowe Explorer for VS Code, propose new ideas, and interact with the Zowe Explorer community.
- #zowe-python-client-sdk - Collaborate with channel members on Zowe Python Client SDK (incubation) and get involved.
- #zowe-mobile - Collaborate with channel members on Zowe Mobile (incubation) and get involved.
- #zowe-build - Discuss and review build related Issues.
- #zowe-cicd - Discuss pipeline related topics.
- Zowefirstname.lastname@example.org - Developers and contributors discussion. Join this mailing list.
- Zoweemail@example.com - User discussion and to provide feedback and submit inquiries. Join this mailing list.
- Zowefirstname.lastname@example.org - Discussion on topics related to project governance or anything else for the TSC. Join this mailing list.
Look for discussion on Zowe topics on the Open Mainframe Project Community Forums.
All code in Zowe aligns with the established licensing and copyright notice guidelines
Submit an issue
You can submit an issue (Bug or Feature) on Zowe in general at https://github.com/zowe/community/issues/new/choose. If you have an issue that is specific to a squad or specific repository, feel free to submit an issue against a specific repo.
Pull Request Guidelines
Pull requests cannot be merged without the approval of at least one maintainer, who will be looking for the pull request to meet requirements as follows:
- The code in the pull request must adhere to the general Code Style Guidelines and those for the squads.
- The code must compile/transpile (where applicable) and pass a smoke test such that the code is not known to break the current state of Zowe.
- The pull request must describe the purpose and implementation to the extent that the maintainer understands what is being accomplished. Some pull requests need less details than others depending on novelty.
- The pull request must state how to test this change, if applicable, such that the maintainer or a QA team can check correctness. The explanation may simply be to run included test code.
- If a pull request depends upon a pull request from the same / another repository that is pending, this must be stated such that maintainers know in which order to merge open pull requests.
Reporting Security Issues
Please direct all security issues to email@example.com. A member of the security group will reply to acknowledge receipt of the vulnerability and coordinate remediation with the affected squad.