►
From YouTube: CNCF TOC Meeting 2022-10-4
Description
CNCF TOC Meeting 2022-10-4
C
D
D
C
D
D
D
I
know
that
there's
been
some
conversations
like
you
know
about
other
things
to
be
able
to
discuss.
We
will
drop
those
into
questions
and
happy
to
be
able
to
like
take
questions
and
chat
as
we
move
along
in
here.
So
tag
updates,
I'm
going
to
pass
us
to
tag,
storage
and
I
know.
You've
got
a
lot
in
here,
so
so
take
it
away.
Yay.
E
E
E
So
we're
going
to
add
a
disclaimer
saying
you
know
this
is
a
community
maintained
use
cases.
So
it's
not
like
we
are
recommending
this
project
for
anything,
but
it's.
This
is
companies
maintained,
so
we'll
add
a
disclaimer
that,
like
that
I'd
like
to
see
if,
if
there's
any
concerns
from
POC
regarding
this.
E
And
other
than
that,
yeah
I
have
a
map
here,
so
open
EBS.
So
I
think
this
incubation
request
is
still
ongoing
and
there
were
some
concerns
regarding
lack
of
maintainers.
There's
the
issue
open
for
that
I
believe
the
team
has
been
trying
to
address
those
issues
and
curve
we
so
they
presented
a
tech
storage.
Also
a
TLC
voted
for
that
it
passed
the
majority
I
believe
it's
still
not
included
yet
because
they
still
need
to
get
this
license.
Issue
resolved.
D
D
E
F
C
D
E
Yeah
well
yeah,
because
the
last
time
I
think
we
basically
just
tell
them
that
we
will
look
at
their
presentations
and
get
back
to
them.
So
we
also
have
not
told
them
that
we
recommended
the
sandbox,
so
I
will
send
them
a
note.
Ask
them
to
reapply
foreign
yeah
so
other
than
that
I.
Think
there's
a
like!
We
already
talked
about
the
supply
paper,
so
there's
a
no
new
update
since
our
previous
update,
I
think
I'm
all
set.
F
So
I
I
did
have
a
general
question:
how
how
was
the?
How
are,
how
is
the
tag
helping
with
or
working
on
the
CSI
specifications
themselves
say
that
somebody
wants
to
propose
a
change
like?
Is
it
still
the
same
process?
You
work
on
the
specification.
Part
first
make
a
change,
and
then
how
do
you
roll
it
out?
Yes,
yes,
yes,.
E
So
you're
saying
like
if
there
is,
if
someone
want
to
propose
a
new
change
to
see
that
how
does
that
go
through
oh
yeah?
So
basically,
normally
people
will
go
to
this.
There
is
a
community
sink
that
happens
once
a
month,
and
so
people
normally
go
there
and
you
know
present
and
then
they
can
submit
APR.
Well,
actually,
you
know
now
I
actually
have
a
PR
there,
so
from
appear
to
say,
I
want
to
bring
in
those
new
changes,
and
normally
they
would
ask
you
to.
E
E
Yeah
and
then
you
know
once
it's
passed,
then
that
can
get
merged
so
right
now
we
actually
have
quite
a
few
new
things,
pretty
big
items
actually
right
now:
oh
okay,
yeah.
We
are
trying
to
yeah
we're
trying
yeah
there's
a
I,
have
a
proposal
for
modern
group
and
one
group
snapshot.
So
that's
a
proposal
in
CSS
that
knows
also
cap
in
kubernetes,
Upstream,
okay,
there's
also
another
proposal
about
chain
block
tracking.
That
also
has
a
proposal
on
adding
some
new
new
things
in
cssback.
G
Son's
video,
maybe
I,
do
apologize
if
I
disappear
again.
I
will
proceed.
Thank
you.
A
huge
Oceanic
world
of
thanks
to
everybody
who's
helped
set
up
Cloud
native
security
con.
This
is
the
spin
out
event
from
the
day,
Zero
and
day
minus
one
events
at
Yukon,
so
we
will
have
a
multi-track
two-day
event
in
Seattle
in
February
and
then
there's
a
proposal
to
intertwine
the
same
kind
of
talk
and
track
titles
into
a
security
Village
in
the
main
cubicon
event
to
replace
those
Day
Zero
and
day
minus
one
events.
G
It's
usually
exciting
and
I'm
very
pleased
to
be
involved.
Then
the
work
we
have
been
undertaking
there
is
a
supply
chain
security
survey
that
has
gone
out.
This
is
looking
to
understand
where
we
best
focus
our
efforts
for
any
future
recommendations
that
the
group
makes
by
understanding
what
projects
or
which
projects
are
in
use
by
cncf
projects.
So
what
type
of
build
systems?
What
type
of
tooling
how
people
are
looking
to
secure
their
supply
chain?
And
indeed,
what
does
the
supply
chain
mean
to
various
people?
G
The
goal
here
is
to
be
able
to
work
through
the
threat
model
for
an
individual
project
within
one
to
two
working
group
sessions.
So
scoping
the
thing
narrowly
time
boxing.
It
and
lowering
the
barrier
to
adoption
of
the
barrier
to
entry
for
new
security
threat,
modeling
contributors,
the
personal
passion,
has
been
very
very
pleased
that
we're
moving
forward
with
that.
G
And
finally,
these
Security
reviews.
You
can
see
Cube
failure,
flux,
multi-tenancy,
they've
performed
the
self-assessment
and
that
will
go
into
threat,
modeling,
Argo
and
Cube
Edge.
The
proposition
is
to
use
that
lightweight
threat,
modeling
process
on
the
flux,
multi-tenancy
audits,
as
the
first
guinea
pig.
If
you
like
this
thing,
that's
all
from
me
anything
else
from
you,
Brandon.
H
Yeah
I
guess
I.
Can
the
the
V3
of
white
paper
you're
talking
about
just
now,
I
think
one
of
the
two
main
focuses
adding
in
content
on
confidential
Computing,
as
well
as
taking
some
of
the
the
content
that
that
we've
written
out
as
part
of
the
serverless
working
group
and
just
integrating
the
anti-v3
instead
of
having
a
separate
white
paper
other
than
that
I.
H
Think
just
just
a
quick
note
on
the
zero
trust
working
group
that
that
we
are
spinning
up,
I
think
one
of
the
the
one
of
the
issues
that
we're
trying
to
to
solve
amongst
the
the
whole
list
of
misconception.
So,
sir
trust
is
like
you
know
a
lot
of
times.
People
are
still
thinking
about
parameter,
security
and
I.
Think
that
is
kind
of
a
lot
of
the
term
parameter
security
encoded
in
a
lot
of
security
and
compliance
documents,
and
that
proves
to
be
very
difficult
for
zero
trust
adoption.
H
D
A
A
H
So
we
we
have
a
process
that
projects
can
can
come
in
like
request
assessment
and
like
we
I'm
going
to
put
a
link.
Oh
thank
you
on,
like
okay.
We
we
need
the
self-assessment
document
to
be
created
by
the
hunter
project,
and
then
we
have
someone
review
it
and
there's
a
whole
process
around
that.
We
have
a
key
of
from
projects
that
are
doing
that.
H
The
the
thing
that
we
don't
have
like
an
official
mapping
of
like
okay.
If
your
sandbox
process
project,
you
need
to
do
a
self-assessment
also
on
the
general
ideology
we
have
usually
is
for
most
projects
that
are
going
for
incubation,
at
least
having
a
self-assessment
which
is
part.
One
of
the
review
is
something
good
to
have.
H
H
B
Okay,
I'll
add
on
there
any
project
within
the
cncf,
sandbox
or
incubation
is
more
than
welcome
to
complete
a
self-assessment.
The
self-assessment
is
set
up
and
design
to
assist
projects
and
understanding
more
about
the
security
and
the
architectural
design
of
the
project
itself
and
to
kind
of
give
them
more
of
a
security
mindset
and
a
lens
around
any
future
development
and
ongoing
work
within
the
project.
It
also
is
incredibly
useful
as
an
initial
set
of
security
documentation
for
any
potential
adapters
to
go
through
and
read
and
understand
kind
of
what
did
a
security
considerations.
B
The
project
has
already
undertaken
any
kind
of
security
features
and
functionality
within
those
projects.
So
it's
something
that
I
would
personally
strongly
recommend
all
projects
take
a
look
at
and
see
if
it's
something
that
they
want
to
keep
within
their
repo
or
file
as
a
PR
against
the
tag
security
repository
that
way,
they're
centrally
located
and
anybody
can
go
and
access
them
and
they
can
link
it
back
in
their
original
box.
A
F
H
More
people
would
definitely
be
helpful,
I
think
we,
especially
in
the
area
of
Security
reviews,
that's
an
area
that
we've
had
a
little
bit
of
a
retention
problem,
because
it's
a
pretty
involved
effort
I
think
we're
trying
to
find
ways
to
do
this.
We've
talked
about
with
Amberley
about
you
know,
having
badging
and
things
like
that.
I
think
that
would
be
helpful,
but
I
think
out
of
most
of
the
projects,
I
would
say.
F
I
We
we've
had
some
presentations
from
different
projects
in
the
containers
and
runtime
space.
We
have
one
coming
up
in
our
next
meeting.
It's
called
Lima,
it's
a
Linux
virtual
machines
and
it's
basically
kind
of
like
a
container
ID
for
Mac.
So
it's
a
way
to
to
run
container
D
on
a
Mac
which
is
kind
of
something
requested
by
developers.
So
I'm
excited
about
that
they're
also
applying
for
sandbox
I,
believe
I,
don't
know
if
they
can
accept
it.
Yet.
I
Possible
and
in
terms
of
workloads,
we
have
discussions
with
this
project
called
westme
and
it's
basically
a
webassembly
interpreter.
So
we
have
a
discussion
going
on
with
them
and
hopefully
one
and
a
half
percent
representation
from
them
pretty
soon
so,
and
hopefully
we
have
more
involvement
from
them.
I
I
We're
also
excited
about
this,
so
we
reached
out-
and
hopefully
we
have
a
presentation
from
them
pretty
soon.
There's
also
a
discussion
on
standardization
of
the
out
of
memory
communicate,
kill
communication
between
the
cubelet
and
the
runtime.
This
is
going
on
between
attack,
runtime
mailing
list
and
slack
Channel
and
kubernetes
sick
node.
So
hopefully
we'll
see
more
progress
there.
I
Also,
we
have
in
a
different
scope,
project
or
open
policy
registry.
This
is
project
related
to
security,
but
also
the
interesting
part
is
with
the
attack,
runtime
or
relationship
with
tag.
Runtime
is
that
it
is
using
oci
to
open
container
interface
to
store
open
policies,
and
we
have
a
presentation
from
there
on
in
our
meeting
on
October,
20th
and
finally,
on
some
activities
with
within
the
tag
our
batch
system
initiative
working
group
finally
got
approved
so
excited
about
that.
I
So
folks
on
the
working
group
are
starting
to
make
some
progress
and
do
some
work.
We'd
also
have
keep
calling
North
America
in-person
session
on
unicorn
and
unicraft.
It's
actually
going
to
be
given
by
Alexander,
Zhang
I.
Think
he's
on
the
call
now
so
excited
about
that
too,
and
we
continue
to
have
conversations
and
interest
in
the
community
about
having
a
working
group
related
to
unit
kernels,
as
well
as
a
working
group
related
to
webassembly.
D
A
Hey
hi,
everyone
sweet
good
to
meet
everyone
today,
just
wanted
to
give
a
quick
update
on
all
the
happenings
at
the
observability
tag:
lots
of
activity
we
first
of
all
finally
have
a
new
logo,
so
we
all
as
a
community,
decided
finally
and
picked
the
The
Owl
and-
and
it's
a
cute
one
so
good
to
good
to
find
me,
you
know,
be
consistent
lots
of
activity
around
you
know
throughout
the
quarter
on
a
different
projects
as
well
as
different
initiatives.
As
you
can
see,
there's
a
lot
of
discussion.
A
That's
been
happening
in
the
community
as
well
as
work
around
interoperability
of
existing
standards
in
observability,
especially
with
the
open,
Telemetry
and
Prometheus
interop
discussions
that
are
ongoing
in
the
Prometheus
work
group,
interoper
group,
in
a
hotel,
open,
Telemetry
and,
and
especially
there's
a
lot
of
work
happening
around
the
advanced
histograms
support
both
on
the
Prometheus
project
as
well
as
Hotel.
It's
a
fair
bit
of
work
and
discussion
around
there.
A
A
The
other
area
that
I'd
like
to
call
out
is
that
there's
a
fair
bit
of
work.
That's
happening
around
the
cortex
project,
Health
discussion,
we've
had
discussions
with
dims
is
you
know,
leading
that
from
the
TOC
as
well
as
working
closely
with
the
cortex
project,
mean
containers
to
be
able
to
then
provide
feedback
and
report
back
to
the
governance
committee
as
well
as
the
TOC,
and
this
is
something
again
that
we've
made
good
progress
on
and
I'd
like
to.
You
know
again.
A
If
you
want
to
follow
details,
the
issue
is
right
there
and,
and
please
feel
free
to
kind
of
dive
into
that
I'll.
Keep
you
folks
updated
as
we
make
you
know,
reports
and
write.
You
know
the
findings
down,
but
we
have
a
good
update
coming
in
from
the
cortex
project
at
this
point
and
there
are
more
maintainers
who
are
getting
involved
in
being
able
to
contribute
to
the
project.
So
that's
that's
exciting,
but
there's
still
work
to
be
done
there.
Obviously
a
couple
of
other
areas.
A
Of
course
we
continue
to
have
good
presentations
in
the
tags
and
discussions
around
new
open
source
projects.
Odigos
was
one
of
the
projects
that
was,
you
know,
discussed,
and
there
was
a
technical
walkthrough
on
it.
We've
also
started
a
series
of
observability
expert
speakers
coming
and
speaking
at
the
tag
and
that's
you
know
pulled
in
a
lot
of
interest.
Liz
Fong
Jones,
who
was
presenting
on
evolving
and
hybridizing
Signal
types
spoke
in
August.
A
We
also
have
a
couple
more
talks
coming
up
by
Yuri,
one
of
the
key
maintainers
in
Jaeger
presenting
in
October
and
then
Jonah
Koval,
who
is
an
expert
on
logs
presenting
in
November.
So
again,
we
hope
that
this
will
actually
help
in
in
also
pulling
in
and
answering
many
of
the
end
user
questions,
because
you
do
tend
to
get.
A
You
know
a
good
mix
of
vendors
as
well
as
end
users
in
the
tag
for
observability,
so
overall
lots
of
activity,
but
we
will
be
actually
doing
a
update
and
a
meeting
at
the
ad
cubecon
in
coming
up
in
three
weeks,
and
we
also
hope
to
have
a
good
agenda
and
plan
for
some
of
the
projects
and
initiatives
that
we
intend
to
carry
out
next
year
so
exciting
times
again.
We
continue
to
see
more
in
engagement,
but
would
love
to
see
more
even
more
going
from
there
and
that's
about
it.
F
So
I
do
have
a
question,
so
I
was
very
happy
to
update
all
our
hotel
libraries
from
Italy,
updated
first
and
then
kubernetes
updated.
It
took
a
little
bit
of
time
to
get
it
right
because
there
are
so
many
libraries
and
the
version
numbers
are
like
all
over
the
place
so,
but
if
we
were
able
to
pull
that
off,
so
thanks
for
that
I
think
it's
getting
better.
F
A
Yes,
actually
so
one
of
the
things
that
I
would
like
to
call
out
and
open
metrics
is
very
integral
in
the
discussion
around
interrupt
providing
interoperability
as
a
you
know,
in
the
protocol
between
Prometheus
and
otlp
right,
which
is
the
open
Telemetry
protocol,
so
open
metrics
has
been
very
integral
to
that
whole
process
and
in
fact,
Hotel
you
know,
has
supported
open
metrics
first
in
terms
of
the
existing
standard
and
Prometheus,
as
a
project
has
also
been
working
towards.
You
know
addressing
some
of
the
implementation
differences
that
they
have
with
open
metrics.
A
So
that
is
something
we'll
continue
to
work
on,
but
you
know
open
metrics
obviously
goes
without
saying
it's
an
integral
part
of
supporting
a
metrics
protocol
on
hotel,
and
there
is
some
discussion
around
that.
As
I
said,
you
know
there
and
maybe
Richard.
You
can
also
provide
some
details
from
the
Prometheus
project,
but
there's
work,
which
is
ongoing
and
open.
Metrics,
of
course,
is
of
core.
There.
C
From
the
Prometheus
side,
the
main
thing
is
high
resolution,
histograms
or
native
histograms,
depending
on
which
name
you
want
to
call
them
with,
and
that's
basically
the
interface
towards
towards
open
Telemetry
to
keep
both
the
Prometheus
high
resolution
histograms
and
the
open
Telemetry
ones
in
sync,
and
that's
also
going
to
be
the
next
major
release
of
openmetrics.
Of
course,
it's
going
to
be
breaking
along
a
few
axes.
Yeah.
A
A
Any
other
questions
attempts
to
your
point
about
the
installation
and
the
the
versioning
differences.
If
you
will
we'll
take
a
look
at
that
on
the
hotel
side,
because
I
I
think
you
know
again,
our
objective
is
to
continue
to
reduce
complexity,
and
you
know
ensure
that
there
is
clear
dependency
association
with
versioning,
consistent
version.
I
A
A
E
C
J
C
J
And
then
we
have
an
upcoming
presentation.
So,
speaking
of
istio,
there's
a
upcoming
presentation
from
a
project
called
slime.
It's
it's
a
project
that
enhances
istio-based
service
meshes
or
enhances
ECU
deployments
with
additional
management
intelligence.
We've
got
a
few
compelling
examples
of
of
how
to
do
that,
so
the
service
mesh
management
and
then
in
the
working
and
so
they're
I
think
they're
they're
filed
for
slime
is
proposed
for
sandbox
and
is
asking
for
a
time
to
present,
and
so
that
should
be
very
shortly
speaking
of
presentations.
J
This
Thursday
is
our
tag
Network
meeting
by
the
way,
just
a
public
service
announcements
for
the
hundreds
of
people
that
attend
Tech,
Network
meeting
we
switched
it
from
we've
had
a
bump
in
Cadence
from
the
second
and
fourth
Thursdays
of
the
month
to
the
first
and
the
third
I
believe
kubernetes
Sig
Network
had
recently
reshuffled
some
of
their
meetings
that
turned
out.
We
were
overlapping,
and
so,
given
the
two
highly
related
topics,
we
decided
to
move
around,
and
so
so
first
and
third
Thursdays
for
tag
Network.
J
So
this
week
is
the
first
Thursday
of
October
and
we'll
have
a
project
update
from
the
the
project
network
service
mesh
NSM.
The
project
update
is
the
details
that
you
can
see
here,
but
a
bit
of
maybe
even
live
demonstration
of
how
network
service
mesh
is
a
mesh
for
up
can
be
used
as
a
mesh
for
other
meshes,
so
network
service
mesh,
going
up
to
layer
three
and
then
having
other
service
meshes
operate
on
top
of
that.
So,
if
you're
into
that
kind
of
thing,
we'll
see
you
on
Thursday.
F
J
Yeah
I
would
have
I'm
hopeful
for
a
bit
of
an
uptick
in
the
the
service
mesh
performance
project
as
it
relates
to
you
know.
One
of
the
compelling
characteristics
of
EV
of
the
use
of
ebpf
is
about
performance
and
that
this
is
again.
Maybe
this
is
too
hand
wavy,
but,
but
is
that
you
know
like,
like
any
system
design,
there's
some
trade-offs
that
happen
between
maybe
you're
getting
a
higher
performance.
J
A
bit
of
that
there's
actually
there's
a
great
book
on
this
subject
written
by,
but
no
it's
free,
and
it's
really
it's
really
short,
but
it
articulates
the
notion
that
you'll
yeah
yeah,
like
hey
if
you've
got
a
proxy
right.
You
know
side
card
right
next
to
your
app.
You
are
you're
risk
boundary
or
your
your
ability
to
to
secure
that
those
transactions
is
really
granular,
and
so,
if
your
proxy
or
anything
that's
controlling
those
transactions
is
Damon
set
base.
J
Or
is
you
know,
node
based
it's
a
little
bit
of
a
different
model
that
some
of
the
models
that
are
coming
out
or
maybe
helping
overcome
that
helping
bring
that
closer
toward
the
side,
car
I?
Guess
what
I'm
trying
to
point
out
is
like
it's
not
a
it's.
It's
a
sure.
You
users,
like
in
istio's
case,
need
to
make
it
they
do
have
to
make
a
comparative
Choice.
J
What
was
I
trying
to
say
is
that
yeah,
you
won't
one.
Doesn't
they
are,
and
so
in
in
that
is
geez
boy.
I
haven't
really
formulated
my
thoughts
very
well
clearly
and
concisely.
Is
it
like
it's
still
not
like
an
Apples
to
Apples
like
like
yeah
they're
gonna
have
to
make
a
choice
so
they're
gonna,
compare
between
the
two
modes
and
then
figure
out
if
one
has
all
the
functions
that
they
want
and
they
want
to
trade
it
off,
for
whether
it
was
performance
or
a
different
use
case
and
so
yeah.
J
C
D
K
Hi,
oh
well,
hello,
everyone,
I'm,
Catherine,
the
new
tech
contributor
strategy
co-chair
so
just
wanted
to
say.
First
I
really
appreciate
the
trust
that
Don
and
Josh,
and
everyone
else
have
placed
in
me.
So
I'm
really
excited
to
be
here
and
thank
you.
Okay.
So
last
time
Don
mentioned
that
we
were
working
on
a
survey
with
the
cncf
and
basically
the
goal
is
to
understand.
Contributor
friction
points,
the
surveys
open.
We
have
73
respondents
so
far.
That
is
not
a
lot
and
we
need
your
help.
K
I,
probably
don't
need
to
explain
why
this
is
important.
I
think
everyone
on
this
call
gets
it.
So
please
please
please,
please,
please
help
us
get
the
word
out
mention
it
during
meetings.
If
you
have
any
talks
share
on
social
media,
maybe
there's
a
company
newsletter
you
where
it
would
make
sense
to
kind
of
add
like
a
little
call
to
action
or
any
other
ideas
that
you
may
have.
The
cncf
wants
to
announce
the
results
during
kubecon.
K
So
there
is
not
a
lot
of
time,
so
we
really
need
to
mobilize
people
here
ideally
quickly.
We
will
have
a
kubecon
kiosk
in
the
project
Pavilion.
So
really
excited
about
that.
Our
goal
is
to
raise
awareness,
so
we'll
be
showcasing
the
different
resources.
We
have
telp
project
project
owners,
how
we
can
help-
and
we
also
created
this
fun
tag
harrowing,
which
was
donated
by
the
very
talented
illustrator
Juan
Ho,
and
you
can
help
too.
K
So
if
you're
at
kubecon
swing
by
the
kiosk,
get
your
stick
it
on
your
laptop
help
us
raise
awareness,
so
people
know
about
the
tag
moving
on
to
mentoring,
so
we
expect
to
complete
110
mentee
projects
across
the
cncf,
that
is
Linux
foundation
and
Google
summer
of
code.
Gold
was
a
hundred,
so
that's
amazing
right
so
over
achieving
here
we
have
27
mentees
who
have
completed
the
Linux
Foundation
project
so
far,
but
we
do
want
to
do
more
Outreach.
K
So
if
anyone
is
interested
in
helping
coordinate
that,
please
please
reach
out
via
slack
or
join
the
mentoring
meeting,
and
we
can
coordinate
also
very
excited
about
that.
We
are
starting
our
New
Zealand
indigenous
recruitment
program.
That
is
a
experiment
where
we're
trying
to
reach
people
outside
of
traditional
contributor
targets,
in
this
case
targeting
the
Maori
Talent.
So
it
is
an
awesome
initiative
and
hopefully
this
will
become
a
blueprint
for
the
future
to
reach
out
to
other
communities
as
well
on
the
governance
site,
it's
been
mainly.
K
F
Thank
you.
Congratulations
and
I
wasn't
sure
if
you
would
make
it
here,
but
you
did
thank
you.
So
we
left
some
notes
on
the
chat
on
like
how
we
can
spread
the
word
on
the
contributor
survey.
So
let's
do
a
few
things
there
and
see
if
we
can
bump
it
up.
So
let's
do
these
things
this
week
and
then
see
the
response
next
week.
F
F
D
C
K
L
Yeah
I'm
I'm
on
the
so
the
Alexander
still
planning
for
that
part
of
the
idea
is
that
we
actually
want
to
make
use
of
the
data
in
the
survey
to
look
at.
What's
going
to
be
effective
and
helpful
for
the
projects
I.
As
I
said
in
the
contributor
strategy
thing,
we
actually
tried
doing
something
like
this
in
kubernetes
and
it
was
not
successful.
L
So
we
really
want
to
take
a
different
and
well-considered
approach
rather
than
just
throwing
something
out
there,
because
otherwise
it'll
end
up
with
a
repeat
of
the
kubernetes
experience
where
we
have
a
board
up,
but
there
are
no
opportunities
listed
and
and,
as
a
result,
it
isn't
really
useful
to
anybody.
So
the
so
we're
not
rushing
into
this.
D
K
Yeah,
but
definitely
something
that
we're
working
on
Kathy
and
we
do
believe
it's
it's
important
and
useful.
But
yes
just
said:
we
want
to
learn
from
what
happened
in
the
past.
What
didn't
work
and
try
yet
to
learn
from
that,
but
yeah
we
do
have
people
who
are
interested
in
working
on
it.
So
I
think
it's
gonna
happen.
F
M
Sure
so
this
actually
originated
from
the
pr
that
was
added
about
requiring
working
groups
to
be
part
of
tax.
So
to
set
some
contacts,
there
were
two
things
that
came
up
with
this
issue,
so
one
was
slightly
tactical.
One
was
a
little
strategic,
so
the
Tactical
part
was
that
we
want
to
have
a
single
source
of
Truth
for
tax
and
working
groups.
That
also
should
be
machine
readable.
We
were
discussing
about
this
and
slack
and
the
TOC
Channel
just
now.
M
We
also
want
to
have
some
more
information
added
to
it
about
like
who
are
the
chairs
and
leads
for
these
tags.
When
were
these
leads
added
and
so
on,
and
we
do
something
similar
in
kubernetes
already
for
six
and
working
groups
and
I
helped
maintain
that
so
I
decided
to
pick
it
up
so
I'm
going
to
create
a
PR
for
it.
M
There's
one
more
strategic
aspect
around
this,
so
the
other
question
open
question
that
came
up
was
whether
Toc
needs
to
approve
working
group.
Creations
or
tags
have
the
autonomy
to
just
go
and
create
it
themselves.
I
think
that
was
still
open,
but
the
consensus
was
that
first,
we're
going
to
get
a
picture
of
what
working
groups
exists,
which
ones
are
active
and
so
on
dims
you
had
a
PR
open
for
it.
I
think
so.
I
wanted
to
talk
about
that
as
well.
M
F
I
do
have
a
to-do
item
to
go
talk
to
the
serverless
working
group,
because
I
think
that
is
the
one
that
is
left
from
the
list
that
we
had
there.
So
don't
use
that
as
a
blocker
for
this
you
know
we
can.
We
can
give
them
leniency
or
we
can
special
cases
for
now.
Okay,
so
let's
just
assume
that
all
the
working
groups
belong
to
a
tag
and
maybe
you
can
propose
a
structure
for
the
yaml
file
and
then
we
can
like
debate
about
it
on
the
PRN
itself.
D
C
D
F
A
Was
I
just
had
a
quick
question?
Is
there
typically
a
retrospective
after
a
kubecon
that
comes
in
from
the
tags?
You
know,
because
I
would,
if
there
isn't
I'd
like
to
suggest
one
and,
and
the
reason
is
that
you
know
often
we'll
get
a
fair
bit
of
feedback
at
kubecon
on
various
projects.
You
know
in
each
of
the
areas,
and
that
would
be
good
to
communicate
back
to
the
fields.