►
From YouTube: K8s SIG Docs Meeting for 20200303
Description
K8s SIG Docs Meeting for 3/3/3020
A
B
C
C
Based
on
Seattle
I,
live
in
SeaTac,
fairly
close
to
the
airport
so
and
I'm
currently
working
at
NetApp
part
of
the
we're
in
a
few
different
paths,
doing
some
community
stuff
with
the
meetups
in
a
few
different
cities
and
then
also
working
on
the
documentation
for
the
that
app
kubernetes
service.
So
I
wanted
to
find
out
more
about
sigdoc
some
myself
there's
another
co-worker
of
mine.
We
work
together
on
a
lot
of
docs
and
I
thought.
C
A
A
Next
week's
PR
Wrangler
is
Jerry
Buckey,
so
Jared.
This
is,
will
not
be
Jared's
first
time
here,
wrangling
but
be
gentle
anyway,
as
always
a
privilege
make
sure
you
know
when
you're
scheduled,
it
is
so
much
easier
to
switch
a
schedule
around
in
advance
rather
than
during
the
week
of
okay
agenda
release.
One
eighteen
update
that
heard
from
beneath
or
sadita
this
week.
D
D
A
There's
somebody
actually
well.
We
move
on
to
somebody
mine's,
looking
at
the
dev
branch
on
the
repo
like
finding
the
official
release,
PR
I,
don't
remember
the
number
off
the
top
of
my
head
and
seeing
whether
it's
okay,
thank
you
Jim
and
just
like
make
sure
it's
some
building
correctly
right
now,
like
passing
CI,
and
all
that,
while
we
do
that,
let's
move
on
to
the
doxy
template
so
gearbox.
A
So
right
now
there
are
three
sections
up
and
available
on
the
site:
the
docks,
the
blog
and
the
partners
pages.
So
if
you
go
to
any
other
page,
things
may
look
wonky
and
that's
as
it
should
be
because
they
haven't
been
work
done
yet.
But
if
you
have
feedback
about
docks,
the
blog
or
the
partners
page,
like
put
it
in
slack,
there's
a
thread
running
within
the
past
24
hours
about
feedback
for
those
particular
page.
A
A
A
E
A
Thank
you
for
the
zoom
link
and
yes,
I
think
this
is
an
excellent
idea,
adding
that
trading
tab
to
the
top
nav.
You
boosted
it
last
week
and
it's
good
to
get
visibility
on
it
again
this
week.
So
if
you
have
any
feedback
about
that
about
either
the
appearance
or
the
implementation,
celeste
speed
are
19
19
to
1.
4
is
the
place
to
do
that
and
Thank
You
Celeste
for
adding
that
and
getting
on
that
so
powerfully
right.
A
Given
all
of
the
discussion
around
best
practices
for
adding
architectural
diagrams
to
the
docks,
I,
wonder
so,
I
think
what
we
would
benefit
from
at
this
point
is
an
issue
describing
what
needs
what
we
need
to
add
to
the
docs.
Just
summarize,
the
discussion
so
far,
and
to
summarize
in
conversation
that
is
that
we're
going
to
adopt
is
Tio's
standards
for
diagrams,
because
they're
very
clear
and
very
well
made
and
used
the
set
of
architectural
icons
in
the
community
repository.
F
A
A
Adding
these
guidelines
really
clearly
because
if
you
remember
way
back
when
we
started
this
conversation
towards
the
end
of
last
year,
first
of
this
year,
the
conversation
was,
we
don't
even
know
what
to
tell
someone
yet.
So,
let's
tell
someone
something
before
we
ask
them
to
do
something
for
us.
If
that
makes
sense,
yeah.
F
Don't
do
the
best
job
of
conveying
what
they're
trying
to
convey
you
know,
I'm
big
into
diagrams
and
visually
learning,
and
then
trying
to
draw
up
certain
concepts
and
I've
tried
to
use
those
same
architectural
images,
but
they
all
just
look
like
blue
squares
at
the
end
of
the
day.
If
that
makes
sense,
and
so
I
didn't
know,
if
this
is
where
the
buck
stopped
or
if
there's
continuing
discussion
around,
maybe
improving
that
making
a
little
bit
more
descriptive
and
what
those
icons
mean
and
do
I.
A
Think
that
sounds
excellent,
I
well,
I
think
that
sounds
excellent
and
it's
a
great
iteration
from
a
starting
point
and
I
guess
what
I'm
saying
now
is:
let's
provide
the
starting
point
from
which
to
make
those
iterations
and
I
agree
this
those
diagrams
they're,
really
not
accessibility
friendly
and
they
don't
scale
well
at
different
levels
of
zoom
celeste.
You
look
like
you,
have
thoughts
about
that
and
because
you're
very,
very
good
at
UX
design.
I
wonder
if
he
makes
I.
E
So
I'm
kind
of
catching
up
in
the
sto
discussion,
because
I
did
not
look
through
these
guidelines.
This
is
my
first
time
seeing
them
today,
but
I
agree.
I,
think
this
is
like
it
kind
of
exactly
what
we
need,
but
adapted
for
kubernetes,
because
I
find
that
architecture,
architecture
diagrams
are
also
maps
and
maps,
always
have
a
legend
and
it's
the
legend
that
makes
the
map
useful,
not
the
picture.
E
So
fundamentally,
yes,
on
board
I've,
also
kind
of
contributed.
My
thoughts
around
like
to
the
the
proposal
we
were
going
to
have
for
our
graphic
designer,
which
is
it's
you're,
not
gonna,
get
a
good
result
with
what
we
were
proposing,
anyways,
because
it's
too
it's
too
ambiguous
for
somebody
who
has
no
background
in
kubernetes
whatsoever.