►
From YouTube: K8s SIG Docs Meeting for 20210511
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
All
right,
hello,
welcome
everybody
to
the
weekly
sig
docs
meeting.
I
am
jim
angel.
One
of
your
co-chairs
for
sick
ducks
today
is
tuesday
may
11th.
I
got
quite
a
full
crowd
today.
Anyone
joining
sick
ducks
for
the
first
time
that
care
to
introduce
themselves.
A
C
D
C
D
A
Yeah
for
those
that
weren't
around
last
week,
we
had
a
kind
of
no
meeting
meeting
around
cubecon
where
folks
could
kind
of
attend
and
socialize.
So
it's
not
always
the
best
one
to
to
join
as
a
newcomer
and
see
how
much
lack
of
work
is
getting
done
as
we
socialize
cool
anybody
else.
Where
do
we
get
everybody.
E
A
Awesome
welcome
welcome
all
right
so
moving
on
to
this
week's
updates
and
reminders,
this
week's
pr
wrangler
is
avita
and
next
week
is
irva
and
pr
approvers
make
sure
that
you
know
your
pr
angular
shifts,
there's
a
link
in
the
agenda
there.
If
you
are
unsure
and
moving
on
to
the
agenda,
release
122.
F
Sure
so,
last
week
we
had
the
onboarding
session.
With
the
with
the
shadows.
I
made
sure
that
everyone
has
access
to
kubernetes
organization.
Everything
has
pretty
much
been
okay.
So
far,
everyone
has
access
to
the
enhancement
sheets
as
well.
So
we
will
see
how
it
goes.
Enhancement
freezes
sometimes
sometime
this
week
on
thursday
13.
F
It
seems
now
like
now
there's
a
thread
asking
to
delay
this
by
a
week,
so
we'll
see
how
that
goes,
but
nevertheless
I
will
go
through.
I
will
go
through
on
on
thursday
night.
F
My
time
sort
of
I
will
go
through
it,
comb
it
and
start
assigning
enhancements,
so
we
can
track
them
to
everyone
in
the
team
and
if
they
push
it
by
a
week,
I
think
I'm
I'm
I'm
still
going
to
assign
it,
but
we'll
we'll
close,
we'll
we'll
keep
a
close
eye
on
on
how
the
the
situation
moves
forward,
because
we
don't
want
to
ping
enhancement
owners
until
enhancements
basically
finishes
with
with
asking
them
for
for
everything
to
be
in
order.
F
F
Give
or
take
a
few
because
I
didn't
again,
I
didn't
comb
the
entire
enhancements
tracking
sheet
to
see
some
of
them
were
removed
from
the
milestone
and
some
of
them
don't
just
don't
need
any
documentation
basically,
but
we're
around
69.
A
It
sounds
like
we're
on
track
tentative,
any
extensions
potentially
coming
up.
A
All
right
awesome,
so
moving
on
to
issues
in
pr's,
I
did
want
to
bring
up
something
that
came
up.
I
want
to
say,
is
about
two
weeks
ago,
with
kubecon
and
the
apec
friendly
meeting.
This
is
the
first
time
that
we've
all
met
together
and
I
can
bring
it
up
as
an
ongoing
discussion
around
markdown
line
lengths,
and
so
some
quick
history
here
on
the
way
hugo
renders
markdown
is.
It
doesn't
really
care
whether
it
is
a
single
line
or
multiple
separated
lines.
A
It's
going
to
mash
them
all
into
a
paragraph
without
having
some
form
of
markdown
separator.
So
what
I
mean
by
that
is,
if
I
have
two
sentences
that
are
on
two
touching
lines,
or
I
guess
one
single
line
break
between
them,
they'll
render,
in
the
same
paragraph
as
the
same
kind
of
two
sets
of
sentences.
If
there's
no
object
in
between
them,
it's
like
a
header
or
an
ampersand
or
a
hashtag.
A
If
you
will
for
the
header,
markdown
or
any
of
the
sort
of
symbols
in
between
that-
and
I
feel
like
I'm
not
doing
the
best
of
job
explaining
what
the
intention
is
here
and
so
when
you're
comparing
what
has
changed
in
two
files,
the
way
git
diff
works,
is
it
compares
line
by
line
differences?
A
So
the
long
and
short
here
is
if
there
were
to
be
multiple,
multiple
smaller
lines
then
get
different
stills
for
that
single
line
as
being
the
entire
piece
of
information
change.
But
now
it's
going
to
be
easier
to
pinpoint
versus
like
a
multiple
sentence,
paragraph
as
a
single
line
being
recognized
as
being
changed.
A
A
It
just
makes
the
life
of
localization
efforts
a
little
easier
if
they're
on
multiple
lines,
but
I
wanted
to
raise
awareness
here,
because
I
almost
feel
like
there's
not
an
outcome
where
you
can
say
blanket:
enforcement
of
line
length
up
to
180
characters
or
up
to
a
certain
character
extent,
and
I
think
that
this
is
going
to
be
a
very
wide
variety
of
implementations
that
folks
would
take
from
this
action
or
this.
This
comment
there's
a
very
long-winded
way
of
saying.
A
Multiple
lines
are
better
for
localization,
but
ultimately
don't
make
a
big
impact
to
the
overall
writing
experience
and
wanted
to
share
that
with
folks.
I
have
no
problem,
you
know
adopting
that
model
or
that
mindset,
but
I
don't
see
a
way
of
enforcing
that
and
I'm
curious
if
anyone
has
any
questions
or
concerns
around
that.
G
I
guess
like
I
can
totally
build
a
thing
that
will
warn
people
if
their
commits
and
putting
in
long
lines.
I
don't
know
if
I
would,
because
I
think,
reviewers
I'd
I'd
prefer
to
have
it
done
by
reviewers,
and
I
prefer
to
give
the
feedback
from
people,
but
we
could
build
it.
H
Is
the
ask
for
like
one
sentence
per
line,
or
is
it
to
do
like
a
cutoff
at
a
certain
character,
length.
A
I
think,
then,
I
don't
want
to
misinterpret
the
ask
here,
it's
more
about
just
having
more
lines
the
better,
not
really
requiring
it
to
be
per
character
or
per
sentence,
or
something
like
there's,
no
real
general
rule
of
thumb.
It
sounds
like
what
tim
was
referring
to
could
be
a
character
based
thing
saying
up
into
this
many
characters
or
sentences
or
words
chop
it
off.
The
tldr
is
when
everything
is
on
one
line
and
extremely
long.
It's
just
a
pain
to
localize
versus
when
it's
broken
into
many
lines.
B
Yeah,
especially,
it's
really
hard
when
you
have
to
compare
like
a
multiple
words
or
like
a
lot
of
like
rephrasing.
Are
there
in
one
sentence?
I
mean
one
line:
it'll
be
really
difficult
to
take
the
diff
yeah
that
that
is
a
really
big
concern
for
localization.
I
can
agree
it
on,
but
one
one
concern
about
putting
multiple
lines
in
like
even
in
within
one
long
sentence
for
me
is
that
actually
in
japanese,
we
do
not
put
any
blanks
just
like
english
or
like
typical
european
languages.
They
put
a
blank
on
each
word
right.
B
So
when
you,
when
you
insert
a
new
line
in
markdown,
that
means
you
will
put
the
blank
between
the
new
line
when
it's
rendered
as
html.
B
This
happens
a
lot
and
yeah
it's
kind
of
driving
me
crazy.
When
I
deal
with
it,
but
it
I
think
it's
only
for
languages
that
don't
have
any
blanks
like
chinese
or
japanese.
Even
korean
has
blanks
because
they
only
have
the
letters,
not
okay.
Let's
not
talk.
B
It's
for
yeah
yeah,
exactly
yeah,
because
it's
it's
more
of
the
localization
issue,
so
we
should
discuss
it
in
the
localization
meeting
a
localized
meeting
but
yeah.
So
so
I
I
would
ask
more
like
not
just
like
putting
multiple
lines,
but
I
was
like.
Can
you
put
this
long
sentence
into?
You
know
a
few
sentences
instead
right
because
it's
easier
for
translation,
anyways.
B
A
Yeah-
and
it
does
seem
like
this-
would
be
something
that
is
ripe
for
automation
down
the
road.
I
just
my
concern
is:
is
the
toil
worth
the
effort
and
I'm
100
worth
you
know,
I
think
if
we
could
automate
it
easily,
there'd
be
a
slam
dunk,
but
I
think
there
are
some
of
the
nuances
and
complexities
of
the
different
translations
and
that
my
gut
says
the
best
way
to
move
forward
with.
A
This
is
best
effort
as
reviewers
as
approvers,
seeing
prs
that
maybe
have
lengthy
you
know
single
line
sentences,
multiple
sentences
on
the
same
line
might
be
worth
bringing
up
and
saying
hey
for
you
know,
localization
efforts,
let's,
let's
try
to
chop
this
down.
A
If
anybody
tim
abbey
are
interested
in
looking
at
automating
this
I'm
100
supportive
in
all
four
like
we
could
even
roll
it
into
some
quarterly
planning
if
we
wanted
for
tracking,
so
not
against
automation
or
any
of
that
stuff,
but
I
think
at
the
very
least
we
can
act
today
with
best
effort
as
reviewers
and
approvers
yeah.
I
would
say
the
same.
I
agree
with
you
cool
any
other
questions
or
comments
on
that
before
moving
on.
A
All
right,
so
just
a
quick
one
here
this
has
been
a
long
time
coming.
I
put
the
pull
request
in
the
agenda
and
I
can
send
it
in
chat
here
just
raising
awareness
of
a
of
a
release
page
that
hold
on
one.
Second,
I
can't
walk
and
talk
here
all
right.
Let's
do
it
in
chat,
so
this
is
a
release
page.
What
really
has
been
the
blocker
is
not
really
the
fact
of
that
we
couldn't
create
a
release
page.
A
It
was
more
about
there's
a
heavy
vested
interest
in
sig
release,
as
well
as
sig
docs,
working
together
on
a
release
page
and
there's
about
a
thousand
different
sources
of
data,
whether
that's
generated
from
sig
release,
it
could
be
generated
from
the
github
api.
There's
things
you
can
do
in
hugo
to
pull
the
release
down.
A
So
the
long
story
short
here
is
there's
two
very
overarching
sigs
that
that
want
to
have
ownership
over
this
releases,
page
sig
docs
from
the
implementation
standpoint
and
the
visualization
standpoint,
sig
release
from
the
data
standpoint,
so
why
this
has
taken
so
long
to
open
up
the
pr
was
to
figure
out
a
way
to
share
the
data
with
sig
sig
release,
as
well
as
present
in
a
way
usable
from
the
rest
of
the
community
and
the
ultimate
goal
here.
A
A
You
see,
there's
kubernetes
or
kate's
dot,
dev,
there's
case
dot,
io,
there's
download,
kubernetes,
there's
releasenotes.com,
there's
a
ton
of
release,
information
and
subsites
out
there,
and
what
we're
trying
to
do
is
pull
the
information
back
into
the
centralized
website,
where
possible
and
and
link
out
where
we
can
so
that's
a
very
long-winded
way
of
describing
what
we're
trying
to
do,
but
really
why
I'm
going
through
so
much
history
on
this
is
to
say
this
is
where
we
got
today.
A
This
isn't
the
perfect
releases
page,
but
it's
kind
of
an
mvp
or
a
phase,
one
of
a
releases
page
that
I
think
will
put
the
foundation
in
place
for
sig
release
and
sig
docs
to
work
together
on
kind
of
presenting
the
data
in
a
unified
front.
So
I'll
pause
there.
Any
questions-
and
I
appreciate
tim
thanks
for
putting
the
preview
in
there,
but
any
questions
or
comments
on
the
general
release,
information
or
the
pr.
A
Cool
hearing
a
whole
lot
of
nothing.
I
just
wanted
to
raise
awareness
that,
hopefully
that
gets
in
hopefully
gets
in
as
an
mvp.
There
might
be
some
more
movement
around
there
and
then
also
victor
when
you
have
a
second,
if
you
don't
mind,
taking
a
look,
because
that
will
potentially
impact
the
release
team
as
well
there's
a
I.
G
Want
to
say
a
couple
of
things.
First
of
all
like
thank
you
jim.
You
know
I
made
a
start
on
this
and
this
your
work
is
clearly
moving
this
a
lot
further
forward
than
the
start,
and
the
second
one
is
that
this
kind
of
pr
feels
to
me
like
a
good
way
for
someone
interested
to
get
involved,
because
it's
git.
So
if
you
know
enough
git
to
take
a
branch
and
copy
that
branch
to
your
fork
and
and
fork
it
a
bit
more,
you
can
iterate
on
that.
G
You
can
make
suggestions,
you
can
make
small
ones.
You
can
make
big
suggestions,
and
I
would
you
know
anyone
who's
feeling
the
itch
to
to
get
get
involved.
This
is
a
great
kind
of
area
where
we'd
love
to
have
a
bit
of
a
bit
more
help.
It
could
be
polishing
some
html.
It
could
be
working
with
hugo
templates.
A
Cool
yeah
yeah,
strong,
strong,
plus
one
there
and,
like
I
said
I
really
want
to
emphasize
that,
since
this
has
gone
around
for
about
a
year
now
really
hasn't
been
prioritized
work,
I'm
really
hot
to
to
get
this
merged,
as
is
and
then
iterating
on
top
and
getting
some
of
those
fixes
in
so,
as
tim
said,
it's
right
for
contributors
to
make.
You
know
valuable
contributions
to
the
overall
release,
documentation
and
improving
that
information.
A
You
know
where
this
fundament
fundamentally
came
from
was
me
selfishly
not
having
a
quick
spot
to
check
upcoming
releases
and
the
current
releases
were
now
supporting
open
source
kubernetes.
It
was
always
buried
in
github
somewhere
or
on
a
release
team
somewhere
and
really
bringing
that
information
up
to
the
forefront
is
one
of
the
top
priorities
of
this.
G
Maybe
shannon
actually
welcome
shannon
you've
been
leading
a
lot
of
the
pull
requests
on
that.
Are
you
happy
to
talk
about
this.
G
I
Don't
have
a
lot
of
knowledge
about
the
actual
concepts
of
eviction
and
scheduling
outside
of
what
I've
read
here.
But
from
what
I
understand,
the
discussion
is
mainly
about.
I
We
have
a
new
page
for
eviction
as
a
concept
which
includes
well
what
was
it
yeah
manual
eviction
using
the
eviction
api,
as
well
as
the
cubelet
eviction,
and
we
were
also
including
stuff
about
preemption
there
and
classifying
it
as
a
form
of
out
of
resource
eviction,
but
then
there's
been
feedback
that
it's
not
really
a
form
of
eviction
as
much
as
it
is
a
way
for
the
scheduler
to
kind
of
make
space
on
nodes
to
schedule
high
priority
pods.
I
J
So
shannon
this
is
brad
on
my
team
is
way
who
who's
co-chair
of
scheduling
of
this
scheduling,
sig
and
a
scheduling
maintainer.
So
let
me
connect
you
with
him.
So
if
you
have
questions
on
eviction,
he's
he's
an
expert,
I'm
a
scheduler
manager
too.
Okay.
Well,
I
know
otherwise.
E
Yeah
I've.
I
also
invited
way
into
some
of
the
issues
he's
not
involved
in
this
one
in
particular,
but
yeah
we
can
ping
him.
J
G
J
E
Add
some
thoughts,
the
the
basic
question
is
whether
preemption
should
be
considered
part
a
form
of
eviction
and
not.
Of
course,
this
is
not
a
cubelet
eviction
and
we
are
kind
of
expanding
the
concept
of
eviction
to
simply
mean
that
pots
get
removed
by
the
by
the
control
plane.
E
Now
this
happens
by
two
controllers,
one
of
them
it's
the
cubelet,
which
would
be
the
no
eviction
and
then
the
other
one
is
the
cluster
eviction
which
is
done
by
the
scheduler.
E
So
today
the
two
concepts
are
separated
and-
and
that's
fine,
but
I
think
the
the
intention
of
the
refactoring
is
precisely
to
put
them
in
one
place.
So
when
people
think
of
pots
being
removed
by
the
cluster
by
the
control
plane,
they
can
refer
to
a
single
page
and
then
then
from
there
they
can
figure
out
which,
which
type
of
eviction
happen.
G
Sure
so
I'm
I'm
going
to
respond
to
the
the
con.
The
question
about
you
know
is:
is
eviction,
so
is
preemption
a
kind
of
eviction
and
we
could
change
that,
but
we
are
21
minor
releases
into
kubernetes.
There
is
a
whole
load
of
history
and
my
gut
feeling
is
that
persuading
the
rest
of
the
kubernetes
community
to
treat
preemption
as
a
form
of
eviction
is,
is
gonna,
be
a
big
ask.
G
Now
I
actually
got
these
mixed
up
like
I
got
eviction
and
preemption
mixed
up
a
while
ago,
when
I
was
doing
some
structuring-
and
I
think,
if
I'd
thought
about
this
more,
I
would
have
changed
the
concept
to
be
the
one
that
actually
we
most
changed
earlier.
So
now
the
concept
is
titled
scheduling,
eviction
and
preemption.
G
G
I'm
going
to
put
a
pin
in
a
comment
about
url
layout,
but
I
want
to
come
back
to
that.
So
my
idea
is
that
if
you
go
to
that
section
of
the
concepts
page
you're
going
to
be
looking
at
the
concept
documentation,
you
want
to
understand
these
kubernetes
concepts
that
maybe
you've
not
never
come
across
before.
G
Perhaps
you've
never
come
across
the
whole
idea
that
immutable
infrastructure
might
get
torn
down
when
some
other
component
doesn't
need
it
anymore.
That
might
be
new
to
you.
You
know
in
general,
not
just
in
kubernetes,
so
I
think
we
should
should
have
a
page
that
introduces
you
to
those
and
then
lets
you
drill
down,
and
I
strongly
feel
that
when
you
drill
down,
you
should
be
able
to
drill
down
into
preemption
as
a
thing
and
then
also
drill
down
into
the
two
types
of
eviction
as
a
thing
and
into
scheduling
is
a
thing.
E
G
I've
I'm
I
approved
that
earlier
you
gave
it
an
lgtm
I'll,
come
back
to
the
thing
about
the
url
urls.
Actually,
so,
if
you
go
and
look
at
the
scheduling
and
eviction
page
now,
it
has
changed,
it
mentions.
Preemption
preemption
is
grouped
in
there.
E
Okay,
sorry,
so,
okay!
No,
but
in
this
case
I'm
talking
about
the
specific
page,
that's
channeling.
E
Well,
can
we
help
you,
I
will
have
to
look
at
the
pull
request.
I
don't
have
it
open.
A
E
So
let
me
come
here,
google,
so
that's
fine.
We
have
merged
the.
We
have
created
a
section
which
is
called
scheduling,
preemption
and
eviction.
That
is
fine.
E
Now,
within
that
there
is
a
page
called
eviction
or
the
proposal
is
to
have
a
page
called
eviction
which
has
the
eviction
through
the
eviction
api,
which
is
user
initiated
and
the
node
initiated
and
the
q
the
one
that
the
cubelet
does
so
those
two
concepts
are
they
going
to?
Are
they
going
to
be
the
only
concepts
in
that
page?
G
Well
I'll
come
back
with
it
with,
and
this
isn't
a
this
isn't.
This
isn't
me
as
a
sort
of
technical
lead
saying
this
is
how
we're
gonna
do
it,
but
this
is
my
personal
view.
I
like
hyperlinking,
I
like
pages,
I
like
laying
out
documentation
where
you
tell
people
there's
another
page,
it's
just
next
door
and
you
know
hypertext
lets
you
use.
E
G
E
G
People
in
the
meeting
do
people
like
aldo's
idea
that
actually
there
should
be
two
pages
about
eviction,
possibly
with
hyperlinks
to
each
other.
D
I'm
just
so
I
missed
the
early
part.
However,
I
was
wondering
if
we
can
actually
see
examples
of
this,
or
is
this
purely
hypothetical.
E
A
Yes,
sorry,
I
got
booted
there.
I
got
some
bad
internet
issues
here,
but
I
did
want
to
time
box
discussion
a
little
bit.
I
am
failing
to
understand
the
fundamental
questions
really
information
architecture
and
where
is
the
most
appropriate
placement?
Is
that
a
fair
question.
A
Gotcha
yeah,
I'm
you
know
I
would
definitely
lean
in
favor
more
towards
the
folks
doing
the
work
and
having
the
proposal
here.
It
sounds
like
there's
arguments
for
for
really
both
placements,
but
I'm
wondering
does
this
make
sense
just
to
have
it
land
and
then
iterate
on
top
of
it
or
do
we
need
to
have
the
situation
made
before
the
pr
can
land.
E
So
that's
why
I
want
this
discussion
so
that
if
we
are
going,
if
we
are
marrying
scheduling
with
eviction,
at
least
preemption
should
be
included
in
that
concept.
Otherwise,
there
is
no
relationship
between
the
concepts.
From
my
perspective,.
E
Yes,
so
yes,
so
that
that
can
already
happen.
But
there
is
still
the
question
of
where,
where,
where
does
prevention
fit
in
that
pr.
A
A
F
Yes,
so
when
I
added
myself
in
in
the
shadows
for
for
this
release,
a
few
people
brought
this
up
like
how
is
this
managed?
Basically
so
as
part
of
the
handbook
when
the
release
is
done,
the
docs
lead
removes
removes
people
like
the
the
shadows
and
himself,
and
the
idea
is
that
currently
right
now,
I'm
I'm.
I
don't
really
want
to
the
at
least
for
the
group
for
website
milestone.
Maintainers,
it's
grown
quite
a
bit.
F
There
are
no
shadows
from
from
the
previous
release,
there's
no
one
there,
but
I'm
really
reluctant
on
on
going
ahead
and
cleaning
that
out.
Since
I'm,
I'm
not
really
even
part
of
sig
docs,
let's
say
so.
That's
that's
one
thing
that
I
wanted
to
bring
up.
Maybe
someone
wants
to
have
a
look
and
knows
better,
which
ones
are
the
the
active
contributors
and
there
are
a
lot
of
people
there,
like.
I
don't
even
remember
seeing
those
github
handles
anywhere
for
the
past
for
this
year,
at
least
and
for
sig
ducks
team.
F
The
way
that
that
it
is
currently
again
like
I've
either
raided
it
previously,
where
he
removed
the
shadows
and
for
this
one
I
will
do
it
so
I'll,
remove
myself
and
when
the
release
is
done
and
also
remove
the
shadows
from
from
the
team
itself,
but
I'm
a
bit
reluctant
on
going
and
cleaning
anything
else,
removing
anyone
anyone
else
from
there,
because
I
really
don't
know
who
still
actively
uses
first,
the
the
milestone
applier,
the
the
milestone
privilege,
let's
say
for
for
the
website
and
second,
who
really
does
you
know
active
contributions.
A
Okay
and
I'm
happy
to
to
give
a
second
higher
second
review
on
those
poll
requests
you
open
up
or
if
you
want
to
message
on
slack,
we
could
even
work
it
out
on
one
of
the
slack
channels
independently.
But
if
I
recall
correctly,
I
think
it
was
probably
two
or
three
releases
ago.
I
think
savitha
started
bringing
in
the
sig
doc
shadows
into
the
website,
milestone
maintainers
group
with
the
idea
that
shadows
could
then
apply
that
slash
milestone.
What
have
you
for
the
various
pull
requests
that
get
open?
A
I
don't
know
if
that's
widely
adopted
or
if
it
continues
to
be
the
case,
but
I
think
that
might
explain
why
that
list
is
quite
large
with
some
folks
that
maybe
haven't
stuck
around
as
long
as
you
might
might
initially
intend
to
so
happy
to
help
you
out
there,
but
that's
a
little
bit
of
history
on
there,
and
I
hope
that
does
that
clear
up
at
least
your
question
or
concern.
F
So
for
for
the
milestone,
there's
currently
intestine
for
our
pro,
basically,
what
it
does
is.
It
goes
to
okay
website
and
there's
a
configuration
that
for
all
the
the
pull
requests
that
are
open
against
dev122.
It
has
a
milestone
applier,
so
it
will
automatically
apply
that.
However,
some
some
contributors,
sometimes
when
they
they
open
some
enhancement
owners
when
when
they
open
a
pr,
they
might
target
the
master
branch
by
mistake
instead
of
dev
122
and
the
bots
will
not
do
that
retroactively.
F
So
if
you,
if
you
do
that,
but
then
change
the
milestone
does
not
get
applied
and
it
still
needs
to
be
done,
and
I
think
that's
one
of
the
reasons
why
we
really
have
that.
Otherwise,
I
don't
maybe
remove
it
from
the
milestone,
but
we
don't
really
do
that.
I
think
enhancement
does
that
when,
when
they
decide
whether
an
enhancement
is
tracked
or
not,
so
we
don't
currently
remove
any
yeah
any
pr's
from
from
there.
So
that's
kind
of
why,
where
we're
there?
F
After
all,
I
think
my
discussion
was
with
when
it
was
between
number
nabarun
and
and
ray,
and
I
think
part
of
the
handbook
was
to
add
shadows
to
the
to
the
milestone
maintainers.
But
then
it
didn't
make
any
sense
because
then
you
could
put
it
throughout
okay
website.
So.
A
Gotcha,
I
appreciate
the
context
in
that
case
it
sounds
like
really
only
the
docs
release
lead
needs
that
maintainer
milestone
maintainer
permission,
then
to
cover
up
any
of
the
misapplied
branches,
yeah
cool,
and
then
this
next
thing
about
reviewing
config.time
on
dev122.
Is
there
anything
special
about
that?
Otherwise
I
can
definitely
review
it
offline
and
we
can
move.
F
A
Yeah
definitely
get
approvers
to
check
that
out
and
sorry
to
be
kind
of
rushed
in
here
I
want
to
make
sure
we
can
get
so
we
have
a
pretty
large
agenda
and
we're
running
out
of
time.
So
my
apologies
to
speed
along
here,
but
moving
on
to
the
analytics
dashboard
abby.
Do
you
want
to
catch
us
up
on
that?
I
know.
I
owe
you
some
feedback,
but
I
figured
you
have
more
context
than
I
do.
H
H
We
collect
about
io
to
explore
that
so
anyone
in
the
community
can
go
get
this
information,
but
we
kind
of
I'm
kind
of
at
a
blocking
point
of
where
I
don't
know
the
best
place
to
host
the
dashboard
either
through
a
google
account
and
then
also
the
best
way
to
host
it
to
get
it
on
the
kubernetes
website.
So
it's
you
can
embed
the
dashboard
from
from
data
studio
into
like
an
iframe
on
the
web
page,
I'm
not
sure.
H
If
there's
that's
the
best
way
to
do
it,
so
I
guess
any
feedback
of
it's.
A
google
data
studio
is
what
we're
using
to
host
this
report
and
I'm
not
sure
if
there's
a
way
to
get
that
report
exposed
like
in
a
way
to
make
it
like
its
own
url
or
if
the
best
way,
if
people
will
be
fine
with
it,
just
as
an
iframe
on
its
own
page
on
the
kubernetes.io
website.
So
that's
sort
of
where
I'm
at
I
don't
know.
H
H
Yeah,
so
the
goal
is
to
have
it
be
something
anyone
in
the
community
can
go
find
so
that
anyone
who
needed
analytics
for
either
localizations
they
wanted
to
know
the
top
pages
being
used
to
prioritize
pages
to
localize
for
their
own
projects
or
just
generally
curious
about
how
many
users
are
active.
Or
what
pages
are
the
top
pages?
There
was
a
lot
of
increase
in
asks
to
get
access
to
the
google
analytics
right
right
now,
so
we
were
wanting
to
make
a
way
to
make
it
more
self-service,
so
be
open
to.
B
B
Yeah,
actually
one
of
them
is
me
so
so
I
I
suppose
this
is
not
for
a
kubernetes
user
more
for
someone
who's
who
wants
to
get
involved
with
the
community
and
who
wants
to
contribute
or
who
wants
to
observe
the
status.
That
of
the
you
know
kubernetes
activity
in
general,
so
in
the
term
of
it,
I
don't
think
you
don't
you
have
to
host
it
on
the
website
itself.
You
know,
as
embedded,
you
can
just
provide
an
external
link
that
that
is
my
current
opinion.
H
A
Cool
yeah
and
it
sounds
like
we
can
definitely
figure
out
whether
it's
a
hyperlink
or
whether
it's
a
full.
You
know
iframe
embedded
web
page.
It
sounds
like
we
can
decide
that
a
little
bit
later
after
the
fact,
I
think,
as
far
as
general
access
I'm
kind
of
clicking
around
in
data
studio
here
too
abby
and
I
see
yeah.
A
And
I
see
you
can
add
people
by
names
or
email
addresses.
I
wonder
if
you
don't
mind
creating
kind
of
the
master,
I
guess
data
studio
report
and
seeing
if
we
can't
share
it
to
the
it's,
a
kubernetes
leads
I'll,
get
you
the
official
email
for
it.
If
we
can
share
it
out
to
a
google
group,
that
will
be
the
best
option
that
way
the
google
leads
could
then
have
access
to
editing,
modifying,
maintaining
managing
the
report.
If
that
doesn't
work,
we
can,
alternatively,
switch
to
sharing
it
out
to
all.
A
A
Cool
no
problem.
Sorry,
it
took
a
million
days
to
get
back
to
you
on
that.
A
All
right,
cool
and
then
moving
on
to
kubecon
sessions
go
ahead.
Do
you
want
to
take
this
section.
B
Sure
so
we
basically
had
two
sessions
regarding
the
documentation
project,
so
one,
although
today
she's
not
here
as
less
they
hold
the
session
for
technical
writing,
which
is
awesome.
I
think
we
actually,
if
you
you,
are
one
of
the
maintainers.
B
You
might
know
a
lot
of
the
facts
that
she
talked
about
on
this
session,
but
if
you're
new
to
contributing
the
documentations
and
if
you
want
to
get
involved,
this
is
yeah.
Definitely
one
of
the
good
resources
to
learn
how
to
manage
document
documents
and
stuff
so
yeah.
That
was
good.
I
think
so.
I
I
appreciate
station
a
lot.
I
wanted
to
say
thank
you,
but
she's,
not
here
so
maybe
next
time
yeah.
So
that's
the
first
one
we
had
and
the
second
one
is
the
session
I
actually
attended
as
speaker.
B
That
was
about
your
path.
You
know
called
contribution
in
the
community
kubernetes
community,
so
it's
not
just
for
documentation,
but
also
a
lot
of
activities
are
going
on
in
the
community
like
contributing
experience
and
the
project
management
under
release
engineering
yeah.
I
think
there's
one
of
the
release
folk
here.
I
guess
yeah
so
yeah,
it's
part
of
it
too.
B
Yeah,
so
it's
basically
for
beginners
to
open
a
door.
Your
contributions
are
welcome
and
yeah.
I
got
the
result,
stats
from
the
cncf
team
and
we
had
around
400
attendees,
both
in
real
time
and
also
the
on
demand
afterwards
yeah.
That's
that's
what
we
did
for
kubecon.
A
Awesome
awesome
thanks
for
bringing
that
up
and
thanks
for
recognizing
this
lesson.
Your
work
here
definitely
awesome
and
definitely
good
sessions
worth
checking
out
for
sure.
A
A
If,
if
my
memory
serves
me
correctly,
we're
talking
about
each
release,
there's
usually
a
little
bit
of
toil
around
the
reference
docks
and
potentially
bringing
up
some
of
that
toil
with
victor
and
and
having
a
discussion
around
there.
I'm
happy
to
move
this
if
there's
no
questions
or
comments,
but
just
wanted
to
keep
track
of
it.
Any
thoughts,
tim
or
victor.
On
this
bullet
point
I
would
say,
we'd
have
a
quick
chat.
A
Yeah,
I
am
all
for
that,
let's
bump
it
for
the
following
week.
If
that
works
and
victor,
would
you
be
okay
next
week,
potentially
talking
about
some
of
the
reference
backs
process?
As
you
understand
it,
or
maybe
we
can
kind
of
talk
about
some
of
the
areas
that
are
a
little
bit
more
hairy
at
the
end
of
the
release.
A
Yes,
absolutely
cool.
So
moving
on
to
the
next
item,
moving
up
the
contributor
ladder
tim,
do
you
want
to
take
this
one.
G
Yeah
we're
close
to
time,
so
I'm
going
to
try
and
be
brief.
I
want
to
encourage
people
to
look
at
well
only
people
who
want
to
but
people
who
want
to
look
at
becoming
reviewers
and
people
who
want
to
look
at
taking
on
bigger
technical
tasks,
people
who
are
who
have
a
an
itch
to
scratch
in
terms
of
volunteering,
otherwise
helping
out
with
the
kubernetes
docks
to
step
forward.
G
In
slack,
I've
got
a
bunch
of
different
size,
things
that
I
could
help
mentor
people
with
and
I'd
like
to
help
people
move
up
the
contributor
ladder.
I've
like
particularly
got
a
few
things
on
the
fly
at
the
moment,
so
I
wanted
to
mention
it.
G
Cool,
I
don't
know,
I
mean
slack
if
you
want
to
you
know
if
you
want
to
do
that
step
forward
and
ask
in
slack,
and
we
will
find
you.
A
Cool
yeah
and
I
appreciate
bringing
this
up,
but
definitely
an
important
topic,
and
I
would
echo
your
your
same
comments
that
I'm
very
willing
to
help
mentor
or
help
folks
move
along
the
contributor
ladder.
A
It's
always
not
a
clear
path
and
I'd
always
recommend
that
if
you
don't
have
your
kubernetes
just
community
membership,
which
I
believe
is
five
prs
and
two
sponsors-
that's
probably
the
first
hurdle
to
to
get
over
and
if
there's
any
questions
around
becoming
a
kubernetes
contributor
or
a
member,
and
you
haven't
done
so
yet,
there's
no
shame
in
bringing
it
up
in
the
sig
docs
channel
opening
publicly.
You
can
definitely
dm
myself.
I'm
gonna
volunteer
to
tim
as
well,
but
happy
to
get
you
over
that
initial
hurdle.
A
If
you
haven't
done
so
yet
and
if
you
are
currently
a
contributor
or
kubernetes
member-
and
you
want
to
move
it
into
more
of
a
reviewer
role
or
an
approver
role-
definitely
happy
to
assist
with
that
as
well.
There
are
some
areas
that
kind
of
are
fast-tracked
to
approve
or
fast
track
to
higher
levels
of
permission.
Usually,
that
is
your
release,
lead
or
your
localization
lead,
and
those
are
also
advanced,
contributing
opportunities
there,
but
but
tim's
right
on
the
money
with
zach
stepping
down
to
emeritus.
A
I
would
imagine
that
that
we
ultimately
need
to
get
a
get
back
to
a
odd
number
of
chairs,
just
for
the
sake
of
consensus
as
well
as
I've
been
doing
this
for
about
two
years
now
and
ultimately,
my
run
will
come
to
an
end
before
you
know
it
and
we'll
have
to
look
for
more
approvers
and
reviewers
as
well
so
spot
on
there.
If
we
can
help
in
any
way.
Let
us
know
that's
a
great
topic
to
bring
up.
A
A
All
right
here
here
not
too
much
there.
I
think
it
would
be
healthy
to
bring
the
carry
this
conversation
also
to
the
upcoming
couple
weeks.
Just
to
keep
this
open
conversation
going
eddie
I
saw
that
you
joined
back.
If
you
want
to
talk
about
cute
pillow,
docs
you're,
more
than
welcome
to
we
have
about
two
minutes
left
here.
Otherwise
we
can
pump
it
punch
it
to
next
week.
A
Yeah.
We
can
put
this
in
next
week
cool.
Do
you
want
to
give
us
a
teaser
preview
in
a
minute
or
just
we'll,
save
it
all
for
next
week
yeah?
Well,
this
is
just
the
first
time
I
was
able
to
come
to
sig
docs,
and
this
has
been
on
my
backlog
for
a
bit,
so
I
just
wanted
to
sync
up
and
find
out
what
we
needed
to
get
done
there
to
consolidate
things
and
yeah
cool
sounds
sounds
in
line
with
what
we're
doing,
with
all
the
other
kind
of
side
sites
and
what?
A
What
now
so,
definitely
look
forward
to
that
discussion.
So
I
know
we
have
about
a
minute
left,
any
other
things
that
folks
like
to
bring
up
for
discussion.