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@...>
Reminder: Hyperledger Smart Contracts WG Quarterly Update Due #tsc-wg-update When: Thursday, 6 June 2019 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.
|
|
Re: Proposal to the TSC: enable 2FA requirement across all orgs
Gotcha. I was thinking of a historical look, not an ongoing one.
On Thu, May 30, 2019 at 4:10 PM Christopher B Ferris <chrisfer@...> wrote:
|
|
Re: Proposal to the TSC: enable 2FA requirement across all orgs
Christopher Ferris <chrisfer@...>
Should be able to write a web hook to post a comment on PRs
toggle quoted messageShow quoted text
Cheers, Christopher Ferris IBM Fellow, CTO Open Technology IBM Digital Business Group, Open Technologies email: chrisfer@... twitter: @christo4ferris 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:
|
|
Re: Proposal to the TSC: enable 2FA requirement across all orgs
On Thu, May 30, 2019 at 3:41 PM Brian Behlendorf <bbehlendorf@...> wrote:
Not easily. We could probably figure it out, though. Everything is a matter of awk, sed, and curl.
|
|
Re: Proposal to the TSC: enable 2FA requirement across all orgs
Brian Behlendorf
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.
-- Brian Behlendorf Executive Director, Hyperledger bbehlendorf@... Twitter: @brianbehlendorf
|
|
Re: Proposal to the TSC: enable 2FA requirement across all orgs
Christopher Ferris <chrisfer@...>
Also should spam mailing lists... just saying.
toggle quoted messageShow quoted text
Cheers, Christopher Ferris IBM Fellow, CTO Open Technology IBM Digital Business Group, Open Technologies email: chrisfer@... twitter: @christo4ferris IBM Open Source white paper: https://developer.ibm.com/articles/cl-open-architecture-update/ phone: +1 508 667 0402
On May 30, 2019, at 5:01 PM, Middleton, Dan <dan.middleton@...> wrote:
|
|
Re: Proposal to the TSC: enable 2FA requirement across all orgs
Christopher Ferris <chrisfer@...>
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.
toggle quoted messageShow quoted text
Cheers, Christopher Ferris IBM Fellow, CTO Open Technology IBM Digital Business Group, Open Technologies email: chrisfer@... twitter: @christo4ferris 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:
|
|
Re: Proposal to the TSC: enable 2FA requirement across all orgs
Middleton, Dan <dan.middleton@...>
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,
From: <tsc@...> on behalf of Ry Jones <rjones@...>
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.
|
|
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.
|
|
Re: Proposal: adopt the Kubernetes GitHub/Community management workflow
hmontgomery@us.fujitsu.com <hmontgomery@...>
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
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, IBM Open Source white paper: https://developer.ibm.com/articles/cl-open-architecture-update/
|
|
Re: Proposal: adopt the Kubernetes GitHub/Community management workflow
Christopher Ferris <chrisfer@...>
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;-)
toggle quoted messageShow quoted text
Cheers, Christopher Ferris IBM Fellow, CTO Open Technology IBM Digital Business Group, Open Technologies email: chrisfer@... twitter: @christo4ferris 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:
|
|
Re: Proposal: adopt the Kubernetes GitHub/Community management workflow
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:
|
|
Re: Proposal: adopt the Kubernetes GitHub/Community management workflow
Shawn Amundson
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:
|
|
Re: Proposal: adopt the Kubernetes GitHub/Community management workflow
Completely agreed. We're where we are, I want to fix it, help?
|
|
Due to conflict, I will not be able to attend TSC meeting today
binh nguyen
I will review the minutes and any action items. Thanks, Binh
|
|
Re: Proposal: adopt the Kubernetes GitHub/Community management workflow
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. ____________________________________
On Thu, May 30, 2019 at 5:09 AM Baohua Yang <yangbaohua@...> wrote:
|
|
Re: Proposal: adopt the Kubernetes GitHub/Community management workflow
Prefer the more-automatic way!
On Thu, May 30, 2019 at 7:13 AM Ry Jones <rjones@...> wrote:
--
Best wishes! Baohua Yang
|
|
5/23 TSC meeting minutes are up
Dave Huseby <dhuseby@...>
|
|
Proposal: adopt the Kubernetes GitHub/Community management workflow
Much of this would not apply - we don't have a CLA, for instance. However: https://github.com/kubernetes/community/tree/master/github-managementwould make on-boarding new users more programmatic. Also: 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
|
|
TSC minutes for 5/9 are up
Dave Huseby <dhuseby@...>
|
|