-
Notifications
You must be signed in to change notification settings - Fork 14
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Future ZLC structure #220
Comments
In reviewing the ZLC description on zowe.org https://github.com/zowe/zlc it states a few things in need of update
I would like to propose with TSC creation we continue to approve incubators, work with OMP in not just marketing but recruiting new members and projects, work to outreach to other projects and any other ideas we want to document. I consider "release train" issues the scope of the TSC and should maybe also be the ones to revoke committer authority. Regarding ZLC members and voting
We can discuss in January but wanted to document some of the ideas here. |
Addition topic: term limits - also see on the zowe.org site: Note the members moving to TSC term limit in 2022 - those of use staying on ZLC have term limit of Feb 2021.....we need to discuss (and seek @jmertic advice on how to handle) ......do we vote for all new ZLC members (allowing current members to run again) or some other arrangement? |
Adding comments from ZLC meeting on Jan 6th
|
Zowe ZLC proposal 2021 Draft .pptx These slides are proposed modifications to the ZLC charter on the zowe.org web site |
Keeping proposals open for review - PR proposed by Bruce is here https://github.com/zowe/zlc/tree/armstro-patch-4 Peter proposal Bruce comments @pdubz3 to review/comment |
Adding my thoughts - please loop me in on the next call on this... |
ZAC Draft Charter - Consolidated Comments .docx Mike offered some times for working session - I am going to pick a hour that he and I have free and see if all can join |
Just a thought - I think there is agreement that ZLC/ZAC needs to "own" the issue for Zowe Support Conformance program (granted it could be a TSC item but ZLC/ZAC seems a fit) - I would like to dissect the issue as to why this issue is appropriate for ZLC/ZAC and use it as a case study ...I think it is a role beyond "advisory" to TSC .....is it the "business aspect" of conformance? the fact we already have 2 vendors offering support in the ZLC/ZAC ... |
Bruce, I think conformance for support offerings and distributions would ultimately be a joint effort. It involves the business aspect of creating the enterprise-grade experience for Zowe customers as well as the rules of engagement for support vendors which I believe to be non-technical details and within the domain of the ZAC. It also touches the specific details of the Zowe deliverables and how Zowe is acquired, installed, configured and maintained. The fact that we have two vendors already offering support shouldn't be relevant to the definition of conformance, although it's reasonable that it might influence some opinions. Having said that, it needs to be owned by one, not both. And I feel the ZAC is the appropriate owner. |
Seeing where this is at - I see the ZLC right now operating with good intentions, but without a solid swimlane. Let me know what I can do to help drive this forward. I recall the last discussions were transitioning the ZLC to more of a 'vendor advisory group' with participation driven by organizations with Zowe Conformant offerings and its role to advise the TSC and being a resource for the TSC in ensuring the project is in line with its downstream vendor ecosystem. I like @pdubz3 idea of letting this group be tasked with coordinating the establishment and evolution of the conformance program criteria for the TSC to approve - likely this group will be the right target audience. |
John - we want to close on the Support Conformance first and then revisit
the charter.....PI Planning and Incubators took up time in 1Q..... the TSC
has (I think) settled on their charter and there are a few things they ask
of the ZLC/ZAC that we need to sort out......
Bruce Armstrong
IBM Z Product Manager assigned to zowe.org
4205 S MIAMI BLVD, DURHAM NC 27703-9141
Email: ***@***.***
Tel: 919-254-8773
Cell: 919-931-3132
From: John Mertic ***@***.***>
To: zowe/zlc ***@***.***>
Cc: Bruce Armstrong ***@***.***>, Assign
***@***.***>
Date: 05/24/2021 10:55 AM
Subject: [EXTERNAL] Re: [zowe/zlc] Future ZLC structure (#220)
Seeing where this is at - I see the ZLC right now operating with good
intentions, but without a solid swimlane. Let me know what I can do to
help drive this forward. I recall the last discussions were transitioning
the ZLC to more of a 'vendor
Seeing where this is at - I see the ZLC right now operating with good
intentions, but without a solid swimlane. Let me know what I can do to
help drive this forward.
I recall the last discussions were transitioning the ZLC to more of a
'vendor advisory group' with participation driven by organizations with
Zowe Conformant offerings and its role to advise the TSC and being a
resource for the TSC in ensuring the project is in line with its
downstream vendor ecosystem. I like @pdubz3 idea of letting this group be
tasked with coordinating the establishment and evolution of the
conformance program criteria for the TSC to approve - likely this group
will be the right target audience.
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub, or unsubscribe.
|
OK - let's try to reboot the charter discussion - I think we start here to recall what is already out there I think we need to read TSC charter for positioning of ZLC/ZAC role We can discuss the word doc (I don't think a PR has been started)... ZAC Draft Charter - Consolidated Comments Reboot Jun 18 .docx
|
Document attached is merge of the existing TSC charter, Contributor File with roles (for reference) and CNCF Principles to be considered for Zowe principles Possible areas for ZLC (ZAC) to serve as advisors
|
ZAC.Draft.Charter - July 19 2021 .docx Much simpler ZAC Charter - topic for July 20 ZLC/ZAC call |
2021.July.Zowe.Quarterly.Webinar.Series.ZAC Overview .pptx Proposed summary of ZAC |
ZAC.Draft.Charter - July 20 2021 .docx Incorporating comments |
@jmertic above is proposed ZAC charter - question is what - if anything - do we need to do to sunset ZLC charter and related zowe.org content? |
Thanks Bruce - I'm reading the charter and struggling a bit with the concept of an "advisory" group having specific responsibilities or "owning" activities. I would have anticipated this group similar to a customer advisory council, which would be easy to convey as a model to the mainframe community and add more clear direction/focus. Happy to chat through this more. |
Hey @jmertic - I think you had asked where we were with the ZAC charter - I provided you this github info - let us finalize the proposal - it likely needs a little clean up and simplification. The "owning" activities is meaning action items assigned by TSC but maybe the word "owning" is not right term or we just need to say action items as agreed. We also need to figure out what to do with the zowe.org contents - there is a fair amount of content that is ZLC specific we need to remove and bridge to a simpler ZAC description. What do we need to do about changing the charter of ZLC to ZAC ? Is it necessary to vote on anything - either by the ZLC or the community at large? |
Got it - didn't realize the charter was still at an early stage. Transition-wise, I think messaging to the community on the transition should be sufficient; it might be good to have the TSC review and approve the plan for the ZAC as well. |
I made another version to address John's concerns and attach two copies - one showing what I changed and the other with all changes accepted. |
Peter, I reviewed your edits and they're good. I corrected two errors, one grammatical and one spelling (a typo). |
What is the state of this document? I had lots of feedback but want to be conscious of where things are at. |
I will ask in the ZLC/ZAC call today - I think we are done - next step is ask TSC to approve. We need to figure out how to update the zowe.org website - there are many references to ZLC .....I propose we provide an explanation of the name and mission change and strip out all the rest |
Got it - can we schedule time this week to walk through this more? |
Forgive me - I felt the need to beat the horse but a little bit more
I'd like to take this to TSC for approval and we work with TSC on updating zowe.org. To stress the role of "advisory" I will try to use the full term externally and try not to just say ZAC. DONE |
I think your new language is just right
From: Bruce Armstrong ***@***.***>
Sent: Wednesday, August 18, 2021 8:13 PM
To: zowe/zlc ***@***.***>
Cc: Peter Fandel ***@***.***>; Assign ***@***.***>
Subject: Re: [zowe/zlc] Future ZLC structure (#220)
EXTERNAL EMAIL
Forgive me - I felt the need to beat the horse but a little bit more
1. Softened the Product Management comment a little tiny bit to "The ZAC brings a product management perspective to the community and acts in cooperation with the others Zowe squads such as the Zowe Technical Steering Committee (TSC) and the Zowe Onboarding squad."
2. Added sub-bullet to explain "hill" (with link to SAFe methodology) in response to concern about being an insider term
3. Gave a few more words on Chair, Vice and Secretary
I'd like to take this to TSC for approval and we work with TSC on updating zowe.org. To stress the role of "advisory" I will try to use the full term externally and try not to just say ZAC.
DONE
ZAC.Draft.Charter.-.August.18.2021.docx<https://github.com/zowe/zlc/files/7010843/ZAC.Draft.Charter.-.August.18.2021.docx>
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub<#220 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AHBGVU4CSEENJOTX4LAFBFTT5REBNANCNFSM4UKL6ZTQ>.
Triage notifications on the go with GitHub Mobile for iOS<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android<https://play.google.com/store/apps/details?id=com.github.android&utm_campaign=notification-email>.
================================
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.
|
ZLC dead. Long live ZAC! |
done |
Two factors driving a rethink of the ZLC 1) term limits expiring for some ZLC members in Feb 2021 2) formation of TSC - assuming it is approved. https://github.com/zowe/zlc
Existing ZLC mission needs rethought as technical issues will be more the domain of the TSC. Assuming ZLC retains its more "business focus" priorities need to be set - possible closer work with OMP, reach out activities, incubators, more focus on new members, etc.
This item is to work out mission of ZLC for 2021
The text was updated successfully, but these errors were encountered: