|
Zowe CLI profile data at rest
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)
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)
|
By
Morten Schiønning
·
#21
·
|
|
Re: Zowe CLI profile data at rest
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
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
|
By
Sujay
·
#22
·
|
|
[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
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
|
By
Matt Hogstrom
·
#23
·
|
|
Re: [zowe-zlc] [VOTE] Require Multi-Factor Authentication for Committers to Zowe Projects in GitHub
+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
+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
|
By
jlinardon@...
·
#24
·
|
|
Re: [zowe-zlc] [VOTE] Require Multi-Factor Authentication for Committers to Zowe Projects in GitHub
+1
By
Mark.Ackert@...
·
#25
·
|
|
Re: [zowe-zlc] [VOTE] Require Multi-Factor Authentication for Committers to Zowe Projects in GitHub
+1
By
Maciej_Serafin@...
·
#26
·
|
|
Re: [zowe-zlc] [VOTE] Require Multi-Factor Authentication for Committers to Zowe Projects in GitHub
+1
--
Jean-Louis Vignaud
Product Management
Broadcom, MF Business Division
+420 770 146 136
+1
--
Jean-Louis Vignaud
Product Management
Broadcom, MF Business Division
+420 770 146 136
|
By
Jean-Louis Vignaud
·
#27
·
|
|
Re: [VOTE] Require Multi-Factor Authentication for Committers to Zowe Projects in GitHub
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
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
|
By
Matt Hogstrom
·
#28
·
|
|
Re: [VOTE] Require Multi-Factor Authentication for Committers to Zowe Projects in GitHub
+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@...
+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@...
|
By
Joe Winchester
·
#29
·
|
|
Re: [VOTE] Require Multi-Factor Authentication for Committers to Zowe Projects in GitHub
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
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
|
By
Matt Hogstrom
·
#30
·
|
|
Re: [zowe-dev] [zowe-user] [VOTE] Require Multi-Factor Authentication for Committers to Zowe Projects in GitHub
+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@...
+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@...
|
By
Joe Winchester
·
#31
·
|
|
Re: [zowe-dev] [zowe-user] [VOTE] Require Multi-Factor Authentication for Committers to Zowe Projects in GitHub
+1
Cordialement, Regards.
Jean-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@...
1 Bis Avenue Gulf Stream
44380
+1
Cordialement, Regards.
Jean-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@...
1 Bis Avenue Gulf Stream
44380
|
By
Jean-Yves Baudy
·
#32
·
|
|
[DISCUSS] Updated Governance Documents and ZLC Succession Plan
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
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
|
By
Matt Hogstrom
·
#33
·
|
|
Re: [zowe-zlc] [DISCUSS] Updated Governance Documents and ZLC Succession Plan
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
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
|
By
Tim Brooks
·
#34
·
|
|
Re: [zowe-zlc] [DISCUSS] Updated Governance Documents and ZLC Succession Plan
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
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
|
By
John Mertic
·
#35
·
|
|
Re: [zowe-zlc] [DISCUSS] Updated Governance Documents and ZLC Succession Plan
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
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
|
By
Matt Hogstrom
·
#36
·
|
|
Re: [zowe-dev] [zowe-user] [zowe-zlc] [DISCUSS] Updated Governance Documents and ZLC Succession Plan
Merged branches to https://github.com/zowe/zlc and https://github.com/zowe/community. Branches referred to below have been merged and deleted.
Files of interest for review
Merged branches to https://github.com/zowe/zlc and https://github.com/zowe/community. Branches referred to below have been merged and deleted.
Files of interest for review
|
By
Matt Hogstrom
·
#37
·
|
|
[DISCUSS] Update on Voting
Last week we continued to discuss our upcoming vote. As I previously indicated, we’ve learned a lot since the community was initially formed and now that we’re at the end of the first year one of
Last week we continued to discuss our upcoming vote. As I previously indicated, we’ve learned a lot since the community was initially formed and now that we’re at the end of the first year one of
|
By
Matt Hogstrom
·
#38
·
|
|
Re: [zowe-dev] [DISCUSS] Update on Voting
Thanks for this Matt.
To address the initial election challenge of determine which seats are 1 year and which are 2 year, the general path many of our projects take is to do it by votes received (
Thanks for this Matt.
To address the initial election challenge of determine which seats are 1 year and which are 2 year, the general path many of our projects take is to do it by votes received (
|
By
John Mertic
·
#39
·
|
|
[VOTE] Shifting the Website over to Github from River
Please review and vote on the shifting of the website from River to Github. The website can be seen here
https://zowe.gihub.io
The Doc squad has created a single page that links out to other
Please review and vote on the shifting of the website from River to Github. The website can be seen here
https://zowe.gihub.io
The Doc squad has created a single page that links out to other
|
By
Matt Hogstrom
·
#40
·
|