Re: Proposal: adopt the Kubernetes GitHub/Community management workflow

Home Messages Hashtags Subgroups Calendar

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

Join toc@lists.hyperledger.org to automatically receive all group messages.