►
From YouTube: CNCF Public TOC Meeting 2017-07-12
Description
Join us for KubeCon + CloudNativeCon in Barcelona May 20 - 23, Shanghai June 24 - 26, and San Diego November 18 - 21! Learn more at https://kubecon.io. The conference features presentations from developers and end users of Kubernetes, Prometheus, Envoy and all of the other CNCF-hosted projects.
E
C
If
you
have
any
questions,
feel
free
to,
let
me
know
we're
still
very
young
organization,
so
achievements
favorite
achievement.
We
finally
have
an
user
functioning
end
user,
community
and
Sam
was
elected
to
kind
of
represent
the
user
community
as
the
TOC
slot,
like
it
thanks
Annie.
So
it's
great
to
have
this
functioning
Sam
is
really
there
at
a
kind
of
funnel
and
user
feedback
to
kind
of
the
rest
of
the
TOC
and
represent
their
interest,
so
I'm
kind
of
happy.
This
is
finally
finally
finally
function
functioning.
C
We
formalized
a
TOC
contributors
program,
so
you
know,
while
we
have
great
you
know,
you
know
super
technical
folks
on
the
TOC.
Not
everyone
is
an
expert
in
you
know
every
specific
technology
and
we
have
a
huge,
great
community
so
being
able
to
leverage
folks
in
the
community
with
different
domains
of
expertise
and
have
them
provide
feedback
on
on
project
or
diligence
you
know,
and
so
on.
It
is
amazing
and
honestly,
this
is
also
a
good
list
of
folks,
as
we
do
elections
next
year
as
potential
candidates
for
actual
toc
slots.
C
So
we
have
39
contributor,
TOC
contributors
total.
If
you
go
to
the
TOC
REBOUND
github,
you
could
see
them
listed,
feel
free
to
do
a
pull
request
if
you're
formally
interested
in
participating.
These
are
essentially
the
folks
we
reach
out
every
time
we
have
a
project
proposal
that
needs
some
due
diligence.
C
C
You
know
it's
nice
that
we
kind
of
have
now
competing
projects
which
kind
of
adheres
to
our
no-no,
kingmakers
principle,
so
we
have
like
rocket
container
d-link
or
D
envoy.
So
it's
great
to
see
this
growth.
The
other
thing
here
you
know
when
we
started
you
know
C
and
C
F.
One
of
the
ideas
was,
you
know
we
had
to
kind
of
bootstrap
everything
right,
so
we
eventually
write
down
like
how
do
we
actually
want
to
do
this?
The
TOC
principles
is
kind
of
a
result
of
that.
C
F
Sure,
please
read
the
document.
It's
very
important.
It
will
address
questions
that
you
may
have
been
pondering
for
some
time.
If
you
haven't
read
it
project
centric.
This
is
really
the
most
important
thing
right
now
for
us.
You
know
we're
all
here
because
of
these
projects.
You
go
to
the
floor.
Talk
to
the
end
users,
real
problems.
They
have
to
solve
it's
the
projects
that
are
solving
it.
I
am
not
really
any
of
us
as
individuals
or
committees.
F
Secondly,
minimal
viable
governance.
This
is
something
that
is
inherited
from
thinking
about
other
foundations
and
what's
successful
and
not
successful,
no
other
foundations,
for
example,
you
know
some
of
the
things
that
Apache
has
taught
us
are
they're
having
one
size
fits
all
governance
for
all
projects
isn't
good,
because
they're
different
sizes
and
stages
of
their
evolution,
at
least
for
the
time
being.
F
We
are
very
happy
that
projects
can
be
self-governing
and
we
have,
as
you
know,
a
solar
system
of
projects
with
the
Jupiter
project,
inventing
a
complex
governance,
because
it
is
a
complex
project,
Prometheus,
probably
a
bits
I'm
looking
at
it,
maybe
will
inherit
some
things
from
Cuba
Nettie's
governance.
If
another
project
gets
as
big
as
kubernetes,
it
probably
will
replicate
your
model.
I
would
think,
but
it's
opt-in.
Rather
we.
G
F
At
least
you
have
some
things
in
place:
no
kingmakers,
so
this
is
about
a
number
of
different
things.
I've
noticed
that
there
are
foundations
where
somebody
says
this
is
going
to
be
the
project
for
function,
X
and
then
every
all
of
the
companies
that
are
involved,
jump
on
that
project
and
so
the
squash
it's
a
path
and
it
stops
moving
and
then
some
other
project,
that's
really
good,
just
gets
not
just
it
gets
ignored
and
also
dies.
So
that's
really
self-defeating.
We
also
don't
believe
we're
smart
enough
with
early
technology
to
predict
over.
F
F
Standards
bodies
like
I,
Tripoli
and
ISO
and
IETF
exists,
who
extremely
slowly
and
carefully
create
documents
that
then
get
used
by
everybody
as
a
standard
will
hopefully
do
many
foundations.
Have
you
know
gone
wrong
by
trying
to
create
standards
before
there
is
a
need
for
one
or
by
focusing
on
creating
standards
when
they
should
be
building
software
that
solves
real
problems.
So
we
wanted
to
avoid
that
there
are
some
specs
in
the
tear
in
the
CNC
F
like
the
CNI.
Has
a
document,
and
the
spiffy
proposed
open
tracing
is
one
as
well.
F
These
represent
conventions
that
people
have
agreed
on
to
essentially
have
a
componentized
model
of
the
world.
It
doesn't
mean
that
they're
necessary
the
only
ways
that
people
will
in
the
future
agree
to
do
whatever
function
they
perform.
And
finally,
we
want
a
comprehensive
which
actually
means
we
want
a
comprehensive
tool
chain.
So
if
someone
says
what
is
the
mission
in
terms
of
the
future,
you
just
add
projects
indefinitely.
No,
we
want
to
fulfill
key
areas
of
functionality,
them
don't
have
missing
pieces.
We.
F
So
I
storage-
the
storage
discussion,
which
some
of
you
have
been
involved
in,
has
shown
up
that
there
is
a
shortage
of
good
open-source
storage
projects
on
the
market,
because
storage
is
a
very
commercial
market,
proceeding
cloud
negative
from,
among
other
reasons-
and
you
know
if
in
doubt
and
you're
saying
how
can
I
help
the
CNC
F
today
find
a
way
to
help
a
project.
That's
the
most
important
thing.
Thank
you.
Cool.
C
Thanks
we
finalized
due
diligence
guidelines
also
that
basically
inputs
in
terms
of
what
TOC
contributors
and
the
actual
TOC
look
for
when
they
go
through
and
review
a
project
super.
Thank
you
I,
don't
I,
don't
see
Quintin
in
the
audience,
but
but
Quinton
definitely
spirit
and
a
lot
of
this
work.
So
thank
you.
Thank
you.
There
Briton
Wednesday
on
official
top
toc
contributor
award.
C
So
you
know
like
we
mentioned,
we
are
a
kind
of
a
project,
first
project,
centric
organization,
right
and
so
for
a
long
time.
You
know
I
think
dan
and
I
have
suffered
be
like
one-off
email.
You
know
syndrome
where
we
were
getting
requests
from
all
of
our
projects.
I
was
kind
of
hard
to
track,
so
we
finally
centralized
things
so
there's
just
a
wonderful.
You
know:
Service
Desk
style
thing
we
have
in
place
now.
C
If
you
go
to
Service
Desk
I've
seen
CIO
or
you
just
email
service
desk
at
C&C,
FIO
you're
able
to
basically
request
funding
for
your
project.
We
recently
funded
some
outreaching
interns.
We
actually
funded
some
rocket
documentation,
I
recently
we're
doing
third-party
security
audits
for
envoy
and
core
DNS,
and
so
this
was
only
been
live
for
you
know
the
last
I
would
say
couple
of
months
and
we're
finally
starting
to
see
you
so
I'm
expecting
this
to
get
more
used
in
the
future.
C
Actually
hired
some
staff,
so
so
you
know
the
fact
that
you
know
that
and
I
are
drowning.
We
now
have
or
who
has
been
a
you
know
already,
a
participant
in
various
SIG's
within
the
kubernetes
community,
like
the
PM
sig
he's
a
developer
advocate
helping
me
out
to
make
sure
we're
promoting
and
supporting
our
projects
and
then
a
technical
writing
is
always
a
huge
pain
or
all
of
our
projects.
So
we've
hired
Zach,
who
was
already
participating
in
sick,
sick
docs
and
have
done
a
ton
of
great
work
to
improve
communities.
C
Documentation,
he's
gonna,
be
leading
a
focus
to
kind
of
bring
some
of
these
practices
to
other
other
ciencia
projects,
so
we
finally
have
some
people
helping
out,
which
is
which
is
great.
You
know,
you
know
one
thing
you
know
that
we're
trying
to
do
is
you
know
from
you
know,
moving
on
starting
next
year,
we're
going
to
be
surveying
our
maintainer
community.
So
these
are
basically
all
people
who
kind
of
work
on
our
projects
right
who
actually
our
project
leads.
Committers,
have
the
commitment
and
kind
of
gauge,
like
you
know,
how
are
we
doing?
C
What
can
we
help
with?
We
try
to
experiment
and
do
this
a
few
months
ago.
You
know
the
results,
were
you
know?
People
seem
to
be
okay,
happy,
there's
some
complaints,
obviously,
but
you
know
we
kind
of
want
to
do
this
on
an
every
six
month.
Basis
well,
transparently,
share
those
results
with
everyone
to
kind
of
help.
Help
keep
us
accountable.
B
F
C
So
yeah
a
big
thing
coming
up,
so
we
also
help
finalize
kind
of
the
POC
election
schedule
so
for
next
year,
we'll
have
two
seats:
kind
of
coming
up
in
the
March
timeframe,
so
that'll
be
a
good
time,
essentially,
if
you're
interested
in
participating
formally
on
the
TOC
and
kind
of
going
through
that
process.
So
look
forward
for
more
information
as
that,
as
that,
as
that
happens
early
next
year
projects.
Yes,
so
we
have
14
projects.
Now
we
had
something
I
think
I
counted
her
like
28
projects
that
presented
to
the
TOC.
C
We
have
six
projects
currently
that
have
been
formally
invited
to
the
proposal
phase,
which
gets
them
ready
per
vote.
So
we
have
six
projects
in
the
due
diligence
phase,
so
we
have
sto
Nats,
OPA
rope,
spiffy
and
the
tests
that
are
essentially
open
for
review
NASA's
proposals
coming
along
that
should
be
early
early
next
year.
But
if
you
have
any
comments
or
feedback,
we
would
appreciate
any
help
and
doing
formal
technical
to
do
due
diligence
on
these
projects.
A
And
again,
the
committer,
a
contributor
diligence
doc,
actually
is
very
nicely
articulates
the
things
that
we
might
be
looking
for
in
diligence.
So
if
you
want
to
be
helpful,
you
can
read
that
doc
and
there's
lots
of
things
you
don't
have
to
do
all
of
them,
but
even
if
you
have
one
area
that
you
think
you
might
be
able
to
dig
in
on
in
one
of
these
projects,
that
would
be
super
helpful.
Yep.
C
Don't
don't
be
scared
to
be
negative
either
so
project
review
backlog,
so
there's
two
things
here,
so
I
think
Alexis
and
I
have
kind
of
tried
to
put
together
kind
of
a
list
of
priorities,
a
review
and
then
kind
of.
What's
what's
what's
been
presented,
TOC
if
there's
any
projects,
or
you
know
things,
you
think
we
should
look
at.
Please
please
send
us
a
note.
You
know
we
kind
of
want
to
have
an
open
dialogue
with
with
the
community.
Here
these
these
sheets
are
open
available.
C
One
thing
we
need
to
figure
out
for
early
next
year
is
each
project
has
a
different
kind
of
maturity,
level
associated
with
there's
an
inception
level,
which
is
basically
meant
for
projects
that
are
kind
of
you
know
a
fairly
very
early
stage
may
or
may
not
actually
make
it
it's
something
kind
of
the
TOC
is
willing
to
take.
You
know
hey.
We
think
this
is
a
good
idea
like
link
or
D
for
examples.
An
inception
project
we
thought
service
meshes.
C
Were
you
know
a
good
good
kind
of
pattern,
and
so
my
critique
kind
of
came
in
as
an
inception
level
incubation
a
little
bit.
You
know
a
little
bit
more
mature,
maybe
has
more
than
one
company
behind
it.
You
know
a
little
bit
more
beers
and
then
graduated
is
like
this
is
kind
of
blessed
and-
and
you
know,
we
think
the
TOC
thinks
this
is
a
good,
solid,
open
source
project.
We
need
to
start
formally
doing
these
reviews
early
next
year.
C
I
expect
kubernetes
fluent
Ecore
deanna
some
of
these
projects
to
be
fully
you
know,
move
to
the
either
next
level
or
graduate
next
year.
So
if
you
have
any
feedback
on
this
process
or
thoughts,
let
us
know
we're
probably
going
to
do
it
just
like
we
do
our
project
proposals,
everything
kind
of
on
github
through
via
pull,
request
and
comment.
So
let
us
know
if
you
have
thoughts
on
on
how
to
potentially
approve
this.
C
F
We
have
four
working
groups
we
had
at
the
Mait.
The
main
of
the
week
has
been
the
storage
face-to-face
which,
for
those
of
you
who
weren't
there
was
a
opportunity
for
some
turns
out
quite
controversial
issues
to
be
discussed
and
I.
Think
it's
fair
to
say
that
things
that
matters
are
not
fully
settled
and
I'm
personally
happy
that
we've
actually
got
to
the
point
of
people
saying
what
they
really
think.
Instead
of
spending
three
three
months
in
this
installing
group
apparently
concealing
what
they
think,
because
they
weren't
sure
we'd
be
upset.
F
So
you
know
we
we
in
the
CN
CF.
We
want
to
be
an
open
community
and
that
has
two
parts.
One
is
don't
piss
people
off
there's
a
code
of
conduct.
You
respectful,
don't
be
aggressive,
but
also
you
know,
bear
in
mind
that
to
actually
work
together
we
have
to.
We
have
to
contend
over
issues
that
will
be
contentious.
We
can't
have
agreement,
learn
everything
at
all
times.
We
have
to
find
areas
where
we
can
get
consensus
and
move
from
there.
F
B
And
Ben
Ben's-
not
here
but
yeah
I,
mean
in
terms
of
the
the
working
group
so
and
we
talked
about
the
contribute
to
Z
contributors
is
one
way
to
scale
out
some
of
the
work
that
the
students
EF
does.
On
the
technical
side
a
little
bit.
The
working
groups
were
actually
our
first
initiative
along
those
lines
and
and
they're
new
this
year
and
we're
still
learning
their
purpose,
but
definitely
we
wanted
to
bring
together
people
from
the
scenes.
B
You
have
community
with
expertise
in
particular
area
and
have
them
help
inform
the
TOC
and
the
whole
C&C
have
community
on
particular
topics
or
to
work
together
towards
specific,
concrete
goals
like
the
CI
working
group.
I
think,
is
a
good
example
about,
so
networking
was
kind
of
one
of
our
early
victories
where
they
helped
the
CNI
project
get
to
a
state
where
a
proposal
could
a
formal
proposal
could
actually
be
made
to
the
TOC
and
get
that
in
as
an
official
project.
I
think
that
was
a
really
good
success
case.
B
The
serverless
working
group
is
current,
doesn't
have
a
specific
project
at
the
moment
that
is
trying
to
do
something
similar
with.
Instead,
they're
starting,
but
with
a
white
paper
to
kind
of
characterize
the
landscape
and
come
to
a
common
understanding
of
what
certain
concepts
mean
and
certain
principles
that
are
needed
and
an
open
source
service
platform
in
terms
of
projects
coming
up
through
that
it
service
the
clear
need
for
a
common
convention
for
how
to
express
events
for
most
services
that
use
HGB
or
rest
api
is.
B
C
Know,
and-
and
the
other
thing
kind
of
mentioned
here
is
we
we
currently
have
you
know,
for
you
know,
official
working
groups
there's
definitely
some
some
things
missing
here,
like
you
know,
just
a
lot
of
folks,
I've
been
talking
to
a
lot
of
folks
interested
in
security
right
and
you
know,
potentially
don't
be
afraid
of
proposing
a
new
working
group
in
C&C
I
have
a
discussion
on
the
TOC
mailing
list,
so
I
hope.
Maybe
next
year
we
spin
up
one
or
two
more
more
working
groups
and
in
some
new
areas
the
purpose
of.
F
These
working
groups
is
to
generate
useful
artifacts
that
can
move
understanding,
discussion,
user
I'm
standing
forward,
but
also
to
help
the
TOC
identify
which
areas
there
are
strong
consensus
on
we
consensus
or
disagreement
where
the
TOC
might
have
to
say.
Oh
dear,
we
have
a
problem
here
we're
going
to
need
a
discussion
about
what
view
to
take,
because
the
TOC
will
be
the
authority
in
all
of
these
matters
with
regard
to
projects
and
rulings,
over
definitions.
C
We
have
events
where
a
cube
con
we're
doing
three
of
them
next
year,
one
in
Europe
in
Copenhagen,
coming
up
in
May,
we're
gonna,
be
in
Shanghai
and
China
for
the
first
time
in
November
and
December,
we'll
be
back
in
the
u.s.
in
in
Seattle
in
mid-december,
so
we'll
see
how
the
weather
is
there,
but
the
weather
is
pretty
terrible
right
now
in
Austin,
we're
gonna
be
canceling
the
January
2nd
TSA
meeting.
Since
that's
right
after
kind
of
nears
not
ideal,
our
next
formal
meeting
will
be
January
16th.
C
Sorry,
it's
too
many
things
going
on
it's
this
week
and
really
you
know
now,
you
know
I
thinks
we
have,
since
we
have
everyone
face-to-face
really.
The
purpose
of
meetings
kind
of
okay
meet
the
TOC.
Let's
have
an
open
discussion.
Is
there
anything
that
you
think
that
is
missing?
Are
we
doing
something
completely
crazy
or
wrong?
What
would
you
like
to
see
improved
and
next
year?
You
know
we're
here
to
take
to
take
feedback
right
now
or
Alexis
could
do
like
a
monologue,
I'm
I'm
open
to
it.
I
C
H
C
L
F
L
One
thing
I
just
noticed
in
general
when
we
get
asked
all
the
time
is
like
you
know,
your
generate
artifacts
things
like
not
just
the
work
here,
but
the
scenes
you
have
in
general
or
any
of
the
related
efforts
here
like.
What's
what
does
everyone
else
doing
to
get
all
the
information
to
keep
up
on
everything
you
know
kind
of
getting
the
holistic
view?
It's
one
thing
to
learn
one
of
these
tools
right
when
these
features
or
ways
of
computing,
but
when
I
see
a
lack
of
justify
going
to
lots
of
companies.
L
Thousands
of
people
every
year
is
a
lot
of
people
still
just
don't
know
how
to
build
apps
on
on
these
things
right
and
it
seems
like
we're,
building
the
tools
to
fix
particular
problems,
but
doesn't
seem
like
anyone
stepping
in
to
be
like
great
here's.
Why
we're
doing
all
this?
This
is
out
now
you've,
all
your
stuff.
On
top
of
it
is
that
anything
that
comes
across
you
guys,
radars
or
yeah.
A
I
think
so
it's
interesting
I
have
for
for
work-related
reasons,
recently
been
like
googling
a
lot
of
like
what
is
what
are
we?
How
do
we
define
cloud
native
again
exactly
like
what
exactly
does
it
mean
is
view
Google
I,
don't
need
a
definition.
You're
gonna
find
some
hilarious
things
and
in
fact
the
Charter
for
the
CNC
F
has
a
very
good
definition
that
does
not
hit
anyone.
It.
D
A
Not
it
is
not
a
high,
you
know,
medium
has
really
outstripped
us,
so
that
tells
you
about
the
random
quality
but
you're
gonna,
see
so
I
actually
think
you're
you're,
absolutely
right
that
that
perhaps
we
should
we
should
put
a
technical
writer
against
against
some
SEO
on
just
like
define
being
a
little
bit
more
of
not
just
doing
the
landscape,
which
we
do
a
lot
of.
We
don't
want
to
work
on.
A
B
And
there
are
some
specific
technologies
emerging
technologies
like
service
messages.
We
get
a
lot
of
questions,
obviously
serverless,
and
how
does
that
relate
to
containers
and
I?
Was
a
religious
service?
Semester's
see
icd
new
kinds
of
automation
that
are
happening,
event-driven
automation,
so
you
know
there
are
lots
of
emerging
things
in
the
cloud
native
space
and
yeah
people
are
gonna,
need
a
diagram
I
think
to
understand
how
they
all
fit
together.
I
mean.
C
One
one
tactical
thing
to
see
in
CF
is
doing
is
we
do
have
kind
of
a
curriculum
and
training
we
do
for
for
at
least
one
of
my
projects.
Kubernetes,
we
have
a
certified
communities,
administrator
game
CKA
that
mostly
focus
on
me
like
operator
aspects,
but
this
week
as
part
of
the
conference
we're
getting
a
bunch
of
people
together
to
build
something
called
CK
ad
which
focus
on
the
application
developers
specific
perspective
in
terms
of
like
yeah.
M
Yeah
so
I
just
had
one
more
piece,
which
is
actually
some
feedback.
I've
been
hearing
from
multiple
different
sources
and
so
I'd
like
to
commit
that
CMC
F
staff
is
aiming
to
redo
our
website
in
the
next
two
months,
so
hopefully
faster,
but
by
February.
I
would
hope
that
we
would
have
a
lot
more
content
to
just
much
more
taxonomy
than
sales
necessarily,
but
even
to
the
degree
of
just
saying.
Oh
two
of
our
projects
actually
compete
as
container
runtimes.
K
So
I
was
actually
part
of
the
see
CAD
test
development.
This
last
weekend
and
I
guess
on
this
topic,
we
were
sort
of
struggling
with
what
what
should
a
developer
have
to
know
to
get
the
certification
granted.
It's
aimed
at
qu
Bernays,
not
cloud
native
in
general,
but
we've
sort
of
come
down
with
a
number
of
topics.
But
if
someone
is
interested
in
this
I
think
they're
still
meeting
on
Saturday
and
Sunday,
you
know
it's
got
to
fit
into
a
couple
of
hours
of
tests,
but
test
should
drive.
K
N
Yes,
along
the
lines
of
what
was
discussed,
I
think
there's
no
real
clarity
and
what
cloud
makes
it
is
sometimes
we're
favoring
the
sort
of
big-tent
approach.
You
know
we
still
have
db2
and
Oracle
on
those
sort
of
charts.
We
need
to
do
provide
patterns
for
developers
in
the
website.
You
know
this
is
cloud
native
our
design
patterns.
This
is
how
you
would
design
the
cloud
native
applications.
I
think
we
were
in
favoring
of
putting
more
projects,
more
vendors,
big-tent
approach
instead
of
specializing
and
educating
the
developers.
This
is
cloud.
B
B
If
you
walk
around
showcase,
you'll
see
data
wire
and
others,
you
know
develop
new
innovative
ways
of
simplifying
deployment
of
certain
types
of
applications,
they're
not
fully
general-purpose,
for
example,
they
may
not
work
for
stateful
applications
or
data
processing
applications
or
CIC
platforms
running
on
top
for
storage
systems
running
on
top,
but
there
are
going
to
be
a
number
of
common
patterns
and
those
we
should
definitely
try
to
help.
Maybe.
N
J
J
My
name
is
an
Eli
I'm,
just
wondering
for
every
release.
Do
we
have
anything
like
release?
No,
that
shows
the
highlights
of
each
release
and
also
for
each
project.
Is
there
any
place
that
we
actually
document?
You
know
not
really
Rome
and
what
people
should
expect
coming
down
the
pike
and
then
what
are
the
areas
that
you
are
looking
for?
More
developers
to
contribute
I
think
this
will
be
really
helpful
for
newcomers.
I.
B
Think
Jesse
I
infrastructure
badge,
one
of
the
things
that
requires
is
to
have
release
notes
with
releases.
There
are
certain
standards
there.
That's
part
of
our
graduation
criteria
for
all
kinds
of
projects,
so
we
don't
have
a
standard
place
where
release
notes
can
be
found
across
all
the
projects.
But
that
is
something
we
try.
You're
gonna
say
something
Chris,
no.
C
B
The
helping
new
contributors
find
where
they
contribute
I
think
is
a
great
idea,
both
at
the
CN
CF
level,
to
direct
people
to
projects
that
are
in
need
of
people
in
for
each
individual
project.
That's
definitely
something
we're
working
on
in
kubernetes
to
make
it
clear
as
the
project
grows.
Where
are
the
areas
most
in
need
of
contributors
and
what
kind
of
roles
do
we
need
contributors
to
fill
and
running
of
the
kubernetes
releases
themselves?
B
One
thing
we
did
is
we
identified
several
specific
roles
and
we're
documenting
what
the
responsibilities
of
those
roles
are,
and
we
found
that
to
be
easier
for
people
to
understand
the
need,
the
areas
of
need
and
and
the
level
of
commitment
and
responsibilities
and
expertise.
That's
compared
to
just
thousands
of
github
issues
and
90
different
repositories,
so
I
think
we're
gonna
expand
that
kind
of
model
across
more
areas
of
the
project
yeah.
B
C
Know
we're
still
a
young
organization,
and
you
know
officially
not
any
project
than
graduated
yet
so
we've
been
steering
projects
into
saying,
like
it's
good,
to
have
like
a
road
map,
and
you
know
it's
good
to
like
list
your
governance
and
so
on
your
adopters
and
so
on
so
like
next
year.
We
should
probably
make
some
strides
in
that,
but
our
current
philosophy
and
cnc
of
each
project
is
kind
of
free
to
define
its
own
governance
and
how
it
operates.
It's
kind
of
you
know
when
we
started
this
thing
was
like
you
know
all
these.
C
For
my
time
and
experience
and
open
source
like
each
open
source
project
is
like
unhappy
in
its
own
way
and
like
you
trying
to
like
dictate
one
way
of
doing
things.
I
think
is
not
productive
right,
and
so
it
makes
it
harder
sometimes
to
track
what's
going
on
and
how
to
interface
with
things,
but
that's
kind
of
the
choice
we
made
at
least
in
the
beginning,
yeah.
C
I
My
name
is
Alex
Coker.
One
of
the
things
I
think
would
be
really
useful
is
if
we
get
more
end-user
involvement
in
the
CN
CF,
because
when
I
go
and
talk
to
different
organizations
about
adopting
some
of
these
technologies,
we
often
see
quite
huge
gaps
between
what
we
think
I
think
it
should
be
versus
where
they
are
at
the
moment
and
I.
C
C
You
know,
12
months,
dan
and
I
have
been
working
really
hard
to
kind
of
add
members
and
that
and
get
going
I
think
a
lot
of
people
may
not
realize
the
end
user
community
actually
meets
on
a
monthly
basis
amongst
themselves
and
has
presentations
sharing
practices
amongst
each
other
and
also
has
CN
CF
projects
presenting
to
them
and
kind
of
sharing
amongst
them,
essentially
away
from
all
the
different
vendors.
So
they
can
have
this
safe
space
for
a
lot
of
lack
of
a
better
word.
To
kind
of
you
know,
share
practices
and,
and
so
on.
C
It
is
one
of
it's
on
my
plate,
Nick's
here
personally,
to
find
a
way
to
you
know
at
a
meeting
earlier
this
week
with
someone
from
Morgan
Stanley.
It's
like
like
we
would
love
to
like
funnel
some
like
requirements
back
to
some
of
the
projects.
How
do
we
do
this,
and
maybe
coming
up
with
some
kind
of
process,
whether
it's
a
github
repo
or
something
where
our
end
user
community
could
actually
funnel?
Some
suggestions
back
to
the
projects
is
something
I
want
to
do?
C
A
And
so
you
know,
I
am
hoping
in
the
next
year
that
we
continue
to
see
not
just
projects
that
are
kind
of
generated
by
the
the
void
of
necessary,
open
source
in
an
area
by
people
who
may
ultimately
want
to
be
vendors
or
you
know,
are
sort
of
cloud
providers
themselves,
but
also
things
actually
coming
from
the
end-user
community.
So
you
know
anyone
listening
to
this.
If
you
guys
have
projects
that
you
think
are
useful,
that
have
been
really
useful
for
your
team
in
becoming
more
cloud
native.
C
So
you
know
kind
of
in
the
interest
of
time.
So
you
know
we've
kind
of
the
way
we
structured
this
is.
We
would
have
like
an
hour
so
of
public
meeting
and
then
you
have
a
private
meeting,
but
it's
up
to
you
actually,
when
you
want
to
start
that
or
if
people
have
more
questions,
so
we
could
gladly
awesome.
So
we
had
a
question
in
the
back,
but
let
me
know
how
you
want
to
do
this.
Hi.
E
John
Bell
America
from
accordion
s,
&
Infoblox
man.
In
the
early
in
the
talk
I
know,
you
came
up
with
a
reference
architecture
or
a
very
high-level
reference
architecture
for
a
stack,
and
you
know
I
was
wondering
if
there's
any,
and
you
also
have
the
landscape
right
and
all
of
those
things
focus
on
infrastructure.
I'm
wondering
two
things:
one
is:
is
there
an
effort
or
a
desire
to
refine
that
reference
architecture
to
you,
something
not
completely
prescriptive,
but
a
little
bit
more
prescriptive
on
what
the
stack
looks.
E
Like
I
mean
we
have
a
sort
of
de
facto
with
kubernetes,
but
there's
the
different
components
and
that
plug
into
that
and
then
the
second
question
is
from
a
and
there's
not
really
been
a
focus
on
what
the
application
architectures
look
like.
I
think
this
is
what
the
gentleman
in
the
back
was
talking
about.
It's
not
just
like
a
certified
kubernetes
application
developer,
but
what
is
the
actual
application
built
that
utilizes
all
these
services
and
utilizes
all
the
things
the
platform
provides
look
like,
and
you
see
that
is
something
that
the
don't.
F
F
A
website
is
kind
of
weird,
and
you
know
when
it
comes
to
what
are
the
customers
actually
doing
turns
out
they're
building
apps?
But
how
do
they
do
that?
And
our
stories
need
to
be
fleshed
out
here
quite
clearly
and
there's
also
elephant
in
the
room,
but
there's
another
foundation
that
looks
after
apps
pod
and
Linux
Foundation
called
the
cloud
Family
Foundation.
So
we
need
to
figure
out.
F
H
Any
I
think
there's
definitely
I
need
to
do
a
more
detailed
one
and
kind
of
set
pointers
made
earlier.
Have
some
users
users
involved
in
that
as
well?
As
you
know,
kind
of
the
cloud
patterns
of
cloud
native
development
patterns
we
talked
about,
haven't
driven
from
sort
of
the
application
developers,
review
down,
I
think
is
sort
of
the
next
step.
We
talked
about
doing
in
something
I.
Definitely
it's
in
kicking
off
early
next
year.
If
there's
interest
in
getting
to
that
level,
I
think.
B
That's
a
good
idea,
so
actually
Ken
had
proposed
this
earlier,
but
he
didn't
get
takers
to
help
them
out
with
it.
So
this
is
an
where
all
of
you
could
help
out.
If
someone
has
an
interest
in
working
on
this
type
of
thing
volunteer
on
the
kissy
mailing
list,
each
volunteer
will
have
their
name
on
a
brick
in
the
oxide.
B
N
I
B
Have
to
say,
I
had
success
with
that
by
the
way
within
kubernetes
getting
a
contributor
to
just
like
start.
Okay,
here's
a
diagram.
This
is
what
I
think
he
meant
is
that
right
and
then
you
know
we
can
iterate
on
that
that
even
just
providing
that
help
in
diagramming
things,
adding
adding
bullets
things
and
making
things
super
concrete,
so
people
as
they,
oh,
no,
actually,
that's
not
what
I
meant
would
be
super
helpful
for
driving
things
forward.
G
G
B
Also,
the
answer
is
kind
of
yeah
like
right.
Now,
we're
not
gonna
have
any
votes
until
on
any
projects
until
January
at
least
so
right
now,
there's
a
little
bit
time.
Also
with
some
specific
projects.
There's
some
issues
to
sort
out,
so
there's
a
little
bit
less
urgency
there.
We
should
definitely
make
it
clear
for
individual
proposals.
What
the
expected
timeline
is
obviously
for
some,
the
timeline
is
we're
gonna,
want
it
to
be
shorter
and
said.
G
F
We've
often
said
things
like
something
can
be
proposed
and
voted
I'm
in
the
same
meeting,
and
that
could
be
extended.
Another
thing
related
to
that
to
me
is
that
we
don't
have
exit
strategies,
working
groups,
so
definition
of
success
and
I
hope
that
you
know
I
don't
want
to
just
exist
indefinitely,
just
kind
of
doing.