toc@lists.hyperledger.org

Home Messages Hashtags Subgroups Calendar

Export Group Data

Between

and

Upcoming Event: Hyperledger Smart Contracts WG Quarterly Update Due #tsc-wg-update - Thu, 06/06/2019 #tsc-wg-update #cal-reminder tsc@lists.hyperledger.org Calendar <tsc@...> #2304 Reminder: Hyperledger Smart Contracts WG Quarterly Update Due #tsc-wg-update When: Thursday, 6 June 2019 View Event Organizer: community-architects@... Description: The Hyperledger Smart Contracts WG update to the TSC was due 03 June, 2019, and it will be presented to the TSC on 06 June, 2019. Please review the update at TSC Working Group Updates prior to the meeting and add your questions to the update.
More
Re: Proposal to the TSC: enable 2FA requirement across all orgs Ry Jones #2303 Gotcha. I was thinking of a historical look, not an ongoing one. toggle quoted messageShow quoted text On Thu, May 30, 2019 at 4:10 PM Christopher B Ferris <chrisfer@...> wrote: Should be able to write a web hook to post a comment on PRs Cheers, Christopher Ferris IBM Fellow, CTO Open Technology IBM Digital Business Group, Open Technologies email: chrisfer@... twitter: @christo4ferris blog: https://developer.ibm.com/code/author/chrisfer/ IBM Open Source white paper: https://developer.ibm.com/articles/cl-open-architecture-update/ phone: +1 508 667 0402 On May 30, 2019, at 6:58 PM, Ry Jones <rjones@...> wrote: On Thu, May 30, 2019 at 3:41 PM Brian Behlendorf <bbehlendorf@...> wrote: Can we tell which commits come in without 2FA? Not easily. We could probably figure it out, though. Everything is a matter of awk, sed, and curl. -- Ry Jones Community Architect, Hyperledger Chat: @rjones -- Ry Jones Community Architect, Hyperledger Chat: @rjones
More All Messages By This Member
Re: Proposal to the TSC: enable 2FA requirement across all orgs Christopher Ferris <chrisfer@...> #2302 Should be able to write a web hook to post a comment on PRs Cheers, Christopher Ferris IBM Fellow, CTO Open Technology IBM Digital Business Group, Open Technologies email: chrisfer@... twitter: @christo4ferris blog: https://developer.ibm.com/code/author/chrisfer/ IBM Open Source white paper: https://developer.ibm.com/articles/cl-open-architecture-update/ phone: +1 508 667 0402 toggle quoted messageShow quoted text On May 30, 2019, at 6:58 PM, Ry Jones <rjones@...> wrote: On Thu, May 30, 2019 at 3:41 PM Brian Behlendorf <bbehlendorf@...> wrote: Can we tell which commits come in without 2FA? Not easily. We could probably figure it out, though. Everything is a matter of awk, sed, and curl. -- Ry Jones Community Architect, Hyperledger Chat: @rjones
More All Messages By This Member
Re: Proposal to the TSC: enable 2FA requirement across all orgs Ry Jones #2301 On Thu, May 30, 2019 at 3:41 PM Brian Behlendorf <bbehlendorf@...> wrote: Can we tell which commits come in without 2FA? Not easily. We could probably figure it out, though. Everything is a matter of awk, sed, and curl. -- Ry Jones Community Architect, Hyperledger Chat: @rjones
More All Messages By This Member
Re: Proposal to the TSC: enable 2FA requirement across all orgs Brian Behlendorf #2300 Can we tell which commits come in without 2FA? Brian On 5/30/19 2:02 PM, Christopher Ferris wrote: You should give a warning. You can add all github ids to a team and @ the team. Maybe give a few days to remediate. I approve subject to advance warning and update to contributors guides. Cheers, Christopher Ferris IBM Fellow, CTO Open Technology IBM Digital Business Group, Open Technologies email: chrisfer@... twitter: @christo4ferris blog: https://developer.ibm.com/code/author/chrisfer/ IBM Open Source white paper: https://developer.ibm.com/articles/cl-open-architecture-update/ phone: +1 508 667 0402 On May 30, 2019, at 4:54 PM, Ry Jones <rjones@...> wrote: In light of recent discussions on this mailing list, I ask the TSC to vote by email on enabling 2FA for the Hyperledger and Hyperledger Labs orgs. We will lose many members that are committers. It will cause turbulence. Ry -- Ry Jones Community Architect, Hyperledger Chat: @rjones -- Brian Behlendorf Executive Director, Hyperledger bbehlendorf@... Twitter: @brianbehlendorf
More All Messages By This Member
Re: Proposal to the TSC: enable 2FA requirement across all orgs Christopher Ferris <chrisfer@...> #2299 Also should spam mailing lists... just saying. Cheers, Christopher Ferris IBM Fellow, CTO Open Technology IBM Digital Business Group, Open Technologies email: chrisfer@... twitter: @christo4ferris blog: https://developer.ibm.com/code/author/chrisfer/ IBM Open Source white paper: https://developer.ibm.com/articles/cl-open-architecture-update/ phone: +1 508 667 0402 toggle quoted messageShow quoted text On May 30, 2019, at 5:01 PM, Middleton, Dan <dan.middleton@...> wrote: Let’s stay the vote. We can bring this up as a topic in the next TSC call and either take a vote there or move to email vote thereafter. There’s not yet enough discussion on the turbulence for an informed vote. Thanks, Dan From: <tsc@...> on behalf of Ry Jones <rjones@...> Date: Thursday, May 30, 2019 at 3:54 PM To: TSC <tsc@...> Subject: [Hyperledger TSC] Proposal to the TSC: enable 2FA requirement across all orgs In light of recent discussions on this mailing list, I ask the TSC to vote by email on enabling 2FA for the Hyperledger and Hyperledger Labs orgs. We will lose many members that are committers. It will cause turbulence. Ry -- Ry Jones Community Architect, Hyperledger Chat: @rjones
More All Messages By This Member
Re: Proposal to the TSC: enable 2FA requirement across all orgs Christopher Ferris <chrisfer@...> #2298 You should give a warning. You can add all github ids to a team and @ the team. Maybe give a few days to remediate. I approve subject to advance warning and update to contributors guides. Cheers, Christopher Ferris IBM Fellow, CTO Open Technology IBM Digital Business Group, Open Technologies email: chrisfer@... twitter: @christo4ferris blog: https://developer.ibm.com/code/author/chrisfer/ IBM Open Source white paper: https://developer.ibm.com/articles/cl-open-architecture-update/ phone: +1 508 667 0402 toggle quoted messageShow quoted text On May 30, 2019, at 4:54 PM, Ry Jones <rjones@...> wrote: In light of recent discussions on this mailing list, I ask the TSC to vote by email on enabling 2FA for the Hyperledger and Hyperledger Labs orgs. We will lose many members that are committers. It will cause turbulence. Ry -- Ry Jones Community Architect, Hyperledger Chat: @rjones
More All Messages By This Member
Re: Proposal to the TSC: enable 2FA requirement across all orgs Middleton, Dan <dan.middleton@...> #2297 Let’s stay the vote. We can bring this up as a topic in the next TSC call and either take a vote there or move to email vote thereafter. There’s not yet enough discussion on the turbulence for an informed vote. Thanks, Dan From: <tsc@...> on behalf of Ry Jones <rjones@...> Date: Thursday, May 30, 2019 at 3:54 PM To: TSC <tsc@...> Subject: [Hyperledger TSC] Proposal to the TSC: enable 2FA requirement across all orgs In light of recent discussions on this mailing list, I ask the TSC to vote by email on enabling 2FA for the Hyperledger and Hyperledger Labs orgs. We will lose many members that are committers. It will cause turbulence. Ry -- Ry Jones Community Architect, Hyperledger Chat: @rjones
More All Messages By This Member
Proposal to the TSC: enable 2FA requirement across all orgs Ry Jones #2296 In light of recent discussions on this mailing list, I ask the TSC to vote by email on enabling 2FA for the Hyperledger and Hyperledger Labs orgs. We will lose many members that are committers. It will cause turbulence. Ry -- Ry Jones Community Architect, Hyperledger Chat: @rjones
More All Messages By This Member
Re: Proposal: adopt the Kubernetes GitHub/Community management workflow hmontgomery@us.fujitsu.com <hmontgomery@...> #2295 Isn’t 2FA standard these days for this kind of thing? Is there anything we can do to push contributors to set it up? I’d have pushed the button… From: tsc@... [mailto:tsc@...] On Behalf Of Christopher Ferris Sent: Thursday, May 30, 2019 1:22 PM To: Ry Jones <rjones@...> Cc: Shawn Amundson <amundson@...>; TSC <tsc@...> Subject: Re: [Hyperledger TSC] Proposal: adopt the Kubernetes GitHub/Community management workflow I’d insist on all ppl with write and admin access to have 2FA. I would also make STRONG recommendation for others to do so as well. I too have been tempted to push the button, but that would only end in a flooded inbox with hate mail;-) Cheers, Christopher Ferris IBM Fellow, CTO Open Technology IBM Digital Business Group, Open Technologies email: chrisfer@... twitter: @christo4ferris blog: https://developer.ibm.com/code/author/chrisfer/ IBM Open Source white paper: https://developer.ibm.com/articles/cl-open-architecture-update/ phone: +1 508 667 0402 On May 30, 2019, at 4:08 PM, Ry Jones <rjones@...> wrote: toggle quoted messageShow quoted text 1. Nobody ever asked for that; I thought it came for free. I added all repos to the "Hyperledger Contributors" group (which should be everyone) as "read". You should see this reflected; I checked a few repos before and after, and it looks how I expect. If you do not see this, let me know. 2. Yes 3. My concern is, honestly, booting everyone that doesn't have 2FA enabled, which is a lot of contributors. I've been tempted to click the button, but I haven't. I suspect the answer is "yes" but we'll need somewhere to host it (GCE or AWS, probably, for production; I'm sure I have a machine that can run minikube that I can dedicate to the cause before I started spending a lot of time on it, I wanted to see if we could reach consensus. On Thu, May 30, 2019 at 12:32 PM Shawn Amundson <amundson@...> wrote: I'm not sure I fully grok everything there, given the amount of kubernetes-specific stuff (staging vs. non-staging repos, etc.). There are a couple things there I really like (if I'm understanding it correctly): 1. By default, everyone in the org having read access to all repos. That would be awesome. 2. For our repos w/MAINTAINERS.md files, we should be able to derive write access programatically (into the tool's format), then apply it programatically. That would be awesome. There are other good things in there too. Would it be possible to pilot this on a few repos so we could gain a better understanding of it, or will this be a heavy lift to try it out? -Shawn On Wed, May 29, 2019 at 6:13 PM Ry Jones <rjones@...> wrote: Much of this would not apply - we don't have a CLA, for instance. However: https://github.com/kubernetes/community/tree/master/github-management would make on-boarding new users more programmatic. Also: https://github.com/kubernetes/test-infra/tree/master/prow/cmd/peribolos Having this would allow committer promotion and removal automagically, instead of by the manual, error-prone process we have today. I would prefer to keep this discussion on this mailing list, and go to the TSC call once a decision is made on if/how to implement it. Ry -- Ry Jones Community Architect, Hyperledger Chat: @rjones -- Ry Jones Community Architect, Hyperledger Chat: @rjones
More All Messages By This Member
Re: Proposal: adopt the Kubernetes GitHub/Community management workflow Christopher Ferris <chrisfer@...> #2294 I’d insist on all ppl with write and admin access to have 2FA. I would also make STRONG recommendation for others to do so as well. I too have been tempted to push the button, but that would only end in a flooded inbox with hate mail;-) Cheers, Christopher Ferris IBM Fellow, CTO Open Technology IBM Digital Business Group, Open Technologies email: chrisfer@... twitter: @christo4ferris blog: https://developer.ibm.com/code/author/chrisfer/ IBM Open Source white paper: https://developer.ibm.com/articles/cl-open-architecture-update/ phone: +1 508 667 0402 toggle quoted messageShow quoted text On May 30, 2019, at 4:08 PM, Ry Jones <rjones@...> wrote: 1. Nobody ever asked for that; I thought it came for free. I added all repos to the "Hyperledger Contributors" group (which should be everyone) as "read". You should see this reflected; I checked a few repos before and after, and it looks how I expect. If you do not see this, let me know. 2. Yes 3. My concern is, honestly, booting everyone that doesn't have 2FA enabled, which is a lot of contributors. I've been tempted to click the button, but I haven't. I suspect the answer is "yes" but we'll need somewhere to host it (GCE or AWS, probably, for production; I'm sure I have a machine that can run minikube that I can dedicate to the cause before I started spending a lot of time on it, I wanted to see if we could reach consensus. On Thu, May 30, 2019 at 12:32 PM Shawn Amundson <amundson@...> wrote: I'm not sure I fully grok everything there, given the amount of kubernetes-specific stuff (staging vs. non-staging repos, etc.). There are a couple things there I really like (if I'm understanding it correctly): 1. By default, everyone in the org having read access to all repos. That would be awesome. 2. For our repos w/MAINTAINERS.md files, we should be able to derive write access programatically (into the tool's format), then apply it programatically. That would be awesome. There are other good things in there too. Would it be possible to pilot this on a few repos so we could gain a better understanding of it, or will this be a heavy lift to try it out? -Shawn On Wed, May 29, 2019 at 6:13 PM Ry Jones <rjones@...> wrote: Much of this would not apply - we don't have a CLA, for instance. However: https://github.com/kubernetes/community/tree/master/github-management would make on-boarding new users more programmatic. Also: https://github.com/kubernetes/test-infra/tree/master/prow/cmd/peribolos Having this would allow committer promotion and removal automagically, instead of by the manual, error-prone process we have today. I would prefer to keep this discussion on this mailing list, and go to the TSC call once a decision is made on if/how to implement it. Ry -- Ry Jones Community Architect, Hyperledger Chat: @rjones -- Ry Jones Community Architect, Hyperledger Chat: @rjones
More All Messages By This Member
Re: Proposal: adopt the Kubernetes GitHub/Community management workflow Ry Jones #2293 1. Nobody ever asked for that; I thought it came for free. I added all repos to the "Hyperledger Contributors" group (which should be everyone) as "read". You should see this reflected; I checked a few repos before and after, and it looks how I expect. If you do not see this, let me know. 2. Yes 3. My concern is, honestly, booting everyone that doesn't have 2FA enabled, which is a lot of contributors. I've been tempted to click the button, but I haven't. I suspect the answer is "yes" but we'll need somewhere to host it (GCE or AWS, probably, for production; I'm sure I have a machine that can run minikube that I can dedicate to the cause before I started spending a lot of time on it, I wanted to see if we could reach consensus. toggle quoted messageShow quoted text On Thu, May 30, 2019 at 12:32 PM Shawn Amundson <amundson@...> wrote: I'm not sure I fully grok everything there, given the amount of kubernetes-specific stuff (staging vs. non-staging repos, etc.). There are a couple things there I really like (if I'm understanding it correctly): 1. By default, everyone in the org having read access to all repos. That would be awesome. 2. For our repos w/MAINTAINERS.md files, we should be able to derive write access programatically (into the tool's format), then apply it programatically. That would be awesome. There are other good things in there too. Would it be possible to pilot this on a few repos so we could gain a better understanding of it, or will this be a heavy lift to try it out? -Shawn On Wed, May 29, 2019 at 6:13 PM Ry Jones <rjones@...> wrote: Much of this would not apply - we don't have a CLA, for instance. However: https://github.com/kubernetes/community/tree/master/github-management would make on-boarding new users more programmatic. Also: https://github.com/kubernetes/test-infra/tree/master/prow/cmd/peribolos Having this would allow committer promotion and removal automagically, instead of by the manual, error-prone process we have today. I would prefer to keep this discussion on this mailing list, and go to the TSC call once a decision is made on if/how to implement it. Ry -- Ry Jones Community Architect, Hyperledger Chat: @rjones -- Ry Jones Community Architect, Hyperledger Chat: @rjones
More All Messages By This Member
Re: Proposal: adopt the Kubernetes GitHub/Community management workflow Shawn Amundson #2292 I'm not sure I fully grok everything there, given the amount of kubernetes-specific stuff (staging vs. non-staging repos, etc.). There are a couple things there I really like (if I'm understanding it correctly): 1. By default, everyone in the org having read access to all repos. That would be awesome. 2. For our repos w/MAINTAINERS.md files, we should be able to derive write access programatically (into the tool's format), then apply it programatically. That would be awesome. There are other good things in there too. Would it be possible to pilot this on a few repos so we could gain a better understanding of it, or will this be a heavy lift to try it out? -Shawn toggle quoted messageShow quoted text On Wed, May 29, 2019 at 6:13 PM Ry Jones <rjones@...> wrote: Much of this would not apply - we don't have a CLA, for instance. However: https://github.com/kubernetes/community/tree/master/github-management would make on-boarding new users more programmatic. Also: https://github.com/kubernetes/test-infra/tree/master/prow/cmd/peribolos Having this would allow committer promotion and removal automagically, instead of by the manual, error-prone process we have today. I would prefer to keep this discussion on this mailing list, and go to the TSC call once a decision is made on if/how to implement it. Ry -- Ry Jones Community Architect, Hyperledger Chat: @rjones
More All Messages By This Member
Re: Proposal: adopt the Kubernetes GitHub/Community management workflow Ry Jones #2291 On Thu, May 30, 2019 at 4:57 AM Casey Kuhlman via Lists.Hyperledger.Org <casey=monax.io@...> wrote: As a contributor to both I can say that the Kubernetes system feels (a) baked, (b) friendly (or at least less human in a bad way), and (c) cohesive across repos and projects; whereas Hyperledger feels... less so. Completely agreed. We're where we are, I want to fix it, help? -- Ry Jones Community Architect, Hyperledger Chat: @rjones
More All Messages By This Member
Due to conflict, I will not be able to attend TSC meeting today binh nguyen #2290 I will review the minutes and any action items. Thanks, Binh
More All Messages By This Member
Re: Proposal: adopt the Kubernetes GitHub/Community management workflow Casey Kuhlman #2289 As a contributor to both I can say that the Kubernetes system feels (a) baked, (b) friendly (or at least less human in a bad way), and (c) cohesive across repos and projects; whereas Hyperledger feels... less so. ____________________________________ Casey Kuhlman, Monax CEO Site: https://monax.io Twitter: @monaxhq, @compleatang Email: casey@... Phone (US): +1-423-523-9531; (UK): +44-75-073-96359 ____________________________________ toggle quoted messageShow quoted text On Thu, May 30, 2019 at 5:09 AM Baohua Yang <yangbaohua@...> wrote: Prefer the more-automatic way! On Thu, May 30, 2019 at 7:13 AM Ry Jones <rjones@...> wrote: Much of this would not apply - we don't have a CLA, for instance. However: https://github.com/kubernetes/community/tree/master/github-management would make on-boarding new users more programmatic. Also: https://github.com/kubernetes/test-infra/tree/master/prow/cmd/peribolos Having this would allow committer promotion and removal automagically, instead of by the manual, error-prone process we have today. I would prefer to keep this discussion on this mailing list, and go to the TSC call once a decision is made on if/how to implement it. Ry -- Ry Jones Community Architect, Hyperledger Chat: @rjones -- Best wishes! Baohua Yang
More All Messages By This Member
Re: Proposal: adopt the Kubernetes GitHub/Community management workflow Baohua Yang #2288 Prefer the more-automatic way! toggle quoted messageShow quoted text On Thu, May 30, 2019 at 7:13 AM Ry Jones <rjones@...> wrote: Much of this would not apply - we don't have a CLA, for instance. However: https://github.com/kubernetes/community/tree/master/github-management would make on-boarding new users more programmatic. Also: https://github.com/kubernetes/test-infra/tree/master/prow/cmd/peribolos Having this would allow committer promotion and removal automagically, instead of by the manual, error-prone process we have today. I would prefer to keep this discussion on this mailing list, and go to the TSC call once a decision is made on if/how to implement it. Ry -- Ry Jones Community Architect, Hyperledger Chat: @rjones -- Best wishes! Baohua Yang
More All Messages By This Member
5/23 TSC meeting minutes are up Dave Huseby <dhuseby@...> #2287 https://wiki.hyperledger.org/display/HYP/2019+05+23+TSC+Minutes --- David Huseby Security Maven, Hyperledger The Linux Foundation +1-206-234-2392 dhuseby@...
More All Messages By This Member
Proposal: adopt the Kubernetes GitHub/Community management workflow Ry Jones #2286 Much of this would not apply - we don't have a CLA, for instance. However: https://github.com/kubernetes/community/tree/master/github-management would make on-boarding new users more programmatic. Also: https://github.com/kubernetes/test-infra/tree/master/prow/cmd/peribolos Having this would allow committer promotion and removal automagically, instead of by the manual, error-prone process we have today. I would prefer to keep this discussion on this mailing list, and go to the TSC call once a decision is made on if/how to implement it. Ry -- Ry Jones Community Architect, Hyperledger Chat: @rjones
More All Messages By This Member
TSC minutes for 5/9 are up Dave Huseby <dhuseby@...> #2285 https://wiki.hyperledger.org/display/HYP/2019+05+09+TSC+Minutes --- David Huseby Security Maven, Hyperledger The Linux Foundation +1-206-234-2392 dhuseby@...
More All Messages By This Member

1601 - 1620 of 3904

Home Hashtags Subgroups Calendar Terms