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;-)


Christopher Ferris
IBM Fellow, CTO Open Technology
IBM Digital Business Group, Open Technologies
email: chrisfer@...
twitter: @christo4ferris

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/ 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?


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:
would 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 Jones
Community Architect, Hyperledger

Ry Jones
Community Architect, Hyperledger

Join to automatically receive all group messages.