►
From YouTube: CNCF TOC Meeting 2020-10-06
Description
CNCF TOC Meeting 2020-10-06
A
A
In
all
honesty,
I'm
kind
of
waiting
around
to
see
if
the
app
delivery
folks
are
here
yet
because
they're
usually
ones
that
kick
us
off.
So
we've
got
a
few
other
things
on
the
agenda
today
as
well,
not
the
least
of
which,
being
like
hello,
dave,
dave,
you're.
Here,
hooray.
A
Excellent
I'll
make
you
do
like
a
more
formal
introduction
and
things
as
we
get
in
towards
all
of
this.
No
excellent.
I
didn't
expect
you
on
camera
as
well,
today,
excellent.
A
A
A
All
right
that
looks
like
everyone
that
we
are
likely
to
get
we're
now.
Four
minutes
past
the
top
of
the
hour,
so
I'll
go
ahead
and
get
us
started
our
normal
anti-trust
policy
notice.
Hello,
welcome,
meeting
logistics-
you
are
here,
please
note
that
this
slide
actually
needs
to
be
updated.
We
now
have
passcodes
on
the
meetings,
but
it's
in
the
public
dock
and
it's
in
the
cncf
calendar
as
well.
So
that's
probably
the
best
place
to
be
able
to
grab
the
zoom
link.
A
So
toc
members
present
today
I'll
update
this
over
on
the
toc
public
working
dock.
So
you
can
see
who's
here
and
all
of
that
our
agenda
is
pretty
straightforward.
Today,
again
welcome
to
new
toc
member,
we'll
kind
of
go
over
the
projects
needing
review
and
we'll
drop
into
sig
updates
and
hopefully
it'll
be
time
for
questions
as
far
as
things
coming
around
in
the
world,
but
we'll
see
so
with
that.
Actually,
I'm
gonna
do
like
dave.
This
is
now
your
time
to
be
able
to
do
like
welcome
new
toc
member
hello.
B
Sure,
I
guess
I'll
try
to
keep
it
quick,
but
I'm
dave
I'm
an
engineer
in
the
platform
team
at
spotify,
I'm
in
stockholm,
sweden.
I
don't
know
what
what
else
do
you
want
to
know
about
me?
No.
A
That's
good!
That's
great
you're
you're
here
you're
welcome
great
to
have
you.
A
Next,
up
kind
of
we've
got
a
few
open
votes
out
here.
That's
kind
of
the
only
thing,
that's
really
on
my
needs,
toc
review.
Anyone
is
fully
welcome
to
be
able
to
put
their
hand
up.
I
am
watching
chad
as
well,
but
we
have
an
open
vote
on
rook
and
an
open
vote
on
the
open
policy
agent,
and,
if
I
remember
right,
I
don't
think
any
of
the
toc
has
actually
voted
on
the
open
policy
agent.
So
this
is
my
shameless
plug
for
please
get
in
there.
Thank
you.
A
Okay:
okay,
no,
that
that
actually
is
a
good
clarification.
I
don't
know
that
it's
entirely
clear
when
we
say
public
comment
is
not
actually
the
vote
yet
public
comment
is
come
by
and
say
things,
so
I
will
be
more
clear
about
being
able
to
indicate
which
is
the
voting,
which
is
public
comment.
A
So
excellent,
any
other
things
that
I
should
have
put
on
this
particular
slide.
I'm
checking
chat
and
check
if
anybody
unmute
to
be
able
to
okay,
no
further
confusion,
excellent
I'll
turn
it
over
to
app
delivery.
If
any
of
those
folks
are
here,
I
think
I've
got
harry
on
the
line.
Hello,
excellent,
go
ahead,
yeah.
D
Yeah
yeah,
I'm
here
so
yeah.
Let
me
give
a
quick
update
on
the
c-gap
delivery,
so
we
recently
have
no
project
under
under
review,
but
we
do
have
some
other
working
items.
The
first
one
is
the
working
groups.
We
have
some
recent
update.
The
first
update
is
from
air
gapped
working
group.
A
video
is
about
a
cloud
native
application.
Delivery
in
air
gap
environment.
D
So
we
are
now
are
inviting
the
telecom
customers
our
way
works
to
share
real-world
user
cases.
This
is
actually
now
also
with
the
help
from
canalia
from
the
reworks.
So
thank
you
very
much
for
her
help.
So
if
any
other
company
or
any
other
members
want
to
contribute
user
cases
regarding
to
the
application
delivery,
the
air
gap
environment,
please
feel
free
contact
to
the
shares
or
attend
attendance
sigma
meeting.
We
are
very
happy
to
include
your
user
cases
in
the
upcoming.
D
I
will
say
it's
a
series
of
blog
posts
about
air
gapped
application
delivery.
So
this
is
the
first
update.
The
second
update
is:
we
also
have
a
discussion
to
about
a
emerging
trade
which
is
about.
We
are
we're
seeing
that
a
lot
of
platform
builders.
Now
they
are
very
active
in
the
community.
They
are
building
native
application
platforms
based
on
kubernetes
based
on
a
clone
native
stack,
but
all
of
them
they're
doing
their
own
work
and
they
are
lack
of
interoperability.
D
D
What
the
community
can
help
is
the
next
step
we
are
thinking
about,
so
we're
we're
trying
to
overcome
these
cloud
native
application
platform
builders
to
see
and
save
which,
which
are
now
they
are
they're
quite
far
from
the
cloud
native
community,
although
what
they
are
doing
is
very
closely
related
to
cncf,
but
they're
still
far
from
far
far
away
from
the
community,
actually
so
we're
trying
to
onboard
them.
D
So
if
anyone
have
any
suggestion
on
how
to
onboard
the
platform
builders,
for
example,
for
example,
somebody
who
are
building
a
platform
service
who
are
building
a
in-house
service
platform
based
on
inclinative
cloud
native
stack,
we're
very
happy
to
involve
them
in
the
sig.
In
the
community
and
to
improve
the
interoperability
to
improve
the
standard
russian-
and
this
is
the
goal-
and
we
also
have
a
proposal
in
community
to
move
certain
working
group
back
to
this
discussion
because
we
notice
there
are-
you
know
the
discus.
D
Some
some
discussion
items
are
split
into
working
groups.
This
is
actually
not
very
easy
to.
D
Yeah,
so
josh
is
asking
them
how
what
do
we
do
we
mean
by
reporting
by
on
boarding
and
saying
that,
yes,
we're
trying
to
reach
out
to
them?
That
is
what
we
are
trying
to
do
and
also
we
try
to
involve
them
more
in
the
cncf
in
the
cloud
native
community
which
which
recently
now
is
not
the
case.
D
Let
me
go
back
to
slides,
and
so,
according
to
the
proposed
I
just
mentioned
in
the
future,
I
think
I
think
c
gap
delivery
may
merge.
Some
of
the
working
groups,
for
example,
operator
working
group
back
into
the
stake,
so
we
will
continue
the
discussion
around
operators
in
the
sikh
meeting.
Instead
of
split
the
discussion
to
a
different
meeting
that
that
that
may
be
the
direction
we
want
to
go,
it's
not
determined
yet,
but
it
is
it's.
I
will
say
it's
promising
and
there
are
also
a
bunch
of
working
items.
D
I
want
to
give
a
quick
update.
The
first
is
that
this
is
actually
proposal
by
alloys,
so
the
community
are
trying
to
propose
a
sample
application
which
are
which
could
which
could
be
used
for
any
kind
of
application,
delivery
or
management
demo,
and
this
demo
is
very
different
from
what
we
are
using
today,
like
wordpress
or
booking
first,
so
this
demo
will
include
more
real
world
use
showcases.
D
For
example,
it
will
include
the
credential
management,
the
data
input
and
output,
to
showcase
how
we
use
kubernetes,
how
we
use
cloud
native
technology
to
solve
the
real
problem
instead
of
just
a
demo
application.
So
this
is,
we
will
call
that
a
generic
sample
application,
which
is
which
will
be
maintained
by
the
community,
so
alloys
is
leading
this
work.
So
the
idea
is,
we
try
to
show.
We
try
to
show
me
the
code
instead
of
by
the
paper.
D
So
this
is
the
direction
we
want
to
go
in
the
next
step.
We
want
to
create
a
sample
app.
We
want
to
create
a
the
demos
that
they
use
and
this
showcases
around
the
application.
Instead
of
just
the
writing
white
papers,
and
in
order
to
do
that,
we
were
also
trying
to
publish
a
blog
post
series
about
application
delivery,
a
technology
deep
dive.
So
one
question
is:
who
who
should
we
contact?
And
since?
If
we
want
to
publish
some
blog
posts
in
the
name
of
state
applicable
delivery,
I
record
there.
D
E
Can
answer
that
sorry
hi?
This
is
bianca.
D
Okay,
god
got
it,
god
yeah.
That
is
what
I'm
asking.
Thank
you
very
much
of
course,
okay.
So
the
last
working
item
I
I
want
to
give
a
quick
update-
is
that
it's
quite
similar
to
the
blog
post.
It's
actually
about
the
station.
The
station
is,
you
can
think
of
it's
more
like
a
summary
about
this
blog
post,
and
so
we
will
give
this.
The
community
will
give
it
a
section
in
the
coupon
north
america.
It's
about
a
it's,
a
deep,
deep
dive
talk
about
clinical
application
management
ecosystem.
D
So
if
anyone
thinks
you
have
some
project
or
idea,
which
is
interesting-
and
I
want
to
be
highlighted
in
the
talk
want
to
be
engaged
more
with
the
community
station,
we
are
very
happy
to
talk
and
we
are
very
happy
to
evolve
anything
which
can
be
shared
in
this
session.
Okay.
This
is
what
we
can
update
regarding
to
c-cap
delivery,
amy
great.
F
I
have
a
quick
question
about
that
about
the
sample
app.
I
think
it's
a
it's
a
great
idea
and
the
question
is
it
says
it's
a
community-maintained
sample.
So
is
the
plan
for
app
delivery
to
start
the
effort
and
then
for
community
to
get
involved
later.
D
I
think
we
want
to
have
the
community
get
involved
at
the
very
beginning,
so
so
so
yeah.
The
idea
that
we
want
to
get
everybody
to
contribute
ideas
around
the
sample
application,
but
the
simple
application
itself
may
be
proposed
by
the
tech
lead
or
coaches
at
the
very
beginning
about
the
application.
But
I
I
will.
I
will
assume
that
this
will
be
just
a
bootstrap
and
then
it
will
be
fully
maintained
by
the
whole
community,
so
yeah.
That
is
the
current
idea.
G
Okay,
so
just
a
few
things,
but
including
a
couple
things
we'd
like
feedback
from
the
toc
on
the
first
thing,
which
we
don't
need,
feedback
from
the
toc
on
is
we've
we're
gonna,
be
doing
a
project
paperwork
help
session
at
kubecon.
G
We
still
need
to
figure
out
the
logistics
of
this,
but
it's
been
accepted,
which
is
we've
been
generating
a
lot
of
checklists
of
what
projects
need
in
order
to
have
a
complete
picture,
particularly
aiming
for
graduation
or
to
get
from
sandbox
to
incubating
or
just
to
get
accepted
to
cncf,
and
our
plan
is
to
help
projects
with
that
at
virtual
kubecon.
G
The
governance
working
group
spent
some
time
discussing
last
week's
special
toc
meeting
wanted
to
remind
the
toc
that
per
our
email,
we're
still
waiting
for
the
toc
to
confirm
that
they
want
to
go
into
this
new
direction
for
requirements
before
we
start
putting
a
lot
of
effort
into
trying
to
write
up
and
define
those.
G
G
G
There
isn't
currently
really
a
place
within
the
cncf
ecosystem
to
publish
that
kind
of
thing.
So
you
know
again
we
want
to
come
to
the
the
toc.
Would
it
be
okay
to
stand
up
a
site
called
something
like
contributors.cncf.io,
where
we
would
publish
material
that
had
had
been
approved
as
guidance
for
cncf
projects.
G
Finally,
governance:
just
putting
there's
an
issue,
a
proposal
that
to
explore,
because
we
have
to
determine
the
projects,
actually
want
to
do
this.
The
idea
of
having
a
joint
code
of
conduct
enforcement
committee
for
smaller
projects,
projects
that
are
not
big
enough
to
have
their
own
coc
committees.
G
So
that's
linked
off
of
the
slides.
I
will
post
that
into
the
chat,
a
link
from
that
and
discuss
that
on
the
issue
for
the
maintainer
circle.
This
will
be
discussion
of
resiliency
and
october
22nd,
cncf
meeting
at
least
tentatively
scheduled
for
that
contributor
growth
again
publishing
documents.
First,
one
is
on
measuring
project
health.
The
they're
prioritizing
finishing
the
documentation
on
creating
a
contributor
ladder,
also
templates
for
that.
A
All
right
lots
going
on
in
here
looking
for
feedback
on
sounds
like
things
that
you
need
the
most
are
kind
of
like.
Where
should
we
be
putting
things.
G
G
And
you
know-
and
this
would
include
guidance
and
governance,
guidance,
contributor
growth,
any
maintainer
circle
activities.
That
is
where
what
is
our
location
for
people
who
are
working
on
the
projects
for
information
for
them,
the
and
because,
right
now
we
have
like
we
have
contribute.cncf.io
and
that's
information
for
potential
new
contributors,
that
sort
of
routes
them
to
projects,
but
that's
actually
a
different
audience
than
the
audience
of
people
who
already
run
existing
projects.
G
The
and
the
maintainer.cncf.io
domain
was
taken
for
a
different
purpose
and
moving.
It
would
be
very
difficult,
so
contributors.cncf.io
is
the
best
name.
We
could
come
up
with
we're,
not
particularly
attached
to
it.
Mostly.
What
we
want
from
the
coc
is
to
determine
that
toc.
It's
determined
that
it's
okay
to
stand
up
a
new
site
subsite
within
the
cncf
domain,
rather
than
necessarily
getting
involved
in
naming
bike
sharing,
although
if
somebody
has
a
particularly
clever
idea
for
a
name,
I
would
love
to
hear
it,
because
I
don't.
A
We
do,
and
that
can
be
as
simple
as
being
able
to
have
just
like
a
github
pages
thing.
That's
attached
to
you
know
whatever
subdomain
you'd
like
so
from
the
technical
side.
It's
not
that.
F
Having
dedicated
location
for
contributors
is
is
a
good
idea
and
josh
you
mentioned
the
maintainers
cncf.io
there
is.
There
is
already
a
page
for
that.
A
Gigantic,
it's
a
lot
of
fun.
I
think
I
think
we
passed
500
maintainers
about
a
month
or
so
ago,
so
yeah.
C
G
Those
we
we
discussed
that
in
one
of
the
meetings,
those
are
actually
pretty
different
audiences
because
you
think
about
why
somebody
goes
to
the
location
right.
Why
somebody
goes
to
contribute
right
now.
Is
there
hey?
G
I
just
graduated
from
programming
camp,
or
I
just
got
involved
in
cloud
native,
but
kubernetes
is
too
big
for
me
to
get
involved
in
you
know
what
other
projects
can
I
get
involved
in
and
that's
one
orientation
and
there's
a
completely
different
orientation,
which
is
to
say
you
know,
hey,
I'm,
you
know
frederick,
I
run
prometheus.
A
G
Yeah,
the
basically,
you
know,
yeah
an
approval
to
get.
You
know
to
to
stand
up
a
new
site
under
cnc
subside
under
cncf.io,
named
to
be
determined
later
bike
shedding
to
happen
on
mailing
list
or
somewhere
else.
J
Yeah,
I
agree.
I
think
it
would
be
useful
to
have
a
website.
That
said,
I
don't
think
everybody
from
the
toc
is
here.
So
maybe,
let's
follow
up
over
email.
H
Well,
well,
good
so
sig
network,
we
we
did
not
meet
this
last
time,
but
we
we
have
been
consistent
prior
to
that
last
time
or
two.
If
memory
serves,
we
use
the
sig
network
core
meeting
time
to
advance
the
service
mesh
working
group.
I
think
we've
covered
once
or
twice
in
this
meeting
part
of
the
some
of
the
initiatives
under
the
service
mesh
working
group,
one
of
them
that
we
had
only
alluded
to
and
hadn't
discussed
much
it
sort
of
relates
to.
H
I
was
talking
about
well
sample,
apps
and
publishing
of
those
and
helping
educate
and
that's
certainly
part
of
the
same
charter
for
sig
network
within
the
service
mesh
working
group
there's
been
an
effort
to
bring
together
a
number
of
common
service
mesh
patterns,
so
the
the
link
in
the
slide
links
to
a
sheet
that
has
right
around
60
patterns,
the
there's
about
30
that
are
considered
foundational
and
about
30
that
are
considered
advanced
and
so
that
working
group
has
been
advancing
those
patterns.
H
It's
the
intention
of
those
that
are
involved
to
well
provide
those
as
provide
those
as
samp.
Well,
how
do
I
provide
easy
tooling
to
deploy
those
sample
patterns,
so
the
sample
patterns
that
are
being
worked
on
in
the
service
mesh
working
group?
Some
of
those
members
are
also
authoring.
H
A
book
on
service
mesh
patterns
so
they'll
be
included
in
that
that
separate
book,
but
also
the
community
around
meshary,
is
working
on
implementing
those
patterns
to
make
them
easy
to
deploy,
so
that
people
can
learn
about
them
to
play
around
with
them.
Part
of
the
effort
of
the
working
group
around
patterns
is
to
also
identify
anti-patterns.
H
And
so
that's
kind
of
an
update
from
the
service
mesh
working
group
recently
submariner,
as
a
potential
project
proposal,
shows
signs
of
of
interest
in
potentially
submitting,
which
is
great.
So
we
want
to
spend
some
time
with
those
folks
and
welcome
them
to
come
present
or
to
go
apply.
H
Yep
those
are
and
then
yep.
We
will,
I
think,
the
last
two
to
three
times
that
we've
had
we've
had
kubecon
deep
dives,
slash,
intros
and
so
we're.
I
think,
we're
on
the
board
again
for
this
upcoming
kubecon.
A
K
Hello,
how
are
you
so?
We
have
a
quick
update
for
today
we're
not
undergoing
we're,
not
in
the
process
of
any
ongoing
reviews.
You
know
for
having
projects
move
from
one
portion
of
the
cncf
to
another
sandbox
incubating
graduated
following
the
state
of
observability
work
that
was
done
by
cheryl.
That
was
pretty
awesome
to
see.
K
K
So,
given
the
given
the
the
nuances
there
in
doing
that
properly
within
you
know
the
umbrella
of
a
cncf
sig,
we've
decided
to
start
formulating
a
proposal
for
an
actual
working
group
that
would
have
you
know
all
of
the
all
of
the
process
and
oversight
that
a
working
group
would
have
at
the
toc
level.
So
that's
work
in
progress.
There's
a
draft,
but
it's
quite
early,
but
just
as
a
preview,
the
sig
is
taking
that
taking
that
up,
there's
another
series
of
work
items
that
are
ongoing.
K
K
That's
that's
still
quite
it's
it's
nascent,
but
it's
all
around
how
analytics
workloads
can
engage
with
you
know
and
and
move
around
access
manipulate
data
generated
from
observability
tooling.
So
there's
a
link
in
the
slide,
and
there
was
a
recent
spike
for
that
to
to
add
parquet
as
an
input
output
format.
K
We
are
organizing
a
round
of
observability
projects
where
they
can
come
to
the
sig
and
do
either
short
webinars
or
introductions
to
the
project
as
an
example
we've
reached
out
and
have
ongoing
discussions
with
litmus,
which
is
a
chaos
engineering
project
that
has
a
lot
of
observability
outputs
and
another
example,
is
open.
Telemetry
we're
you
know,
we'll
be
having
a
webinar
with
them,
but
the
actual
work
item
that
is
happening
presently
is
defining.
K
What's
the
format
for
that,
you
know
a
template
for
slides
things
like
that,
so
that
it's
well
formed
and
it's
within
the
the
scope
of
the
sig
and
not
either.
You
know
architecture
or
things
like
that
and
then.
Lastly,
there's
a
work
stream
document
that
we've
been
incubating
in
this
in
the
in
the
sig
around
analytics,
use
cases
for
observability
data
more
broadly
and
there's
a
link
there
for
anyone,
that's
interested,
but
other
than
that.
I
think
things
are
going
well.
K
We
have
more
people
joining
every
week
and
the
community
has
been
growing
and
I
think
you'll
see
the
sig
transition
from
open
discussion
meet
greet,
let's
figure
out
what
this
is
about
to
to
more
horizontally
scaling,
work,
streams
and
being
able
to
really
you
know,
provide
provide
people
who
are
passionate
about
the
about
the
whole
domain
to
work
in
parallel
and
and
collaborate
across
projects
and
across
industry.
So
that's
been
very
exciting
to
see
I'll,
say.
H
K
Yes,
that
actually
consumed,
I
think,
two
meetings
ago,
almost
the
entire
meeting
in
a
positive
way
as
well
as
last
meeting
a
portion
of
it
and
out
of
that
discussion.
You
know,
I
think
we
wanna
vector
people's
passions
I'll
say
to
to
the
working
group
so
that
we
can.
We
can
actually
have
you
know
a
time-bounded
effort
goals,
artifacts
outputs
that
are
that
are
agreed
upon
before
it
starts.
K
Given
again
the
nuance
around
the
cncf,
its
role
in
the
space
and,
frankly,
most
of
our
most
of
the
folks
that
have
been
showing
up
to
the
sig
meetings
are
actually
from
companies
working
in
the
space.
We
actually
would
like
to
see
more
and
more
end.
Users
show
up
I'm
an
end
user,
but
I'm
in
I'm
quite
outnumbered
and
that's
not
a
bad
thing
either
right
to
see.
You
know
it's
actually
yeah
I'll
I'll,
just
I'll
just
leave
it
there.
I'm
not.
I'm
not
sure.
B
K
Spawn
quite
a
lot
of
conversation
and
cheryl
joined
us
two
two
meetings
ago
so,
a
month
ago,
to
kind
of
help
to
disambiguate
and
and
provide
more
context
around
what
it
was,
what
it
was
not
what
the
goals
were,
what
the
goals
were
not
etc.
K
Oh
yeah,
well,
so,
if
I'm,
if
I'm
speaking
freely
well
carefully
freely,
I
think
I
think
some
of
the
and
again
the
the
recordings
are
up.
I
don't
want
to.
I
don't
want
to
put,
I
don't
want
to
poorly
summarize,
but
I
think
there
was
a
little
bit
of
learning
that
that
folks
knew
to
the
cncf
and
to
the
sig
structure.
I
don't
see,
learning,
that's
pejorative
it
wasn't
enough.
K
K
I
think
that
is
well
within
the
our
scope.
We
called
it
out
in
our
charter
as
something
we'd
like
to
do
and,
and
it
serves
a
number
of
purposes,
one
of
which
being
to
identify
gaps
in
the
cncf,
where
we
might
want
to
engage
with
projects
that
are
not
in
the
cncf,
but
also
to
look
at
how
people
out
in
industry
that
are
using,
in
some
cases,
a
blend
of
open
source,
endorsing
ncf
projects
or
vendor
projects,
and
sometimes
vendor
projects
are
based
on
those
open
source
projects.
K
So
it's
it's
quite
a
layered
nuanced
domain,
and
so
if
we
wanted
to
undergo
a
broader
survey
that
doesn't
just
include
cncf
members
but
includes
you
know,.
K
Generally,
how
would
we
go
about
that,
and
so
thankfully,
some
people
in
the
sig
have
prior
experience
with
running
surveys
like
that,
and
you
know
again
it's
it's
a
very
early
proposal
in
its
earliest
days
of
the
first
draft.
So
we
don't
really
have
anything
to
talk
about
concretely,
but
we
hope
in
the
coming
cycles
to
have
a
concrete
proposal
for
the
toc
for
a
working
group
that
so
we
can,
you
know,
be
be
clear
and
specific
about
what
it
is
and
then
and
then
take
on
the
work
to
do
it.
A
L
Hey
everyone:
this
is
ricardo,
so
yeah,
so
we
have
been
doing
some
work
reaching
out
to
communities
and
having
some
presentations
in
our
meetings
so
in
different
spaces.
It's
so
on
the
os
for
container
space.
L
We
had
two
projects:
two
projects
presenting
our
meetings,
the
first
one
was
talos
and
that's
an
operating
system
that
allows
you
to
manage
all
the
components
using
api.
So
it's
a
secure
way
of
managing
all
the
components
and
in
its
pattern
that
it's,
you
know
being
used
more
in
there.
For
example,
there's
a
there's.
Another
project
called
the
bottle
rocket
from
amazon
web
services
and
they're,
using
a
similar
approach
where
you
manage
the
operating
system
using
just
apis,
and
so
you
don't
have
access
to
the
shell
or
you
know
or
ssh
access.
L
So
yeah
and
that
in
in
and
the
same
idea
behind
core
os,
where
you
have
this
lightweight
operating
system,
where
you
can
run
containers
on
top
of
it
and
then
on
the
containers
in
runtimes,
we
had
some
projects
present
and
we've
also
reached
out
to
some
other
projects.
So
one
of
the
interesting
ones
that
we
had
at
our
last
meeting
is
wscc,
which
is
a
web
secure
capabilities
connector.
L
So
that's
a
way
to
decouple
your
applications
into
different
pieces
into
different
web
assembly
modules
in
these
different
pieces
can
talk
to
each
other
using
a
broker.
So
the
idea
is
for
making
it
easier
for
developers
to
just
focus
on
on
the
business
logic
and
use
some
of
the
other
bits
in
web
assembly.
So
they
they.
L
You
know
they
have
those
other
capabilities
in
those
other
bits,
for
example
like
if
you
want
to
connect
to
a
database
using
or
redis
database
or
like
cassandra
database,
that
would
be
a
web
assembly
module
just
for
that,
and
so
developers
wouldn't
have
to
focus
on
on
creating
that
webassembly
module,
but
they
would
just
use
it
and
use
the
system
to
connect
to
it.
L
Workloads
and
and
how
they're
going
to
be
maybe
running
in
the
future
or
a
glimpse
of
how
they
won't
run
in
the
future.
So
another
project
is
trial
and
we
reached
out
to
them.
L
That
was
that's
a
container
image
registry
and
it's
written
rust,
so
they're
interested
in
presenting,
so
they
haven't
confirmed
yet
so,
hopefully
we
get
them
to
present
in
our
meetings,
then
we
reached
out
to
wazon3,
which
is
webassembly
runtime,
and
this
is
a
runtime
that
you
can
use
to
run,
something
like
your
webassembly
modules
that
can
be
used
with
something
like
wascc.
L
And
then
we
also
reached
out
to
another
project
called
nanos
and
that's
basically
running
a
unikernel
in
a
vm,
so
we'll
see
if
they
want
to
present
in
our
meeting
on
the
aiops
and
h
iot
space.
Also,
we
had
some
projects
presented
and
we
reached
out
to
so
seldom
core
is
basically
a
machine
learning
operating
operations
framework.
L
So
it
allows
you
to
serve
your
models,
machine
learning
models
and
then
also
make
the
inference
and
and
have
some
other
capabilities
on
how
to
improve
some
of
the
the
model
and
and
get
information
on
the
how
it's
working
and
how
it's
doing
the
inference
part.
L
Then
qflow
is
another
project
that
we
reached
out
and
they're
interested
in
presenting.
So
basically,
this
is
machine
learning
end
to
end,
so
it
allows
you
to
run
the
full
stack
like
the
learning
part,
the
serving
part.
So
you
can
use
something
like
salon
core
on
top
of
qflo,
so
we'll
hopefully
have
them
present
flow
is
another
project
that
it's
in
the
edge
computing,
iot
space
and
they're,
scheduled
to
present
at
our
next
meeting
and
last
but
not
least,
barry
net.
L
So
that's
what
for
the
projects
and
for
for
the
presentations
and
communities,
I'm
sorry
and
and
as
far
as
the
projects,
so
we
don't
have
a
lot
of
activity
activity,
so
huey
is
still
looking
for
a
toc
sponsor.
L
So
this
is
the
the
standard
way
of
using
devices
in
containers,
so
they're,
looking
at
doing
a
pfc
for
with
potman
and
container
d,
which
is
which
are
two
runtimes
and
then
they're,
also
looking
at
integrating
with
nri,
which
is
the
no
resource
interface.
L
Another
project
presented
presented
our
under
one
one
of
our
meetings
about
a
month
ago,
yeah
and
that's
all
I
have
for
the
updates
first
runtime.
So
any
questions
or
anything.
So
thank
you.
A
M
Hello,
hello
click
update
on
sec
security,
so,
first
up
we
have
cloud
native
security
day
and
that's
happening.
We
are
excited
about
it.
I
believe
the
cfps
just
ended
yesterday,
so
we're
gonna
have
kind
of
round
up
with
the
reviews
for
the
proposals
there's
also
kind
of
chatter.
Are
we
are
thinking
about
doing
a
ctf
for
this
virtual
instance,
for
this
we'll
see
how
that
works
out.
But
again,
all
these
details
about
this
is
in
six
security.
Events
on
the.
M
So
another
thing
to
happen
is
dan
shaw
finished
his
term
as
a
co-chair
for
six
security.
So
we
have
nominated
amity
fox
as
our
new
co-chair
and.
M
And
another
another
thing
is
on
security
assessments,
so
this
is
something
that
we
started
off
in
dockercon
2019.
M
We
got
together
and
created
the
first
draft
for
what
security
assessments
would
look
like
the
security
assessment
process,
and
we
made
the
decision
to
say
that
after
the
first
five
assessments,
we
will
come
back
and
take
a
review
of
this
process
and
kind
of
fine
tune
it
and
change
it
in
the
way
that
made
sense.
M
But
we
didn't
want
to
make
any
changes
yet
until
we
had
a
good
amount
of
data
points.
M
So
right
now
we
are
on
the
completion
of
our
fifth
security
assessment,
which
is
key
cloak,
so
the
assessment
has
been
done.
The
other
outline
has
been
drafted,
so
it's
just
a
matter
of
cleaning
things
up
and
and
presenting
it.
So
in
light
of
that
we
did
a
retrospective
presentation.
M
We
put
together
kind
of
some
feedbacks
from
the
initial
drafters
of
the
assessment
process
and
there
were
a
lot
of
ideas
and
a
lot
of
discussion
points
that
were
brought
up
in
the
community.
M
So
we've
set
up
a
kind
of
a
small
working
group
to
kind
of
target
what
some
things
you
can
do
with
the
security
assessment
process.
M
This
involves,
you
know,
making
the
documentation
a
little
bit
better
figuring
out
how
to
modify
the
schedule,
so
it
works
better
for
both
reviewers
as
well
as
project
leads,
and
one
of
the
target
items
that
we
also
like
to
see
is
to
see
how
this
will
map
onto
the
new
toc
process
from
the
new
sandbox
process,
as
well
as
incubation
and
graduation,
and
how
it
relates
to
security
assessment.
M
M
We,
we
are
expecting
all
content
to
be
done
within
another
week
or
two,
and
we
will
be
having
a
draft
that
will
be
ready
to
for
review
by
select
reviewers.
So
hopefully
that
will
be
an
already
set
that
we
can
share
pretty
soon.
A
A
In
chat
around
security
working
on
the
recommendation
for
in
toto
at
the
moment,.
M
I
think
that
I
think
the
last
one
we
did
was,
if
I
recall
correctly,
we
did
something
for
oppa.
I
don't
think
we've
made
a
recommendation
for
in
total
yet,
but
this
would
be
similar
to.
I
think
what
we
did
with
oppa,
which
we
would
is
this
for
incubation.
M
I'm
not
wrong,
I
believe,
say
yes,
okay,
yeah.
I
think
we've
got
to
go
back
to
the
we've
already
done.
The
security
assessment
for
intel.
B
M
I
think
we
will
go
back
to
that.
Just
see
what
are
the
the
changes
that
have
been
since
then,
and
if
we
would
give
a
recommendation
based
on
that,
but
let
let
me
make
sure
that
we
have
that
on
our
list
of
to
use.
N
Hello,
okay,
so
with
praveega
who
are
currently
looking
to
come
in
as
a
incubation
project,
justin
cormac
has
volunteered
to
be
the
the
tac
sponsor
for
the
due
diligence
process.
N
We're
going
to
allocate
tech
leads
and
I'll
be
working
to
to
show
you
those
those
first
meetings
with
the
with
the
project
team
in
the
coming
days
or
or
a
couple
of
weeks
with
open
ebs,
we
had
a
good
review
with
the
project
team
around
the
the
multitude
of
of
repos
and
some
of
the
the
challenges
with
regards
to
the
licenses.
We
may
we're
going
to
be
reviewing
this
internally,
but
we
may
need
to
touch
base
with
with
the
with
the
foundations.
N
B
N
N
N
But
fundamentally
you
know
we
think
there
is
little
overlap
with
the
with
the
with
the
cap
that
the
the
toc
was
was
concerned
about.
So
so
we
think
that
this
should
this
new
information,
hopefully
should
should
allow
the
toc
to
vote
for
the
for
the
project
at
the
next
sandbox
meeting,
also
the
performance
and
benchmarking
white
paper.
N
B
N
In
the
run-up
to
kubecon
is
some
of
the
a
view
of
some
of
the
gaps
that
we
see
in
the
in
the
storage,
cncf
landscape,
at
least
and
similar
to
to
what
runtime
have
done,
which
is
absolutely
exemplary,
is
try
and
try
and
invite
some
of
the
some
of
the
projects
within
that
landscape
to
to
present
at
the
sig
and
and
build
up
a
bit
more
of
a
community
to
to
address
some
of
those
gaps.
So
watch
this
space.
We'll
have
more
information
for
the
next
meeting,
and
that's
me.
A
All
right,
I
don't
see
any
other
questions
in
chat.
Anything
else.