►
From YouTube: K8S SIG Docs Meeting for 20220419
Description
For more info see https://git.k8s.io/community/sig-docs
A
A
Everyone
hi,
my
name,
is
Natalie.
One
of
the
co-chairs
here
of
seek
docs.
Welcome
to
today's
sync
docs
community
meeting,
it's
the
19th
of
April,
a
very
sunny
Tuesday
here
in
in
Berlin
Germany
and
wherever
you
fix,
are
I
hope
the
weather
is
lovely
too,
and
we've
got
a
we've
got
a
very
short
agenda
today,
but
I
think
we
can
power
through
it.
I
think
I
think
we've
got
some
decent
stuff
to
discuss
thanks.
A
Everyone
for
taking
part
in
the
community
meeting
do
want
to
just
make
sure
that
everyone's
aware
of
our
code
of
conduct
guidelines
that
we
follow
here
for
the
kubernetes
project,
let's
all
be
respectful
and
awesome
to
each
other,
and
with
that
with
that
kicking
off,
let
me
quickly
share
my
screen
being
honest.
Being
on
a
single
monitor
today
is
a
lot
of
fun,
alrighty,
and
so
would
that
be
the
case.
A
I've
got
the
agenda
up
here
and
would
love
to
get
started
by
seeing
if
we've
got
any
new
contributors
who
are
joining
today.
That
would
like
to
say
hello.
A
Going
twice
already
for
anyone
who
is
new
I
might
quickly
write
a
message
in
here
that
feel
free
to
add
your
add
your
names
and
say
hello.
A
And
we
definitely
had
some
folks
joining
the
channel
lately,
so
we
might
go
give
them
a
virtual
hello
later
on
alrighty.
Firstly,
quick
update
in
terms
of
our
PR
English
shifts.
A
We've
got
Divya
who's,
our
PR
angular
for
this
week
and
and
she's
already
been
diligently
jumping
onto
some
PLS
already,
and
next
week's
PR
Moringa
we
have
is
Jim
with
darshana,
is
going
to
be
a
shadowing
for
anyone
who's
on
the
call
that
is
interested
in
the
pr
shadowing
program,
definitely
reach
out
to
any
of
us
leads
or
to
Brad
and
Abby
and
we'd
be
able
to
pop
you
on
to
be
able
to
Shadow
one
of
our
PR
Wranglers.
A
It's
a
really
it's
a
it's
a
job,
that's
a
really
something
that
helps
us
push
a
contribution
through
in
the
Sig
and
really
helps
to
kind
of
get
PR's
to
the
place
that
they
need
to
be
and
the
reviews
that
need
to
happen
so
that
we
can
accept
a
bunch
of
contributions
if
you're
interested
in
understanding
how
that
works,
definitely
jump
onto
the
shadowing
we'd
love.
We
love
to
have
you
and,
with
that
being
the
case,
let's
jump
over
to
the
next
part
of
the
agenda.
A
B
Hello
awkwardly
for
the
star
position:
we
have
planted
our
release
date,
so
I
think
it's
official
now
I
think
that
it
has
been
sort
of
in
the
works
for
a
couple
of
weeks,
but
we
have
had
an
upstream
issue
with
one
of
the
go:
golang
security
bugs.
So
we
have
had
to
push
our
release
date
from
April
19th,
which
was
going
to
be
yeah
today,
two
May
3rd
I
believe
it
was.
The
new
is
the
new
date
for
the
most
part.
B
This
actually
I
think
helps
the
docs
a
little
bit.
We
do
have
one
PR
still
open
that
I
think
I
I
have
noted
it
here.
B
It's
in
a
position
where
it's
had
its
technical
looks
good
to
me,
but
I
I
think
that
there
have
been
some
questions
about
the
clarity
of
the
the
docs
update.
So
if
you
have
time
and
are
interested
in
helping
shape
some
of
the
documentation
here,
this
particular
issue
has
had
some
feedback,
but
I
think
could
use
some
help
with
the
clarity
of
the
copy,
so
other
than
that,
though,
we've
had
39
complete
and
five
still
no
dash
required.
B
So
those
are
in
a
good
position
going
into
I.
Think
Ray
and
Tim
have
put
some
notes
in
for
me
here.
The
quote:
there
is
I
believe
from
Stephen
Augustus
release.
Dates
are
aspirational,
so
we
we
are
aiming
for
May
3rd,
but
because
we
have
an
upstream
issue
that
we
can't
really
control.
We
we,
if,
if
it
if
the
I,
believe
it's
golang
18.1.
If
that
doesn't
solve
our
problem,
we
may
have
to
punt
again,
and
that's
that's
okay.
B
So
that's
where
that
is
Ray,
I!
Think
v125!
Here!
That's
your
note.
Would
you
like
to
speak
to
it?
Yeah.
C
Since
the
124
release
has
been
delayed
and
of
course
really
states
are
aspirational,
the
125
starts
release
cycle
starts,
dates
has
been
delayed,
also
so
I
and
it.
The
dates
are
currently
under
discussion.
So
don't
have
a
any
set
dates.
C
We
did
discuss
starting
the
release
in
May,
2nd
also
on
May
9th,
so
that's
still
and
that's
still
pending,
but
if
you
do
want
to
become
a
shadow
on
the
release
team
and
a
shadow
or
a
shadow
on
the
docs
or
other
shadow
on
the
really
stocks
team,
the
application
is
open
until
April
29th,
so
I
did
paste
that
link
on
the
agenda.
If
you
please
fall
out,
if
you're,
if
you're
interested
in
becoming
a
shadow
or
dark
shadow
for
125.
B
Thank
you
and
I
I
I,
plus
one
that
I,
it's
I,
think
a
great
way
to
learn
the
the
documentation
and
the
the
the
system
we
we
tend
to
try
to
have
folks
in
as
Shadows
who
haven't
necessarily
been
Travelers
before
who
aren't
necessarily
experts.
So
we
have
two
generally
senior
and
two
sort
of
Junior.
B
B
B
So
we
need
to
update
I
believe
this
has
to
do
with
configuring
cni
and
ensuring
that
the
information
that
we
are
reporting
doesn't
break
existing
configurations.
I,
don't
know
if
Mike
Brown
is
on
the
line
here
or
Tim.
Maybe
you
can
speak
to
this
a
little
bit
more
eloquently
than
I
can.
D
So
well,
there's
there's
two
things
that
came
up
in
the
same
discussion,
so
30898
I'm,
not
sure
is
that
a
blocker?
It
depends.
We
we
mentioned
Docker
in
the
page
about
cnis
and
30899
is
saying:
well,
we
shouldn't
really
mention
Docker.
We
shouldn't
use
an
example
of
a
container
runtime
and
so
on.
I
think
you're.
Also
talking
about
the
issue
that
Mike
Brown
raised
with
containerdy,
specifically
and
and
research.
D
So,
to
summarize,
the
challenge
we're
we're
telling
people.
Oh
you
know
you
need
to
move
away
from
Docker
via
dockershan.
You
could
use
cni
doctor
D.
If
you
sorry
CRI,
doctor
d
wrong
bit
of.
D
If
you
want
we're,
not
stopping
you,
other
container
run
times
exist
and
there
is
a
hint
that
we
are
giving
people
a
bit
more
of
a
steer
towards
container
day,
which
is
problematic
because
the
latest
container
date,
if
you
upgrade
it-
and
you
have
certain
ways
of
setting
up
your
cluster,
which
are
entirely
supported
with
kubernetes
1.23.
You
can
end
up
with
all
your
nodes
unhappy
because
you
have
inherited
an
early
cni
configuration
which
containerdy
doesn't
like
and
I
hope
that
an
issue
is
going
to
come
out
about
that.
B
And
you're
right,
I
think
I
I
linked
to
this
one,
because
that's
the
one
that
triggered
the
the
conversation
I'm,
not
sure.
We've
got
a
new
issue
yet.
D
For
clarity,
mate
can
I,
can
I
add
another
thing
please
so
I
mean
my
understanding
is
that
you
know
if,
if
you
were
being
a
lawyer
about
this,
which
I
don't
intend
to
be
other
than
for
clarification,
kubernetes
says
we
support
cni
version
0.4.0
of
the
spec,
and
that
is
what
the
project
uses
now
the
spec
has
moved
on.
There
is
now
a
one-point
note,
cni
spec,
but
kubernetes
is
still
expecting
configurations
between
0.4.0.
D
D
That
is
just
for
context.
I
am
not
saying
people
shouldn't
use
container
D
I'm,
just
saying
it
kind
of
explains
where
things
are.
B
So
that,
thank
you,
Jim
for
the
explanation,
I
think
that's
sort
of
where
that
is.
We've
got
an
actual
conversation
in
the
release.
Docs
Channel
around
this,
so
we
are
we're
on
it
and
we're
hoping
to
get
this
sorted,
but
I
figured.
It
was
important
enough
to
bring
to
the
table.
A
Awesome
Nate
thanks
and
we
will
have
a
we'll
have
a
slack
update
meeting
for
next
week,
so
maybe
we
can
also
follow
up
in
in
in
our
slack
updates
for
next
week,
if
need
be,
but
yes
great,
that
a
great
that
we've
put
that
conversation
over
to
release
doc,
so
the
writer
write
folks
can
get
their
eyes
on
that
thanks.
So
much
alrighty
thanks
for
that
update,
everybody
I
was
taking
notes
just
quickly
on
the
side,
so
feel
free
to
jump
in
and
edit
any
any.
A
E
Okay,
very
good,
so
I've
been
through
this
a
lot.
I've
tried
all
the
different
suggestions
and
some
of
my
own,
some
of
my
own
doing.
It
seems
that
we
might
still
have
a
problem.
I
did
run
through
a
couple
of
things
with
chrome
and
I
am
able
to
you
know
if
I
bang
away
at
the
reload
a
bunch
of
times,
I,
don't
know
how
realistic
that
is,
but
I
do
get
a
a
chrome
air
Chrome
error
as
well.
E
Like
I,
said:
I
tried
all
the
different
permutations
of
mermaid
releases:
I,
updated,
8,
14,
0,
9.0.0
I've.
Also.
C
E
Up
an
issue
with
the
mermaid
team
as
well,
you
know
I,
don't
know.
If
is
this
really
an
issue?
You
know
it
seems
that
you
know
something
like
this.
You
know
may
occur
with
you
know
if
you're
browsing
really
anything
that
has
inline
code
and
that
has
to
sort
of
put
it
together
during
a
building.
I,
don't
know
I'm
just
looking
to
the
team
for
some
guidance
to
see
how
we
want
to
take
this
thing
forward.
E
Do
we
fling
it
over
to
someone
else
in
in
web
development
land
to
maybe
take
a
look
at
it.
A
I
think
that's
a
great
question.
I
think
it's
great
that
you've
raised
the
issue
with
the
mermaid
project
itself.
I
think
we
discussed
this
on
slack
last
week,
where
I
did
a
quick
look
through
the
issues
that
that
were
that
were
up
for
the
mermaid
folks
and
it
didn't
look
like
anyone
had
really
posted
anything
of
significance
going
on
on
the
Firefox
side
in
terms
of
errors
and
bugs
so
I
think
that's
great.
A
It
would
be
awesome,
feel
free
to
do
this
later.
If
we
could
have
a
link
to
that
issue
specifically
in
the
in
the
agenda
here.
A
If
you
don't
mind
bringing
it
up
from
the
mermaid
side,
and
we
can
add
that
in
but
I'm
of
the
opinion
and
I'm
definitely
happy
to
be
overruled
here-
that,
if
we've
a
lot,
if
we've
put
in
an
issue
Upstream
to
the
mermaid
folks
being
able
to
just
let
folks
know
that
we
we're
aware
of
the
issue
and
we're
hoping
to
work
with
the
mermaid
team
to
try
and
resolve
things
at
the
moment
and
see
how
it
goes
for
a
week
or
so.
E
All
right
so
I
just
remember
one
thing:
I,
don't
know
if
I
put
it
in
the
notes,
but
one
of
the
folks
did
say
I.
Think
of
another
issue
that
quote
unquote.
This
Behavior
has
been
observed
on
occasion
when
the
browsers
have
a
a
bunch
of
add-ons.
A
Yeah
but
at
the
same
time,
I
wonder
and
I'd
love
to
hear
Tim
and
Ray,
maybe
Abby
what
you
think
about
this.
Is
it
worth
us
putting
up
that
same
information
that
you
made
some
mermaid
docs
may
not
may
not
load
due
to
add-ons,
but
not
making
any
recommendations,
really
just
stating
something
there
from
the
project
that
they've
also
shared.
E
E
That
sort
of
thing
that
that's
just
my
only
fear
and
I
don't
know.
If
people
will
remember
to
put
the
the
live
editor
links
so
that
folks
can
play
around
with
it
if
they
generate
an
SVG
and
then
dump
it
into
the
documentation.
C
Yes,
so
I
I,
don't
like
the
fact
that
and
I
don't
know
if
we
could
say
that
if,
if
your
browser
has
it
has
a
number
of
add-ons
that
or
that
you
need
a
separate
browser
environment
to
to
view
the
kubernetes.io
documentation
sites
correctly
I,
it
just
doesn't
feel
right,
but
I
don't
I.
Also
don't
have
that
forward.
To
be
honest
at
the
end,
I
don't
have
a
recommendation
yet
I
have
to
wrap
my
my
head
around
this
a
little
bit
more.
E
E
Again,
oh
okay,
moving
away
at
the
reloads
and
you
know
see
if
I
I
can
generate
the.
E
There
is
what
was
it
shift,
controller
or
shift
reload,
and
that
seemed
to
clear
up
the
the
Firefox
problem.
E
Also
I,
you
know,
I
checked
it
out
on
localhost
as
well
or
check
it
out
locally
and
then
I
deployed
a
a
preview
and
I
could
recreate,
or
at
least
I,
observe
the
same
behavior
in
in
both
environments.
D
For
my
part,
I
use
Firefox,
as
my
as
my
main
browser.
It's
got.
Some
features,
I
really
like
I
can
reliably
see
a
broken
diagram
if
I
go
to
say
the
Ingress
page
and
if
I
force
a
Reload
I
can
reliably
not
see
a
broken
diagram.
D
This
this
gives
me
an
idea
we
could
put.
We
could
we
could
use
a
layout
or
some
mechanism
to
look
or
JavaScript
to
tell
people
hey
now
you're
using
Firefox,
we're
pretty
sure
it's
Firefox
that
you're
using
and
this
page
has
a
shortcut
in
it.
That
is
broken
so
I'm.
You
know,
unfortunately,
there's
there's
a
bug
and
leave
a
link
to
the
issue
and
say
you
know
we're
working
on
it.
E
Yeah
that's
a
possibility.
I
was
also
thinking
that
if
we
could
maybe
get
to
the
mermaid
folks
and
and
point
to
this
problem
that
maybe
they
could
put
something
in
their
you
know,
syntax
error
message
or
something
saying:
hey
I,
don't
know
I'm
trying
reloading
to
to
see.
If
this
error
goes
away.
D
I
mean
we
can
do
that,
one
of
the
things
we
could
do
so
I
mentioned.
We
could
tell
people,
there's
a
problem
but
I'm
not
really
proud
of
suggesting
this,
but
we
could
detect
the
error
and
force
a
Reload.
If
we
found
that
fixed
the
issue
we
could,
we
could
have
that
we
could
write
our
own
JavaScript
code,
sort
of
30
lines
of
JavaScript
that
triggers
a
Reload
when
needed.
E
E
So
in
the
meantime
again,
the
the
mermaid
issue
has
been
the
issue
with
mermaid
has
been
raised.
I
also
threw
in
the
fact
that
we
love
mermaid,
we're
using
it
in
kubernetes
docs.
Maybe
that
gives
it
a
little
bit
of
weight
or
priority.
A
Yeah
I.
Definitely
when
I
was
looking
looking
at
the
project
the
other
week
as
well.
It
does
have
a
decent
amount
of
contributors,
but
they
do
also
call
out
very
similarly
like
we
do
funnily
enough
in
big
dogs
that
new
contributes
or
contributors
always
welcome,
and
there's
lots
of
things
to
work
on
and
to
do
so.
A
I
think
trying
to
see
how
how
we
can
invite
this
issue,
which
you
love,
which
is
great
trying
to
see
how
else
that
we
can
help
out
rather
than
completely
putting
the
the
error
in
their
court
so
to
speak,
and
what
else
we
can
we
can
do
to
help
might
be
worthwhile
I
think
it's
great
that
you've
called
out
that
we're
using
in
the
project
so
yeah
similar
to
Rey
I,
even
though,
in
my
own
suggestion
of
mentioning
that
you
know
extra
add-ons
or
someone
could
actually
Place
problems.
A
I
also
don't
feel
like
that
feels
like
the
right
thing
to
do,
and
yeah
I'm
a
little
bit
stuck
over
else
what
else
to
kind
of
what
else
to
kind
of
action
on
at
the
moment.
Until
we
get
a
bit
more
into
the
issue,
there.
E
D
A
Hi,
very
sorry,
as
soon
as
you
started
speaking,
we
lost
you
there
for
a
sec.
D
Okay,
we've
got
the
short
code,
we
could
add
some
localizable
text
to
the
short
code
to
say
by
the
way,
if
this
doesn't
work
due
to
a
bug,
it
might
not
try
Ctrl
shift
r
or
command
shift
R
if
you're
on
a
Mac
foreign.
That
would
be
a
good
first
issue,
I.
Think
like
yeah,
it's
it's
just
on
the
you
know,
it's
a
it's
a
it's
a
stretch
for
a
good
first
issue,
but
I
think
it's
a
good
first
issue.
How
about
we?
We
follow
that.
A
E
So
so,
when
we
have
the
short
code
for
an
inline
mermaid
diagram,
it
builds
it.
But
now
where
might
we
put
that
little
message.
D
D
D
D
Could
actually
use
some
CSS
right?
This
is
thinking
out
loud,
but
I
reckon
we
could
use
some
CSS
to
only
show
to
hide
that
if
it
doesn't
follow
a
broken
diagram.
D
I
mean:
do
you
mean
what
selector
would
you
write?
I'd
I'd
have
to
think
about
that
I.
Don't
know
off
the
top
of
my
head,
but
CSS
has
this
mechanism
called
selectors?
Where
you
can
you
can
you
can
write
queries
like
am
I
a
paragraph
following
a
heading
that
is
in
a
different
language
to
the
paragraph,
the
main
body
text
things
like
that
some
of
those
are
fairly
Arcane
to
write
and
some
of
them
are
pretty.
D
What
do
you
want
to
do?
I'm,
I'm
discussing.
E
A
F
Yeah
I
think
I
think.
If
a
lot
of
people
are
seeing
this,
then
we
should
get
something
out
there
in
front
of
people
faster
and
if
it's
going
to
take
longer
to
figure
out
the
CSS
hiding
trick.
If
that's
really
fast
like
we
can
get
that
done
quickly,
then
we
could
do
that,
but
I
think
for
like
just
getting
it
out
there.
If
a
lot
of
people
are
seeing
this
and
there's
a
lot
of
confusion,
then
maybe
having
something
on
every
diagram
isn't
an
issue,
and
then
we
can
follow
up
with
them,
making
it
improvements.
E
So
people
are
able
to
recreate
this
problem
right.
We
don't
want
to
put
a
survey
out
there
and
then
call
attention
and
I.
You
know
and
Miller
made's
broken
for
a
while
I
guess,
I
won't
use
it.
A
Well,
yeah
I,
don't
think
we
I,
don't
think
we
want
to
call
attention
to
that,
because
it's
not
broken
in
every
context
and
and
for
for
everyone
necessarily
as
well
and
so
I
think
and
we've
definitely
seen,
especially
in
the
in
the
main
issue.
That
was
that's
been
logged
about
this.
A
few
folks
being
able
to
recreate
there.
A
Is
there
so
I
believe,
there's
enough
Recreation
to
to
Warrant
us
to
put
that
first
issue
that
that
issue
out
as
a
good
first
issue,
like
you
said
just
a
Tim
I
really
like
that
idea
and
for
us
to
perhaps
actually
share
that
in
the
in
the
channel,
as
this
is
an
issue
that
we
as
a
community
really
want
to
prioritize,
because
it's
something
that
we
actually
want
to
solve
pretty
quickly
and
the
calling
for
folks
who
maybe
want
to
work
on
this.
E
Yeah
I'd
like
to
work
on
it,
so
so
the
solution
is
at
this
point
in
time
is
to
number
one
open,
an
issue
for
a
enhancement
to
the
short
code,
to
indicate
that
when
there
might
be
a
problem,
you
know
hit
shift
reload
number
two
I'd
like
to
put
something
in
in
the
diagram
guide,
since
that's
sort
of
our
first
foray
into
guiding
the
community
towards
diagrams
and
I'm
again
I'm
concerned
that
folks
may
become
discouraged
or
think
that
you
know
mermaids.
E
You
know
broken
number
three
I
guess
pursue
that
issue
with
the
mermaid
folks
and
and
see
what
see
what
the
deal
is
and
I
guess
number
four.
We
want
to
broadcast
something
out
on
Sig
doctor
slack
to
indicate
that
we're
working
on
this
but
keep
using
mermaid.
It's
it's
something.
That's
you
know
shouldn't
just
it
shouldn't
dissuade
you
from
from
using
it.
The
diagrams
are
important,
so
keep
it
up.
A
Yeah
I
love
all
of
those
anyone
else
with
any
further
suggestions.
I
think
that's
great.
D
A
couple
more
things
we
could
do,
we
can
apply
to
the
cncf
and
say
we
need
help.
We
would
like
to
apply
from
some
CF
cncf
resources
to
sort
this
I
I
would
very
much
we.
We
did
that
for
the
docker
Shin
removal
and
I
think
that
was
justified.
I,
don't
think
this
is
as
just
this
is
as
clearly
Justified
at
request,
but
we
could
do
it.
That
is
a
thing
we
can
do.
D
D
Yeah
and
it's
actually
older
than
Java,
which
is
great
and
yeah
we
could
see
if,
if
someone
who's
like
oh
yeah,
no
I
can
take
a
look
at
this.
We
can.
We
can
match,
make
the
the
contributor,
with
with
the
capacity
to
the
the
bug
that
needs
fixing.
E
Maybe
reach
out
to
First
contributors,
I'm
sure
that
some
of
these
young
Engineers
have
experience
in
JavaScript,
and
this
would
be
certainly
an
important
an.
E
I
will
Address,
given
it
you
know
it.
It
covers
the
entire
documentation,
Suite.
D
A
Right
and
and
the
other
suggestion
just
to
double
check,
I
got
that
correctly
was
to
appeal
to
the
cncf.
Is
that
right,
Tim.
B
So
there
I
can't
remember
the
exact
website,
but
if
you
need
help
with
certain
things
around
documentation
and
whatnot,
the
cncf
is
able
to
help.
Just
to
note.
We
are
somewhat
short-handed
right
now,
so
that
that
request
may
be
cued
and
delayed
a
little
bit,
but
as
as
an
organization.
Yes,
we
are
absolutely
here
to
to
help
with
with
things
like
that,
I
can
find
out.
I
can
find
out.
I
can
find
out.
B
The
exact
URL,
I
think
I
think
officially,
like
a
maintainer
would
have
to
open
a
a
ticket
in
in
the
system,
but
there
was
also
I
believe
Bob
Killen
opened
it
just
on
the
cncf
tech,
docs
retail,
as
an
issue
as
a
way
of
reaching
out
and
starting
the
conversation.
So.
D
D
Some
examples
of
where
we've
done
that,
then
the
doctrine
work
and
also
we
use
doxy
now
and
we
engaged
and
worked
with
a
supplier
to
convert
the
site
to
doxy
who
who
did
a
lot
of
a
much
better
job
than
than
you
know
the
community
not
having
time
to
do
it.
So
there
are
cases
where
it's
it's
appropriate.
E
E
I
think
on
the
doxy,
you
know
issues
and
whatnot
I
didn't
see
anything.
Should
we
maybe
go
after
those
folks
as
well.
E
Again,
oh
I
think
you
know
go
after
the
the
doxy
maintainers,
oh
I,
see.
B
We
we
actually
so
I
I
I
should
clarify,
but
if,
if
an
issue
is
important,
enough
Tim
is
absolutely
correct.
We
can
should
probably
research
this
before
I
say
this
publicly,
but
I
believe
we
can
hire
contractors
not
to
bring
folks
in
to
shore
up
things
like
that
in
terms
of
the
doxy
developers
and
whatnot
Patrice
Chaplin
is
actually
on
their
I
think
he's
on
their
leadership
group
now,
and
so
he
may
be.
B
E
Okay,
I
thought
I
was
wondering
if
I
should
just
take
the
example.
You
know
in
the
in
the
doxy
Hugo
template,
Plug-In
or
a
short
code
and
just
try
and
recreate
the
problem,
because
it
would
be
sort
of
clean
from
all
the
you
know,
the
kubernetes
stuff.
What
do
you
think
I
think
that
might
sort
of
I
mean
if
it's
really
clean
there
and
it's
really
hard
to
recreate
there
or
that
might
point
to
something
that
maybe
is
you
know,
we've
got
heavyweight
docks
and
you
know
maybe
we
could.
E
A
I
wonder
I'm
I'm
a
big
fan
of
us
appealing
to
the
mailing
list.
First,
we
could
probably
do
a
couple
of
things
in
parallel,
but
I
think
the
cncf
support
would
probably
be
the
last-ish
effort
that
I'd
I'd,
like
I
personally
think,
is
with
us
trying
just
because
of
like
you
mentioned
Nate,
there's
not
a
lot
of
hands
on
deck
at
the
moment
and
trying
to
maybe
appeal
to
see
if
anyone
from
the
k8's
mailing
list
wants
to
jump
in
and
help
I
think
that
would
be
I.
E
Okay,
meaning
Sig
docs,
you
say:
hey
we're
experiencing
this
issue.
It
doesn't
appear
all
the
time,
but
we're
looking
to
some
folks
to
maybe
take
a
look
at
it
and
see
if
they
can
uncover
as
to
what
the
problem
might
be.
Yeah.
A
We
could
we
could
do
it
in
Duck,
so
we
could,
even
if
we
want
to
broaden
our
Horizons
to
all
okay
Denver,
although
maybe
starting
with
docs
first,
might
be
the
way
to
go.
E
Okay,
yeah
and
I
really
like
the
idea
of
a
short
code,
so
I'd
like
to
investigate
that,
and
you
know,
work
with
Tim's
guidance
on
on.
Maybe
you
know
something
there.
A
Yeah
great
yeah
I
think
once
we
have
that
issue
put
up
that
would
be
when
we'd
be
able
to
thanks
for
taking
over
the
note-taking
Tim.
Once
we
have
that
issue
put
up
we'd,
be
able
to
then
send
out
that
kind
of
call
out
to
action
to
the
Sig
mailing
list
and
and
see
how
we
go
there,
but
yeah
I
think
that's
I,
definitely
think
that's
a
great
first
step.
Okay,.
E
So
what
I'll
do
is
number
one
take
the
existing
issue
because
that's
sort
of
slanted
towards
Firefox,
but
it
could
be
something
and
I
was
able
to
recreate
it
again
by
you
know,
with
with
multiple
consecutive
reloads
I,
don't
know
if
that
I,
don't
think.
That's
a
realistic
scenario,
but
I'll
send
something
out
and
or
yeah
should
I
open
up
the
new
issue
to
just
point
out.
A
I
think
what
we
want
is
a
new
issue
specifically
to
create
this
short
code
error.
Yeah
I
would
I
would
still
keep
the
original
issue
going
for
the
general
issue
around
mermaid,
but
a
new
issue
specifically
for
the
shortcut
area
that
we
want
to
add
in
and
then
using
that
new
issue.
As
the
with
our
call
out
to
for
JavaScript
aficionados.
E
Right:
okay,
but
now
there
was
another
I
think
Abigail.
You
had
suggested
that
we
we
we
put
something
out
on
Sig,
docs,
to
sort
of
grow
awareness
or
raise
awareness
about
this
problem.
F
I,
don't
remember
if
I
said
that,
but
I
think
just
boosting
it
through
the
issue
and
I
I.
Think
specifically
like
letting
people
know
that
their
the
fix
is
refreshing.
So
if
they
are
seeing
a
broken
lick,
like
you
said
with
the
short
code,
the
fix
would
be
just
refreshing.
F
E
Good
actually,
I
didn't
remember
if
you
said
it
either
you're,
just
in
the
middle
of
my
screen
of
people
on
the
call
say
why
yeah
I
just
sort
of
randomly
addressed
you.
F
A
Thanks
so
much
Chris
and
thank
you
to
both
Tim
and
Nate,
who
are
jumping
into
the
the
agenda
here
to
like
to
write
out
the
action
items
much
better
than
I
did.
Thank
you
so
much
so
we've
got.
We've
got
some
italicized
and
folded
bits
there
Chris
that
you'll
be
able
to
follow,
along
with,
in
terms
of
like
the
decision
that,
or
should
I
say
what
we're
going
to
do
course
of
action.
Next.
A
Perfect,
that's
great
I
understand.
There
was
a
lot
of
a
lot
of
discussion
on
that,
but,
as
you
like,
you
have
been
so
diligent
on
looking
after
and
kind
of
like
tracking
what
is
going
on
here
and
and
really
trying
to
get
to
the
bottom
of
this
so
hey.
Firstly,
thank
you
so
much.
It's
really
really
great
that
you're
Trucking
on
with
this.
A
It's
really
awesome
and
we
will
definitely
the
community
definitely
going
to
be
trying
to
help
as
much
as
possible
and
as
soon
as
you
feel
like
that,
you
definitely
need
a
few
more
hands
on
deck
in
terms
of
even
project
managing
the
whole
thing.
Let
us
know
we.
E
We've
got
this,
you
know
short
on
time,
so
I'll
I'll,
take
that
and
you
know
we'll
just
brute
force
it
all
the
way
through
to
the
solution.
Great.
D
I
want
to
say
that
one
way
that
people
can
help
like
if
someone
says
I,
have
found
a
way
to
make
this
happen
reliably.
This
is
how
you
set
up
a
test
case.
I
have
never
used
JavaScript
in
my
life.
That
is
a
really
useful
contribution,
and
you
know
we
should
give
people
who've
got
that
and
kind
of
way
of
helping
a
path
to
do
so.
A
B
They're,
if
the
priority
in
need
is
high
enough,
we
can
obviously
make
some
decisions
or
whatnot
at
the
CNC
have
to
help
out
I've
linked
the
service
desk
and
the
policy
around
it.
I
do
believe
that
for
kubernetes
any
any
requests
to
the
service
desk,
we
probably
need
to
come
from
the
steering
committee.
A
Gotcha,
okay,
that's
good
to
know
so
so
it's
good
that
we're
looking
at
like
the
trail
of
the
kind
of
things
that
we're
trying
and
and
ways
that
we're
trying
to
resolve
the
issue
so
that
we
can
kind
of
send
all
that
to
the
steering
committee
as
needed,
maybe
at
the
at
a
meeting
in
future.
If
you
need
be
to
get
them
to
escalate,
that's
great
yeah
awesome,
actually
I'm
going
to
quickly
note
that
down
so
that
we
don't
forget.
A
Alrighty
thanks
once
again
Chris
and
everyone
for
the
the
great
discussion
on
this
I
know.
This
has
been
on
the
cards
for
a
little
while,
but
we
we're
we're
going
to
get
there
eventually
for
sure
at
least
we
have
definitely
a
plan
of
action
for
a
couple
of
steps
that
if
they
don't
work,
we
have.
We
have
a
next
escalation
path
forward.
So
thanks
again
Chris
so
much
alrighty
I
am
aware
of
time.
A
E
Okay,
very
good,
so
again,
sensitive
to
everybody's
time,
so
we
could
take
the
majority
of
this
on
the
on
the
slack
room,
but
real
quick,
several
months
back
or
I.
Think
it
can.
You
opened
this
issue
a
while
ago,
so
we
restructured
and
rebuilt
the
resource
metric
pipeline
section
and
that
had
a
couple
of
the
well
I
guess
it
had
the
the
resource,
metrics
or
metrics
API,
and
another
gentleman
open
up
an
issue
about
you
know:
hey.
E
We
need
something
that
documents
how
to
build
a
you
know:
custom
metrics,
exporter,
Tim
Hewitt
suggested.
Maybe
a
Blog
you'd
also
mention
that
you
know
you'd
really
like
to
get
something
for
metrics.k8s.io,
those
that
API
Suite.
So
again,
your
guidance
or
the
community's
guidance
I
think
it's
important
I
see
a
ton
of
stuff
out
there.
You
know
people
asking
about
it
and
you
know
various
blogs
of
you
know
how
to
set
it
up
so
yeah.
E
What
would
the
Community
think
and
again
we
can
just
you
know,
take
this
offline
if
it's
something
that's
probably
going
to
take
more
than
32
seconds.
D
I
think
I
think
that
we
struggle
to
prioritize
the
unloved
parts
of
our
docs,
because
those
are
those
are
parts
that
we
don't
see.
So
imagine
that
you
know
there
was
a
concept
called
game
spaces
I've
just
made
that
up
completely
and
we
didn't.
We
didn't
document
it.
The
docs
on
that
would
not
get
many
bug
reports.
You
know
because
it
wouldn't
be
documented,
but
actually
that
might
be
the
thing
that
we've
we've
missed
out
completely.
D
So
I
just
think:
there's
a
there's,
a
there's,
a
prioritization
challenge
around
knowing
what
you
haven't
got
and
I
have
a
feeling
that
there
are
some
even
more
rough
areas
of
the
Docks.
But
even
though
this
is
poor,
it's
met.
Maybe
not
the
you
know:
it's
not
the
constraint.
D
What
that
makes
me
think
is
we
as
a
Sig.
Maybe
we
want
to
put
some
time
into
finding
out
the
constraint
which
part
of
the
docs
is
letting
people
down
the
most
and
then
we
should
use
that
information.
A
Very
likely
very
likely,
however,
we
are
trying
to
figure
out
if
we're
going
to
be
definitely
putting
on
a
three-hour
doc
Sprint
at
qcom.
A
That
could
be
a
really
great
topic
for
the
doc
Sprint
and
something
that
we
can
continue
as
a
maybe
a
thread
on
slack,
given
the
time
that
we've
got
or
even
maybe
in
next
week's
a
slack
thread.
Meeting
too.
E
Okay,
very
good,
maybe
I'll
open
up
an
issue,
so
we
could
have
just
some
discussion
there
and
then
we
can
always.
You
know,
can
it
if
we,
you
know,
want
to
move
in
another
Direction.
A
Sure
definitely
I've
just
put
here
as
a
question
mark
I'm
gonna
see
just
writing
CC
Abby
there
and
and
Natalie
for
us
too,
to
kind
of
think
about
how
we
want
to
if
we
want
to
put
that
on
the
possible
agenda
for
the
doc
Sprint,
still
kind
of
figuring
out
some
information
there,
but
we're
gonna
have
an
update
for
the
community
very
soon
about
that
as
well.
Luckily,
next
week's
likely
next
week's
like
update
meeting
all
right.
A
Thank
you
so
much
Chris
going
to
give
Nate
the
the
mic
again
here
and
the
versioning
the
website
here
over
to
Unique.
B
Just
with
the
time
in
mind,
I
I'd
like
to
maybe
just
raise
awareness
of
this
issue.
B
A
while
ago,
almost
10
000
issues
ago,
Tim
opened
up
this
one
suggesting
that
we
revised
how
we
currently
version
documentation
for
the
website
right
now,
we're
using
feature
branches
and
sub-domains
in
order
to
version
the
entire
site,
not
just
the
documentation.
So
that
includes
things
like
the
blog
and
the
home
page
I'll
get
versioned
every
time
we
do
a
release
which
might
be
a
touch
too
much
By.
E
B
Way
it's
it's
a
bit
unwieldy
to
to
do
also.
It
has
knock-on
effects
on
search
and
all
the
rest
of
that.
So
I've
got
a
couple
of
comments
in
there
about
different
ways
of
potentially
exploring
this.
B
But
recently,
almost
a
month
ago
now,
Hugo
came
out
with
I
think
it's
zero
point,
96.0
a
new
release
version,
and
one
of
the
features
is
something
that
they're
calling
vertical
merging
of
content
notes,
which
is
a
little
bit
of
an
unwieldy
thing,
but
essentially,
and
the
example
that
they
use
is
the
ability
to
to
have
a
a
base
page
and
for
any
changes
to
it.
It
would
you
can
you
can
set
up
a
Delta
and
if
there
isn't
a
Delta,
the
base
page
would
be
the
default.
B
So
this
works
really
well
for
languages.
Let's
say:
you've
got
a
base
language
of,
for
example,
English,
and
you
want
to
change
it
to
German.
You
would
only
ever
have
to
translate,
or
rather
you
would.
You
would
have
your
German
sort
of
version
and
for
any
page
that
hadn't
already
been
translated,
it
would
default
back
to
your
base
language.
B
So,
in
this
case
English
we
can
do
that
potentially
for
I,
believe
versioning
as
well
as
languages,
and
so
what
we
could
do
is
set
up
a
base
version
and
only
update
the
pages
per
version
that
have
had
changes,
which
means
we
would
then
only
ever
version
the
documentation,
folder
and
we
may
be
able
to
significantly
reduce
the
complexity
around
releasing
as
well
as
searchable
older
versions
and
whatnot.
B
Now,
I
haven't
done
much
by
way
of
testing
or
building
out
a
proof
of
concept,
but
I
did
want
to
bring
it
up
and
say:
Hey
There
is
a
new,
but
there's
potentially
a
new
way
of
doing
this.
So
I
thought
it
was
worth
bringing
up
to
this
forum
to
say:
hey.
Let's
all
look
at
this.
A
A
I've
thought
as
much
but
I
think
it's
it's
worthwhile
exploring
if
it
means
we
can
take
complicate
uncomplication
I,
say
a
little
of
of
that
visioning
overall
for
sure,
given
time,
I
think
it's
also
worthwhile
that
we
maybe
have
kind
of
maybe
bring
this
up
again
in
in
our
in
our
slack
Community
Channel
for
folks
to
kind
of
look
at
and
maybe
be
able
to
have
a
longer
discussion
next
time.
What
do
you
think.
B
Yeah
I've
already
I've,
already
I've
posted
it
in
in
our
slack
Channel,
probably
about
a
week
ago.
I
think
but
I
didn't
get
a
whole
lot
of
traction,
so
I
figured
I'd,
bring
it
up
here.
Gotcha.
A
That's
great
yeah,
let's
yeah
agree
that
we
should
take
a
look
at
that
and
yeah.
It
definitely
doesn't
sound
like
an
insignificant
change,
but
something
that
requires
a
bit
of
quite
a
lot
of
prep
and
and
research
to
go
into
it
for
sure.
A
Yeah
for
sure
alrighty
folks,
thank
you
for
giving
us
a
bit
more
of
your
time.
A
Today
we
had
a
very
a
really
decent
discussion,
hopefully
solving
a
few
problems,
maybe
uncovering
some
new
ones
that
we
are
going
to
be
finding
challenging
and
exciting
to
solve
in
future,
but
I'm
going
to
stop
sharing
the
agenda
right
now,
so
I
can
see
all
of
your
faces,
who
are
showing
it
and
thanks
again
for
attending
today's
meeting
and
look
out
for
the
slack-based
meeting
that
we'll
have
for
next
week
and
until
then
see
you
all
next
time.
Thank
you.