►
From YouTube: K8s SIG Docs Meeting 20200218
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
Let's
start
as
we
always
do
by
welcoming
new
contributors,
Barney
is
not
a
new
contributor,
but
I
think
this
is
maybe
the
first
time
we've
ever
actually
seen
his
face.
So
welcome
Barney,
Thank,
You
Barney
was
one
of
our
release,
leads
for
one
dot:
1.16
1.15
yeah
16:16
yeah
good
to
see
it
welcome
back
Adam
Kaplan.
A
This
week's
PR
Wrangler
is
Barney
and
next
week's
PR
regular
instaminis
Satya
Domini
was
our
release
lead
for
1.17,
as
always
Kruger's
make
sure
you
know
when
your
PR
Wranglers
shift
is
scheduled.
It's
a
lot
easier
to
swap
shifts
around
ahead
of
time
rather
than
during
the
week
of
alright.
Let's
talk
about
docks
so
release
1.18
update.
A
Currently
the
dev
dot,
1.18
branch
is
broken,
and
that's
because
beneath
one
of
the
pieces
of
release,
maintenance
is
making
sure
that
the
dev
branch
for
that
release
keeps
current
with
the
master
branch
and
we
do
that
by
merging
master
into
the
dev
branch,
and
there
are
some
very
specific
reasons
why
we
do
that,
as
opposed
to
rebasing.
But
in
order
to
do
that
in
a
healthy
way,
we
have
to
apply
a
specific
tied
label
to
merge
PRS
to
ensure
that
they
don't
that
commits
in
there
don't
misbehave
and.
A
Beneath
the
release
lead
opened
a
PR
to
merge
master
into
the
branch
he
didn't
apply.
The
label
I
approved
it
and
didn't
notice
that
it
didn't
have
the
label
so
we
broke,
and
now
we
get
to
fix
that
so
I've
asked
Karen
Bradshaw
for
a
sanity
check
on
the
proposed
method.
You
can
think
did
I
link
to
the
there
is
a
slack
discussion
about
it
if
you're
really
that
interested
it's
in
the
cig,
Doc's
Channel.
A
A
Right,
let's
move
on
to
the
kept
for
third
party
and
dual
source
content.
Brad.
Is
that
you
breathing
that
immediately
all
right,
so
the
kept
for
how
kubernetes
talks
deal
with
third
party
and
dual
sourced
content?
So
a
couple
of
updates
on
that
we're
getting
we've
gotten
some
really
good
feedback
about
how
to
implement
specific
language.
Tim
had
the
genius
idea
of
instead
of
referring
to
bounding
documentation,
to
only
be
for
entry
functionality
to
expand
that
to
in
project
functionality,
which
I
think
is
much
more
robust
and
that's
also
gotten
very
positive
feedback.
A
The
next
big
update
on
that
particular
kept
is
that
we're
on
the
agenda
for
the
open
steering
committee
meeting
on
Monday,
March,
2nd
and
I
am
happy
to
keep
folks
updated
with
with
the
results
of
that
meeting.
One
thing
to
be
aware
of
it's
going
really
well
at
this
point,
so
I
anticipates
that
we
could
see
some
forward
potentially
you'd
like
getting
this
kept
approved
within
a
like
by
the
end
of
March.
A
A
Take
a
look
at
content
that
would
no
longer
belong
in
the
docks
based
on
the
final
form
of
that
cap
and
start
opening
PR
so
either
well.
Letting
letting
content
owners
of
non-conforming
content
know
that
they
have
90
days
to
start
removing
content
so
basically
starting
to
give
folks
90-day
warnings
as
soon
as
that
cap
is
approved.
A
A
C
Cool
I,
like
that
and
the
other
question
I
had
was
around
sort
of
the
cleanup.
Basically,
so
you
know
on
the
assumption
that
this
might
land
I,
guess
that
there's
a
thing
for
possibly
you
know
losing
get
annotate
and
that's
the
polite
form
of
get
blame.
If
you
don't
know
that
come
on
to
find
out,
you
know
how
some,
how
some
changes
landed
and
maybe
give
people
proactive
heads
up
and
I
was.
Is
that
the
sort
of
thing
you
were
getting
out?
C
C
A
Blame
excellent:
yes,
that
is
exactly
the
kind
of
work.
So
it's
a
little
early.
Yet
so
I
didn't
plan
for
this
level
of
detail,
but
Amy
you
Kasich,
opened
an
umbrella
issue
featuring
non-conforming
content.
The
language
around
that
and
the
process
around
that
would
need
to
be
updated,
will
need
to
be
updated
when
we're
ready
to
start
moving
forward
on
it.
But
yes,
using
its
get
annotate
seems
like
the
reasonable
way
to
find
that
content
and
notify
the
the
relevant
committees
that
that
content
needs
to
find
a
home
elsewhere.
A
A
Applying
the
doxy
template
to
the
website,
so
I've
reached
out
to
gearbox
the
contracting
studio,
that's
doing
the
work
for
an
update.
This
process
has
been
slowed
down
a
great
deal
by
how
the
CNC
F
has
chosen
to
handle
billing
for
this
project.
I
am
doing
my
best
to
speed
that
up,
but
they're
working
on
applying
the
doxy
template
to
the
blog
section
now
so,
hopefully
we
will
have
an
updated
preview
link
that
includes
the
blog.
A
C
C
So
I
remember
this
issue,
but
I'm
gonna
get
it
on
my
screen.
First
yeah.
So
this
is
reported
by
artistic
cheese,
who's
I,
think
not
a
contributor.
But
as
currently
let
us
know
about
a
problem-
and
it
looks
very
much
like
a
particular
kind
of
failure
mode
and
my
gut
feeling
is
that
it
almost
definitely
something
is
balancing
between
two
things
and
then
one
of
those
weights
for
six
seconds
before
failing
and
then
another
process
takes
over,
and
this
only
seems
to
affect
things
with
cache-control
max
age
equals
zero,
most
revalidate
of
them.
A
Thank
you
for
boosting
visibility
on
this.
The
reason
why
I
wanted
to
boost
this
particular
issue
is
because
it's
germane
to
a
larger
set
of
well
to
a
larger
pressure.
I
guess
in
sig
Docs
is
the
best
way
to
say
that
right
now
there
is
a
very
limited
number
of
people
who
have
access
to
our
net
left
eye
configuration
historically,
that's
been
limited
to
in
sig,
Docs
has
been
limited
to
chairs
and
I.
Don't
think
it
needs
to
be
there's.
There
is
some
responsibility
that
comes
with
access
to
nullify.
A
Someone
could
do
a
fair
amount
of
damage
if
they
were
to
act
irresponsibly
with
those
permissions,
but
there's
really
no
reason
to
bottleneck
these
permissions
exclusively
to
the
role
of
the
chair
and
so
I
want
to
raise.
The
I
want
to
raise
the
discussion
about
adding
a
role
to
leadership
and
sig,
Docs
and
specifically
technical
leads.
A
A
Think
folks,
who
would
make
excellent
candidates
are
rightly
sort
of
wary
about
taking
on
the
whole,
taking
on
everything
that
comes
with
being
a
chair
and
that
folks
might
not
be
or
might
be
more
willing
to
consider
cig
leadership
if
it
was
limited
at
the
scope
of
that
role
was
limited
to
technical
leadership.
So
I
want
to
raise
this
possibility
and.
C
There's
everything
yeah
go
sure,
so
I'm
really
focusing
on
the
issue.
You
know
the
technical
issue
and-
and
this
becomes
a
girl
from
it
rather
than
the
the
tech
made
idea,
but
it
strikes
me
that
this
is
the
sort
of
thing
that,
with
a
work
hat
on,
and
sometimes
we
would
say
well
a
good
way
to
solve
that
is
to
pay
for
the
next
support
here,
up,
pay
more
money
and
then
ask
the
supplier
to
make
the
problem
go
away
for
you.
C
The
thing
is
that
at
the
moment,
I
imagine
that
you
have
to
be
a
chair
also
even
to
raise
a
support.
Crate
case
is
that
right.
A
C
A
Exactly
that
you've
encapsulated
the
point
nicely
so
I
guess
this
is
my
call
if
you
are
interested
in
being
a
technical
lead
for
cig
docks.
Please
reach
out
to
either
myself
in
Jim
angel
or
Caitlin
Bernard,
and
we
can
talk
specifically
about
what
that
means
and
what
it
doesn't
mean
in
greater
detail.
A
Timeouts,
okay,
I
wanted
to
boost
visibility,
also
on
an
issue
that
Remy
Leon
raised
about
the
dot
summary
attribute
and
Hugo.
So
apparently
it
has
an
effect
on
SEO
and
the
the
means
by
which
this
attribute
is
populated
is
currently
opaque.
So
Remy
is
doing
some
digging,
but
if
you're
interested
in
SEO-
and
you
also
know
a
little
bit
about
Hugo
I-
would
reach
out
to
him.
Let
me.
B
A
Until
until
we
find
a
contractor
who
can
execute
on
creating
standards
for
diagrams
that
doesn't
look
like
it's
moving
forward
like
we
talked
about
at
our
quarterly
review
at
the
end
of
last
year,
there
are
a
ton
of
great
ideas
that
we
could
execute
on,
but
unless
someone
is
willing
to
to
own
it
and
drive
it,
they
just
won't
get
done
so
I
reached
out.
I
have
come
up
with
nothing
at
the
CN
CF
in
terms
of
people
who
can
recommend
a
graphic
designer
to
do
that
work.
B
A
A
D
A
D
B
A
A
A
A
A
I
experience
frustration
around
things
that
are
not
inefficient,
but
I
don't
know,
maybe
maybe
you
were
all
or
just
you
know,
pools
of
column
and
I
alone
and
the
rage
lucky
for
inefficient
processes.
A
But
that
seems
to
me,
like
the
most
reasonable
way,
we're
not
necessarily
the
most
but
a
reasonable
way
to
cultivate
more
first
issues
or
good.
First
issues
is
to
take
tasks
that
seem
obvious
and
rather
than
just
doing
them
ourselves,
because
it's
easier
and
faster
making
them
available
for
other
people
to
do
so.
E
E
The
I
feel
like
the
best
way
that
I've
ever
seen
anybody
do
this
in
the
world
of
tech.
Writing
is
having
effectively
a
mini,
hackathon
and
pause
because
we're
gonna
adopt
it
but
effectively.
The
hackathon
has
two
parts.
First,
you
get
a
bunch
of
people
in
the
room,
it
doesn't
matter
if
they
actually
know
documentation
or
not.
Second,
is
you
go
through
just
a
section
or
the
entire
set
of
documentation?
Kubernetes
is
huge,
I
suggest
we
go
section
by
section.
One
person
drives
and
shares
their
screen
and
everybody
else
just
yells
out.
That's
wrong!
E
That's
wrong!
That's
wrong!
That's
wrong
and
you
just
take
bullet
point
lists
and
then,
after
that,
you
convert
them
into
issues
and
go
move
section
by
section
and
I.
Think
if
we
spent
say
the
other
half
hour
of
these
meetings
every
week,
taking
one
section
and
just
throwing
like
this
is
crap.
This
is
crap.
This
is
cough.
This
is
crap
one
onto
a
bullet
point
list
and
then
taking
the
time
to
convert
those
two
issues
after
we'd
have
a
lot
of
first
issues
very,
very
quickly.
E
F
F
So
I
mean
one
of
the
things
I
have
is
initiative
at
my
company
is
trying
to
increase
the
number
of
contributors
to
open-source
it's
one
of
my
day,
jobs
as
opposed
to
my
night
job,
and
so,
if
we
can,
you
know
using
techniques
like
you
described.
If
we
can
build
a
greater
list
of
those
great
first
items.
I
know
you
know
that
a
little
worried
about
efficiency,
but
but
you
know
fall,
goes
well.
I
will
have
a
pipeline
of
folks
who
could
could
love
having
a
good
first
issue
as
they
even
learn.
E
Don't
even
they
don't
have
to
be
kind
of
complicated,
there's
a
lot
of
even
just
kind
of
scrolling
through
the
coop
and
any
documentation,
as
it
is
there's
a
lot
of
like
the
grammar
and
this
paragraphs,
not
great.
That's
a
fantastic
first
issue:
it'll
teach
you
the
processes
here,
it's
fairly
low
effort,
improved
documentation,
quality,
you
know
no
harm,
no
foul
and.
F
A
C
I
wonder
about
timing,
because
I
am
kind
of
minded
to
save
up
my
effort
to
look
too
much
of
this
until
it
is
I,
say
a
few
weeks
out
from
Cuba
calm
and
then
because
you
know
if,
if
there's
gonna
be
some
get
involved
with
sigdoc
sort
of
activity
around
Cuba
calm
and
a
big
pool
of
good
first
issues
is
great,
and
if
you
open
them
too
soon,
people
will
resolve
them.
For
you.
C
C
A
We
looked
at
the
conversion
results,
looked
at
it
and
basically
went
section
by
section
said
this
is
wrong.
This
is
wrong
and
just
like
opened
issues
like
crazy
and
then
a
week
later,
Andrew
Chen
Rena
docks
friended
right
the
docks
where
everyone
just
fixed
those
issues,
so
that
kind
of
it
boggles
the
mind
how
effective
that
was
at
both
identifying
issues
and
then
resolving
them
so
but
yeah
timing,
this
around
coop
con
I
think
does
make
a
lot
of
sense.
A
B
E
B
C
F
Fear
is
that
you'd
get
in
there
and
think
that
you
get
a
whole
bunch
of
folks
that,
were
you
know,
very
passionate
and
giving
you
this
was
wrong.
That's
wrong!
That's
wrong!
My
fear
is,
if
you
hit
the
wrong
audience.
They're
all
just
gonna
sit
there
and
look
at
you
and
you're
gonna
be
like
I
got
to
do
this
for
another
50
minutes.
That's
fair!
Let
me
see.
A
H
C
I
mean
a
thing
that
I
can
do
locally
and
I
guess
we
can
all
replicate,
and
we
can
suggest
this
more
widely
to
people
interested
in
the
website.
If
I
can
go
to
my
local
tribal
native,
meetup
or
whatever,
and
just
ask
people
what
what
problems
they're
having
with
the
website
again
I
think
I
will
I,
because
the
people
who
are
new
to
kubernetes
give
us
the
best
feedback
drink
yep.
A
Great,
but
it's
not
documented,
it's
not
documented
well,
and
it
is
one
of
those
non-obvious
pieces
of
information
that
is
critical
but
just
assumed,
but
because
it's
so
critical
that
it's
obvious
and
that's
really
bad
documentation.
Yeah
I
mean
that's
Tim.
Do
you
might
finding
that
issue
and
and
linking
that
to
the
to
zoom
chat
and
maybe.
B
A
Don't
have
a
look,
thank
you
yeah.
It
was
Ben
Ben
elder
raised
it
to
our
visibility,
and
he
said
this
is
a
painful
issue
to
read
and
he
was
he
was
right.
It
deserves.
It
is
a
painful
issue
to
read,
but
yes,
I,
think
giving
more
opportunities
to
offer
this
kind
of
feedback
and
receive
this
kind
of
feedback
contributes
nicely
to
a
good
first
issue,
pool.
A
A
A
E
E
Mean
I
think
I
get
what
you're
getting
at,
because
I
can
see.
Ii
I'm
in
Adam
Catherine's
issues
the
step
by
steps,
a
lot
of
the
good
first
issues,
but
come
by
and
then
they're
gonna,
add
some
of
the
complexity.
And
it's
not
a
really
a
good
issue
and
like
in
some
ways,
for
example,
the
issue
that
Tim
just
linked.
It's
very
well
defined.
So
it's
kind
of
a
good
first
issue.
But
you
need
to
know
what
a
kubernetes
manifest
is
quite
differently.
So
it's
maybe
not
a
great.
C
E
E
Was
also
gonna
say
like?
Is
it
a?
Is
it
a
question
of
like
and
I'm
just
gonna
share
personal
experience
here
of,
like
when
I
was
trying
to
start
contributing
more
to
open
source,
just
because
I
thought
it
was
an
interesting
thing
to
do
like
the
form
right
career
here.
I
would
often
click
into
a
repository
see
a
good
first
issue
for
documentation
and
realized,
like
there's
no
possible
way.
E
H
Know
I
think
you're
Zack,
you
mentioned
you
you,
you
know
I've
chatted
about
having
like
new
contributor
ambassadors
that
are
like
people
who
can
help
people
get
started,
but
there's
always
like
that
step.
Like
I,
don't
know
a
couple
PRS
out
where
it's
like
I
know
enough
to
commit
a
PR,
but
I
don't
know
enough
to
actually
make
a
substantive
change
that
I
can
put
towards
becoming
an
official
contributor
to
the
repo.
H
F
So
a
very
targeted
mentoring
for
those
issues,
because
then
somebody
look
at
it
and
go
even
if
they
don't
know
about
the
Ambassador
Program
or
even
worse,
they
get
one
of
our
weaker
ambassadors
like
myself,
but
maybe
he
doesn't
know
the
issue.
This
would
give
better
results.
So
if
there
was
an
issue
you
were
passionate
about,
but
you
didn't
have
time
to
do
yourself,
but
you
say
you
know,
but
I'd
be
happy
to
mentor.
Somebody
I
think
we
get
good
results
from
that.
It
helps
build
that
bond
and
grow
the
number
of
contributors.
F
Yeah,
it
borrows
from
one
of
my
list
of
sort
of
wonderful
guidance
that
I
give
for
becoming
a
contributor
or
maintainer
one
of
the
tricks
that
I've
taught
people
is,
if
you're,
really
trying
to
break
into
a
community,
go
find
somebody
and
do
work
on
their
behalf,
because
then
they'll
be
very
motivated
to
give
you
advice
for
a
motivated
to
review
your
work.
So
don't
start
out
with
your
own
issues,
start
out
by
by
trying
to
do
established,
commit
or
maintain
errs
issues,
and
it's
been
a
model
that
it's
worked
very
well
in
the
past.
A
E
E
That
makes
it
easier
for
other
technical
writers
to
get
involved,
because
that's
how
technical
writers
work,
we
talked
to
subject
matter
experts
and
then
we
do
the
writing
bit
and
that's
something
that
a
lot
of
open
source
projects
struggle
with
is
like.
How
do
we
get
people
who
have
writing
knowledge
involved
in
these?
A
A
C
Well,
I
guess
I
guess
the
PR
that
comes
out
of
the
issue
is
where
we
can
have
that
discussion
in
detail
to
share,
but
I
think
it's
really
the
value
I.
Think
of
having
anything
contribute
to
go
as
well
is
the
people.
Oh
I
can
do
a
thing
and
also
well
I'm,
not
a
reviewer.
Yet,
but
apparently
there
are
people
who
can
do
a
thing
and
that
second
bit
I
think
is
equally
valuable.
C
A
Let's,
let's
pick
this
up
next
week,
because
I
I
think
I
think
we
would
benefit
from
taking
some
time
to
to
noodle
on
this
and
think
about
really
specific
ways
to
like
cultivate
and
flag
for
for
available
mentorship
in
specific
issues
or
as
an
approver
or
reviewer.
You
know
this
is
but
yeah.
This
has
been
a
really
powerful
discussion
around
this.
Thank
you.
Everyone
for
contributing.
F
Just
real
quickly,
my
head
is
just
like:
we
label
something
good
first
issue.
If
we
had
a
label
that
said
mentor
available
and
then
you
were
able
to
say
in
the
description
of
what
needed
to
be
done,
so
answer
was
willing
to
sort
of
as
a
mentor.
Those
are
some
pretty
good
breadcrumbs
that,
ideally,
someone
could
come
across.
F
A
F
B
A
F
H
A
I
Sure
so,
actually
today
is
our
blog
me
being
I
liked.
What
you
asked
me
on
blog
meeting
of
the
week,
so
I
can
give
a
shout
out
that,
if
anybody's
interested
in
joining
that
or
learning
more,
we
have
it
right.
After
this
meeting,
we
have
two
blog
posts
in
the
pipeline
right
now,
one
on
Q,
cuddle,
plugins
and
then
another
one
on
ingress
controllers.
In
its
do
we
published
one
last
week
on
OpenStack
with
cube
a
DM
and
just
to
+1
that
technical
lead
position
for
net
liffe.