►
From YouTube: K8s SIG Docs Quarterly Planning - 20200401
Description
For more info see https://git.k8s.io/community/sig-docs
A
Right,
hello,
everyone
today
is
Wednesday
April,
1st
2020,
and
this
is
the
quarterly
planning
and
review
meeting
for
kubernetes,
sig,
Docs
I,
say
quarterly
ends
up
being
more
like
five-month
Annalee,
but
whatever
here
we
all
are-
and
it's
so
good
to
see
everyone.
So
the
agenda
link
I
posted
in
slack
but
I'm
going
to
post
it
again
in
zoom
chat.
Just
so
we
have
it
all
handy.
A
A
A
A
We
take
a
dance
break
nice
movement
break
to
stretch
and
then
we'll
come
back
from
that
and
we'll
talk
about
proposals
for
what
to
do
next
and
how
to
go
forward
so
right
now.
The
topic
proposals
are
at
the
top
of
this
meeting,
I'm
going
to
move
them
now
to
the
end,
and
if
you
have
a
proposal
that
you'd
like
to
that
you'd
like
to
talk
about,
feel
free
to
add
it.
There
just
know
that
it's
now
at
the
end
of
the
agenda
rather
than
at
the
start.
A
C
D
A
A
E
F
G
Absolutely
clear
on
my
name
is
Taylor
Dolezal
I
work
at
a
big
entertainment
company
that
you
probably
recognize
I
came
to
kubernetes
about
a
year
and
a
half
I
came
to
kubernetes
about
a
year
and
a
half
ago
and
start
contributing
really
really
love
website,
stocks,
blogs
and
I've
gotten
into
the
release
process.
A
few
times
my
favorite
colors
red
head,
one
Sam.
A
A
Let
us
go
right
into
the
2019
q4
and
2020
q1
review,
and
ideally
this
should
take
about
45
minutes.
So
let's
do
let's
talk
about
wins.
I
have
added,
some
will
talk
about
wins
and
challenges
first
and
I've
added
some
wins
and
added
some
challenges,
but
this
is
by
no
means
complete.
So
if
you
see
or
think
of
other
things
that
we
can
add
to
either
our
wins
or
our
challenges
feel
free
to
add
those.
A
So
let's
talk
about
our
wins.
Our
web
traffic
is
consistently
climbing.
It's
considered
the
or
it's
continued.
The
rate
of
increased
page
views
that
we've
seen
consistently
over
time,
and
we
are
now
up
to
one
point:
six:
six
million
use
per
week
and
that's
up
from
1.4
million
in
November
of
last
year,
so
our
our
traffic
keeps
going
up
and
our
satisfaction
ratings.
A
A
A
A
A
Okay,
so
our
pure
velocity
is
increasing
slightly
when
I
say
slightly
I
mean
very
slightly,
but
there's
some
things
that
I
want
to
point
out.
Normally,
our
annual
combined
issue
in
PR
velocity
is
about
six
thousand.
We
worked
through
six
thousand
issues
in
PRS
per
year
on
average
and
we're
on
track
with
those
numbers
so
far
and
that's
with
fewer
approvers
and
more
reviewers.
So
we're
doing
a
lot
of
things.
A
Getting
through
content
at
a
brisk
and
effective
rate,
so
that's
awesome
and
I
will
also
point
out
that
we
are
still
a
second
in
the
kubernetes
project,
only
behind
kubernetes
kubernetes
for
PR
velocity.
So
it's
just
it's
us
leading
test
infra
in
the
top
three
bracket,
there's
really
a
huge
gap
between
the
top
three
and
everyone
else,
and
we're
on
the
silver
medal
podium
for
PR
velocity.
So
congratulations
it's
due
to
due
to
an
excellent
community
and
an
effective
community.
So
thank
you.
A
A
This
was
a
bit
of
a
saga
to
a,
but
credit
goes
to
Tim
for
being
willing
to
drive
that
first
draft
and
take
aggro
for
the
especially
the
first
part
of
that
cap
process,
so
Tim.
Thank
you
very
much
for
leading
the
way
in
getting
us
to
where
we
could
have
a
meaningful
discussion
and
close
this
camp
out.
A
A
C
We
have
so
we
formalized
the
blog
process
into
a
sub-project
gosh,
maybe
six
months
ago
now
time
is
really
flying
and
that
allowed
us
to
bring
in
more
contributors
to
help
with
that
process.
We
have
I'd
love
to
pull
some
numbers
for
this,
but
we
have
really
been
able
to
increase
the
amount
of
content
on
the
blog.
Just
there
really
formalizing
this
process,
Thanks.
A
Alright,
then,
let's
talk
about
challenges
so
in
terms
of
content
and
information
architecture,
we're
still
in
maintenance
mode.
We
have
wonderful
contributors,
but
our
ability,
we
don't
have
any
dedicated
technical
writers.
So
I
say
that
with
Celeste
sitting
right
there,
we
don't
have
the
we
don't,
have
a
full
bench
of
technical
writers
devoted
to
like
improving
content,
improving
information
architecture,
so
we're
still
in
maintenance
mode.
We're
not
really
innovating
in
terms
of
our
content
and
that's
a
challenge.
A
A
A
Another
challenge
we've
had
several
approvers
drop
out
over
the
past
really
the
past
six
months.
Some
of
this
is
expected.
Honestly,
people
move
on
jobs,
move
on
people's
involvement
in
open
source
projects
is
transient,
so
it
has
made
it
difficult
to
maintain
an
active
and
accurate
PR
regular
schedule.
A
H
A
A
A
A
J
H
A
Thank
you.
It's
a
very
generous
offer
that
I
would
like
to
defer
discussion
about
what
we
do
with
PR
Wranglers
to
maybe
a
little
further
on
in
the
meeting
yeah,
because
we
do
need
as
generous
as
and
offers
that
is.
We
do
need
an
actual
plan
for
like
how
how
to
how
to
respond
to
churn,
because
your
turn
is
inevitable
and
and
healthy,
even
so.
I'd
rather
I'd.
Rather
we
take
a
real,
take
a
real
shot
at
the
underlying
piece,
rather
than
sent
to
stop
it
with
bodies.
A
A
I
think
that
the
last
two
planning
meetings,
but
it's
still
an
open
issue
about
how
to
make
sure
that
our
content
stays
fresh
or
this,
how
do
to
track
freshness
effectively
and
the
final
challenge
that
I
have
listed
here:
release
1
that
18
was
a
bear
of
a
release
for
a
host
of
technical
reasons.
We
saw
a
little
bit
of
struggle
with
1.17,
but
1.18
really
brought
some
of
the
flaws
and
pain
points
in
the
docks
release
process
forward
in
a
big
way.
A
D
Would
say
it's
related
to
the
approvers
dropping
out
is
the
contributor
ladder
I
feel
like
I'm
boarding,
new
folks,
onboarding
new
contributors,
a
lot
of
drive-by
PRS
and
a
lot
of
drive-by
contributions,
and
you
know,
building
a
contributor
ladder
up
needs
to
start
somewhere
and
and
I.
Don't
necessarily
think
that
that's
as
great
as
I've
seen
it
in
the
past.
E
A
A
Karen
has
done
some
really
valuable
work
to
update
our
scripts
and
responds
to
a
change
in
how
scripts
are
tagged
upstream
in
kubernetes
kubernetes,
but
it's
still
like
a
really
a
really
fragile
piece
of
our
publishing
chain.
Is
it's
the
thing
that
I
think
we
do
the
least
well
in
terms
of
our
like
content
output?
So
that's
also
something
to
be
aware
of
alright.
So
with
our
wins
and
our
challenges
in
mind,
let
us
go
to
our
goal
review
so.
A
A
Right
in
each
one
of
these
things,
you'll
see
something
like
this
color-coded
bits
with
a
grade
assigned
and
what
this
is.
This
is
a
wholly
arbitrary
number
between
0
and
1
that,
in
my
estimation,
I've
assigned
like
zero
zero
to
zero
point.
Three
is
red,
meaning
it's
like
a
percentage
of
the
way
done
point
four
two
point:
seven
is
yellow
and
point
eight
to
one
is
green.
A
This
is
not
a
grade
like
the
quality.
This
is
just
like
how
much
of
this
did
we
actually
accomplish,
and
this
is
also
wholly
arbitrary,
like
this
is
the
work
of
me.
One
person,
my
view.
So,
if
you
don't
agree
with
this,
fascinating
I
would
love
to
hear
your
own
opinion
and
let's
have
dialogue
around
that.
So
any
questions
about
the
the
grading
system
before
we
launch
into
the
review
discussion.
A
The
first
school
that
we
had
was
better
admin
Doc's
on
how
to
set
up
a
cluster
having
secured
clusters.
This
was
Zack
Arnold
took
this
on,
and
the
deliverable
that
he
agreed
on
at
the
time
was
to
define
a
prioritized
list
of
topics
that
need
to
be
documented
for
users
around
specifically
cluster
administration
and
security.
I
put
a
big
fat
question
mark
on
this,
because
I
know
that
Zack
Arnold
isn't
involved
anymore,
but
I
know
that
Seth
and
Peter
have
stepped
up
and
Seth
and
Peter
I.
K
A
A
A
D
See
a
whole
bunch
of
thumbs,
ups
no
thumbs
down.
One
comment
that
I
would
have
on
this
is
I.
Think
if
there's
a
great
effort
going
on
for
the
security
improvement
of
documentation,
but
I
know
both
Seth
and
and
Peter
have
both
been
very
busy
with
getting
those
meetings.
Rolling
it'd
be
nice
to
see
what
this
looks
like
next
quarter
and
if
there's
still
kind
of
this
hit
or
miss
meetings,
low
attendance.
A
A
A
A
D
A
A
A
A
A
I
A
A
L
A
A
That
said,
Brad
I,
think
they're,
adding
specifically
focusing
on
adding
approvers
and
improving
our
pipeline
sounds
like
a
great
proposal.
Will
you
add
that
to
the
proposal
section
at
the
end
of
the
agenda,
sure
thank
you,
of
course,
all
right.
So
next
item
we
talked
about
increasing
automation,
reducing
manual
labor
burdens
and
we
had
floated
the
idea
of
a
linter.
We
didn't
take
any
action
on
that
linter,
so
yeah,
no
action
specifically
unveil
I
would
say
that
we
are
actively
embracing
automation
wherever
we
can
so
I
guess
the
do
we
carry
forward.
A
M
A
M
It's
a
effectively
a
natural
language
linter
which
is
handy
for
us,
but
it
would
take
a
lot
of
configuration
to
set
up
and
is
awesome.
Nobody
knows
how
it'll
work
with
a
bunch
of
localizations
in
tow,
because
at
least
in
my
experience
with
it,
everybody
who's
used
to
has
used
it
on
English
language,
only
cutter
with
all's
right,
but
it
could
be
really
handy
so.
E
I'd
like
to
step
back
to
these
coffee
and
comments
thing,
because
I'll
just
try
and
summarize
the
sort
of
suggestions
I
was
making
yesterday
in
the
sigdoc
weekly
meeting.
My
idea
was
that
it
would
be
lovely
if
prowl
would
magically
let
people
squash
their
own
commits,
and
that
would
help
support
the
workflow.
The
people
who
have
never
run
the
gate
command-line
tool,
but
want
to
contribute
to
Docs
and
I.
Think
that's
what
yeah!
That's
what
that
little
bit
was
about.
I
I
think
for
consistency
purposes.
Ideally,
if
it's
a
proud
command
that
we're
staying
in
the
groove
and
doing
all
the
things
using
the
sort
of
a
approved
way
of
doing
things,
I
mean
don't
get
me
wrong.
Did
hub
actions
are
fantastic,
but
but
the
first
choice
is
the
proud
command
I.
Think
just
because
that's
the
first
thing
they'll
ask
is:
why
did
you
do
this
is
approximate
so.
A
At
this
point
it
sounds
like
we
are
interested
in
it
and
that
we're
that
that
discussion
is
heading
down
to
implementation
details
rather
than
strategy
details.
So
the
strategy
question
is:
do
we
carry
forward
with
attempting
to
automate
everything
that
we
can
and
I'm
going
to
propose
that
we
do
this?
Not
only
in
q2
but
annually,
so.
A
A
D
N
D
Sure
we're
seeing
the
chip,
but
Karen
mentioned
just
not
sure
about
linting,
look
good
to
investigate.
Okay
and
I'll.
Give
that
a
plus-one
as
well
in
the
limping
piece
there.
I
know
that
contra
backs
is
using
a
linter
today
and
their
justification
is
that
it
reduces
driving
by
PRS,
doing
typos,
fixes
and
I.
Think
if.
I
D
A
Gotcha,
no,
that's
real!
Okay
contract,
your
funding,
so
an
update
on
some
of
the
projects
that
we
talked
about
at
the
last
les
planning
meeting
and
it's
still
true.
The
CNC
F
is
willing
to
fund
contractors
for
variety
of
improvements,
but
we
need
someone
to
drive,
but
here's
what
we
agreed
on
at
the
time.
So
we
agreed
on
a
new
theme
for
the
website
and
that
the
shape
of
that
was
applying
the
doxy
theme
to
Hugo.
A
I
gave
this
a
point:
seven,
because
the
work
is
in
progress.
We've
got
the
preview
sites
are
up
in,
live
and
available
for
testing
more
and
more
content.
All
the
time
and
the
contractor.
The
last
when
I
talked
to
the
contractor
last
week,
he
said
about
three
four
more
weeks,
even
in
the
mid-nineteen
landscape.
So,
given
my
experience
with
him,
I
would
put
that
at
about
five
to
six
weeks,
but
even
so
like
it's
happening,
and
it's
getting
close
so
I
guess.
A
E
So
I'm
a
professional
worked
with
a
few
firms
there
in
this
space
and
I
feel
like
it's,
not
the
sort
of
thing
that
I'm
used
to
people
didn't
easily
do
for
commerce,
but
I
feel
like
it's
something
that
you
know
a
contractor
could
make
provide
much
better
insights
to
let's
as
work
out.
What's
missing
like
we
know
what
pages
are
popular,
but
we
don't
know
what
pages
are
missing.
E
E
A
A
A
D
A
A
D
Yeah,
so
that
was
a
comment
that
came
up
just
in
general
about
improving
kubernetes
overall
SEO
since
there's
been
no
work
on
it.
I
don't
see
a
value
in
carrying
it
forward.
It
might
also
be
a
candidate
for
removal,
but
if
we
wanted
to
fund
someone
to
to
move
that
forward
and
have
SEO
improved
I'm,
not
against
it,
but
I
don't
want
to
speak
for
the
wider
community.
I
just
don't
know
once
again
we're
kind
of
in
the
ambiguous
yeah.
We
all
agree
in
general.
We
want
to
improve
and
be
better.
A
D
A
A
A
A
H
H
A
I
may
not
be
able
to
do
it
during
this
meeting,
but
definitely
get
that
and
feel
free
to
feel
free
to
bug
me
because
my
memory
is
this:
what
it
is
so
Steve
you
had
talked
about
doing
a
scope
of
work
for
how
to
create
video
content
and
I
marked
that
as
a
one,
because
you
did
it.
So
do
you
want
to
talk
about
that
and
what
that
looks
like
I'm,
going
forward
in
q2.
H
As
far
as
I'm
concerned
that
the
document
is
finished
and
the
the
work
that
that
I'm
gonna
do
on
this
is
finished.
There
are
some
comments
still
in
the
dock,
along
the
lines
of
now
that
we've
taken
the
viewer.
This
far,
should
we
also
show
them
how
to
do
this
or
that
and
I
don't
have
a
strong
feeling,
one
way
or
the
other
I
the
way
I
wrote
the
dock.
It
was
my
you
know
my
best
estimate
of
what
you
know.
H
What
would
be
just
the
right
amount
of
content
for
this
purpose,
which
is
just
just
to
get
people
to
a
place
where
they
can
start
doing
what
you
would
do
at
a
dock
sprint,
but
whoever
takes
to
the
next
step.
I
have
no
objection
to
saying.
Oh
well,
it's
there's
a
few
more
things
we
want
to
add
so
I
I
consider
my
work
on
this
done.
A
H
Yeah
and
the
the
motivation
for
this
was
the
few
times
I've
been
at
docs
prints.
What
I've
seen
is
you
know?
Half
the
people.
There
already
know
how
to
use
git
and
github
so
they're
fine,
but
the
people
who
don't
they
spend
almost
their
entire
time
they're
getting
set
up
and
we
spent
a
lot
of
our
time,
helping
them
get
set
up,
and
so
I
just
thought.
If
we
could
show
them
a
video
a
week
ahead
of
a
docs
print,
they
could
get
themselves
set
up.
Only.
A
I
J
A
A
Can
the
docs
be
improved
anywhere
to
reduce
complexity
and
simplify
understanding?
Can
we
help
lower
the
high
bar
for
understanding
Kate's
back
in
November?
We
Tim
noted
that
the
Linux
Foundation
course
doesn't
tie
in
to
the
official
Docs
and
at
the
time
we
decided
not
to
adopt
it
in
q1
and
to
revisit
the
question
about
lowering
the
barrier
to
entry
to
kubernetes
with
Steve
Harry
in
q2,
so
I
gave
it
2.5
because,
even
though
we
agreed
not
to
adopt
it,
we
have
made
a
couple
of
iterations
that
I
think
are
helpful.
A
Celeste
added
the
top
level
trading
page
Jim
added
yeah,
exactly
yes,
well
done,
Celeste
and
Jim
added
a
top
level
or
handy
alias
for
our
back.
So
there
have
been
some
improvements
to
like
lower
barrier
to
entry
for
I.
Think
the
most
valuable
topics
so
I
gave
it
a
point:
5
I,
guess
the
question
is:
do
we
have
someone
willing
to
drive,
reduce
barriers
to
entry
and
keeps
you.
M
M
Mean
I
have
just
like
one
suggestion
that
came
up
from
some
feedback:
I
got
on
that
training,
page
from
like
friends
of
mine
who
are
kubernetes
users,
which
is
what's
kind
of
the
recommended
training
path.
Like
sure
we've
got
these
courses,
but
what
do
you
actually
need
to
go
from
zero
to
Rockstar
kubernetes
developer?
M
H
This
is
a
very
tricky
question
because
there
are
so
many
different
kinds
of
kubernetes
users
and
they
need
different
skills.
You
know
just
the
difference
between
a
cluster
administrator
and
a
developer,
who's,
creating,
say
some
application
that
might
have
two
or
three
deployments,
though
those
people
need.
You
know
quite
different
things
as
far
as
skills
and
understanding.
E
G
A
H
H
A
I
You
don't
get
much
response
where,
if
you
find
that
the
models,
so
the
only
thing
I
felt
concerned
about
the
models
is
there
was
so
much
work
to
try
and
get
the
models
to
actually
model
kubernetes.
It
worked
for
the
easy
stuff,
but
the
harder
stuff
it
got
real,
more
difficult
with
the
harder
stuff
that
I
didn't
want
that
to
derail
you
from
your
excellent
goals.
So
you
feel
like
taking
a
different
approach.
Please
have
the
freedom
to
to
take
whatever
approach.
A
But
yeah
thank
you
for
that.
I
also
want
to
concur
with
Brad
that
when,
when
you
drive
you
get
to
pick
so
take
the
approach
that
works
for
you
all
right.
That
is
our
quarterly
goal.
Review
yay
I'm
gonna
hand
it
over
to
Jim
to
lead
this
section.
I
need
to
drop
for
a
few
minutes,
but
I
will
be
back
in
10
to
15.
So
Jim
did
you
wait.
D
D
M
I
D
Think
the
takeaway
here
is
the
lesson
learned,
such
as
I
know,
Junyi,
one
of
our
Korean
localization
approvers
was
scheduled
due
to
that
process
and
then
they
said
hey.
We
can't
effectively
review
English
pr's,
given
the
nature
of
their
role
as
an
approver
for
the
Korean
localization
team.
So
I
see
this
as
being
lessons
learned.
Where
is
an
improvement
proving
process,
and
we
want
to
carry
forward
improving
that
I
think
this
is
also
puppies
and
kittens
yeah.
I
I
I
I
Yeah,
that's
a
really
good
point.
Think
that's
a
very
fair
point.
Kailyn
of
what
you
said
Zacks
not
here
for
the
few
minutes
vote.
I
recall
is
it
seemed
like
he
was
getting
from
above
the
TOC
or
whatever
just
they
listen.
We
need
to
be
a
little
more
proactive
about
removing
approvers
if
they're
not
participating
and
so
I
think
that
was
that's.
What
you're
saying
yeah,
but
but
a
process
in
place
would
be
better.
So
people
don't
go
what
happened?
Yeah.
P
C
P
So
we
need
to
be
flexible,
but
we
also
need
to
be
able
to
react
with
some
agility,
so
I
I
think
if
there's
ways
in
which
we
can
create
a
process
for
people
to
either
step
back
temporarily.
If,
like
I,
need
to
take
the
next
two
months
and
not
do
this,
they
maybe
do
a
hold,
and
then
people
who
are
going
to
drop
out
entirely.
We
should
create
a
process
for
that.
I
think
that's
a
good
goal
to
have
right
now.
I
And
just
just
just
just
for
accuracy,
I
mean
so
what
had
happened
was
the
the
motivation
to
pull
somebody
was.
There
was
no
way
to
get
a
hold
of
them.
It
wasn't
there
wasn't.
Oh
I
can't
do
my
PR
wrangling
this
week.
You
know
my
dogs
going
into
surgery,
something
it
was
literally.
There
was
no
way
to
reach
the
person
they
weren't
responding
and
and
then
the
way
that
that
Zaka
did
it
was
hey.
You
can
come
back
anytime,
so
so
it
was
an
implicit
temporary.
Just
just
just
to
be
clear.
I
D
You
awesome
yeah
I,
completely
agree
in
that
believe.
All
those
comments
are
very
accurate.
You
know,
I'm,
like
Brad
was
saying
that
you
know
when
folks
have
been
basically
removed
from
that
approvers
list
from
being
inactive,
they've
always
been
more
welcome
to
come
back
but
I
agree.
There
needs
to
be
an
explicit
process
to
find
so
there's
a
almost
a
precedent
for
how
we
handle
these
situations
and
how
we
move
forward.
There.
H
I
H
P
P
I
D
Anybody
want
to
take
on
the
action
item
to
make
this
a
little
more
of
a
formal
recommendation.
I
guess
we
can
vote
if
you
want
to
carry
it
forward
and
somebody
I
guess
we
need
someone
to
own
it
first
and
then,
if
somebody
wants
to
carry
this
forward
is
less
of
a
suggestion
or
a
feeling
that
we
have
on
this
quarterly
review.
Was
someone
willing
to
own
updating
our
fear
Wrangler
guide,
to
outline?
Maybe
this
posture?
D
O
D
D
All
right
moving
on
to
the
release
notes
process,
so
this
I
feel
like
can
go
a
few
different
angles.
So
today,
on
the
release
team,
the
release
notes
process
is
outside
of
Docs.
So
this
idea
of
handing
it
over
to
Sasha
I,
don't
believe,
is
necessarily
an
option,
but
I
do
know
on
the
kubernetes
website.
D
E
D
So
I
actually
worked
out
relatively
nicely
accept
away.
We
focus
most
of
our
time
on
the
very
first
issue
here
and
we're
chatting
about
the
improving
the
docks
process
for
the
PR
Wrangler
piece
and
after
having
a
conversation
about
how
we
can
deal
with
some
of
the
approvers
dropping
out
the
progress
handling.
Some
of
that
churn
are
the
long
and
short
of
it
is
that
Brad
stepped
up
to
own.
D
Improving
the
process
as
well
as
Brett
and
Jared
and
Steve
had
the
suggestion
to
allow
the
PR
Wrangler
to
make
an
executive
decision
to
merge
PRS,
even
if
they're,
not
exactly
in
line
with
the
style
guide,
with
the
action
that
they
would
open
up
an
issue
to
say,
can
someone
fix
this?
It's
a
good
first
issue
for
the
sake
of
merging
PR
fester,
for
the
sake
of
maybe
a
little
quality
degradation
to
improve
quality
of
content.
D
A
D
Happy
to
carry
on
cool
and
where
we
left
off
was
on
the
release
notes
process.
It's
possible
I,
misunderstood
what
this
last
item
was,
but
is
talking
over
handing
over
the
release,
notes
to
the
manager
to
Sasha
and
I
was
saying
that
there's
already
a
separate
release
team
for
for
the
release
notes
themselves.
So
it
doesn't
really
impact
sig
docks,
but
it
does
in
line
with
my
overall
efforts
to
improve
the
Sigma
X
release
process
where,
ultimately,
some
of
that
piece
would
get
automated
by
the
release.
Managers.
A
D
D
Aspect
so
my
take
was,
this
is
less
about
the
release
notes
process.
This
is
more
about
the
release,
notes
that
live
on
kubernetes,
that
I,
oh,
that
never
get
updated
and
I
can
update
this
to
be
a
little
bit
clearer
and
handing
that
over
to
more
automation
and
the
release
manager
group,
which
is
part
of
cig
release,
yeah.
A
J
Is
Raya
I
have
a
few
things
to
note
about
this
process.
So
I
was
part
of
the
118
release,
notes,
team
and
there's
actually
a
movement
to
automate
out
the
release,
notes
process
with
krell
and
for
119,
so
119
might
be
the
last
with
a
release,
notes,
team
and
there
might
be
a
way
sasha
has
been
doing
all
the
code
changes
to
to
krell
and
then
and
Adolfo
as
well.
To
make
to
further
automate.
J
A
I
think
that
the
discussion
in
November
was
to
put
more
attention
where
we
could
into
better
better
documenting
security,
documentation
and
bulletins,
so
I
think
like
Quesada,
AO
/.
Our
back
is
a
good
example
of
that.
Do
we
want
to
keep
doing
work
like
that,
with
the
understanding
that
it
will
need
that
specific
instances
of
improvement,
we'll
need
specific
people
to
drive
them?
Is
that
something
that
we
want
to
continue
doing?
I
would
say
yes
again
like
who
likes
puppies
and
kittens
so
I.
A
A
D
D
Karen
suggested
an
alternative
solution
that
I
haven't
had
time
to
review
properly.
That's
really
what
my
blocker
is
just
time,
but
this
piece
here
about
version
skew
and
alex
is
really
about.
What's
the
current
release
version
was
the
latest
supported
version?
What's
the
deprecation
process,
similar
to
what
you'd
see
on
kernel.org
or
Ubuntu
and
I
added
a
note
at
the
very
bottom
here.
If
you
were
to
go
to
Wikipedia
for
the
kubernetes
entry
and
I'll,
send
it
in
the
zoom
chat
here
they
have
a
better
release
timeline
than
arcade
stocks.
D
Do
so
they
actually
have
a
full
table
and
what
releases
are
deprecated
and
outlined
dates?
It
would
be
great
to
create
something
similar
to
that
or
maybe
link
out
to
that,
or
just
in
general,
be
as
good,
if
not
better
than
Wikipedia.
Sentry
as
the
official
source
of
tax
for
kubernetes
I
would
like
to
carry
that
forward.
B
A
B
B
A
A
O
A
B
A
B
I
A
A
We
also
have
new
tech
leads,
who
are
going
gangbusters,
Tim
and
Karen
Taylor.
We're
so
glad
that
you're
joining
us
I
will
admit
that
I
expressed
some
skepticism,
given
that
Taylor
is
also
their
release,
lead
for
1.19
I'm,
like
you
Billy.
You
have
time
for
all
of
this,
but
the
Energizer
buddy.
So
I'm
glad
we
have
you
welcome
Taylor.
A
A
I
I
I
F
F
F
I
I
E
E
D
F
Q
Q
R
I
I
A
A
D
D
A
P
P
P
We
have
maybe
health
concerns
of
our
own
and
I
just
wanted
to
set
expectations
for
folks
when
they
do
planning
this
quarter
and
possibly
next
quarter
that
you
pace
yourself
because
there's
going
to
be
requirements
that
are
asked
of
us
for
and
heroics,
possibly
that
are
asked
of
us
outside
of
kubernetes
and
give
yourself
the
space
to
rise.
To
that
occasion.
Should
you
need
to?
Would
you
take
a
mental
health
break?
Should
you
need
to
as
well
I'm
asking
folks
on
my
own
team
to
you
know
honestly
take
a
mandatory
one
day.
P
Every
month,
health
like
mental
health,
break
yeah,
take
one
every
two
weeks.
If
you
need
me
for
my
team
and
I'm
just
suggesting
for
folks,
that's
we
do
planning
here
to
maybe
not
go
for
heroics
in
the
particular
projects,
because
much
of
us
is
going
to
be
demanded
by
the
larger
world
in
our
work.
So,
as
we
put
these,
you
know,
goals
together
and
our
plans
for
the
quarter.
Definitely
keep
that
in
mind.
There's
a
larger
world
that
we
live
in
the
larger
world
is
going
to
need
us.
P
I
Yeah,
just
just
a
follow
on
that
Jared
I
know
lots
of
folks.
You
know
we're
just
to
give
concrete
examples.
You
have
both
folks,
working
and
and
now
they've
got
a
split
days
because
they
no
longer
have
childcare,
so
one
person
works,
Tuesday,
Wednesday
Thursday,
then
works
Monday
Friday
and
they
switch,
and
you
know,
including
myself.
I
My
my
son
is
now
home
all
day
until
May,
15th
and
I
can
I
can
just
tell
you
my
productivity
personally
is
not
at
the
level
as
it
was
before
all
of
this,
and
there
are
just
times:
I
have
to
take
time
to
actually
go.
Do
things
that
are
not
work-related
right
and
and
that
that
just
didn't
have
to
do
before.
But
if
I
don't
do
it,
you
know
wheels
are
gonna,
come
off
at
my
house
right,
so
I
think.
That's
really
really
good
advice
that
people
just
have
to
understand
be
comfortable.
I
Not
being
you
know,
so
many
of
us
are,
you
know,
comfortable
being
at
90
percent,
productive
hundred
percent,
productive,
maybe
a
little
more
than
I'm,
productive
and
now
we're
facing
I
can't
do
that.
I
can't
do
that.
This
quarter,
I'm
I'm!
More
70%,
productive
or
whatever
your
number
is,
and
you
just
have
to
just
not
to
just
really
take
the
good
advice
that
Jared
gave
to
heart,
because
it's
gonna
be
kind
of
rough
like
that,
and,
and
so
does
that
make
sense
sure
it's
just
kind
of
the
same
yeah.
P
P
A
A
So,
specifically,
to
and
I
want
to
scoop
that,
specifically
to
creating
the
umbrella
issue,
is
there
someone
who
would
be
willing
to
create
the
umbrella
issue
that
identifies
all
of
the
the
places
of
third
party
and
dual
source
content
in
the
docs?
You
don't
have
to
do
it
all
at
once.
You
can
build
off
of
the
work
that
Amy
already
did
and
the
pre-existing
PR
is
theirs,
but
is
there
someone
who
is
willing
to
open
and
own
that
issue?
Tim
I.
E
A
Yeah,
that
is
thank
you
that
is
very
accurate.
Just
because
this
cap
has
passed
doesn't
mean
that
the
people
whose
content
will
be
affected
will
like
it.
There
is
a
there's
gonna,
be
a
fair
amount
of
your
doing.
What
you
didn't
talk
to
me
about
that.
Why
wasn't
that
consulted?
I
have
very
strong
opinions
and,
as
we
go
to
implement
this
cap,
all
of
our
responses
need
to
be
oriented
around.
This
is
not
a
discussion
about
whether
this
will
happen.
It
is
happening.
A
So
one
thing
to
highlight
from
the
kept
discussion
is
that
we
offered
the
entirety
of
the
1.19
release
cycle
for
stakeholders
with
affected
content,
to
figure
out
what
to
do
with
their
content,
to
re-home
it
to
refactor
it
to
do
whatever.
So
this
will
not
be
an
instantaneous
process,
so
we're
looking
at
realistically
a
3-month
three
months
to
get
all
of
this
done,
that's
not
to
say
that
it's
three
months
worth
of
work
just
that
it
will
take
it'll,
be
three
months
before
we
can
cross
the
finish
line.
A
A
E
I
A
And
that
there
that's
not
ever
going
to
be
a
hard
list,
because
projects
are
moving
in
and
out
of
the
kubernetes
project.
So
you
read
that
content
guide
and
make
sure
that
then
you
know
what
those
guidelines
are.
If
you
have
any
questions,
ask
away
ask
away
in
github
issues:
ask
in
sigdoc
slack:
ask
on
email,
it's
better
to
surface
questions
than
to
let
content
through.
A
If
you
get,
if
you
say
once,
if
you
open
a
PR
to
remove
content
that
doesn't
conform
to
the
style
guide
or
to
the
content
guide
and
you
get
pushback,
please
let
me
know
or
let
one
of
the
chairs
know
again.
This
is
not
a
question
of
whether
all
of
that
has
been
decided.
Cig
architecture
has
got.
Our
back
steering
committee
has
got
our
back,
so
it's
not
a
question
of
whether
this
content
will
be
removed.
That
is
a
done
deal
if
anybody
tries
to
tell
you
oh,
this
is
too
important.
A
So
if
you
get
any
pushback,
if
anybody
has
CIL's
you
definitely
if
they
break
the
code
of
conduct,
let
us
know,
but
if
anybody
even
just
gives
you
a
hard
time,
please
let
us
know,
because
that's
not
something
that
you
need
to
to
take.
That's
not
something
that
Doc's
contributors
need
to
tank.
That's
something
for
the
chairs
to
do
so.
Don't
let
the
fact
that
this
I.
A
A
F
M
A
E
E
K
N
K
M
A
A
E
A
Let's
move
on
alright,
so
teaming
asks
that
we
discuss
this
particular
pull
request.
Nineteen
five
to
six,
if
I
remember
rightly
care
and
I-
think
you
probably
have
like
the
most
involvement
in
backgrounds.
I
wish
that
she
mean
could
be
here,
but
it's
like
3
a.m.
for
him.
So
Karen.
Are
you
comfortable
giving
like
a
summary
of
this
issue
because
there's
like
a
ton
of
a
ton
of
discussion.
F
But
I
do
have
a
problem
with
I.
Think
I
have
a
problem
with
sort
of
changing
the
way
authors
write
links
in
a
page
as
far
as
using
that
shortcode
and
so
there's
two
short
codes,
I
guess
and
I.
Guess
that
from
Hugo
also
chimed
in
at
the
bottom
of
this
issue
as
well
and
suggested
the
render
hooks,
which
is
like
web
hook
and
I've.
Actually,
I
did
a
little
test
of
that
and
that's
a
little.
It's
interesting
I
mean
I'm,
not
sure
that
that's
the
right
way
either,
but
I'd
love
to
know.
F
So
there's
some
examples
of
the
links
and
how
the
shortcode
modifies
the
links-
and
this
is
shown
you'd-
have
to
look
through
it
there's
a
lot
of
examples,
so
he
suggested
this
yeah
portable
Hugo
links
so
I,
don't
know
what
others
think
about
it,
but
I'm
not
completely
sold
on
either
issue.
You
know
either
either
a
solution
but
I'm
interested
to
hear
what
others
think.
F
F
Okay,
I
think,
there's
gonna,
be
we're
opening
ourselves
up
to
user
error
and
creating
these
links,
that's
my
biggest
concern
with
it.
There's
not
sort
of
one
way
of
saying,
hey
folks.
This
is
how
you
write
this
link.
There
seems
to
be
you
know
a
number
of
ways
you
could
write.
Lengths
and
I
think
it's
always
good
to
standardize
on
on
some
way
so
yeah.
E
Oh
yeah
I'm
not
getting
this,
and
if
people
can
hold
things
like,
if
you
can
hold
it
wrong
and
it's
detectable
and
there's
a
particular
way.
That
sounds
like
a
job
real
intern
I
wonder
if
there's
actually
a
hard
dependency
on
having
a
linting
system
in
place
before
we
adopt
this.
What
do
people
think.
M
I
think
we
should
be
linting
for
links
anyways,
even
though
it's
a
high-cost
activity
for
a
site
as
big
as
kubernetes
like
even
when
I
was
just
doing
the
contribute
section.
There
were
a
lot
of
links
that
were
super
duper
broken
and
had
been
broken
for
a
really
long
time,
and
you
know-
and
that
was
it
I
agree,
though
I
think
there
needs
to
be
some
kind
of
link,
checking
or
linting
which
will
open
this
up
to
a
Pandora's
box
of
horrible
things.
I
mean
solving,
but
we'll
be
good
to
solve.
D
You
know
I
did
want
it
in
real
quick
I
made
a
comment
there
saying
that
you
know.
Maybe
this
is
something
we
could
merge
and
iterate
on
top
of
Karen
you've
done
more
investigative
work
on
what
the
recommendation
from
Beth
was
so
I
don't
want
to
sound,
like
that's
the
preferred
method,
moving
forward
by
any
means.
D
This
is
somewhat
in
line
with
when
are
talking
about
being
a
PR,
angular
and
potentially
merging
and
iterating
on
top
of,
and
maybe
opening
an
issue
as
far
as
this
doesn't
have
to
be
perfect
out
of
the
gate,
my
opinion
was
more
or
less
that
it
doesn't
break
things
from
a
technical
perspective.
It
helps
out
localization
teams
in
a
minor.
D
You
know
area
here
if
it
works,
as
is
maybe
we
merge
this,
we
have
somewhat
of
a
fragmented
state
that
benefits
some
and
maybe
not
all
just
my
two
cents,
but
I
wanted
to
be
very
clear.
That
I
wasn't
saying
we
should
go
with
the
best
recommendation
or
we
should
do
an
alternative
way
and
also
my
LG
TM
is
more
or
less
saying
this
works
and
it's
a
solution
for
localizations
today
and
that's
about
where
my
opinion
stands
and
good.
To
get
that
you
know
and
hear
it
in
person
versus
a
github
comment.
I
guess.
F
You
know
I'm
well,
the
other
thing
is,
if
you
know
we
haven't
actually
seen
it
in
pragmatically
as
far
as
how
this,
how
the
translation
team
actually
use
it,
we
don't
have
an
example
of
a
changed
page
from
say
another
team
and
then,
if
the,
if
a
page
does
not
exist,
we
brought
this
up
on
the
issue,
whether
we
you
know,
there's
a
404
returned
or
we
create
another
page.
That
says
sorry.
This
content
is
not
available
in
this
language.
That's
that's
kind
of
a
separate
issue,
but
it's
part
of
this
issue.
F
I
think
my
biggest
concern
is
just
making
the
leap
of
saying
this
is
this:
is
the
approach
we're
taking
I?
Think
it's
good
to
kind
of
decide?
Yes,
we've
thought
it
through,
and
this
is
this
is
the
answer
and
moving
forward
versus
doing
a
piecemeal
approach,
I'm,
okay,
with
deciding
one
way
or
the
other,
but
just
to
make
a
decision
to
say
this
looks
good.
F
This
is
why
we
think
this
is
the
right
approach
versus
starting
on
something
and
saying:
oh,
we
got
to
back
out
five
files
or
you
know
that
sort
of
thing
and
letting
it
letting
a
translation
or
localization
team
take
off
with
it.
So
I
don't
know,
I
think
it's
worth
prototyping
or
figuring
out,
which
is
approach.
You
want
to
tank
I'll,
be
quiet,
no.
A
My
concern
with
adopting
this
approach
is
that
I
am
am
not
at
all
sure.
This
is
the
best
way
and
I'm
also
not
sure
that
the
best
needs
to
become
the
enemy
of
better
I.
Do
Tim
I
think
that
that
is
a
really
interesting
and
powerful
question
about
whether
there's
a
hard
dependency
on
the
presence
of
a
linter
and
to
make
this
work.
A
A
E
A
Although,
if
we
do
that
think
that
this
very
very
knowledgeable
and
very
strongly
opinionated
about
how
things
should
be
so
Karen,
if
you
have
any
reservations
at
all
about
the
rendering
hooks
approach,
now
is
the
time
to
express
those,
because
if
that
believes,
they're
right,
that's
what
that
will
direct
us
towards
a
contractor
to
do
so.
Like
are
you
comfortable
with
a
rendering
hooks
approach
versus
this
one?
F
B
A
So
I
think
one
question
is:
do
we
approve
this
now
or
not,
and
I?
Don't
think
that
this
is
a
simple,
yes
or
no
I.
Think
it's
yes,
yes,
and
no!
No,
and
and
based
on
what
I'm
hearing
in
the
discussion
so
far,
I
personally
am
leaning
towards
no
and
let's
not
approve
this
right
now
and
let's
do
the
investigation
to
find
out
what
it
would
take
to
approve
it.
So.
H
I
have
a
question
about
this.
This
is
a
naive
questions.
They
don't
really
understand
why
why
the
this
new
format
for
links
would
help,
but
couldn't
we
instead
of
putting
in
the
effort
into
formatting
all
of
our
links
in
this
way
have
someone
write,
write
tooling,
that
would,
as
a
kind
of
a
preflight
on
translation,
go
through
and
find
all
our
existing
links
and
convert
them
to
this
format,
and
then
they
would
be
translation,
friendly.
F
It's
a
good
question:
I
think
the
render
hooks
what
it
does
is.
It
does
a
rewrite.
So
it
applies
this
template
as
the
last
thing
and
the
processing
and
it
basically
converts
the
links
you
can
make
it
so
it
converts
the
links.
You
can
write
the
template,
it's
up
to
you
to
make
them
localization
friendly,
so
it's
possible
to
get
it
to
work.
It's
just
my
question
is:
is
it
the
right
way
to
do
this?
You
know
is:
do
we
have
sort
of
confirmation
that
it's
not
a
hack,
I'm
sure
it
can
be
done?
F
F
It's
a
template,
so
it's
basically
it
would
be
a
hugo
template
and
I
did
a
little
testing
in
another
issue,
not
a
PR
rather,
but
it's
not
I
didn't
complete
it.
I
just
basically
did
a
little
experiment
and
saw
how
the
template
could
work
and
it
does
a
rewrite
of
the
links,
but
I
didn't
actually
fix
the
template
to
do
the
inter
page
links.
So
if
you
have
like
a
you,
know,
links
within
a
page
that
wasn't
getting
rewritten,
but
it's
rewriting
the
link.
F
H
H
A
F
See
the
answer
I
think
it's
yes,
I,
think
this
issue,
or
this
pier
is
proposing
to
use
the
ref
or
real
ref
short
code
versus
their
that
brought
up
that
there's
a
new
render
hooks
or
web
box
as
part
of
a
later
version
of
Hugo,
and
that
is
in
that
case
you
basically
write
this
template.
It's
only
available
with
the
Goldmark
parser
and
the
template
basically
gets
read
through
and
it
goes
and
it
changes
the
links
according
to
what
you've
specified
in
the
template.
F
D
F
A
D
B
A
F
Okay,
so
this
I
think
in
the
Hugo
Docs
you'll
see
something
very
similar
and
there's
I
didn't
clean
up
this
file
entirely,
but
it
offers
the
main
part
is
the
rel
Lang
URL
is
what
I
added
in
and
the
rest
of.
It
is
pretty
much
what
that
provided
and
to
rewrite
the
link,
and
we
could
there's
some
I,
did
a
little
surfing
and
found
some
more
information
from
another
contributor
to
Hugo
about
adding
in
modifying
like
the
Lang
for
the
links.
F
So
the
if
you
noticed
in
the
pull
request
and
the
preview
that
I
provided
that
the
some
of
the
links
are
not
correct,
so
the
intra
page
links
are
not
correct,
so
that
would
have
to
be
changed.
The
template
would
have
to
change,
and
here
I've,
given
an
example,
he
gave
me
some
links
and
I
showed
him
how
they
were
actually
written
on
the
page
and
the
Chinese
page,
and
so,
but
the
you
can
see
the
page.
Let
me
see
so
these
are
all
rewritten.
They
used
to
be
just
Doc's
concepts
and
so
on.
A
F
D
F
D
A
A
That's
like
going
through
and
like
rewriting.
All
of
the
links
in
our
site
just
seems
like
a
really
cumbersome
fix
to
apply
a
short
code,
and
if
we
can
handle
that
all
through
templating
that
that
seems
like
a
much
better
way
of
preserving,
preserving
the
readability
of
markdown
and
I
guess
minima
minimizing
the
surface
area
of
things
that
can
be
damaged
by
the
upper.
A
So
it
sounds
to
me
like
you,
the
best
approach
is
to
say
no,
we
well.
We
recognize
that
this
is
a
problem
that
exists.
A
short
code
is
not
the
way
to
fix
it.
The
render
hook
approach
seems
preferable.
Yes,
we
will
have
to
update
Hugo
but
as
like
Jim
I
think
I
recall
you
mentioning
in
that
thread
that
getting
to
goldmark
is
preferable
anyway,
to
which
I
like
at
a
thorough,
+1
and
there's.
Also.
M
Just
just
one
out
onto
that
which
is
before
we
start
any
solution
to
the
translation
link
problem,
we
need
to
be
able
to
start
from
a
consistent
baseline
ie,
a
place
where
we
know
all
links
are
working
or
else
we'll,
never
know
if
anything
broke
because
of
the
because
of
our
little
templating
change,
so
I
don't
think
its
dependency,
but
I
think
it's
it's
there's
a
path
that
must
be
followed.
There.
A
A
F
Well
I'm,
just
my
only
concern
is
that
Jimmy
hasn't
had
a
chance
to
voice
his
opinion.
So
that's
my
only
thing,
I,
don't
say:
hey.
We
decided
this
sorry
for
your
ideas.
You
know
I,
think
I
think
it'd
be
worthwhile
to
at
least
clued
him.
You
know
and
saying
this
is
why
I
think
this
would
work
or
this
is
why
you're
you
know
it
shouldn't
work
so
anyway,
that's
my
only
reservation.
A
A
M
A
A
E
A
B
A
I
I'm
sure
this
shouldn't
take
long
at
all.
The
thought
process
here
would
be
to
to
be
more
proactive
at
trying
to
identify
candidates
who
you
know
if
they're
willing
to
put
in
the
time
could
be
put
on
a
path
to
becoming
say
an
approver
and
and
usually
the
difference
is
so
right.
Now
we're
more
sort
of
a
lazy
approach.
Right
people
show
up,
they
start
contributing
like
many
of
the
newer
folks
that
have
done
here.
They
do
a
great
job
and,
and
you
know
magic
happens,
they
become
an
approver
and
they've
done
it.
I
This
is
a
little
more
proactive
where
we
we
actively
try
and
get
the
candidates
and,
and
it's
a
little
more
formal
process,
a
listen.
If
you
come
join
us
and
you
start
learning
through
one
of
us
as
a
mentor.
You
start
learning,
you
know
our
style
guideline,
our
processes.
You
come
to
our
meetings
and
start
doing.
What
have
you
you'll
be
on
a
not
a
fast
path,
but
a
fairly
fast
path
to
become
a
reviewer
and
then
an
approver?
So
it's
it's
a.
I
We
say:
hey:
what's
up
I'm,
sorry,
a
well-lit
path,
a
well
lit
path
like
that
very
nice,
and
so
you
know
it's
it's
a
matter
of
sort
of
a
little
more
formalism,
because
the
people
understand
there
they're
actively
being
recruited
for
this
role.
For
example,
I
would
look
my
company
for
good
candidates
and
say
hey
if
you're
interested
in
understand.
I
This
is
a
big
commitment,
but
if
you're
interested
and
you're
willing
start
learning
the
ropes
and
we'll
get
you
a
mentor
from
one
of
the
either
a
tech
lead
or
or
a
chair
or
somebody
that
would
be
a
targeted
way
to
try
and
and
increase
our
number
of
say
our
reviewers
/
approvers,
and
sometimes
that
works
a
little
better
because
the
people
feel
like.
Oh,
these
people
really
really
want
me
and
really
want
to
me
to
succeed
and
I
just
need
to
put
in
the
work.
A
A
A
Being
more
consciously
and
intentionally
available
as
mentors
for
the
process
is
a
good
thing
that
said,
I
also
want
to
be
mindful
of
Jared's
advice.
To
us
to
be
really
intentional,
with
how
much
energy
we
have
to
be
like
meaningfully
available,
because
I
think
the
last
thing
that
would
be
helpful
right
now
is
to
promise
people
a
well-lit
path
and
then
not
do
the
work
to
light
it
I
think
that
would
be
more
harmful
than
being
sort
of
massively
available.
Did
that
make
sense?
No.
I
So
does
that
make
sense
so
I
wouldn't
necessarily
do
the
old
recruit
and
hand
off
like
we
all
think
Brad's
going
to
do
know
I,
but
but
but
just
to
have
that
mindset
it's
really
more
of
a
mindset.
So
just
like
you
are
doing
but
he'll,
you
know
you
would,
you
know,
be
Proactive,
hey,
I,
think
and
everybody
feeling
comfortable,
because
normally,
unless
we
say
hey,
that's
okay,
I,
don't
think
any
of
us
would
have
felt
comfortable
or
at
least
I
wouldn't
have
to
to
make
aspirations
of
hey.
Why
don't
you
come
work
with
us?
I
She'd
make
a
great
approver
there's
a
well-lit
path.
I
would
feel
out
of
place
to
be
that
proactive,
because
now
what
if
I
picked
some
crazy
person
right
and
then
you're
like
glad
you
brought
the
crazy
person
right.
So
so
it's
more
of
a
mindset,
saying
hey!
This
is
okay,
it's
okay,
to
kind
of
be
the
group
of
us
to
be
a
little
more
proactive
and
try
and
do
these
things.
I.
A
I
A
I
A
A
Reducing
any
and
all
barriers
to
participation
from
anyone
of
any
background.
That's
why
I
get
thank
you.
I
know
it
sound
like
a
broken
record
when
I'm
like
you,
I
need
to
script
myself.
I
need
to
script
a,
but
it
just
says
anytime.
Someone
says
guy
is
just
as
folks,
but
there's
a
reason.
Why
I
do
that
and
it's
because
language
matters
so
like
my
own
commitment
to
making
sure
making
us
an
inclusive
and
possible
environment
and
welcoming
environment
is
very
high
and
everything
that
I
know
of
our
co-chairs
and
leads
is,
is
likewise.
I
So
this
is
more
of
a
mindset.
I
will
personally
start
doing
this
I'm
going
to
actively
look
for
folks
and,
like
I,
said
it's
more
just
letting
them
know
we
really
are
trying
to
grow
our
numbers
and
and
you'll.
You
know
you
will
get
some
mentoring
and,
like
I
said,
I
can
just
take
ownership
for
what
I'm
willing
to
mentor
I
won't
promise
anybody
else's
cycles,
but
if
the
other
people
want
to
feel
that
way
too
or
if
somebody
says
oh
I
do
have
cycles.
I
L
B
D
Gonna
say
that
I
believe
there
also
might
be
a
more
passive
approach
going
back
to
Jarrod's
comment
earlier
about
not
everyone
having
the
ability
to
foresee
the
future
when
we
all
don't
know
really.
What's
going
on
and
everything's
pretty
unpredictable,
but,
for
example,
you
know
I
kind
of
linger
around
a
control
box
and
they
do
immediate
contributors.
D
I
think
it's
monthly
meeting
and
I
was
on
slack
while
they
were
talking
about
their
monthly
meeting
and
there's
a
lot
of
folks
out
there
who
get
into
contributing
kubernetes
at
more
advanced
levels
in
the
project
that
start
with
documentation
and
documentation
being
the
entry
point
for
them
to
contribute,
and
just
by
being
present
I
heard,
someone
make
a
comment
about
trying
to
start
contributing
and
I'm
able
to
send
a
link
to
the
site.
Saying
hey,
find
us
and
slack
over
here
or
here's
how
you
can
get
started.
D
I
don't
know
if
it
helps
anybody,
but
if
they
have
the
capacity
to
start
initiative
of
that
like
a
best
sort,
pretty
much
is
putting
it
out
there.
You
know
passive
ways
to
help
passive
ways.
I
hate
the
word
advertise
but
say
like
hey
we're
here
and
if
you
know
maybe
you're,
not
a
technical
expert,
and
you
can't
do
some
of
the
more
upstream
kubernetes
kubernetes
contributions.
D
If
you
don't
know
the
community
or
if
you
don't
know
what
sig
names
you
don't
know,
what
cat
means
all
these
kind
of
pretty
prerequisites
to
being
a
given
the
larger
community
doctors
happy
to
welcome
you.
As
you
know,
as
an
entry
point,
there
I
think
that
there's
there's
things
we
can
do
passively
to
encourage
that
and.
I
A
As
well
too
yeah-
and
it's
just
sometimes
it's
as
simple
as
saying
here-
we
are
Caitlyn-
is
like
I
think,
while
Caitlin
and
Steve
I
think
this
is
a
moment
for
video
to
shine
like
having
basic
videos
for
contribution
is
a
way
of
providing
a
well
lit
path
for
for
a
new
folks
to
come
in
and
join
so
Caitlin.
Do
you
have
any
any
thoughts
around
big
video
and,
like
smoothing
the
patch
for
new
approvers
yeah,.
C
I
mean
I
think
that
kind
of
intro
to
to
get
github.
All
of
that
is
really
the
one
barrier
we
see,
but
it
almost
seems
like
there's
room
for
more
of
more
introductory
videos
as
well
along
that
way
like
talking
about,
like
you
know,
if
people
don't
understand
even
what
a
cigar
is
like,
how
can
we
make
it
really
easy
for
them,
because
we'd
be
able
to
provide
a
video
to
teach?
You
is
a
lot
easier
than
me
dedicated
an
hour
of
my
time
to
get
you
up
and
running.
B
I
You
know
and
I've,
actually
my
role
is
gone.
More
digital
I've
actually
just
installed
a
tool
called
OBS,
which
is
you
know
for
streaming
and
and
recording
videos
and
allows
you
have
multiple
views
and
inserts
it's
a
pretty
cool
tool.
I
guess
all
the
video
gamers
use
it
or
something
not
me,
but
anyway
long
story
short
I
mean.
Certainly
you
can
think
about
just
making
short
videos
of
hey.
Let
me
just
show
you
where
our
style
guide
line
is,
and
let
me
just
show
you
a
few
things
in
the
style
guide
line.
I
If
you
haven't
seen
it,
we've
got
to
think
about
a
place
where
to
put
the
videos,
but
but
we
could
all
certainly
start.
You
know
just
taking
short
videos
of.
Oh,
let
me
show
you
our
issue
list
and,
or
you
know,
good
good
first
issues
so
I
mean
obviously
I
coordinate
with
you
Caitlin,
but
but
but
some
thoughts
there.
If
there's
different
parts
of
our
you
know,
even
just
showing
them
hey
did
you
know
you
can
go,
see
the
docs
and
try
them
in
all
these
different
languages.
Things
like
that
things.
M
Yeah
I'm
more
convinced
about
this
idea
of
an
introductory
video
as
I
hear
more
and
more
about
it.
I
just
like
want
to
put
that
out.
There
cuz
I've
been
on
like
that
yeah
video
side
of
this
debate
for
a
while,
the
more
I
hear
about
it,
the
more
you're
making
the
case
this
I
guess
the
question
I
have
is
like
I.
A
M
I
A
D
This
this
would
be
really
quick.
Hopefully
it's
really
just
looking
for
alignment
here.
While
we
have
all
the
folks
on
a
call
saying,
do
we
want
all
the
pain
now
or
do
we
want
all
the
pain
later,
and
what
has
happened
is
that
we're
about
ten
versions
behind
of
updating
our
hugo
version
and
we've
created
a
PR
to
update
to
the
latest
hugo
version,
which
takes
a
new
default
markdown,
a
rendering
engine
called
gold
mark,
and
it
breaks
a
lot
of
stuff.
D
Yet
so,
there's
a
there's:
the
ability
for
us
here
to
ease
some
of
the
pain
to
get
to
a
later
version
for
the
sake
of
not
falling
further
behind
or
the
vote
is,
let's
go
to
gold
for
gold
Friday
now
I'm
combining
the
two
mark
deal
with
the
pain
and
some
things
might
break,
but
kind
of
the
breaks
makes
make
an
omelet
saying,
I
think
rings.
True
here,
chimp
forgive.
A
D
The
safe,
unsafe,
correct,
yeah,
so
so
gold
mark
by
itself
has
two
options
to
run.
One
is
safe
and
one
is
unsafe.
The
real
difference
is
is
that
the
unsafe
allows
you
to
put
scripts
embed
it
into
your
markdown
documentation
and
when
you
put
that
script
in
your
markdown
documentation,
the
idea
is,
somebody
could
inject
something
malicious
into
your
code
by
adding
a
malicious
script.
So
that's
what
the
whole
safe
versus
unsafe
option
is,
but
then
both
versions
on
top
of
the
whole
safe
scripts
versus
unsafe
scripts.
They
also
disable
pure
HTML
files.
D
So
what
that
means
is
that
all
of
our
API
ref
dens
break
everything.
That's
pure
HTML
breaks.
If
it's
not
marked
down,
it's
gonna
be
broken
and
that's
all
of
the
metla
fire
warnings
that
we've
been
getting
to.
Yes,
that
I'm
not
entirely
sure
but
I
believe
that
the
separate
real
okay,
bernetta,
five
right
yeah.
Thank
you.
Sorry
I.
My
brain
yeah,
no
problem
so
so,
like
I
said,
while
I
have
everybody
on
the
call,
if
we
say
Black
Friday's
out
good
riddance
all
right,
so
then
we're
gonna
go
forth.
D
A
A
So
one
thing
that
comes
to
mind
is-
and
this
is
an
unrelated-
a
tangential
e
related
issue
is
once
Doxey
is
applied.
Then
we
can
look
at
my
greening
our
API
reference,
those
swagger
Doc's
that
would
get
them
out
of
HTML
and
into
a
more
renderable
format,
pain,
but
I
think
it
may
be
worthwhile
to
do
the
do.
The
upgrade
version
that
allows
us
to
operate
unsafely.
A
D
Not
and
when
I
say
that
I
mean
you
could
write,
hTML
is
like
a
template,
I
guess
generated
at
the
end
there.
At
the
end
of
the
day,
everything
is
generated
as
markdown
and
presented,
but
if
we
created
a
pure
HTML
file
somewhere
in
the
site
and
embedded
it,
it
will
show
up
as
just
plain
text.
It
won't
show
up
as
a
generated
HTML
page
so.
G
H
I
I'm
so
sorry
that
I
helped
usher
in
that
gigantic
HTML
API
reference
page
with
what
I
would
have
with
what
I
know
now,
when,
when
the
person
proposed
that
I
would
have
just
said
no
for
whatever
that's
worth
it
just
was
not
a
good
idea.
It's
caused
all
kinds
of
problems
and
here's
another
one.
Yeah.
D
A
H
Of
broad
question
here,
how
do
the
rest
of
you
feel
about
this
when
I,
when
I
hear
that
we're
using
Hugo
and
Hugo
has
made
the
decision
that
they
will
not
support?
Html
pages
that
to
me
seems
unbearable.
You
know
that
that
just
seems
like
what
are
we
thinking
to
go
with
a
tool
that
would
put
that
restriction
on
us?
Do
the
rest
of
you
share
that
outrage,
or
do
you
just
think
this
is
the
way
things
are
I
agree.
C
D
A
good
move
and
the
reason
I
say
that
is
that
if
you
want
to
be
a
markdown
rendering
engine
and
your
markdown
is
not
only
rendering
you
know
more
than
just
markdown
I
believe
the
scope
might
have
been
too
wide
to
begin
with,
and
you
know
it's
more
of
a
mm-hmm
as
things
evolve,
it's
a
more
of
a
safe
approach,
pure
HTML
or
not
pure
markdown,
getting
rendered
by
pure
markdown
rendering
engine
to
HTML
makes
a
lot
more
sense
than
a
markdown
plus
HTML.
Getting
rendered
down
into
that.
D
And
then,
additionally,
to
that,
you
still
are
able
to
create
your
templates
in
your
short
codes.
You
just
aren't
able
to
have
a
markdown
content
source
for
the
end
result.
So
they're
saying
use
our
product
the
way
it
should
be
used
and
I
said
a.
But
but
that's
my
opinion
is
that
this
is
a
direction
to
be
a
little
bit
more
secure
a
little
bit
safer,
a
little
bit
cleaner,
but
it's
kind
of
a
slap
in
the
face
I
mean
I.
Will
I
will
give
everybody
that
but
I'm
kind
of
for
it
and.
M
Well,
no
I
didn't
want
to
override
Jim
too
much
so
because
of
my
position
in
the
C&C.
If
I
work
with
a
lot
of
other
humor
sites
and
a
lot
of
the
other
hugo
sites
in
the
scenes,
TF
are
on
more
recent
versions
of
Hugo.
So
I've
dealt
with
this
issue
and
a
couple
of
other
repos
already
and
I
echo.
What
Jim
says?
Is
it
really
forces
you
to
use
better
development
practices?
M
M
However,
it
gets
really
complicated
for
websites
like
this
one
when
you
have
like
the
API
reference,
where
the
content
just
happens,
to
be
an
HTML
format,
because
that's
how
we
could
export
it
and
then
you
suddenly
have
to
get
into
this
place
of
like
do.
We
develop
a
pipeline
to
render
JSON
into
like
a
like
markdown
so
that,
like
it,
gets
really
weird
there
so
I
think
it's
the
right
direction.
Well,.
A
I'm
sorry
I
need
to
time
box,
I'm,
sorry,
I'm.
So
sorry
I
need
to
time
box
this
discussion
because
we've
got
five
minutes
left.
We
can't
break
the
reference
page
in
production.
That's
we
just
cannot
do
it
without
a
very
clear
pant,
very
clear
pain
without
a
very
clear
plan
for
how
we
are
immediately
going
to
fix
it.
So.
A
H
H
F
I
agree:
I
was
just
looking
at
Jim
it
your
to
PRS
and
I.
I
could
have
sworn
I
looked
at
the
previews
and
check
it
out
and
that's
right,
I
post
a
little
question
as
far
as
you
know,
is
it
just
HTML,
that's
embedded
that
the
processor
complains
about
if
the
the
reference
is
just
a
link
in
a
markdown
page,
so
I'm
not
100%
sure,
that's
true,
but
I
think
it
might
be
true
same
thing
with
the
cube
Caudill
reference.
D
A
A
C
A
Ok,
everyone
do
your
homework
and
we'll
come
ready
to.
Let's
come
ready
to
discuss
specific
plans
of
action
for
how
to
go
forward
with
this
on
weekly
meeting
on
Tuesday.
All
right,
normally
I
would
ask
for
more
business,
but
we're
out
of
time.
So
thank
you.
Everyone
really
good
participation,
really
good
feedback
and
input.
This
is
what
makes
this
SIG
work.