Date   

Zowe Architecture Call (https://zoom.us/my/zowe.cicd) - Wed, 11/27/2019 #cal-notice

zowe-dev@lists.openmainframeproject.org Calendar <noreply@...>
 

Zowe Architecture Call (https://zoom.us/my/zowe.cicd)

When:
Wednesday, 27 November 2019
12:00pm to 1:00pm
(GMT-05:00) America/New York

Where:
https://zoom.us/my/zowe.cicd

Organizer:
kocsis@...

Description:

Zowe Architecture Callin Information:
https://zoom.us/my/zowe.cicd

Agenda:
- Add the topics you wish to discuss (along with date) to the agenda
https://wiki.zowe.org/display/ZOWE/Architecture+Call+Topics


Upcoming Event: Zowe Architecture Call (https://zoom.us/my/zowe.cicd) - Wed, 11/27/2019 12:00pm-1:00pm #cal-reminder

zowe-dev@lists.openmainframeproject.org Calendar <zowe-dev@...>
 

Reminder: Zowe Architecture Call (https://zoom.us/my/zowe.cicd)

When: Wednesday, 27 November 2019, 12:00pm to 1:00pm, (GMT-05:00) America/New York

Where:https://zoom.us/my/zowe.cicd

View Event

Organizer: kocsis@...

Description:

Zowe Architecture Callin Information:
https://zoom.us/my/zowe.cicd

Agenda:
- Add the topics you wish to discuss (along with date) to the agenda
https://wiki.zowe.org/display/ZOWE/Architecture+Call+Topics


Zowe ZLC meeting - Wed, 11/27/2019 #cal-notice

zowe-dev@lists.openmainframeproject.org Calendar <noreply@...>
 

Zowe ZLC meeting

When:
Wednesday, 27 November 2019
9:00am to 10:00am
(GMT-05:00) America/New York

Where:
https://zoom.us/j/935375531

Organizer:
matt@... +1-919-656-0564

Description:

Join from PC, Mac, Linux, iOS or Android: https://zoom.us/j/935375531

Or iPhone one-tap : US: +16699006833,,935375531# or +16465588656,,935375531# Or Telephone: Dial(for higher quality, dial a number based on your current location): US: +1 669 900 6833 or +1 646 558 8656 or +1 877 369 0926 (Toll Free) or +1 855 880 1246 (Toll Free) Meeting ID: 935 375 531 International numbers available: https://zoom.us/u/b1u8uCXIn


Upcoming Event: Zowe ZLC meeting - Wed, 11/27/2019 9:00am-10:00am #cal-reminder

zowe-dev@lists.openmainframeproject.org Calendar <zowe-dev@...>
 

Reminder: Zowe ZLC meeting

When: Wednesday, 27 November 2019, 9:00am to 10:00am, (GMT-05:00) America/New York

Where:https://zoom.us/j/935375531

View Event

Organizer: matt@... +1-919-656-0564

Description:

Join from PC, Mac, Linux, iOS or Android: https://zoom.us/j/935375531

Or iPhone one-tap : US: +16699006833,,935375531# or +16465588656,,935375531# Or Telephone: Dial(for higher quality, dial a number based on your current location): US: +1 669 900 6833 or +1 646 558 8656 or +1 877 369 0926 (Toll Free) or +1 855 880 1246 (Toll Free) Meeting ID: 935 375 531 International numbers available: https://zoom.us/u/b1u8uCXIn


Cupids Scrum - This squad works on issues related to installing, packaging, launching Zowe including SMP/E PTF and APAR delivery. - Wed, 11/27/2019 #cal-notice

zowe-dev@lists.openmainframeproject.org Calendar <noreply@...>
 

Cupids Scrum - This squad works on issues related to installing, packaging, launching Zowe including SMP/E PTF and APAR delivery.

When:
Wednesday, 27 November 2019
1:00pm to 1:30pm
(GMT+00:00) UTC

Where:
https://zoom.us/my/zowe.onboarding

Organizer:
winchest@... +447749965423

Description:
Cupids Scrum - This squad works on issues related to installing, packaging, launching Zowe including SMP/E PTF and APAR delivery.  
https://github.com/zowe/zowe-install-packaging#workspaces/community-5c93e02fa70b456d35b8f0ed/board?repos=145870120,151615191,155383451,144619729,144599701,144592776


Upcoming Event: Zowe ZLC meeting - Wed, 11/27/2019 9:00am-10:00am #cal-reminder

zowe-dev@lists.openmainframeproject.org Calendar <zowe-dev@...>
 

Reminder: Zowe ZLC meeting

When: Wednesday, 27 November 2019, 9:00am to 10:00am, (GMT-05:00) America/New York

Where:https://zoom.us/j/935375531

View Event

Organizer: matt@... +1-919-656-0564

Description:

Join from PC, Mac, Linux, iOS or Android: https://zoom.us/j/935375531

Or iPhone one-tap : US: +16699006833,,935375531# or +16465588656,,935375531# Or Telephone: Dial(for higher quality, dial a number based on your current location): US: +1 669 900 6833 or +1 646 558 8656 or +1 877 369 0926 (Toll Free) or +1 855 880 1246 (Toll Free) Meeting ID: 935 375 531 International numbers available: https://zoom.us/u/b1u8uCXIn


Upcoming Event: Cupids Scrum - This squad works on issues related to installing, packaging, launching Zowe including SMP/E PTF and APAR delivery. - Wed, 11/27/2019 1:00pm-1:30pm #cal-reminder

zowe-dev@lists.openmainframeproject.org Calendar <zowe-dev@...>
 

Reminder: Cupids Scrum - This squad works on issues related to installing, packaging, launching Zowe including SMP/E PTF and APAR delivery.

When: Wednesday, 27 November 2019, 1:00pm to 1:30pm, (GMT+00:00) UTC

Where:https://zoom.us/my/zowe.onboarding

View Event

Organizer: Joe Winchester winchest@... +447749965423

Description: Cupids Scrum - This squad works on issues related to installing, packaging, launching Zowe including SMP/E PTF and APAR delivery.  
https://github.com/zowe/zowe-install-packaging#workspaces/community-5c93e02fa70b456d35b8f0ed/board?repos=145870120,151615191,155383451,144619729,144599701,144592776


Re: Expiring project Giza dot org domain

Jack-Tiefeng Jia
 

Thanks a lot Dan for the explanations and the Artifactory token.
 
I attached a screenshot about the "Build with Parameters" option for Jenkins Pipeline. For a parameterized pipeline, we have this option to run the same code/pipeline but different input. In the screenshot, you can see, without changing github code, we can test any Zowe build and on any server. If we don't have this permission, we have to create a git commit and hardcode what zowe build to test and trigger the build. Since the test could be just one time run, the commit is useless for the code base. So if we can have the Build with Parameters permission, it's really convenient for the team, and avoid to create dummy commits.
 
 
And one more background is almost all our builds can be run as many times as user like. It won't create conflict in the Artifactory.
 
But we do have one build we wish it could be restricted, which is promote-publish build. We wish this build can only is started by CI/CD squad.
 
Thanks,
 
Jack (T.) Jia
Software Developer
IBM Z Management Software
IBM Systems

Phone: 1-905-413-3195
IBM

8200 Warden Ave
Markham, ON L6G 1C7
Canada
 
 

----- Original message -----
From: "Daniel Pono Takamori" <dtakamori@...>
Sent by: zowe-dev@...
To: Jack-Tiefeng Jia <Jack-Tiefeng.Jia@...>, zowe-dev@...
Cc: Andrew Grimberg <agrimberg@...>, John Mertic <jmertic@...>
Subject: [EXTERNAL] Re: [zowe-dev] Expiring project Giza dot org domain
Date: Mon, Nov 25, 2019 4:56 PM
 
Hey Jack and Team,
First note is about permission for starting/ editing jobs: 
Unfortunately on the production Jenkins we do not allow triggering of arbitrary jobs from the UI (or API as you noted). However, on jenkins.zowe.org/sandbox Jack and Mark are in a group that allows them to start jobs at will (without the dance of posting 'retry' or 'recheck' [0] in the comments on a Github PR). This group can be added to by filing a ticket on support.linuxfoundation.org [1].  Is this an integral part of the workflow _after_ jobs are merged somewhere?  (currently we don't allow that permission on the production Jenkins instances, but could look into options if this is a necessary feature).
Since you are one of the first projects using Pipelines, our usual workflow of using `jenkins-job-builder` [2] will need to be looked at and reconsidered to fit your needs.
Secondly, I'm going to rebuild the Jenkins builder nodes with the containers already in them to reduce the bandwidth/ time overhead of pulling them in.  We can update them when new containers are released, but in the meantime if you are building them from the same underlying bits, it'll drastically reduce the time spent fetching new layers.
Thirdly, I've responded on the ticket about the Artifactory token.
 
I apologize for not being more a part of the CI discussions; I've joined the zowe-dev list to track updates and feel free to reach out for how we can better help you in this process!
 
-Daniel Pono Takamori on behalf of LF CI/ Release Engineering
 
 
On Fri, Nov 22, 2019 at 11:36 AM Jack-Tiefeng Jia <Jack-Tiefeng.Jia@...> wrote:
John, for sure. Currently when we test the Jenkins Library, which is a gradle build, the test starts with gradle test command, it will try to test several functionalities in the library. It's generally integration tests since when the code runs under Jenkins, it may behave differently when we run under JRE. Jenkins pipeline workflow plugin will convert the code into CPS https://github.com/cloudbees/groovy-cps/blob/master/doc/cps-basics.md.
 
For each major functionality, we will create a test Jenkins job on-the-fly with Jenkinsfile, and/or start the build with different parameters. The job could be a simple Pipeline, or a Multibranch Pipeline depends on the feature the test case is testing. For multibranch pipeline, we will also trigger a scan job to find the branches.
 
With current LF Jenkins setup, we don't have these permissions:
- create a job on-the-fly (or through Jenkins API)
- start a scan on Multibranch Pipeline job (or through Jenkins API)
- start a job on Jenkins (or through Jenkins API)
- start a job with parameters on Jenkins (or through Jenkins API)
- delete the temporary test job when the test is done
 
So we have to figure other ways to perform the tests.
 
For the permission of starting a job with parameters on Jenkins, we do rely a lot on this with our own Jenkins. Few scenarios like:
- start a smoke test on any build we produced,
- or start a smoke test on a different testing server.
- parameters to decide if/how we want to release.
 
For all the permission limitations, I believe we can have workarounds, just not ideal. Like we have to create dummy branches/commits to the github to trigger a build. The dummy commits eventually will end up to many merging conflicts, which is minor but have to deal with. To create workaround on testing Jenkins Library, we will need to change a lot on the way how we start our test.
 
FYI, another workaround we have already added is building in docker containers. The Jenkins has docker support VM agent, but the agent is not reusable. We can start the container with the build, but every build it will need to download the base build image again.  For example, https://jenkins.zowe.org/job/zowe-docs-site/job/users%252Fjack%252Flf-jenkins/6/execution/node/8/log/. Currently the base image is 1.24G, which create extra overhead to the build and server traffic. We may be able to try to make the base image slightly smaller, but I think with JDK8 and node.js v8 or v12 pre-installed, it will be still about 600M to 900M.
 
Hope this explains the issues we are having.
 
Thanks,
 
Jack (T.) Jia
Software Developer
IBM Z Management Software
IBM Systems

Phone: 1-905-413-3195
IBM

8200 Warden Ave
Markham, ON L6G 1C7
Canada
 
 
----- Original message -----
From: "John Mertic" <jmertic@...>
Sent by: zowe-dev@...
To: zowe-dev@..., Andrew Grimberg <agrimberg@...>, Daniel Pono Takamori <dtakamori@...>
Cc:
Subject: [EXTERNAL] Re: [zowe-dev] Expiring project Giza dot org domain
Date: Fri, Nov 22, 2019 11:34 AM
 
Hey Jack!
 
Adding +Andrew Grimberg and +Daniel Pono Takamori to this thread...
 
I will keep investigating the possibilities of migrating everything to LF Jenkins. One difficulty we have is the "Jenkins Library" build which will fail on LF Jenkins due to the permission limitation we have. Will see what we can do. The tests for Jenkins Library code is suggested because if it fails, it may indicate every other builds using that branch will fail. The test has to be performed against a real Jenkins server, not a virtual JVM environment because Jenkins handles Groovy scripts differently. The way of testing Jenkins Library is it will try to create a job through Jenkins API and start the build and check result, which is against the permission scheme we have on LF Jenkins.
 
Can you elaborate on the permissions issues? I thought we had built the environment to align with the existing practices, but wondering if something changed from discovery to implementation.
 
Thanks!
 
John

 

 

 
 


Re: Expiring project Giza dot org domain

Jack-Tiefeng Jia
 

Thanks a lot Dan for the explanations and the Artifactory token.
 
I attached a screenshot about the "Build with Parameters" option for Jenkins Pipeline. For a parameterized pipeline, we have this option to run the same code/pipeline but different input. In the screenshot, you can see, without changing github code, we can test any Zowe build and on any server. If we don't have this permission, we have to create a git commit and hardcode what zowe build to test and trigger the build. Since the test could be just one time run, the commit is useless for the code base. So if we can have the Build with Parameters permission, it's really convenient for the team, and avoid to create dummy commits.
 
 
And one more background is almost all our builds can be run as many times as user like. It won't create conflict in the Artifactory.
 
But we do have one build we wish it could be restricted, which is promote-publish build. We wish this build can only is started by CI/CD squad.
 
 
Regards,
 
Jack (T.) Jia
Software Developer
IBM Z Management Software
IBM Systems

Phone: 1-905-413-3195
IBM

8200 Warden Ave
Markham, ON L6G 1C7
Canada
 
 

----- Original message -----
From: "Daniel Pono Takamori" <dtakamori@...>
Sent by: zowe-dev@...
To: Jack-Tiefeng Jia <Jack-Tiefeng.Jia@...>, zowe-dev@...
Cc: Andrew Grimberg <agrimberg@...>, John Mertic <jmertic@...>
Subject: [EXTERNAL] Re: [zowe-dev] Expiring project Giza dot org domain
Date: Mon, Nov 25, 2019 4:56 PM
 
Hey Jack and Team,
First note is about permission for starting/ editing jobs: 
Unfortunately on the production Jenkins we do not allow triggering of arbitrary jobs from the UI (or API as you noted). However, on jenkins.zowe.org/sandbox Jack and Mark are in a group that allows them to start jobs at will (without the dance of posting 'retry' or 'recheck' [0] in the comments on a Github PR). This group can be added to by filing a ticket on support.linuxfoundation.org [1].  Is this an integral part of the workflow _after_ jobs are merged somewhere?  (currently we don't allow that permission on the production Jenkins instances, but could look into options if this is a necessary feature).
Since you are one of the first projects using Pipelines, our usual workflow of using `jenkins-job-builder` [2] will need to be looked at and reconsidered to fit your needs.
Secondly, I'm going to rebuild the Jenkins builder nodes with the containers already in them to reduce the bandwidth/ time overhead of pulling them in.  We can update them when new containers are released, but in the meantime if you are building them from the same underlying bits, it'll drastically reduce the time spent fetching new layers.
Thirdly, I've responded on the ticket about the Artifactory token.
 
I apologize for not being more a part of the CI discussions; I've joined the zowe-dev list to track updates and feel free to reach out for how we can better help you in this process!
 
-Daniel Pono Takamori on behalf of LF CI/ Release Engineering
 
 
On Fri, Nov 22, 2019 at 11:36 AM Jack-Tiefeng Jia <Jack-Tiefeng.Jia@...> wrote:
John, for sure. Currently when we test the Jenkins Library, which is a gradle build, the test starts with gradle test command, it will try to test several functionalities in the library. It's generally integration tests since when the code runs under Jenkins, it may behave differently when we run under JRE. Jenkins pipeline workflow plugin will convert the code into CPS https://github.com/cloudbees/groovy-cps/blob/master/doc/cps-basics.md.
 
For each major functionality, we will create a test Jenkins job on-the-fly with Jenkinsfile, and/or start the build with different parameters. The job could be a simple Pipeline, or a Multibranch Pipeline depends on the feature the test case is testing. For multibranch pipeline, we will also trigger a scan job to find the branches.
 
With current LF Jenkins setup, we don't have these permissions:
- create a job on-the-fly (or through Jenkins API)
- start a scan on Multibranch Pipeline job (or through Jenkins API)
- start a job on Jenkins (or through Jenkins API)
- start a job with parameters on Jenkins (or through Jenkins API)
- delete the temporary test job when the test is done
 
So we have to figure other ways to perform the tests.
 
For the permission of starting a job with parameters on Jenkins, we do rely a lot on this with our own Jenkins. Few scenarios like:
- start a smoke test on any build we produced,
- or start a smoke test on a different testing server.
- parameters to decide if/how we want to release.
 
For all the permission limitations, I believe we can have workarounds, just not ideal. Like we have to create dummy branches/commits to the github to trigger a build. The dummy commits eventually will end up to many merging conflicts, which is minor but have to deal with. To create workaround on testing Jenkins Library, we will need to change a lot on the way how we start our test.
 
FYI, another workaround we have already added is building in docker containers. The Jenkins has docker support VM agent, but the agent is not reusable. We can start the container with the build, but every build it will need to download the base build image again.  For example, https://jenkins.zowe.org/job/zowe-docs-site/job/users%252Fjack%252Flf-jenkins/6/execution/node/8/log/. Currently the base image is 1.24G, which create extra overhead to the build and server traffic. We may be able to try to make the base image slightly smaller, but I think with JDK8 and node.js v8 or v12 pre-installed, it will be still about 600M to 900M.
 
Hope this explains the issues we are having.
 
Thanks,
 
Jack (T.) Jia
Software Developer
IBM Z Management Software
IBM Systems

Phone: 1-905-413-3195
IBM

8200 Warden Ave
Markham, ON L6G 1C7
Canada
 
 
----- Original message -----
From: "John Mertic" <jmertic@...>
Sent by: zowe-dev@...
To: zowe-dev@..., Andrew Grimberg <agrimberg@...>, Daniel Pono Takamori <dtakamori@...>
Cc:
Subject: [EXTERNAL] Re: [zowe-dev] Expiring project Giza dot org domain
Date: Fri, Nov 22, 2019 11:34 AM
 
Hey Jack!
 
Adding +Andrew Grimberg and +Daniel Pono Takamori to this thread...
 
I will keep investigating the possibilities of migrating everything to LF Jenkins. One difficulty we have is the "Jenkins Library" build which will fail on LF Jenkins due to the permission limitation we have. Will see what we can do. The tests for Jenkins Library code is suggested because if it fails, it may indicate every other builds using that branch will fail. The test has to be performed against a real Jenkins server, not a virtual JVM environment because Jenkins handles Groovy scripts differently. The way of testing Jenkins Library is it will try to create a job through Jenkins API and start the build and check result, which is against the permission scheme we have on LF Jenkins.
 
Can you elaborate on the permissions issues? I thought we had built the environment to align with the existing practices, but wondering if something changed from discovery to implementation.
 
Thanks!
 
John

 

 

 
 


Re: Zowe code

John Mertic
 

Hi Tom!

Adding the +zowe-dev@... list for more context here. I'll also send you a note separately around the Zowe Conformance Program in case you wish to participate.

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 Mon, Nov 25, 2019 at 4:27 PM Tom Williamson <tom@...> wrote:

Hello,

 

I am looking at adding code in our products to support Zowe.

 

In the doc it says: These resources are usually represented in the form of JSON or XML documents. The preferred documentation type in Zowe™ is in the JSON format.

 

Does this mean that zowe can handle data in XML format or does it require JSON?

 

I have a general Alexa interface working.  We will do a demo at the next Share.

 

Thanks

Tom

 

 

 


Upcoming Event: CI/CD Squad Scrum (https://zoom.us/my/zowe.cicd) - Tue, 11/26/2019 11:00am-12:00pm #cal-reminder

zowe-dev@lists.openmainframeproject.org Calendar <zowe-dev@...>
 

Reminder: CI/CD Squad Scrum (https://zoom.us/my/zowe.cicd)

When: Tuesday, 26 November 2019, 11:00am to 12:00pm, (GMT-05:00) America/New York

Where:https://zoom.us/my/zowe.cicd

View Event

Organizer: kocsis@...

Description: CI/CD Squad Scrum (https://zoom.us/my/zowe.cicd)


Upcoming Event: Zowe ZLC meeting - Wed, 11/27/2019 9:00am-10:00am #cal-reminder

zowe-dev@lists.openmainframeproject.org Calendar <zowe-dev@...>
 

Reminder: Zowe ZLC meeting

When: Wednesday, 27 November 2019, 9:00am to 10:00am, (GMT-05:00) America/New York

Where:https://zoom.us/j/935375531

View Event

Organizer: matt@... +1-919-656-0564

Description:

Join from PC, Mac, Linux, iOS or Android: https://zoom.us/j/935375531

Or iPhone one-tap : US: +16699006833,,935375531# or +16465588656,,935375531# Or Telephone: Dial(for higher quality, dial a number based on your current location): US: +1 669 900 6833 or +1 646 558 8656 or +1 877 369 0926 (Toll Free) or +1 855 880 1246 (Toll Free) Meeting ID: 935 375 531 International numbers available: https://zoom.us/u/b1u8uCXIn


Cancelled Event: Core - Web UI meeting - Friday, 29 November 2019 #cal-cancelled

zowe-dev@lists.openmainframeproject.org Calendar <zowe-dev@...>
 

Cancelled: Core - Web UI meeting

This event has been cancelled.

When:
Friday, 29 November 2019
9:00am to 10:00am
(UTC-05:00) America/New York

Where:
https://zoom.us/j/226432549

Organizer: nrogers@...; sgrady@...; jlinardon@...

Description:
This is a recurring working meeting. Format and content to be determined by the squad and adjusted as necessary.

Possible content includes:

  1. Status review
  2. Roadmap discussion
  3. Technical conversations
  4. Q&A


Re: Expiring project Giza dot org domain

Daniel Pono Takamori
 

Hey Jack and Team,
First note is about permission for starting/ editing jobs: 
Unfortunately on the production Jenkins we do not allow triggering of arbitrary jobs from the UI (or API as you noted). However, on jenkins.zowe.org/sandbox Jack and Mark are in a group that allows them to start jobs at will (without the dance of posting 'retry' or 'recheck' [0] in the comments on a Github PR). This group can be added to by filing a ticket on support.linuxfoundation.org [1].  Is this an integral part of the workflow _after_ jobs are merged somewhere?  (currently we don't allow that permission on the production Jenkins instances, but could look into options if this is a necessary feature).
Since you are one of the first projects using Pipelines, our usual workflow of using `jenkins-job-builder` [2] will need to be looked at and reconsidered to fit your needs.
Secondly, I'm going to rebuild the Jenkins builder nodes with the containers already in them to reduce the bandwidth/ time overhead of pulling them in.  We can update them when new containers are released, but in the meantime if you are building them from the same underlying bits, it'll drastically reduce the time spent fetching new layers.
Thirdly, I've responded on the ticket about the Artifactory token.

I apologize for not being more a part of the CI discussions; I've joined the zowe-dev list to track updates and feel free to reach out for how we can better help you in this process!

-Daniel Pono Takamori on behalf of LF CI/ Release Engineering


On Fri, Nov 22, 2019 at 11:36 AM Jack-Tiefeng Jia <Jack-Tiefeng.Jia@...> wrote:
John, for sure. Currently when we test the Jenkins Library, which is a gradle build, the test starts with gradle test command, it will try to test several functionalities in the library. It's generally integration tests since when the code runs under Jenkins, it may behave differently when we run under JRE. Jenkins pipeline workflow plugin will convert the code into CPS https://github.com/cloudbees/groovy-cps/blob/master/doc/cps-basics.md.
 
For each major functionality, we will create a test Jenkins job on-the-fly with Jenkinsfile, and/or start the build with different parameters. The job could be a simple Pipeline, or a Multibranch Pipeline depends on the feature the test case is testing. For multibranch pipeline, we will also trigger a scan job to find the branches.
 
With current LF Jenkins setup, we don't have these permissions:
- create a job on-the-fly (or through Jenkins API)
- start a scan on Multibranch Pipeline job (or through Jenkins API)
- start a job on Jenkins (or through Jenkins API)
- start a job with parameters on Jenkins (or through Jenkins API)
- delete the temporary test job when the test is done
 
So we have to figure other ways to perform the tests.
 
For the permission of starting a job with parameters on Jenkins, we do rely a lot on this with our own Jenkins. Few scenarios like:
- start a smoke test on any build we produced,
- or start a smoke test on a different testing server.
- parameters to decide if/how we want to release.
 
For all the permission limitations, I believe we can have workarounds, just not ideal. Like we have to create dummy branches/commits to the github to trigger a build. The dummy commits eventually will end up to many merging conflicts, which is minor but have to deal with. To create workaround on testing Jenkins Library, we will need to change a lot on the way how we start our test.
 
FYI, another workaround we have already added is building in docker containers. The Jenkins has docker support VM agent, but the agent is not reusable. We can start the container with the build, but every build it will need to download the base build image again.  For example, https://jenkins.zowe.org/job/zowe-docs-site/job/users%252Fjack%252Flf-jenkins/6/execution/node/8/log/. Currently the base image is 1.24G, which create extra overhead to the build and server traffic. We may be able to try to make the base image slightly smaller, but I think with JDK8 and node.js v8 or v12 pre-installed, it will be still about 600M to 900M.
 
Hope this explains the issues we are having.
 
Thanks,
 
Jack (T.) Jia
Software Developer
IBM Z Management Software
IBM Systems

Phone: 1-905-413-3195
IBM

8200 Warden Ave
Markham, ON L6G 1C7
Canada
 
 
----- Original message -----
From: "John Mertic" <jmertic@...>
Sent by: zowe-dev@...
To: zowe-dev@..., Andrew Grimberg <agrimberg@...>, Daniel Pono Takamori <dtakamori@...>
Cc:
Subject: [EXTERNAL] Re: [zowe-dev] Expiring project Giza dot org domain
Date: Fri, Nov 22, 2019 11:34 AM
 
Hey Jack!
 
Adding +Andrew Grimberg and +Daniel Pono Takamori to this thread...
 
I will keep investigating the possibilities of migrating everything to LF Jenkins. One difficulty we have is the "Jenkins Library" build which will fail on LF Jenkins due to the permission limitation we have. Will see what we can do. The tests for Jenkins Library code is suggested because if it fails, it may indicate every other builds using that branch will fail. The test has to be performed against a real Jenkins server, not a virtual JVM environment because Jenkins handles Groovy scripts differently. The way of testing Jenkins Library is it will try to create a job through Jenkins API and start the build and check result, which is against the permission scheme we have on LF Jenkins.
 
Can you elaborate on the permissions issues? I thought we had built the environment to align with the existing practices, but wondering if something changed from discovery to implementation.
 
Thanks!
 
John

 

 

 


Re: NOMINATIONS OPEN: ZLC Voting seat

Peter Haumer
 

+1 Joe Winchester



Thanks and best regards,
Peter Haumer.

______________________________________________________________

PETER HAUMER, Dr. rer. nat.
IBM zSystems Software
______________________________________________________________

"Onno Van den Troost" ---11/25/2019 08:53:23 AM---+1 Joe Winchester Onno Van den Troost

From: "Onno Van den Troost" <onno@...>
To: zowe-dev@...
Date: 11/25/2019 08:53 AM
Subject: [EXTERNAL] Re: [zowe-dev] NOMINATIONS OPEN: ZLC Voting seat
Sent by: zowe-dev@...





+1 Joe Winchester


Onno Van den Troost
z/OS specialist for Developer for z/OS
IBM z Systems
[+1] (720) 342-6760
onno@...


"Murali Panchalingam" ---11/25/2019 11:16:43 AM---+1 Joe Winchester ______________________________________________

From:
"Murali Panchalingam" <panchali@...>
To:
zowe-dev@...
Date:
11/25/2019 11:16 AM
Subject:
[EXTERNAL] Re: [zowe-dev] NOMINATIONS OPEN: ZLC Voting seat
Sent by:
zowe-dev@...





+1 Joe Winchester



______________________________________________
Murali Panchalingam
Software Development Manager
IBM Systems | zSystems Software
Hursley Park, Winchester, SO21 2JN
United Kingdom
IBM United Kingdom Limited

panchali@...




From:
"John Davies" <daviesja@...>
To:
zowe-dev@...
Date:
25/11/2019 16:03
Subject:
[EXTERNAL] Re: [zowe-dev] NOMINATIONS OPEN: ZLC Voting seat
Sent by:
zowe-dev@...




Hello,

I too wish to nominate Joe Winchester.

Regards,

John A Davies, z/OS IBM Systems | zSystems Software, Hursley, UK. Tel 37245623. (+)44 (0)1962 815623. daviesja@...

"If you don't know how much of your code has been tested, why are you releasing it?" Ask me about code coverage or click on this link
Code coverage on IBM Connections




From:
"John Mertic" <jmertic@...>
To:
zowe-zlc@..., zowe-dev@..., zowe-user@...
Date:
25/11/2019 14:44
Subject:
[EXTERNAL] Re: [zowe-dev] NOMINATIONS OPEN: ZLC Voting seat
Sent by:
zowe-dev@...




Friendly reminder that nominations for the ZLC seat close TODAY at 11:59pm US Eastern Time.

Thank you,

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



On Mon, Nov 18, 2019 at 4:30 PM John Mertic <jmertic@...> wrote:
Zowe Community,

As the vast majority of the Zowe Community is in favor of replacing the open seat on the ZLC, I'd like to formally open the nomination and election period.

Based on the ZLC structure and processes ( see https://github.com/zowe/zlc/blob/master/process/structure.md ), I'd like to propose the following schedule for the election:

TODAY: Call for Nominations, email all Zowe project committers
11/25: Nominations close, 11:59pm ET
11/27: Voting period opens, all current Zowe project committers vote, vote by electronic mail or CIVS as appropriate
12/4: Voting period ends, 11:59pm ET
12/6: Election results announced

We have one nomination already received for Joe Winchester. If you would like to nominate someone else or nominate yourself, please email your name and rationale for serving on the ZLC to me by 11/25 at 11:59pm ET. Note that in order to serve on the ZLC, you must be a Zowe Committer.

Thank you,

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



---------- Forwarded message ---------
From: John Mertic <jmertic@...>
Date: Thu, Nov 7, 2019 at 12:47 PM
Subject: Re: [zowe-user] Change in ZLC Composition
To: <zowe-user@...>
Cc: <zowe-zlc@...>, <zowe-dev@...>


Zowe Community,

First and foremost, I would personally like to thank Matt for his service on the ZLC. There has been amazing progress in year 1 of Zowe which Matt has spearheaded, and his leadership has set the tone for the way the community will continue to grow in years to come.

The ZLC had a discussion yesterday on next steps with backfilling this seat, in light of the ZLC structure and processes ( see https://github.com/zowe/zlc/blob/master/process/structure.md ), and came up with two possible steps forward...

1) Immediately hold an election to backfill Matt's seat per the guidelines established ( https://github.com/zowe/zlc/blob/master/process/structure.md#composition ) with the term of this seat to be through the planned elections for the full ZLCin early January.
2) Start the process of the full ZLC re-election now, with the terms effective 1/1/2020 and the 1 year seats effective through 12/31/2020 and the 2 year seats effective through 12/31/2021.

The ZLC wanted community feedback on the way to proceed. Please share your preference on the approach on this thread. The ZLC would like to wrap up the discussion by the end of next week ( 11/15/2019 ) and then will discuss a plan for next steps at the subsequent ZLC meeting.

Let me know of any questions or concerns you might have.

Thank you,

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



On Thu, Nov 7, 2019 at 10:52 AM Matt Hogstrom <matt@...> wrote:

I have had a shift in responsibilities for my day job and as such have not been able to attend to Zowe as much as I think I should be commensurate with my responsibilities. As such, I’m stepping down from the ZLC; but not from Zowe.

The momentum for what the community is creating is palpable. Customers are now asking for it to do their own internal development, products are using it and we’ve made substantial progress over the past few years from incubator to open source to a critical part of product offerings and customer consumption. I’m honored to work with giants such as yourself.

One of the activities that needs to be done is to replace my seat on the ZLC. For consideration, I’d like to nominate Joe Winchester for that role. He is active in the community, driving critical work for packaging via CUPIDS and is the goto guy for so many things Zowe.

John Mertic will help to facilitate the process.

Again, thanks so much. You are all fantastic to work alongside.

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




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: NOMINATIONS OPEN: ZLC Voting seat

Onno Van den Troost
 

+1 Joe Winchester


Onno Van den Troost
z/OS specialist for Developer for z/OS
IBM z Systems
[+1] (720) 342-6760
onno@...


"Murali Panchalingam" ---11/25/2019 11:16:43 AM---+1 Joe Winchester ______________________________________________

From: "Murali Panchalingam" <panchali@...>
To: zowe-dev@...
Date: 11/25/2019 11:16 AM
Subject: [EXTERNAL] Re: [zowe-dev] NOMINATIONS OPEN: ZLC Voting seat
Sent by: zowe-dev@...






+1 Joe Winchester



______________________________________________
Murali Panchalingam
Software Development Manager
IBM Systems | zSystems Software
Hursley Park, Winchester, SO21 2JN
United Kingdom
IBM United Kingdom Limited

panchali@...




From:
"John Davies" <daviesja@...>
To:
zowe-dev@...
Date:
25/11/2019 16:03
Subject:
[EXTERNAL] Re: [zowe-dev] NOMINATIONS OPEN: ZLC Voting seat
Sent by:
zowe-dev@...




Hello,

I too wish to nominate Joe Winchester.

Regards,

John A Davies, z/OS IBM Systems | zSystems Software, Hursley, UK. Tel 37245623. (+)44 (0)1962 815623. daviesja@...

"If you don't know how much of your code has been tested, why are you releasing it?" Ask me about code coverage or click on this link
Code coverage on IBM Connections




From:
"John Mertic" <jmertic@...>
To:
zowe-zlc@..., zowe-dev@..., zowe-user@...
Date:
25/11/2019 14:44
Subject:
[EXTERNAL] Re: [zowe-dev] NOMINATIONS OPEN: ZLC Voting seat
Sent by:
zowe-dev@...




Friendly reminder that nominations for the ZLC seat close TODAY at 11:59pm US Eastern Time.

Thank you,

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



On Mon, Nov 18, 2019 at 4:30 PM John Mertic <jmertic@...> wrote:
Zowe Community,

As the vast majority of the Zowe Community is in favor of replacing the open seat on the ZLC, I'd like to formally open the nomination and election period.

Based on the ZLC structure and processes ( see https://github.com/zowe/zlc/blob/master/process/structure.md ), I'd like to propose the following schedule for the election:

TODAY: Call for Nominations, email all Zowe project committers
11/25: Nominations close, 11:59pm ET
11/27: Voting period opens, all current Zowe project committers vote, vote by electronic mail or CIVS as appropriate
12/4: Voting period ends, 11:59pm ET
12/6: Election results announced

We have one nomination already received for Joe Winchester. If you would like to nominate someone else or nominate yourself, please email your name and rationale for serving on the ZLC to me by 11/25 at 11:59pm ET. Note that in order to serve on the ZLC, you must be a Zowe Committer.

Thank you,

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



---------- Forwarded message ---------
From: John Mertic <jmertic@...>
Date: Thu, Nov 7, 2019 at 12:47 PM
Subject: Re: [zowe-user] Change in ZLC Composition
To: <zowe-user@...>
Cc: <zowe-zlc@...>, <zowe-dev@...>


Zowe Community,

First and foremost, I would personally like to thank Matt for his service on the ZLC. There has been amazing progress in year 1 of Zowe which Matt has spearheaded, and his leadership has set the tone for the way the community will continue to grow in years to come.

The ZLC had a discussion yesterday on next steps with backfilling this seat, in light of the ZLC structure and processes ( see https://github.com/zowe/zlc/blob/master/process/structure.md ), and came up with two possible steps forward...

1) Immediately hold an election to backfill Matt's seat per the guidelines established ( https://github.com/zowe/zlc/blob/master/process/structure.md#composition ) with the term of this seat to be through the planned elections for the full ZLCin early January.
2) Start the process of the full ZLC re-election now, with the terms effective 1/1/2020 and the 1 year seats effective through 12/31/2020 and the 2 year seats effective through 12/31/2021.

The ZLC wanted community feedback on the way to proceed. Please share your preference on the approach on this thread. The ZLC would like to wrap up the discussion by the end of next week ( 11/15/2019 ) and then will discuss a plan for next steps at the subsequent ZLC meeting.

Let me know of any questions or concerns you might have.

Thank you,

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



On Thu, Nov 7, 2019 at 10:52 AM Matt Hogstrom <matt@...> wrote:

I have had a shift in responsibilities for my day job and as such have not been able to attend to Zowe as much as I think I should be commensurate with my responsibilities. As such, I’m stepping down from the ZLC; but not from Zowe.

The momentum for what the community is creating is palpable. Customers are now asking for it to do their own internal development, products are using it and we’ve made substantial progress over the past few years from incubator to open source to a critical part of product offerings and customer consumption. I’m honored to work with giants such as yourself.

One of the activities that needs to be done is to replace my seat on the ZLC. For consideration, I’d like to nominate Joe Winchester for that role. He is active in the community, driving critical work for packaging via CUPIDS and is the goto guy for so many things Zowe.

John Mertic will help to facilitate the process.

Again, thanks so much. You are all fantastic to work alongside.

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




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: NOMINATIONS OPEN: ZLC Voting seat

murali panchalingam
 


+1 Joe Winchester




______________________________________________

Murali Panchalingam
Software Development Manager
IBM Systems | zSystems Software
Hursley Park, Winchester, SO21 2JN
United Kingdom
IBM United Kingdom Limited

panchali@...





From:        "John Davies" <daviesja@...>
To:        zowe-dev@...
Date:        25/11/2019 16:03
Subject:        [EXTERNAL] Re: [zowe-dev] NOMINATIONS OPEN: ZLC Voting seat
Sent by:        zowe-dev@...




Hello,

I too wish to nominate
Joe Winchester.

Regards,

John A Davies, z/OS
IBM Systems | zSystems Software, Hursley, UK. Tel 37245623.  (+)44 (0)1962 815623.  daviesja@...

"If you don't know how much of your code has been tested, why are you releasing it?"  Ask me about code coverage or click on this link

Code coverage on IBM Connections




From:        
"John Mertic" <jmertic@...>
To:        
zowe-zlc@..., zowe-dev@..., zowe-user@...
Date:        
25/11/2019 14:44
Subject:        
[EXTERNAL] Re: [zowe-dev] NOMINATIONS OPEN: ZLC Voting seat
Sent by:        
zowe-dev@...




Friendly reminder that nominations for the ZLC seat close TODAY at 11:59pm US Eastern Time.

Thank you,

John Mertic
Director of Program Management - Linux Foundation
ASWF, ODPi, and Open Mainframe Project

jmertic@...
+1 234-738-4571
Schedule time with me at
https://calendly.com/jmertic



On Mon, Nov 18, 2019 at 4:30 PM John Mertic <jmertic@...> wrote:
Zowe Community,

As the vast majority of the Zowe Community is in favor of replacing the open seat on the ZLC, I'd like to formally open the nomination and election period.  

Based on the ZLC structure and processes ( see
https://github.com/zowe/zlc/blob/master/process/structure.md ), I'd like to propose the following schedule for the election:

TODAY: Call for Nominations, email all Zowe project committers
11/25: Nominations close, 11:59pm ET
11/27: Voting period opens, all current Zowe project committers vote, vote by electronic mail or CIVS as appropriate
12/4: Voting period ends, 11:59pm ET
12/6: Election results announced  

We have one nomination already received for Joe Winchester. If you would like to nominate someone else or nominate yourself, please email your name and rationale for serving on the ZLC to me by 11/25 at 11:59pm ET. Note that in order to serve on the ZLC, you must be a Zowe Committer.

Thank you,

John Mertic
Director of Program Management - Linux Foundation
ASWF, ODPi, and Open Mainframe Project

jmertic@...
+1 234-738-4571
Schedule time with me at
https://calendly.com/jmertic



---------- Forwarded message ---------
From: John Mertic <
jmertic@...>
Date: Thu, Nov 7, 2019 at 12:47 PM
Subject: Re: [zowe-user] Change in ZLC Composition
To: <
zowe-user@...>
Cc: <
zowe-zlc@...>, <zowe-dev@...>


Zowe Community,

First and foremost, I would personally like to thank Matt for his service on the ZLC. There has been amazing progress in year 1 of Zowe which Matt has spearheaded, and his leadership has set the tone for the way the community will continue to grow in years to come.

The ZLC had a discussion yesterday on next steps with backfilling this seat, in light of the ZLC structure and processes ( see
https://github.com/zowe/zlc/blob/master/process/structure.md ), and came up with two possible steps forward...

1) Immediately hold an election to backfill Matt's seat per the guidelines established (
https://github.com/zowe/zlc/blob/master/process/structure.md#composition ) with the term of this seat to be through the planned elections for the full ZLCin early January.
2) Start the process of the full ZLC re-election now, with the terms effective 1/1/2020 and the 1 year seats effective through 12/31/2020 and the 2 year seats effective through 12/31/2021.

The ZLC wanted community feedback on the way to proceed. Please share your preference on the approach on this thread. The ZLC would like to wrap up the discussion by the end of next week ( 11/15/2019 ) and then will discuss a plan for next steps at the subsequent ZLC meeting.

Let me know of any questions or concerns you might have.

Thank you,

John Mertic
Director of Program Management - Linux Foundation
ASWF, ODPi, and Open Mainframe Project

jmertic@...
+1 234-738-4571
Schedule time with me at
https://calendly.com/jmertic



On Thu, Nov 7, 2019 at 10:52 AM Matt Hogstrom <
matt@...> wrote:


I have had a shift in responsibilities for my day job and as such have not been able to attend to Zowe as much as I think I should be commensurate with my responsibilities.  As such, I’m stepping down from the ZLC; but not from Zowe.

The momentum for what the community is creating is palpable.  Customers are now asking for it to do their own internal development, products are using it and we’ve made substantial progress over the past few years from incubator to open source to a critical part of product offerings and customer consumption.  I’m honored to work with giants such as yourself.  

One of the activities that needs to be done is to replace my seat on the ZLC.  For consideration, I’d like to nominate Joe Winchester for that role.  He is active in the community, driving critical work for packaging via CUPIDS and is the goto guy for so many things Zowe.

John Mertic will help to facilitate the process.

Again, thanks so much.  You are all fantastic to work alongside.

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





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: NOMINATIONS OPEN: ZLC Voting seat

John Davies <daviesja@...>
 

Hello,

I too wish to nominate Joe Winchester.

Regards,

John A Davies, z/OS
IBM Systems | zSystems Software, Hursley, UK. Tel 37245623.  (+)44 (0)1962 815623.  daviesja@...

"If you don't know how much of your code has been tested, why are you releasing it?"  Ask me about code coverage or click on this link

Code coverage on IBM Connections




From:        "John Mertic" <jmertic@...>
To:        zowe-zlc@..., zowe-dev@..., zowe-user@...
Date:        25/11/2019 14:44
Subject:        [EXTERNAL] Re: [zowe-dev] NOMINATIONS OPEN: ZLC Voting seat
Sent by:        zowe-dev@...




Friendly reminder that nominations for the ZLC seat close TODAY at 11:59pm US Eastern Time.

Thank you,

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



On Mon, Nov 18, 2019 at 4:30 PM John Mertic <jmertic@...> wrote:
Zowe Community,

As the vast majority of the Zowe Community is in favor of replacing the open seat on the ZLC, I'd like to formally open the nomination and election period. 

Based on the ZLC structure and processes ( see https://github.com/zowe/zlc/blob/master/process/structure.md ), I'd like to propose the following schedule for the election:

TODAY: Call for Nominations, email all Zowe project committers
11/25: Nominations close, 11:59pm ET
11/27: Voting period opens, all current Zowe project committers vote, vote by electronic mail or CIVS as appropriate
12/4: Voting period ends, 11:59pm ET

12/6: Election results announced 

We have one nomination already received for Joe Winchester. If you would like to nominate someone else or nominate yourself, please email your name and rationale for serving on the ZLC to me by 11/25 at 11:59pm ET. Note that in order to serve on the ZLC, you must be a Zowe Committer.

Thank you,

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



---------- Forwarded message ---------
From: John Mertic <
jmertic@...>
Date: Thu, Nov 7, 2019 at 12:47 PM
Subject: Re: [zowe-user] Change in ZLC Composition
To: <
zowe-user@...>
Cc: <
zowe-zlc@...>, <zowe-dev@...>


Zowe Community,

First and foremost, I would personally like to thank Matt for his service on the ZLC. There has been amazing progress in year 1 of Zowe which Matt has spearheaded, and his leadership has set the tone for the way the community will continue to grow in years to come.

The ZLC had a discussion yesterday on next steps with backfilling this seat, in light of the ZLC structure and processes ( see https://github.com/zowe/zlc/blob/master/process/structure.md ), and came up with two possible steps forward...

1) Immediately hold an election to backfill Matt's seat per the guidelines established ( https://github.com/zowe/zlc/blob/master/process/structure.md#composition ) with the term of this seat to be through the planned elections for the full ZLCin early January.
2) Start the process of the full ZLC re-election now, with the terms effective 1/1/2020 and the 1 year seats effective through 12/31/2020 and the 2 year seats effective through 12/31/2021.

The ZLC wanted community feedback on the way to proceed. Please share your preference on the approach on this thread. The ZLC would like to wrap up the discussion by the end of next week ( 11/15/2019 ) and then will discuss a plan for next steps at the subsequent ZLC meeting.

Let me know of any questions or concerns you might have.

Thank you,

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



On Thu, Nov 7, 2019 at 10:52 AM Matt Hogstrom <matt@...> wrote:


I have had a shift in responsibilities for my day job and as such have not been able to attend to Zowe as much as I think I should be commensurate with my responsibilities.  As such, I’m stepping down from the ZLC; but not from Zowe.

The momentum for what the community is creating is palpable.  Customers are now asking for it to do their own internal development, products are using it and we’ve made substantial progress over the past few years from incubator to open source to a critical part of product offerings and customer consumption.  I’m honored to work with giants such as yourself. 

One of the activities that needs to be done is to replace my seat on the ZLC.  For consideration, I’d like to nominate Joe Winchester for that role.  He is active in the community, driving critical work for packaging via CUPIDS and is the goto guy for so many things Zowe.

John Mertic will help to facilitate the process.

Again, thanks so much.  You are all fantastic to work alongside.

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: NOMINATIONS OPEN: ZLC Voting seat

John Mertic
 

Friendly reminder that nominations for the ZLC seat close TODAY at 11:59pm US Eastern Time.

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 Mon, Nov 18, 2019 at 4:30 PM John Mertic <jmertic@...> wrote:
Zowe Community,

As the vast majority of the Zowe Community is in favor of replacing the open seat on the ZLC, I'd like to formally open the nomination and election period. 

Based on the ZLC structure and processes ( see https://github.com/zowe/zlc/blob/master/process/structure.md ), I'd like to propose the following schedule for the election:

TODAY: Call for Nominations, email all Zowe project committers
11/25: Nominations close, 11:59pm ET
11/27: Voting period opens, all current Zowe project committers vote, vote by electronic mail or CIVS as appropriate
12/4: Voting period ends, 11:59pm ET
12/6: Election results announced 

We have one nomination already received for Joe Winchester. If you would like to nominate someone else or nominate yourself, please email your name and rationale for serving on the ZLC to me by 11/25 at 11:59pm ET. Note that in order to serve on the ZLC, you must be a Zowe Committer.

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



---------- Forwarded message ---------
From: John Mertic <jmertic@...>
Date: Thu, Nov 7, 2019 at 12:47 PM
Subject: Re: [zowe-user] Change in ZLC Composition
To: <zowe-user@...>
Cc: <zowe-zlc@...>, <zowe-dev@...>


Zowe Community,

First and foremost, I would personally like to thank Matt for his service on the ZLC. There has been amazing progress in year 1 of Zowe which Matt has spearheaded, and his leadership has set the tone for the way the community will continue to grow in years to come.

The ZLC had a discussion yesterday on next steps with backfilling this seat, in light of the ZLC structure and processes ( see https://github.com/zowe/zlc/blob/master/process/structure.md ), and came up with two possible steps forward...

1) Immediately hold an election to backfill Matt's seat per the guidelines established ( https://github.com/zowe/zlc/blob/master/process/structure.md#composition ) with the term of this seat to be through the planned elections for the full ZLCin early January.
2) Start the process of the full ZLC re-election now, with the terms effective 1/1/2020 and the 1 year seats effective through 12/31/2020 and the 2 year seats effective through 12/31/2021.

The ZLC wanted community feedback on the way to proceed. Please share your preference on the approach on this thread. The ZLC would like to wrap up the discussion by the end of next week ( 11/15/2019 ) and then will discuss a plan for next steps at the subsequent ZLC meeting.

Let me know of any questions or concerns you might have.

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 Thu, Nov 7, 2019 at 10:52 AM Matt Hogstrom <matt@...> wrote:

I have had a shift in responsibilities for my day job and as such have not been able to attend to Zowe as much as I think I should be commensurate with my responsibilities.  As such, I’m stepping down from the ZLC; but not from Zowe.

The momentum for what the community is creating is palpable.  Customers are now asking for it to do their own internal development, products are using it and we’ve made substantial progress over the past few years from incubator to open source to a critical part of product offerings and customer consumption.  I’m honored to work with giants such as yourself. 

One of the activities that needs to be done is to replace my seat on the ZLC.  For consideration, I’d like to nominate Joe Winchester for that role.  He is active in the community, driving critical work for packaging via CUPIDS and is the goto guy for so many things Zowe.

John Mertic will help to facilitate the process.

Again, thanks so much.  You are all fantastic to work alongside.

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

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





Cupids Scrum - Install/Package/SMP-E/PTF/Componentize - Mon, 11/25/2019 #cal-notice

zowe-dev@lists.openmainframeproject.org Calendar <noreply@...>
 

Cupids Scrum - Install/Package/SMP-E/PTF/Componentize

When:
Monday, 25 November 2019
2:30pm to 3:00pm
(GMT+00:00) UTC

Where:
https://zoom.us/my/zowe.onboarding

Organizer:
winchest@... +447749965423

Description:
Cupids Scrum - This squad works on issues related to installing, packaging, launching Zowe including SMP/E PTF and APAR delivery.  
https://github.com/zowe/zowe-install-packaging#workspaces/community-5c93e02fa70b456d35b8f0ed/board?repos=145870120,151615191,155383451,144619729,144599701,144592776

2721 - 2740 of 3855