►
From YouTube: CNCF TOC Meeting 2023-06-06
Description
CNCF TOC Meeting 2023-06-06
B
A
A
As
a
reminder,
we
are
all
in
all
in
compliance
with
the
antitrust
policy
notice
for
this
meeting
and
if
you're
here,
you
found
where
we're
at
the
meeting
Logistics
are
on
the
screen,
they're
also
in
the
TOC
repo
next
slide.
We
have
several
Toc
members
here
today
and
we'll
be
doing
some
updates
from
the
tags
and
then
any
additional
questions
for
everyone
towards
the
end
of
the
call.
So
let's
go
ahead
and
get
started
with
tags
stored
up
projects
applying
to
move
levels,
yeah.
A
B
C
A
A
A
D
There's
a
there's
a
quite
a
lot
hidden
in
that
last
sentence
there.
This
is
projects
waiting
for
sponsors
are
on
the
meeting
minutes.
Doc
I
did
know
that
there
were
three
or
four
projects
that
have
been
waiting
now.
What
seems
like
six
months?
I
just
wondered
if
there
is
any
plan
on
having
more
visibility
into
allocation
responses
or
when
those
will
move
forward.
A
Yeah
so
I'll
add
on
there
Craig.
We
do
have
the
incubation
and
graduating
projects
black
backlog
on
the
TOC
project
boards,
we're
going
in
through
those
trying
to
identify
projects
that
have
been
in
the
queue
the
longest
between
the
two
of
them
we're
actively
working
through
things.
All
Toc
members
have
been
advised
that,
as
they
are
starting
to
wrap
up
and
turn
projects
over
to
public
comment,
take
a
look
in
the
backlog,
look
at
which
ones
have
been
in
there,
the
longest,
which
ones
align
with
background.
A
D
E
Okay,
hello,
everyone,
so
a
few
updates
on
some
of
the
projects.
We've
had
quite
a
quite
a
bit
of
activity
on
a
number
of
different
projects
which
are
looking
to
join
the
cncf
and
and
presenting
so
I'll
touch
on
those
first
Cloud
native
PPG
had
previously
applied
for
sandbox,
and
it's
going
to
be
reapplying.
They
are
a
an
operator
kubernetes
operator
for
postgres
that
manages
the
entire
life
cycle
of
databases
within
within
kubernetes
and
also
does
things
like
replication
and
and
other
failovers
and
high
availability.
E
E
Pelican
is
a
very
interesting
project
in
that
it
is
an
exceptionally
mature
caching,
subsystem
similar
to
Manchester
or
redis,
for
example,
and
used
to
be
part
of
the
code
base
at
Twitter.
Due
to
some
of
the
things
that
have
been
going
on
there.
The
entire
team
has
moved
on
and
they've
also
open
sourced
their
that
that
code
base
as
a
result,
and
and
has
some
it
has
some
particularly
interesting
Cloud
native
applications.
E
So
they're
looking
to
to
consider
joining
a
sandbox
X
line
is
also
very
Innovative.
They
are
deploying
new
consensus
type
protocol
called
curb,
which
is
designed
to
remove
some
of
the
latency
that
we
have
in
in
things
like
the
raft
protocols
typically
and
their
ideas,
to
have
a
strong
consensus,
key
value
store,
which
also
has
an
SCD
compatible
API.
So
there
are
some
interesting
use
cases
for
that.
E
Some
some
project
updates
coming
up
like
for
proviga
and
then.
Finally,
we
want
just
want
to
remind
everybody.
I've
sent
an
email
to
the
TOC
mailing
list
that
we're
proposing
Rafael
spazzoli
to
join
as
a
co-chair
for
the
tag.
Rafael
has
been
working
with
us
for
a
number
of
years
now,
and
then
it
was
previously.
A
tech
lead
for
the
tank
is
also
it's
a
number
of
papers
and
being
a
presenter
with
this
at
kubecon
a
few
times,
and
it's
very,
very
highly
recommended.
A
E
F
Hello,
so
I'm
pleased
to
announce
that
we
have
a
proposed
a
nomination
for
our
next
co-chair.
This
is
replacing
the
long
standing
and
long-serving
Brandon
Lum
who's
who's,
just
about
finished
with
his
term.
That
is
currently
on
the
TOC
mailing
list
for
feedback.
Secondly,
there
is
a
proposal
to
spread
out
the
chair
terms,
Environ
Nuance
of
originally
how
additional
co-chairs
were
added.
We
are
due
to
have
a
Radnor
finish
within
the
next
I
think
month
or
so,
which
would
mean
two
chairs
rotating
within
very
short
succession.
F
F
So,
thanks
to
all
the
Italian
speakers
who
have
done
a
sterling
job
of
translating
the
cloud
native
white
paper
V2
into
Italian,
that
is
now
finished
and
published
as
of
four
days
ago,
and
secondarily,
we
have
a
proposal
for
a
Chinese
translation
underway
that
is
currently
inviting
contributors
and
a
number
of
Security
reviews
on
the
way.
Through.
First
of
all,
we
have
pixie,
which
is
ebpf
flavored.
F
If
people
are
interested
to
jump
in
there,
we
are
looking
for
again
additional
security
reviewers
in
there
I
think
Justin
kappos
will
be
leading
that
one
for
us.
We
also
have
flat
car
flag.
Car
is
quite
a
large
surface
area,
let's
say
being
a
full
distribution.
It
is
more
than
we
would
generally
see
with
a
specific
Cloud
native
application.
F
I
I
should
add
that
we
have
been
traditionally
doing
a
Cadence
of
meetings.
Initially
every
week
on
the
US
time
zone,
we
then
stood
up
the
emit
the
Emir
meeting.
There
has
been
some
diffusion
of
of
contributors
across
those
two
time
zones.
So
the
goal
of
the
of
the
tag
is
now
to
maintain
that
Weekly
Cadence
in
North
America
on
the
North
American
time
zone,
while
also
maintaining
the
two
weekly
Cadence
of
the
Emir
team,
which
has
probably
half
two
were
to
a
third
of
the
number
of
contributors.
F
C
No
I
just
wanted
to
you
know
the
security
reviews
for
the
project
because
Pixies
you
know,
has
already
presented
in
the
tag.
Observability
and
we've
been
working
with
closely
with
the
team,
for
you
know
getting
them
lined
up
and
ready
for
review
by
the
TOC
for
incubation
status.
So
thank
you,
Andy
for
and
to
the
Thai
Community
security
community.
A
Ricardo's
got
a
second
on
that,
thanks
for
picking
up
flat
car
Andy,
while
we
have
you
a
quick
question
as
I
understand
it,
you
all
are
always
in
need
of
security
reviewers
to
support
and
assist
this,
because
it
is
a
volunteer
driven
activity.
I
assume
that
is
still
the
case,
and
if
so,
is
there
any
Security
review
or
resources
for
individuals
that
may
not
have
a
security
background,
but
are
interested
in
learning
more
and
how
they
can
assist
tag
Security
in
reviewing
these
projects,
security,
posture.
F
A
F
Yes,
I
appreciate
the
nudge
there's
one
more
thing
in
this
space
which
we
have
considered,
we
tend
to
experience
individuals
being
involved
in
contributing
in
their
line
of
business
interest.
Let's
say,
and
we
have
wondered
if
we
can
open
that
up
more
broadly
and
ask
people
if
they
can
contribute
maybe
to
the
proceeding
or
the
following
review
Once.
They
have
a
feel
for
the
way
that
we
pursued
the
the
minutiae
of
how
we
undertake
the
thing.
So
it's
an
open
discussion,
the
tag
security
right
now.
C
In
fact,
Emily
thank
you
for
calling
that
out,
because
I
just
wanted
to
call
out
that
the
secure
the
open
Telemetry
project
which
I
actively
work
on
is
we
just
created
a
security
web
group
which
is
you
know,
related
to
open
Telemetry
and
looking
at
security
use
cases
for
observability
and
again
Andy
I.
Think
perhaps
you
know
those
two
team
groups
can
collaborate
to
support
the
tech
security,
so
I'll
I'll
get
the
word
out
for
sure.
G
G
G
G
So
karmada
is
has
already
presented
in
the
tag
runtime
and
they
are
waiting
for
a
sponsor
from
the
TLC
and
we
had
two
sandbox
projects
that
have
been
accepted,
which
is
Kepler
and
the
cube
service
stack
eraser
as
well.
We
are
working
to
make
sure
they
you
know,
like
they
already
covered
all
the
information
that
the
TOC
asked
asked
them
to
provide
and
yeah
we
have
in
the
next
meeting.
We
have
the
cube
Clipper
project,
which
is
a
management
system,
kubernetes
management
system.
G
We
wanted
to
you,
know
like
discuss
here,
or
you
know
like
letting
you
know
that
the
session
in
Keep,
Calm
EU
was
very
productive
and
that
co-chairs
have
a
lot
of
successful
one-on-one
talking
and
people
were
so
interested
on.
You
know,
meeting
them
and
talking
it
to
them
during
the
session.
So
the
tag
is
planning
to
have
another
one
for
cube,
cubecon
Le
and
hopefully
we
can
have
more
elaborate
elaborating
sessions
as
well.
G
Hopefully,
the
charter,
the
drafted
Charter,
is
almost
ready,
so
we
will
send
it
for
Toc
review,
hopefully
this
week
and
we
already
nominated
the
co-chairs
and
team
leaders
based
on
people
interested
and
of
course
we
took
lots
of
other
other
other
factors
into
our
considerations
and
we
had
a
meeting
already
like
time
and
dates,
and
hopefully
once
we
have
the
DLC
review
and
everything
is
good.
We
can
start
to
kick
off
the
first
meeting
or
was
a
working
group
and
yeah
it
was.
G
It
was
so
you
know
like
so
happy
to
to
see
like
the
one
is
the
thing
now
and
it
will
happen
soon,
so
it
it
sync
up
with
the
working
group.
Hopefully
we
can
do
more
more
work
together.
Moving
back
again
to
the
patch
system
initiative,
the
team
had
the
pretty
consistent
chunk
of
work
and
they
are
making
a
good
progress
to
to
reach
to
the
landscape
phase
which,
which
is
pretty
excited,
and
for
the
other
working
group,
The,
iot
and
God.
G
A
C
Right
hi,
everyone
I,
wanted
to
kind
of
run
through
some
of
the
really
cool
stuff
that
we've
been
doing
in
the
tag
observability
and
and
the
first
and
and
foremost
I.
Think
thank
you
to
Toc
for
approving
our
request
for
work
group
on
the
query
language
standard
work
that
you
know.
Different
groups
are
interested
in
Netflix
eBay
as
well
as
Apple.
C
We
have
been
looking
at
some
of
the
use
cases
where
convergence
of
multiple
query
languages
in
the
industry
for
observability
are
leading
to
more
discussion
around
how
there
could
be
a
baseline,
which
is
a
standard
set
of
again
just
standard
set
of
syntax
right.
So,
based
on
that,
the
querying
query
language,
where
group
has
been
set
up,
we
will
reuse
the
cncf
tag
observability
time
on
the
day
on
the
weeks
when
the
tag
meeting
is
not
held.
C
So
the
tag
meeting
typically
is
on
the
first
and
third
Tuesdays
and
the
work
group
worker
language
discussions
will
be
held
on
the
second
and
fourth,
we
have
already
had
the
first
discussion.
A
lot
of
folks
attended
a
very
good
representation,
both
from
end
users,
as
well
as
from
a
different
vendor
teams
that
have
been
involved.
C
And
that's
very
exciting,
because
again,
this
is
an
and
I
stated
the
work
group
goals
on
the
right
hand,
side
as
well
as
the
non-goals.
Obviously
we
are
not
looking
at
defining
a
form
of
standard
or
implementations.
That's
up
to
the
if
new
projects
spin
up
based
on
that
that's
up
to
the
projects
to
do
what
we
want
to
focus
in
on
in
this
web
group
is
really
looking
at
a
variety
of
use
cases
capturing.
C
You
know
what
some
of
the
end
user
pain
points
are
and
the
use
cases
which
really
require
complex
queries,
often
for
observability
data
and
just
looking
at
Telemetry
models
and
establishing
and
documenting
that.
We
also
plan
to
interview,
query
language
designers
from
different
groups
within
the
cncf
ecosystem,
as
well
as
problem
different
vendors
and
this
and
also
survey.
You
know
multiple
end
user
groups
who
have
been
super
interested
in
first
of
all
providing
feedback
and
also
hope
to
inform
the
diversity
of
observability
use
cases
that
exist.
D
C
C
I
H
To
talk
about
an
MIT,
open
source
project
called
klein.io,
it
is
a
streaming
graph
interpreter.
I've
mentioned
this
in
the
past,
and
we
finally
got
him
to
come.
I
highly
recommend
giving
the
talk
a
lot,
giving
the
talk,
a
watch,
it's
about
35,
minutes
or-
and
it
starts
with
the
theory
of
observability
that
goes
back
quite
a
bit
deeper
than
an
older
than
you
might
think:
Beyond
a
predating
kind
of
control,
theory
and
and
with
its
roots
in
philosophy.
H
Rather
it's
a
stateful,
durable
graph
database
backing
that
sort
of
buffer.
If
you
will
so
string
and
graph
interpreters
have
a
lot
of
applications,
I
think
in
observability,
in
particular,
Cloud
native
observability,
due
to
the
high
cardinality
and
the
nature
of
a
kubernetes
observability.
So
the
talk
ends
with
a
demo
of
using
wine
to
understand,
what's
happening
in
a
cluster.
So
that's
that.
C
C
You
know
what
is
the
best
process
for
reaching
out
to
the
cncf
legal
team,
as
well
as
the
TOC
for
reviews
of
different
licensing
requests
or
Community
requests
that
come
up
right
and
and
we
did
file
a
service
desk
ticket
from
open
Telemetry
a
while
back
and
it's
been
a
few
months.
We
have
not
heard
back
on
the
ticket
from
the
legal
team,
so
maybe
Amy
you
can
guide
us
in
terms
of
what
the
process
is
there.
C
A
J
Hello,
so
we
organized
actually
a
while
back
I
think,
a
month
ago,
a
getting
started
meeting,
which
was
quite
nice.
We
had
a
couple
of
new
folks,
I
think
around
10
around
10
new
faces,
and
we
will
work
on
those
slides
over
time
and
then
have
again
getting
started
meetings
after
each
major
conference.
So
every
time
we
expect
a
lot
of
new
contributors
or
new
folks,
interesting
in
the
tech.
We
will
organize
a
getting
started
meeting.
J
We
published
a
blog
post
I
think
two
weeks
ago.
It
should
be
published
today
also
on
the
cncf
blog.
So
we
have
it
on
our
website
already
and
it
should
also
be
published
today
or
tomorrow
or
tomorrow.
It's
about
kubecon
and
Cloud
native
at
kubecon.
Basically,
and
we
had
a
couple
of
sections
in
the
blog
post,
where
we
had
interview
style
questions
and
folks
from
the
tag
answer
those
questions
so
I
think
this
was
a
very
nice
idea
or
or
a
thing
to
get
folks
from
the
tag
involved
in
a
blog
post.
J
J
It
is
just
like
a
resource
which
you
can
deploy
anywhere,
but
it's
governed
under
different
organizations
or
a
different
foundation.
So
this
was
a
very
good
demo
for
us
to
know
a
little
bit
more
about
the
tool
itself,
but
also
to
get
a
connection
to
to
the
author
and
also
to
to
the
other
Foundation.
Potentially
we
published
a
couple
of
months
ago
and
we've
talked
about
it
and
the
cloud
native
sustainability
landscape
document,
and
it
has
been
translated
to
Korean,
which
is
very
nice.
J
J
There
was
also-
and
we
have
been
talking
in
the
tag
about
this
for
quite
some
time,
because
at
the
moment
a
lot
of
our
efforts
are
focused
around
communication
and
and
so
on.
So
we've
been
starting
and
creating
an
issue
about
the
working
group.
Around
communication,
which
I
think
is,
is
a
very
good
step.
J
J
J
There's
also
another
effort
about
organizing
a
cloud
native
week
of
cloud
native
sustainability,
and
the
idea
is
that
we
use
the
community
groups,
so
we
have
in
the
scenes.
You
have
all
those
chapters
they
organize
meetups
and
we
have
this
this
network
and
the
idea
is
that
we
leverage
this
network
and
that
we
organize
in
in
a
particular
week
the
second
week
of
October
all
around
the
globe,
Cloud
native
meetups,
around
the
topic
of
sustainability,
and
we
already
have
over
20
meetups,
interested
or
organizers
interested.
J
J
J
J
Also,
we
have
been
working
on
refining
governance
and
guidelines.
We
pushed
a
new
process
around
reviewing
blog
posts.
This
has
been
a
problem
a
couple
of
months
ago
when
we
first
had
a
blog
post,
a
submission,
and
we
we
notice
that
we
are
missing
guidelines
so
to
review
it,
and
it
was
a
little
bit
messy
and
now
I
think
we
have
a
very
interesting
process,
maybe
something
we
can
also
document
in
the
best
practices.
Effort.
There's
like
another
issue,
open.
E
J
The
TOC,
so
maybe
this
could
be
interesting
that
you
and
the
last
two
things
we
have
been
also
talking
about
tech
roles
and
like
a
leadership
ladder,
because
some
tag
members
are
interested
in
in
moving
moving
up
roles
and
have
different
leadership
roles
and
we've
been
also
talking
about
the
host
Playbook.
So
how
to
organize
the
meeting
and
so
on.
A
Awesome
thanks
so
much
Leo
for
those
of
you
that
are
interested
in
learning
more
about
that
hackathon
definitely
check
out
the
issue
link.
There
is
a
lot
of
great
information
and
discussion
on
there.
I
think
the
folks
in
tag
observability
might
be
interested
in
checking
that
out
so
Leo.
Thank
you
so
much
any
questions
for
tag.
Environmental
sustainability
before
we
move
on
okay.
Next.
K
Hello,
everyone
We've
made
really
good
progress.
Dave
sudia,
in
particular,
has
made
really
good
progress
on
revitalizing
the
maintainer
circle,
so
this
has
been
exciting
to
see
so
we
held
one
with
with
Nate
and
Lee
just
a
little
over
a
week
ago,
and
we
have
one
coming
up
on
Community
Management,
with
Paris
Pittman
on
the
28th,
so
we'll
be
announcing
that
one
soon,
if
you
want
to
hold
it
on
your
calendar,
that
would
be
great.
K
C
K
You
so
it's
it's
a
university
for
for
the
deaf
and
hard
of
hearing
and
so
she's
working
with
them
and
meeting
with
a
professor
to
to
look
at
how
we
can
make
our
communities
more
accessible
to
contributors
in
the
space.
So,
if
you
know
any
community
members
who
are
deaf
hard
of
hearing
or
fluent
in
American
Sign
Language
and
who
are
maybe
interested
in
collaborating
with
us
on
this
effort,
have
them
reach
out
to
us
at
a
contributor
strategy.
K
We'd
love,
love
to
hear
them
and
their
experiences
and
get
more
people
involved
in
this.
This
new
initiative
we're
also
making
really
good
progress
in
that
the
work
that
Jay
talima
is
doing
with
the
Maori
in
New
Zealand
and
some
some
work
with
government
initiatives
to
to
help
them
move
into
careers
and
the
cloud
native
space.
K
So
it's
part
of
kind
of
a
national
National
program
to
get
more
more
native
Maori
people
into
I.T
careers
and
in
particular,
in
our
case
the
cncf.
So
that
also
is
really
really
exciting.
To
see
on
the
governance
side,
we've
got
some
governance,
reviews
and
progress,
so
we're
doing
governance,
reviews
for
istio
and
telepresence
right
now.
K
So
so,
like
the
last
group,
we
updated
our
slides
a
little
late.
So
if
you
go
back
to
the
slides
later,
you
can
see
that
we've
added
a
few
things
to
the
general
section.
In
particular,
we
have
new
tech
leads,
so
we
have
Ali
okay
and
Rianne
kleinhouse
kleinhans,
who
are
stepping
in
to
fill
Carolyn's
very
big
shoes.
K
Contributor
strategy,
road
map,
so
that
we
have
a
better
feel
for
what
we're
what
we're
working
on
what's
coming
next
and
how
people
can
get
involved.
So
there's
also
a
lot
of
great
work
happening
there
and
then
our
friendly
monthly
reminder
that
any
cncf
project
is
welcome
to
come
and
talk
to
us.
If
you
want
some
help
with
governance
or
building
your
contributor
strategy
growing,
your
contributors
so
feel
free
to
drop
into
any
of
our
meetings.
Slack
channels,
mailing
lists.
You
know
if
your
projects
need
some
help,
any
questions
for
the
tag.
C
Don
I
think
I
had
a
question
about
getting
the
tag
contributor
strategy.
You
know
team
more
involved
in
the
projects,
the
opposite
way
that
is,
can
we
invite
you,
for
example,
open
to
Elementary?
And
you
know
it's
a
very
large
project,
communites,
you
or
you
know,
folks
from
the
tech
contributor
strategy
to
come
and
speak
to
the
to
the
GC
and
the
DC,
for
example.
Right
because
we
have
a
regular
meetings,
but
typically
what
I've
noticed
is
that
most
projects
don't
go
to
the
contributor
strategy.
It's
kind
of
isolated
and
separated
out.
C
A
K
We'd
certainly
be
open
to
that.
I
would
say
reach
out
to
us
on
on
our
slack
Channel
or
the
the
mailing
list
with
when
the
meetings
are,
and
maybe
some
some
idea
of
some
of
the
challenges
you're
facing
that
you'd
like
for
us
to
talk
about
and
then
we'll
we'll
see.
If
we
can
find
somebody
who
can
who
can
come
into
to
your
meetings
as
well.
K
And
you
know,
projects
that
are
having
particular
issues
or
want
to
review
on
something
or
maybe
they're,
updating
their
governance
and
want.
Some
advice
are
also
always
welcome
to
just
file
issues
and
tag
contributor
strategy,
and
we
can
deal
with
those
asynchronously.
So
you
don't.
You
don't
have
to
pop
into
a
meeting
if
you've.
If
you've
got
a
question
we
can,
we
can
deal
with
some
of
those
via
VIA
issues
as
well.
C
Okay,
that
that
makes
sense
still
I
mean
again
all
all
good.
It's
just
more
that
you
know
they
are
often
a
lot
of
discussions
that
the
community
repos,
for
example,
on
hotel,
are
very
active
lots
of
different
discussions
happening
there,
but
they
don't.
You
know,
really
they
stay
centered
in
the
in
on
the
project
itself,
right
and
and
books.
Typically,
don't
intersect,
so
I'd
love
to
see
more
collaboration.
There.
A
Okay,
I,
have
a
recommendation
for
everyone
if
you're
a
tag
chair
or
technical
lead
or
a
maintainer
of
a
project
or
interested
in
becoming
a
maintainer
for
a
project
at
some
point
in
the
future,
highly
recommend
going
to
that
Community
Management
session
with
Paris
Pittman
keep
an
eye
out
from
TAG
contributor
strategy
for
information
and
details
on
that,
even
though
it
may
not
be
immediately
relevant
to
something
you're
working
on.
There
are
always
good
sessions
to
understand
what
is
going
on
in
the
movie
and
the
rest
of
the
community.
K
I
D
I
I
I
Yeah
we're
pursuing
a
couple
things
I
think
they
want.
One
of
the
things
they
asked
was
about
patterns
for
integrating
events
and
reacting
to
them
and
I
kind
of
said:
hey
are
serverless
working
group
which
I
always
have
my
eye
on
most
about
Cloud
events.
Ask
them
to
talk
with
them.
Some
too
continuing
through
the
list
are
ouija's.
So
Ouija
is
just
what
I
call
working
groups
artifacts.
So
we've
had
some
productive
couple
meetings.
I
After
our
you
know,
initial
back
and
forth
asynchronously
the
charter
is,
is
ready
for
review.
I
opened
them
the
so
delete.
Well,
one
of
the
leaders
opened
up
PR
in
the
tag
repo
and
I
opened.
The
thing
in
the
talks
today
so
take
a
look
at
that
see
what
you
think,
which
there's
a
lot
of
different
examples
of
forming
Ouija
so,
and
there
were
a
lot
of
opinions
in
the
meetings
too
so
and
I'm
sure
there
will
be
more
on
the
pr
so
comment
there.
B
I
It's
you
know,
the
work
we're
doing
is
bottoms
up
effort,
it's
not
to
set
a
spec,
it's
more
to
gather
just
the
fact
is
that
people
don't
have
the
motivation
to
register
all
these
media
types
with
Iana,
so
we're
trying
to
bottoms
up
gather
them
together,
find
conventions
and
eventually
it
might
affect
it-
might
affect
oci,
artifacts,
2o
or
oci
image
spec.
Even
to
oh
there's,
some
discussions,
Within
oci.
I
I
The
maturity
model,
some
of
our
folks
are,
are
in
depth
on
that,
and
we
want
to
push
it
Forward,
maybe
have
it
ready
by
Chicago,
Korean
translation,
I
think
the
same
person
that
did
the
environmental
sustainability
to
ours,
but
we
haven't
quite
figured
out
how
to
get
it
merged
in
there.
Yet,
if
somebody
wants
to
it's
really
almost
done
it,
just
it's
the
Hugo
figuring
out
how
to
negotiate
that
the
platform
survey
is
live.
We
haven't
gotten
a
ton
of
responses
and,
to
be
honest,
we
haven't
really
promoted
it.
I
Yeah
I
mean
it's
just.
We
need
some
help
if
folks
want
to
help
promote,
it's
been
on
my
backlog
to
write
a
blog
post
about
it
and
explain
what
we're
doing,
but
I
haven't
done
that
yet
newsletter
and
marketing
same
thing.
Actually,
this
is
really
good.
I
just
talked
with
some
of
the
folks
that
are
interested
in
this,
and
we
do
have
a
few
people
that
want
to
in
a
vendor
neutral
way
share.
You
know,
information
about
application,
development
and
delivery
on
kubernetes
and
so
they're
pursuing
ways
to
share.
I
You
know
the
stuff
that
comes
to
our
tag
and
some
of
the
projects
that
we're
working
on
working
on,
like
Potato
Head
I,
did
want
to
share
this
last
bit,
which
is
within
from
the
platforms
Group,
which
is,
you
know,
probably
accomplished
a
lot
of
the
core
of
what
it
wanted
to
do.
But
we
want
to
continue
somehow
pursuing
Synergy
standards,
conventions,
reduction
of
complexity
for
platform
apis.
I
You
know
the
ways
that
you
actually
call
the
platform
for
portals,
where
there
is
some
confusion
in
the
industry
about
what
portals
are
meant
to
do
things
like
backstage
and
secrets
buying
these
management,
which
comes
up
freaking
every
conversation
I
have,
but
it's
you
know,
there's
not
that
much
money
in
it.
Frankly,
I
think
in
solving
the
problem,
it's
hard
to
get
everyone
together
on
there's
about
20
different
ways.
So
that's
definitely
been
an
hour.
I
I
I
I
have
noticed
that
the
pre-day
events
are
proliferating.
They
seem
to
be
is
twice
as
many
in
Amsterdam
as
Detroit.
Maybe
there
were
much
more
before
the
pandemic.
I'm,
not
really
sure,
but
were
I
was
thinking
about
a
lot
of
those
are
app
delivery
projects,
and
so
I
was
thinking
about
trying
to
coordinate
that
a
bit
most
of
them
are
only
an
hour
or
something
anyway,
so
that
we
can
all
attend
each
other's
and
learn
from
each
other's.
I
J
F
C
I
Yeah,
and
in
fact
you
know,
I
was
kind
of
thinking
because
I
don't
know
if
you
all
have
heard,
but
there's
a
proposal
for
an
app
developer
day
on
that
day
and
I
was
thinking
about
how
that
fits
with
the
project
meetings.
Does
that
negate
the
need
for
them,
but
I've
actually
been
thinking
like
that
event
is
towards
end
users
to
the
you
know,
the
people
that
come
in
and
want
to
learn,
whereas
these
project
meetings
I
mean
certainly
if
end
users
want
to
come.
C
A
So,
knowing
that
that's
difficult
and
having
done
the
schedule
a
few
times
for
kubecon,
if
you
both,
could
take
a
few
moments
and
type
something
up
and
paste
it
in
either
the
TOC
Channel
or
the
tag
chairs
Channel,
concerning
like
scheduling
conflicts
associated
with
kubecon
and
we'll
make
sure
that
that
is
sent
over
to
the
events
team
and
the
co-chairs
for
kubecon.
So
that
they're
aware
and
mindful
of
it,
when
they're
building
out
the
schedule.