►
From YouTube: GMT 2018-10-08 Community WG
A
C
A
B
B
B
C
C
C
B
C
B
You
can
link
to
headers
yeah
headings,
but
you
can't
and
I've
noticed
in
some
of
the
other
documentation
I've
been
to
you
go
to
the
page
and
if
it's
long,
there's
like
table
of
contents
at
the
top
that
you
can
click
to
the
section
you're
interested
in
I,
whereas
like
some
of
our
lengthier
ones,
you're
kind
of
like
just
lots
of
scrolling
to
figure
out
how
this
documents
laid
out.
I.
B
B
We
haven't
revived
it
like
once
or
twice,
but
the
last
time
Vinod
and
I
looked
at
it
and
tried
to
think
about
how
to
do
it
in
a
way.
That's
gonna
work,
I
think
we
wrote,
we
wrote
it
down
in
the
review,
so
anyone
could
read
it,
but
I
don't
think
he
had
time
to
to
follow
up
again.
So
we
it's
probably
gonna,
be
on
us
I.
Don't
think
we
can
rely
on
someone
to
have
the
time
to
work
on
it.
C
B
B
What
people
could
work
on
by
things
that
we
know
are
really
useful
and
people
have
asked
for
mm-hmm
versioned
documentation
was
at
the
last
Agathon
as
well.
I
think
I
think
it
got
closer
but
yeah
it's
the
approach
that
was
taken
wasn't
didn't
seem
like
the
right
one.
So
we
left
the
feedback
round
how
we
think
we
should
do
it
so
someone's
just
gotta
kind
of
execute
on
that
mm-hmm.
C
B
The
Tim
did
it
was
every
time
you
generated
the
documentation,
it
like
checks
out,
every
single
tag
in
turn
and
what
build
it
and
we'll
like
then
we'll
publish
it
and
all
that,
whereas
phono
and
I
were
hoping
for
more
of
a
like
a
release.
Branch
based
approach
where,
like
the
documentation
generation,
runs
on
master
and
CI
as
well
as
on
these
branches,
and
then
it
looks
at
where
it
is
and
it's
it
sees
it's
on
one
7x
and
it
sees
that
the
verse
his
171.
B
But
maybe
he
knows,
there's
no
tag
so
then
it
goes
and
publishes.
That
is
like
one,
seven
one
tentative
or
something
like
that,
and
then
you
could
do
one
off
to
build
all
the
old
documentation
for
previous
releases,
but
that
would
make
it
so
that
when
we
run
CI
to
update
the
docs,
we
don't
have
to
build
like
50
tags,
yeah.
B
C
B
B
B
It
wasn't
changing
anything
dramatic
like
we
already
have
a
link
structure
that
has
latest
in
it
all.
Our
documentation
is
just
latest
ray
and
he
was
just
publishing
the
version
stuff
at
slash.
You
know
one
seven
Oh
instead
of
latest,
so
he
just
basically
like
did
the
same
thing
but
published
this
one
over
and
one
seven
Oh
instead
of
slash
latest
mm-hmm.
A
B
The
left
hand
like
menu
navigation
thing,
is
a
little
more
involved
just
because
you
have
to.
Yes,
you
have
to
feed
in
structure.
To
that
thing,
it's
not
just
gonna
know
it
automatically
like
most
of
them
are
based
on
folders
and
we
don't
really
have
like
a
cohered
folder
structure
in
there.
So
we
don't
do
that
and
then
right
right,
some
additional
things
which
tell
it
like.
What
should
the
sections
be
and
all
that
yes,
I,
looked
at
like
how
the
kubernetes
website
is
generally,
it
looks.
B
B
C
C
B
C
I
agree:
you
know
yeah,
let's
make
it
happen,
I
think
we
can.
My
plan
for
the
hackathon
was
to
do
like
a
test
fix
a
thon
for
anybody
who's
interested,
because
that
seems
to
be
useful
and
pretty
easy
to
do
and
rewarding,
but
depending
on
the
interest,
I
could
do
version
Docs
instead,
but
I'll
see
if
I
can
get
someone
else,
who's
interested
in
leading
that
how
that
we
can
make
it
happen.
C
B
What
test
test
fixing,
if
you
like
that'd,
be
great
as
well
I
think
there's
still
a
little
bit
of
a
lacking
communication
and
clarity
about
the
current
situation,
we're
in
and
how
one
could
help
with
it.
Like
I,
don't
actually
know
how
bad
is
it
right
now
like
how
could
I
go
and
get
the
list
and
start
working
on
some
more
I.
Just
don't
know
well,
I
think
that's
true
of
a
lot
of
people.
So,
if.
A
B
Hackathon
was
to
come
in
with
some
structure
for
that,
like
okay,
here's
here's,
the
data
of
like
which
ones
are
most
we're
hitting
most
often
and
yeah,
would
be
most
valuable
to
fix,
and
people
could
start
off
that
list,
the
most
frequently
hit
ones
first
or
whatever.
That
would
be
I
think
more
useful
than
kind
of
just
where
we
are
now,
which
is
I,
don't
even
know
where
to
help
or
if
it's
bad
still
or
did
we
disable
a
bunch
of
tests
that
we
should
rename.
C
Alas,
oh
I
think
I
think
it
means
fear
we
can
probably
do
a
better
job
to
help
people
stay
up
to
date
on
that
because
we
have.
We
have
this
like
CIA
call
rotation
which
we
haven't
been
doing.
A
good
job
of
staying
on
top
of
Benna
was
on
that
rotation
recently
and
did
a
really
good
job
of
sending
out
summaries
of
flaky
tests,
but
they
were
all
kept
internal,
so
that
should
be
open
and
I
bet.