►
From YouTube: SIG Docs meeting for 20210706
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
Let
me
share
my
screen.
Oh
and
I'm
tim
banister,
so
yeah,
let's
talk
about
first
new
contributors.
Is
there
anyone
on
this
call?
Who
is
new
anyone
who
wants
to
introduce
themselves?
I
think
I
recognize
everyone,
so
I'm
going
to
move
on
this
week.
We
are
following
us
holidays,
and
so
there
is
no
one
doing
pr
wrangling.
A
No
one
officially
doing
it.
Approvers
and
reviewers
are
still
welcome
to
to
do
approving
and
reviewing
it's
just
that
there
isn't
someone
who's
volunteered
to
put
themselves
and
and
do
that
as
their
particular
thing
is
weak.
Next
week
it
will
be
steve,
perry53,
okay,
let's
move
on
to
a
release,
update
victor,
perhaps.
B
Hello,
everyone,
so
our
status
is
yellow,
but
mostly
because
the
integration
branch
has
some
conflict
since
we
merged
that
pull
request
with
the
feature
gates
with
the
feature
gates
update,
we
are
starting
to
pick
up
a
bit
more
speed.
Currently,
we
have
30
enhancements
that
need
documentation,
12
that
are
drafts,
12
that
are
ready
for
review
and
11
that
are
merged.
B
We
will
ping
people
this.
I
did
a
sweep
just
earlier,
and
I'm
going
to
continue
to
do
one
today
to
see
who
do
we
need
to
ping,
because
also
enhancements
has
been
giving
us
a
hand
to
remind
people
of
the
deadline
for
docs
pr,
and
I'm
going
to
finish
that
up
and
probably
being
the
rest
of
the
people
myself,
because
I
don't
think
that
there
are
that
many,
since
most
of
the
enhancements
are
at
risk
anyway,
and
enhancements
has
pinged
them
here
and
there.
B
So,
basically,
after
this
sweep
I'll
I'll
have
a
look
at
what
else
needs
to
be
done,
and
I
think
that's
it.
Nothing
comes
to
mind
outside
of
that.
So
that's
it
from.
A
So
I
have
a
question
victor:
how
are
we
doing
on
reviewing
those
12
ready
to
review
changes.
B
Currently,
to
be
honest,
I
did
review
some
pull
requests.
I
need
to
give
a
heads
up
to
to
the
shadows
to
also
have
a
look.
Currently,
the
main
focus
is
to
kind
of
wrap
up
the
rest
that
that
we
have
the
rest
of
the
enhancements
that
we
have
for
the
upcoming
deadline,
and
then
we
will.
B
A
Okay,
sure,
given
that
it
is,
you
know,
fourth
of
july
holiday
week,
and
that
the
the
freeze
is
on
the
ninth,
I
think
it's
reasonable
that
that
next
week
is
probably
going
to
be
the
big
one,
where
we
focus
on
making
sure
that
those
pr's
are
reviewable
and
get
reviewed.
A
Cool,
let's
move
on
to
issues
and
pull
requests;
we're
waiting
for
feedback
from
sig
release
about
the
the
overall
idea
of
using
automation
to
generate
the
feature
gates
list.
B
Yeah,
so
we
had
a
discussion
last
time
and
I
think
anna
yeah
anna's
here
as
well-
maybe
you
can
also
address
so.
The
main
concern
was
the
generation
from
the
generation
of
the
feature
gates
from
the
ammo
files
and
basically
tim,
and
I
have
discussed
this
offline
on
slack
and
yaml.
Is
there
basically
because
we
don't
have
any
kind
of
generated
data?
B
At
this
point,
however,
I
can
start
working
on
generating
that
from
from
the
actual
code,
if,
if
we
really
want
to
go
there,
if
we're
ready
to
go
there,
I
haven't
seen
any
like
kind
of
opposition
from
seek
release
for
doing
the
tool
itself.
But,
as
I
said,
the
discussion
was
really
around
the
yama
files.
But
if
we
remove
that
from
the
equation,
maybe
we
can
move
forward.
A
C
Yeah,
let
me
repaint
the
leads
to
make
sure
to
get
this
pr
reviewed.
I
will
also
take
a
look.
A
Sure
I'm
really
curious,
there's
two
pieces
of
this-
that
I'm
keen
to
get
feedback
on
one
is
you
know,
should
we
do
it
at
all
and
then
the
second
one
is.
C
So
I
think
the
idea,
I
think
we
are
very
happy
with
the
idea
and
we're
in
support
of
it.
I
think
the
concern
just
was
what
victor
mentioned.
C
B
A
Yeah,
I'm
I
you
might
be
raising
a
good
point
there
anna,
like
if
that's
not
representing
sig
release,
and
I
I
know
that
weekly
meetings
aren't
necessarily
representing
a
sig
but
like
an
official
like
this
is
a
thing
where
actually
an
official
sig
position
would
be
useful.
I
think
to
us
really
because
we
need
that
buy-in.
I
just
don't
think
it's
sensible
for
sig
docs
to
put
the
effort
in
without
sig
release
being
convinced
that,
as
and
sig
release,
rather
than
the
release
team
for
docs
being
convinced.
It's
a
good
idea.
B
Absolutely
the
problem
is
that
that's
a
week
from
now.
Is
that
a
huge
issue,
or
should
we,
I
don't
know,
bring
people
on
slack
or
start
the
slack
thread
regarding
this.
A
This
I
mean,
I
might,
for
my
take
like
it'd,
be
nice
to
land
this
just
after
the
1.22
release,
but
this
is
the
time
of
of
in
the
cycle
when
sig
release
is
busy.
So
if
that
sick
doesn't
have
time
right
now
to
make
a
decision
and
to
give
feedback,
I
would
understand.
C
So
I
am
not
able
to
make
the
stick
release
meetings.
Is
anyone
else
able
to.
B
Yeah,
I
can,
I
can
bring
this
up
next.
It's
on
tuesday
yeah
it's
on
tuesday,
on
the
13th.
A
Someone
else
take
the
work
I've
done
in
that
pull
request,
and
if
someone
wants
to
open
their
own
pr,
that
has
a
different
tack
but
borrows
as
much
code
as
they
like,
like
I've
signed
a
cla,
it's
kubernetes
code
already
now,
if
you
like,
broadly
what
I've
done,
but
you
want
to
do
it
a
different
way
go
ahead,
like
I
don't
really
mind,
I
quite
like
how
I've
done
it,
but
I'm
also
open
to
see
someone
else's
approach
go
in
and-
and
you
can
do
it
completely
different-
you
can
use
jason,
you
can
use
tommel,
don't
go,
don't
go
too
mad,
but
you
know
if
someone
wants
to
do
a
different
thing
and
say
this
is
my
take
on
doing
it.
A
B
Yeah
I
had
one
thing
about
the
localization
stuff,
so
this
is
something
that
came
up
yesterday:
pull
request
localizations
for
dev122,
or
that
include
localizations
better
said,
and
this
is
not
something
that
I
knew
you
know-
apologies
if
I
missed
this,
I
don't
know,
I
don't
think
I've
seen
it
anywhere
so.
A
Yep
cool,
but
specifically,
if
there
is
a
particular
pr
or
issue
people
want
to
talk
about
I'd,
be
happy
to
cover
that
now.
D
Hey
tim
chris
metz
here
so
I
had
opened
that
issue
about
adding
some
diagrams
to
the
to
the
contribute
section.
As
part
of
my
adventure
into
the
squashing
commits
documentation.
I
just
you
know
was
looking
over
at
the
entire
section
and
I
really
thought
that
some
diagrams
might
be
helpful.
D
I
spoke
to
jim
about
this
and
and
he
thought
it
was
a
pretty
good
idea,
so
I
was
playing
around
with
mermaid
and
I
think
it's
been
suggested
that
we
use
that
use
those
capabilities
and
I
thought
maybe
I'd
start
to
draft
up
a
couple
of
proof
of
concepts.
Things
maybe
add
those
to
the
issue
and
maybe
get
sort
of
some
consensus
or
suggestions
before
opening
vr.
D
Yes,
yes,
and
I
think
it
would
present
a
more
friendly
or
inviting
presentation,
particularly
for
new
contributors,
who
may
not
be
able
to
delve
into
some
of
the
details
outlined
in
the
text
or
haven't
worked
with
that
kind
of
thing.
Before.
A
Oh,
it's
I've
misspelled
your
surname
there,
it's
a
wrong
letter.
Sorry
right
and
I
think
that's
other
chris
there's
too
many
chris
sorry,
it's
not
I
mean
I'm
all
for
it.
I
I
I
m
my
feedback
would
be
yes
what
what
would
a
play?
People
feel
about
this
concept
of
adding
diagrams,
and
would
anyone
like
to
help.
D
Yeah
I
mean:
if
people
have
some,
you
know
examples
of
mermaid
it.
It
seems
slightly
limited,
but
you
know
I
think
it's
sufficient
enough
that
we
could
put
together
something
that
again
would
outline
the
steps
and
to
find
some
of
the
terms
and
where
they
fit
into
the
whole.
You
know
a
pipe
pipeline
life
cycle.
C
A
C
It's
actually
really
funny
because
I
just
started
looking
at
this
tool
for
sick
release,
because
we
have
an
issue
for
visualizing
the
release
process
and
I
actually
created
two
mermaid
visual
graph
and
I
can
share
like
the
code
or
what
I
did
not
code.
It's
actually
text-based
so
like.
I
can
share
that
and
show
you
like
what
it
looks
like,
and
I
mean
I
like
the
tool,
I'm
actually
still
waiting
for
sig
release
to
get
back
to
me
also
on
whether
they
want
to
proceed
with
this
tool.
C
So
if
siddox
is
also
using
it-
and
I
actually
didn't
know
that
it
was
part
of
the
kubernetes
documentation
either,
but
I
think
yeah
I'm
happy
to
help
in
some
way.
I
guess.
D
Sure
that
would
be
great
anna,
so
I
thought
what
I
do
is
just
set
up
a
quick
google
docs
with
some
of
the
text
code
for
some
of
the
diagrams,
and
maybe
we
could
do
a
little
brainstorming
there
and
you
know,
try
and
group
our
efforts
and
maybe
try
and
have
a
consistent
application
of
these
of
this
tool
and
again
I
think
it
will
add
a
huge
amount
of
value.
I'm
a
big
time
diagrams
guy
and
gaiden.
D
Whatever
we
have
in
the
text
is
fantastic,
but
again
for
for
new
users,
even
you
know
six
existing
contributors.
They,
I
think,
they'll
find
they'll,
find
these
diagrams
helpful.
C
A
A
D
Yeah,
that
might
be
the
best
place
to
go
at
least
for
at
least
for
some
ideation.
If
you
will
on
some
of
these
diagrams.
A
Yeah,
if
you
want
to
find
an
example
of
a
page
that
uses,
I
always
think
of
the
ingress
page
right,
which
I
can
probably
share,
because
I
know
I
think
I
did
the
diagrams
for
it,
which
is
actually
one
of
our
more
popular
pages
on
the
website.
Generally,
let
me
visually
indicate
what
I'm
talking
about
you
are,
that
is
mermaid,
so
here
we
are.
If
I
look
at
the
source,
I'm
not
sure
how
this
renders,
but
well
mermaid
has
taken
it
away
from
me.
A
A
You
don't
have
to
use
the
kubernetes
colors
for
contributed
dots,
but
I
would
I
would
try
and
use
the
kubernetes
colors
because
just
matches
the
style
better
right
and
yeah,
you
can
use
as
many
as
you
like
and
any
page
that
has
a
mermaid
diagram
in
it
automatically
loads
the
javascript
to
turn
that
into
the
what
you're
seeing
rendered
here.
A
A
A
couple
of
reasons
you
might
do.
That
would
be.
A
You
know
that
the
rendering
is
inconsistent
between
browsers
or
you're
worried
that
the
rendering
would
be
inconsistent
between
browsers,
because
you've
got
a
very
complicated
diagram
and
you
might
say,
I'm
going
to
turn
that
mermaid
diagram
into
an
svg
and
then
I'm
going
to
commit
the
svg
and
I'll
just
somewhere
make
a
note
of
what
the
mermaid
source
was
in
case.
Anyone
needs
to
go
back
and
edit
it
and
the
the
other
reason
you
might
do.
A
That
is
because,
actually
you
want
to
edit
the
svg
somehow
you
want
to
do
it
all
in
mermaid
and
then
I
don't
know
add
the
kubernetes
logo.
That
kind
of
thing-
I
don't
think,
that's
relevant
really
here,
but
I
would
I've.
Since
we
talked
about
mermaid,
I
thought
I'd
mention
it.
C
No,
so
that's
a
really
good
point.
That's
one
of
the
questions
I
also
had
was
that
like
do
you
actually
export
and
save
the
text
that
was
used
to
generate
it
or
is
it
generating
on
the
page,
I
guess
and
so
for
the
ingress?
Do
you
know
tim
damn
diane
yeah.
A
D
Real
quick
so
in
the
source,
if
we're
using
an
svg
that
that
would
be
the
svc
svg
image
used
in
the
documentation,
would
we
put
the
mermaid
source
anywhere
so
that
down
the
road?
Maybe
if
someone
wants
to
open
a
pr
to
modify
it,
they
could
at
least
have
this
source.
A
Absolutely
so
svg
is
xml,
xml
does
comments,
so
you
could
put
a
comment
in
the
top
of
the
svg
or
you
could
put
the
comment
in
the
file
that
includes
you
know
in
the
so
in
the
page
that
references
the
svg,
you
could
put
it
there.
I
would
probably
put
the
comment
in
the
the
svg
file
so
that
it's
it's
as
obvious
as
you
can
make
it
all
right.
Now.
People
still
miss
that,
but
that's
what
I
do
trying
to
dust
off
some
of
my
svg
editing
tools.
A
Yeah
I
mean
like
just
to
be
clear.
I
would
edit
the
you
know
if
you're
exporting
an
svg
do
it
from
from
mermaid
and
then
export
to
svg,
and
then
normally
you
wouldn't
look
at
that.
You
just
treat
it
as
some
sort
of
graphics
file.
But
if
you're
adding
a
comment,
I
personally
would
use
vim,
but
you
know
use
it.
A
You
can
use
a
text
editor
to
take
xml
and
put
a
comment
in
there
right
because
behind
the
scenes,
it's
really
a
text
file-
and
this
is
what
the
moment
looks
like
there's
a
short
code.
So
that's
a
hugo
short
code
and
then
the
contents
of
the
short
code
are
mermaid
and
the
website
makes
you
know
the
website
layout.
Make
sure
that
that
renders
how
we
want
it
to.
A
There's
nothing
to
stop
us
changing
how
the
website
works,
to
have
this
render
during
static
site
generation
into
an
svg,
but
that
is
more
programming
than
anyone's
got
their
hands
dirty
at
doing
just
yet.
A
If
you
want
the
kubernetes
styles,
you'll
see
these
class
depths
here
you
can
use
those
to
get
the
you
know,
kubernetes,
blue
and
so
on.
A
I'm
not
hearing
anything,
I
see,
there's
a
person
I
think
who's
joined
the
call
ritu
panjuani.
Is
that
how
I
should
say
it.
A
Hey,
I'm
not
sure,
is
this:
your
first
time
you've
joined
a
sig
dogs,
weekly
meeting.
E
No,
no,
I
have
been
joining
a
like,
sometimes
yeah,
but.
A
A
F
Yes,
we're
done.
Hopefully
my
internet
won't
drop
out
from
under
me
as
it
did
last
week
when
I
went
to
discuss
this
yeah,
so
we
want
to
try
to
get
the
blog
meetings
going
again,
so
I
just
wanted
to
see
when
everyone
thinks
would
work
our
day
and
time.
F
So
the
is
that
the
previous
one
you're
typing
in
there
tim,
I
think
we're
gonna
have
one
in
about
35
minutes.
Okay,
good!
I
didn't
know
it
got
scheduled.
Okay
great,
so
I
guess
it
will
be
on
this
zoom
correct.
F
F
Channel
great
and
also
I
didn't
know
if
it
needed
to
get
added
to
a
calendar
or
anything
like
that,
so
others
know
to
look
it
up.
I
I
couldn't
find
where,
where
to
look
it
up
so.
A
I
so
I
don't
know,
I
don't
know
how
to
get
things
added
to
the
calendar.
I'm
sure
I
could
work
that
out.
So,
yes,
we
should
probably
add
this
to
the
calendar,
but
I
think
more
important
than
the
calendar
is
having
the
meeting.
So
I've
focused
on
that
bit.
F
Perfect
yeah,
I'm
glad
you
did
that
because
I
wasn't
I
I
knew
that
there
was
some
discrepancy
with
the
time
in
the
day.
So
so
glad
you
went
ahead
and
did
that.
Okay,
great.
A
So
does
anyone
want
to
feel
free
to
unmute
and
say
oh
I'll,
be
in
that
meeting
too
if
anyone's
interested?
A
Oh,
I
I
expect
I'll
come
I'll,
probably
join
shortly
cool,
so
nate
and
victor
yeah
good
to
see
you
there
yeah.
So
I
said
11
30,
pacific
time
in
the
announcement.
I
I
put
1930
utc,
but
I
was
wrong.
It
is
1830,
etc.
So,
just
in
case
you
look
at
the
utc
time
it
is
1830
utc,
11,
30,
pacific.
A
And
I'm
not
sure
if
it'll
be
every
other
tuesday
or
every
tuesday
or
something
I
would
prefer
to
be
not
every
week,
because
I
already
cover
up
plenty
of
time
for
kubernetes
and
it
is
after
after
work.
For
me,
that's
just
my
view.
A
Oh
yes,
so,
is.
B
There,
a
like
a
process
for
this,
where
we
don't
merge
is.
Is
it
something
like
clearly
defined
where
we
don't
merge,
localization
prs
in
the
dev
branch,
but
rather
we
do
it
when
when
the
release
is
done
or
we
don't
do
it
whatsoever
or
what
what
can
I,
how
should
I
act
moving
forward
because
it's
something
I
have
no
idea
of
and
it
didn't
even
cross
my
mind.
A
The
challenge
that
I
think
I
see
is
that
let's
say
we
merge
in
a
russian
a
ukrainian
and
a
korean
change,
localizing
text
that
has
been
proposed
for
the
next
release
and
once
that
happens,
two
of
those
localizations
change
the
main
branch
and
they
they
update
their
documentation
on
the
main
branch
because
they're
localizing
and
keeping
things
current,
there's
now
a
merge
conflict.
But
here's
the
problem
to
resolve
that
merge
conflict.
You
might
need
to
speak
ukrainian,
or
did
I
say
russian
and
korean.
A
B
Yeah,
I
see
the
problem,
so
my
question
is:
is
this
communicated
to
to
where
well?
This
should
be
communicated,
probably
throughout
the
project,
for
people
to
not
open
localizations
localization
prs
against
the
branch
right.
A
E
Yeah,
I
don't
recall
anyone
trying
to
do
in
last
release.
Actually
you
know
what
there
might
have
been
a
few,
but
I
think
was
just
on
the
feature:
gate
side
and
the
person
that
was
on
the
docs
release
team.
B
So
now
no,
this
explains
the
lack
of
any
kind
of
you
know
documentation
because
this
didn't
happen
before,
but
I
I
think
I
will
add
it
to
as
a
note
to
to
the
docs
lead
shadow,
whatever
documentation
that
we
have.
A
Thank
you
for
pointing
that
out,
as
people
who
have
been
involved
with
release
cycles
and
kubernetes
releases
will
will
know
already
there's
a
crunch.
It's
not
like
there's
a
constant
flow
of
prs.
They
come
in
more
at
the
end
of
the
cycle
and
merge
conflicts
are
probably
more
likely.
A
You
know
as
we
near
the
release.
Just
when
you
don't
want
them
is
when
they
turn
up
so
yeah.
I
think
it's
kind
of
a
theoretical
risk,
but
I
think
it's
also
like
a
believable
risk.
A
A
Okay,
I'm
going
to
wrap
things
up
there
thanks
folks
have
a
great
rest
of
your
week.
See
some
of
you
in
the
vlog
call
cheers
bye-bye.