Skip to content

Latest commit

 

History

History
209 lines (188 loc) · 9 KB

support_provider_evaluation_guide_table.md

File metadata and controls

209 lines (188 loc) · 9 KB

Zowe Support Provider Conformance Guide

Zowe Support Provider Conformance Guide is a set of self-certifying and self-service tests to help support Zowe framework.

This guide describes the requirements of the support conformance program. All Applicants complete sections in the Core section. Items marked (best practice) are considered best practices.

Zowe Support Core Section

Zowe Binaries

Item Version Required Best Practice Conformant Criteria
1 v2 x Support Provider agrees: to provide capable support for the given authenticated binary(s) of the Zowe core component(s) being attested to for the version(s) of Zowe defined in this version of the Zowe Support Provider Conformance program.
Capable Support is defined as having necessary hardware, software, and persons to diagnose issues, code solutions, test solutions, and provide fixes for issues in a reasonable timeframe.
Zowe core component(s) are defined here.
Authenticated binaries are defined as those applicable to a given Zowe Core component and that passes the verification process (see here).
2 v2 x Support Provider agrees: to abide by the applicable license associated with the Zowe source code which produced the authenticated binaries.

Zowe Security

Item Version Required Best Practice Conformant Criteria
3 v2 x Support Provider agrees: to follow the Security Reporting Process outlined in the Zowe Docs Report Security Issues section when reporting security vulnerabilities (see here)

Zowe Fix Strategy

Item Version Required Best Practice Conformant Criteria
4 v2 x Support Provider agrees: to the extent that code is contributed upstream to the Zowe project by the Support Provider, the Support Provider would make such contributions adhere to the Zowe project contribution guidelines (see here).
5 v2 x Support Provider agrees: that it is able to both create and apply emergency fixes to the authenicated binary, including emergency fixes that may come from a third-party. Further, the Support Provider agrees to adhere to any requirements of the applicable license for the emergency fix. An emergency fix is defined as a change made to the components in the authenicated binary to resolve an issue which is deemed urgent or critical for use of the authenicated binary.

Zowe Support Components Section

  • Comprehensive Zowe Support Applicants: Mark and complete ALL sections below
  • Partial Zowe Support Applicants: Mark and complete just the sections applicable to your Support Offering
    • Zowe API Mediation Layer
    • Zowe App Framework
    • Zowe Command Line Interface
    • Zowe Explorer

For each of the applicable COMPONENT SECTIONS selected, Support Provider Applicant confirms Capable Support as defined in item (1) (mark each applicable section as conformant in "Conformant" column).

Zowe Component Requirements: API Mediation Layer

Item Version Required Best Practice Conformant Criteria
6 v2 x Support Provider confirms: Capable Support as defined in item (1)

Zowe Component Requirements: App Framework

Item Version Required Best Practice Conformant Criteria
7 v2 x Support Provider confirms: Capable Support as defined in item (1)

Zowe Component Requirements: Command Line Interface

Item Version Required Best Practice Conformant Criteria
8 v2 x Support Provider confirms: Capable Support as defined in item (1)

Zowe Component Requirements: Explorer

Item Version Required Best Practice Conformant Criteria
9 v2 x Support Provider confirms: Capable Support as defined in item (1)