►
From YouTube: SIG Docs meeting for 20220111
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
Perfect
now
for
those
who
don't
have
access
to
the
agenda,
I'm
just
popping
it
here
in
nope
I
was
just
sending
that
to
tim,
privately
and
now
I'll
just
do
that
again,
sending
it
to
everyone
there
in
the
chat
for
the
agenda
there
nate.
I
hope
it's
okay
with
you
that
I've
sort
of
added
your
name
just
to
kind
of,
say,
hi
from
the
release,
docs
team
for
1.24,
but
yeah
we'll
now
just
get
started
so,
firstly
hi
everyone,
I'm
natalie!
A
A
So
myself
and
tim
are
steering
the
ship
today
this
afternoon
this
evening,
wherever
you
may
be
around
the
world,
I'd
love
to
get
started
with
the
meeting
to
actually
see
if
we've
got
any
new
contributors
who
are
joining
us
today,
or
maybe
new
would-be
contributors.
That
would
like
to
say
hi
and
introduce
themselves.
B
C
Sure,
hey,
I
go.
First,
hey,
hey
everyone,
I'm
nash
from
india,
it's
actually
pretty
late
over
here
and
yeah.
This
is
actually
my
first
time
attending
this
meeting,
but
I've
contributed
to
the
docs
during
the
previous
release
cycle,
but
this,
my
first
time
being
here
in
this
meeting
so
looking
forward
to
it
yeah
I'm
looking
forward
to
learning
how
the
entire
process
goes
about.
A
A
We
meet
every
every
two
weeks
at
around
this
time
and
of
course,
if
you
can't
make
any
of
the
meetings
we
try
to
upload
these
meetings
to
youtube
as
well,
so
you
can
watch
them
later
on
and
you
can
also
access
the
agenda
too,
if
you're
part
of
the
google
group
as
well
that
we've
just
posted
there
in
the
chat.
A
Oh
yes,
be
nice
to
folks
for
sure
anyone
else,
who's,
a
new
contributor
or
first
time
at
the
meeting,
would
be
a
contributor
that
wants
to
say
hi.
A
All
right
going
once
going
twice
all
right,
we'll
we'll
we'll
get
on
with
the
rest
of
the
agenda.
If
anyone
joins
a
bit
later
or
you
notice
a
few
folks
that
maybe
want
to
say
something
feel
free
to
just
say,
hi
and
chat,
we're
a
friendly
bunch,
we
we
don't
bite
getting
on
to
the
next
agenda
item.
I
want
to
just
do
a
couple
of
reminders
here,
especially
for
some
of
the
new
folks
or
folks
newer
to
our
processes.
We
have
this
great.
A
We
have
a
great
example
of
one
of
the
seed
box
processes
that
we
have
here
called
pr
wrangling
where
we
assign
someone
each
week
to
kind
of
get
into
our
larger
selection
of
prs,
to
be
able
to
try
and
help
move
them
along
and
get
some
progress
going
on
some
of
the
work
in
sig
docs.
And
so
we
have
an
agenda
or,
should
I
say,
a
schedule
of
pr
wranglers
for
the
year
that
brad
has
lovingly
put
together.
A
So
I
don't
see
him
on
the
meeting,
but
if
you're
watching
the
recording
brad.
Thank
you
so
much,
and
I
do
want
to
say
that
actually,
this
week's
pr
wrangler
is
brad.
But
I
do
believe
the
shadow
for
this
week
is
whitney
who's
on
the
call
at
the
moment,
and
hopefully
whitney
you
get
a
lot
out
of
that
for
for
this
week
as
well.
For
the
for
the
wrangling
too,
and
I
do
want
to
mention
for
folks
who
are
interested
in
pr
wrangling.
A
That
is
that's
that's
around
where
you
get
to
kind
of
check
out
what
pr
wrangling
is
connect
with
the
current
pr
wrangler
of
the
week
or
whatever
week
that
you
wish
to
sign
up
on
thanks
chris
for
linking
that
there
in
the
chat-
and
this
is
something
that
could
be
a
really
really
great
way
for
you
to
just
learn
about
what
we're
doing
in
sig,
docs
understanding
how
to
even
kind
of
go
about
pr
wrangling
or
just
general
pr's
overall
and
a
great
way
to
learn
a
bit
more
and
and
meet
a
lot
of
folks
in
the
community.
A
So
for
anyone,
who's
interested
on
the
pr
wrangling
front
feel
free
to
definitely
have
a
look
at
that
link
that
chris
has
just
posted
there
in
the
chat
and
you
can
reach
out
to
brad
brad
topple
directly
on
slack
and
he'll,
definitely
be
able
to
help
you
and
add
you
to
the
schedule
as
you
wish.
A
So
thanks
whitney
well
done
for
signing
up,
and
maybe
maybe,
if
you're
up
for
it
next
meeting,
you
could
tell
us
how
how
your
experience
was,
and
we
can
kind
of
get
some
more
shadows
signed
up
awesome
for
next
week's
wrangler.
We've
got
divyo
who's.
One
of
our
co-chairs,
she'll
be
she'll,
be
on
the
schedule
for
next
week.
So
if
anyone
is
interested
in
wrangling
there,
too
you'll
be
able
to
shadow
divia
for
next
week.
A
All
right
now
going
on
to
the
rest
of
our
agenda.
We
are,
I
would
love
to
invite
nate.
We
are
going
to
be
talking
a
little
bit
about
1.24
in
terms
of
the
release
docs
team
nate
over
to
you.
D
Hello,
everyone.
Thank
you
so
much.
I
would
also
like
to
say
hello
to
james
lavrak,
who
is
our
release
lead
overall,
but
just
a
quick
update
on
the
status
of
release,
one
two:
four
we
are
just
just
starting
out:
we've
just
invited
our
shadows
to
to
join
us.
We
have
chris.
D
Forgive
me
if
I've
pronounced
your
name,
I
don't
think
you're
actually
on
the
call.
This
is
the
first
time
I've.
I've
said
some
of
these
things
out
loud
as
well,
as
victor,
have
all
decided
to
join
us
and
I'm
very
excited
to
work
with
everyone,
we're
just
getting
the
announcements
sheet
up
and
running,
and
I've
put
together
the
integration
branch.
So
that's
currently
healthy.
D
It
can
almost
not
help,
but
to
be
so,
we
are
literally
just
right
at
the
beginning
of
this
thing
and
myself,
or
one
of
the
shadows
will
be
at
each
of
these
meetings-
sort
of
moving
forward
throughout
the
process.
Just
to
keep
you
all
sort
of
informed
as
to
what's
going
on
if
you've
got
any
questions,
feel
free
to
to
ask
myself
james
or
any
of
the
shadows,
we're
happy
to
we're
happy
to
help
them
we're
happy
to
chat
about
it.
D
Oh,
we
should
sorry
a
less
less
talk
about
dr
next,
but
that's
gonna
be
the
big
thing.
I
think.
A
Yes,
topic
de
jour,
I
think
for
sure
before
we
go
on
to
that,
actually
does
anyone
have
any
questions
for
nate
or
for
james
around
the
release,
docs
team
or
just
the
1.24
release
schedule
in
general.
E
I
did
just
want
to
say
hello
really,
so
I'm
actually
going
right.
As
nate
said,
my
name
is
james.
I'm
the
release
lead
424,
I'm
actually
going
around
every
sig
and
kind
of
saying
hello
and
asking
if
there's
anything
that
we
in
the
release
team
could
do.
Obviously,
doc's
is
a
little
bit
more
connected
anyway.
So
nate's,
a
very
good
point
of
contact
for
you
and
I've
got
every
confidence.
E
A
Thanks
james
thanks
for
thanks
for
coming
along,
I
guess
you're,
I
guess
you're
going
to
be
on
slack
quite
a
lot
in
order
to
answer
a
lot
of
questions
so
yeah
for
sure,
thanks.
So
much
for
coming
to
introduce
yourself
you're
welcome
at
obviously
meetings
anytime
for
sure.
We're
also
awesome
to
have
you
great,
just
double
checking
if
there's
any
more
questions
around
really
stocks
team
in
general
or
the
release
schedule.
F
So,
for
those
who
are
not
aware
in
1.24,
we
are
finally
removing
docker
shim.
We
deprecated
it
about
three
releases
ago,
and
that
means
that
we
have
to
remove
it
for
the
docks
from
the
docks,
which
is
everybody's
favorite
task.
As
technical
writers,
we
spent
the
latter
the
tail
end
of
last
year
doing
most
of
the
checking
through
the
docs
to
see
where
we
actually
need
to
remove
things.
F
So,
as
this
release
cycle
goes
forward,
I
will
slowly
be
piecemealing
out
good
first
issues
and
other
things
that
if
y'all
could
help
and
pick
up
and
do
some
writing
would
be
super
helpful
for
those
of
you
who
don't
know
to
claim
an
issue,
you
have
to
leave
a
comment
that
says
slash
a
sign
in
the
issue.
I
think
you
have
to
also
tag
yourself.
Your
github
handle
prow
and
I
never
get
along.
So
don't
quote
me
on
that.
F
F
F
The
second
is
a
a
bit
of
a
mixed
bag
from
shannon
who
was
not
on
the
call
today,
but
did
great
work
in
this
checking.
It's
a
lot
of
kind
of
smaller
mentions
of
docker
here
there
and
everywhere
that
just
need
to
be
picked
up
and
checked,
but
it
is
fairly
straightforward
to
execute
on
the
next
two
issues:
three,
oh
nine,
five
one
and
three,
four
nine
five
two
are
a
touch
more
complicated
because
they
more
or
less
involve
complete
rewrites
30951
is
far
more
complicated.
F
So
this,
basically
the
entire
con
concept
page
on
images
needs
rewriting
at
this
point,
because
the
the
style
of
the
writing
essentially
contrasts
it
to
docker
at
like
every
step,
and
at
this
point
I
think
we
want
to
just
generally
use
a
more
generic
container.
F
So
it's
not
hard,
you
don't
necessarily
need
to
be
technical
to
do
that,
but
you
do
need
to
have
a
very
under
solid
understanding
of
both
kubernetes
and
container
images
to
approach
that
30952
is
actually
a
lot
easier.
It's
a
shorter
topic,
there's
only
a
couple
of
mentions
of
docker,
which
I
honestly
think
you
could
just
generically
replace
with
my
container
in
some
cases,
but
it
is
also
a
conceptual
topic.
Yes,
natalie
you've
got
your
hand
up.
A
I
do
you,
you
noted
some
pretty
pretty
easy
instructions
earlier
around
how
to
claim
an
issue.
I
just
want
to
double
check
for
those
who
might
be
new
on.
The
call
is
that
are
these
instructions
also
in
the
issues
themselves,
so
that
people
know
what
they
need
to
do
or
written
somewhere?
No
they're
not,
and
I
apologize
no,
it's
okay.
It
could
maybe
be
something
that
we
could
do
in
in
in
some
of
the
slack
channels,
as
well
as
like
a
maybe
a
reminder
for
folks.
F
F
Aside
from
that,
by
the
way
I
have
noticed
a
few
people
in
doing
reviews
around
dockers
himself
have
been
tagging
me
specifically
for
the
approve
you
do
not
actually
need
to
do
that.
I
do
not
actually
need
to
be
the
approver.
Anybody
who
is
a
sig
docs
approver
can
make
that
call,
and
because
these
are
technical
changes,
I
actually
believe
it
is
who's
actually
responsible
for
this
removal.
It's
either
signed
or
cigar.
It's.
B
B
No
to
the
people
who
will
review
those
pages,
celeste
sick
architecture
will
have
a
have
a
role
in
it
as
well,
but
no
to
the
people
to
ask
if
you're,
okay.
F
Whoever
is
whoever's
wrangling
that
way
they
aren't
any
different
than
any
other
pr
for
the
most
part.
That
did
give
me
one.
I
did
have
one
question
around
that
which
is:
do
we
want
to
merge
these
against
the
main
branch
or
1.24,
but
correct
me
if
I'm
wrong
tim?
I
actually
don't
see
a
reason
not
to
merge
these
against
me
and
it
might
keep
the
1.24
branch
a
little
cleaner.
B
So
there's
a
couple
things:
I've
got
I'll
come
back
to
your
question,
whitney
so
celeste
question
about
what
branch
to
use,
if
you're,
not
sure,
if
you're
on
this
colony,
like
you're,
not
sure
what
branch
to
target
go
for
maine,
because
that's
the
easy
way.
If,
if
we're
giving
you
a
good
first
issue,
we
don't
want
you
to
have
to
think
about
what
branch
and
think.
Oh
my
gosh,
I've
got
an
extra
question.
It's
fine
target
main.
B
If
you
are
a
more
advanced
contributor
and
you
understand
about
documenting
for
a
future
release,
you
might
want
to
write
your
documentation
change
in
a
way
that
makes
sense
only
after
the
next
release,
and
sometimes
that
will
be
the
case.
So
it's
fine
for
people
who
are
advanced
contributors
to
rely
on
the
nuances
they
understand.
But
if
you
don't
then
go
for
maine
is
my
advice.
B
I
think
that's
good
advice
and
then
whitney
you
had
a
question
about.
You
know
if
you
are
the
pr
angler
of
the
week.
What
do
you
do
when
a
pr
comes
in
and
it's
about
the
docker
shim
removal?
B
This
is
on
our
website,
though,
like
if
you
go
and
look
on
the
the
contributor
guide,
there
is
a
place
on
it.
B
What
you
would
do
is
that,
if
you're
not
sure
about
a
technical
detail
of
kubernetes,
there
are
special
interest
groups,
so
node
special
interest
group
security,
special
interest
group,
autoscaling
special
interest
group
as
an
example-
and
you
would
say:
okay,
I
know
kubernetes
well
enough
to
you
know,
approve
changes
and
so
on
I
know
technical
writing
will
have
to
do
that,
but
I
need
some
help
and
you
would
say
right.
I
will
find
someone
from
the
auto
scaling
group.
B
First
thing
you
can
do
is
tag
the
pr
with
the
relevant
sig,
so
slash
six
space
node
and
put
that
command
in,
but
then
you
may
have
to
nag
a
bit
as
the
pr
wrangler
as
an
approver.
You
may
then
have
to
go
and
chase
up
that
sig
to
say.
Okay,
we
need
you
to
do
a
technical
review,
and
so
you
can
send
a
message
on
github,
saying
generally
we'd
like
a
review
here
and
then,
if
you
still
haven't
got
that
you
know,
people
have
other
things
in
their
in
their
lives.
B
A
lot
of
contributors
are
volunteers.
That's
fine,
you'll,
dive
onto
slack
and
you'll
go
and
find
that
that
six
slack
channel
and
you'll
say
I
need
a
review
here.
I
need
technical
review
and
if
that
doesn't
work,
two
options
ask
asking
the
pr
reviews
channel,
which
is
kind
of
like
pulling
the
big
and
on
chord
in
a
factory
and
highlighting
this
is
like
for
the
entire
project.
The
pr
reviews
channel
is
saying
everyone.
B
H
Yeah,
I
I
mean
tim-
I'm
actually
have
a
shadow
this
week
and
this
is
what
I've
been
teaching.
I
actually
will
go
to
this.
You
know
go
find
the
sig
page
see
who
the
leads
are
and
go
right
to
a
lead.
I
feel
like
instead
of
trying
to
broadcast
and
nobody
gets
responsibility.
If
I
pick
a
victim,
then
then
usually
they're,
pretty
responsive.
F
I
I
usually
prefer
to
go
for
the
channel
myself.
I
will
highlight
that,
specifically
for
docker
shim.
This
is
these,
whether
or
not
no
matter
what
brand
you
put
these
on.
These
are
a
part
of
the
1.24
release
and
they
are
ignoring
their
release
responsibilities
if
they
ignore
you
and
do
not
feel
bad
about
shaming
people
for
that,
but
just
in
general,
as
a
technical
writer
like
chasing
down,
people
for
review,
is
kind
of
a
part
of
the
job
and.
F
It's
a
part
of
their
responsibility
to
the
project
and
that's
what
it
boils
down
to
excellent.
A
I
Yeah,
I
would
just
add
one
more
thing:
brad
was
an
excellent
person
to
to
shadow,
so
you'll
learn
a
lot
from
him
very
helpful
and
one
other
comment
on
on
finding
people
to
review
things.
If
you
find
someone
who's
really
helpful
and
really
nice
write
their
name
down
and
save
them
for
later
when
you're.
In
a
pinch,
that's
a
really
good
thing
to
do:
send
them
cookies,
whatever
you
have
to
do
and
and
they
will
be
helpful
when
you
really
need
them
later.
So
I
would.
I
would
just
pass
that
on.
A
Yeah,
I
think
yeah
I
agree
gift.
Buyer
food
definitely
helps
with
a
lot
of
reviewers.
Definitely
tim
we'd
love
to
hand
over
to
you
now,
but
I'm
not
sure
if
we
got
to
your
question
at
last,
amongst
others.
A
C
Yeah
mentioned
earlier
that
there
was
a
release
process
for
a
particular
branch
that
we're
supposed
to
push
the
pr
against.
So
is
there
a
place
where
that
is
documented,
where
I
can
learn
more
about
it.
So,
up
until
now,
I've
been
right
making
all
the
peers
to
the
main
branch.
So
I
just
want
to
understand
the
process
better,
so
I
make
it
to
the
right
branch.
C
A
Great
thanks
so
much
tim
chris.
I
can
see
that
you've
got
your
hand
up.
I
did
you
have
another
question
that
you'd
like
to
ask
great.
Okay,
no
worries,
then
any
more
questions
from
anyone
on
the
call
around
the
docker
shim
work.
B
Tim
I'll
take
it
yes,
so
I
wanted
to
talk
about
what
I
think
the
level
is
for
the
two
issues
that
celeste
called
out
is
more
difficult,
and
what
I
would
say
is
these
are
easier
you,
you
don't
need
to
be
at
a
level
to
pass
the
ckad
exam,
but
what
you
can
do
if
you're
worried
about
like
is
this
for
me.
B
B
F
They
need
like
you,
need
to
be
comfortable
enough
with
the
idea
of
a
container
and
an
image
to
be
able
to
like
smoosh
those
two
concepts
together.
Honestly
container
images
are
such
a
foundational
part
of
the
kubernetes
and
cloud
native
sphere
that
you
could
potentially
google
more
information
about
this
to
aid
in
the
rewriting.
F
What
I
will
say
about
these
ones
is
because
they
are
conceptual
again.
They
involve
less
coding,
and
I
agree,
I
think,
they'd
be
a
great
study
topic
for
revision.
They
are
the
kind
of
change
which
a
lot
of
people
will
be
able
to
review
and
comment
on
as
well,
so
you're
not
going
to
go
too
far
off
base,
and
you
should
definitely
give
it
a
shot.
If
you're
curious.
A
A
Alrighty
then,
with
that
being
the
case,
we're
going
to
go
into
our
next
agenda
item
and
the
the
next
somewhat
speaker,
yes,
has
joined
somewhat
just
in
time.
The
next
gen
item
that
we've
got
here
is
some
of
the
lift
updates
that
are
taking
place
here
with
sig
docs
and
I'd
like
to
say
a
big
hello
to
jim.
J
Perfect,
I
appreciate
the
tea
off
and
I
you
know
I
apologize.
I
had
some
limited
availability,
but
it
worked
out
perfectly.
So
that's
awesome,
so
yeah
just
wanted
to
raise
awareness.
There
is
an
announcement,
the
links
in
the
agenda
there,
we've
kind
of
been
working
out
in
the
open
for
the
past
12
plus
weeks
or
so
with
the
various
individuals
with
the
mentoring
group
and
ultimately,
what
we're
planning
on
doing
is
building
a
larger
documentation
team
to
provide
better
support
for
sig
docs
as
a
whole.
J
So,
ultimately,
this
proposal
is
to
build
out
a
larger
sig
docs
team,
to
support
each
other
and
to
build
out
a
more
of
a
support
system
for
sig,
docs
and
documentation
as
a
whole
and
really
the
reason.
We're
raising
awareness
to
this
and
the
reason
we're
making
this
change
beyond
just
supporting
each
other
is
that
you
don't
want
to
make
these
large
overarching
changes
kind
of
in
a
bubble.
So
we
want
to
be
very
transparent
around.
Why
we're
doing
it?
J
What
we're
doing
and
how
we're
going
to
accomplish
this
and
making
sure
there's
general
alignment
in
the
community
so
like
one
of
the
best
parts
about
kubernetes,
and
one
of
the
reasons
why
I
stuck
around
is
it's
such
a
welcoming
and
inclusive
community,
and
so
I
really
encourage
folks
to
check
out
the
announcement
that
I
sent
out
around
some
of
the
changes
coming
in
the
pipelines.
J
And
you
know
I,
I
hope,
there's
no
objections,
but
really
that's
the
values
of
open
source
and
that's
the
value
of
an
open
source
community.
And
so,
if
you
see
anything
there
that
you
want
to
object
with
that
you're
complete
you're
you're
in
the
complete
right
or
the
ability
to
do
so.
If
you
feel
like,
I
feel
like
doing
so
and
short
of
that,
I'm
also
announcing
that
I'm
stepping
down
at
the
end
of
the
first
quarter
here
as
we
assist
with
these
transitions.
J
Assuming
things
go
smoothly,
and
so
I
just
want
to
say
a
big
thank
you
to
all
of
you
all
that
have
been
around
or
anyone
watching
the
video
or
you
know
from
the
beginning
to
to
here.
It
has
been
an
incredible
experience,
I'm
not
going
anywhere.
I
plan
on
sticking
around
as
an
individual
contributor
and
ultimately,
I
hope
to
come
into
a
leadership
role
down
the
road
at
some
point,
maybe
as
a
non-volunteer
at
some
point.
J
So,
who
knows
what
the
future
holds,
but
at
the
very
least
I
just
wanted
to
say
a
big
thank
you
and
you
know
I
got
to
give
a
lot
of
credit
to
the
sig
docs
community
for
being
such
an
awesome
and
welcoming
place,
and
I
hope
that
these
changes
are
going
to
continue
to
make
it
welcoming
and
awesome
and
they're
all
for
for
the
better
any
questions
on
that.
A
Definitely
I
think
chris
you
mentioned
that
brad
is
a
great
person
to
shadow
around
pi
wrangling.
I
would
say
jim
is
also
really
awesome
to
shadow
around
wrangling
having
shadowed
him
before.
So
maybe
folks
can
get
on
the
the
shadow
roster
when
he's
around
to
also
be
able
to
work
alongside
him.
It's
been
a
really
real
honor
and
a
privilege,
jim.
H
A
I
think
the
other
things
that
we'd
like
to
mention
around
those
leadership
changes
is
that
we've
also
got
this
really
amazing
work
coming
up
around
localization
and
it's
great
that
brad's
on
the
call
too.
As
he's
one
of
the
localization
leads,
as
is
abigail
who's,
also
on
the
call
our
other
localization
lead
that
we're
spinning
up
in
terms
of
a
project
and
that's
going
to
be
something.
That's
super
exciting
too,
for
the
seeker
coming
up
as
well.
A
All
righty
with
that
being
the
case,
I
want
to
now
open
the
floor
because
we've
reached
the
end
of
our
agenda
technically,
just
to
see
if
anyone's
got
anything
that
they
wanted
to
bring
up.
Maybe
any
issues
or
prs
you'd
like
to
look
at
or
any
other
discussion
topics
that
you
would
like
to
add
to
the
session
for
today.
A
Going
once
going
twice
well,
I
have
a
feeling
that
might
be
it,
but
at
the
same
time,
jim,
I
know
that
you'll
be
still
around
for
quite
a
while
in
term
when
I
say
quite
a
while
about
a
month
or
so
in
the
in
the
transition
with
sig
doc,
so
so
focus
on
the
call
you'll
still
be
able
to
see
jim
around
here
and
there
again,
it's
been
a
huge
honor
to
be
able
to
work
alongside
you,
and
I
can
totally
understand
that
you
know
taking
a
break.
A
A
I
should
say
2022
if
you've
got
any
other
questions
or
any
other
follow-up
that
you'd
like
to
continue
with,
but
please
feel
free
to
head
over
to
slack
sig
docs
and
the
kubernetes
slack
we're
over
there
to
be
able
to
answer
some
questions
and
thanks
again
for
everyone
joining
in
all
the
newcomers
who
joined
today
as
well.
Thanks
so
much
and
we'll
see
you
in
a
couple
of
weeks.