►
From YouTube: CNCF TOC Meeting 2023-02-07
Description
Meeting notes:
https://docs.google.com/document/d/1jpoKT12jf2jTf-2EJSAl4iTdA7Aoj_uiI19qIaECNFc/edit#heading=h.k6qzprqgc1u9
A
A
A
A
E
One
initiative
we
have
is
that
Tech
storage
and
the
dok
community
are
collaborating
by
paper
that
describes
the
patterns
of
running
data
on
kubernetes,
focusing
on
databases.
Initially,
we
have
been
discussing
it
in
the
last
few
meetings
and
we
have
a
draft
by
paper
online
Focus
From
the
tag
and
dok
have
been
discussing
and
providing
feedback.
E
We
will
also
be
using
information
from
our
database
white
paper
that
we're
working
on
to
fill
in
that
template
and
we
got
the
the
cloud
native
Disaster
Recovery
paper
completed
published
and
we're
still
need
some
work
to
do
to
finish
the
to
finalize
the
performance
by
paper.
So
that's
all
from
Tech
storage.
D
E
D
So
you
are
you're
going
to
set
up
a
meeting
and
then
they're
going
to
come
and
okay
present
yeah,
okay
yeah
sounds
good.
The
second
one
I
I
was
while
you
were
seeing
white
papers
a
few
times
like
how
do
we
know
that
folks
are
looking
at
the
white
paper
and
it
it's
actually,
you
know
being
used
in
the
wild,
so
to
say:
do
we
have
any
metrics
or
something.
E
That's
actually
a
good
question,
so
so
I
know
that
for
the
for
those
two
white
papers,
the
the
landscape
by
paper,
I
did
see
someone
send
out
some
messages
on
LinkedIn,
saying
hey.
This
is
a
great
paper,
so
some
feedback
I'm
not
sure
how
to
measure
the
metrics
and
for
the
and
also
the
other
one,
the
cloud
native
Disaster
Recovery.
E
D
C
So
I
would
highly
recommend
coordinating
with
the
cncf
to
formulate
blog
posts
around
these,
so
that
will
drive
both
visibility
because
there's
a
lot
of
folks
that
watch
the
blog
posts
and
sending
them
out
to
the
TOC
public
mailing
list
so
that
you
get
more
visibility
and
awareness
through
that
channel
we've
often
in
the
past,
when
tax
security
does
papers,
we've
also
leveraged
our
Twitter
account.
So
you
can
coordinate
with
cncf
on
getting
a
retweet
of
that
paper
going
out
as
well
as
on
LinkedIn
as
well.
C
So
there's
a
couple
of
different
things
for
the
blog
post
I
would
recommend
filing
an
issue
with
the
service
desk
to
go
ahead
and
get
that
started
beyond
that.
I
think
those
are
really
good,
high
visibility
platforms
for
elevating
this
and
kind
of
getting
that
content
out
there
as
far
as
confirming
the
metrics
for
who's
accessing
content.
As
long
as
your
content
is
stored
within
the
GitHub
repo,
there
are
some
metrics
in
GitHub
about
how
that
page
is
being
accessed
and
where
it's
coming
from,
so
you
can
actually
see
who's
been
looking
at
that
information.
D
E
E
C
Yep,
so
the
everyone
is
in
full
recovery
from
cloud
native
security
con,
which
happened
in
Seattle
last
week
for
those
of
you
that
were
able
to
join
us.
Thank
you
so
much.
We
appreciate
your
attendance
for
those
of
you
that
couldn't
make
it.
We
hope
you
were
able
to
stream
the
live.
Keynotes
everything
was
fantastic.
We
had
excellent
excellent
feedback
from
attendees.
C
A
lot
of
the
responses
and
feedback
we
received
were
that
the
content
was
more.
It
was
significantly
deeper
and
more
enriching
to
their
work.
In
some
cases
they
it
was
suggested
that,
like
while
the
security
track
at
kubecon
provides
a
great
first
level
of
information
for
individuals
in
a
domain
specific
space
like
security.
Looking
for
that
additional
content,
having
that
dedicated
event
just
to
focus
on
those
has
been
extremely
beneficial
for
them.
Attendees
walked
away
with
a
lot
of
really
good
technical,
technically
deep
Disco
discussions.
C
C
So
tax
security
was
actually
able
to
hold
a
dinner
like
they
used
to
pre-pandemic.
They
had
a
ton
of
people,
show
up
they're
working
on
I,
believe
updating
the
repo
for
those
meetups
with
that
picture.
But
it
was
a
very,
very
large
table
of
community
members
that
were
able
to
meet
and
in
person
and
talk
about
how
how
they've
been
enjoying
the
conference.
D
C
Do
and-
and
we've
been
talking
about
this-
a
lot
within
both
kubecon
co-chairs,
as
well
as
with
tag
security
about
how
what
is
the
next
iteration
about
of
the
color
into
the
Standalone
event,
while
still
providing
that
same
level
of
content
within
kubecon.
So
what
right
now
is
going
on
is
we're.
Exploring
the
creation
of
a
security
village
within
cubecom
proper
is
like
a
mini
conference
within
the
primary
conference
itself.
C
I
think
that
I
think
we
have
a
high
likelihood
of
that
being
successful,
but
we
do
need
to
try
things
out
and
figure
out
how
it'll
work
the
village
will
first
show
up
in
EU
as
I
understand
it
and
then
from
there
we'll
figure
out
how
it's
going
to
look
for
North
America.
But
this
is
all
like
very
much
in
flux.
Discussions
are
still
going
on
live,
so
I
don't
want
to
commit
anybody
to
anything,
but
we're
looking
at
how
we
can
make
this
work
across
the
board.
D
A
Yeah
I
think
so
I
mean
part
of
it
is
sort
of
like
the
the
security
tag
has
had
so
much
history
and
so
much
like
you
know,
peace
is
coming
together.
That
I'm
not
sure
if
we
have
like
a
process
yet
to
be
able
to
replicate
it
but
yeah.
If
you're
interested
we
can,
we
can
look
towards
what
would
be
possible.
Okay,.
D
E
E
D
A
D
G
Say
yesterday,
at
runtime,
we've
had
a
couple
of
projects
present
at
our
meetings
and
there's
also
been
some
great
progress
happening
in
our
working
group
activities.
So
talking
about
the
projects,
we've
had
presentations
to
go
and
capture.
So,
if
you're
not
familiar
with
cool,
it
helps
you
build
container
images
from
go
programs
and
pushes
them
to
contain
electric
trees.
G
The
interesting
part
is
that
it
does
all
of
this
without
like
requiring
you
to
write
a
Docker
file
or
even
installing
Docker
itself
on
your
machine,
and
it's
also
been
recently
accepted
into
the
pncs
landmark.
So
some
things
that
we
talked
about
them
were
about
expanding
the
pool
of
contributors
and
things
on
the
roadmap,
like
publishing
case
studies,
adding
support
for
signing
images
and
adding
some
more
ecosystem
integration.
G
So
moving
over
to
Capital,
the
presentation
and
demo
were
awesome.
I
recommend
really
like
checking
out
the
meeting,
recording
we're
also
like
pretty
impressed
by
the
project.
So
essentially
what
capital
does
is
it
provides
a
multi-renal
environment
for
kubernetes,
so
it
has
this
abstraction
called
a
tenant,
which
is
basically
a
grouping
of
kubernetes
namespaces
and
within
each
tenant.
Users
are
free
to
create
their
name
faces
and
share
all
their
assigned
resources.
G
So
one
thing
that
was
really
nice
from
the
meeting
was
that
they
also
invited
an
end
user
from
a
gaming
company.
If
I
recall
correctly,
we've
been
using
this
in
production
successfully
to
share
their
experience
and
actually
for,
like
the
end,
users,
also
been
contributing
to
the
project,
which
was
also
pretty
cool.
Today
they
wanted
to
consider
applying
to
the
CNC
of
sandbox,
so
we
gave
them
a
rundown
of
the
process.
G
Their
contributions
seemed
to
be
mostly
from
a
single
company,
so
we
also
suggested
that
they
expand
their
first,
like
School
of
contributors
interact
with
the
multi
tenancy
working
group
in
kubernetes,
and
especially
the
hierarchical
name,
Facebook
project
within
that
working
group.
We
also
have
a
few
more
products
in
our
pipeline
for
our
next
meetings,
including
flat
car,
who
have
also
recently
applied
for
incubation,
and
in
fact,
actually,
the
project
interest
has
been
so
great
lately
that
we've
also
had
to
schedule
a
few
additional
meetings
compared
to
our
regular
parents.
G
So
moving
over
to
a
working
group
activities,
so
the
iot
edge
working
group
published
the
first
edition
of
The
Edge
native
applications
principles.
White
paper,
which
is
the
name
suggests
that
lets
down
a
set
of
principles
for
being
educated,
and
it
also
took
it
a
step
further
by
using
the
principles
to
consolidate
an
edge
landscape.
This
is
a
work
in
progress
currently,
but
I
think
we
already
have
like
135
six
projects
on
there.
G
Cloud
developer
Summit
in
Chan
and
similar
to
what
the
edge
working
group
is
doing.
We
also
have
the
batch
working
group.
That's
going
to
be
putting
out
one
pager
to
mainly
layout
the
main
tools
in
the
cncf
batch
landscape
today,
I
think
that's
going
to
just
get
started
with
it,
but
that's
the
main
goal
and
the
CDI.
That
is
the
container
device
interface
side
of
things.
G
There
were
some
improvements
made
to
the
dynamic
resource
allocation
cap
for
kubernetes
127,
and
this
feature
essentially
uses
CDI
under
the
hood
to
do
its
device
injections.
So
the
improvements
mainly
centered
around,
like
passing
information
about
Syria
devices
more
efficiently
and
for
the
reason
the
CRI
is
now
extended
to
accept
CDI
devices
directly.
G
There's
also
been
discussion
about
CBI
support
for
Docker,
so
this
was
discussed
in
the
movies
last
week
or
during
the
week
before,
and
the
working
group
members
are
now
working
with
movie
maintenance
to
figure
out
what
Docker
interchanges
will
be
required
to
enable
the
support
we
also
summative
for
keep
going
Amsterdam
and
I.
Guess
it's
probably
a
bit
of
shout
this
year
because
the
small
group
that
we
got
accepted
it's
called
session
and
Conference
yeah.
G
D
Sounds
good
the
other
question
that,
like
there
seem
to
be
a
bunch
of
multi-tenancy
stuff
popping
up,
it
would
be
good
to
like
do
a
one-pager
or
a
white
paper,
or
you
know,
whatever
you've
been
doing
for
other
areas,
do
that
for
multi-tenancy
and
try
to
get
folks
from
the
project
like
capsule,
V,
cluster
and
those
kinds
of
things
and
like
get
get
them
together
and
figure
out,
like
okay
who's
doing
what
what
works?
What
doesn't
work,
or
things
like
that?
Do
you
think
that
that
would
be
a
good
good
thing
to
do.
D
F
Yeah
I
think
I
think
it's
a
great
idea.
I
mean
the
captioning
team
seemed
pretty
interested
and
in
growing
the
ecosystem
and
I
think
they're
thinking
about
applying
for
incubation,
so
I
think
we
can
reach
out
to
them
and
and
see
if
they're
interested
in
you
know
Drive
in
a
white
paper
and
and
maybe
reaching
out
to
other
projects
and
see
if
they're,
interested,
okay.
I
I
I
B
I,
like
Kathy's
suggestion,
because
I
think
it
is
very
useful,
especially
as
a
blog
post,
because
Verizon
is
such
an
you
know,
area
where
a
lot
of
teams
are
working
on
it.
Also,
a
lot
of
you
know
different
projects
right
so
again,
you
know.
Having
that
comparison
available
in
searchable
format
is
always
helpful.
D
J
Actually,
the
most
recent
thing
is
that
profit
and
the
company
is
sponsoring.
Enochs
has
just
shut
down.
Okay,
so
I'm
I'm,
but
yeah
I
mean
there
is
a
bunch
of
other
stuff
going
on,
but
yeah
I'm
not
sure.
What's
going
on,
there
I
need
to
catch
up
with
some
people.
It
just
happened
a
couple
of
days
ago:
okay,.
B
Right
hi
everyone
good
morning,
we
had
a
some
some
amount
of
activity.
You
know
during
the
first
couple
of
months
here
and
just
wanted
to
kind
of
call
out
what's
in
progress,
a
couple
of
exciting
initiatives
that
have
picked
up
steam.
This
is
based
on
the
first
initiative,
which
was
the
observability
query
standard
work
group
that
has
been
actually
a
hot
topic
for
a
few
quite
a
few
months
now,
and
there
was
a
lot
of
good
conversation
and
discussion
around
the
need
for
a
query
standard.
B
You
know
as
different
vendors,
build
their
own
query
standards
and
or
query
languages
and
dsls
and
roll
them
out
really
the
fragmentation
that
is
felt
at
the
end
user
level,
right
and
and
a
work
group
has
been
proposed
in
the
in
the
tag
observability
area,
where
you
know
we
are
encouraging
different
folks
who
had
actually
had
a
quite
an
in-depth
discussion
at
kubecon
in
Detroit,
leading
up
to
actually
making
a
proposal
for
an
initial.
You
know
scope
as
well
as
a
charter,
so
that's
ongoing.
B
That's
really
exciting.
To
see
that
initiative
pick
up
eBay
as
well
as
Netflix
have
been
maintainers
from
you
know.
These
two
core,
you
know
end
users,
have
been
leading
this
discussion
and
looking
forward
to
kind
of
driving
that-
and
perhaps
you
know
actually
spinning
it
off
as
a
work
group,
so
that
discussion
is
ongoing
and
there's
also
a
proposal
available
so
exciting.
B
We
decided
as
a
community
as
an
observability
Community
across
projects
to
kind
of
keep
it
at
the
tag
level
because
again
and
reference
spec
could
be
suggested
from
such
a
web
group
and
then
implementation
could
be,
you
know
easily
embedded
in
open,
Telemetry
or
other
projects.
You
know
which
are
really
working
closely.
B
K
It's
it's
been
dormant
for
a
quarter
or
two,
but
in
later
this
month
we
intend
to
open
the
door
to
contribution
and
start
having
project
meetings
for
anyone.
Interested
I'll
speak
to
a
little
bit
in
today's
tag
meeting,
but
I
don't
want
to
spend
a
ton
of
time.
There's
some
links
there
for
those
that
are
interested.
In
short,
it
takes
the
data
behind
the
landscape
and
builds
a
labeled
property
graph
so
that
we
can
use
graph
analysis
techniques
versus
more
rectangular
relational.
K
If
you
will
techniques
so
that
that's
happening,
there's
a
work
group,
that's
the
kubernetes
observability
work,
grouper
observed
k-8s.
That
group
will
have
an
update
in
next
month's
Toc
meeting,
but
the
tldr
is.
It
remains
to
be
seen
what
the
end
endpoint
of
this
is
sort
of.
In
parallel,
there's
the
open
Telemetry
demo
application
stack,
which
really
observe
k8s,
had
an
earlier
Fork
up.
K
So
we
we
might
actually
roll
changes
there,
but
we'll
back
to
open
Telemetry
and
call
it
a
day
or
perhaps
leave
something
more
permanent.
In
place,
but
we'll
have
an
update
next
month,
I
did
want
to
just
mention
that
tell
all
your
friends,
if
you
have
case
studies
or
end
user
sort
of
stories
or
experiences
using
observability,
tooling
or
open
source
projects
within
the
cncf
or
otherwise.
K
Please
send
us
a
message.
Look
us
up
we're
friendly
case
in
point
in
today's
tag,
observability
meeting,
which
immediately
follows
TLC
meeting
here
we
have
Vijay
Samuel
from
eBay.
I
will
lead
a
line
this
up
a
long
time
ago,
but
he's
talking
about
how
and
why
he'd
be
pivoted
to
open
Telemetry,
there's
a
blog
post
from
a
few
months
ago.
K
It's
actually
a
really
cool
story,
that's
a
good
blend
of
business
and
Technical,
and
and
highlights
why
hotel
is
gaining
adoption
at
the
rates
we've
been
seeing,
which
is
great
for
the
project
on
the
14th.
This
is
still
pending,
but
Ryan
Wright
from
Quine.
If
you're
not
familiar
with
client
in
a
shelter
streaming
graph
interpreter,
which
is
kind
of
a
new
thing.
It's
an
MIT
license
project.
K
That's
a
result
of
seven
to
eight
years
with
DARPA
funded
research
into
basically
something
that
can
work
in
streaming
pipelines
and
read
a
bunch
of
little
things
and
then
at
the
other
side,
have
more
interesting,
correlated
aggregated
things.
But
unlike
a
lot
of
existing
Solutions
there's
a
timing
window,
you
know,
and
you
only
have
the
it
uses
a
stateful
graph,
Atop
A
number
of
stores.
To
do
that.
So
you
effectively
don't
have
a
timing
window
anymore.
So
it's
quite
good
for
a
lot
of
observability
use
cases.
K
B
Stuff
yeah,
yeah,
sure
sure,
and
then
thanks
Matt
I
mean
again
just
wanted
to
highlight
that
our
speaker,
Series,
has
been
pretty
successful.
You
know
again
just
engaging
as
well
as
pulling
in
different.
You
know
case
studies
from
the
end
user
world,
as
well
as
from
actual
project,
subject
matter:
experts
from
London
and
maintainers
from
different
projects
in
the
observability
space
there's
also
a
lot
of
energy.
You
know
in
in
specific
topics
such
as
cost
management.
You
know
leveraging
observability
techniques.
B
B
You
know
around
the
observability
day,
so
looking
forward
to
kind
of
having
that
energy
at
EU
at
kubecon,
U
and
also
the
maintainer
track,
where
we
do
plan
to
you,
know
again
have
a
set
of
discussions
around
some
of
the
key
topics
that
have
been
important
to
all
the
different
maintainers,
as
well
as
end
users
who
participate
and
just
to
wrap
it
up
again.
I'm
sorry
we're
running
a
bit
late,
but
I
wanted
to
call
out.
You
know
again.
B
How
do
we
better
communicate
with
the
TOC,
because
I
think
that
there's
a
lot
of
activity
that
is
happening
on
the
projects?
You
know
both
Innovative
features
as
well.
As
you
know,
various
projects
going
through
different
phases
of
growth
as
from
a
contributor
standpoint,
but
I
think
that
it
would
be
useful
to
have
a
more
formal
mechanism
of
communicating
with
the
TOC
in
some
amount
of
detail
on
these
projects.
B
Because
often
you
know
there
is
a
lot
of
interest
from
different
community
members
who
want
to
participate
in
the
tag,
but
don't
necessarily
have
a
process
for
participation
other
than
just
joining
in
and
attending
again.
Totally
understand
that
it
is,
you
know
as
much
as
what
people
want
to
contribute
to
and
how
people
get
involved,
but
it's
also
encouraging
folks.
You
know
with
a
clear
process
if
folks
want
to
become
tech,
leads
or
co-chairs.
B
You
know
again
having
some
of
that
process
established
and
published
would
be
useful,
so
really
working
closely
with
the
TSC
to
Define
at
least
some
criteria,
which
you
know,
then
the
larger
projects
and
communities
can
leverage
to
to
get
more
involved.
So
why
don't
you
call
that
out
because
I
think
we'd
like
to
have
a
more
detailed
conversation
about
you
know:
how
do
we
actually
leverage,
perhaps
even
contributor
strategy,
the
tag
you
know,
experts
there,
as
well
as
the
TOC
itself,
to
get
some
guidance.
C
Our
Lolita,
if
you
could
right
you,
you
talked
about
a
lot
of
different
area.
Is
that
I
think
we've
discussed
in
the
past
with
the
tag
chairs,
as
well
as
with
the
TOC
at
previous
kubecons?
If
you
could
write
down
a
couple
of
those
points
and
send
that
to
the
TOC
mailing
list
that
way,
we
we
have
some
form
of
documentation
around
them,
because
I
believe
we
already
have
an
open
issue
on
talk
and
tag,
communication
and
better
partnership
there,
all
right
gems,
an
issue
would
actually
probably
yeah.
B
C
D
This
exactly
and
if
you,
if
you
need
like
ongoing
engagement
with
the
QC,
we
should
figure
out
like
what
shape
or
form
it
takes,
because
we
need
to
scale
as
well.
So
far
we've
been
trying
to
do
like
hey
here
are
two
Liaisons
you
can
talk
to,
but
I
don't
know
if
that
is
working
as
well.
That's
the
point
in.
B
K
Yeah,
so
speaking
to
the
to
the
need,
you
know
just
just
to
just
to
be
clear
that
we've
seen
obviously
the
explosive
growth
in
the
open
source
project.
You
know
the
number
of
them
over
the
last
several
years.
Right
now
we
see
the
vendor
ecosystem,
leveraging
those
projects
to
bring
various
open
source
based.
You
know,
cncf
open
source
based
projects
to
Market,
in
that
you
know
in
whole
ecosystem.
K
K
Right,
there's
also
one
thing:
I
forgot
to
put:
we
forgot
to
put
on
a
slide
and
I
just
didn't,
want
to
lose
to
lose
sight
of
it
and
that's
the
effort
to
add
profiling,
continuous
profiling
or
profiling
reports
as
a
formal
signal
type
to
open
Telemetry,
which
we've
reported
on
it
in
past
months,
that
that
remains
ongoing.
It's
transitioned
to
a
more
technical
implementation,
focused
discussion
in
open
Telemetry
itself
within
that
umbrella.
Now
that
it's
a
formalized
work.
K
I
B
I
B
D
B
Know
yeah,
that
was
that
was
the
result
and
again
the
open,
Telemetry
project
GC
does
tend
to
meet
around.
You
know
having
guidelines
from
the
cncf
to
kind
of
handle.
You
know
different
interveetter,
you
know
conversations
or
in
public,
because
I
think
that
you
know
at
some
point.
The
project
itself
is
focused
on
the
technical
aspects
right
and
and
really
when
there
are
inter
vendor.
You
know
discussions
or
you
know
some
kind
of
which
shows
up
and
influences
the
project.
B
It
is
something
where
we
would
love
to
have
the
cncf.
You
know
press
liaison,
for
example,
to
kind
of
help
in
there,
because
again
there
were
you
know
a
couple
of
reporters
who
reached
out
and
kind
of
pressurized
some
of
the
maintainers
to
make
statements.
So
it
is
something
that
I
think
needs
to
have
again
the
same
kind
of
communication,
where
there
is
a
clear
guideline
that
hay
projects
can
reach
out
to
press.
B
D
So
you
know
we
were
all
watching
it
right
so
and
we
were
waiting
for
to
see
if
you
can
resolve
it
within
the
tag
or
you
would
come
to
us,
and
you
know
we
we
were
waiting
for
that,
but
I'm
glad
it
got
sorted
out.
But
yes,
I
think
it
took
some
time
and
some
effort
from
all
of
you
to
like
get
every
everything
in
a
line.
But
yes,
I,
agree
with
you.
We
should
have
a
little
bit
more
set
of
things
that
we
need
to
so
next
time.
B
And-
and
you
know
again,
these
kind
of
things
can
happen
right
because
there
are,
and
cncf
is,
you
know,
has
a
amazing
set
of
contributors.
You
know
coming
in
from
the
different
members
of
the
industry,
but
also
they
are
competitors
often,
and,
and
you
know
it
is
something
that
where
we
really
don't
want
our
projects
to
be
affected
by
you
know
that
kind
of
an
interaction
so
having
some
clear
guidelines
there,
and
perhaps
you
know,
having
some
clear
process.
B
H
H
H
You
know
users
could
get
familiar
with
kubernetes
and
Prometheus
as
the
first
two
as
the
first
two
projects
inside
of
this
demo
and
so
like
carrying
along.
In
that
same
vein,
this,
this
Cloud
native
playground,
is
something
that
I
wanted
to
raise
up
today,
as
as
an
initiative
from
the
Mastery
project
that
I
wanted
to
get
some
visibility
to
Toc
members,
maybe
see
how
much
you
all
feel
like
this
makes
sense
that
other
projects
might
want
to
participate
in
this.
The
cloud
native
playground.
H
D
D
H
A
D
Absolutely
yeah
equinix
is
very
easy,
like
just
in
the
last
week,
I
was
able
to
set
up
some
stuff
for
one
of
the
projects,
so
yeah
I
think
we
should
be
able
to
get
get
something
together,
especially
if
you
want
other
projects
to
do
more
here,
it
would
make
sense
for
it
to
be.
You
know
not
tied
just
to
one
sandbox
project,
but
also
okay,
yeah,
so
one
question
I
had
for
you
was
I've,
been
hearing
fragments
of
conversations
around
like
a
CMI
V2
of
you
know.
D
The
specification
is
the
tag
one
of
the
papers
where
we
would
be
able
to
collect
people
together
because
it's
happening
all
over
the
place
like
some
stuff
in
continuity.
Some
in
kubernetes,
some
in
like
a
repo
called,
continue
networking.
So
I
I,
don't
know
if
you
want
to
like
pull
together,
people
to
say:
hey,
let's
go
do
this
and
let's
see
especially
because
you
know,
there's
a
lot
of
good
people
in
this
tag
and
they've
done
they've
seen
it
all
before,
so
that
that's
why
I'm
curious?
H
H
D
I
The
yeah
I
I,
like
the
idea
of
this,
like
the
playground,
the
set
box,
you
know
environment,
for
people
to
try
out
different
projects
right,
I,
think
that's
good,
and
if
that's
you
know
that
can
take
off.
You
know
I
think
I'll
follow
on
what
we
you
know
you
can
do
is
to
publish
you
know
some
data
on.
You
know
users.
Experience
of
using
you
know
these
different
projects
right,
so
I
think
that
information
will
be
very
useful
for
the
end
user
to
you
know
to
know
yeah
to
choose.
I
H
Yeah,
you
have
to
regurgitate
that
briefly,
like
yeah.
Not
only
is
it
for
the
service
mesh
projects,
but
just
really
really
any
any
workload
or
any
project
that
runs
on
kubernetes
or
and
basically
all
of
the
cncf
projects,
but
like
I,
think
in
part
what
Kathy,
what
you
were
saying
is
yeah
the
ability
it
gives
some
of
the
projects
event
an
alternative
venue
to
promote
best
practices
with
their
projects
that
they're
able
to
share
some
of
those
configuration
best
practices
in
a
sandbox
type
environment.
I
L
Hello,
so
a
few
updates
from
the
tag
we
created,
two
new
working
groups
or
we.
So
these
are
also
the
first
working
groups.
The
first
one
is
around
Communications
with
the
streams
events
survey
like
in
general
communication
between,
like
also
different
organizations
and
projects
and
so
on,
and
then
also
we
plan
to
do
a
website.
L
So,
for
example,
about
the
survey
last
year
end
of
last
year
we
created
the
survey
we
plan
to
do
this
not
like
every
month
or
so,
but
if,
if
it
like
makes
sense,
so
maybe
we
have
like
a
small
team
around
events,
a
small
team,
around
survey
and
so
on.
So
you
will
see
how
it
goes,
but
this
is
like
roughly
the
plan.
Maybe
this
will
also
change,
maybe
create
like
new
working
groups
or
not,
but
this
is
like
the
starting
point.
L
L
So
this
is
not
100
clear.
We
are
at
the
moment
in
contact
with
the
green
suffer
Foundation
because
they
are
also
looking
into
the
same
direction
and
they
have
not
yet
something
set
up
so
possib.
So
one
possibility-
and
maybe
this
is
like
also
like
likely-
that
we
have
both
things
so
we
integrate
with
the
cloud
native
maturity
model
and
also
contribute
to
the
green
software
Foundation
or
just
collaborate
in
that
way
about
the
landscape.
L
So
we've
been
working
working
on
collecting
tools
and
I
can
generally
like
landscape
stuff
organizations
and
so
on
for
quite
some
time.
It's
like
not
yet
finished.
It's.
Obviously,
it's
also
not
yet
finished
for
a
first
version,
but
we
plan
to
release
it
or
the
first
version
to
show
it
in
kubecon,
EU
and
like
the
third
stream
in
the
second
working
group,
is
around
best
practices.
L
So
there's
already
a
few
best
practices
in
the
green
software
space,
but
they
are
not
mapped
to
Cloud
native
and
not
to
the
cloud
space
they're
like
General
to
software
engineering.
So
our
idea
was
to
basically
frame
this
in
the
software
space
in
the
cloud
native
space
and
yeah.
We
are
starting
with
these
working
groups.
We
plan
to
do
a
maybe
bi-weekly
meeting
or
something
like
this
see
how
it
goes
and
yeah
about
the
next
topic.
L
I
already,
like
briefly,
talked
about
the
survey,
so
we
correct
collected
a
few
like
responses
to
the
survey
and
we
are
working
on
a
like
a
presentation.
We
are
currently
thinking
about
how
to
publicize
this.
It's
not
like
finalized,
but
it
looks,
looks
interesting.
So
probably
we
will
write
a
blog
post.
Maybe
if
there's
enough
content,
maybe
we
can
also
do
like
a
like
a
short
webinar,
maybe
20
minutes
or
something
like
this
to
just
to
show
the
results.
L
So
our
like
idea
currently
is
that
we
have
like
two
Milestones,
like
roughly
two
Milestones,
so
keep
going
to
use
Milestone
and
the
kubecon
in
a
milestone,
and
that
we
have
like
a
couple
of
things
that
we
want
to
like
do.
In
half
a
year
roughly
so,
for
example,
for
kitchen
EU,
we
have
a
milestone
where
we
want
to
like
have
a
landscape
document
ready
and
show
already
like
our
first
ideas
about
the
maturity
model,
and
people
have
a
discussion
tomorrow
about
the
Milestones
itself
and
also
like
meetups
tag
meetups.
L
L
So
we
discussed
in
the
tech
meetings
that
we
would
like
to
have
project
meetings
just
to
connect
with
the
creators
of
these
projects
and
also
to
introduce
them
to
the
cncf
and
then
just
to
have
this
communication
flowing.
So
we
want
to
have
like
every
month-
or
maybe
we
also
can
increase
this,
but
every
month,
roughly
a
presentation,
half
an
hour
or
something
about
some
tool.
L
L
I
I
would
give
it
like
short
in
the
last
meeting.
One
one
contributor
race
raised
the
issue
that
we
would
like
to
like
elaborate
a
little
bit
more
in
how
to
contribute
to
the
tags
or
to
the
cncf
from
like
a
non-technical
point
of
view.
So
if
you
don't
know
GitHub,
if
you
don't
know
anything
like
this,
so
we
we
look
into
this
and
we
agreed
on
an
abbreviation,
because
environmental
sustainability
is
very
long.
L
D
M
M
There's
55
different
proposals
across
the
CNC
projects
for
things
for
mentees
to
work
on.
So
if
anybody
is
connected,
particularly
with
universities,
please
share
out
that
information
which
you
can
get
from
our
mentorship
repo
I.
We
already
proposed
this
to
the
TOC,
adding
governance
review
as
part
of
graduation,
and
you
all
said
yeah.
M
We
have
restarted
maintainership.
So
again,
please
share
this
with
any
maintainers
that
you
work
with
we're.
Gonna
have
one
in
February
13th
on
managing
non-code
contributors
for
your
project,
because
we
find
that
a
lot
of
projects
are
missing
out
on
a
very
good
source
of
contributors,
because
they
don't
have
specific
programs
for
non-code
contributors
and
we're
also
planning
on
trying
to
have
a
lot
in
in-person
maintainer
circle
in
Amsterdam
space
permitting
the
so.
But
please
share
that.
First,
one
with
anybody.
D
M
A
F
B
Yeah
and
just
to
call
out
Josh.
Thank
you
again
for
calling
this
out
because
again
as
projects,
even
a
hotel
is
not
aware
of
this,
so
this
g-soc
bush,
so
that
would
be
useful
to
communicate
to
the
projects.
If
you
can
help
in
any
way
you
know,
I
can,
and
you
can
point
me
to
some
material.
We
can
gladly
you
know
remind
different
projects,
but
it's
also
that
outreachy,
for
example,
is
also
accepting
applications
again.
Maybe
having
a
more
comprehensive
mentoring
list
may
be
useful,
because.