Someone forwarded me a link to this thread about Zowe.  I am part of the Zowe 
project and would be happy to answer any questions you have.  

From the thread so far there are some good questions.  I'll try and answer them 
here.

Zowe's mission is to provide a rallying point for improving administrative / 
management capabilities on z/OS so we can lower the barrier for new system 
programmers and developers that are not interested in the platform.  Zowe is a 
collection of technologies from CA, IBM and Rocket that are broadly broken down 
into REST APIs and management, Web Desktop (we call this zLUX) and a command 
line interface.  The breakdown of initial contribution was IBM, Rocket and CA 
for the components described before.

Why?
A rising tide lifts all boats has been a common discussion point in the team.  
z/OS has traditionally been proprietary and this has created barriers that make 
interoperability across administrative and management domains a challenge.  The 
founding members (and read this as exactly that, founding members, we are 
reaching out to Synsort, BMC, Compuware and all the other ISVs to come and work 
with us.).   The intent is that we can make better applications through a REST 
enablement and modern technology.  This is not closed, all source is EPL 2.0 
and resides in a public GitHub at https://github.com/zowe.

How does this related to z/OSMF?
Think of z/OSMF as a collection of RESTful services.  Workflows, Notifications, 
Console access, files, ... .  Zowe will exploit the existing services in z/OSMF 
but we are also innovating with other industry vendors on new capabilities 
which z/OSMF is not doing.  Its an IBM product and we expect it will consume 
Zowe capabilities but we take the approach that we like RESTful services build 
on a secure fabric of SAF authentication.

If you have questions where the community is listening I'd venture over to 
openmainframeproject.slack.com.  Slack is open to anyone and you can particpate 
in the conversation.  Tell us where we're broken and suggest how we can 
improve.  

Feel free to reach out by e-mail, slack and join the community.

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN

Reply via email to