Revise and Publish the V2 Conformance Program

[RASakach]

The Zowe V2 Conformance Program needs to be published ASAP

• Update Testing Criteria
• Update the application process (include forms in each application)
• Publish a new page / site for V2 conformance
• Publish the V2 landscape

[RASakach]

@jmertic we noticed the Conformance Page has been partially updated for the "V2" conformance program. We have a few issues that need to be addressed: (1) The page is displaying V1 badges: ZoweConformancePage.PNG (2) The Testing Criteria is the V1 criteria

Please help us address #1 For #2 I believe we have a PULL REQUEST

[jmertic]

Sorry about (1) - forgot to save my changes to the page. Should be fixed now.

Once we merge the PR for (2) we can update the other links. The application link should be correct.

[RASakach]

@jmertic we will have a new PR ready for review for today.

[pdubz3]

(Jan Prihoda - June 10) PR is closed now and merged. V2 landscape is published and available. Test evaluation guides are also published.

[RASakach]

Next Steps to creating a new Docusign that includes a checklist / conformance criteria.

• Jan will work towards presenting OMP a "POC"
• Discuss changes with OMP (Rose to schedule call w/John)
• OMP owns the repo that houses the Docusign

Issue: Many V2 applicants have expressed concern over the delay in processing Action: Rose will open an issue and tag Yarille and John.

[jmertic]

Hey, been playing with the form and think we could do this pretty easy with DocuSign as it has the ability to attach a document.

I tweaked the form to make it easier to get through. Curious on what y'all think...

Zowe.Conformance.Program.-.Participation.Form.pdf

[jmertic]

Any feedback on this @RASakach ?

[RASakach]

Hi @jmertic : this is heading in the right direction. We'd like to progress this even further as follows:

1. One form per request
2. Each form should include a link to the appropriate testing criteria PDF
3. The testing criteria PDF will be able to accept "X"s and can be saved for attaching
4. A note indicating that the completed forms will be stored in a github location (link will be included)

@jp669844 was going to present a sample for your review. OK with you if we proceed or do you have concerns that we should discuss before moving forward?

[jmertic]

Thanks @RASakach!

I was thinking about the one form per request part. Since the Testing Criteria also contains each type of conformance, I'm not sure there is a good value in splitting all the forms out individually. Especially since Docusign will let you attach files in the form, it feels like splitting out doesn't have much value. What do you think?

[Domenico224]

As per today onboarding meeting I agree with Rose, it would be useful to have one form x request, including the specific criteria for the request with the possibility to check the criteria matched.

[jmertic]

Hey - trying to understand the requirements a bit more as I'm unclear. Are we saying that the Test Evaluation Guide will also have multiple versions as well for each type of conformance?

[Domenico224]

The test evaluation guide alerady includes different sections that apply to the different conformance badges. So in the form for the Zowe CLI badge, only the conformance criteria for Zowe CLI should appear.

[jmertic]

Are you saying that should be in the participation form itself? Sorry I'm a bit confused on requirements.

[Domenico224]

yes, in the participation form, making it specific for the badge you are requesting, it is what we said in today meeting @RASakach please confirm I got it correctly

[jmertic]

So if that is the proposal, I see two concerns...

1. From a usability standpoint, I would imagine one would take the Test Evaluation Guide with their technical teams to review and complete, and then go to the DocuSign agreement to submit for conformance. Having some need to use the DocuSign form for a working document seems to overcomplicate things.
2. When we see one completing multiple conformance types for a single offering, all of the details of the offering ( name, description, URL ) tend to be identical. If we are stating now that for that use-case they would need to complete two participation forms vs one, that seems again to be a step backward.

From my understanding, the primary goal is to have the Test Evaluation Guide submitted and published for offerings. I think what I proposed satisfies that requirement while not adding much burden to the submitter. If there are additional goals let's chat and outline these so we can be on the same page. Apologizes for any confusion caused.

[jmertic]

I would also suggest we either rename this ticket or create a new one since this request feels to be a bit different than the original ( and the original seems to be fulfilled ).

[RASakach]

Onboarding meeting on 8/5 with J Mertic

• We agreed to the following:

• Include the checklist in the docusign application

• allow the user to submit for more than 1 conformance badge on a single application

• deliver a Web UI that allows the applicant to complete the form interactively and click submit

• Store the application in a designated Github repo

Action Items:

• Research the APIs for docusign
• define goal and how we plan to achieve them
• interact with Doc Squad and exchange ideas / insights

[RASakach]

Onboarding update 10/21:

Action Items:

• Docusign research pending
• Web UI research leads to needing a community-based 3rd-party application for forms (research continues) - current Github pages will not suffice

[RASakach]

We will close this issue and move the items related to the application process over to a new issue dedicated to V3 Conformance