Content Comparison

Zowe is an integrated and extensible framework designed to allow users the flexibility to choose how they interact with z/OS applications and services. In order to better serve this goal, the Zowe community is developing aConformance Program. 

The Zowe Conformance Program gives users the confidence that when they use a conformant product, app, or distribution they can relyon a high level of common functionality, interoperability and user experience. 

Conformance provides Independent Software Vendors (ISVs), SystemIntegrators (SIs) and end users confidence that their software will behave as expected.Just like Zowe, the Conformance program will continue to evolve and is being developed by committers and contributors in the community.

Hypothesis
For developers who want to build new or on-board existing applications the conformance program is a framework of specific criteria and tests that provides developers a self-serve path and submission process for identifying extension points and adhering to best practices.

...

• ZLC - this conformance program will effect every squad and require entire community participation
• OMP - will be influential in implementing and coordinating the other LF stakeholders including:
  • LF Creative Services- Responsible for designing conformance logo, developing mark and logo usage brand guidelines
  • Legal - Reviewing and developing the trademark Ts&Cs, developing conformance program Ts&Cs, develop the participant submission form
  • Trademark counsel - Responsible for identifying additional jurisdictions for registration, file USPTO registration marks and logo
  • LF Marketing - Prepare public announcements (press releases, blog posts, etc.) for the conformance program go-live

Stories

•  Determine details of the conformance program
•  Develop method of measuring and demonstrating conformance

  • Link to DRAFT Web-UI: https://github.com/zowe/zlux/blob/conformance/docs/app-conformance.md

  • Link to DRAFT CLI: https://github.com/zowe/zowe-cli/blob/conformance/docs/cli-conformance.md

  • Link to DRAFT API: https://github.com/zowe/api-layer/blob/conformance/docs/conformance.md

•  Determine who will perform the conformance testing
  • Develop set of testing capabilities allowing developers to self-check for conformance
  • Example: https://bestpractices.coreinfrastructure.org/en/projects/2226?criteria_level=1#changecontrol
•  Determine the different conformance categories: Conformant Applications and Conformant Distributions
•  What is the desired duration of conformance validation? After what level of release does conformance need to be re-tested? how will it effect the semantic versioning discussion?
•  Eligible participants and fees: For members of the OMP, there is no charge for certification. This is also no charge for non-profit organizations. For commercial organizations that wish to certify, but don't want to become and OMP member, the fee is the same as joining the OMP: https://www.openmainframeproject.org/about/join
•  Where and how will conformance program documents and brand assets be hosted? Zowe conformant applications conformance evaluation should be public knowledge and made available.
  •  Where and how to submit participation forms?
  •  Where and how to submit testing results?