►
From YouTube: K8s SIG Docs Meeting for 20200811
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
A
I
am
one
of
your
chairs,
but
today
I
am
only
vaguely
chair
shaped.
I
have
just
come
back
from
two
weeks
away,
and
so
I
am
here
to
be
ornamental
and
to
hold
space
while
well.
A
The
true
power
in
the
sig
jim
angel
decides
what
it
is
that
we
talk
about
and
lets
us
know,
what's
actually
going
on.
A
So
start
as
we
always
do
with
new
contributors,
we
do
not
have
any
new
contributors,
but
we
have
a
returning
contributor
from
days
of
eld.
Abigail
mccarthy
was
one
of
the
original
maintainers
for
kubernetes
documentation
back
when
I
started
three
years
ago.
So
abigail
welcome
back
it's
good
to
have
you
yeah
cool.
A
Let's
see,
updates
and
reminders,
this
week's
pr
wrangler
is
caitlin
bernard
next
week's
pr.
Wrangler
is
me,
and
I
promise
that
I
will
not
dodge
out
of
it
this
time.
A
Let's
move,
oh
sorry,
as
always
approvers.
Please
make
sure
you
know
when
your
scheduled
pr
angular
shift
is
abigail.
If
you
are
interested
in
becoming
an
approver
again,
we
will
get
you
up
to
speed.
Maybe
one
of
the
easiest
ways
is
to
shadow
our
pr
wrangling
shift
and
see
how
things
have
changed.
A
Sweet
all
right,
let's
talk
about
the
agenda.
First
up
is
release
1.19.
So
let's
see,
I
think,
did
they
see
that
cevito?
Wouldn't,
oh,
no
cedita's
here
great
savita.
Do
you
want
to
talk
about
1.19.
B
Sure
so
the
first
item
is
vitam.
I
guess
so.
I'm
gonna
skip
that
and
I
will
go
through
the
rest
and
open
the
floor
for
them.
The.
C
B
Thing
is
in
progress,
so
anna
has
a
volunteer
to
it.
You
do
the
branch
sink
and
overall
it
went
great
except
for
one
issue
that
we
found
there
are
a
couple
of.
I
think
there
are
two
overall
three
red
marks
and
two
of
them
are
some
tight
issues
in
jim
from
that
netlify
build
issue
and
one
of
the
pr
has
a
march
conflict,
but
it
has
been
already
marched.
B
Yeah
has
a
message
in
he.
He
created
a
message
in
sick
testing
asking
about
it
and
there
is
a
threat
in
syncdocs
channel,
that's
ongoing
and
that's
it.
That
is
the
broad
sync
and
the
second
one
is
the
updated
update
api
references.
So
this
is
the
one
of
the
final
steps
to
get
prepare
for
the
release
that
pr
is
in
progress
and
care
me,
ken
bradshaw,
I
I
need
to
give
a
shout
out
to
karen
bachcha.
B
She
has
helped
me
a
lot
like
from
the
start.
She
modified
a
lot
of
python
code
for
me
and
it's
been
wonderful,
I'm
not
sure
if
he
is
here,
but
thank
you
so
much.
B
So
that's
in
progress
and
she
identified
that
there
is
a
problem
with
the
cube,
idiom,
documentation
and
the
master,
so
that
has
been
fixed,
so
it
needs
to
be
merged
into
dev
1.19,
which
the
branch
sync
would
take
care
of
and
after
that,
I'm
going
to
do
another
final
round
of
reference
generation
and
push
it
to
the
branch
and
see
if
everything
is
good.
B
That's
the
second
thing
and
the
third
thing:
the
branch
status
is
not
a
healthy,
because
there
is
a
conflict.
The
official
documentation,
official
docs
period
is
showing
that
it
needs
a
release
and
I'm
guessing
the
branson
could
take
care
of
it.
It's
all
from
me
any
questions.
A
Thank
you
for
that
update
yeah,
I'm
curious
to
hear
what
or
how
the
the
sig
test
conversation
goes.
It's.
It
is
really
odd
for
a
merged
conflict
to
to
successfully
merge
or
pass
through
prow,
so
yeah,
I'm
really
curious.
How
where
that
conversation
will
lead
so
normally
at
release
time,
we
freeze
the
website
repo,
like
24
hours
in
advance
of
merging
the
official
docs
pr.
So
what
date
are
we
looking
at
for
freezing
the
repo.
B
So
that
will
be
24th
of
august,
assuming
that
the
targeted
release
date
is
25.
So
we
will
all
the
relief
team
will
check
in
on
24th
and
see
if
everything
is
good
to
go,
and
I
am
planning
to
reach
out
to
all
the
localization
teams
once
I
know
for
sure
that
before
I
freeze
the
website
and
everything
start
anything
that
I
need
to
take
care
of
other
than
posting
an
announcement
in
the
channels.
C
B
A
Nice
that
seems
accurate
to
me
feedback
from
tim
or
jim
or
erdy.
D
I
know
that
last,
I
think
his
last
session.
We
had
a
issue
or
maybe
not
really,
an
issue
where
we
put
in
the
issue
for
the
tied,
merge
blocker.
But
then
we
wanted
to
approve
specific
prs
and
couldn't
without
introducing
a
flood,
and
I
believe
tim
had
to
jump
in
and
put
hold
on
the
prs
that
were
held
or
pr's
that
we
didn't
want
to
merge
and
but
basically
I'm
interested
just
to
be
aware
of
that
potential
catch
22
or
that
idea
of
pull
requests
kind
of
piling
up
on
top
of
each
other.
D
Just
be
aware
that
that
could
be
funky
and
if
there's
a
better
way
to
do
that,
or
maybe
an
improvement
to
the
process.
Just
general
awareness
and
attempt
go
ahead.
E
If
you,
if
you
have
a
bunch
of
pr's
that
are
ready
to
approve,
then
one
thing
I
think
a
tech
lead
or
chair
can
do.
Is
octopus
merge
them?
I
don't
know
if
people
who
are
some
people
might
not
be
familiar
with
get
that
get
feature.
Some
people
might
know
it
already,
but
it's
possible
to
do
and
it's
a
way
out
of
it
that
I
will
be
I'd
rather
not
have
to
do
that,
but
it's
an
option.
E
D
Cool
and
then
one
other
thing
I
did
want
to
add,
is
on
the
on
the
testing
ops
issue
that
I
brought
up
on
the
merge
conflict
and
I'm
just
reading
verbatim
here.
So
I'm
just
a
messenger.
In
this
case
they
said
if
the
status
didn't
pass.
D
D
So
it's
a
race
condition
where
one
kind
of
merger,
before
the
other,
ultimately
the
pr
that
was
open
with
the
merge
sync,
it
builds
properly.
The
labels
look
okay,
I'm
tempted
to
say
we
let
this
kind
of
be
what
it
is
and
let
it
merge
and
then
there's
an
issue
linked
as
well,
but
open
for
thoughts
or
conversation.
We
don't
really
have
to
solve
this
now
by
any
means.
A
Well,
I
think
we
all
owe
tim
a
beer,
because
I
think
you
called
it
what
like
a
month
and
a
half
ago
when
we
were
trying
to
diagnose
what
it
was
that
was
causing
these
conditions
in
general,
so
yeah.
I
think
I
mean
that
sounds
reasonable
to
me,
jim,
I
think,
if
it's
not
causing
any
obvious
breakage,
then
I
think
I
think
we
can
go
ahead
and
merge
it.
E
And
I'm
going
to
stick
sort
of
in
the
chat
setting
site
to
deprecated
as
in
for
a
release,
so
what
we
will
do
is
we
will
mark
1.18
as
as
deprecated
and
then
master
will
be
documenting.
1.19
does
not
show
a
document,
deprecation
warning
in
the
dock
section
of
the
site.
E
We've
we've
changed
themes,
since
we
last
did
a
release.
E
A
E
C
So
I
recently
redid
the
way
that
the
deprecation
warnings
show
so
that
they
don't
use
a
short
code
anymore.
They
use
a
layout
partial
and
by
way
so
really.
This
is
probably
a
celeste
up
problem
and
I
imagine
that
the
rollback
will
be
somewhat
easy
to
manage
by
just
like
finding
the
commit
and
doing
like
revert.
C
However,
when
I
did
this
change,
I
tested
this
locally
by
changing
the
version
number
in
the
config.tumble
and
then
setting
deprecated
to
true,
which
then
shows
the
deprecation
warning
and
it
did
work
locally,
and
so
this
to
me
is
another
one
of
the
scenarios
where
it's
like.
We
really
need
to
start
getting
better
about
how
we
test
these
front-end
changes
like
it's,
not
as
simple
as
being
like
yeah,
it
doesn't
seem
the
site
keeps
building,
because
that,
ideally
shouldn't
have
been
merged,
but
this
is.
This
is
definitely
an
error
that
I
introduced.
C
My
first
instinct
is
to
revert
that
change,
which
is
a
two-part
thing.
It's
going
to
be
re-adding
the
shortcode
onto
index.md
and
undeleting,
the
shortcode
html
file,
and
given
that
that
was
the
way
things
were
working
before
that
should
work.
If
not
you'll,
see
me
in
the
channel.
E
So
I
have
a
thing,
though,
if
you
look
at
two
three
zero:
three,
two,
like
one
bigger,
that's
the
pr
with
a
fix,
so
it
needs
review.
But
I
don't
think
it's
a
big
challenge.
I
think
I
I
know
I
think
we
can.
I
think
we
can
get
this
sorted,
but
I
would
like
that
reviewed
and
and
I'd
like
a
few
eyes
on
it.
C
A
C
If
not,
we
can
take
this
to
slack.
I
just
want
to
make
sure
that
we're
all
in
consensus
as
to
what
use
cases,
we're
actually
testing
and
verifying
work
and
what
are
important
to
us.
A
So
you
see
we
have
a
number
of
issues
in
prs
to
get
through.
Let's
put,
let's
add
zero
three
two
to
that
list
and
I
wanna
make
sure:
let's
see
what
time
is
it
17
minutes
in,
I
think
we'll
get
to
it,
but
I
am
going
to
reorder
this
list
slightly.
A
Actually,
I'm
not
going
to
do
that
because
I
didn't
put
this
together
jim
in
what
order
do
should
we
discuss
this?
Should
we
bump
like
so
I
see
at
the
end,
we
have.
A
A
ckss
qualification,
hugo
and
doxy
in
a
container
and
analytics
do
we
want
to
discuss
this
before
or
after
we
work
through
individual
issues.
D
So
I
think,
delay
two
that
I
really
like
to
get
to
this
week
is
the
ones
that
start
within
parentheses
from
previous
week.
We
didn't
have
enough
time
last
week
and
bumped
those
after
that,
I
think
we
can
make
do
with
whatever
we
got.
A
Okay,
then,
let's
move
those
up
ahead
of
issues
and.
A
Prs:
okay,
cool
celeste!
Thank
you
for
being
flexible.
Let's
move
on
from
the
blog
and
let's
take
that
first
previous
week,
item
guidelines
for
promotion
of
localization
thresholds.
So
jim
you
want
to
talk
about
this.
One.
D
Yep,
so
this
came
up
about
two
weeks
ago
now
and
the
apec
meeting,
where,
for
those
that
aren't
aware,
when
we
start
a
localization
process,
the
whole
traditional
model
of
approvers
reviewers,
that
kind
of
contribute
or
ladder
is
a
little
bit
expedited
for
the
initial
two
contributors
of
the
localization.
D
One
thing
that
it
seemed
like
the
localization
team
that
brought
this
up
wasn't
aware
of
was
that
community
membership
ladder,
given
that
kind
of
rapid
introduction
to
being
a
more
of
a
senior
approver
and
not
having
that
kind
of
traditional
onboarding?
They
weren't
aware
that
the
process
even
existed,
and
so
what
came
up
was
well
that's
a
great
process,
for
you
know
the
majority
of
english
contributors
or
where
there's
a
larger
community
for
the
smaller
communities
that
are
doing
localization.
D
Is
it
worth
having
a
separate
guideline?
Do
they
have
a
little
bit
more
flex
like
when
we're
on
boarding
the
initial
contributors
to
there
and
the
overall
question
came
down
to
at
what
point
do
it
makes
them
a
reviewer?
At
what
point
do
we
make
someone
approve
or
what
does
that
promotion
process
look
like,
and
while
we
do
have
guidelines?
Is
that
appropriate
for
all
localizations?
And
that
was
the
topic
for
discussion.
A
That's
fair
also.
I
want
to
boost
that
brad
in
chat
says
that
he'd
also
like
to
discuss
feedback
about
localization
that
brad
got
from
the
polish,
french
and
italian
localization
teams.
Brad.
Do
you
wanna?
Is
it?
Is
that
relevant
to
talk
about
right
now
or
do
you
want
to
discuss
that
as
a
separate
thing.
A
I
think
brad
may
have
stepped
away
okay.
Well,
for
now,
that's
a
really
good
point.
Jim.
The
localization
guidance
that
we've
given
historically
has
been
for
people
who
are
already
well
familiar
and
well
integrated
with
the
project
and
hasn't
served
well
folks
who
are
new
and
who
are
starting
out
as
like
as
new
members.
A
A
So
jim,
are
you
proposing
specifically
that
we
write
like
a
not
only
a
new
localization
guide
but
like
to
add
a
section
specifically
for
new
to
project
as
well.
D
Yeah,
so
we
do
have
an
open
issue
right
now
in
general,
about
the
localization
process.
This
came
up
last
week
as
well.
The
general
consensus
was
there's
a
great
onboarding,
how
to
start
a
localization,
but
there's
not
a
lot
of
great
documentation
on
continuing
localization
and
there's
not
a
lot
of
knowledge
sharing
between
how
folks
are
keeping
branches
and
sync
things
of
that
nature.
So
that's
the
scope
of
the
issue
I
opened
up.
If
we
wanted
to
you
know,
have
a
look,
have
a
little
bit
of
scope
creep
here
and
include
this.
D
We
definitely
could.
I
would
imagine
I'd,
take
involvement
with
sig,
controlbacks
or
contributor
experience
as
well
to
make
sure
that
we're
not
doing
anything,
that's
deviating
from
the
norm,
and
you
know
for
all.
I
know
there
might
not
be
a
need
to
have
a
different.
You
know
what
makes
somebody
a
reviewer
an
approver,
but
that
was
just
kind
of
the
consensus
that
I
had
is
that
these
teams
are
small
and
agile
and
they
want
to
make
sure
they
have
a
process.
D
A
Gotcha,
I
definitely
think
we
can
serve
folks
well
by
linking
to
the
community
membership
the
url
that
you
provided
in
the
agenda.
I
am
really
curious
to.
A
It
might
be
a
good
idea
to
see
if
the
community
repo
is
willing
to
host
localizations
of
that
as
well,
because
it
adds,
I
know
it
adds
another
localization
burden
on
to
contributors
who
already
are
struggling
with
a
workflow.
A
E
A
Yeah,
let's
so,
let's
take
that
advice
and
form
a
working
group
through
the
magic
of
kubernetes
governance.
It's
done.
We
just
need
somebody
to
organize
it
and
I'm
happy
to
boost
visibility
about
it
to
do
like
the
well.
Oh
sorry,
it's
not
it's
not
magically
done.
I
have
to
pull
that
sparkle
dust
back.
If
we're
going
to
form
a
working
group
as
opposed
to
a
subproject,
we
have
to
use
these
terms
very
carefully
some
projects
we
can
instantly
hand
wave
and
they're
done
working
groups.
A
A
This,
let's
do
the
easy
one,
so
that
is
a
sub-project
and
you
tim
as
a
tech,
lead
and
gemini's
chairs
have
the
ability
to
wave
our
hands
poof,
it's
done
so
the
localization
subgroup.
Let's
boost
visibility
on
that
in
the
channel.
Let's,
actually,
let's
do
that
by
email
and
slack.
A
And
yeah
we
can
work
through
the
logistics
like
getting
a
slack
channel
set
up.
A
And
I
get
to
get
the
stakeholders
involved
for
how
best
to
move
forward,
what
what
to
actually
create
in
order
to
make
folks
happier
there.
A
All
right,
brad
is
not
back,
but
I
I
recall,
reading
from
earlier
that
the
french
team
in
particular
had
questions
about
how
best
to
keep
aware
and
keep
in
sync
with
changes
to
english
source,
which
makes
me
wonder
if
the
french
team
knows
about
the
the
diff
script
that
we
include
in
the
repo
and
whether
they're
already
using
it.
So
I
guess
that's
a
question
to
follow
up
on
with
the
french
team
is
whether
or
not
they're
already
using
the
diff
script.
Let
me
find
that
really
quick.
A
In
the
repo
from
the
top
level
of
the
repo,
it
is
scripts.
Yes,.
B
Actually,
I
have
a
conversation
with
raymie
from
the
friends
localization
team
and
he
said
that
he
already
used
this
script,
but
the
thing
is:
if
we
only
do
this
not
in
a
periodic
manner,
then
there
is
times
where
the
diff
is
like
really
huge,
and
we
are
confused
on
how
we
can
test
things
and
choose
what
kind
of
changes
that
we
will
impose
for.
Something
like
that.
A
Interesting,
so
do
do
you
have
do
you
have
ideas
there,
your
v
about
what
to
do
differently.
B
No,
actually,
I
also
have
the
same
kind
of
a
problem
so
yeah.
This
is
like
really
common
problems
for
for
the
themes
in
localizations.
A
Is
it
would
it
be
solved
by
like
running
the
script
more
frequently.
B
B
Maybe
we
need
to
make
sure
what
kind
of
problems
that
they
are
finding
with
these
scripts,
whether
the
periodic
jobs
will
help
that.
E
A
That
I
don't
have
a
good
answer
to.
I
haven't
played
with
the
analytics
api
at
all,
so
I
don't
know
if
there's
a
way
to
to
script
that
neatly
brad.
Oh
sorry,
guys!
Okay,
I
don't
go,
go
get
it.
D
I
was
gonna
say
this
is
all
kind
of
like
there's
like
a
melting
pot
of
localization
issues
over
the
past
couple
weeks
here
today.
I
think
we're
all
hitting
it
on
the
head
that
it
sounds
like
it's
a
little
bit
larger
than
the
initial
need,
so
subgroup
definitely
makes
sense.
The
one
piece
of
information
that
I
passed
on
to
brad
when
he
brought
this
up
was.
I
saw
folks
in
this
initial
issue
that
I
opened
up
and
I'll
send
a
link
in
chat
here.
D
D
I
believe
that
the
japanese
localization
team
is
also
doing
a
very
good
job
at
modeling
after
the
korean
team
and
then
there's
other
folks
kind
of
figuring
out
their
own.
I
know
that
remy's
doing
a
great
job
with
the
french,
but
obviously
having
some
issues
with
the
process
as
well.
But
what
was
interesting
to
me
that
I
saw
I
had
no
idea
it
existed-
was
that
the
ukrainian
translation
team
actually
has
a
translation
issue
creator
that
they
created
from
scratch
and
they
shared
it
in
this
chat
as
well.
D
So
that
was
surprising
to
me.
I
had
no
idea,
and
I
think
this
is
really
what
we're
trying
to
fundamentally
solve
is
have
that
umbrella
guide
guidance
of
here's.
You
know,
here's
the
getting
started
playbook
and
maybe
everyone
keeps
their
own
scripts
and
their
little
the
different
different
pieces
of
the
scripts.
D
Maybe
I'll
live
in
the
same
location
or
some
common
mechanism
for
sharing
and
communicating
this
at
the
end
of
the
day,
so
yeah,
just
a
big
plus
one
to
this
whole
discussion,
and
I
think
it's
all
bubbling
up
now
that
we
have
more
and
more
localizations
yeah.
A
F
Yeah
so
so
same
topic,
so
I
reached
out
to
last
night
on
slack
to
france
and
poland
and
italy,
and
I
got
really
good
feedback
and
questions
on
on
those
three
things,
and
I
did
see
the
issue
that
that
jim
opened.
I
think
I
think
the
piece
that
was
that
I'm
missing
is:
how
do
we
drive
this?
How
you
know?
How
do
I
respond
back?
You
know
for,
for
you
know
how
these
folks
get
their,
so
some
folks
can
contribute
hey.
F
We've
got
great
ideas
and
great
tools,
and
then
there's
some
folks
who
say
no,
no,
I'm
here
for
the
help.
I
need
help
like
the
question
from
france
was
hey.
I
need
better
understanding
on
something
and
from
poland
it
was.
I
need
a
better
understanding
on
the
analytics
of
which
pages
are
hit
most,
and
so
what
wasn't
clear
to
me
jim,
was
the
the
best
way
that
we
corral
these
people.
Maybe
it
is
a
subgroup,
maybe
that's
what
you're
saying
we'll
just
form
a
subgroup,
but
but
you
know
the
interesting
thing
will
be.
F
A
F
A
I
don't
think
we've
gotten
that
far.
Oh
okay,
sorry!
I
I
I'm
reluctant
to
volunteer
people
for
things,
but.
A
I'm
yeah,
I
am
happy
to
pick
up
the
administrative
pieces
and
like
chase
down
getting
a
new
slack
channel
things
like
that.
So,
while
I'm
happy
to
be
like
an
administrative
point
of
contact,
I
also
don't
think
that
this
is
something
that
the
chairs
and
tech
leads
need
to
drive
per
se.
I
think
that,
like
our
best
involvement
is
as
an
administrative
help
and
that
the
best
the
best
help
that
localization
teams
can
give
to
each
other
is
from
each
other.
A
So
I'm
happy
to
create
all
of
the
things
necessary
for
serendipity
to
occur.
But
beyond
that,
I
don't
know
that
driving
top
down
is
going
to
actually
fix
anyone's
problems
in
an
effective
way.
Does
that
make
sense.
F
F
F
I
think
the
difficulty
is
the
time
zone
thing
or
how
we
do
it,
but
I
yeah
I
can.
I
can
actually
do
that.
I
I
don't
know
as
much
about
the
localization,
but
I'll
have
to
rely
on
the
the
teams
that
are
the
experts,
so
I
don't
mind
doing
that.
So
I
just
got
to
figure
out
how
we're
going
to
do
that.
Maybe
we'll
use
the
zoom
meeting
or
whatever,
but
I
guess
it'll
be
a
sub
group
and
we'll
we'll
have
a
weekly
meeting
or
something
so.
A
Doesn't
have
to
be
weekly
whatever
cadence
works,
maybe
maybe
it's
a
thing
that
you
do
monthly
and
then
increase
as
needed.
F
A
I
would
rather
make
sure
that
information
doesn't
get
siloed
off
into
google
doc.
I
would
rather
like
beef
up
our
localization
docs
in
the
contributor
section.
Okay,.
F
A
And
I
will
take
an
action
item
to
do
the
administrative
pieces
for
subgroup
formation.
No
thanks.
Let's
see
yeah
well.
F
A
I
think
technically
it's
called
a
subproject,
but
all
right.
So,
let's
move
on
to
our
next
discussion
from
last
week,
the
ckss
qualification
tim.
You
want
to
talk
about
this.
E
Celeste,
do
you
want
to
talk
about
this?
Because
if
you
do
I'll,
let
you.
C
This
is
the
new
qualification
from
the
lf
right.
There's
a
new
qualification
from
the
lf
we're
giving
out
a
new
test
for
kubernetes
things.
We
gotta
add
the
new
test
to
the
training
page.
C
A
C
Of
august
or
september
september,
okay,
okay,
yeah,
so
we
got
to
get
it
done
by
september.
Yeah.
Anybody
who
kind
of
has
some
web
chops
can
do
this.
It
doesn't
necessarily
need
to
be
me,
though
I
did
create
the
original
page.
A
E
Oh,
I
saw
it
in
the
announcement
from
the
cncf
and
I
went
oh
we'll
need
to
put
that
on
the
website.
I
will
look
for
an
issue
I'll
just
do
that
for
a
moment.
C
But
it's
not,
I
don't
think
it's
a
hard
edition
really.
You
just
need
to
know
how
to
you
need
to
know
like
enough
html
not
to
go
completely
awry.
C
If
the
skills
are
fly
clearly
yeah,
I
don't
think
it
should
be
a
problem,
because
it's
pretty
much
just
like
there's
like
that
little
grade
listing
the
existing
qualifications,
the
two
of
them.
It's
like
copy
paste
that
test
it
on
mobile,
to
make
sure
nothing
breaks
and
continue
on
your
merry
way.
A
C
C
Think
the
only
other
thing
we'd
need
from
the
cncf,
and
I
can
if
there
is
in
fact
an
issue
we
can
petition
chris
about
this
to
petition
on
our
behalf,
like
the
one
liner
description
of
the
course
kind
of
thing,
because
I
copied
those
for
the
original
page,
I
copied
those
directly
from
the
ls
training
website
and
if
the
course
is
not
live
yet
there
will
be
nothing
to
copy.
Yet.
E
C
I'm
still,
I
think
this
is
a
good
follow-up
issue.
This
is
good
to
follow
up
on.
A
And
I'll
just
thank
you
for
being
very
proactive
yeah.
That
gives
like
even
more
time
for
it
to
be
a
good
first
issue.
So
yeah
I
would,
I
would
say,
let's
focus
on
making
this
as
clearly,
let's
focus
on
making
the
issue
an
excellent
candidate
for
a
new
contributor
to
pick
up
and
and
do
yeah,
and
that
sounds
like
a
really
good
way
to
to
resolve
that.
In
the
short
term.
A
Just
quickly,
I
know
I
don't
want
to
linger
too
long.
We
have
a
lot
to
cover.
I
don't
think
we're
going
to
get
to
everything
this
week,
but
so
I
reached
out
to
other
folks
in
the
linux
foundation
about
a
recent
experience
with
the
cka
exam
and
how
the
exam
broke
for
some
candidates,
based
on
some
of
our
changes
to
remove
third-party
content.
A
It
turns
out,
there's
really
no
good
way
in-house
and
no
active
monitoring
in-house
to
make
sure
that
breaking
content
changes
are
surfaced
well.
So
that
is
something
that
I'm
working
on
in
houses
to
make
sure
that
there's
a
good
mechanism
to
make
sure
that
changes
surface
clearly
and
visibly
to
exam
designers.
A
So
I
saw
that
there
was
quite
a
thread
about
that.
While
I
was
away
so
just
to
let
you
know
I'm
following
up
on
that
and
I'm
totally
open
to
input
about
how
best
to
do
that
and
what
specific
checks
we
need
to
need
anything
more
about
that.
Or
can
we
move
on.
A
All
right,
so
let
me
go
right
issues
in
pr's,
two,
three:
zero,
three
one
and
twenty
three
o
thirty,
two.
Yes,
we
have
already
discussed
this
a
little
bit
celeste.
I
think
you
had
more
to
say
about
32.
C
Nope
other
than
that,
you
will
need
to
pull
that
down
locally
to
test
it,
and
I
think,
on
slack
before
we
dive
at
it.
Let's
have
a
discussion
about
what
specifically
we
are
going
to
test,
because
it's
not
as
simple
as
navigating
to
a
version
in
like
the
version
drop
down,
because
those
are
hard
links.
C
A
So
it
sounds
like
this
might
all
be
a
really
good
comment
on
32
for
testing
criteria.
A
Okay,
let's
move
on
to
21797
tim:
do
you
want
to
talk
about
reducing
the
height
of
the
header.
E
A
Fair,
are
these
both
equal
in
your
eyes
or
do
you
is
there
an
approach
that
you
think
is
more
elegant
and
more
sustainable.
E
C
C
Right
so,
to
give
you
an
update,
zach.
This
is
also
related
to
third-party
content
questions
yet
again
and
very
specifically
around
the
networking
page
and
prs
of
projects
to
this
page,
which
are
kind
of
sort
of
tangentially
related
to
networking,
but
are
not
a
specific
cni
plug-in
they're,
just
like
they
make
networking
nicer.
C
So
we
had
a
long
discussion
about
this
last
meeting
and
the
conclusion
we
came
to
is:
we
need
to
warn
people
very
clearly
on
pages,
where
you
we,
where
we
must
list
third-party
projects.
We
need
to
say
like
these.
We
know
they're
listening
third-party
projects.
We
are
not
responsible
for
them.
C
They
are
listed
alphabetically
per
the
cncf's
website
guidelines
and
if
you
want
to
pr
a
page
to
this
a
project
to
this,
you
must
meet
the
content
guidelines
first,
because
I
think,
without
a
really
clear
warning
like
there's,
we're
gonna
get
keep
getting
people
trying
to
sneak
in
prs
first
off
and
second
off,
it's
not
really
actually
fair,
because
it's
not
kind
of
clear
at
the
point
of
contact
like
this
is
what's
listed
on
this
page
and
why
so?
C
A
D
22
960,
that
was
just
the
discussion
that
we
had
related
to
driving
all
these
changes
just
trying
to
thread
them
all
together.
I
don't
believe
it
needs
discussion.
This
is
one
of
the
pr's
that
came
up
and
and
kind
of
what
all
started.
This
discussion
was
when
I
was
pr
wrangling,
there's
a
pr
that
didn't
quite
fall
in
the
guidelines,
but
I
didn't
have
a
great
resource.
D
It
didn't
quite
felt
like
it
definitely
fell
into
the
kep
guidelines,
but
it
wasn't
clear
because
there's
other
third-party
content
in
the
same
page-
and
I
had
no
way
to
say
here's-
why
we're
not
accepting
this
content?
Here's
a
reference
link
to
that
that
statement
other
than
saying
here's,
a
kepler
kind
of
falls
into
it.
Here's
where
I
think
it
falls
out
and
then
it
becomes
more
of
my
personal
opinion,
rather
than
the
official
stance
of
sig
ducks,
and
so
I
appreciate
the
work
that
celeste
has
done
driving
this.
A
Forward
excellent,
so
let
me
take
a
note
on
this.
One
zach
will
review
and
I
will
review
that
by
friday
this
week.
C
C
This
is
kind
of
what
we
think
like
a
cni
plug-in
should
be
like,
and
this
is
something
that
we
think
would
fall
out
of
those
guidelines
and
for
those
reasons
like
I
think
we
need
to
be
a
little
more
heavy-handed
with
our
recommendations
for
people,
because
I
think
the
natural
tendency
is
again
to
try
and
sneak
a
pr
and
hope
for
the
best
right,
and
I
would
like
that
and
every
time
it
comes
up,
it
becomes
a
big
discussion
and
it
drains
the
group's
energy.
A
That's
fair,
I
will
say
flatly
that
I'm
not
qualified
to
assess
cni
plugins
for
for
fitness,
so
this
is,
I
think,
an
excellent
place
for,
like
sig
network,
to
provide
that
kind
of
input.
A
But
I
wish
that
I
could
say
yes,
I
agree
with
you.
I
wish
I
could
say
yes,
I'll
drive
it.
I
can't
drive
it
right
now.
C
A
I,
if
you
are
willing,
would
you
be
willing
celeste
to
write
up
those
thoughts
in
an
issue.
C
Yeah,
I
can
write
up
those
thoughts
on
the
issue.
Please
put
me
down
for
it
on
the
agenda
and
I
might
actually
take
a
stab
at
it
when
I
submit
the
pr
for
the
button
we'll
see
how
I
feel
to
just
like
extract
a
little
more
language
from
the
cap
and
put
it
in
the
content
guidelines,
because
I
don't
think
we
want
to
be
linking
people
to
the
cap
for
all
eternity.
Oh.
A
B
So
basically,
I
already
created
a
link
checkers
using
the
github
actions
and
it's
already
works,
but
I
will
need
to
review
from
you
folks
just
to
make
sure
that
this
is
exactly
what
we
want
to
have,
and
I
already
put
the
sample
of
report
that
we
have
if
there
is
links
that
actually
doesn't
valid
anymore
and
this
will
be
executed
in
a
period
of
manners
or
whenever
we
are
creating
a
pull
request.
B
No,
no,
I
still
need
the
review
for
this
right
because
there
is
still.
I
think
tim
is
already
reviewing
that,
but
I
just
want
to
make
sure
if
the
report
is
already
what
we
expect
it
to
be.
B
A
Okay,
I'm
I'm
not
seeing
the
the
sample
report.
C
So
zach,
if
you
click
on
the
link
in
the
agenda,
go
to
the
right
hand,
pane.
B
C
And
I
wonder
if
we
can
break
this
out
into
a
separate,
build
step
so
that
it
doesn't
get
lost
in
the
in
the
rest
of
the
build
output.
B
There's
a
possibility
of
doing
that,
but
I'm
not
sure
since
github
actions
is
actually
not
using
specific
docker
image.
They
already
put
specific
steps
in
in
their
repository
and
then
just
import
that
steps
into
our
configurations,
and
probably
we
need
to
create
our
own
actions
just
to
be
able
to
do
that.
E
Tim,
I
I
think
to
if
this
is
going
to
be
useful,
for
people
maybe
even
blocks
the
build
but
later.
But
if
there's
going
to
be
any
sort
of
point
where
a
reviewer
says
this
hasn't
gone
right,
it
needs
to
be
something
where
the
person
whose
pr
it
is
can
see
that
before
the
reviewer
does-
and
I
think
that
needs
to
be
easy.
E
A
Agreed,
but
if,
if
we're
not
going
to
use
it
for
reviews,
but
it
is
going
to
add
to
the
build
time,
then
it
feels
ornamental
rather
than
then
useful.
So
I
would
say:
let's:
let's
get
this
to
the
point
where
it's
easy,
where,
where
its
results
are
easily
discoverable
and
where
they're
easily
reviewable,
I
guess
more
to
the
point
so
evie.
Are
you
fine,
with
waiting
on
this
to
to
improve
discoverability.
B
Yeah,
I
will
take
a
look
into
how
we
can
make
it
easier
for
us
to
see
at
the
field
result.
Okay,.
E
Awesome
yeah
tim.
I
will
maybe
next
month
mid
next
month.
I
might
have
some
time
to
help
you.
I
know
that's
a
long
time
off.
A
Excellent,
okay,
that
is
it
for
issues
and
pr's.
We've
got
five
minutes
left.
Surely
five
minutes
is
enough
to
talk
about
hugo
and
doxie
in
a
container
jim
and
celeste.
You
want
to
talk
about
22995.
D
Yes,
so
this
is
related
to
discussion
that
came
up
last
week
about
npm
versus
yarn.
I
believe
that
has
been
resolved
I'll.
Let
tim
mercedes
talk
to
that.
If
it's
not,
but
but
there's
a
pr
opened
up
where
long
story
short
is
npm
was
being
ran
outside
of
the
container,
where
the
challenge
was
the
files
to
build
the
website
don't
exist
in
the
container
until
you
actually
run
it
locally.
D
So
the
instructions
started
out.
As
you
run
the
container,
then
you
run
npm,
because
now
you
have
the
files
in
the
container,
then
you
can
hugo
serve
out
of
it.
I
know
some
of
the
efforts
that
you
know.
I've
talked
about
about
having
that
one
portable
image
that
can
be
distributed,
anyone
could
use
and
not
have
to
actually
build
the
container
every
time
they
wanted
to.
D
So
the
long
and
short
of
all
this
is
the
comment
that
I
left
before
the
meeting
started
here
about
potentially
adding
in
a
initialization
script
in
the
container
that
runs
your
npm
and
runs
your
hugo
command.
So
when
you
start
the
container,
you
have
your
files
in
there
every
time
you
start
that
container,
it
would
run
npm
and
then
launch
hugo.
D
C
It
sounds
like
a
yes,
this
pr
is
actually,
I
think,
there's
also
kind
of
a
question
around.
C
You
can
kind
of
go
wild
when
you're
building
this
locally
and
you
can
use
yarn
to
kind
of
figure
out
dependencies
or
you
can
use
npm,
and
I
think
at
this
point
with
doxydocs,
he
wants
npm,
but
you
can
kind
of
still
run
yarn
and
it's
just
it's
just
another
kind
of
like
thing
we
need
to
manage.
The
tldr
is
the
the
pr
link
I'm
personally
comfortable
with.
I
think
it
probably
will
improve
the
situation.
C
I
like
what
jim's
suggesting
of
initializing
a
state
inside
the
container.
That
makes
sense
to
me,
and
it's
kind
of
one
less
thing
that
a
new
contributor
has
to
worry
about
so
yeah.
That's
where
I
stand
on
this.
D
A
Excellent,
we
have
two
minutes
left
jim
assuming
you
can.
Is
there
any
reason
not
to
give
anonymous
view?
Read
access,
say
more
about
anonymous
view.
Read.
D
This
is
a
quick
one,
so
in
the
past
we
were
sending
out
the
hundred
top
pages
to
the
email
list
and
any
folks
who
got
that
email
were
able
to
open
up
the
pdf
click
view
in
the
web
browser
and
they
would
eventually
trigger
a
email
to
the
administrator.
Saying
so-and-so
is
requesting
review
access
and
you
can
click
approve
for
the
the
people
on
the
analytics
side
since
we're
no
longer
sending
the
report
out.
D
I
believe,
and
I
make
an
assumption
here-
that
process
no
longer
exists
or
if
you
go
and
open
up
an
old
pdf,
you
click
request
view
access.
The
email
doesn't
get
triggered.
The
long
story
short
here
is,
you
know,
short
of
creating
some
sort
of
funky
over
engineered
process
where
people
can
individually
request
access.
Is
there
any
reason
why
we
couldn't
open
up
anonymous
reader
view
only
access
to
anyone
who
wants
to
access
it,
given
that
they
have
the
link
or
the
ability
to
get
there?
Now?
D
A
I
see
no
reason
not
to
do
it
the
more
access
that
we
can
give
to
this
information,
the
better
it's
historically,
it's
just
been.
It's
been
a
needless
choke
point
administratively,
so
anything
that
we
can
do
to
make
that
access
available.
The
the
only
thing
that
people
shouldn't
have
access
to
is
changing
or
removing
data
or
giving
permissions
to
other
people.
A
Okay,
cool
and
we
have
a
couple-
let's
see:
oh,
we
actually
got
to
the
poll
in
france,
italy,
tim
sorry,
we'll
have
to
get
to
security
liaison
next
week.