On Jul 8, 2019, at 10:30 AM, Matt Hogstrom via Lists.Openmainframeproject.Org <matt=hogstrom.org@...> wrote:

I wondered that last night as I was making the multi-repo changes.   I’ll create a PR for both and looks for a reviewer / approver.  Thanks for the suggestion John.  Welcome back from vacation.

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

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

On Jul 8, 2019, at 10:12 AM, John Mertic <jmertic@...> wrote:

Wondering if with all these docs in active development, should we consider merging the ZLC and community repos? That might help centralize process docs that impact all communities and reduce the repo sprawl that's happening.

Thoughts?

On Mon, Jul 8, 2019 at 10:06 AM Tim Brooks <tim.brooks@...> wrote:
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