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

E-mail: tim.brooks@...

Office: 919-254-2436

Mobile: 703-343-5030

 

Zowe.org

 

 

----- 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

 

Community Repo - https://github.com/zowe/community/tree/20190418-process-updates

ZLC Repo - https://github.com/zowe/zlc/tree/20190418-process-updates

 

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

 

 

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

+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.

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