Document expected outcomes for Zowe

[balhar-jakub]

As the Zowe team, we have plenty of internalized assumptions about what Zowe is and what our goal is going forward. This is good enough for the current team, but it makes onboarding new contributors difficult and does not help potential users understand the full Zowe value proposition.

The goal of this issue is to analyze and agree on a few key outcomes for Zowe as a whole, then document them in an easily accessible way. The ZAC and TSC need to play an active role in the generation and documentation.

[balhar-jakub]

Examples of such outcomes may be:

• Zowe server side becomes part of the z/OS
• Zowe client side will be easily available in all major client-side operating systems
• Engineers without mainframe background feel as comfortable working with z/OS as with any other cloud ecosystem

[balhar-jakub]

Transferring the latest state that we should work with from the previous issue here:

By 2024 (3 years) - assume Zowe V2 is in maintenance and V3 LTS have been released:

1. Zowe is the preferred "defacto" standard for interacting with z/OS services.
   BA: I am not sure we want to claim "processes and data"? We can discuss.

2. Its ease of deployment and modern interfaces attract new talent to the mainframe platform by creating an experience which is similar to interacting with cloud platforms. By attracting new talent Zowe assists to both maintain existing z/OS workloads and grow new workloads.

3. Vendor offerings can easily leverage Zowe to create an ecosystem filled with consistent and compatible solutions that interact securely and seamlessly.

4. Zowe supports the deployment options demanded by the user and exploiter communities as well as being generally accepted as providing an excellent up-and-running experience for the installer. Zowe technology is flexible in its deployment options meaning the services can run natively on z/OS (for those environments that only have or want z/OS) or run Zowe on platforms in combination with z/OS such as Cloud or Distributed servers.

5. Zowe has an "app store" model with a variety of open/free apps, plug-ins and extensions for selective download with easy install/configure (and removal). Zowe to be a suite of services that consumers can pick and choose to deploy

6. Zowe is committed to preserving mainframe security and embraces the use of advanced authentication and authorization features when interacting with mainframe services. Zowe will integrate with and leverage the latest security capabilities of z/OS for the benefit of all Zowe consumers and software extensions they implement.
   BA: Being "respectful" didn't seem strong enough. I beefed up the words here (well tried)

7. Zowe protects the future of the mainframe platform by enabling and simplifying modernization and automation of mainframe workloads securely to ensure that they remain on the platform.
   BA: I propose removing this as I tried to merge this into item 2 above

[balhar-jakub]

Next step would be to discuss this on TSC and get input on the topic.