Reminder: nominations close at 12 noon Pacific time tomorrow! 

On Thu, Dec 19, 2019 at 10:09 AM Amye Scavarda Perrin <amye@...> wrote:

Based on both feedback from the community and the amount of nominations currently in, we're extending the nomination deadline to January 4, 2020 at 12 PM Pacific. 

This applies to all nominations.

Current count for nominations as of 10am Pacific:

GB: 4
End-user: 2
Maintainer: 4 

Updated Timeline:

December 12: Nominations open – 12 PM PT
WAS: Dec 20: Nominations close (last day of business before holiday) – 12 PM PT

NOW: Jan 4, 2020 - 12 PM PT -- this is a Saturday! 
Jan 6: Qualification period opens
Jan 20: Qualification period closes
Jan 20: Election opens, Voting occurs by a time-limited Condorcet-IRV ranking in CIVS
Feb 1: Election closes
Feb 3: Election results posted

If you have questions, CNCF staff (myself and others) will be watching over the mailing lists, the slack channels:#elections and #toc and email over the next two weeks. Responses may be delayed, but we will be responding! 

Let me know if you have questions on this. 

-- amye 

--

Amye Scavarda Perrin | Program Manager, CNCF | amye@...

--

Amye Scavarda Perrin | Program Manager, CNCF | amye@...

On Dec 17, 2019, at 2:21 PM, Joe Beda via Lists.Cncf.Io <jbeda=vmware.com@...> wrote:



This email is from an external sender.

+1 assuming that this takes effect as the size of the TOC increases (as in we give folks fair warning that this will happen as we seat the new members)

 

From: <cncf-toc@...> on behalf of Liz Rice <liz@...>
Date: Tuesday, December 17, 2019 at 12:41 PM
To: "cncf-toc@..." <cncf-toc@...>
Subject: [cncf-toc] [VOTE] Increase Sandbox requirement to three sponsors from the TOC

 

As discussed earlier, I’m proposing that we change the requirement to join Sandbox to three TOC sponsors (up from two) as we are increasing the size of the TOC from 9 to 11 seats.

--

Liz Rice

@lizrice | lizrice.com | +44 (0) 780 126 1145

+1 binding


from Alimail iPhone

------------------------------------------------------------------
发件人：Brian Grant via Lists.Cncf.Io<briangrant=google.com@...>
日　期：2019年12月20日 02:50:38
收件人：Liz Rice<liz@...>
抄　送：<cncf-toc@...>
主　题：Re: [cncf-toc] Proposal - change one word in TOC Charter

+1 binding

On Tue, Dec 17, 2019 at 12:37 PM Liz Rice <liz@...> wrote:

+1 as well

On 17 Dec 2019, 20:13 +0000, Joe Beda via Lists.Cncf.Io <jbeda=vmware.com@...>, wrote:

+1 Would love to see us make this change.

On 12/17/19, 10:39 AM, "cncf-toc@... on behalf of alexis richardson" <cncf-toc@... on behalf of alexis@...> wrote:

Folks

NOTE Clause 6.d.ii in the TOC charter:
https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fcncf%2Ffoundation%2Fblob%2Fmaster%2Fcharter.md%236-technical-oversight-committee-toc&;data=02%7C01%7Cjbeda%40vmware.com%7Ce4461a3054ef4ab82f6608d7832069e1%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637122047561995158&amp;sdata=uHq8dO6Fb4CaKAtbYnLCj3gXSzN8SGNv7%2BzD4zl9uJU%3D&amp;reserved=0

It says:
"ii. demonstrate an advanced level of professional experience as
engineers in the scope of CNCF"

As the TOC looks after ALL aspects of projects, community, etc, not
just "engineering".... I propose that we change "engineers" to
"technologists".

I'd be happy to say more about why, not least that IANAE myself. But
honestly I think the reasons should be fairly obvious.

alexis

------------------------------------------------------------------
发件人：Brian Grant via Lists.Cncf.Io<briangrant=google.com@...>
日　期：2019年12月20日 02:50:38
收件人：Liz Rice<liz@...>
抄　送：<cncf-toc@...>
主　题：Re: [cncf-toc] Proposal - change one word in TOC Charter

+1 binding

On Tue, Dec 17, 2019 at 12:37 PM Liz Rice <liz@...> wrote:

+1 as well 

On 17 Dec 2019, 20:13 +0000, Joe Beda via Lists.Cncf.Io <jbeda=vmware.com@...>, wrote:

+1 Would love to see us make this change.

On 12/17/19, 10:39 AM, "cncf-toc@... on behalf of alexis richardson" <cncf-toc@... on behalf of alexis@...> wrote:

Folks

NOTE Clause 6.d.ii in the TOC charter:
https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fcncf%2Ffoundation%2Fblob%2Fmaster%2Fcharter.md%236-technical-oversight-committee-toc&amp;data=02%7C01%7Cjbeda%40vmware.com%7Ce4461a3054ef4ab82f6608d7832069e1%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637122047561995158&amp;sdata=uHq8dO6Fb4CaKAtbYnLCj3gXSzN8SGNv7%2BzD4zl9uJU%3D&amp;reserved=0

It says:
"ii. demonstrate an advanced level of professional experience as
engineers in the scope of CNCF"

As the TOC looks after ALL aspects of projects, community, etc, not
just "engineering".... I propose that we change "engineers" to
"technologists".

I'd be happy to say more about why, not least that IANAE myself. But
honestly I think the reasons should be fairly obvious.

alexis

On 19 Dec 2019, at 11:05, Liz Rice <liz@...> wrote:



That's great, thanks Amye! 

--

Liz Rice

@lizrice | lizrice.com | +44 (0) 780 126 1145

On 19 Dec 2019, 18:27 +0000, alexis richardson <alexis@...>, wrote:

Thank you very much 

On Thu, 19 Dec 2019, 18:09 Amye Scavarda Perrin, <ascavarda@...> wrote:

Based on both feedback from the community and the amount of nominations currently in, we're extending the nomination deadline to January 4, 2020 at 12 PM Pacific. 

This applies to all nominations.

Current count for nominations as of 10am Pacific:

GB: 4
End-user: 2
Maintainer: 4 

Updated Timeline:

December 12: Nominations open – 12 PM PT
WAS: Dec 20: Nominations close (last day of business before holiday) – 12 PM PT

NOW: Jan 4, 2020 - 12 PM PT -- this is a Saturday! 
Jan 6: Qualification period opens
Jan 20: Qualification period closes
Jan 20: Election opens, Voting occurs by a time-limited Condorcet-IRV ranking in CIVS
Feb 1: Election closes
Feb 3: Election results posted

If you have questions, CNCF staff (myself and others) will be watching over the mailing lists, the slack channels:#elections and #toc and email over the next two weeks. Responses may be delayed, but we will be responding! 

Let me know if you have questions on this. 

-- amye 

--

Amye Scavarda Perrin | Program Manager, CNCF | amye@...

Thank you very much 

On Thu, 19 Dec 2019, 18:09 Amye Scavarda Perrin, <ascavarda@...> wrote:

Based on both feedback from the community and the amount of nominations currently in, we're extending the nomination deadline to January 4, 2020 at 12 PM Pacific. 

This applies to all nominations.

Current count for nominations as of 10am Pacific:

GB: 4
End-user: 2
Maintainer: 4 

Updated Timeline:

December 12: Nominations open – 12 PM PT
WAS: Dec 20: Nominations close (last day of business before holiday) – 12 PM PT

NOW: Jan 4, 2020 - 12 PM PT -- this is a Saturday! 
Jan 6: Qualification period opens
Jan 20: Qualification period closes
Jan 20: Election opens, Voting occurs by a time-limited Condorcet-IRV ranking in CIVS
Feb 1: Election closes
Feb 3: Election results posted

If you have questions, CNCF staff (myself and others) will be watching over the mailing lists, the slack channels:#elections and #toc and email over the next two weeks. Responses may be delayed, but we will be responding! 

Let me know if you have questions on this. 

-- amye 

--

Amye Scavarda Perrin | Program Manager, CNCF | amye@...

On Dec 17, 2019, at 8:43 AM, alexis richardson <alexis@...> wrote:

+1 binding

TOC & Falco folks,

I think it is really important to keep adding these use cases.  If
Falco passes into Incubation, I suggest the TOC table this as a review
item for one year's time.  The project shows promise but needs a solid
production user base.

alexis

On Tue, Dec 17, 2019 at 1:30 PM Michael Ducy <michael.ducy@...> wrote:

One question I had come up regarding Falco and our incubation proposal is adoption and end users. While we are just about done with the voting process, I'd still like to share this video from Kubecon NA 2020.

Kris Nova co presented with Abhinav Srivastava of Frame.io on the event processing pipeline they've built for Falco. In my opinion this is one of the better examples of Falco use cases:

Abhinav's presentation starts at 45:44 (and start at 0:00 if you want a great explanation of Falco from Kris) -
https://youtu.be/Z4POV5IXnHQ?t=2744

We're hoping to have a Frame.io case study published in the coming months.

One of the Falco project's goals as we move into Incubation is to increase the number and quality of end users. Currently our end users tend to come from tech, retail, or healthcare. We want to expand this out to include more financial services, fintech, and other regulated industries. We feel there's a opportunity to help these verticals with compliance use cases, as well as expand our current compliance use cases for retail and healthcare.

Thank you to the TOC for all your support thus far,
Michael


On Tue, Dec 17, 2019 at 6:22 AM Liz Rice <liz@...> wrote:

+1 binding

(Thought I sent this yesterday but apparently not. Apologies if a dupe.)
On 17 Dec 2019, 11:20 +0000, Li, Xiang <x.li@...>, wrote:

+1 binding