Date   

Re: RFC: Project Health Dashboard

Chris Aniszczyk
 

* Are you tracking components/individual repos as well?

yes, each project has its own site, all repositories are tracked and grouped into repository groups. For "All CNCF" project each repository groups is a single project.

* Are you tracking people (most commits, etc) as well?

yes, there are specific dashboards for this (see per project dashboards)

* Will you expand the UI filters, ordering, etc?

on this particular dashboard, this is hardest to do. It is not a Grafana dashboard at all, HTML is programmatically generated. Grafana only has a very basic tabular dashboard.

* There's too much information in default state. How about hiding the 3 month, 3 month, trend, 6 month lines on first view?

we can hide/show anything. We'll add some UI element showing/hiding rows when clicked, but it would have to be implemented as embedded javascript code.

* Is the underlying data persisted somewhere?

yes, it is, like for all other dashboards. It is stored in a Postgres database, i.e., 
* If yes, is that accessible?

Only for a small team of people who have access to an SSH bastion host, but anyone can run their own version of devstats:

nobody ever asked for this :) It was stored in the InfluxDB once (a long time ago), but we replaced it with Postgres.

* Time to last commit it relative, time to last release is absolute,

this is confusing - there is both time of last commit and days since the last commit, there is only last release date (no days since the last release), we're still working on highlighting the right metrics for project health

* Are you tracking sandbox projects as well?

yes, header row contains all CNCF projects grouped by Graduated, Incubating and Sandbox.

On Tue, Dec 4, 2018 at 11:55 AM Richard Hartmann <richih@...> wrote:
Looks like a good collection and basis for more analysis; questions in
no particular order:

* Are you tracking components/individual repos as well?
* Are you tracking people (most commits, etc) as well?
* Will you expand the UI filters, ordering, etc?
  * There's too much information in default state. How about hiding
the 3 month, 3 month, trend, 6 month lines on first view?
* Is the underlying data persisted somewhere?
  * If yes, is that accessible?
  * Is it stored in Prometheus? :)
* Time to last commit it relative, time to last release is absolute,
this is confusing
* Are you tracking sandbox projects as well?


--
Chris Aniszczyk (@cra) | +1-512-961-6719


Re: RFC: Project Health Dashboard

Richard Hartmann
 

Looks like a good collection and basis for more analysis; questions in
no particular order:

* Are you tracking components/individual repos as well?
* Are you tracking people (most commits, etc) as well?
* Will you expand the UI filters, ordering, etc?
* There's too much information in default state. How about hiding
the 3 month, 3 month, trend, 6 month lines on first view?
* Is the underlying data persisted somewhere?
* If yes, is that accessible?
* Is it stored in Prometheus? :)
* Time to last commit it relative, time to last release is absolute,
this is confusing
* Are you tracking sandbox projects as well?


FYI: Cancelling the 12/18/2018 TOC meeting

Chris Aniszczyk
 

The TOC has decided to cancel the 12/18 meeting due to the December holidays. 

We hope everyone has a great holiday and new years!

--
Chris Aniszczyk (@cra) | +1-512-961-6719


RFC: Project Health Dashboard

Chris Aniszczyk
 

Hey all, we have been experimenting with surfacing project health metrics via DevStats for CNCF projects: https://all.devstats.cncf.io/d/53/projects-health?orgId=1

If there are metrics that are missing that you would like added, let us know.

NOTE: this is still a work in progress!

--
Chris Aniszczyk (@cra) | +1-512-961-6719


Re: ​Kubernetes' first major security hole discovered | ZDNet

Chris Aniszczyk
 

The Kubernetes Steering Committee delegated it to a committee to select a vendor:

On Wed, Dec 5, 2018 at 12:34 AM Quinton Hoole <quinton@...> wrote:
Another reminder how important this stuff is...

https://www.zdnet.com/article/kubernetes-first-major-security-hole-discovered/

What is the status of out independent security audit of Kubernetes?

Do we have any idea whether that might have caught this ahead of time?

Q



--
Chris Aniszczyk (@cra) | +1-512-961-6719


​Kubernetes' first major security hole discovered | ZDNet

Quinton Hoole <quinton@...>
 

Another reminder how important this stuff is...

https://www.zdnet.com/article/kubernetes-first-major-security-hole-discovered/

What is the status of out independent security audit of Kubernetes?

Do we have any idea whether that might have caught this ahead of time?

Q


TOC Agenda 12/4/2018

Chris Aniszczyk
 

Hey all, the agenda for the TOC meeting is below:


We will focus on the categories proposal (https://docs.google.com/document/d/1mt1LH1QJgwA91A6x-DEdjg4ZOXrOnxxc1d2xhq4Hq3I/edit#) and hear from the CoreDNS and Fluentd projects regarding graduation.

Thanks!

--
Chris Aniszczyk (@cra) | +1-512-961-6719


Re: Important - next TOC call agenda and Categories / SIGs

alexis richardson
 

Addendum:

Thanks to Justin Cormack for adding some narrative around an example
SIG for Security. Please see the doc & comment!

On Thu, Nov 29, 2018 at 12:05 PM Alexis Richardson <alexis@...> wrote:

Hi all

REMINDER to please look at and comment on this doc on SIGs

https://docs.google.com/document/d/1mt1LH1QJgwA91A6x-DEdjg4ZOXrOnxxc1d2xhq4Hq3I/edit#

I know we are all ridic busy with Kubecon looming and more. But, if
we can all get this doc into a near final state this year then we can
kick off the SIGs, start to scale, and hopefully unblock stuff. Your
help is invaluable.

If you have any other agenda items for next week, please let us know
and have them added to the living agenda & minutes doc.

a


Re: RFC: containerd graduation review

Brian Grant
 

Hi, all.

All the projects seeking graduation need to be thoroughly reviewed. That's unlikely to happen for all the projects before Kubecon at this point. Fluentd has been waiting longest. I'd like the TOC to take a look at Fluentd first.


On Tue, Nov 20, 2018 at 8:51 AM Chris Aniszczyk <caniszczyk@...> wrote:
The containerd team presented to the TOC and community today about graduating.

They are asking for final feedback on the proposal:

If there are no strong objections after a week and the original TOC sponsor, Brian Grant is in support, I will call for a formal vote from the TOC.

Thanks!

--
Chris Aniszczyk (@cra) | +1-512-961-6719


Important - next TOC call agenda and Categories / SIGs

alexis richardson
 

Hi all

REMINDER to please look at and comment on this doc on SIGs

https://docs.google.com/document/d/1mt1LH1QJgwA91A6x-DEdjg4ZOXrOnxxc1d2xhq4Hq3I/edit#

I know we are all ridic busy with Kubecon looming and more. But, if
we can all get this doc into a near final state this year then we can
kick off the SIGs, start to scale, and hopefully unblock stuff. Your
help is invaluable.

If you have any other agenda items for next week, please let us know
and have them added to the living agenda & minutes doc.

a


Re: [RESULT] Envoy moving to graduation (PASSED)

Lee Calcote
 

Woo-hoo! Awesome.

- Lee

Sent from my mobile
 

From: cncf-toc@... on behalf of alexis richardson <alexis@...>
Sent: Wednesday, November 28, 2018 8:31 AM
To: Chris Aniszczyk
Cc: Alexis Richardson via cncf-toc
Subject: Re: [cncf-toc] [RESULT] Envoy moving to graduation (PASSED)
 
congratulations!

On Wed, Nov 28, 2018 at 4:31 PM Chris Aniszczyk
<caniszczyk@...> wrote:
>
> The vote for Envoy moving to the graduation maturity level has been approved: https://github.com/cncf/toc/pull/167
>
> +1 binding TOC votes (9/9):
> Alexis: https://lists.cncf.io/g/cncf-toc/message/2634
> Camille: https://lists.cncf.io/g/cncf-toc/message/2639
> Ben: https://lists.cncf.io/g/cncf-toc/message/2644
> Jonathan: https://lists.cncf.io/g/cncf-toc/message/2647
> Brian: https://lists.cncf.io/g/cncf-toc/message/2659
> Bryan: https://lists.cncf.io/g/cncf-toc/message/2666
> Quinton: https://lists.cncf.io/g/cncf-toc/message/2670
> Ken: https://lists.cncf.io/g/cncf-toc/message/2671
> Sam: https://lists.cncf.io/g/cncf-toc/message/2686
>
> +1 non-binding community votes:
> Alex Chircop: https://lists.cncf.io/g/cncf-toc/message/2635
> Shuresh Krishnan: https://lists.cncf.io/g/cncf-toc/message/2636
> Michael Hausenblas: https://lists.cncf.io/g/cncf-toc/message/2637
> Ruben Orduz: https://lists.cncf.io/g/cncf-toc/message/2638
> Mark Peek: https://lists.cncf.io/g/cncf-toc/message/2640
> Justin Garrison: https://lists.cncf.io/g/cncf-toc/message/2641
> Andrew Randall: https://lists.cncf.io/g/cncf-toc/message/2642
> Bassam Tabbara: https://lists.cncf.io/g/cncf-toc/message/2643
> Gary Brown: https://lists.cncf.io/g/cncf-toc/message/2645
> Sonya Koptyev: https://lists.cncf.io/g/cncf-toc/message/2646
> Justin Cormack: https://lists.cncf.io/g/cncf-toc/message/2648
> Christian Jantz: https://lists.cncf.io/g/cncf-toc/message/2649
> Yong Tang: https://lists.cncf.io/g/cncf-toc/message/2650
> Joseph Jacks: https://lists.cncf.io/g/cncf-toc/message/2651
> Ihor Dvoretskyi: https://lists.cncf.io/g/cncf-toc/message/2652
> Yassine Tijani: https://lists.cncf.io/g/cncf-toc/message/2653
> Nick Chase: https://lists.cncf.io/g/cncf-toc/message/2654
> Randy Abernathy: https://lists.cncf.io/g/cncf-toc/message/2655
> Chris Short: https://lists.cncf.io/g/cncf-toc/message/2656
> Andy Satosa: https://lists.cncf.io/g/cncf-toc/message/2657
> Ayrat Khayretdinov: https://lists.cncf.io/g/cncf-toc/message/2658
> Richard Li: https://lists.cncf.io/g/cncf-toc/message/2660
> Niraj Tolia: https://lists.cncf.io/g/cncf-toc/message/2661
> Mark McBride: https://lists.cncf.io/g/cncf-toc/message/2662
> Pete Miron: https://lists.cncf.io/g/cncf-toc/message/2663
> Rob Lalonde: https://lists.cncf.io/g/cncf-toc/message/2664
> Doug Davis: https://lists.cncf.io/g/cncf-toc/message/2665
> Richard Hartmann: https://lists.cncf.io/g/cncf-toc/message/2667
> Roman Chepurnyi: https://lists.cncf.io/g/cncf-toc/message/2668
> Jean-Christophe Counio: https://lists.cncf.io/g/cncf-toc/message/2669Alena Prokharchyk: https://lists.cncf.io/g/cncf-toc/message/2672
> Liz Rice: https://lists.cncf.io/g/cncf-toc/message/2673
> Venil Noronha: https://lists.cncf.io/g/cncf-toc/message/2674
> Davanum Srinivas: https://lists.cncf.io/g/cncf-toc/message/2675
> Christian Posta: https://lists.cncf.io/g/cncf-toc/message/2676
> Heng Du: https://lists.cncf.io/g/cncf-toc/message/2677
> Jimmy Song: https://lists.cncf.io/g/cncf-toc/message/2678
> Anirudh: https://lists.cncf.io/g/cncf-toc/message/2679
> Mathias Herzog: https://lists.cncf.io/g/cncf-toc/message/2680
> Daniel Bryant: https://lists.cncf.io/g/cncf-toc/message/2681
> 郑淮城: https://lists.cncf.io/g/cncf-toc/message/2682
> Jon Edvald: https://lists.cncf.io/g/cncf-toc/message/2683
> Lee Calcote: https://lists.cncf.io/g/cncf-toc/message/2684
> Dan Wilson: https://lists.cncf.io/g/cncf-toc/message/2685
> Eduardo Silva: https://lists.cncf.io/g/cncf-toc/message/2688
> Geri Jennings: https://lists.cncf.io/g/cncf-toc/message/2689
> Golfen Guo: https://lists.cncf.io/g/cncf-toc/message/2690
> 徐翔轩: https://lists.cncf.io/g/cncf-toc/message/2691
> Peter Kim: https://lists.cncf.io/g/cncf-toc/message/2692
> Vadim Solovey: https://lists.cncf.io/g/cncf-toc/message/2693
> Zhang Lei: https://lists.cncf.io/g/cncf-toc/message/2694
> Alois Mayr: https://lists.cncf.io/g/cncf-toc/message/2695
> Allen Sun: https://lists.cncf.io/g/cncf-toc/message/2697
> Cathy Zhang: https://lists.cncf.io/g/cncf-toc/message/2702
> Steven Dake: https://lists.cncf.io/g/cncf-toc/message/2703
>
> Thanks all for voting!
>
> --
> Chris Aniszczyk (@cra) | +1-512-961-6719
>




Re: [RESULT] Envoy moving to graduation (PASSED)

alexis richardson
 

congratulations!

On Wed, Nov 28, 2018 at 4:31 PM Chris Aniszczyk
<caniszczyk@...> wrote:

The vote for Envoy moving to the graduation maturity level has been approved: https://github.com/cncf/toc/pull/167

+1 binding TOC votes (9/9):
Alexis: https://lists.cncf.io/g/cncf-toc/message/2634
Camille: https://lists.cncf.io/g/cncf-toc/message/2639
Ben: https://lists.cncf.io/g/cncf-toc/message/2644
Jonathan: https://lists.cncf.io/g/cncf-toc/message/2647
Brian: https://lists.cncf.io/g/cncf-toc/message/2659
Bryan: https://lists.cncf.io/g/cncf-toc/message/2666
Quinton: https://lists.cncf.io/g/cncf-toc/message/2670
Ken: https://lists.cncf.io/g/cncf-toc/message/2671
Sam: https://lists.cncf.io/g/cncf-toc/message/2686

+1 non-binding community votes:
Alex Chircop: https://lists.cncf.io/g/cncf-toc/message/2635
Shuresh Krishnan: https://lists.cncf.io/g/cncf-toc/message/2636
Michael Hausenblas: https://lists.cncf.io/g/cncf-toc/message/2637
Ruben Orduz: https://lists.cncf.io/g/cncf-toc/message/2638
Mark Peek: https://lists.cncf.io/g/cncf-toc/message/2640
Justin Garrison: https://lists.cncf.io/g/cncf-toc/message/2641
Andrew Randall: https://lists.cncf.io/g/cncf-toc/message/2642
Bassam Tabbara: https://lists.cncf.io/g/cncf-toc/message/2643
Gary Brown: https://lists.cncf.io/g/cncf-toc/message/2645
Sonya Koptyev: https://lists.cncf.io/g/cncf-toc/message/2646
Justin Cormack: https://lists.cncf.io/g/cncf-toc/message/2648
Christian Jantz: https://lists.cncf.io/g/cncf-toc/message/2649
Yong Tang: https://lists.cncf.io/g/cncf-toc/message/2650
Joseph Jacks: https://lists.cncf.io/g/cncf-toc/message/2651
Ihor Dvoretskyi: https://lists.cncf.io/g/cncf-toc/message/2652
Yassine Tijani: https://lists.cncf.io/g/cncf-toc/message/2653
Nick Chase: https://lists.cncf.io/g/cncf-toc/message/2654
Randy Abernathy: https://lists.cncf.io/g/cncf-toc/message/2655
Chris Short: https://lists.cncf.io/g/cncf-toc/message/2656
Andy Satosa: https://lists.cncf.io/g/cncf-toc/message/2657
Ayrat Khayretdinov: https://lists.cncf.io/g/cncf-toc/message/2658
Richard Li: https://lists.cncf.io/g/cncf-toc/message/2660
Niraj Tolia: https://lists.cncf.io/g/cncf-toc/message/2661
Mark McBride: https://lists.cncf.io/g/cncf-toc/message/2662
Pete Miron: https://lists.cncf.io/g/cncf-toc/message/2663
Rob Lalonde: https://lists.cncf.io/g/cncf-toc/message/2664
Doug Davis: https://lists.cncf.io/g/cncf-toc/message/2665
Richard Hartmann: https://lists.cncf.io/g/cncf-toc/message/2667
Roman Chepurnyi: https://lists.cncf.io/g/cncf-toc/message/2668
Jean-Christophe Counio: https://lists.cncf.io/g/cncf-toc/message/2669Alena Prokharchyk: https://lists.cncf.io/g/cncf-toc/message/2672
Liz Rice: https://lists.cncf.io/g/cncf-toc/message/2673
Venil Noronha: https://lists.cncf.io/g/cncf-toc/message/2674
Davanum Srinivas: https://lists.cncf.io/g/cncf-toc/message/2675
Christian Posta: https://lists.cncf.io/g/cncf-toc/message/2676
Heng Du: https://lists.cncf.io/g/cncf-toc/message/2677
Jimmy Song: https://lists.cncf.io/g/cncf-toc/message/2678
Anirudh: https://lists.cncf.io/g/cncf-toc/message/2679
Mathias Herzog: https://lists.cncf.io/g/cncf-toc/message/2680
Daniel Bryant: https://lists.cncf.io/g/cncf-toc/message/2681
郑淮城: https://lists.cncf.io/g/cncf-toc/message/2682
Jon Edvald: https://lists.cncf.io/g/cncf-toc/message/2683
Lee Calcote: https://lists.cncf.io/g/cncf-toc/message/2684
Dan Wilson: https://lists.cncf.io/g/cncf-toc/message/2685
Eduardo Silva: https://lists.cncf.io/g/cncf-toc/message/2688
Geri Jennings: https://lists.cncf.io/g/cncf-toc/message/2689
Golfen Guo: https://lists.cncf.io/g/cncf-toc/message/2690
徐翔轩: https://lists.cncf.io/g/cncf-toc/message/2691
Peter Kim: https://lists.cncf.io/g/cncf-toc/message/2692
Vadim Solovey: https://lists.cncf.io/g/cncf-toc/message/2693
Zhang Lei: https://lists.cncf.io/g/cncf-toc/message/2694
Alois Mayr: https://lists.cncf.io/g/cncf-toc/message/2695
Allen Sun: https://lists.cncf.io/g/cncf-toc/message/2697
Cathy Zhang: https://lists.cncf.io/g/cncf-toc/message/2702
Steven Dake: https://lists.cncf.io/g/cncf-toc/message/2703

Thanks all for voting!

--
Chris Aniszczyk (@cra) | +1-512-961-6719


[RESULT] Envoy moving to graduation (PASSED)

Chris Aniszczyk
 

The vote for Envoy moving to the graduation maturity level has been approved: https://github.com/cncf/toc/pull/167

+1 binding TOC votes (9/9):
Alexis: https://lists.cncf.io/g/cncf-toc/message/2634
Camille: https://lists.cncf.io/g/cncf-toc/message/2639
Ben: https://lists.cncf.io/g/cncf-toc/message/2644
Jonathan: https://lists.cncf.io/g/cncf-toc/message/2647
Brian: https://lists.cncf.io/g/cncf-toc/message/2659
Bryan: https://lists.cncf.io/g/cncf-toc/message/2666
Quinton: https://lists.cncf.io/g/cncf-toc/message/2670
Ken: https://lists.cncf.io/g/cncf-toc/message/2671
Sam: https://lists.cncf.io/g/cncf-toc/message/2686

+1 non-binding community votes:
Alex Chircop: https://lists.cncf.io/g/cncf-toc/message/2635
Shuresh Krishnan: https://lists.cncf.io/g/cncf-toc/message/2636
Michael Hausenblas: https://lists.cncf.io/g/cncf-toc/message/2637
Ruben Orduz: https://lists.cncf.io/g/cncf-toc/message/2638
Mark Peek: https://lists.cncf.io/g/cncf-toc/message/2640
Justin Garrison: https://lists.cncf.io/g/cncf-toc/message/2641
Andrew Randall: https://lists.cncf.io/g/cncf-toc/message/2642
Bassam Tabbara: https://lists.cncf.io/g/cncf-toc/message/2643
Gary Brown: https://lists.cncf.io/g/cncf-toc/message/2645
Sonya Koptyev: https://lists.cncf.io/g/cncf-toc/message/2646
Justin Cormack: https://lists.cncf.io/g/cncf-toc/message/2648
Christian Jantz: https://lists.cncf.io/g/cncf-toc/message/2649
Yong Tang: https://lists.cncf.io/g/cncf-toc/message/2650
Joseph Jacks: https://lists.cncf.io/g/cncf-toc/message/2651
Ihor Dvoretskyi: https://lists.cncf.io/g/cncf-toc/message/2652
Yassine Tijani: https://lists.cncf.io/g/cncf-toc/message/2653
Nick Chase: https://lists.cncf.io/g/cncf-toc/message/2654
Randy Abernathy: https://lists.cncf.io/g/cncf-toc/message/2655
Chris Short: https://lists.cncf.io/g/cncf-toc/message/2656
Andy Satosa: https://lists.cncf.io/g/cncf-toc/message/2657
Ayrat Khayretdinov: https://lists.cncf.io/g/cncf-toc/message/2658
Richard Li: https://lists.cncf.io/g/cncf-toc/message/2660
Niraj Tolia:  https://lists.cncf.io/g/cncf-toc/message/2661
Mark McBride: https://lists.cncf.io/g/cncf-toc/message/2662
Pete Miron: https://lists.cncf.io/g/cncf-toc/message/2663
Rob Lalonde: https://lists.cncf.io/g/cncf-toc/message/2664
Doug Davis: https://lists.cncf.io/g/cncf-toc/message/2665
Richard Hartmann: https://lists.cncf.io/g/cncf-toc/message/2667
Roman Chepurnyi: https://lists.cncf.io/g/cncf-toc/message/2668
Jean-Christophe Counio: https://lists.cncf.io/g/cncf-toc/message/2669Alena Prokharchyk: https://lists.cncf.io/g/cncf-toc/message/2672
Liz Rice: https://lists.cncf.io/g/cncf-toc/message/2673
Venil Noronha: https://lists.cncf.io/g/cncf-toc/message/2674
Davanum Srinivas: https://lists.cncf.io/g/cncf-toc/message/2675
Christian Posta: https://lists.cncf.io/g/cncf-toc/message/2676
Heng Du: https://lists.cncf.io/g/cncf-toc/message/2677
Jimmy Song: https://lists.cncf.io/g/cncf-toc/message/2678
Anirudh: https://lists.cncf.io/g/cncf-toc/message/2679
Mathias Herzog: https://lists.cncf.io/g/cncf-toc/message/2680
Daniel Bryant: https://lists.cncf.io/g/cncf-toc/message/2681
郑淮城: https://lists.cncf.io/g/cncf-toc/message/2682
Jon Edvald: https://lists.cncf.io/g/cncf-toc/message/2683
Lee Calcote: https://lists.cncf.io/g/cncf-toc/message/2684
Dan Wilson: https://lists.cncf.io/g/cncf-toc/message/2685
Eduardo Silva: https://lists.cncf.io/g/cncf-toc/message/2688
Geri Jennings: https://lists.cncf.io/g/cncf-toc/message/2689
Golfen Guo: https://lists.cncf.io/g/cncf-toc/message/2690
徐翔轩: https://lists.cncf.io/g/cncf-toc/message/2691
Peter Kim: https://lists.cncf.io/g/cncf-toc/message/2692
Vadim Solovey: https://lists.cncf.io/g/cncf-toc/message/2693
Zhang Lei: https://lists.cncf.io/g/cncf-toc/message/2694
Alois Mayr: https://lists.cncf.io/g/cncf-toc/message/2695
Allen Sun: https://lists.cncf.io/g/cncf-toc/message/2697
Cathy Zhang: https://lists.cncf.io/g/cncf-toc/message/2702
Steven Dake: https://lists.cncf.io/g/cncf-toc/message/2703

Thanks all for voting!

--
Chris Aniszczyk (@cra) | +1-512-961-6719


Re: sponsor for sandbox - Keycloak

Erin Boyd
 

Thanks, Quinton!
Erin


On Tue, Nov 27, 2018 at 12:44 PM Quinton Hoole <quinton.hoole@...> wrote:
SGTM.  I am available to sponsor. 
Is there an opportunity to share further information in-person at KubeCon Seattle?
Posting a link to the slide deck that was to be used in early October here would be useful.  
I would be in support of following that up with a presentation to interested parties as soon as is practical.  Chris A manages the backlog and can help with that.

Q

Quinton Hoole

Technical Vice President

America Research Center

2330 Central Expressway, Santa Clara, CA 95050

Tel: 408-330-4721   Cell: 408-320-8917   Office # C2-27

Email: quinton.hoole@...   ID#Q00403160


From: <cncf-toc@...> on behalf of Erin Boyd <eboyd@...>
Date: Tuesday, November 27, 2018 at 07:46
To: CNCF TOC <cncf-toc@...>
Subject: Re: [cncf-toc] sponsor for sandbox - Keycloak

A little more infomation (the draft proposal):

https://github.com/bdaw/toc/blob/master/proposals/keycloak.md

On Tue, Nov 27, 2018 at 8:41 AM Erin Boyd <eboyd@...> wrote:
Hi TOC,
I am soliciting a sponsor for  the Keycloak project. They were set to preset to the TOC the first week of October and were bumped. Now, following the newer Sandbox process they are looking for a sponsor.

Keycloak is an Open Source Identity and Access Management Solution for today’s Cloud Native Applications and Services. It provides an easy way to secure applications and services with minimum effort.

The Keycloak team believes that this project aligns well with section 1(c) of the CNCF Charter by providing a standard and simple way to secure Cloud Native applications and services. Out of the box, Keycloak provides an extensive set of features such as user federation, admin console and account management console. Securing applications and services can be done with only a few lines of code through Keycloak adapters that are provided for a range of languages and frameworks. Keycloak also provides both OpenID Connect and SAML 2.0 enabling any application that have support for either to be easily secured.

With it's already large community support, bringing Keycloak into the CNCF, the team hopes to continue to expand the list of features, making it even easier to secure different types of applications and reach an even wider community interested in contribution and adoption.

Website: https://keycloak.org
GitHub: https://github.com/keycloak
License: Apache License, Version 2.0


The team is happy and willing to present the project in more detail. Please let me know if any of you are able to sponsor so we may move forward.


Thanks,

Erin



Re: sponsor for sandbox - Keycloak

boleslaw.dawidowicz@gmail.com
 

Thanks Quinton!

We really appreciate it. 

Original slide deck from Keycloak is available at the end of 2nd Oct TOC meeting slides (starting at slide 26th):
I have updated the proposal with the link to those slides as well. Official PR is here:
Unfortunately neither me or Stian are attending KubeCon Seattle. We hope to be at the European one. 

We are open to jump on a call and present as soon as possible to arrange. 


W dniu wt., 27.11.2018 o 20:44 Quinton Hoole <quinton.hoole@...> napisał(a):

SGTM.  I am available to sponsor. 
Is there an opportunity to share further information in-person at KubeCon Seattle?
Posting a link to the slide deck that was to be used in early October here would be useful.  
I would be in support of following that up with a presentation to interested parties as soon as is practical.  Chris A manages the backlog and can help with that.

Q

Quinton Hoole

Technical Vice President

America Research Center

2330 Central Expressway, Santa Clara, CA 95050

Tel: 408-330-4721   Cell: 408-320-8917   Office # C2-27

Email: quinton.hoole@...   ID#Q00403160


From: <cncf-toc@...> on behalf of Erin Boyd <eboyd@...>
Date: Tuesday, November 27, 2018 at 07:46
To: CNCF TOC <cncf-toc@...>
Subject: Re: [cncf-toc] sponsor for sandbox - Keycloak

A little more infomation (the draft proposal):

https://github.com/bdaw/toc/blob/master/proposals/keycloak.md

On Tue, Nov 27, 2018 at 8:41 AM Erin Boyd <eboyd@...> wrote:
Hi TOC,
I am soliciting a sponsor for  the Keycloak project. They were set to preset to the TOC the first week of October and were bumped. Now, following the newer Sandbox process they are looking for a sponsor.

Keycloak is an Open Source Identity and Access Management Solution for today’s Cloud Native Applications and Services. It provides an easy way to secure applications and services with minimum effort.

The Keycloak team believes that this project aligns well with section 1(c) of the CNCF Charter by providing a standard and simple way to secure Cloud Native applications and services. Out of the box, Keycloak provides an extensive set of features such as user federation, admin console and account management console. Securing applications and services can be done with only a few lines of code through Keycloak adapters that are provided for a range of languages and frameworks. Keycloak also provides both OpenID Connect and SAML 2.0 enabling any application that have support for either to be easily secured.

With it's already large community support, bringing Keycloak into the CNCF, the team hopes to continue to expand the list of features, making it even easier to secure different types of applications and reach an even wider community interested in contribution and adoption.

Website: https://keycloak.org
GitHub: https://github.com/keycloak
License: Apache License, Version 2.0


The team is happy and willing to present the project in more detail. Please let me know if any of you are able to sponsor so we may move forward.


Thanks,

Erin



Re: sponsor for sandbox - Keycloak

Quinton Hoole
 

SGTM.  I am available to sponsor. 
Is there an opportunity to share further information in-person at KubeCon Seattle?
Posting a link to the slide deck that was to be used in early October here would be useful.  
I would be in support of following that up with a presentation to interested parties as soon as is practical.  Chris A manages the backlog and can help with that.

Q

Quinton Hoole

Technical Vice President

America Research Center

2330 Central Expressway, Santa Clara, CA 95050

Tel: 408-330-4721   Cell: 408-320-8917   Office # C2-27

Email: quinton.hoole@...   ID#Q00403160


From: <cncf-toc@...> on behalf of Erin Boyd <eboyd@...>
Date: Tuesday, November 27, 2018 at 07:46
To: CNCF TOC <cncf-toc@...>
Subject: Re: [cncf-toc] sponsor for sandbox - Keycloak

A little more infomation (the draft proposal):

https://github.com/bdaw/toc/blob/master/proposals/keycloak.md

On Tue, Nov 27, 2018 at 8:41 AM Erin Boyd <eboyd@...> wrote:
Hi TOC,
I am soliciting a sponsor for  the Keycloak project. They were set to preset to the TOC the first week of October and were bumped. Now, following the newer Sandbox process they are looking for a sponsor.

Keycloak is an Open Source Identity and Access Management Solution for today’s Cloud Native Applications and Services. It provides an easy way to secure applications and services with minimum effort.

The Keycloak team believes that this project aligns well with section 1(c) of the CNCF Charter by providing a standard and simple way to secure Cloud Native applications and services. Out of the box, Keycloak provides an extensive set of features such as user federation, admin console and account management console. Securing applications and services can be done with only a few lines of code through Keycloak adapters that are provided for a range of languages and frameworks. Keycloak also provides both OpenID Connect and SAML 2.0 enabling any application that have support for either to be easily secured.

With it's already large community support, bringing Keycloak into the CNCF, the team hopes to continue to expand the list of features, making it even easier to secure different types of applications and reach an even wider community interested in contribution and adoption.

Website: https://keycloak.org
GitHub: https://github.com/keycloak
License: Apache License, Version 2.0


The team is happy and willing to present the project in more detail. Please let me know if any of you are able to sponsor so we may move forward.


Thanks,

Erin



Re: sponsor for sandbox - Keycloak

Erin Boyd
 

A little more infomation (the draft proposal):

https://github.com/bdaw/toc/blob/master/proposals/keycloak.md


On Tue, Nov 27, 2018 at 8:41 AM Erin Boyd <eboyd@...> wrote:
Hi TOC,
I am soliciting a sponsor for  the Keycloak project. They were set to preset to the TOC the first week of October and were bumped. Now, following the newer Sandbox process they are looking for a sponsor.

Keycloak is an Open Source Identity and Access Management Solution for today’s Cloud Native Applications and Services. It provides an easy way to secure applications and services with minimum effort.

The Keycloak team believes that this project aligns well with section 1(c) of the CNCF Charter by providing a standard and simple way to secure Cloud Native applications and services. Out of the box, Keycloak provides an extensive set of features such as user federation, admin console and account management console. Securing applications and services can be done with only a few lines of code through Keycloak adapters that are provided for a range of languages and frameworks. Keycloak also provides both OpenID Connect and SAML 2.0 enabling any application that have support for either to be easily secured.

With it's already large community support, bringing Keycloak into the CNCF, the team hopes to continue to expand the list of features, making it even easier to secure different types of applications and reach an even wider community interested in contribution and adoption.

Website: https://keycloak.org
GitHub: https://github.com/keycloak
License: Apache License, Version 2.0


The team is happy and willing to present the project in more detail. Please let me know if any of you are able to sponsor so we may move forward.


Thanks,

Erin



sponsor for sandbox - Keycloak

Erin Boyd
 

Hi TOC,
I am soliciting a sponsor for  the Keycloak project. They were set to preset to the TOC the first week of October and were bumped. Now, following the newer Sandbox process they are looking for a sponsor.

Keycloak is an Open Source Identity and Access Management Solution for today’s Cloud Native Applications and Services. It provides an easy way to secure applications and services with minimum effort.

The Keycloak team believes that this project aligns well with section 1(c) of the CNCF Charter by providing a standard and simple way to secure Cloud Native applications and services. Out of the box, Keycloak provides an extensive set of features such as user federation, admin console and account management console. Securing applications and services can be done with only a few lines of code through Keycloak adapters that are provided for a range of languages and frameworks. Keycloak also provides both OpenID Connect and SAML 2.0 enabling any application that have support for either to be easily secured.

With it's already large community support, bringing Keycloak into the CNCF, the team hopes to continue to expand the list of features, making it even easier to secure different types of applications and reach an even wider community interested in contribution and adoption.

Website: https://keycloak.org
GitHub: https://github.com/keycloak
License: Apache License, Version 2.0


The team is happy and willing to present the project in more detail. Please let me know if any of you are able to sponsor so we may move forward.


Thanks,

Erin



Re: RFC: containerd graduation review

alexis richardson
 

Brian

The containerd folks made a good presentation last week. In the Q&A
afterwards both Quinton and I were asking if you could provide more
colour on why you think they are ready to graduate, possible gotchas
etc.

a

On Tue, Nov 20, 2018 at 4:51 PM Chris Aniszczyk
<caniszczyk@...> wrote:

The containerd team presented to the TOC and community today about graduating.

They are asking for final feedback on the proposal:
https://github.com/cncf/toc/pull/165

If there are no strong objections after a week and the original TOC sponsor, Brian Grant is in support, I will call for a formal vote from the TOC.

Thanks!

--
Chris Aniszczyk (@cra) | +1-512-961-6719


Re: [VOTE] Harbor moving to incubation

Jimmy Song <jimmysong@...>
 

+1 non-binding
---------------------------------------
Best Regards.
 
Jimmy Song(宋净超)

Developer Advocate
Ant Financial
CNCF Ambassador
Co-founder of ServiceMesher community
 
WeChat: jimmysong






On Nov 21, 2018, at 10:08 PM, Jonathan Boulle <jon@...> wrote:

+1 binding

On Fri, 9 Nov 2018 at 17:31, Ayrat Khayretdinov <akhayretdinov@...> wrote:
+1 non-binding

On Tue, Nov 6, 2018, 09:27 Chris Aniszczyk <caniszczyk@... wrote:
The Harbor community has requested to move to the incubation maturity level and believes it has fulfilled the criteria: https://github.com/cncf/toc/pull/163

They have also created a presentation on top of the proposal for the community: https://docs.google.com/presentation/d/1aBQnE96kKatc1_t3E97lJBwiWvL-3GTitojuv-nWMuo/edit?usp=sharing

Document that it is being used successfully in production by at least three independent end users which, in the TOC’s judgement, are of adequate quality and scope: https://github.com/goharbor/harbor/blob/master/ADOPTERS.md

Maintainers of the project are listed in https://github.com/goharbor/harbor/blob/master/OWNERS.md

Maintainers are added and removed from the project as per the policies outlined in the project governance: https://github.com/goharbor/community/blob/master/GOVERNANCE.md

Demonstrate a substantial ongoing flow of commits and merged contributions:

Releases: 7 major releases - https://github.com/goharbor/harbor/releases
Roadmap: https://github.com/goharbor/harbor/wiki/Harbor-Roadmap
Contributors: https://github.com/goharbor/harbor/graphs/contributors
Commit activity: https://github.com/goharbor/harbor/graphs/commit-activity
CNCF DevStats: https://harbor.devstats.cncf.io

Please vote (+1/0/-1) by replying to this thread; the full proposal located here: https://github.com/cncf/toc/pull/163

Remember that the TOC has binding votes only, but we do appreciate non-binding votes from the community as a sign of support!

--
Chris Aniszczyk (@cra) | +1-512-961-6719



5001 - 5020 of 7724