►
From YouTube: CNCF TOC Meeting 2020-02-04
Description
CNCF TOC Meeting 2020-02-04
A
A
A
A
A
A
A
A
A
A
A
A
All
right,
it
is
5:00
afterwards
in
here,
so
I
think
we
will
get
going
I
know.
We
definitely
want
to
be
able
to
welcome
our
new
TOC
members
and
kick
off
our
new
group
here.
So
we'll
just
go
ahead
and
get
started
assuming
that
everything
works,
there's
both
that
goes
our
normal
and
I
trust
policy
notice.
Our
mating
logistics,
because
this
is
where
you
all
are-
and
here
is
our
TOC
members
present
today
welcome
to
our
new
TOC.
We
are
now
at
the
point
where
we
now
have
11
of
you.
A
A
Yeah
this
marks
our
first
meeting
of
the
term.
You
all
officially
are
established
as
like
real
members.
This
is
now
our
official
TOC,
so
part
of
this
is
also
being
able
to
let
the
community
know
that
if
they
are
looking
for
people
to
be
able
to
help
sponsor
either
their
sig
or
some
of
their
projects-
and
these
are
the
people
to
be
able
to
go
to-
and
you
know
that's
that's
basically,
it
yeah
anything.
C
Hello,
thank
you
very
much.
The
main
toners
appointing
me
I
think
it's
really
exciting
that
we've
got
to
maintain
a
position.
That's
measured
by
the
maintain
is
because
there's
extremely
important,
important
people
in
this
group
and
if
you
don't
know
me
I'm,
always
happy
to
talk
to
people
I'm
based
in
the
UK
but
I'm
in
the
in
the
u.s..
A
lot
so
feel
free
to
ping
me
and
I
love
to
talk
to
you.
D
On
the
same
note,
I'm
not
sure
if
Erin
can
hear
me
but
hi.
My
name
is
Katie
and
I'm
very,
very
excited
to
be
part
of
the
TLC
member
board,
I'm,
looking
very
looking
forward
to
collaborate
with
everyone
and
I'm
based
in
London
as
well.
So
as
previously
mentioned,
if
you
have
any
questions
regarding
anything,
I
would
be
more
than
happy
to
help.
E
D
F
Hello,
everyone,
my
name,
is
Todd
I,
am
also
based
in
the
Bay
Area,
very,
very
excited
to
be
part
of
the
TOC
and
feel
free
to
reach.
Out
to
me,
my
email
address
is
they're
very
excited
to
listen,
learn,
understand
what
problems
folks
are
facing
and
look
forward
to
helping
work
with
this
community
to
address
those.
A
A
G
We've
had
for
the
storage
use
case
library,
which,
which
was
a
reminder.
This
is
this
going
to
be
a
library
to
cover
best
practice
and
different
options
for
how
to
deploy
storage
for
four
different
use
cases
where
we've
we've
come
up
with
the
first
set
of
categories
that
we're
going
to
be
that
we're
going
to
be
working
on
and
we'll
have
updated
templates.
G
Shortly
again,
we
want
to
launch
the
use
case
with
the
first
five
or
six
use
case
categories
for
cube,
gun
we've
been
discussing
the
the
process
and
the
template
for
sandbox
and
incubation
processes.
Aaron
has
put
together
the
the
merged
documents
from
that
that
were
available
from
the
different
templates
in
the
different
six.
G
It
would
be
really
great
if
we
could
get
reviews
and
comments
on
that
and
I
suspect,
obviously
that
that
will
be
the
topic
for
the
talk
and
sig
chairs
meeting
too
and
then
finally,
we
re
reviewed
dragonfly,
including
installing
it
and
they
some
sort
of
basic
failure.
Testing
I
will
said:
we've
sent
feedback
and
clarifying
questions
back
to
the
project
team
as
soon
as
we
get
the
responses
for
that
will
incorporate
it
into
the
due
diligence
document
and
finally,
project
Harbor.
A
G
A
B
A
Here
but
okay
yeah
we've
got
our.
These
folks
are
working
on
the
final.
My
project
review.
I
know
this
is
something
a
lot
of
people
have
been
asking
about
as
far
as
what's
going
on
with
like
how
our
projects
are
moving
through
and
I
think
this
is
a
pretty
good
example
of
being
able
to
say
which
projects
are
actually
in
flight.
A
A
H
So
a
few
updates,
so
the
sick
got
approved
a
couple
weeks
ago.
So
thank
you
for
one
vote.
It
approved
so
we're
looking
at
meeting
next
thursday
and
there's
going
to
be
a
presentation
on
sandbox
presentation
on
volcano
and
then
we'll
make
a
recommendation
and
based
on
that
we'll
talk
to
the
TAC
members.
H
Whether
we
want
to
make
that
to
go
forward
with
that
or
not,
and
then
next
up
would
be
Kido
that
sorry
volcano
is
batch,
workloads
and
kubernetes
natively
and
then
next
up
is
Keita.
That's
kubernetes,
event-driven
auto-scaling!
That's
also
scheduled
for
sandbox
review
and
we're
scheduling
that
meeting
two
weeks
from
Thursday.
So
then,
the
next
meeting
after
that,
the
one
that
we
have
coming
up
and
harbor
so
I
heard
from
this
six
storage
folks
that
they're
actually
waiting
for
us,
so
so
we're
actually
waiting
for
some
more
critical
mass
in
they're
sick.
H
So
this
he
just
got
approved.
So
once
we
get
more
critical
mass,
then
we'll
start
doing
the
due
diligence
and
as
far
as
the
runtime
components
for
hardware,
the
other
update
that
I
have
a
drone.
Amy
I
don't
think
we
have
enough
quorum
in
this
meeting,
so
I'd
like
to
call
a
vote
for
the
new,
a
new
co-chair,
that's
Diana,
Fatima
from
Red
Hat,
so
I'm
looking
for
suggestions
about
what
will
be
the
best
course
of
action
here.
So
that
thing.
H
Great
great
awesome
so
in
and
then
so
we
have
a
new
tech
leads
and
contributors,
so
we
have
Urvashi
from
Red
Hat
and
then
Peng
from
Microsoft,
sorry
and
actually
think
I
lost
my
slides
here
so
yeah
so
and
then
we
have
more
now
Patel
from
from
Red
Hat.
So
I'm
gonna
nominate
those
two
folks.
So
so
the
process
for
nominating
tech
leads
is
in
it's
a
2/3
vote
from
the
co-chairs
in
2/3
vote
from
the
TOC
right.
H
G
Think,
just
to
just
clarify
this,
the
last
time
that
we
wanted
to
ant
a
co-chair
or
or
a
tech
lead
we
just
needed.
According
to
the
city
charter,
we
just
need
a
two-thirds
majority
of
the
COC
members
to
vote
server.
So
I
don't
know
if
we
have
quorum
today,
but
we
can
possibly
do
a
verbal
throat
or
or
and
maybe
they're
at
final
separately.
If,
if
there
aren't
enough
people
online
yeah.
A
A
A
A
C
H
H
Okay,
yeah
so
Diane
Fatima,
she's
interested
in
being
the
Sikh
runtime
co-chair
she's,
a
principal
software
engineer
at
Red
Hat
in
the
AI
Center
of
Excellence
in
the
CTOs
office.
I
have
a
background
in
high-performance
computer
and
have
and
have
been
working
on,
AI
machine
learning,
applications
and
benchmarking
at
Red
Hat
for
seven
years,
I'm
interested
in
this
role,
because
I'm
working
with
our
hardware
partners
to
enable
hardware,
acceleration,
GPU,
FPGAs,
etc.
That
will
run
on
kubernetes
and
OpenShift
and
there's
something
to
that.
Her
LinkedIn
profile
placed
it
on
the
chat
there.
A
A
A
G
A
Co-Chair
excellent
vote
is
plus
one
from
Matt
Klein,
plus
one
from
judgment,
Cormac,
+1,
jangly,
Michelle,
Katie,
Shanley
and
and
a
verbal
plus
one
from
Brandon,
so
this
passes.
Thank
you
all
cool
I'm
glad
we
had
everyone
here
for
this
all
right.
Anything
else
that
we
needed
to
be
able
to
talk
about
for
sig,
run-time.
I
H
A
A
A
I
So
we
have
been
meeting
on
the
first
and
third
Thursday
of
every
month
and
have
had
quite
a
bit
of
interest
and
so
definitely
would
enjoy
others,
and
especially
the
new
TMC
members.
If
you
wanted
to
kind
of
join
us
sometime
and
check
out
what
we're
talking
about,
you're
welcome
to
and
it's
been
matt
has
been
doing
a
great
job
of
keeping
us
on
task,
and
you
can
see
how
to
connect
with
us
and
there's
really
nothing
else
like
not
update
thanks.
J
Everyone
good
morning
afternoon
evening,
wherever
you
are
I,
am
Paris
work
at
Google
I
used
to
do
this
contributor
experience
thing
for
kubernetes
for
a
while
nice
to
meet
you
all
Josh,
say
hello
as
well:
Josh
burkas
you
probably
have
to
code.
Eight
all
right,
Josh
is
another
ring
leader
for
this,
and
it's
been
a
great
help.
J
So
for
those
that
were
not
on
the
lines
for
the
last
two
TOC
calls,
we
proposed
this
little
shindig
of
a
thing
called
contributor
experience,
but
we've
changed
the
name
because
we
do
not
want
to
duplicate
kubernetes
community
and
thus
confuse
folks
further,
so
we're
looking
at
contributor
strategy.
What
do
you
all
think
I'll?
J
Ask
you
at
the
end,
so
some
of
the
areas
that
we're
going
to
be
focusing
on
from
from
our
proposal
standpoint
is
project
governance,
Josh,
taking
taking
much
of
that
contributor
outreach
in
growth
and
maintainer
health
and
leadership
circles,
which
I
can
explain
in
a
minute,
but
all
of
these
things
would
equate
and
boil
up
to
ultimately
a
contributing
MD
project
health
check
for
evaluation
period,
storing
during
C
and
C
F
projects.
No,
that
doesn't
mean
we're
going
to
audit
that
we're
going
to
audit
you're
contributing
markdown
file.
J
J
Please
help
us
how
we're
gonna
do
this
is
get
involved
with
more
project
mailing
lists,
email,
our
Charter
out
to
folks
try
to
get
some
people
to
help
us
form
working
groups
for
each
of
these
focus
areas.
We
already
have
some
of
those
going,
but
you
can
see
on
our
baby.
Actually,
if
you
update
the
slides,
if
you
hit
refresh
you're
gonna,
get
it
updated,
you
can
get
an
updated
deck.
J
You
know
what
you
it
right
now,
but
in
the
in
the
updated
deck
there
is
a
link
to
the
Charter,
and
things
like
that
you
can
check
out
and
help
us
get.
The
word
out,
there's
actually
a
parking
lot
of
future
road
map,
things
that
we
could
do
if
we
had
to
help
to
do
it.
Josh
and
I
have
done
a
lot
of
those
things
before,
for
instance
like
contributor
metrics,
for
instance,
but
we
just
don't
have
the
help
right
now.
We
want
to
focus
because
they
can
get
sort
of
broad
fast.
J
Some
other
things
we're
gonna
do
is
be
dressing
guidelines,
documentation,
evaluation
criteria
again
for
that
health
check
status,
check
of
projects
as
it
relates
to
their
contributor
activities
and
then,
of
course,
continue
with
discovery,
because
we
want
to
hear
what
projects
actually
need.
We
already
have
a
ton
of
information
from
TLC
members
like
Matt,
with
his
information
about
like
what
projects
need
doc,
as
well
as
like
Chris,
a
is
done.
J
Maintainer
surveys
in
the
past
was
CN
CF,
so
we
do
have
some
of
that
data
as
well,
and
then
we
can
do
some
immediate
impact,
things
Josh
and
I,
and
a
lot
of
other
people
that
have
shown
interest
already
have
tons
of
training,
materials,
talks,
etc.
On
things
like
hey,
we
use
Help
Wanted
an
issue
and
good
first
issue,
but
we're
still
not
getting
people
like
what's
next
or
hey
I
have
a
contributing
markdown
file.
So
what
trainings
like
that
like?
J
J
K
No
it's
about
it.
So
next
meeting
we'll
be
finishing
up
the
initial
charter
because
of
the
nature
of
the
city,
we
want
to
have
that
Turner,
a
lot
more
nailed
down
than
necessarily
others
see.
Charters
have
been
for
that
matter
as
a
demonstration
as
part
of
a
charter.
We
want
to
actually
outline
the
process
of
handling
working
groups
within
a
sig,
because
the
CNC
F
has
not
had
that
sort
of
process
documented
before
since
its
new.
K
A
I'm
doing
the
the
hand
wave
back
and
forth
because,
like
I'm
not
necessarily,
certainly
we
need
to
be
able
to
have
like
a
direct
TOC
meeting
vote
for
it.
What
typically
happens
is
that
everybody
does
exactly
what
you're
doing
right
now
is
like
man
look
at
our
charter,
I'll
kind
of
put
together
and
like
we
like
it
enough
that
we
would.
We
would
agree
to
be
able
to
do
this,
and
then
you
put
it
into
a
PR
and
that's
where
we
run
a
vote
firm.
J
J
J
J
Conversation
is
anybody
upset
with
our
initial
focus
areas,
because
the
deal
is
like
it's
humans
right,
we've
got
like
50
million
things
that
we
could
do
for
these
projects,
but
like?
How
can
we
boil
this
down
to
impact
the
most
projects
with
I
mean
Josh
and
myself
and
I
think
Jared
and,
like
maybe
a
few
others
said
that
that
we
have
like
six
to
eight
hours
a
week,
for
instance,
like
we
even
like,
went
to
the
Nitty
Gritty,
so
it's
like
well,
how
can
we
invest
our
skyline
here
wisely?
That
impacts
the
most.
A
H
In
Paris
this
is
a
Ricardo
yeah.
I
think
this
is
great,
I,
think
yeah.
Initially,
you
might
want
to
focus
a
little
bit
on.
You
know,
kind
of
you
make
make
it
smaller.
You
know,
start
small
and
then
go
from
there.
So
cuz
there's
a
lot
of
different
aspects,
and
you
know
and
helping
our
contributors
and
I
for
me,
I
think
one
of
the
important
ones
is
maintaining
our
health.
H
J
Sure
and
that's
the
circles
that
I
didn't
really
go
into,
which
is
focus
groups
honestly.
I
know
that
sounds
weird.
It's
not
like
focus
groups
isn't
like
we're.
Just
gonna
get
marketing
out
of
you
all,
but
it's
like
circles
and
you're
also
going
to
provide
camaraderie,
and
some
of
you
already
may
be
in
leadership
circles
outside
of
open
source,
maybe
like
at
your
company
or
something
where
everybody
gets
together.
J
And
you
know
you
share
things
and
like
share
best
practices
and
whatnot,
but
that's
really
also
where
we
can
hear
as
a
cig
to
what
needs
to
happen
and
what
we
need
to
do
to
make
things
better.
So
it's
sort
of
a
kind
of
a
really
great
feedback
loop
for
us
and
then
also
provide
training
to
you
specifically
as
mentors,
and
then
we
can
even
talk
about
some
of
the
hard
stuff
like
burnout
as
well.
So
that's
kind
of
what
I
meant
by
circles.
B
B
J
That's
honestly,
that
was
about
to
be
the
fourth
bullet
Michele,
honestly,
the
fourth
leg,
a
jaw
you
know
Josh
has
been
like
trendabl,
that's
I
know,
that's
that's.
Definitely
on
the
try.
That's
in
the
Charter
as
well.
Honestly,
it's
one
of
our
pillars,
I
think,
and
we
just
want
more
help.
So
we
know
how
to
do
it
like
I
feel
like
I
know,
I
have
some
ideas
as
well,
so
if
we
can
recruit
some
more
help,
that's
gonna
be
the
fourth
bullet
yeah.
B
Awesome
I
think
she'll
be
a
great
resource,
I
mention
we
can
just
make
sure
the
scope
that
y'all
have
to
find
here.
It
looks
great
to
me
this
is
a
great
free,
starting
point,
great
charter.
We
can
just
go
forward
and
and
see
you
know
how
much,
how
much
Cheryl
needs
in
terms
of
interaction,
I,
think
she's
she's
got
a
really
good
grasp
on
how
to
communicate
with
the
end
user,
members
and
and
I'm
sure
she
can
be
a
great
resource
here.
J
And
yeah
we
have
some
best
practices
to
with
like
we're
trying
to
create
these.
You
know
user
groups
within
the
kubernetes
upstream
community,
probably
very
similar
to
like,
what's
going
on
here,
we're
you
know,
obviously
users
wanting
a
feedback
to
us,
but
don't
necessarily
want
to
come
to
a
cig
meeting.
So
maybe
we
could
do
that
on
a
larger
scale,
collectively
too,
and
again
yet
reason
455
as
to
why
I
want
to
do
this
thing
so
yeah
together.
I
H
You
guys
have
a
plan
to
grow
this
thing.
Yeah
I
mean
in
terms
of
like
getting
more
people
trying
to
get
more
people
involved
right.
So
you
know
I
think
you
talked
about
like
kubernetes
user
groups,
you
guys
have
any
list
of
things.
I
think
it
would
be
a
good
idea
to
come
up
with
a
list
of
things
of
you
know,
places
that
you
can
reach
out
and
and
try
to
get
people
involved
in
the
sake,
because
it
sounds
like
there's
a
lot
of
work
to
do.
Yeah.
J
Yeah
there's
actually
on
the
updated
slide.
I
I
was
like
doing
slides
literally
like
during
this
meetings.
You
know,
that's
me
and
attention
anything
anyway.
I
know,
there's
on
the
updated,
slides
I
have
a
little
bit
more
about
that
bullet
for
recruit
more
people.
So,
if
you're
on
the
slides
the
live
slides
now
we
definitely
intend
on
doing
sort
of
a
campaign.
J
Once
we
have
the
Charter
flushed
out
the
campaign
being
going
to
Moore's
project
mailing
lists
like
y'all
stuff,
mailing
lists,
also
using
and
trying
to
beef
up
the
maintainer
list
that
CN
CF
has
to
to
get
some
more
collective
voices
on
there
also
reach
out
to
Sheryl,
which
is
what
we
just
discussed
and
try
to
get
some
more
time
in
front
of
the
end
user,
community,
officially
informally,
and
figure
out
some
more
some
strengths.
Some
you
know
some
strengthening
strengthening
the
pipeline
there
and
then,
of
course,
also
going
to
kubernetes.
J
I,
know
a
lot
of
humanities
folks
that
are
interested
in
this
as
well
to
collaborate,
so
I
think
once
we
get
started
and
once
we
get
up
off
the
ground
and
get
a
charter
and
get
some
more
communication
pipelines
going
so
slack
and
our
mailing
lists
and
things
like
that
for
now,
we
just
don't
have
any
way
for
people
to
contact
us
unless
they
like
know
me
and
Josh,
and
some
of
the
other
people
that
have
come
forward
of
interest.
So
I
think
once
we
get
going
we're
gonna,
we're
gonna,
see
some.
J
D
D
A
One
of
the
things
that
we
do
try
to
do
for
the
sig
is
to
be
able
to
make
sure
that
all
of
them
get
a
session
at
cube
con
at
this
point
in
time.
I
can't
guarantee
that
there's
going
to
be
exact
session
for
them,
but
we
will
make
sure
that
there
is
time
to
be
able
to
meet
with
all
of
the
sega's
at
cube.
Con
awesome.
A
Okay,
I
will
actually
move
us
on
here,
assuming
that
I
can
get
us
do
that
and
drop
in
towards
there.
We
go
here's
your
updated,
revised
charter
thing
and
here
for
to
contribute
strategy.
I
think
we've
probably
gone
through
most
of
this,
and
we
can
move
on
towards
process
updates,
but
before
we
do,
I
know
that
there
was
another
sig
that
wants
to
be
able
to
talk
about
forming
in
here
that
doesn't
necessarily
have
slides
today.
Matt
in
the
interest
of
time,
are
you
willing
to
be
able
to
talk
about
your
sig
observability.
L
Yes,
I
can
be
brief
right
and
gone
hi
everybody.
My
name,
is
Matt
I've
generated
and
drafted
a
very
early
proposal
for
a
charter
for
one
of
the
proposed
SIG's
observability
observability
is
something
that
really
touches
everyone
and
that's
all,
and
so
it
seemed
like
a
no-brainer
and
I've
always
been
a
geek
for
logging
monitoring,
alerting
tracing
and
the
like.
L
L
L
Clearly
so
I
welcome.
All
feedback
and
I'm
super
excited
to
meet
many
of
you
and
see.
If
we
can
launch
this
I
think
given
the
breadth
of
tooling
that
exists
and
what's
going
on
in
the
whole
ecosystem,
around
monitoring
and
observation
of
cloud
native
systems
and
not
just
you
know,
capturing
you
know
the
three
pillars
but
gaining
meaningful
insights
into
the
behavior
of
these
very
complex
systems.
At
ever
code.
L
Here
we
run
a
cloud
engineering
team
and
we
every
day
work
with
all
of
our
engineering
teams
and
our
problems
and
our
challenges
and
our
opportunities
are
not
unique.
So
with
that
I'll
be
done,
I'll
have
a
male
out
to
whatever
the
right
email
verses,
but
thank
you
so
I'm,
looking
forward
to
meeting
with
it's.
A
Good
to
be
able
to
see
this
rise,
and
this
is
something
we
were
talking
about
at
the
end
of
last
year
as
something
that
was
really
missing
for
the
SIG's
so
happy
to
be
able
to
take
input
on
this
happy
to
be
able
to
see
who
of
the
TOC
would
like
to
be
a
liaison,
because
I
believe
that
is
one
of
the
things
you
were
missing
that
correct
me.
If
I'm
wrong,
I'm.
A
L
A
L
I
had
been
new
to
this
and
CF
t
under
user
community
I
wasn't
sure
about
process
and
administrivia,
and
such
so
I
have
a
I,
have
a
private
PR
on
my
fork,
but
I
was
assuming
that
a
Google,
Doc
or
something
else
would
be
more
conducive
to
collaboration.
So,
as
I
said,
I'll
have
an
email
out
to
the
relevant.
Is
that
Amy
will
help
me
with
after
this
and
I
look
forward
to
to
iterating.
A
Right
we
can
move
on
I
believe
if
there's
no
other
questions
all
right.
Excellent,
thank
you.
Matt
last
piece
is
here
this
morning
are
kind
of
some
process
updates
and
later
we'll
turn
it
up
towards
Michelle.
If
you're
available
to
be
able
to
talk
about
any
changes
in
the
flow
chart
where
we
are
with
that,
this
would
be
we've
short-handed
into
the
slides,
but
this
is
a
flow
chart
indicating
how
a
project
gets
into
CN
CF.
So
Michelle
are
you
available
for
that
conversation.
A
B
I
G
Don't
have
the
link
the
latest
link,
which
lays
was
working
on
for
the
for
the
process
for
the
the
process
workflow,
but
the
link
for
the
for
the
latest
consolidated
template
is,
is,
in
the
storage
sake,
update
page.
If,
if
people
would
have
a
quick
look
at
that,
so
it's
the
the
thing
that's
highlighted
in
yellow,
so
we've
taken
we've
taken,
I,
think
and
play
that
was
available
from
Sega
apps,
plus
the
template
that
was
from
sleek
storage
and
unmerged
them
together
to
have
to
have
a
comprehensive
list.
So
we'd
love
to
have
we'd
love.
F
G
Actually
most
most
of
the
most
of
the
template
was
was
based
on
our
original
cig
storage
templates,
the
one
that
we
used
when
we
were
doing
say
open
abs
and
Longhorn
and
Jarboe
FS.
And
then
we
added
in
some
of
the
content
to
to
cover
things
for
the
incubation
promotion
stage
as
well,
because
our
our
one
has
focused
primarily
on
sandbox.
M
Just
a
in
from
our
perspective,
it
was
I'm
a
little
bit
less.
It
was
less
about
adding
new
things
more
about
consolidating
a
couple
of
different
places.
That
criteria
and
and
data
points
about
the
projects
were
laid
out.
There
were
laid
out
in
various
places
and
there
were.
It
was
not
necessarily
explicit
with
whom
to
have
conversations
with
and
when,
as
those
projects
come
for
review
to
go
first,
the
cigs
or
second
to
the
cigs
to
present
twice
or
not
door.
So.
G
M
A
Ricardo
I
believe
has
actually
found
this
particular
document,
and
it
is
way
too
long
to
be
able
to
walk
through
here
in
the
last
like
bit
that
we've
got
here.
So
we'll
put
this
on
a
future
meeting,
because
I
know
this
is
going
to
be
important
for
everyone
to
be
able
to
review,
understand
and
will
be
moving
towards
a
vote.
Probably
before
cube
con
on
this.
So.