|
Re: OPA to graduation
Saad Ali
Thank you for the clarification Torin!
The governance doc says "All changes in Governance require a 2/3 majority organization vote from all areas of expertise." What does "all areas of expertise" mean? Does it mean all the folks in https://github.com/open-policy-agent/opa/blob/master/MAINTAINERS.md ?
|
|
|
|
Re: OPA to graduation
Torin Sandall
Hi Liz, To your comment, the OPA governance model protects against one organization unfairly controlling any part of the project (including the open-policy-agent/opa repository) by allowing any maintainer (from any repository) to call for an update to the model (this is covered by the "Changes in Governance" section). The model we have in place balances (i) the desire for experts on a repository to make decisions for that repository and (ii) for the OPA contributor community to take action if one or more organizations starts misbehaving. Sustained contributors for each repository make decisions for what goes into that repository, but if those contributors begin making decisions that are not in the interest of the broader community, the OPA governance model allows maintainers from other repositories to step in and take corrective action. The model is based on the premise that maintainers are acting in the best interest of the community, but it recognizes that exceptions can occur and accounts for that. https://github.com/open-policy-agent/opa/blob/master/GOVERNANCE.md#changes-in-governance
On Fri, Sep 18, 2020 at 3:27 AM Liz Rice <liz@...> wrote:
--
-Torin
|
|
|
|
Re: OPA to graduation
Liz Rice
I am a big fan of OPA, and in general the project seems to be going well. But it does give me pause to see that open-policy-agent/opa (in particular) is controlled by one organisation Liz
On Fri, 18 Sep 2020 at 00:42, Maor Goldberg <maor@...> wrote:
|
|
|
|
Re: OPA to graduation
Maor Goldberg <maor@...>
Thank you for the clarification Torin, appreciate it. My intention was to highlight the need and to hopefully encourage other organizations to join and help your team. We are participating in the community meetings for a long time now and can only applaud everything that Styra is doing. Congratulations and good luck! 
On Sep 17, 2020, at 3:07 PM, Torin Sandall via lists.cncf.io <torin=styra.com@...> wrote: Hi All, Maor from apolicy.io sent a follow up email asking about organization responsibilities for different repos. This is all covered in the MAINTAINER.md file: # Maintainers The following table lists OPA project maintainers and areas of expertise in alphabetical order: | Name | GitHub | Email | Organization | Repositories/Area of Expertise | Added/Renewed On | | --- | --- | --- | --- | --- | --- | | Ash Narkar | @ashutosh-narkar | anarkar4387@... | Styra | opa, opa-istio-plugin | 2020-04-14 | | Craig Tabita | @ctab | ctab@... | Google | gatekeeper, gatekeeper-library | 2020-04-14 | | Max Smythe | @maxsmythe | smythe@... | Google | frameworks/constraints, gatekeeper, gatekeeper-library | 2020-04-14 | | Patrick East | @patrick-east | east.patrick@... | Styra | opa | 2020-04-14 | | Rita Zhang | @ritazh | rita.z.zhang@... | Microsoft | frameworks/constraints, gatekeeper, gatekeeper-library | 2020-04-14 | | Sertaç Özercan | @sozercan | sozercan@... | Microsoft | gatekeeper, gatekeeper-library | 2020-04-14 | | Tim Hinrichs | @timothyhinrichs | timothy.l.hinrichs@... | Styra | all repositories | 2020-04-14 | | Torin Sandall | @tsandall | torinsandall@... | Styra | all repositories | 2020-04-14 | We also have non-voting folks w/ write access on certain repos, which is valuable for onboarding new contributors to admin the project on a day-to-day basis w/o inheriting full voting rights that are essentially a conflict resolution mechanism for when other attempts to reach consensus fail. Here's a summary of contributor organizations w/ write across across major repos under the open-policy-agent org: * open-policy-agent/conftest - DataWorkz, Plex, Red Hat,Snyk, Styra * open-policy-agent/frameworks - Google, Microsoft, Styra * open-policy-agent/gatekeeper - Google, Microsoft, Styra * open-policy-agent/gatekeeper-library - Google, Microsoft, Styra * open-policy-agent/opa - Styra * open-policy-agent/opa-envoy-plugin - Styra We're always looking for folks that are interested in making long-term sustained contributions. If you're interested, please get in touch. On Wed, Sep 16, 2020 at 6:05 PM Torin Sandall <torin@...> wrote:
-Torin
|
|
|
|
Re: OPA to graduation
OPA would be a very welcome addition, in my opinion.
|
|
|
|
Re: OPA to graduation
Torin Sandall
Hi All, Maor from apolicy.io sent a follow up email asking about organization responsibilities for different repos. This is all covered in the MAINTAINER.md file: # Maintainers The following table lists OPA project maintainers and areas of expertise in alphabetical order: | Name | GitHub | Email | Organization | Repositories/Area of Expertise | Added/Renewed On | | --- | --- | --- | --- | --- | --- | | Ash Narkar | @ashutosh-narkar | anarkar4387@... | Styra | opa, opa-istio-plugin | 2020-04-14 | | Craig Tabita | @ctab | ctab@... | Google | gatekeeper, gatekeeper-library | 2020-04-14 | | Max Smythe | @maxsmythe | smythe@... | Google | frameworks/constraints, gatekeeper, gatekeeper-library | 2020-04-14 | | Patrick East | @patrick-east | east.patrick@... | Styra | opa | 2020-04-14 | | Rita Zhang | @ritazh | rita.z.zhang@... | Microsoft | frameworks/constraints, gatekeeper, gatekeeper-library | 2020-04-14 | | Sertaç Özercan | @sozercan | sozercan@... | Microsoft | gatekeeper, gatekeeper-library | 2020-04-14 | | Tim Hinrichs | @timothyhinrichs | timothy.l.hinrichs@... | Styra | all repositories | 2020-04-14 | | Torin Sandall | @tsandall | torinsandall@... | Styra | all repositories | 2020-04-14 | We also have non-voting folks w/ write access on certain repos, which is valuable for onboarding new contributors to admin the project on a day-to-day basis w/o inheriting full voting rights that are essentially a conflict resolution mechanism for when other attempts to reach consensus fail. Here's a summary of contributor organizations w/ write across across major repos under the open-policy-agent org: * open-policy-agent/conftest - DataWorkz, Plex, Red Hat,Snyk, Styra * open-policy-agent/frameworks - Google, Microsoft, Styra * open-policy-agent/gatekeeper - Google, Microsoft, Styra * open-policy-agent/gatekeeper-library - Google, Microsoft, Styra * open-policy-agent/opa - Styra * open-policy-agent/opa-envoy-plugin - Styra We're always looking for folks that are interested in making long-term sustained contributions. If you're interested, please get in touch.
On Wed, Sep 16, 2020 at 6:05 PM Torin Sandall <torin@...> wrote:
--
-Torin
|
|
|
|
Re: [RESULT] KubeEdge to move to Incubation
"Benjamin <bingjiehuo@...>
Congrats ------------------ Original ------------------ From: Steven Tan <steven@...> Date: Thu,Sep 17,2020 2:02 PM To: Tina Tsou <tina.tsou@...> Cc: quinton@... <quinton@...>, Amye Scavarda Perrin <ascavarda@...>, CNCF TOC <cncf-toc@...> Subject: Re: [cncf-toc] [RESULT] KubeEdge to move to Incubation Congrats to the KubeEdge team!
On Sep 16, 2020, at 1:33 PM, Tina Tsou <tina.tsou@...> wrote:
Congrats at KubeEdge Project!
Look forward to more deployment.
Thank you,
Tina ^ ^
On Sep 16, 2020, at 1:22 PM, Quinton Hoole via lists.cncf.io <quinton=hoole.biz@...> wrote:
|
|
|
|
Re: [RESULT] KubeEdge to move to Incubation
Steven Tan <steven@...>
Congrats to the KubeEdge team!
On Sep 16, 2020, at 1:33 PM, Tina Tsou <tina.tsou@...> wrote:
Congrats at KubeEdge Project!
Look forward to more deployment.
Thank you,
Tina ^ ^
On Sep 16, 2020, at 1:22 PM, Quinton Hoole via lists.cncf.io <quinton=hoole.biz@...> wrote:
|
|
|
|
Re: OPA to graduation
Torin Sandall
Hi Maor, https://github.com/open-policy-agent/opa/blob/master/GOVERNANCE.md https://github.com/open-policy-agent/opa/blob/master/MAINTAINERS.md As far as plans for more organizations go, we have a governance process defined that outlines how new maintainers can be added. It requires a proposal from an existing maintainer and a vote from the other maintainers. That would likely occur after someone has made sustained contributions over a period of time. Note, the governance model allows for individuals to be granted permission to admin repos on GitHub without being granted full voting rights to onboard external efforts within OPA (this is how open-policy-agent/conftest is currently managed.) -Torin
On Wed, Sep 16, 2020 at 5:03 PM Maor Goldberg <maor@...> wrote:
--
-Torin
|
|
|
|
Re: OPA to graduation
Maor Goldberg <maor@...>
Hey,
toggle quoted messageShow quoted text
Great news and congratulations to the OPA team, great project and a cornerstone for the cloud native enterprise. Looking at the maintainer status on the project, I wonder if there’s a plan to add more organizations? I believe there’s only one organization (Styra) with maintainer status on the OPA project while Google and Microsoft only maintain the Gatekeeper project (my understanding is that Gatekeeper is a separate project). I think it will be great to see more than one organization sharing responsibility and leadership for this important project. Good luck, Maor. 
On Sep 16, 2020, at 10:46 AM, Brendan Burns via lists.cncf.io <bburns=microsoft.com@...> wrote: Folks The OPA project has applied for graduation from incubation to graduated. (https://github.com/cncf/toc/pull/520) The due dilligence document can be found here: https://docs.google.com/document/d/19M5fTpe57rQIMNxawRl5wSWvJUapuzY-CkV4O5pvieU/edit The public comment period is now open for 2 weeks, and all SIGs, end users, TOC members, and community members are welcome to comment by replying to this thread. Brendan Burns
|
|
|
|
Re: [RESULT] KubeEdge to move to Incubation
Congrats at KubeEdge Project!
Look forward to more deployment.
Thank you,
Tina ^ ^
On Sep 16, 2020, at 1:22 PM, Quinton Hoole via lists.cncf.io <quinton=hoole.biz@...> wrote:
|
|
|
|
Re: [RESULT] KubeEdge to move to Incubation
Quinton Hoole <quinton@...>
Congrats KubeEdge! Very well earned, IMO. Q
On Wed, Sep 16, 2020 at 8:01 AM Amye Scavarda Perrin <ascavarda@...> wrote:
--
Quinton Hoole quinton@...
|
|
|
|
Re: OPA to graduation
Quinton Hoole <quinton@...>
As some of you are probably aware, I've been a strong proponent of OPA for several years now. Both the project, and the team seem like a great fit for CNCF graduation. I have not yet read the full due diligence, but I can state that I am not aware of any fundamental blockers to graduation, and would love to see it proceed successfully. (note: I have zero professional affiliations with the project - the above represent my best attempt at an unbiased opinion). Q
--
Quinton Hoole quinton@...
|
|
|
|
OPA to graduation
Brendan Burns
Folks
The OPA project has applied for graduation from incubation to graduated. (https://github.com/cncf/toc/pull/520)
The due dilligence document can be found here: https://docs.google.com/document/d/19M5fTpe57rQIMNxawRl5wSWvJUapuzY-CkV4O5pvieU/edit
The public comment period is now open for 2 weeks, and all SIGs, end users, TOC members, and community members are welcome to comment by replying to this thread.
Brendan Burns
|
|
|
|
[RESULT] KubeEdge to move to Incubation
Amye Scavarda Perrin
KubeEdge is approved to move to incubation: https://github.com/cncf/toc/pull/461 7/10 Alena Prokharchyk: https://lists.cncf.io/g/cncf-toc/message/5017 Brendan Burns: https://lists.cncf.io/g/cncf-toc/message/5030 Michelle Noorali: https://lists.cncf.io/g/cncf-toc/message/5043 Liz Rice: https://lists.cncf.io/g/cncf-toc/message/5050 Sheng Liang: https://lists.cncf.io/g/cncf-toc/message/5053 Justin Cormack: https://lists.cncf.io/g/cncf-toc/message/5067 Katie Gamanji: https://lists.cncf.io/g/cncf-toc/message/5249 +1 NB: Davanum Srinivas: https://lists.cncf.io/g/cncf-toc/message/5018 Zhipeng Huang: https://lists.cncf.io/g/cncf-toc/message/5019 Felix: https://lists.cncf.io/g/cncf-toc/message/5020 Klaus Ma: https://lists.cncf.io/g/cncf-toc/message/5021 Roger Klorese: https://lists.cncf.io/g/cncf-toc/message/5022 Tina Tsou: https://lists.cncf.io/g/cncf-toc/message/5023 Andrew Aitken: https://lists.cncf.io/g/cncf-toc/message/5024 Ricardo Aravena: https://lists.cncf.io/g/cncf-toc/message/5025 Thor Anker Kvisgård Lange: https://lists.cncf.io/g/cncf-toc/message/5026 Kiran Mova: https://lists.cncf.io/g/cncf-toc/message/5027 Jeremy Rickard: https://lists.cncf.io/g/cncf-toc/message/5030 Dejan Bosanac: https://lists.cncf.io/g/cncf-toc/message/5032 Paul Buck: https://lists.cncf.io/g/cncf-toc/message/5033 Phillipe Robin: https://lists.cncf.io/g/cncf-toc/message/5040 Quinton Hoole: https://lists.cncf.io/g/cncf-toc/message/5041 Richard Hartmann: https://lists.cncf.io/g/cncf-toc/message/5042 Deepak Vij: https://lists.cncf.io/g/cncf-toc/message/5044 Kevin Ryan: https://lists.cncf.io/g/cncf-toc/message/5045 Anni Lai: https://lists.cncf.io/g/cncf-toc/message/5046 Steve Wong: https://lists.cncf.io/g/cncf-toc/message/5061 GolfenGuo: https://lists.cncf.io/g/cncf-toc/message/5070 Feilong Wang: https://lists.cncf.io/g/cncf-toc/message/5079 Qingchen Job: https://lists.cncf.io/g/cncf-toc/message/5131 Shenkh: https://lists.cncf.io/g/cncf-toc/message/5132 Ryan: https://lists.cncf.io/g/cncf-toc/message/5133 Plutoligs: https://lists.cncf.io/g/cncf-toc/message/5134 Zhiyiliu: https://lists.cncf.io/g/cncf-toc/message/5135 Stanley: https://lists.cncf.io/g/cncf-toc/message/5136 Zongkheshuaige: https://lists.cncf.io/g/cncf-toc/message/5137 Amye Scavarda Perrin | Program Manager | amye@...
|
|
|
|
Agenda for 9/15
Amye Scavarda Perrin
Hi all, We'll be meeting tomorrow with a presentation on the latest End User Tech Radar. Presentation: https://docs.google.com/presentation/d/1egNKT1d5vthITnM03D9EheHqn0iBkkjBLFinVNtHZug/edit?ts=5f5f468a#slide=id.g25ca91f87f_0_0 Amye Scavarda Perrin | Program Manager | amye@...
|
|
|
|
Re: [RESULT] Tech Lead nomination for SIG Observability: Bartłomiej Płotka
Thanks, Amye for the summary, and thank you All for your trust! (: Looking forward to what we can achieve together in the CNCF Observability space 💪 Kind Regards, Bartek Płotka (@bwplotka)
On Tue, 8 Sep 2020 at 22:55, Amye Scavarda Perrin <ascavarda@...> wrote:
|
|
|
|
Re: Sandbox Projects included from September 8 TOC meeting
Li, Xiang
(I am familiar with the team behind the project, and the background of the project). OpenKurise itself is not an experiment. It supports some of the largest Kubernetes clusters in production environment at Alibaba and a few other large internet companies (https://github.com/openkruise/kruise/issues/289). For any sizable companies using Kubeternetes, it is not uncommon to have tens of generic controllers that are not specific to any particular application. The motivation of OpenKruise project is to find a subset of these controllers that are commonly useful to a number of users rather than just one company. So we can reduce some duplication, improve collaboration and help the community to grow. Yes, if some enhancements or workload types are popular enough that everyone wants then, we hope them to be upstreamed to Kubernetes project itself.
|
|
|
|
Re: Sandbox Projects included from September 8 TOC meeting
Amye Scavarda Perrin
The recording for the 9/8 meeting is up on YouTube: https://www.youtube.com/watch?v=q_FO3PWnkY4
On Wed, Sep 9, 2020 at 10:36 AM Liz Rice <liz@...> wrote:
--
Amye Scavarda Perrin | Program Manager | amye@...
|
|
|
|
Re: Sandbox Projects included from September 8 TOC meeting
Liz Rice
OpenKruise is experimenting with a number of workload-related resource definitions, some of which are enhancements to existing core K8s resources. We're happy to see these experiments and want to support them, but we wondered if it makes more sense for them to belong within the purview of the Kubernetes project rather than as a standalone project? My understanding is that OpenKruise intends to eventually contribute successful experiments to upstream Kubernetes anyway. There's also a question about project scope. If the Kubernetes project would actually prefer these experiments to take place in a separate project, does that make OpenKruise the natural home for all workload-related CRD ideas, or some other scope? The discussion was recorded (I'm sure Amy can provide the link if she hasn't already circulated it) and that might be worth listening to for more context, if you have the time.
On Wed, Sep 9, 2020 at 4:21 PM Matt Farina <matt@...> wrote:
|
|
|
