►
From YouTube: K8s SIG Docs Meeting for 20201110
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'm
jim
angel,
one
of
your
co-chairs
for
sig
docs.
It
is
november
10th
2020.,
it's
the
first
meeting
we've
had
in
two
weeks
or
so
because
there
was
a
meeting
that
was
canceled
as
well
as
for
the
u.s
election.
We
had
the
november
third
meeting
cancelled.
So
it's
it's
good
to
see
everybody
again
and
get
back
into
somewhat
regular
cadence,
although
next
week
is
kubecon.
A
A
Yep,
I
see
a
lot
of
familiar
folks,
welcome
back
everybody,
no
new
contributors
but
good
to
see
some
friendly
faces
and
for
updates
and
reminders
this
week,
week's
pr
wrangler
is
myself
and
to
be
completely
honest
and
transparent
with
everyone
else's
call.
I
haven't
been
doing
a
great
wrangling
job,
but
expect
to
see
some
noise
and
chatter
from
me
later
on
tonight
and
throughout
the
week
as
I
get
into
full
gear
as
the
pr
wrangler
and
next
week's
wrangler
is
kubecon.
A
So
big
question
mark,
but
I
do
see
that
tim
banister
might
chip
in
which
would
be
much
appreciated
and
approvers
make
sure
you
know
your
scheduled
pr
wrangler
shifts
that
is
in
the
agenda
as
well.
If
you
need
it
so
jumping
straight
to
the
agenda,
and
I
started
chatting
about
this
a
little
bit,
I
like
the
idea.
I
want
to
bring
it
up
with
the
group,
and
that
is
for
kubecon,
since
a
lot
of
folks
are
attending
events
they're
watching
videos
they're
hosting
their
own
different
sessions.
A
It
worked
out
really
well
for
kubecon
eu
to
switch
this
meeting
to
be
opt-in
only
basically
a
social
hangout.
If
you
want
to
join,
you
can,
if
not
you're,
not
missing
out
on
an
official
meeting,
are
folks,
okay
with
us
doing
that
again
next
week,
do
they
have
any
other
suggestions
of
what
they
would
like
to
do
any
thoughts
on
that.
C
A
And
if
I
recall
correctly
for
the
eu
one,
there
is
a
cncf
like
social
hour,
hangout
channel
and
there's
slack
and
I
believe
tim
boosted.
The
meeting
there
saying
hey
if
you
want
to
hang
out,
learn
about
sig
ducks,
and
that
was
that
was
awesome.
C
A
Awesome
yeah.
No,
I
think
that's
a
great
idea
and
I
think
it
really
alleviates
the
the
burden
of
pressure
and
a
lot
of
busy
folks
here
in
the
community,
so
strong,
plus
one
will
roll
forward
with
that
all
right.
So
up
next
is
the
release
120..
I
did
update
some
notes
from
what
I've
heard
from
jeremy
rickard
about
the
current
status
of
the
release.
So
for
those
who
don't
know
the
tentative
release
date
is
december.
A
E
Yeah
so
a
few
meetings
ago,
we
actually
had
a
discussion
about
whether
we
should
extend
the
docs
deadline,
but
they
actually
came
back
and
said
no,
because
if
that
happens,
then
release
would
get
extended
and
then
every
release
is
already
on
december
8th
and
if
you
go
beyond
december,
8th
everyone's
in
like
in
the
holiday
mode,
and
it's
not
going
to
get
done
so
that's
the
response
that
we
got
from
the
sick
release
team.
So
pretty
much.
E
If
you
look
at
the
timeline
like
we
are
like,
I'm
not
sure
how
we're
gonna
do
this,
because
there
is
58
enhancements
and
they're
all
being
tracked
right
now,
but
the
code
freeze
is
this
thursday,
so
I'm
hoping
because
by
looking
at
all
the
docs
pr,
that's
currently
we're
tracking
everything's
on
hold,
except
maybe
like
three
that
I
mentioned
yesterday,
because
the
kkprs
have
not
been
merged
then
so
I'm
hoping
that
after,
like
a
lot
of
enhancements,
will
make
it
to
the
code
phrase
that
will
you
know
lighten
our
load.
F
So
what
I'm
saying
is
that
there
are
draft
prs
for
draft
features.
The
features
aren't
in,
but
the
documentation
is
not
finished
for
quite
a
few
pr's
as
well.
Nothing
wrong
with
finishing
your
documentation.
Whilst
the
code
is
being
reviewed-
and
I
really
encourage
it
rather
than
doing
those
in
series.
C
Yeah,
but
I'm
just
also
looking
at
the
statuses
of
these
two
pages
worth
of
prs,
which
is
terrifying
and
there's
there's
a
lot
of
things
that
are
on
hold
but
just
haven't
received.
It
looks
good
to
me
slash
and
approve.
Yet
do
you
want
us
to
kind
of
swarm
and
on
the
things
that
aren't
works
in
progress
start
dropping
looks
good
in.
Is
that
what
you're
hoping
for.
E
So
they're
not
ready,
like
tim
said,
a
lot
of
them
are
not
ready
to
be
reviewed
and
everything
that
has
a
hold
is
that
their
kkprs
aren't
not
merged.
Then.
So
I
actually
check
those
like
every
day.
Try
to
remove
holds
if
I
can,
but
I
haven't
been
able
to
a
lot
of
them.
So
I
I
don't
know
what
the
plan
is,
because
after
code
freeze,
then
we
have
kubecon
and
that
after
kubecon
we
have
our
deadline
for
docs,
which
is
on
november.
E
E
A
D
A
D
So
if
let's
say
I
saw
there
is
a
lot
of
pr's
that
actually
is
still
in
the
draft
mode,
then
should
we
start
reviewing
that
or
no
because
it's
kind
of
confusing
when
the
status
is
still
graphed,
as
in
github
draft,
not
like
ready
to
be
reviewed.
F
You
know,
there's
nothing
wrong
with
saying,
oh
and
by
the
way
I
I've
given
you,
I
don't
think,
there's
anything
wrong
with
saying
I've.
Given
you
some
essential
feedback,
and
here
are
some
other
suggestions
that
are
up
to
you
to
take.
F
F
A
And
I
would
add
to
that
as
well,
and
I
agree
that
we
can
definitely
move
in
that
direction,
but
I
think
also
there's
nothing
wrong
with
a
little
bit
of
nagging.
So
we
see
a
pr,
that's
been
in
the
draft
mode
or
it's
been
work
in
progress
for
over
a
week
two
weeks.
Whatever
we
think
is
a
reasonable
amount
of
time.
I
think
a
week
is
more
than
reasonable
enough
to
say:
hey
look,
there's
been
no
status
change
in
over
a
week,
any
updates
any
progress.
I
think
poking
in
that
sense.
You
know.
A
E
A
Awesome
yeah.
I
added
that
to
the
agenda
just
for
tracking
but
yeah.
That
sounds
great.
If
the
docs
team
wants
to
take
a
look
at
that,
I
feel
like
with
the
code
freeze
on
thursday.
We
should
have
a
better
idea
of
what's
getting
in
or
not
even
with
exceptions.
Hopefully,
if
every
enhancement's
an
exception,
I
feel
like
there's
a
bigger
problem.
That's
not
not
a
dox
related
problem.
You
know.
A
But
yeah,
I
think,
for
man
in
the
the
docs
release
process,
I
wouldn't
hesitate
to
reach
out
to
the
sig
docs
group.
I
know
there's
the
release
channel
itself.
I
see
a
lot
of
great
communication
going
on.
There
feel
free
to
copy
any
of
those
messages
and
post
them
in
boost
for
visibility
on
the
sig
docs
channel.
A
I
consider
this
to
be
all
hands
on
deck.
We
can
help
out
any
way
we
can
boost
it,
raise
visibility
as
much
as
you
possibly
can
and
feel
free
to
ping
people
dm
them
on
slack
reach
out
to
them
on
github.
A
You
know,
definitely
get
the
information
and
progress
that
you
need
as
you
need
it.
One
thing
that
was
shared
with
me
during
the
release
process
is
docs
as
a
sub-release
project
or
a
sub-release
group
does
have
the
power
to
potentially
block
or
prevent
enhancements
from
making
the
kubernetes
release.
It
also
has
the
ability
to
dictate
when
that
release
comes
out.
Some
of
those
deadlines.
A
Historically,
we
haven't
had
to
enact
on
those.
You
know
quote
unquote
powers,
but
just
know
that
it's
not
like
we're
going
to
get
steamrolled
by
the
kk
community.
Doing
what
they
do
and
just
not
doing
doc
straight
up
ducks
are
an
important
piece
of
the
kubernetes
release,
and
we
want
to
make
sure
that
we
have
the
the
leverage
and
mechanisms
we
need
to
get
the
docs
in
place
for
the
release
successfully
and
if
things
that
we're
doing
today
aren't
working,
we
need
to
raise
those
alarms
and
make
those
changes.
G
And
I
sorry
well
I
just
wanna.
I
just
want
to
add
one
more
thing
to
what
out
of
those
50.
At
least
half
of
them
might
need
a
tech
review
in
addition
to
the
docs
review
to
verify.
So
I
would
suggest
that
we
could
start
asking
the
six
and,
if
the
release
lead
could
help
and
if
you
need
any
help
from
the
release,
leads
team,
please
give
a
shout
out
or
reach
out
we'll,
be
happy
to
help
in
any
way.
G
But
that
has
been
a
huge
blocker,
at
least
in
the
last
release,
that
the
things
would
be
reviewed
from
their
dog
sick
dogs
perspective
inside
and
they
would
have
lgtm.
But
the
tech
review
would
take
a
while,
because
it's
very
hard
to
get
a
hold
of
those
folks.
They
are
always
busy.
G
Whoever
is
going
to
review.
They
already
have
so
many
announcements,
they
are
reviewing
the
code
and
they
also
need
to
review
the
docs.
So
you
might
want
to
plan
a
little
bit
for
that.
A
Yeah
yeah,
I
would
definitely
plus
one
to
that
as
well,
and
I
know
there's
not
one
blanket
statement.
It
comes
to
technical
review,
but
if
there
are
any
docs
out
there
that
we're
looking
at
the
content-
and
we
don't
think
we
have
the
ability
to
give
a
proper
technical
review
finding
those
reviewers
early
rather
than
later
might
help.
A
This
is
a
really
general
statement,
but
occasionally
I've
seen
prs
come
in
for
the
release
or
enhancements
where
grammatically
and
content-wise
they
look
good
to
me
and
what
they're
saying
sounds
good,
maybe
it's
about
certificates
or
about
other
nuances
of
kubernetes,
where
I'm
like.
This
feels
right,
but
I'm
just
not
100
sure
this
is
entirely
accurate.
A
I've
had
success
too,
just
dming
folks
on
slack
or
poking
people
who
are
related
to
the
pr
saying,
hey
look
just
you
don't
even
need
to
do
a
docs
review
on
this.
Just
is
this
information
generally
accurate
and
we
can
actually
merge
it
in
for
the
release
and
getting
a
thumbs
up.
There
would
be
great.
I
know
I
dealt
with
that
a
lot
when
it
came
to
like
advanced
storage
mechanisms,
things
changing
and
graduating
where
yeah.
That
sounds
good.
But
let
me
just
make
sure
someone
in
storage
says
yeah.
A
C
I
wonder
if
a
suggestion
for
sig
release
to
take
to
the
retro
is:
do
we
need
to
start
effectively
assigning
a
point
person
from
each
sig
to
do
tech
reviews,
because
this
always
seems
to
be
a
problem
where
we're
constantly
chasing
tech
reviews
and
it's
a
problem
for
technical
writers
in
general
and
just
saying
that
as
a
part
of
the
release
process,
if
you're
submitting
an
enhancement,
you
also
have
to
submit
the
person
who
is
going
to
do
the
tech
review
on
the
docs
and
it
cannot
be
the
same
person.
E
Sorry
was
taking
notes
but
yeah.
I
like
the
idea
and
I
can
write
it
down
in
our
retro
board.
A
Yeah
now
I'd
be
strong,
plus
one
for
that
as
well.
I
think
it
makes
sense.
We
could
potentially
even
include
that
in
the
opening
template-
or
you
know
some
of
the
formatting
options
there
to
say
all
right.
You
can
open
your
draft
pr.
You
can
open
up
what
whatever
docs
you
got
to
open
up.
You
could
open
up,
but
then
also
include
in
the
opening
pr
message
who
the
tech
reviewer
is
going
to
be.
At
that
point,
person.
A
Cool
anything
else
about
the
release,
sounds
like
we're
all
hands
on
deck
and
ready
to
help
out
where
we
can.
E
I
have
like
just
a
few
more
things:
the
the
integration
branch
is
not
healthy
after
one
of
the
pr
got
merged
done
and
I
don't
really
see
any
problems
with
the
loss,
but
I
mean
like
it
failed
of
course,
but,
like
I
think,
maybe
me
triggering
it
would
solve
it,
but
I
don't
have
that
access.
But
if
you
could
take
a
look,
I
can
I.
F
What
you
can
do
is
file
an
issue
I
mean
you
don't
need
to
but,
like
I
think,
if
this
happens
file
an
issue
to
track
that
it's
got
a
fault
and
and
then
post
that
issue
into
slack
and
sort
of
highlight
that
as
pulling
the
end
on
chord
and
getting
the
supervisor
to
come
along
production
line,
it's
summoning
help
and
in
other
words,
what
another.
What
I
would
say
is
please
don't
feel
you
have
to
wait
till
the
the
weekly
meeting.
E
Yeah
yeah,
okay
got
it
and
then
another
thing.
So
I
know
we
talked
about
the
automatically
applying
milestones
and
hold
label
it
during
the
sick
planning
meeting.
So
I
actually
created
an
issue
for
it
because
there
was
a
lot
of
pr's.
There
was
a
lot
of
discussion
going
on
in
different
pr
different
places,
so
we
don't
have
to
talk
about
it.
E
I
just
want
to
make
sure
that
everybody's
aware
that
it's
there's
an
issue
there
and
there
are
two
topics
that
need
to
be
discussed
and
you
can
like
comment
on
it
on
the
issue
unless
we
want
to
talk
about
it
here,
but
I
think
I
already
took
a
bunch
of
time.
D
I
actually
created
a
point
here
about
that
just
so,
everyone
is
aware
and
about
the
pr
as
well.
A
I
think
it'd
be
great
to
spend
some
time
on
it.
I
mean
really
the
point
of
these
weekly
docs
meetings
when
we're
all
together
here
to
solve
some
of
these
problems.
Raise
awareness
talk
about
context,
even
if
we
talk
a
little
bit
more
about
the
release.
I
feel
like
this
is
all
important
content,
so
yeah.
Let's
cover
that
a
little
bit
more
in
depth
when,
when
every
topic
comes
up,
which
it
will
surely
hear
and
is
that
the
same
issue
interview
that
you
linked
in
there
as
well.
E
So
sig
release
is
working
on
a
receipt
process
for
caps,
and
it's
actually
so.
I
actually
attended
the
meeting
today
and
it's
gonna
start
they're
gonna
create
a
cap
for
it
for
the
process
and
start
working
on
it
for
the
next
release,
but
it's
actually
gonna
affect
how
the
release
works.
The
process
so
especially
because
it's
making
changes
to
the
tracking
sheet
for
the
caps
which
will
affect
the
docs.
So
I
just
wanna.
Let
people
know
about
that
project.
E
If
you
haven't
seen
that
I'm
gonna
also
put
a
link
in
the
chat,
they
have
like
a
overall
process
that
they
have
they're
documenting
right
now.
So
if
you
want
to
take
a
look
leave
a
comment,
any
like
you
know,
comment
from
sick
dogs
would
be
really
appreciate.
It
and
I'll
keep
an
eye
on
it.
If
there
any
like
progress
that
needs
to
be
announced
here,
I
will
do
that,
but
just
fyi
there.
A
E
So
right
now,
as
I
said,
docs
we
are
using
the
tracking
sheet
right,
like
the
google
excel
to
track
all
the
enhancements
for
enhancement,
team
and
docs
team,
but
they
are
moving
that
to
get
basically
so
that
will
right
so
they're
gonna
track
all
the
caps
and
get
in
instead
of
a
tracking
sheet.
So
then,
like
the
docs
team,
won't
have
any
enhancement
to
track
if
their
enhancement
team
is
not
going
to
do
that.
E
C
So
here's
another
suggestion.
I
wonder
if
the
owners
of
this
kept
to
be
need
to
come
and
talk
to
us
about
it
at
one
of
our
next
meetings
and
if
maybe
we
need
to,
like
crook,
that
finger
and
just
say
hey,
please
come
talk
to
us
so
that
we
can
form
an
opinion.
E
Sure
I
can
relate
that
message.
Sure
I
mean
like
I
think,
they're
gonna
like
create
a
cup
and
but
I
will
relate
on
that
fish
yeah
could.
A
A
Yeah
it
sounds
like
there's,
you
know,
I'm
just
thinking
right
now,
there's
a
handful
of
ways
to
solve
that
problem.
Obviously
we
don't
need
to
discuss
the
options
here,
but
just
with
the
difference
of
whatever
they're
going
to
end
up
doing
or
that
approach
they'll
take
doesn't
mean
that
the
docs
can't
find
a
way
to
easily
track
docs
update,
spreadsheets
things
of
that
nature,
but
definitely
can
cross
that
bridge
as
they
get
more
finalized,
and
what
that
final
get
state
looks
like
and
potentially
there's
an
opportunity
for
us
to
collaborate.
There.
E
A
A
It
looks
like
this
pr
here
the
deploy
preview
worked,
but
then
it's
not
happy
about
these
top
checks,
so
yeah
either
way.
I
think
issue
and
looking
at
that
would
be
good,
but
it
looks
like
the
vnx
staging
branch
is
building
successfully,
but
those
header
rules,
mix,
content,
pages
change
and
redirect
rules
are
failing,
which
I
couldn't
tell
you
what.
A
A
All
right
so
moving
on
to
the
blog
update,
it
looks
like
business
as
usual.
Keep
these
coming.
So
I
I
like
that.
I'm
guessing
taylor.
That's
that's
europe,
but
I
appreciate
that
absolutely.
H
Yeah
happy
to
see
all
the
different
focuses,
and
things
like
that
going
on.
Obviously,
2020
has
been
no
shortage
of
just
events
in
general,
but
I
really
like
reading
about
the
kubernetes
ones,
most
of
all,
very
biased
here,
so
keep
them
coming
if
you've
got
good
ideas
or
if
you,
if
anyone
wants
to
talk
about
any
blog
post,
they
want
to
write.
You
know
I'm
more
than
happy
to
sit
down
and
chat
with
some
people
on
that
front
as
well.
A
Awesome
yeah
thank
you
and
moving
on
to
the
updates
and
prs.
If
anyone
has
any
other
updates
or
pr's
or
issues,
they
want
to
bring
or
raise
up
visibility
and
feel
free
to
add
them
there.
The
one
I
added
was
this
enhancement,
so
this
kept
that's
potentially
coming
down
the
pipeline.
A
There's
no
action
needed
right
now,
but
I
wanted
to
give
some
context
and
what
this
cut
means
and
potentially
the
work
that's
coming
our
way
in
relation
to
this
cup.
So,
ultimately,
I
want
to
say:
maybe
it
was
a
year
ago,
a
year
and
a
half
or
so
ago,
all
of
the
cloud
providers
got
pulled
out
of
the
kubernetes
kubernetes
repository
and
said
your
code
should
belong
to
your
you
know
cloud
providers,
code
base
and
integrate
with
some
sort
of
interoperable
cloud
provider
in
kubernetes
kubernetes.
A
So
what
that
also
meant
was
when
the
source
code
got
pulled
out
of
kubernetes
kubernetes,
also
the
documentation
of
some
of
the
related
pieces
there,
some
of
it
never
existed
to
begin
with,
they
were
all
hosted
in
the
git
repos
already
I
don't
know
of
any
massive
cloud
provider
documentation
that
was
taken
out
of
the
kubernetes
website,
but
ultimately
this
kept
tries
to
establish
a
guideline
of
what
documentation
looks
like
for
out
of
tree
cloud
providers.
A
A
This
might,
at
the
end
of
the
day,
be
that
kubernetes,
sig
doc
says
here's
a
recommended
way
to
deploy
to
netlifier
here's
the
recommended
theme
or
a
way
to
stay
in
synchronized
with
our
with
our
web
page.
It
might
be
a
little
bit
more
standardized
than
than
what
we've
seen
in
the
past
with
the
different
sub
projects.
Breaking
out,
like
I
know,
kind
has
its
own
netlife
page
cubecuddle
has
its
own
netlify
page.
A
A
A
All
right,
moving
on
to
okay,
I
added
an
action
item
to
talk
about
the
background
and
demo
krell
corel.
If
prepared,
I
am
not
prepared
to
do
a
demo,
we're
going
to
skip
that,
hopefully,
after
kubecon
I'll
be
able
to
throw
something
together.
That
was
something
that
came
up
in
our
quarterly
review.
We've
talked
about
using
the
corel
automation
tool
for
some
of
the
docs
release
processes,
and
karen
made
the
great
suggestion
that
you
know
giving
just
a
general
demo
or
overview
of
what
it
is
how
it
works.
A
Some
of
the
components
there
for
folks
who
aren't
tied
into
the
release
team
would
help
out
a
ton,
and
I
completely
agree
just
need
to
put
something
together
and
that
will
be
coming
here
in
probably
two
weeks
or
so,
and
with
that
we'll
move
on
to
your
v
automation
and
manual
process
being
merged,
and
this
was
related
to
anna's
issue
earlier.
If
you
all
want
to
take
that
away.
D
Yes,
so
basically,
we
have
some
kind
of
discussions
where
we
eventually
decided
that
we
will
use
test
infra
tools
pro
one
and
there
is
a
several
pr
that
actually
been
merged.
D
But
another
follow-up
discussion
is
whether
we
should
add
fee
prefix
to
the
depth
staging
as
well,
because
the
others
I
mean
the
kiki
is
using
graphics.
Feel
right.
Please
correct
me:
if
I'm
wrong,
no,
that's
right.
Yes,
yeah!
Basically
that
and
we
need
some
kind
of
input,
whether
it's
necessary
for
us
to
kind
of
rename
the
branch
for
current
release,
or
we
will
start
it
from
the
next
release,
and
maybe
if
there
is
something
that
you
want
to
bring
up
anna
for
this.
E
D
A
Cool
just
from
a
general
understanding
at
a
very
high
level,
whether
a
prefix
of
the
v
or
not,
doesn't
matter
so
much
in
the
sense
of
how
we
move
forward.
Whether
we
do
that
or
not
the
most
important
thing
is
going
to
be
the
documentation
around
it
and
the
release
leads
moving
forward.
So
any
change
that
we
make
to
naming
branches
strategy
prefixing
the
v
or
not,
labels.
A
How
that
happens
each
subsequent
release.
We
have
at
least
four
other
releases
that
are
going
to
need
to
essentially
deal
with
this
change,
as
well
as
as
the
merge
is
trickled
down,
and
what
I
mean
by
that
is
master
at
some
point,
becomes
a
release
branch
and
that
release
branch
becomes
an
older
release
branch
and,
as
we've
updated
and
changed
things
in
the
site.
There's
kind
of
this
trickle-down
effect
of
changes
that
we've
made
up
streams.
A
So
I
I
don't
really
have
a
strong
opinion
at
the
moment
other
than
it's
just
a
big
burden
from
a
knowledge
transfer
from
a
documentation
standpoint
and
making
sure
that
there's
there's
so
much
so
much
documentation
out
there
on
the
release
process.
A
As
far
as
the
different
areas,
whether
it's
okay
website,
whether
it's
in
the
sig
release
handbooks,
whether
it's
you
know
in
our
meeting
minutes
in
our
old
youtube
videos,
just
making
sure
that
we've
covered
all
of
our
bases
and
none
of
the
older
lingering
stuff
is
out
there
if
we
change
direction
but
whether
we
change
it
or
not,
my
general
gut
says
to
go
with
what
the
majority
of
the
community
is
doing,
but
I'd
be
open
for
anyone
else's
feedback
or
comments.
A
E
So
it's
just
covering
well,
one
of
the
main
thing
was
the
whole
label
and
that
I
think
that
means
like
a
bigger
discussion,
because
I
thought,
during
the
planning
meeting
that
we
agreed
to
have
a
hold
label,
but
karen
brought
a
good
point
with
that,
maybe
hold
is
not
really
necessary
for
every
pr
that's
created
to
the
deaf
brand,
so
I
just
need
a
feedback
from
people
here
and
if
you
need
some
time
to
think
about
it,
you
can
think
about
it
and
comment
on
the
issue
later.
E
A
Cool
yeah
I'll
definitely
take
some
time
to
to
get
a
closer
understanding
on
the
issue
and
leave
some
feedback
there.
You
know
and
leave
it
in
stone,
cool
all
right,
so
moving
on
brad
brought
up
earlier
on
the
call-
and
I
wanted
to
capture
this-
for
the
recording-
was
about
the
time
zone
changes
in
the
us
so
for
context.
The
us
recently,
I
think
we
sprung
ahead.
We
fell
back
in
the
fall,
we
lost
an
hour
in
the
fall
and
a
lot
of
our
international
or
apec
meetings
deal
with
utc
timing.
A
So
when
the
us
does
a
time,
change
or
a
daylight
savings
time,
change
ultimately
doesn't
really
get
reflected
in
the
utc
time
why
this
is
complex,
as
opposed
to
saying,
okay.
Well,
it
was
eight
o'clock.
You
know
in
previous
days,
and
now
it's
going
to
be
nine
o'clock
course
it's
gonna
be
seven
o'clock.
Whatever
your
standard,
local
time
is
what
makes
this
challenging
is
for
our
eight
pack
meeting,
for
example,
when
the
time
shifted
it
actually
went
into
the
lunch
time
of
some
of
our
korean
contributors.
A
So
they're
saying
that
you
know
we
don't
mind,
we
don't
mind
it
moving
and
jumping
an
hour
earlier,
as
we
you
know,
didn't,
do
anything
if
you
will
and
leaving
it
at
that
utc
time.
So
I
don't
have
a
great
answer,
but
I
wanted
to
bring
that
up
here
and
you
know
I
look
for
folks
like
cohey,
I
see
you're
on
the
call
from
you
know
the
the
other
side
of
the
pond.
If
there's
any
other
input
there
as
far
as
how
we
can
address
and
align
those
those
meeting
times.
C
So
I
actually
have
a
question
tim:
do
you
have
daylight
savings
time
in
the
uk
or
is
it
just
a
north
american
thing.
F
Yeah,
it
confuses
it,
confuses
microsoft,
a
lot
because
they
think
that
we
have
greenwich
mean
time.
We
have
great
mean
time
in
the
gmt.
A
F
That's
what
we're
gonna,
which
we
are
now
which
is
like
kind
of
the
predecessor
of
utc,
and
then
we
use
british
summer
time
in
the
summer,
and
then
we
and
then
the
techies
use
utc
all
year
round
or
set
their
computers
to
think
they're
in
iceland.
D
Basically,
in
europe,
it's
it's
still
common
for
us
to
have
like
daylight
surfing
time
also,
but
I
think
it's
come
like
one
week
earlier
than
the
folks
in
the
europe
I
mean
like
in
the
north
america.
I
B
So
I
I
can,
I
guess
I
could
manually
so
the
the
calendar
notices
caused
some
grief
too.
I
guess
jim.
A
Right,
and
so
there
is
the
ability
for
us
to
set
the
calendar
to
utc,
which
might
ultimately
be
the
the
easiest
outcome
here,
I'm
looking
at
coordinated
universal
time,
so
we
could
set
it
to
that
where
it
stays
without
being
impacted
by
daylight
savings
time.
A
Another
thing
about
that
that
probably
is
going
to
be
the
best
option.
Just
folks
need
to
be
aware
that
that
calendar
might
jump
up
or
jump
down
below
you
know,
depending
on
what
time
zone
you're
living
in
what
changes
happen.
I
believe
that
that's
how
our
apac
meeting
is
set
now,
just
to
the
the
coordinated
universal
time
or
utc.
B
I
think
that
would
work,
because
we
all
check
our
calendars,
and
so
you
know,
I
think
we
have
plenty
of
time
for
the
one
or
two
times
a
year.
It
moves.
A
A
And
then
also
the
other
question
that
would
come
up
potentially
is
for
the
monthly
localization
meeting,
I
believe,
like
the
documentation.
The
community
group
has
american
pacific
time
listed
in
there
for
a
specific
time
and
date
that
hasn't
been
changed
or
auto
updated
when
that's
going
to
also
shift
as
well.
So
utc
fixes
the
problem
for
apac
residents,
which
is
great,
but
we
might
need
to
consider
a
way
to
maintain
all
the
united
states,
and
you
know
the
northern
american
time
zoned
locations.
You
know
syd
community
documentation,
the
release,
notes.
C
Yeah,
the
other
thing
that's
actually
coming
to
mind,
too,
is
for
countries
that
are
shifting
around
time
zones
because
of
daylight
savings
time.
If
this
meeting
stays
consistent
in
time
and
space,
but
none
of
the
other
meetings
we
might
have
around
it
stay
consistent
in
time
and
space.
There
is
a
scenario
in
which
this
meeting
could
suddenly
for
two
or
three
weeks
overlap.
Other
meetings,
other
standing
meetings
that
we
have,
because
those
meetings
have
shifted,
but
this
one
hasn't
so
there's
this
part
of
me.
That
is
actually
thinking.
C
At
the
same
time,
pause
plus
pause,
we
have
a
very
strong
standing
contingent
population
that
is
in
asian
time
zones
and
in
european
time
zones,
and
that
is
due
to
the
nature
of
us
maintaining
localizations
and
him.
Whereas
I
don't
know,
if
that's
as
much
a
concern
for
other
sigs,
they
have
kind
of
transient
people
coming
and
going
from
diff
from
like
very
far-flung
time
zones
from
north
america.
C
So
they
may
not
see
the
same
level
of
concern
as
we
do
sorry.
For
that.
B
A
It's
definitely
predates
myself,
but
I
believe
that
the
concept
here
is
that
the
tuesday
regular
meeting
is
in
pacific
time.
That
has
the
utc
time
listed.
But
it's
going
to
be
consistently
for
the
you
know.
North
american
contributors
for
kubernetes
and
anita
rose
for
the
apec
meeting
to
exist.
We
did
the
once
a
month,
localization
or
apec
meeting,
and
then
we
added
on
the
localization
efforts
that
you're
being
brad
are
leading
once
a
month
as
well.
A
It
almost
might-
and
this
is
kind
of
a
wild
concept
of
doing
both
at
the
same
time,
but
it
almost
might
make
sense
to
leave
the
weekly
tuesday
meeting
a
specific
time
zone
meeting
throughout
consistently,
always
in
pacific
north
american
time
and
any
of
the
localization
apec.
Considering
meetings
such
as
our
monthly
apec
contributors
meeting
our
monthly
localization
meeting.
Maybe
those
get
locked
into
utc
to
accommodate
more
of
the
audience
that
generally
attend
those
meetings.
A
Cool
your
viewer
brad.
Could
you
take
the
action
item
once
I
switch
it
over
to
utc
to
announcing
it
to
the
team
saying
that
we
figured
this
out.
It's
going
to
be
utc
and
I'll
also
boost
that
in
signboxing.
Look
the
the
weekly
pacific
time,
tuesday
meeting
for
the
you
know.
Northern
american
folks
is
not
changing,
but
the
apex
specific
meetings
will.
C
A
C
We
I
can
wait
for
two
weeks
from
now.
I
think
yeah,
okay,
I
guess
one
thing
that
I
will
say,
though,
in
the
quick
interreading
time
period,
we
do
have
a
recommendation
pushed
in
for
changing
the
term
master
to
control
plane
in
the
context
of
nodes.
So
that
is
officially
a
thing
that
you
will
see
approvals
and
held
prs
and
the
likes
start
going
through
on
something
I
would
like
to
bring
to
the
attention
of
the
localizations.
C
So
you
have
a
recommendation
and
I
don't
know
what
the
best
way
for
you
to
implement.
That
recommendation
is
but
yeah,
that's
that's
the
short
update,
we'll
talk
a
little
bit
more
later
about
the
crunchy
updates.
B
C
I
I
So
that's
why
we're
behind,
so
it
is
kind
of
like
on
purpose,
but
at
the
same
time,
if
you
think
it's
urgent
and
you
should
change
it,
we're
totally
welcome.
I
mean
any
any
types
of
pro
requests
that
is
urgent,
so
I
think.
C
Priority
not
urgent
is
how
I
would
put
it
like.
Don't
don't
you
know,
get
gray
hairs,
but
don't
let
it
sit
forever.
I
Oh
so
yeah
as
as
it's
written
here
so
japanese
first
work
of
1.18
has
finally
been
merged,
so
it's
only
the
first
work
and
we
have
a
bunch
of
gifts
to
modify
and
yeah.
Korean
team
has
a
really
big
team
and
yeah
we're
actually
facing
difficulties
in
hiring
active
contributors
in
japanese,
and
I
think
other
languages
have
some
kind
of
difficulties
too.
So
yeah,
it's
just
an
update.
I
I'm
not
really
seeking
for
a
help
here,
but
yeah
this.
I
It's
just
an
update,
and
because
of
that
we
are
way
ahead
of
the
upstream
right
now
I
mean
no
way
behind
so
yeah.
That's
even
why
it's
kind
of
taking
time
to
merge.
I
mean
deal
with
that
master
thing,
yeah,
which
is
kind
of
fortunate
yeah.
A
Cool,
I
appreciate
you
bringing
that
up
and
and
feel
free
like
I
was
mentioning
earlier.
If
you
need
to
use
like
the
sig
doc
slack
channel
to
advertise
looking
for
contributors
or
contributes,
or
I
know
that,
there's
regular
office
hours
and
new
kubernetes
contributors
and
users
potentially
there's
a
recruiting
opportunity
there
that
maybe
they
don't
know
that
that
exists
or
that
opportunity.
A
Cool
we're
at
time,
so
we
will
punt
the
rest
of
the
agenda
for
the
next
next
meeting.
Next
meeting
will
be
a
kubernetes
social
hour
and
I
look
forward
to
seeing
you
all
there.
C
Yeah
I
mean
read
the
recommendation:
aaron
kirkenberger
wrote
it
and
he
did
a
really
really
great
job
with
our
kind
of
pilot
recommendation
and
very
very
in
short
notice.
Blacklist
whitelist
will
have
a
recommendation
up
for
pr
as
well.