►
From YouTube: CNCF TOC Meeting - 2019-02-05
Description
Join us for Kubernetes Forums Seoul, Sydney, Bengaluru and Delhi - learn more at kubecon.io
Don't miss KubeCon + CloudNativeCon 2020 events in Amsterdam March 30 - April 2, Shanghai July 28-30 and Boston November 17-20! Learn more at kubecon.io. The conference features presentations from developers and end users of Kubernetes, Prometheus, Envoy, and all of the other CNCF-hosted projects
B
Let's,
let's
get
started,
I
think
Taylor's
got
the
got.
The
deck
will
just
quickly
go
to
terms
of
TOC
members
present
I,
think
I
have
every
everyone,
but
Brian
grant
and
Kelsey
rape
house.
It
was
seven
out
of
nine
but
we'll
I'll
check
before
the
meeting
is
over
for
others,
and
we
got
a
lot
of
outgoing
folks
here
today
too.
But
you
know
the
you
know
rough
agenda
today
is
we're
going
to
discuss
the
election
results.
Both
you
know
incoming
new
toc
members
and
provide
some
time
for
outgoing
QC
members
to
make
some
comments.
B
A
A
The
current
intent
is
that
it's
pretty
easy
to
get
into
sandbox
and
there's
no
marketing
associated
with
it
and
then
getting
into
incubation
is
pretty
high
hurdle
with
quite
a
bit
of
DD
and
then
graduation
should
cover
off
more
things
around.
You
know
community,
where
the
governance
is
in
place
and
non
technical
criteria.
However,
I
think
that
there's
an
emerging
view
that
we
do
need
to
validate
some
technical
criteria
during
the
final
graduation
step,
and
so
I
refer
you
to
the
mailing
list.
Discussion
about
that.
A
Please
pay
attention
to
that
discussion
and
contribute
I
think
over
the
next
few
months.
We
need
to
find
some
time
to
review
the
graduation
criteria,
not
by
very
much
but
by
a
bit.
Okay,
next
slide,
please
Summer
of
Code!
Please
apply
next
slide.
Please
conference
is
Chris.
What
are
we
saying
about
this
right
now.
B
A
For
China
soon
Chris,
can
you
please
look
into
the
amount
of
work
that
the
reviewers
are
doing?
I
received
some
back-channel
complaints
from
a
few
people
saying
that
they
felt
very,
very
overloaded,
with
many
many
hundreds
of
things
to
review
in
a
very
short
space
of
time
and
remarkably
few
cookies
to
justify
it.
Okay
will
do.
Thank
you
next
slide.
Please
yep.
B
Annual
report
we
just
released
it
yesterday
so
feel
free
to
take
a
look
at.
It
basically
covers
everything
we
did
in
2018
from
helping
projects,
events,
you
know,
maintainer
satisfaction
and
then
so
on.
So
please
take
a
look
and
if
you
have
any
comments
on
how
to
improve
it,
let
us
know
we
tried
to
include
a
lot
more
data
this
year
around
good.
A
A
A
B
Oh,
you
know
my
thing:
is
you
know?
First,
you
know
thanks
and
you
know
give
people
some
time
to
make
kind
of.
You
know
any
comments
or
advice
they
want
to
give
for
the
kind
of
new
TOC
based
on
their
experience.
I
know,
Ben
Ben
is
on
I
think
some
others
are
on
also.
So
it's
the
kind
of
stages
there's
to
make
any
comments.
A
C
C
Yeah,
congratulations
to
the
new
PSA.
Obviously,
I!
Think
it's
a
terrific,
TOC
and
I'm
excited
to
see
excited
was
excited
to
see
so
many
qualified
people
run
for
election
and
excited
to
see
on
a
terrifically,
well-qualified,
TLC
elected
the
the
one
piece
of
advice.
I
would
give,
is
well
Kobey's.
The
rest,
I
guess
I
think
for
each
of
you
that
are
coming
in
on
the
TOC,
try
to
figure
out
what
you
want
to
get
done
in
the
next.
C
What
they've
got
everyone's
on
a
two-year
term
right
generally
and
so
try
to
figure
out
what
you
really
want
to
get
done
over
the
next
two
years
and
I
think
it's
actually
important
to
have
have
an
agenda.
Not
I
mean
not
not.
You
should
subvert
other
things.
Don't
have
a
hidden
agenda
but
have
goals
that
you
want
to
achieve
because
I
think
it's
it's
easy
to
I
mean
I,
feel
that
honestly
personally,
I
think.
C
You
there
were
just
things
that
that
didn't
end
up
happening
for
other
reasons,
so
I
would
say,
have
an
idea
of
what
you
really
want
to
achieve
and
what
you
want.
The
CNC
you
have
to
be
I.
Think
one
open
question
is:
is
the
CNC
f
going
to
be
the
kubernetes
foundation
and
that
wasn't
the
original
intent?
C
But
you
know
maybe
that's
and
maybe
that's
something
we've
overly
resisted
or
we
overly
resisted
on
the
outgoing
TOC,
but
something
you
kind
of
consider
and
then
the
other
thing
I
would
say
is
so
have
a
kind
of
a
queer
idea.
What
you
wanna
get
done,
I
think
I
would
say.
Is
there
are
a
lot
of
financial
resources
available?
It
should
be
that
shouldn't
be
available
to
the
CN
CF.
C
C
Do
that
are
not
just
conferences
to
actually
aid
I
think
the
most
core
constituencies
we,
which
are
the
actual
communities
of
users
and
developers,
not
just
the
immediate
constituency
of
the
governing
board,
so
those
new
pieces
of
advice,
but
again
congratulations
to
everybody
and
it's
actually
well.
I
actually
will
add.
One
final
piece
of
advice:
I
think
it's
really
important
to
have
a
diversity
of
thought
on
the
TOC
and
I.
Think
that
you
want
to,
as
you
are
looking
towards
your
TOC
elected
member
I,
would
encourage
you
to
kind
of
look
at
look
for
someone.
C
That's
gonna
bring
in
a
new
perspective,
a
different
perspective,
because
I
think
a
couple
of
times
over.
We
really
appreciated
having
very
different
perspectives
and
having
pretty
different
backgrounds
and
coming
to
problems
from
different
backgrounds.
Definitely
the
most
rewarding
bit
for
me
was
getting
to
know
and
working
with
my
fellow
TSA
members
who
I
really
enjoyed
so
thanks
to
all
them
and
with
that
all
adios.
B
D
It
is
very
easy
to
it's
very
easy
for
the
group,
particularly
when
it
is
made
up
entirely
of
people
who
work
for
companies
providing
you
know
these
products
for
financial.
You
know
as
vendors,
essentially
to
really
lose
track
of
what
people
who
are
not,
who
are
not
working
for
those
companies
really
actually
need
and
want,
and
so
you
know,
make
sure
you're
really
making
a
lot
of
time
to
get
that
perspective,
because
there's
a
big
echo
chamber
effect
right
now.
D
B
A
Everybody
I
particularly
wanted
to
say
thank
you
to
everybody
who
did
the
TOC,
but
also
ask
them
to
don't
go
away.
Please
stay
with
us.
If
you
can
we'd
really
need
your
help
with
the
kinds
of
things
we
don't
know
what
all
of
them
are
yet.
So
please
PLEASE
offer
help
to
people
who
want
to
come
into
the
TOC
as
contributors
or
community
or
in
the
CEG's.
It's
very
important
to
have
continuity,
so
the
chair
election
I
am
I
could
not
be
more
relieved
to
see
this
slide.
A
I
have
to
say
it's
been
quite
a
lot
of
emotional
cost
doing
this
thing,
but
I'm
really
excited
to
see
some
strong
names
in
the
Hat.
It's
not
too
late
to
nominate
yourself
if
you're
one
of
the
handful
of
people
who
can
so
do.
Bear
that
in
mind
any
questions
about
this
and
the
timing.
The
schedule
increase
you'll
know
just
talk
us
through
the
dates
yeah.
B
Yeah
I
mean
basically,
my
goal
is
to
kick-off
the
election
today,
I'll.
Basically,
if
there's
any
other
TSU
members
that
want
to
run
please.
Let
me
know
before
the
end
of
this
meeting
and
then
I
will
kick
off
the
election
on.
Have
it
run
till
Monday
next
week
and
then
we'll
be
ready
for
the
new
toc-toc
chair
for
the
February
19th
meeting.
So.
F
F
And
just
to
be
cam
wasn't
actually
talking
about
myself
running
or
not.
I
was
actually
more
referring
to
the
person
who
may
replace
me
soon
makes
sense
for
them
to
be
able
to
be.
The
chair.
I
would
probably
kick
off
a
new
election.
Okay,
it's
luck,
I
mean
I,
think
what
it
does
is.
If
we
do
it
now,
it
means
we
kind
of
have
to
do
it
again
in
a
month
because
there's
another
candidate,
so
I,
don't
know.
Let's
maybe
figure
that
out.
F
B
B
Yeah,
so
you
know
there
was
a
lot
of
you
know,
I'm
sure,
discussion
on
the
last.
You
know
think
weeks
since
we've,
you
know,
nominate
an
elected
the
neat
new
TOC.
You
know
we
have
had
a
lot
of
private
discussion
amongst
the
current
set
of
TOC
on
ways
of
you
know,
essentially
improving
the
situation
where
we're
at
a
point
where
we
have
elected.
You
know,
there's
nine
men
on
the
TOC
and
definitely
it's
not
reflective
of
kind
of
the
wider
community
that
we
have
here.
B
So
the
TOC
is
looking
to
explore
are
kind
of
simply
other
ways
to
expand
the
diversity
in
kind
of
all
parts
of
the
CN
CF
governing
structure.
There
has
been
discussions
on
proposing
specific
changes
on
the
allocation
of
TOC
seats
right
now.
We
kind
of
have
this
structure
where
six
of
them
are
elected
by
the
governing
board.
Two
are
elected
by
the
TOC
themselves
and
one
is
elected
by
the
end-user
community
we've
had.
B
Discussions
of
you
know
essentially
giving
a
little
bit
more
variety
to
that,
where
maybe
there
are
less
governing
board
selected
seats,
more
end-user
seats,
maybe
seats
representing
developers
and
maintainer
x'.
We're
still
essentially
having
these
discussions
and
plan
to
bring
it
up
to
the
board
on
in
march.
B
A
G
I
mean
just
I
mean
for
the
record,
I
think
all
of
us.
You
know
you
hold
an
election,
you
get
results,
you
look
at
you're
like
how
did
we
end
up
here
and
so
now
we're
in
a
position
of
alright?
What
do
we
do
about
it
now,
and
so
you
know
our
lines
of
control
here
are
limited,
so
we're
gonna
do
what
we
can,
but
I
think
we
we
want
to.
Let
folks
know
that
you
know
it
doesn't
end
there.
So
I
think
that's
the
intent
here.
I
think
exactly
how
we
go
about
that.
H
B
We
have
brought
it
up
to
some
governing
board
members.
At
least
staff
has
there
hasn't
been
a
formal
discussion
between
say
the
TOC
and
the
governing
board?
Essentially,
you
know
the
way
it
works
is
we
will
be
looking
for
a
proposal
from
you
know
the
TOC
potentially
on
how
they
would
want
to
change
the
TOC
structure,
for
example,
but
it's
definitely
slotted
for
discussion
in
March
at
the
March
board
meeting
great.
B
It'll
be
up
to
the
TOC
how
they
want
to
essentially
do
this
there's
been
already
some
proposals
from
you
know,
folks,
like
Brian
grant
and
and
others,
and
how
to
structure
things,
but
I
still
think
there
it's
in
the
discussion
phase.
You
know
if
we
have
a
proposal
to
the
governing
board,
they'll
probably
have
to
discuss
it
themselves,
then
there's
a
vote
and
so
on.
B
F
Sure,
actually,
just
really
was
a
was
a
cleaner-upper
of
the
doc
I.
Think
Alexis
section
was
the
one
who
started
this
conversation
and
and
the
bulk
of
the
work
but
yeah
there's
a
document
about
there,
essentially
I
think
many
people
have
weighed
in
on
it
already.
It
sketches
out
a
plan
for
creating
CN
CF
special
interest
groups.
The
goal
you
know
as
written
almost
lions
there
is-
is
basically
to
help
the
TOC
to
scale
in
its
ability
to
service
duties
and
provide
value
to
both
the
project
and
the
end
users
of
CN
CF
technology.
F
I
won't
go
through
all
the
details
now,
but
basically,
these
things
would
be
created
by
the
TOC
and
they
would
provide
expertise
piece
for
a
valued
experts,
in
particular
fields,
to
help
the
TRC
to
evaluate
project,
to
educate
end-users
and
provide
a
various
variety
of
other
services
that
require.
You
know,
expertise,
knowledge
in
particular
domains.
F
If
you
can
maybe
flip
to
the
following
slide.
These
are
the
proposed
initial
things.
The
thinking
was
to
try
and
keep
this
list
relatively
limited,
at
least
to
start
with,
so
that
we
don't
end
up
with
a
kind
of
a
six
full
situation
where
we
have
large
numbers
of
six,
significant
percentage
of
which
are
not
very
effective.
F
If
anyone
has
any
questions,
perhaps
we
can
just
dwell
on
this
slide.
For
one
minute.
I
know
there
were
some
questions
around
which
projects
get
allocated
to
which
areas
whether
the
naming
of
the
areas
is
appropriate.
Just
to
be
clear.
These
names
about
finalized
absolutely
expect
that
the
SIG's
themselves
will
wordsmith
some
of
these
names
and
make
sure
that
the
scope
of
each
one
of
these
six
is
very
clearly
articulated
but
yeah.
If
anyone
has
any
questions
around
the
slide,
now
is
probably
a
good
time
to
chime
in.
J
A
J
A
That's
something
that
we
tried
to
clarify
in
the
original
version
that
may
have
gotten
munched.
The
CNC
FCI
group
will
not
be
part
of
this
sig.
It's
a
separate
thing
associated
with
testing
I
think
we
need
to
look
at
CI,
CD
pipelines
and
workflows
as
either
part
about
dev
or
my
preference,
separate
sig
from
app
dev
and
focus
on
app
dev
LAN
application
types,
but
that's
a
that's
a
conversation
we
can
have
offline,
but
to
your
question,
CNC
f.
Ci
is
not
part
of
this
sig.
Okay,.
J
F
G
Yeah
so
I
mean
I
I've
been
catching
up
on
this
cuz
I
hadn't
been
paying
attention
to
the
dock,
and
so
I
was
like.
Oh,
my
kind
of
I
gotta
pay
more
attention.
The
TMC
stuff
now
and
so
I
gave
it
a
rate
through
and
I.
Think
it's
great
I
did
have
some
questions
and
I
don't
have
all
the
history,
so
I
can
take
this
stuff
offline
if
y'all
want.
But
I
noticed
like,
for
example,
that
multiple
times
through
the
document,
the
phrase
on
biased
is
eatest
and
I.
G
Think
you
know
I
look
at
this
with
some
of
the
comments
coming
from
like
Brian
and
Camille
and
I'm
wondering.
Is
there
anything
as
a
TOC
that
we
can
do
to
try
and
put
some
meat
on
the
bones
of
what
does
some
bias
to
actually
mean?
How
do
we
enforce
that
and
I
do
know
that,
like
you
know,
looking
outside
of
our
little
bubble,
there
are
folks
who
have
very
strong
opinions
about
the
CN
CF
and
and
would
say
that
there's
nothing
unbiased
about
what
we
do.
G
F
A
topic:
what
I
can't
say
is
there
are
some
words
in
the
document
which
hopefully
go
towards
that,
which
is
that
we
feel
we've
articulated
that
we
would
like.
We
have
this
theory
that
that
you
know
the
rising
tide,
raises
all
boats
and
that
our
aim
is
to
rise,
the
time
which,
which
involves
basically
increasing
adoption
of
cloud
native
technologies,
not
not
to
benefit
one
project
over
another
or
one
vendor
over
another,
but
to
raise
the
tide
and
I
personally,
think.
G
Maybe
we
can
have
a
different
and
separate
discussion
about
that
at
some
point
yeah,
but
the
other
things
that
I
think
are.
You
know
one-year
terms
for
the
for
the
chairs
of
the
SIG's
with
staggered.
That
means
we're
always
going
to
be
having
elections.
I,
don't
know
if
there's
been
thought
put
into
that,
but
that
implies
an
election
every
six
months
for
every
sig
yeah.
F
G
F
G
G
G
F
Yeah
I
mean
just
just
to
be
clear
that
the
proposal
as
it
stands
at
the
moment
is
that
the
TRC,
basically
it
approves
the
chairs
and
selects
them
in
consultation
with
the
Sagan,
the
chairs
at
the
time.
So
you
know
in
practice
their
three
chairs.
You
know
they're
gonna
want
to
replace
one
or
two
of
them
every
year
or
three,
every
six
months
and
yeah
I'm,
not
sure
how
heavyweight
that
process
will
in
practice,
be
it's
not
quite
the
same,
as
you
know,
having
a
board
of
directors
elect.
You
know.
Eight
seats
on
yeah.
E
F
F
G
Then
my
final
comment
and
then
I'll
shut
up
on
this,
like
here
with
the
with
the
list
of
SIG's.
These
are
also
like
when
we
think
about
sort
of
who
are
the
sort
of
constituencies
for
the
CNCs.
Broadly,
there's
you
know,
vendors,
which
dominates
the
governing
board.
Part
of
our
job
here
is
to
look
at
the
community
in
the
projects
this.
G
G
Are
there
ideas
around
sort
of
things
that
are
more
community
focused,
more
user
focused
versus
just
project
focus
and
I'm
thinking
in
terms
of
things
that
are
cross-cutting,
because,
like
one
that
I
think
that
critical,
cigs
and
kubernetes
is
the
contributor
experience
state
which
ends
up
being
a
bit
of
a
of
a
kitchen
sink
where
we
dump
a
lot
of
stuff
in
there?
But
it
is
this
idea
of
like
how
do
we
actually
build
efficiencies
across
the
project
versus
just
focusing
on
single
technical
issues?.
F
Yeah
brief
brief
in
response
to
that
subject,
so
I
don't
I,
don't
actually
think
that
these
things
are
as
project
focused
as
they
may
come
across
what
we
have
to
assign
projects
to
SIG's,
just
because
you
know
that
was
part
of
the
intention
of
these
things.
But
if
you
look
at
the
at
the
actual
names
and
the
errors
they
cover
they're
not
actually
designed
to
fit
projects
they're
actually
designed
to
fulfill
end-user
requirements
and
to
whatever
extent
that
may
not
have
been
achieved.
We
should
perhaps
look
at
changing
things
that
the
intention
was.
F
G
So
then
my
suggestion
would
be,
as
we
present
this
to
a
wider
audience.
We
start
with
sort
of
like
you
know.
What
is
this
thing
about?
Maybe
a
paragraph
and
then
the
set
of
project
is
a
sub
bullet
of
that.
So
it's
like
you
know.
We
provide
more
detail
more
color
beyond
just
the
set
of
projects
actually.
K
F
L
L
The
last
I
checked
as
I
emailed
about
the
comments
were
turned
off
on
the
word
doc,
which
might
be
fine,
but
is
this
going
to
be
added
in
a
PR
to
the
TOC
repo
so
that
people
can
add
comments
to
the
PR
and
how
does
it
going
to
move
forward
so
that
then
the
SIG's
that
are
proposed
could
start
working
on
the
work
that
they
have
to
do
to
define
whether
the
naming
is
correct
and
stuff
like
that?
Yeah.
F
Sure
so
the
next
slide
actually
deals
with
precisely
those
points
regarding
comments.
The
doc
just
to
be
clear.
This
doc
has
been
out
in
the
open
and
distributed
on
TOC
public
mailing
lists
since
November.
So
you
know,
I
have
assumed
that
November
December
January,
like
a
lot
of
the
people
who
wanted
to
make
input
already
have.
If
there's
anyone
you
know,
and
at
some
point
we
have
to
pop
that
it's
been
out
for
long
enough
and
we're
going
to
close
it
for
comments.
F
If
now
is
not
the
appropriate
time
for
that,
we
can
certainly
extend
the
comment
area.
The
document
became
extremely
unwieldy
because
there
were
hundreds
and
hundreds
of
comments,
and
it
took
a
long
time
to
kind
of
put
everything
back
together
again,
so
I
would
I
would
prefer
if
we
can
to
limit
the
doing
that
all
over
again.
But
if
there
is
a
need
to
provide
more
comments,
there
have
been
a
few
by
email
in
the
last
few
days
and
I
think
those
were
very
well.
L
Was
part
of
the
reason
that
I
was
asking
because,
since
the
comments
were
closed,
the
naming
of
the
security-related
sig
was
changed
to
governance
and
I
just
want
to
make
sure
that
anything
else
that
is
outstanding
like
that
people
are
able
to
provide
that
feedback,
and
it
should
make
sense
to
do
it
once
the
document
is
pretty
much
finalized
and
there's
just
maybe
a
handful
of
comments.
That's
why
I
thought,
maybe
a
github
issue
with
the
PR
associated
to
it
might
be
easier.
I,
don't
really
know,
but
yeah.
F
A
Github
to
hey,
we
should
do
that.
Can
we
I
mean?
Can
we
do
that
now?
Is
there
anything
stopping
us
doing
it
now,
I,
don't
believe
there
is
now,
let's,
let's
do
that
as
a
next.
Please
sounds
good
I
think
we
can
go
into
linear
comments
at
this
point,
given
the
nature,
for
example,
Joe's
comments
and
the
ones
that
were
just
cited.
We
don't
need
to
have
a
document
model
anymore.
We
can.
We
need
to
push
this
to
vote
able
state
as
soon
as
possible.
Yeah.
F
J
Yeah
I
was
just
gonna
to
suggest
I.
Think
there's
a
lot
of
context
here
that
a
lot
of
folks
don't
have
on
this.
Like
Quentin,
you
went
through
and
curated
literally
over
a
hundred
comments
on
this,
because
it
was
so
heavily
discussed
and
brought
that
down.
But
when
we
look
at
it
like
this,
this
displayed
the
cigs
that
would
be
under
it
and
and
there's
contexts
like
this
sakes.
Don't
have
any
authority
over
the
projects
right
because
we
we
talked
about
that
and
I
think
that
may
even
be
expressly
in
there
now.
J
J
If
you
haven't
read
it
yet
that
talks
about
those
things
and
one
thing
that
hasn't
been
worked
out,
I
think
if
I
remember
right,
there's
the
end
user
group
and
that
Cheryl
handles
and
she
talked
about
SIG's
and
forums
and
other
things
over
there.
That
project
and
others
can
be
a
part
of
to
try
to
get
more
of
that
end
user
stuff.
So
there's
other
things
going
on
in
the
CNC
F
to
try
to
get
to
it.
These
SIG's
are
not
the
end-all
be-all,
but
there's
a
whole
lot
going
on
hold.
A
Up
Matt,
okay,
we
are
still
figuring
out
what
the
end
user,
SIG's
exact
relationship
with
these
TOC
SIG's
needs
to
be
the
reason
being
that
there
are
some
end
users
who
are
asking
to
work
on
specific
areas
like
security,
okay,
so
there's
a
group
of
banks
that
want
to
work
on
banking
security,
so
that's
going
to
overlap
between
the
end-user
world
and
the
technical
world.
So
please
everyone
be
a
little
patient
while
I'm,
you
know
Cheryl's
getting
up
to
speed
on
setting
up
her
basic
structures
and
then
we
can.
K
A
K
Just
wanted
to
chime
in
and
say
that's
very
much
in
line
with
my
thoughts
as
well
and
I
want
to
make
sure
that
the
projects
and
the
end
users
and
the
contributors
do
talk
as
much
as
possible.
But
I
also
want
to
make
sure
that
everybody
is
getting
what
they
want
out
of
these
six.
So
it's
not
finalized
yet
and
hopefully
we'll
work
that
out
over
the
upcoming
weeks.
A
F
A
Excellent,
so
we
believe
that
when
a
sig
is
created,
there
should
be
quite
a
lot
written
down
about
what
it's
supposed
to
do
in
particular,
what
are
the
success
criteria,
so
we
can
track
it.
Okay
and
there's
quite
a
lot
of
details
about
that.
This
question
about
Authority
and
unbiasness.
We
need
to
make
sure
all
that
stuff
is
crystal
clear,
I
think
if
we
have
any
politics
or
debates
or
disputes
around
these
things,
it
will
be
around
those
issues.
A
The
particular
question
of
bias
was
the
concern
that
one
or
two
vendors
might
try
and
capture
a
cig
and
Quinten,
and
the
others
came
up
with
a
number
of
mechanisms
for
governance
in
the
six,
hopefully
to
mitigate
that
risk.
Please
please
take
a
look.
We
must
make
sure
these
things
operate
as
value-adding,
but
also
unbiased.
In
that
sense,
okay,
that's
really
really
important.
I
have.
A
M
A
F
M
M
M
B
F
Allow
a
final
sort
of
round
of
reviews,
hopefully
put
it
to
the
boat
shortly
selected,
TRC
liaison
per
sync
to
get
those
things
bootstrapped
and
then
perhaps
start
you
know
not
trying
to
all
six
in
parallel
at
once,
but
start
with
the
most
pressing
ones,
select
chairs
and
get
those
moving
forward.
That's
that's
kind
of
the
rough
plan
of
action
at
this
point.
F
B
Sounds
good
I
just
wanted
to
you
know.
Obviously
we
have
a
review
and
bla
backlog
of
kind
of
graduation
requests,
but
you
know
I.
You
know
silly
forgot
to
give
some
time
for
the
new
TOC
members
to
kind
of
introduce
themselves.
You
know
we
had
some
comments
from
the
outgoing
folks,
but
someone
ping
me
like
you
should
have
the
new
folks
introduce
themselves
because
not
everyone
knows
everyone.
B
B
N
So
you
can
expect
me
to
be
looking
at
graduation
requirements,
making
sure
the
projects
are
getting
what
they
need
to
thrive,
and
you
know
I'm
also
very
interested
in
making
sure
that
we
are
looking
out
for
people
who
are
actually
using
this
this
technology,
so
yep.
Thank
you.
Everyone
very
excited
to
be
here.
B
G
Yes,
I'm
Joe
Beda
now
at
VMware,
but
I
think
you
know
my
goals
on
the
on
the
TOC
looking
forward
is
to
focus
on
the
community
and
the
projects
a
couple
things
I
want
to
explore.
Is
you
know
how
can
we
make
the
TOC
more
effective?
How
can
we
expand
the
reach
I?
Think
things
like
the
like
the
state
proposal
are
critical,
they're
sort
of
in
line
with
what
Matt's
saying.
What
can
we
do
to
support
projects?
G
How
do
we
not
just
boost
CN
CF
projects,
but
how
do
we
look
at
boosting
this
segment
sort
of
the
idea
of
cloud
native
in
general,
because
I
think
that,
as
we
look
at
the
set
of
technologies
that
folks
use
to
solve
problems,
you
know
we're
not
in
a
world
where
every
single
technology
is
gonna
come
from
the
CNC
F,
so
I
think
we
have
to.
We
have
to
think
more
inclusively
about.
You
know,
users
beyond
just
the
projects
that
are
in
the
CNC
f.
E
J
P
Okay,
hello,
I,
won
and
so
I'm,
seeing
from
Alibaba,
so
I'm
working
on
the
cluster
management
system
for
a
paparazzi
or
companies
container
service
for
the
iCloud.
So
previously,
I
worked
at
her
eyes
on
some
open
source
projects,
including
a
city
property,
et
cetera,
so
I'm
super
glad
to
have
the
opportunity
to
work
with
awesome
people,
as
since
yep
and
from
the
community,
so
I
hope
to
help
with
the
adoption,
growth
and
direction
of
cloud
native
technologies.
P
So,
as
a
chioce,
remember,
I,
hope,
late
to
listen
to
more
end
users
and
really
makes
a
technology
useful
for
the
end
users
and
also
I,
think
I
hope
to
help
it's
more.
The
sandbox
products
to
help
them
to
grow
and
to
eventually
graduate
because
I
think
we
didn't
really
pay
enough
attention
to
those
sandbox
products.
Personally,
I
get
involved
into
a
fuse
and
most
products
I
think
they
all
really
want
to
graduate,
but
they
don't
really
know
how
to
it.
So
I
really
want
to
help
them.
Thank
you.
Q
You
know
really
being
the
consumers
of
these
technologies,
and
so
we
dabble
a
little
bit
in
in
the
open
source
as
well.
So
I'd
like
to
bring
a
few
of
the
you
know
the
of
the
technical
pieces
in
there,
but
but
it's
mostly
focus
on
on
that
end,
user
and
and
the
kinds
of
things
that
we
can
do
just
to
just
to
make
those
developers
a
lot
more
successful.
B
If
not,
we'll
give
him
a
little
time
next
time
cool.
Thank
thanks!
Everyone!
You
know
we
have
about
eight
minutes
left.
We
could
talk
a
little
bit
about
graduation
backlog.
From
my
perspective,
next
up,
fluency
is
pretty
much
cleared
to
go.
We're
just
waiting
some
on
some
kind
of
legal
stuff
behind
the
scenes
to
get
done
before
we
call
a
vote
for
that.
B
I
also
believe
Brian
grant
is
interested
in
bringing
container
D
forward,
but
I
would
kind
of
like
open
up
the
floor
to
any
discussion
amongst
a
TOC
on
how
they
feel
about
the
backlog,
especially
the
kind
of
existing
TOC.
You
has
a
little
bit
more
knowledge
and
context
of
what's
going
on
here.
Yeah.
R
I
just
want
to
say
a
little
bit
about
the
graduation
process
and
fluency
and
container
D.
Specifically,
we
have
a
set
of
graduation
criteria,
but
they're
pretty
lightweight,
but
we
do
have
have
some
existing
criteria.
So
what
I
recommend
doing
for
anybody
with
questions
is
to
look
at
the
graduation
proposals,
which
has
a
bunch
of
information
that
specifically
addresses
the
existing
criteria.
R
Even
I
suggest
digging
into
the
what
the
CII
the
core
infrastructure
initiative
badge
means.
That's
one
of
the
criterion,
so
take
a
look
at
that.
We
also
have
the
project
health
dashboard
and,
generally,
the
project's
put
together
a
presentation
with
an
update
about
their
progress.
So
container
D
in
particular,
has
all
those
things
I
believe
the
presentation
was
in
December.
We
can
dig
up
a
link
and
maybe
post
it
to
the
proposal.
R
If
it's
not
there
already,
but
you
know,
take
a
look
at
those
materials
we
have
and
then,
if
there
are
additional
questions
we
can
ask
them.
People
are
proceeding.
The
CNC
F
graduation
to
be
a
high
bar
I.
Think
that's
a
good
thing.
We
want
it
to
be
a
high
bar
people
in
the
ecosystem,
users
and
others
still
have
concerns
about
whether
the
bar
is
high
enough.
R
So
that's
definitely
something
I'm
interested
in
looking
at
as
well,
because
we
do
want
a
rich
ecosystem
of
projects,
but
we
want
people
to
be
able
to
rely
on
those
projects
and
all
the
context
in
which
they
want
to
use
them.
So
graduation
criteria
are
currently
our
best
mechanism,
maybe
our
one
of
our
only
a
few
mechanisms.
We
have
to
do
that.
B
You
know
I
think
we
have
to
be
careful
too.
You
know
I
think
we
could
update
a
lot
of
these
requirements
in
parallel
by
and
also
kind
of,
respect
kind
of,
a
cube
that
that
currently
exists
at
least
my
perspective
there
for
the
container
dbits.
You
know
I'm
I'm,
you
know,
since
there's
a
you
know,
it's
generally.
The
way
we've
been
working
is
asking
for
a
primary
TOC
sponsor
for
any
of
these
requests,
who
call
a
formal
vote.
Brian
has
volunteered
both
for
fluency
and
container
D.
B
Fluency
I
will
I'm
happy
to
call,
but
once
the
legal
stuff
happens
behind
the
scenes
and
container
D,
maybe
since
we
have
a
new
TOC
and
maybe
we
leave
it
open
for
maybe
a
week
of
commentary
from
the
new
TOC
in
community
and
if
there
are
no
they're
kind
of
strong
dissent,
I'm
happy
to
kick
off
a
formal
vote
on
container
D
next
week
and
the
others
I.
You
know
it's.
Basically,
the
other
kind
of
graduation
requests
are
looking
for
primary
kind
of
TOC
sponsored
to
push
for
for
a
boat.
R
Yeah
and
if
you
are
unfamiliar
with
the
details
of
a
project-
and
you
feel
that
the
graduation
information
that's
been
provided
is
not
sufficient,
please
do
speak
up
because
I
know
for
a
number
of
the
past,
graduations
they're
pretty
so
they
were
pretty
well
known
projects,
so
that
was
less
of
an
issue.
But
as
we
get
to
some
of
these
I
imagine
that
that
may
not
be
the
case.
R
B
B
B
I'll,
send
out
a
note
on
the
graduation
kind
of
criteria
and
ask
for
kind
of
wider
feedback
on
that
would
be
good
to
get
something
refreshed
over
the
next
couple
of
months.
So
look
for
that
other
than
that
we'll
meet
again
on
federal
19th.
So
thanks
again
to
the
new
TOC
members
and
also
thank
you
again,
the
outgoing
TSU
folks
totally
appreciate
the
work
that
you've
done
over
the
last
few
years
to
get
where
seen
see
us
today.
So
thank
you.