►
From YouTube: K8s SIG Docs Meeting for 20200331
Description
For more info see https://git.k8s.io/community/sig-docs
A
All
right
we're
live.
Welcome
everybody!
Sorry
for
a
little
bit
of
a
chaotic
start
here.
Welcome
to
the
sig
Doc's
weekly
meeting.
My
name
is
Jim
angel
I
will
be
your
host
thanks
to
Tim's
passing
the
baton.
Today
is
March
31st
and
it
is
Tuesday
at
10:30.
Pacific
I'll
send
a
link
to
the
agenda
in
chat.
If
you
all
haven't
already
grabbed
it,
I'll
start
off.
Is
there
any
new
contributors
joining
in
this
call
for
the
first
time
that
would
care
to
introduce
themselves.
A
Let's,
like
we
have
a
Colin
and
I,
don't
recognize
Davi
Garcia,
but
doesn't
mean
that
y'all
are
new
if
y'all
want
to
introduce
yourselves
I,
see
Davey
just
put
in
chat,
they're,
just
updated,
fedora
2:30
to
beta
and
the
mic
stops
working.
So
it's
gonna
be
text
only
that
is
rough.
Well
welcome.
Hopefully
your
mic
troubles
get
solved
and
I'm
gonna.
Add
you
here
to
the
new
folks
joining
us.
A
Alright,
so
moving
on
to
updates
for
reminders,
this
week's
PR
Wrangler
is
a
bunch
of
question
marks.
We
have
had
some
woes
with
our
PR
Wrangler
schedule
and
we're
looking
for
some
folks
to
fill
in,
so
I
did
send
out
a
message
on
sig
duck's
maintainer
for
a
lot
of
our
owners
and
approvers
usually
reside.
D
A
Fix
the
format
here
so
you're
not
highlighted
perfect.
Thank
you
and
then
next
week
is
Peters
out
and
I
reached
out
to
Peter
to
see
what
his
availability
is
right.
Now,
it's
currently
unknown,
but
I'm
putting
that
up
as
tentative
that
we
might
need
someone
for
next
week
as
well.
We'll
get
this
straightened
out
here
and
we'll
go
from
there
and
so
moving
on
to
the
agenda
in
Docs
release,
118
was
released.
A
Whoo,
it
was
released
on
March
25th
last
week
is
the
lated
day,
but
nevertheless
the
the
docks
and
the
blog
all
landed
very
healthily
I
think
that
there's
still
maybe
a
little
bit
of
cleanup
work,
but
for
the
most
part
the
overall
release
process
is
complete.
So
congratulations
there
and
many
things
have
beneath
and
Tim
and
Karen
for
helping
that
release
go
very
successfully.
B
What
you
got
for
us
so
I
did
what
Zack
recommended
kind
of
create
a
dumping
ground
in
an
issue.
I
pasted
it
in
the
chat
just
to
you
know,
place
all
of
the
historical
blah
blah
stuff
in
there.
So
that's
there
and
I've
gotten
a
little
bit
of
traction
on
it
from
someone
in
the
community
who
thought
it
was
interesting
provided
feedback
which
was
actually
really
really
good.
So
I
clicked
per
his
comments.
I
made
some
changes
still
very
early
stages.
I
want
to
say
it's.
B
It's
still
in
draft,
but
I
do
have
the
an
example.
Kubernetes
architecture
with
some
newer
icons
and
I
do
have
kubernetes
diagram
icons.
There
I
built
them
myself,
just
through
raw
google,
draw
trying
to
emulate.
What's
in
sto
diagram
guideline,
which
is
far
more
expansive,
obviously
so,
just
looking
for
more
feedback,
maybe
even
some
help.
I
can
give
some
edit
rights
to
folks
who
want
to
jump
in
and
make
some
tweaks,
but
still
early
draft.
At
this
point,
that's
where
I'm
at.
A
Awesome
yeah
I'll
check
that
out
and
to
provide
some
feedback
where
I
can
I
personally
haven't
checked
out
that
issue,
so
I
don't
want
to
speak
to
without
being
a
little
warm,
so
worries
appreciate
your
work
on
that
and
I
did
update
our
note,
saying
that
you're
looking
for
more
feedback
help
and
edits.
If
any
folks
want
to
jump
in
there
cool
moving
on
to
any
Pierre's
needing
review
or
special
attention
or
anything
going
on
in
the
greater
case,
slash
website
world.
A
A
E
So
I
like
to
make
a
call
for
any
volunteers.
Every
few
weeks
here,
the
kubernetes
blog
lives
as
a
sub
project
under
sigdoc.
So
we
have
a
separate
group
of
reviewers
and
approvers
there
as
well,
who
review
all
of
the
incoming
blog
posts
that
we
have.
So
we
have
our
bi-weekly
meeting
today
at
11:30
Pacific
right
after
this.
So
if
anybody's
interested
in
getting
involved,
that's
a
great
place
to
to
check
out.
A
So
the
next
item
on
our
agenda
that
I
wanted
to
bring
to
everyone's
attention
here
is
the
merge
strategy
and
I'm
gonna,
be
beating
this
drum
pretty
heavily
here
over
the
next
release
cycle,
with
the
goal
of
solving
some
of
these
problems
in
the
119
release.
So
last
one
we
talked
about
this
Celeste
volunteer
to
create
some
content
for
review
on
how
to
squash
commits
I
guess
before
moving
forward
Celeste.
You
wanna
speak
to
that
yeah.
F
I
was
gonna,
say,
I
haven't
started
on
that
and
the
reason
I
haven't
started
is
I
realized.
I
didn't
ask
a
key
question
last
time,
which
is
who
is
this
document?
Who
is
this
merge
squashing
documentation
intended
for?
Like
am
I,
as
an
individual
contributor
responsible
for
squashing,
my
own
commits,
or
is
that
something
that
the
approver
needs
to
take
care
of
before
something
is
merged
in
targeted
yeah.
A
F
A
F
So
here's
here's
another
follow-up
question
for
you.
Then
our
documentation
is
currently
kind
of
divided
into
two
paths
you
could
possibly
take.
One
is
I
really
don't
know
anything
about
get
I'm
gonna
use,
github
UI
to
make
a
change,
and
the
other
is
make
a
fork
clone
the
fork
locally.
Do
your
changes?
Do
the
whole
get
process.
F
F
A
A
That's
kind
of
like
a
break
glass
option
that
I
don't
think
we
want
to
make
that
a
standard,
but
we
also
don't
want
to
not
merge
the
PR,
because
folks
don't
have
the
technical
know-how
to
squash
the
PRS.
So
that
would
be
a
solution
that
we
would
involve.
Someone
has
write
access
to
apply
a
label
to
squash
them.
Okay,.
F
F
A
A
A
Appreciate
that
and
then
the
one
thing
I
did
want
to
add
on
that
PR
is
that
stephen
augustus
as
part
of
the
sig
release
engineering,
folks
that
we
meet
with
mention
that
he
would
like
to
be
copied
in
on
the
PR
when
it
comes
in
just
for
their
general
review.
The
documentation
on
squashing
is
really
poor
today,
so
their
recommendation
was
to
put
the
documentation
and
the
contributors
guide
and
then
linked
from
the
kubernetes
website
to
the
contributors.
Guy.
F
A
F
F
A
B
Cool,
thank
you.
I
got
a
question
on
that.
So,
when
you
put
together,
let's
say
fast
forward
in
the
future,
and
you
have
this
documentation
on
squash
and
PRS,
is
there
like
a
one-stop
place
to
get
like
a
full
stack
of
everything?
So
this
is
like
setting
up
your
environment
and
getting
going
with
get
doing
the
first
PR
and
then
maybe
moving
on
to
more
intermediate
steps
which
is
squashing
PRS?
Is
there
like
a
like
I'm
starting
from
scratch?
B
I
want
to
get
through
the
basics,
maybe
a
little
bit
of
the
intermediate
stuff
and
that's.
It
is
right.
Now
the
only
thing
I
see
is
Gwen's
a
Seattle
YouTube
thing
which
is
like
you
know,
18
hours
of
in-depth
goodness,
but
I'm
just
wondering
it's
like
there's
a
dummy's
guide
for
CLI
for
it
for
for
the
just
the
nuts
and
bolts
so.
F
That's
a
part
of
another
really
big
PR
that
I've
been
working
on
for
everyday.
It
was
going,
but
it's
also
a
really
it's
a
dicey
issue,
because
we
can't
just
like
outright
replicate,
github
documentation
or
like
how
to
use
git
like
that's
we're,
not
the
place,
but
we
do
have
to
provide
something.
So
it's
kind
of
a
delicate
balance.
It's
never
gonna
be
like
a
one-stop
shop
because
I
don't
think
that's
humanly
possible
with
get
like,
unfortunately,
got
you,
okay,.
B
A
B
Was
just
thinking
for
sink
docks
like
what
is
the
version
of
its
me
Tim
and
Celeste,
and
I've
got
a
blank
laptop
and
and
they're
showing
you
how
to
set
up
my
laptop
and
set
up
the
environment
to
do
my
first
PR
and
then,
if,
if
I
need
to
squash
a
PR?
What
are
those
commands
like
that
in
a
formal
kind
of
you
know
coffee
shop
experience?
Is
there
like
a
text
version
of
what
that
would
be
like
if
people
were
just
doing
some
knowledge
sharing?
Do
you
get
what
I'm
saying
not
like
hey
you're?
B
A
Yeah
I,
like
the
idea,
a
lot
I
think
this
might
be
something
that
would
be
great
to
talk
about
in
our
quarterly
planning,
which
I'll
mention
later,
but
I
I
see
a
value
and
I
see
some
challenges
also
with
it.
So
I
think
that
you
know
without
going
through
and
seeing
what's
existing
today.
What's
the
state
of
that,
you
know
how
user-friendly
is
the
onboarding
process.
A
D
A
D
A
I
did
it
almost
like
the
milestone
where
you'd
have
a
command
in
the
CLI
or
the
the
UI
that
you'll
be
able
to
run
it
like
a
proper
round?
Exactly
a
brown
come
on
so
I
brought
this
up
with
tests
infra
just
to
see
why
you
needed
right
access
to
change
the
merge
method
and
why
we
kind
of
got
this
pickle
to
begin
with,
and
it
turns
out
that
they,
just
in
general,
don't
want
a
lot
of
folks.
Changing
that
merge
method
of
tied
via
the
CLI
are
good.
That
use
alright.
A
Keep
saying
CLI
via
the
UI
like
in
a
comment,
maybe
is
something
we
could
resurface.
Maybe
there's
a
special
case
for
Docs,
but
I
know
when
I
initially
brought
it
up.
The
general
opinion
was
they
wanted
the
repository
admins
or
the
people
with
write
access,
those
repos
to
be
in
control
of
that
merging
strategy
and
not
to
have
it
all
over
the
place,
but
maybe
there's
a
way
that
that
could
be
limited
to
approvers
or
people
who
are
you
know,
elevated
in
the
kubernetes
repository.
A
A
The
one
thing
I
do
want
to
add
before
we
move
on
is
that
this
is
somewhat
of
a
work
in
progress,
so
we're
talking
about
creating
this
documentation
for
squashing
we're
talking
about
changing
the
merge
method,
and
there
might
be
some
unintended
consequences
of
that,
such
as
folks
who
are
using
the
UI
who
don't
know
how
to
squash
such
as
you
know,
some
these
different
roadblocks.
If
we
find
out,
we
make
this
change
and
things
get
worse
and
not
better,
there's
no,
no
pain
and
reverting
it
back
to
the
old
way.
A
A
Now,
right
here,
then
we're
gonna
move
on
to
the
administration
component
of
today's
meeting.
So
we
do
have
a
new
technically
denomination
from
Kaitlyn
nominated
Taylor
dozle
to
become
a
tech
lead
alongside
Karen
and
Tim.
Banister
and
Kaitlyn
has
worked
with
Zach
myself
and
obviously
she
agrees
with
this
as
part
of
the
nomination
getting
all
the
members
aligning
her.
The
alignment
they're
also
working
with
some
of
the
tech
folks,
such
as
Karen
and
Tim,
to
get
alignment
there
for
the
membership
agreement.
That
Taylor
would
be
qualified
to
become
a
technical
lead.
A
A
So
to
make
this
official
I
put
air
quotes
because
it's
not
something
we
commonly
do.
We
never
really
had
tech
leads,
and
then
we
had
to
Karen
and
Tim
joined
not
too
long
ago,
and
we're
really
thankful
that
y'all
join
us.
Tech
leads
so
part
of
the
governance
by
KU
Bernays
in
the
community.
There's
needs
to
be
an
alignment
between
the
chairs
and
also
the
tech
leads
to
vote.
A
Taylor
in
the
final
say,
is
of
the
co-chairs,
so
Kaitlyn
and
I
represent
two-thirds
of
those
chairs
that,
unfortunately,
couldn't
be
here
today,
but
Zach
has
said
that
he
agreed
with
this
process
moving
forward.
He
agreed
with
Taylor's
nomination
of
moving
into
a
tech
lead,
so
we
have
offline
alignment
with
Zach,
but
then
also
there
needs
to
be
a
supermajority
and
I'm
making
I'm
not
making
up
terms
but
I'm
trying
to
go
from
memory
here
and
what
we
need.
A
A
C
A
Thank
you
sailor.
So
the
first
work
that
you
cut
out
for
you
is
you'll
need
to
PR
yourself
as
a
tech
lead
into
the
link
and
the
in
the
agenda
there,
and
if
you
have
any
issues
with
that
feel
free
to
reach
out
to
the
sig
Docs
channel
or
one
of
us
absolutely
thank
you
so
much
cool
and
moving
on
here
we
have
the
quarterly
review
that
was
scheduled
for
tomorrow.
Read
that
is
scheduled
for
tomorrow.
April
1st,
at
11
a.m.
Pacific
I
have
linked
in
the
agenda
the
agenda
for
the
quarterly
planning
right.
A
Now,
it's
more
of
just
an
open
agenda.
Looking
for
topics
but
I've
also
included
a
link
in
there
for
our
quarterly
planning
from
q4
of
last
year.
So
you
can
see
what
that
looks
like
and
there's
anything
that
that
sparks
any
ideas
from
definitely
check
that
out
and
review
that
I've
included
the
zoom
link
there.
If
someone
needs
a
quick
link
to
it
and
before
moving
on
any
further,
does
anyone
need
to
invite
who
would
like
to
attend
and
hasn't
seen
that
invite
come
through
yet.
A
Cool
so
yeah
David,
I'll,
I'll
email
you
that
after
we
get
off
the
line
here,
okay,
no
problem
at
all
and
then
if
anyone
wants
to
discuss
anything
at
the
quarterly
planning.
This
is
where
we
discuss
a
lot
of
more
the
strategic
goals.
We
talked
about
videos
last
quarter
more
or
less.
You
know
what
what
are
our
goals
to
accomplish
this
quarter?