►
From YouTube: K8s SIG Docs Meeting for 20201013
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
A
A
Oh
sorry,
I
really
appreciate
zach
stepping
in
for
raja
and
a
substitution
for
the
pr
anglership,
so
much
appreciated,
and
next
week's
pr
wrangler
is
karen
bradshaw,
kb
hockey,
and
that
is
listed
there
in
the
agenda.
Let
me
go
ahead
and
throw
the
link
to
the
agenda
in
chat
for
those
who
don't
have
it.
B
I'll
speak
status.
Okay,
I'll
go
ahead
to
some
touching
now
you
signed
up
for
it.
C
Okay,
I'm
sorry,
I
was
muted,
I'm
a
release,
docs
shadow
for
the
release,
docs
theme
and
our
status
is
green.
C
We
created
a
pr
or
to
match
master
into
the
dev
1.0
branch,
and
that
has
been
matched
okay
and
an
issue
we
were
having
with
you
know,
having
arts
and
hashtags
in
like
pr
names
or
comments,
also
got
resolved
by
appear
to
test
infra
by
nikita
yeah.
I
think
that's
all-
and
this
week
hello
me
hello.
Yesterday,
oh
okay,
yes,
so
the
enhancements
have
been
assigned
to
different
team
members
and
we
begin
tracking
the
docs
we
are
this
week.
Thank
you.
A
A
We
created
a
process
where
the
release
team
was
then
opening
up
in
their
fork,
the
emerge
pr
and
then
pr
in
to
kubernetes
website
and
for
the
most
part
it
worked
very
well.
The
biggest
challenge
was
if
anybody
were
to
merge
any
other
prs
into
master
before
synchronizing
the
two
branches,
the
actual
commit
tag
in
github
would
say:
issue
number
one:
two,
three
four
five
is
getting
merged
into
master.
A
So
inherently
there's
nothing
wrong
with
that.
However,
prow
has
a
rule.
That
would
say
if
there's
a
commit
message
that
has
a
hashtag
in
it
mark
it
as
an
invalid
commit
message,
because
they
didn't
want
triggering
alerts,
notifications
and
invalid
links
between
different
pr's
and
that's
a
great
check
to
have
when
you're
monitoring
just
kubernetes
website.
A
This
is
the
main
branch
by
itself,
but
when
you're
talking
about
using
that
check
against
a
merged
pr,
there's
a
lot
of
things
out
of
your
control
there,
where
you
can't
really
define
what
that
commit
message
is
without
actually
breaking
history
there.
So
I
I'm
not
aware
of
what
exactly
nikita
did
to
fix
that
if
it's
completely
removed
or
adjusted
for
that
specific
use
case.
But
ultimately
that
was
the
issue.
It's
a
valid
check.
It
makes
sense,
but
but
ultimately,
when
it's
emerged
pr,
it's
a
little
bit
funky
any
questions
on
that.
A
D
So
we
don't
have
any
upper
for
this
part.
We
we
don't
have
any
kind
of
meetings,
but,
like
yesterday
we
have
some
kind
of
problems
with
the
slack
names
finding
the
bengali
localization
group
to
the
correct,
like
abbreviations.
D
I
just
realized
that
we
can
do
that,
so
I
just
renamed
one
of
us
select
for
localization
group
for
bengal,
because
we
have
kind
of
invalid
variation
for
for
the
language.
It
should
be
the
m
instead
of
e,
so
I
created
the
r
and
what
helped
me
to
merge
it.
A
Gotcha
now
is
it
correct
in
kubernetes
website
as
well,
or
is
it
only
in
slack
that
it
was
incorrect.
A
A
Cool
thanks
for
the
update-
and
I
know
that
I
owe
the
localization
group
some
meetings
here
shortly
so
I'll
have
that
delivered
here
in
the
next
couple
days
or
so,
and
then
also
I
posted
out
to
the
localization
channel
as
well
as
the
docs
channel.
I
copied
over
the
youtube
videos,
so
we
have
videos
from
the
first
localization
meeting
for
folks
who
are
interested
in
catching
up
there.
A
A
E
E
Thank
you
all
right.
Let
me
see
if
I
can
resurrect
what
I
was
thinking
about
last
night
right.
Yes,
so
tim
bannister
made
april
on
on
basically
the
sitemap
from
doxy
just
like
a
standard
priority,
but
then
he
wanted
to
also
override
it
and
add
pages
that
had
a
higher
priority
relative
to
others
and
they
seem
like
sensible
pages.
E
I'm
sorry,
the
site
map
itself
got
a
higher
priority
for
what
is
kubernetes.
The
docs
like
kubernetes,
slash,
docs
and
then
slash
concepts
overview,
and
that
seems
sensible
to
me.
I
have
no
problem
with
it,
so
we
just
kind
of
wanted
a
chair
to
be
aware
of
this
before
I
went
ahead
and
merged
it,
and
I
don't
know
tim
if
you
wanted
to
add
any
additional
context,
but
I
was
fine
with
it.
E
F
So
I
can
tell
you
working
finance
ash
zac
you're,
all
about
you,
know
compliance
steps,
but
it's
good.
We
have
a
generated
xml
sitemap
for
the
kubernetes
website.
We
already
have
that
what
this
configuration
changes
is
basically
the
default
priority
changes
to
0.75
and
then
a
few
things
like
the
front
page
gets
1.0
and
those
other
pages
get
0.9.
E
A
Cool
yeah
and
sorry,
I
wasn't
paying
attention
to
that
one
there.
It
is.
D
A
It
seems
relatively
straightforward:
is
there
any
drawbacks
to
this?
It
seems
seems
trivial,
something
we
could
revert
it
if
there's
any
major
disastrous
effects
or
impacts
by
it.
F
I
mean
I'm
mainly
an
infrastructure
person,
so
I
think
this
is
fine,
but
if
anyone's
concerned
now
it's
a
good
time,
I
don't.
A
F
F
All
right,
oh
well,
I'm
going
to
bring
up
a
thing
which
yeah.
I
think
this
is
the
right
point
to
bring
it
up.
We
have
a
triage
process.
Now
you
want
to
talk.
Is
that
okay
to
talk
about
now?
Yeah,
absolutely
so
all
all
issues
coming
in
are
now
proud
spots
that
they
haven't
been
triaged
and
labels
them
as
deeds
triage.
F
It's
a
process
copied
from
the
main,
kubernetes
repo
and
that's
happening,
and
you
can
sort
of
add
other
labels
like
slash
kind
support
if
it's
actually
a
support.
Query
slash
triage
duplicate
if
it's
duplicate,
slash
triage
accepted.
If
it's
a
valid
issue
and
that's
the
thing
that.
D
Okay,
so
basically,
if
let's
say
we
accepted
the
the
three
ash,
then
should
we
put
the
level
of
the
sig
that
responsible
for
that
issue?.
D
Okay.
Okay,
sorry!
So,
basically,
if
let's
say
we
already
accepted
the
tradition,
should
we
put
a
label
for
the
sig
that
are
responsible
for
the
issues
or.
A
Not
if
we
should
put
a
label
for
like
let's
say
it's
sig
architecture,
for
example,
putting
those
labels
on
the
issues
as
well.
A
F
So
I
guess
my
rule
of
thumb
is
there's
plenty
of
stuff
that
doesn't
have
a
sig,
you
know
or
sig
docs,
which
I
don't
think
really
counts
as
needing
labeling.
But
if
someone
reports
that
the
documentation
about
cluster
storage
interface,
for
example,
is
wrong,
I
might
label
that
sig
storage
and
my
intention
there.
Let's
say
someone
comes
along
and
they're
from
scheduling
and
they're.
Looking
for
sig
scheduling
issues
to
work
on,
I
want
to
make
it
easy
for
them
to
discover
that
work.
F
A
A
Sounds
good
so
the
next
agenda
item
I
took
from
the
previous
week.
I
don't
know
if
we
really
have
much
to
discuss
here,
but
just
bringing
up
or
reiterating
the
cube
contact.
That
is
upcoming
and
some
of
the
folks
here
on
sig
ducks
working
on
it.
Whether
someone
wants
to
give
a
status,
update
or
ask
any
questions
or
talk
about
any
challenges
or
blockers
is
up
to
y'all
and-
and
I
guess
I'll
leave
it
open-ended
from
there.
G
I'll
come
off
mute
for
this,
we're
we're
doing.
Okay,
I
think
we've
basically
got
round
one
of
the
slides
up
to
date,
and
what
we're
doing
right
now
is
trying
to
coordinate,
to
do
kind
of
a
rehearsal
run,
see
where
we
invariably
have
too
many
slides
and
are
going
over
time
and
then
edit
down
one
thing
I'll
call
out
just
because
people
are
here
is
irvy
pointed
out
that
we
do
actually
have
consensus
on
two
times
tim,
both
of
them,
I
think,
are
today.
G
F
G
F
Right,
I
will
yeah
I
I
know
that
I
need
to
to
contribute
back
in
between,
as
the
the
four
of
us
need
to.
Oh,
the
four
of
us
need
to
actually
pick
a
time
to
do
that.
Rehearsing
and
recording.
A
Awesome
sounds
good
and
then
the
consent,
the
consensus,
that's
needed,
that's
all
handled
with
y'all
there's
no
action
really
needed.
There
sounds
like
tim
zone
in
that
one
perfect.
A
Sounds
good
looking
forward
to
it.
Moving
on
we
are.
This
is
the
announcement
that
we're
canceling
the
november
3rd
weekly
kubernetes
sig
docs
meeting
I'll
send
out
that
cancellation
today,
I
didn't
want
to
send
it
out
prior
to
because
it's
going
to
look
like
I'm
canceling,
the
next
upcoming
meeting,
so
try
to
be
as
clear
as
I
can
and
I'll
send
out
something
to
sig
docs
as
well.
This
is
for
the
us
or
united
states
election
and
november
3rd
to
open
up
people's
calendars
as
much
as
possible
to
assist
with
voting.
E
A
Yep
go:
go
out
and
vote
everybody
if
you,
if
you
can,
if
you're
in
the
united
states,
moving
on
to
the
quarterly
q4
planning
days,
just
a
reminder.
We
are
planning
as
of
right
now
to
go
over
our
quarterly
planning
on
october
22nd.
That
is
a
thursday
at
5,
00
pm
pacific.
A
That
was
a
tentative
time
proposed
last
week
we
heard
no
objections.
Now,
it's
relatively
formalized,
I
suppose
I'll,
have
a
document
coming
out
shortly.
I'll
share
it
on
slack
as
well,
and
folks
can
review
that
for
people
who
are
not
aware
of
what
happens
at
quarterly
planning,
these
are
the
long-term
goals.
These
are
the
projects
that
aren't
just
something
that
can
be
taken
at
an
individual
level
or
on
a
daily
level,
it's
kind
of
like
what
you'd
want
to
accomplish
over
a
quarter.
So
big
changes.
A
For
example.
I
know
one
that
tim
has
been
working
on
as
well
as
myself
is
getting
a
release,
page
updated
for
kubernetes
and
improving
the
website's
presence
when
it
comes
to
kubernetes
releases.
So
things
like
that
that
can't
be
accomplished
by
you
know
some
sort
of
weekend
project
and
then
more
the
long-term
objectives,
and
also
it's
a
it's
also
a
time
to
reflect
on
what
happened
to
previous
quarter.
What
went
well,
what
didn't
go
well.
A
And
the
last
item
here
I
actually
talked
about
earlier,
just
saying
that
you
know
youtube's
updated.
I
got
talked
to
contributes
about
why
youtube
videos
aren't
moving
over
you.
Zoom
videos
aren't
moving
over
nothing
major,
just
raising
awareness,
so
that
is
the
agenda
or
all
of
the
agenda
items
that
we
had
is
there
anything
else.
Folks
want
to
talk.
A
A
You're,
nothing
we'll
call
it
an
early
meeting,
appreciate
everyone's
time
and
talk
to
you
all
later,
thanks
jim
take
care.
Everyone
thank.