Zowe™ Is Zowe — What is an Authentic Distribution?
{Core} There is a myth that the Open Mainframe Project’s Zowe executable code is somehow different depending on where the software is acquired or how it is packaged. It’s a myth. Regardless of how and from who Zowe was obtained all Zowe conformant extensions will work with the installed Zowe. You won’t be required to have multiple Zowes in your infrastructure.
You may have already come across the zowe.org software download option as well as options provided by other vendors and are confused in how do they differ. As long as Zowe is acquired from the zowe.org open community or a Zowe Conformant Support Provider (you will learn what that means below), then Zowe is Zowe regardless of the provider or package format. If you are seeking more information about Zowe packaging, distribution or looking into how you can obtain support read the rest of this article.
Zowe is open source, and therefore could be cloned and modified. Being open source, customers or vendors could provide custom builds for use, which is why Zowe distinguishes the Conformant providers that abides by the rules that Zowe is Zowe. Zowe executable code is produced by the Zowe open community using one set of build processes. The open community provides the same code in a variety of package formats depending on the format most common for the code in question (SMP/E, PAX, PSWI, npm, etc.).
The Zowe version and release may change with enhancements and fixes but the same code is delivered to consumers even when it is via different (Support Conformant) vendors, or packaging or delivery methods. There can be additional Zowe extensions that a vendor may include in their Zowe distribution but Core Zowe will be the same. Not only do Conformant Support Providers deliver an authentic Zowe but they also agree to support the code following a set of principles that we will describe.
How is Zowe distributed?
The distribution of useful, executable software by the Zowe community is at the heart of Zowe’s value. As a collaborative effort, the community produces the Community version of Zowe, making it accessible to anyone who wishes to download and use it. Some open source communities provide only the source code, Zowe goes one step further to build the code and package it in a variety of formats for deployment and use.
One of the key benefits of Zowe is its open-source nature, which means that it is available for free under the EPL 2.0 license. This allows individuals and organizations to leverage its capabilities without any restrictions, as long as they adhere to the terms and conditions outlined in the license.
By relying on the collective efforts of the community, Zowe ensures that its software remains accessible and continuously improved upon. This collaborative approach fosters innovation and encourages individuals from various backgrounds to contribute their expertise to enhance the overall functionality and usability of Zowe.
How do I obtain support for Zowe?
The success and growth of Zowe, an open-source project, can be attributed to the dedicated support of its community. The collaborative efforts of individuals and organizations have played a vital role in advancing the capabilities and adoption of Zowe.
To further enhance the support ecosystem, we have introduced the Zowe Conformance Support Provider Program. This program enables vendors to claim support for Zowe or its components, ensuring that users have access to reliable assistance when using the project.
Conformant vendors who participate in this program are granted a badge, symbolizing their commitment to supporting Zowe. This badge serves as a mark of quality assurance, assuring users that these vendors are equipped to provide assistance with any genuine instance of Zowe, regardless of where it was obtained.
The Providers are expected to provide Support either for Zowe Core or for a subset of Core components based on the type of the Conformant Support that they claim to support. To learn more on the topic go to the [Zowe Conformant Support Provider Program](https://openmainframeproject.org/our-projects/zowe-conformant-support-provider-program/). The Extensions support isn’t guaranteed.
There are some key principles in the Support Conformance Program:
- Vendors agree to distribute unaltered Zowe Core software
- Vendors recognize Core Zowe distributions from other Conformant providers as binary equivalent to the open community software
- Vendors agree to follow the Zowe community security reporting procedures
- Vendors can make emergency changes to Zowe code to assist their customers but agree to contribute any fixes back to the community in a timely fashion and work with the community to incorporate fixes to the community source
What does Genuine Zowe mean?
Genuine instance of Zowe is an important point, but what does it actually mean? It means that the binary that is installed is the same as the one provided on [Downloads](https://www.zowe.org/download) by the Zowe Community. All conformant vendors provide the same genuine Zowe instance.
As a Conformant Support Vendor you need to recognize genuine Zowe instance installed in the system and provide support to the instance. Generally, we expect one Zowe instance per customer, which will serve as the foundation for all extensions, regardless of the vendor supporting the genuine Zowe instance or providing the extensions. This is especially true for Conformant extensions. These extensions are guaranteed to work seamlessly with other extensions in the ecosystem, ensuring that no functionality is compromised for other extensions.
It’s possible for the vendors to add additional content to their delivery. E.g. if you provide an CLI extension supporting version control system, it’s possible that the vendor will package the extension with their distribution and that’s ok as long as it will work with genuine Zowe installed from another vendor.
Conclusion
As users, we expect to have one genuine Zowe in our systems, serving as the basis for all the extensions provided by various vendors. The beauty of this approach is that it doesn’t matter where you obtain your Zowe from, as long as it is authentic, we will fully support it.
The concept of conformance plays a crucial role in ensuring compatibility and interoperability within the Zowe ecosystem. Conformant extensions are designed to seamlessly integrate with the genuine Zowe, providing users with a cohesive and efficient experience.
In conclusion, by embracing the genuine Zowe and its conformant extensions, we can foster a thriving community where users can benefit from a wide array of innovative solutions while enjoying continuous support and compatibility. Let us come together to build a stronger future for Zowe.
If you enjoyed this blog checkout more Zowe blogs here. Or, ask a question and join the conversation on the Open Mainframe Project Slack Channel #Zowe-dev, #Zowe-user or #Zowe-onboarding. If this is your first time using the OMP slack channel register here.
Zowe™, and the Zowe™ logo, and the Open Mainframe Project™are trademarks of the Linux Foundation.”
