Date   

Re: [zowe-zlc] [DISCUSS] Updated Governance Documents and ZLC Succession Plan

Tim Brooks
 

Hi Matt,
 
Great note - we really have done a lot in the past year.
 
One question I have is what you are looking to be reviewed in the community repo? I have been working with the other squad leads to have the committers contribute their contact info to a committers list here: https://github.com/zowe/community/blob/Committer-List/Zowe%20Committers.md
Its in a separate branch than the one you had listed in your note.
 
Tim Brooks
Associate Offering Manager - Zowe
IBM Z
Office: 919-254-2436
Mobile: 703-343-5030
 
 
 

----- Original message -----
From: "Matt Hogstrom" <matt@...>
Sent by: zowe-zlc@...
To: zowe-zlc@..., zowe-users@..., zowe-user@...
Cc:
Subject: [EXTERNAL] [zowe-zlc] [DISCUSS] Updated Governance Documents and ZLC Succession Plan
Date: Sun, Jul 7, 2019 9:25 PM
 
We are preparing to setup a vote for the Zowe Project in accordance with the original charter we created last year when the project was open sourced.  Please review the following branches for changes to documents
 
 
Comments and questions can be directed to the mailing lists.
 
One area that we’ve been discussing at the ZLC is succession.  We’ve learned a lot this last year from the time we originally open sourced.  Some of the accomplishments and lessons learned (in no particular order):
 
* Break the CLI apart from the main Zowe release.  
* Learned the importance of constant communication.  I think this was not a lesson inasmuch as a better understanding at how to communicate openly as many of the participants work for companies accustomed to proprietary software.
* Realized the importance of considering existing users of z/OS systems and their unique process and support requirements.
* Registered the OpenMainframeProject with IBM as an ISV for z/OS software.
* Secured message IDs for ZWE and OMP prefixes to ensure consistent messages and naming
* Created the zowe-common-c project as a new project to reduce proprietary binaries
* Improved the ZWESIS by allowing multiple versions of Zowe to co-exist on a single z/OS instance (we prefer one but backwards compatibility is important)
* Added JWT support into the API Mediation Layer
* Worked collaboratively with the IBM z/OSMF team during architecture calls and as we factor in new capability.
* Discussed openly how Zowe can be architected to provide for a vendor neutral distribution for support services.
* Received a significant amount of media attention via the OMP media relations teams.
* Worked with Marist to bring our first z/OS system for community builds on real hardware (almost there) with the popular security managers ACF2, RACF and Top Secret each in their own instance.
* Migrated most of our resources to Linux Foundation infrastructure.
* Created extensions for VSCode to make accessing z/OS more intuitive (several folks use them internally at IBM and users keep asking to bring their own IDE.
* Understood from users that we needed to change our install / packaging and the CUPIDS team came together.
 
In all its been a really good year.
 
One area that has become clearer now is that we need some consistency at the top level as we continue to make a number of changes.  To aid in consistency we feel that rather than replacing the ZLC each year a staggered approach is a better alternative.  Please review and comment specifically on this document https://github.com/zowe/zlc/blob/20190418-process-updates/process/ZLC%20Succession%20Plan%20-%201.md
 
The unfortunate side effect is that the size of the ZLC will grow over the next few years and then provide a staggered approach to adding new members.  I have to give Tim Brooks a nod for the suggestion as it strikes a good balance between loss of continuity and growth of the community through diversity.  
 
We will be starting a community wide vote in a little over a week and will allow the voting to take place over a few days to allow for various timezones, vacations and the like.  We will tally and complete the voting prior to the face to face at Share for those that can attend.
 
More on the voting process to come this week as we’re still investigating a tool to facilitate the voting.
 
This thread is for discussion as a community.
 
Personally I’m very proud at what we’ve accomplished, how we’ve progressed and where we are going.  It’s an honor to work alongside everyone in the community.

Matt Hogstrom
matt@...
+1-919-656-0564
PGP Key: 0x90ECB270
Facebook  LinkedIn  Twitter

“It may be cognitive, but, it ain’t intuitive."
— Hogstrom
 


[DISCUSS] Updated Governance Documents and ZLC Succession Plan

Matt Hogstrom
 

We are preparing to setup a vote for the Zowe Project in accordance with the original charter we created last year when the project was open sourced.  Please review the following branches for changes to documents


Comments and questions can be directed to the mailing lists.

One area that we’ve been discussing at the ZLC is succession.  We’ve learned a lot this last year from the time we originally open sourced.  Some of the accomplishments and lessons learned (in no particular order):

* Break the CLI apart from the main Zowe release.  
* Learned the importance of constant communication.  I think this was not a lesson inasmuch as a better understanding at how to communicate openly as many of the participants work for companies accustomed to proprietary software.
* Realized the importance of considering existing users of z/OS systems and their unique process and support requirements.
* Registered the OpenMainframeProject with IBM as an ISV for z/OS software.
* Secured message IDs for ZWE and OMP prefixes to ensure consistent messages and naming
* Created the zowe-common-c project as a new project to reduce proprietary binaries
* Improved the ZWESIS by allowing multiple versions of Zowe to co-exist on a single z/OS instance (we prefer one but backwards compatibility is important)
* Added JWT support into the API Mediation Layer
* Worked collaboratively with the IBM z/OSMF team during architecture calls and as we factor in new capability.
* Discussed openly how Zowe can be architected to provide for a vendor neutral distribution for support services.
* Received a significant amount of media attention via the OMP media relations teams.
* Worked with Marist to bring our first z/OS system for community builds on real hardware (almost there) with the popular security managers ACF2, RACF and Top Secret each in their own instance.
* Migrated most of our resources to Linux Foundation infrastructure.
* Created extensions for VSCode to make accessing z/OS more intuitive (several folks use them internally at IBM and users keep asking to bring their own IDE.
* Understood from users that we needed to change our install / packaging and the CUPIDS team came together.

In all its been a really good year.

One area that has become clearer now is that we need some consistency at the top level as we continue to make a number of changes.  To aid in consistency we feel that rather than replacing the ZLC each year a staggered approach is a better alternative.  Please review and comment specifically on this document https://github.com/zowe/zlc/blob/20190418-process-updates/process/ZLC%20Succession%20Plan%20-%201.md

The unfortunate side effect is that the size of the ZLC will grow over the next few years and then provide a staggered approach to adding new members.  I have to give Tim Brooks a nod for the suggestion as it strikes a good balance between loss of continuity and growth of the community through diversity.  

We will be starting a community wide vote in a little over a week and will allow the voting to take place over a few days to allow for various timezones, vacations and the like.  We will tally and complete the voting prior to the face to face at Share for those that can attend.

More on the voting process to come this week as we’re still investigating a tool to facilitate the voting.

This thread is for discussion as a community.

Personally I’m very proud at what we’ve accomplished, how we’ve progressed and where we are going.  It’s an honor to work alongside everyone in the community.

Matt Hogstrom
matt@...
+1-919-656-0564
PGP Key: 0x90ECB270
Facebook  LinkedIn  Twitter

“It may be cognitive, but, it ain’t intuitive."
— Hogstrom


Re: [zowe-dev] [zowe-user] [VOTE] Require Multi-Factor Authentication for Committers to Zowe Projects in GitHub

Jean-Yves Baudy
 

+1

Cordialement, Regards.


IBM France Lab logoJean-Yves BAUDY
IT Specialist
z System Software
IBM France Laboratory
Office: +33 2 51 16 40 48
Mobile: +33 6 74 68 49 12

baudy.jy@...
IBM logo
1 Bis Avenue Gulf Stream
44380 Pornichet - France


"Joe Winchester" ---20/06/2019 13:08:52---+1 Joe Winchester IBM z/OS Explorer Senior Technical Staff Member - Project Zowe Contributor zowe

From: "Joe Winchester" <winchest@...>
To: zowe-dev@...
Cc: zowe-dev@..., zowe-user@..., zowe-zlc@...
Date: 20/06/2019 13:08
Subject: [EXTERNAL] Re: [zowe-dev] [zowe-user] [VOTE] Require Multi-Factor Authentication for Committers to Zowe Projects in GitHub
Sent by: zowe-user@...





+1

Joe Winchester
IBM z/OS Explorer Senior Technical Staff Member - Project Zowe Contributor zowe.org

Phone: 44-7749-965423
Twitter: @JoeWinchester LinkedIn: joewinchester
E-mail: winchest@...


----- Original message -----
From: "Matt Hogstrom" <matt@...>
Sent by: zowe-dev@...
To: zowe-user@...
Cc: zowe-zlc@..., zowe-dev@...
Subject: Re: [zowe-dev] [zowe-user] [VOTE] Require Multi-Factor Authentication for Committers to Zowe Projects in GitHub
Date: Thu, Jun 20, 2019 1:38 AM

Vote passes … all +1s with


+1’s
Matt Hogstrom
Sean Grady
Jean-Philippe Linardon
Mark Ackert
Jean-Louis Vignaud

Petr Plavjanik
Michael Supak
Guilherme Cartier
Doug Ross
Vitek Vicek
Joe Winchester



Matt Hogstrom

matt@...
+1-919-656-0564
PGP Key: 0x90ECB270

Facebook LinkedIn Twitter

“It may be cognitive, but, it ain’t intuitive."
— Hogstrom

      On Jun 12, 2019, at 3:16 PM, Matt Hogstrom via Lists.Openmainframeproject.Org <matt=hogstrom.org@...> wrote:

      As discussed in the ZLC meeting security is a critical aspect for Zowe as it is in all projects. To increase security all Committers (members of the Zowe organization in GitHub) should have multi-factor authentication enabled.

      After July 17th those members of the community that have not enabled MFA in GitHub will have their write access suspended until their account is secured with MFA.

      ZLC members have binding votes but all are welcome to express their view.

      Please respond to this e-mail with
      +1 - Approve
      0 - No opinon
      -1 - Disagree (please respond with specific objections)


      Matt Hogstrom

      matt@...
      +1-919-656-0564
      PGP Key: 0x90ECB270

      Facebook LinkedIn Twitter

      “It may be cognitive, but, it ain’t intuitive."
      — Hogstrom


Unless stated otherwise above:
IBM United Kingdom Limited - Registered in England and Wales with number 741598.
Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU





Re: [zowe-dev] [zowe-user] [VOTE] Require Multi-Factor Authentication for Committers to Zowe Projects in GitHub

Joe Winchester
 

+1
 
Joe Winchester
IBM z/OS Explorer Senior Technical Staff Member - Project Zowe Contributor zowe.org
 
Phone: 44-7749-965423
Twitter: @JoeWinchester    LinkedIn: joewinchester
E-mail: winchest@...
 
 
----- Original message -----
From: "Matt Hogstrom" <matt@...>
Sent by: zowe-dev@...
To: zowe-user@...
Cc: zowe-zlc@..., zowe-dev@...
Subject: Re: [zowe-dev] [zowe-user] [VOTE] Require Multi-Factor Authentication for Committers to Zowe Projects in GitHub
Date: Thu, Jun 20, 2019 1:38 AM
 
Vote passes … all +1s with 
 
+1’s
Matt Hogstrom
Sean Grady
Jean-Philippe Linardon
Mark Ackert
Jean-Louis Vignaud
 
Petr Plavjanik
Michael Supak
Guilherme Cartier
Doug Ross
Vitek Vicek
Joe Winchester
 
 

Matt Hogstrom
matt@...
+1-919-656-0564
PGP Key: 0x90ECB270
Facebook  LinkedIn  Twitter

“It may be cognitive, but, it ain’t intuitive."
— Hogstrom
 
On Jun 12, 2019, at 3:16 PM, Matt Hogstrom via Lists.Openmainframeproject.Org <matt=hogstrom.org@...> wrote:
 
As discussed in the ZLC meeting security is a critical aspect for Zowe as it is in all projects.  To increase security all Committers (members of the Zowe organization in GitHub) should have multi-factor authentication enabled.
 
After July 17th those members of the community that have not enabled MFA in GitHub will have their write access suspended until their account is secured with MFA.
 
ZLC members have binding votes but all are welcome to express their view.
 
Please respond to this e-mail with
+1 - Approve
 0 - No opinon
-1 - Disagree (please respond with specific objections)
 

Matt Hogstrom
matt@...
+1-919-656-0564
PGP Key: 0x90ECB270
Facebook  LinkedIn  Twitter

“It may be cognitive, but, it ain’t intuitive."
— Hogstrom
 
Unless stated otherwise above:
IBM United Kingdom Limited - Registered in England and Wales with number 741598.
Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU


Re: [VOTE] Require Multi-Factor Authentication for Committers to Zowe Projects in GitHub

Matt Hogstrom
 

Vote passes … all +1s with 

+1’s
Matt Hogstrom
Sean Grady
Jean-Philippe Linardon
Mark Ackert
Jean-Louis Vignaud

Petr Plavjanik
Michael Supak
Guilherme Cartier
Doug Ross
Vitek Vicek
Joe Winchester



Matt Hogstrom
matt@...
+1-919-656-0564
PGP Key: 0x90ECB270
Facebook  LinkedIn  Twitter

“It may be cognitive, but, it ain’t intuitive."
— Hogstrom

On Jun 12, 2019, at 3:16 PM, Matt Hogstrom via Lists.Openmainframeproject.Org <matt=hogstrom.org@...> wrote:

As discussed in the ZLC meeting security is a critical aspect for Zowe as it is in all projects.  To increase security all Committers (members of the Zowe organization in GitHub) should have multi-factor authentication enabled.

After July 17th those members of the community that have not enabled MFA in GitHub will have their write access suspended until their account is secured with MFA.

ZLC members have binding votes but all are welcome to express their view.

Please respond to this e-mail with
+1 - Approve
 0 - No opinon
-1 - Disagree (please respond with specific objections)


Matt Hogstrom
matt@...
+1-919-656-0564
PGP Key: 0x90ECB270
Facebook  LinkedIn  Twitter

“It may be cognitive, but, it ain’t intuitive."
— Hogstrom



Re: [VOTE] Require Multi-Factor Authentication for Committers to Zowe Projects in GitHub

Joe Winchester
 

+1
 
Joe Winchester
IBM z/OS Explorer Senior Technical Staff Member - Project Zowe Contributor zowe.org
 
Phone: 44-7749-965423
Twitter: @JoeWinchester    LinkedIn: joewinchester
E-mail: winchest@...
 
 
----- Original message -----
From: "Matt Hogstrom" <matt@...>
Sent by: zowe-user@...
To: zowe-zlc@...
Cc: zowe-user@..., zowe-dev@...
Subject: [zowe-user] [VOTE] Require Multi-Factor Authentication for Committers to Zowe Projects in GitHub
Date: Wed, Jun 12, 2019 8:16 PM
 
As discussed in the ZLC meeting security is a critical aspect for Zowe as it is in all projects.  To increase security all Committers (members of the Zowe organization in GitHub) should have multi-factor authentication enabled.
 
After July 17th those members of the community that have not enabled MFA in GitHub will have their write access suspended until their account is secured with MFA.
 
ZLC members have binding votes but all are welcome to express their view.
 
Please respond to this e-mail with
+1 - Approve
 0 - No opinon
-1 - Disagree (please respond with specific objections)
 

Matt Hogstrom
matt@...
+1-919-656-0564
PGP Key: 0x90ECB270
Facebook  LinkedIn  Twitter

“It may be cognitive, but, it ain’t intuitive."
— Hogstrom
 
Unless stated otherwise above:
IBM United Kingdom Limited - Registered in England and Wales with number 741598.
Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU


Re: [VOTE] Require Multi-Factor Authentication for Committers to Zowe Projects in GitHub

Matt Hogstrom
 

My +1 

Matt Hogstrom
matt@...
+1-919-656-0564
PGP Key: 0x90ECB270
Facebook  LinkedIn  Twitter

“It may be cognitive, but, it ain’t intuitive."
— Hogstrom

On Jun 12, 2019, at 3:16 PM, Matt Hogstrom <matt@...> wrote:

As discussed in the ZLC meeting security is a critical aspect for Zowe as it is in all projects.  To increase security all Committers (members of the Zowe organization in GitHub) should have multi-factor authentication enabled.

After July 17th those members of the community that have not enabled MFA in GitHub will have their write access suspended until their account is secured with MFA.

ZLC members have binding votes but all are welcome to express their view.

Please respond to this e-mail with
+1 - Approve
 0 - No opinon
-1 - Disagree (please respond with specific objections)


Matt Hogstrom
matt@...
+1-919-656-0564
PGP Key: 0x90ECB270
Facebook  LinkedIn  Twitter

“It may be cognitive, but, it ain’t intuitive."
— Hogstrom



Re: [zowe-zlc] [VOTE] Require Multi-Factor Authentication for Committers to Zowe Projects in GitHub

Jean-Louis Vignaud
 

+1

On Wed, Jun 12, 2019 at 9:16 PM Matt Hogstrom <matt@...> wrote:
As discussed in the ZLC meeting security is a critical aspect for Zowe as it is in all projects.  To increase security all Committers (members of the Zowe organization in GitHub) should have multi-factor authentication enabled.

After July 17th those members of the community that have not enabled MFA in GitHub will have their write access suspended until their account is secured with MFA.

ZLC members have binding votes but all are welcome to express their view.

Please respond to this e-mail with
+1 - Approve
 0 - No opinon
-1 - Disagree (please respond with specific objections)


Matt Hogstrom
matt@...
+1-919-656-0564
PGP Key: 0x90ECB270
Facebook  LinkedIn  Twitter

“It may be cognitive, but, it ain’t intuitive."
— Hogstrom



--
Jean-Louis Vignaud
Product Management
Broadcom, MF Business Division
+420 770 146 136


Re: [zowe-zlc] [VOTE] Require Multi-Factor Authentication for Committers to Zowe Projects in GitHub

Maciej_Serafin@...
 

+1


Re: [zowe-zlc] [VOTE] Require Multi-Factor Authentication for Committers to Zowe Projects in GitHub

Mark.Ackert@...
 

+1

On Wed, Jun 12, 2019 at 5:22 PM <jlinardon@...> wrote:

+1

 

Jean-Philippe Linardon

Director, Software Engineering

Rocket Software

77 Fourth Avenue • Waltham, MA • 02451 • USA

T: +1 781 684 2350 • E: jlinardon@... • W: www.rocketsoftware.com

 

From: zowe-zlc@... <zowe-zlc@...> On Behalf Of Matt Hogstrom via Lists.Openmainframeproject.Org
Sent: Wednesday, June 12, 2019 3:16 PM
To: zowe-zlc@...
Cc: zowe-user@...; zowe-dev@...
Subject: [zowe-zlc] [VOTE] Require Multi-Factor Authentication for Committers to Zowe Projects in GitHub

 

As discussed in the ZLC meeting security is a critical aspect for Zowe as it is in all projects.  To increase security all Committers (members of the Zowe organization in GitHub) should have multi-factor authentication enabled.

 

After July 17th those members of the community that have not enabled MFA in GitHub will have their write access suspended until their account is secured with MFA.

 

ZLC members have binding votes but all are welcome to express their view.

 

Please respond to this e-mail with

+1 - Approve

 0 - No opinon

-1 - Disagree (please respond with specific objections)

 


Matt Hogstrom
matt@...
+1-919-656-0564
PGP Key: 0x90ECB270
Facebook  LinkedIn  Twitter

“It may be cognitive, but, it ain’t intuitive."
— Hogstrom

 

================================
Rocket Software, Inc. and subsidiaries ■ 77 Fourth Avenue, Waltham MA 02451 ■ Main Office Toll Free Number: +1 855.577.4323
Contact Customer Support: https://my.rocketsoftware.com/RocketCommunity/RCEmailSupport
Unsubscribe from Marketing Messages/Manage Your Subscription Preferences - http://www.rocketsoftware.com/manage-your-email-preferences
Privacy Policy - http://www.rocketsoftware.com/company/legal/privacy-policy
================================

This communication and any attachments may contain confidential information of Rocket Software, Inc. All unauthorized use, disclosure or distribution is prohibited. If you are not the intended recipient, please notify Rocket Software immediately and destroy all copies of this communication. Thank you.


Re: [zowe-zlc] [VOTE] Require Multi-Factor Authentication for Committers to Zowe Projects in GitHub

jlinardon@...
 

+1

 

Jean-Philippe Linardon

Director, Software Engineering

Rocket Software

77 Fourth Avenue • Waltham, MA • 02451 • USA

T: +1 781 684 2350 • E: jlinardon@... • W: www.rocketsoftware.com

 

From: zowe-zlc@... <zowe-zlc@...> On Behalf Of Matt Hogstrom via Lists.Openmainframeproject.Org
Sent: Wednesday, June 12, 2019 3:16 PM
To: zowe-zlc@...
Cc: zowe-user@...; zowe-dev@...
Subject: [zowe-zlc] [VOTE] Require Multi-Factor Authentication for Committers to Zowe Projects in GitHub

 

As discussed in the ZLC meeting security is a critical aspect for Zowe as it is in all projects.  To increase security all Committers (members of the Zowe organization in GitHub) should have multi-factor authentication enabled.

 

After July 17th those members of the community that have not enabled MFA in GitHub will have their write access suspended until their account is secured with MFA.

 

ZLC members have binding votes but all are welcome to express their view.

 

Please respond to this e-mail with

+1 - Approve

 0 - No opinon

-1 - Disagree (please respond with specific objections)

 


Matt Hogstrom
matt@...
+1-919-656-0564
PGP Key: 0x90ECB270
Facebook  LinkedIn  Twitter

“It may be cognitive, but, it ain’t intuitive."
— Hogstrom

 

================================
Rocket Software, Inc. and subsidiaries ■ 77 Fourth Avenue, Waltham MA 02451 ■ Main Office Toll Free Number: +1 855.577.4323
Contact Customer Support: https://my.rocketsoftware.com/RocketCommunity/RCEmailSupport
Unsubscribe from Marketing Messages/Manage Your Subscription Preferences - http://www.rocketsoftware.com/manage-your-email-preferences
Privacy Policy - http://www.rocketsoftware.com/company/legal/privacy-policy
================================

This communication and any attachments may contain confidential information of Rocket Software, Inc. All unauthorized use, disclosure or distribution is prohibited. If you are not the intended recipient, please notify Rocket Software immediately and destroy all copies of this communication. Thank you.


[VOTE] Require Multi-Factor Authentication for Committers to Zowe Projects in GitHub

Matt Hogstrom
 

As discussed in the ZLC meeting security is a critical aspect for Zowe as it is in all projects.  To increase security all Committers (members of the Zowe organization in GitHub) should have multi-factor authentication enabled.

After July 17th those members of the community that have not enabled MFA in GitHub will have their write access suspended until their account is secured with MFA.

ZLC members have binding votes but all are welcome to express their view.

Please respond to this e-mail with
+1 - Approve
 0 - No opinon
-1 - Disagree (please respond with specific objections)


Matt Hogstrom
matt@...
+1-919-656-0564
PGP Key: 0x90ECB270
Facebook  LinkedIn  Twitter

“It may be cognitive, but, it ain’t intuitive."
— Hogstrom


Re: Zowe CLI profile data at rest

Sujay
 

Zowe CLI stores credentials in plain text. However, you don't need to always store your credentials in the CLI. Zowe CLI is able to accept credentials from other sources such as environment variables.

Using it from automation tools like Jenkins which has its own secure credential storage capability https://jenkins.io/doc/developer/security/secrets/ allows the CLI to consume secure credentials via environment variables.

In the case where you're using it from your laptop and you'd like to store your credentials securely, there are 3rd party plugins available for Zowe that accomplish this.

Thanks,

Sujay Solomon

Global Product Manager | Mainframe DevOps Advisor

Helping Enterprises Achieve Integrated Mainframe DevOps

Broadcom, Pittsburgh, PA


Zowe CLI profile data at rest

Morten Schiønning
 

Hi

 

I’m a security professional, working for an infrastructure provider for major financial institutions in Denmark. I’m tasked with doing a risk assessment (and subsequent security approval) of Zowe, and, as part of that, Zowe CLI.

 

I am reading through the documentation and learn that users can create profiles, saving them from retyping, among other things, username and password.

 

I am lacking a description of how that information is stored. Is it saved in a regular file? Is it in clear text? Please provide as many details as you can J

 

From what I can tell about the other aspects of operation of Zowe (and Zowe CLI) the culture around seems to be pretty security aware, so I keep my fingers crossed. J

 

Regards

 

Venlig hilsen

Morten Schiønning

Sikkerhedskonsulent, Security & Compliance

Direkte +45 6363 9394

Mobile +45 5179 4116

msc@...

”De dygtigste vinder sammen, stræber efter enkelhed, fokuseret på kundens bedste”

 

JN Data A/S

·

Havsteensvej 4

·

4000 Roskilde

Telefon 63 63 63 63/ Fax 63 63 63 64

www.jndata.dk

 

jndata_new1

 


ZLC Meeting for Wed @ 0900 ET

Matt Hogstrom
 

ZLC Agenda for 2019-05-15 at 0900 ET can be found here https://github.com/zowe/zlc/tree/2019-05-15

@Alvin Tan offered to help facilitate the meeting in my absence, thanks Alvin.



Matt Hogstrom
matt@...
+1-919-656-0564
PGP Key: 0x90ECB270
Facebook  LinkedIn  Twitter

“It may be cognitive, but, it ain’t intuitive."
— Hogstrom


Zowe Enterprise Installer Play-Forward

Tim Brooks
 

Mark Your Calendars - We want to hear from you!

When: Tuesday, April 23rd, 11am-Noon ET

What: Since Zowe was launched we have received a lot of community feedback regarding the current experience installing Zowe drivers. We’d like to present the community plans to improve the current solution and get more input on issues relating to installing, upgrading, extending distributions, service, support, packaging and runtime lifecycle.

Why: This will be of interest to anyone who has installed Zowe, is thinking of installing Zowe, and/or would like to contribute to helping us drive our install experience forward. Our end goal is to make the Zowe install, launch, and maintain experience comfortable and familiar to system programmers in the z/OS community. 

Additional Info:



Calendar Event Link: https://lists.openmainframeproject.org/g/zowe-dev/viewevent?eventid=469263&calstart=2019-04-23


Zoom Link
: https://zoom.us/my/zowe.onboarding


Re: Zowe Install Help

John Mertic
 

Adding the Zowe-user email list on CCing for the community to help chime in here.

Thank you,

John Mertic
Director of Program Management - Linux Foundation
ASWF, ODPi, and Open Mainframe Project
Schedule time with me at https://calendly.com/jmertic



On Fri, Apr 12, 2019 at 3:56 PM Prucker,Dylan S <DPRUCKER@...> wrote:

Hello,

I am with Travelers Insurance and we are currently in the process of trying to get Zowe installed in our testing environment. The main issue seems to be upon start up Zowe can’t get an instance for the apicatalog. The specific reoccurring error is as follows:

ERROR 84083301 --- Ý          main¨ c.c.m.a.s.i.InstanceRetrievalService     : An error occurred when trying to get instance info for:  apicatalog

 

I have posted a question to the github site with no resolve. I was wondering if there was a way were we could set up a webinar or I could get some direction as what may have occurred in the install process that caused this. Any insight would be much appreciated, we are eager to start using this tool. Thank you!

 

Best Regards,

 

Dylan Prucker |Technology Engineer

Travelers |1 Tower Sq, PB02

Hartford, CT 06183

P: (860) 954-3113

E: dprucker@...

 

 

 


This message (including any attachments) may contain confidential, proprietary, privileged and/or private information. The information is intended to be for the use of the individual or entity designated above. If you are not the intended recipient of this message, please notify the sender immediately, and delete the message and any attachments. Any disclosure, reproduction, distribution or other use of this message or any attachments by an individual or entity other than the intended recipient is prohibited.

TRVDiscDefault::1201


Zowe v1.1.0 Release

Tim Brooks
 

The Zowe community has just released v1.1.0. To learn about what's new, changed, removed and known issues visit the release notes here:
https://zowe.github.io/docs-site/latest/getting-started/summaryofchanges.html#version-1-1-0-april-2019

There will also be a community system demo scheduled for Monday, 4/8, from 9-10am ET. This demo is open to all interested parties and community members are encouraged to attend.
Add to your calendar here: https://lists.openmainframeproject.org/g/zowe-dev/viewevent?eventid=462628&calstart=2019-04-08

Congratulations to everyone who helped ship v1.1.0!


DevOps.com Zowe Webinar - Register Today!

Tim Brooks
 

John Mertic, the Director of Program Management for The Linux Foundation, Joe Winchester, Senior Technical Staff Member at IBM, and Rose Sakach, Product Manager at Broadcom,  will discuss the challenges and opportunities that led to the creation of the the Open Mainframe Project and the Zowe initiative.  Launched last August, Zowe is the first open source project based on z/OS and serves as an integration platform for the next generation of tools for administration, management and development on z/OS mainframes.

By utilizing new interfaces and an API mediation layer, enterprises can now more easily integrate rich mainframe resources and extend ‘API-first’ to the mainframe.

Click here to register.


Re: Zowe v1.0.0 Webinar

Tim Brooks
 

For anyone who was not able to attend the Zowe webinar last month, the Open Mainframe Project has posted the recording here (Zowe talks start at 11:45):

https://www.openmainframeproject.org/resources/videos

41 - 60 of 74