►
Description
This is the annual retrospective and planning meeting for SIG Docs. We'll review docs accomplishments in 2018, set high-level priorities for the coming year, and set specific goals for content in the first quarter of 2019.
A
I
just
want
to
say
hello
and
thank
you
all
for
making
the
trek
to
come
here.
It
has
been
quite
a
year
in
cig,
docks
and
I
think
we
have
a
lot
to
celebrate
and
look
back
on
and
I'm
also
excited
for
for
the
year
to
come.
I
think
it'll
be
a
very
different
year.
I
hope
it's
a
very
different
year
from
what
we
have
done
this
year.
But
why
don't
we
get
started
with
an
introduction?
A
So,
let's
take
just
a
few
minutes
to
go
around
and
introduce
ourselves
and
say
hello:
most
we've
interacted
with
each
other
a
lot,
but
we
mostly
have
only
seen
each
other
in
two
dimensional
300
pixel
by
300
pixel
boxes.
So
I
wonder
if
we
could
go
around
the
room
and
let's
do
let's
do
names
pronouns
and
where
you
are
traveling
from
so
I
am
Zack
Corliss
in
he/him
day
them
I'm.
Here
from
the
amazingly
far
distance
of
Portland
Oregon
Brad.
B
B
A
Excellent
well
what
I
would
like
to
do
in
the
time
that
we
have
I'd
like
to
spend
about
20
minutes
going
over
what
we've
accomplished
in
the
past
year?
I
feel
like
we
do
a
lot,
but
we
have
not
really
had
time
to
kind
of
catch
our
breaths
and
take
a
moment
to
celebrate
and
acknowledge
the
work
that
has
gone
into
this
past
year
and
what's
come
out
of
it.
A
So
I'd
like
to
do
a
little
bit
of
a
retrospective
and
from
there
I
would
like
to
move
into
the
I've
divided
our
planning
time
into
two
parts.
The
first
part
I
would
like
to
like
focus
on
the
year
for
to
come
for
2019
and
think
about
what
is
it
that
we
want
to
be
able
to
say
when
we
meet
again
next
year
at
this
time?
What
are
the?
What
are
the
goals?
A
How
do
we,
how
do
we
divvy
that
up
and
what
are
the
immediate
steps
that
we're
going
to
take,
then
we'll
have
lunch
and
after
lunch
we'll
have
some
time
to
do
some
deep
dives
I
know
that
that
Andrew
and
Dominic
are
planning
to
demo
some
of
their
fundamental
modeling
concept,
work
and
I'm
looking
forward
to
that.
But
if
there
is
a
topic
that
you
would
like
to
dive
into
very
specifically
in
depth,
why
don't
we
come
back
and
do
that
after
lunch?
A
A
A
A
We
have
hosted
numerous
stocks
prints
at
a
variety
of
conferences.
Brad.
You
have
led
a
couple
Andrew
you
have
also,
and
Andrew
and
Jennifer
have
both
led
Sprint's
at
write.
The
docs
Portland
at
write,
the
docs
Cincinnati
Brad.
You
were
at
index
IBM
index
in
February
yeah.
We
Andrew
helped
lead
in
Copenhagen.
D
A
A
A
A
Thank
you
for
bringing
that
up.
Andrew
I
want
to
point
out
how
much
our
localization
contributors
have
contributed,
not
just
to
their
own
localizations,
but
to
sig
Docs
as
a
whole,
like
I,
think
about
like
Junior,
Eve
and
Claudia
came
from
the
Korean
team
and
how
much
they
have
been
willing
to
proof
test
and
fault
test
internationalization.
Like
the
the
contribution
guidelines
that
we
put
in
place
there,
their
willingness
to
fault
test
our
branching
strategy
and
point
out
they.
A
It
was
only
their
willingness
to
ask
some
really
interesting
questions
that
got
us
to
realize
that
we
did
not
need
to
put
localizations
in
different
repositories
that
we
could
host
them
all
in
one
in
in
NK
website,
and
do
that
and
I
also
want
to
call
out
the
work
of
his
a
carnold
who,
even
though
we
did
not
implement
it
or
it
was
implemented.
Very
briefly,
but
built
the
kubernetes
Docs
language
labeler,
to
make
it
possible
for
us
to
label
localization
content
to
filter
and
then
I
think
was
a
Christoph.
A
Blocher
came
along
and
said:
oh,
you
can
do
natively
in
prowl
and
we
were
like.
Why
didn't
you
tell
us
this,
but
it
was
the
willingness
to
build
it
that
made
that
conversation
possible
so
Zack
for
your
that
segues
nicely
into
release
Meister
gratitude.
So
we
have
on-boarded
how
many
for
different
release
Meister's
this
year,
starting
with
Jennifer
in
q1
for
1:10
and
Jennifer,
you
did
a
remarkable
job,
considering
that
we
switched
midstream
from
Jekyll
to
Hugo,
so
doing
doing
one
release
in
in
one
platform
and
then
sort
of
going,
oh
well,
I!
A
Right
hello
welcome.
This
is
Tim
Fogarty
and
I.
Just
barely
missed
the
introductions,
whether
accidentally
or
by
design
I,
don't
know
but
Tim
Fogarty
is
was
our
1.13
release
Meister
and
you
have
arrived
at
the
portion.
Where
were
you
express
gratitude
for
these
things?
So
thank
you
very
much
Tim
for
your
all
of
your
work
in
1.13,
so
Jennifer
you
started
out
the
year
with
1.10
Zach.
You
did
1.12.
Thank
you
and
I
have
to
confess
that
it
slips
my
mind
momentarily.
A
A
A
Yes
and
credited
that
goes
for
Andrew,
for
having
the
having
the
idea
of
having
a
PR
Wrangler
shift
to
make
sure
that
we
were
constantly
getting
PRS,
giving
giving
pull
requests
regular
attention,
so
Andrew
I
think
that's
been
one
of
one
of
the
like
most
successful
ideas
for
preserving
our
sanity
and
for
preserving
the
common
life
of
the
SIG's.
So
thank
you
very
much
other
things
from
2018
Jared.
A
A
We
finished
getting
the
blog
migrated
over
from
from
blogspot
or
blogger
to
github,
so
Caitlyn
Barnard
is
our
one
of
our
maintainer
x'
and
Caitlyn
is
the
maintainer
for
the
kubernetes
blog,
so
I'm,
so
glad
that
you
could
make
it
Caitlyn
and
I
hope
that
you
were
happier
working
in
github
than
then.
You
were
a
blogger.
A
Yeah,
so
we
have
a
couple
of
working
groups
now
that
we
did
not
have
at
the
start
of
the
year.
We
have
tooling
the
we
have
Docs
tooling
as
its
own
working
group.
We
have
the
reference
stock
generation
as
its
own
as
its
own
sub
project,
and
we
had.
We
started
collaborating
with
sig
cloud
provider
this
year
in
order
to
start
making
sense
out
of
the
the
section
of
the
content.
That's
currently
labeled
set
up,
we
on
be
on
boarded
yep.
We
have
lost
the
screen
I've
there
we
go.
A
We
have
on
boarded
how
many
new
maintainer,
sir,
how
many
new
approvers
this
year,
if
you
became
an
approver
this
year,
raise
your
hand
right,
1,
2,
3,
4,
5,
6,
7,
8,
8,
new
approvers,
and
that
process
has
gotten
I.
Think
more
and
more
streamlined
over
time,
as
as
we've
had
to
do
it
more
and
more
intentionally.
A
A
Yes,
so
we
had
a
good,
comprehensive,
UX
study
by
by
Neha
the
Google
intern
that
gave
us
some
really
actionable
feedback
to
implement
for
content
and
we'll
come
back
to
content
when
we,
when
we
get
into
planning
because
out
of
all
these,
this
is
a
really
remarkable
list
of
achievements
over
the
past
year,
but
there
are
some
missing
pieces
and
it's
those
missing
pieces
that
I'd
like
to
address
when
we
get
to
planning
so
is
there?
Is
there
anything
else
that
folks
want
to
call
out
about
our
work
over
this
past
year?
A
A
One
more
thing:
I
want
to
call
out
before
we
move
to
planning
and
that's
Andrew
did
a
lot
of
work
with
site
analytics
so
that
we
have
decent
site
analytics
and
we
actually
have
a
sense
of
what
we're
we're
able
to
look
at
specific
metrics
for
site
traffic,
page
landings
and
things
like
that
and
get
real
real
value
and
real
feedback
based
on
site
analytics,
and
that
is
largely
at
andrew's
initiative
that
those
conversations
happened.
So
that's
that's
sort
of
below
the
surface.
A
A
A
So
one
of
the
things
that
we
talked
about
when
we
met
at
the
sigdoc
summit
six
months
ago
in
Portland
was
what
we
wanted.
What
we
wanted
to
say
was
true
in
six
months:
I,
don't
know
that
we
really
got
that
well
defined
at
the
summit.
Frankly,
I
think
it
was
just
sort
of
us
getting
together
and
saying:
yes,
is
this
a
thing?
It's
a
thing.
This
is
good
and
that
was
a
good
start,
but.
A
What
so
I
mentioned
earlier
a
missing
piece
in
our
accomplishments
for
this
year,
and
that
is
I
think
specifically
around
content.
We
have
been
working.
Jared
said
this
to
me.
We
have
been
working
at
the
edges
of
our
core
competencies,
as
as
people
who
work
in
tech
Docs,
we
have
been
working
out
rather
than
at
the
heart
of
content
and
ensure
that
making
content
and
the
documentation
itself
as
clear
and
as
valuable
and
as
concise
as
possible.
We've
been
solving
technical
debt.
A
We've
been
working
through
process,
but
in
this
list
there's
not
anything,
there's
not
a
whole
lot
that
we
can
point
to
specifically
in
terms
of
content
and
say
ours
set
up
our
getting
started.
Page
is
better
than
it
ever
has
been
our
our
developer,
onboarding,
our
API
reference
are
better
than
they
ever
have
been,
and
so
I
want
to
start
our
conversation
there
with
content
for
the
coming
year.
A
I
would
like
I
would
like
to
honor
the
work
that
we've
done,
but
I
would
like
to
for
us
as
a
sig
to
think
about
refocusing
on
content
for
2019
and
looking
at
the
heart
of
kubernetes,
documentation
and
figuring
out.
What
are
the
pieces
that
we
need
to
work
on?
What
are
what
are
the
the
things
that
we
want
to
be
able
to
say
are
true
of
our
content
in
2019,
so
I
guess
to
begin
with.
Does
that
seem
reasonable
to
folks?
Do
folks
agree
with
that?
With
that
assessment?
A
Rajee
is
asking
how
we
want
to
approach
accessibility
for
our
content
in
this
coming
year
and
accessibility.
It's
sort
of
it
straddles
the
line
between
process
and
content,
but
I
think
that
it's
really
worthwhile
to
discuss
and
to
approach.
So
we
can't
make
assumptions
about
how
people
are
coming
to
our
material
or
the
challenges
that
the
way
that
we
present
our
content
is
as
excessive
as
equally
accessible
for
everyone.
So
there
are
some
things
that
we
can
do
with
accessibility
to
to
make
our
content
easier
for
a
wider
audience
to
consume.
So.
A
A
A
A
And
I
want
to
call
out
that,
in
in
the
released
just
passed
in
1.13
Jim's
solved
a
problem
that
had
recurred
from
an
earlier
release.
It
was
fixed
it
and
earlier
released,
never
made
its
way
to
master,
and
then
we
had
to
solve
it
all
again
and
tried
to
dredge
up
the
lore
of
how
we
solved
it
the
first
time,
but
Jim
has
ensured
that
that
won't
happen
again
that
that
that
particular
issue,
yes,
so
making
sure
that
we
have
a
comprehensive
release.
Playbook
for
release,
Meister's
welcome
hello,
other
things
to
Steve.
Yes,.
A
A
A
Just
at
the
contributor
summit
last
night,
I
got
I
talked
to
a
couple
of
deaths,
who
came
up
specifically
to
say
thank
you
for
the
docs,
so
your
work
is
very
much
appreciated.
It
is
there.
It
is
very
helpful
and
folks
are
finding
value
in
use
in
our
documentation,
so
I
just
wanted
to
show
that
out
and
make
sure
that,
yes,
we
talk
we're
going
to
talk
a
lot
about
ways
in
which
our
documentation
is
missing
today,
but
it's
still
helpful
and
people
love
it.
B
A
A
Want
you
to
know
how
many,
how
many
meetings
with
Jared
and
with
Chris
that
I
have
sat,
thankfully
not
literal,
but
metaphorical,
tears
streaming
down
my
cheeks
that
after
a
year,
our
setup
page
has
still
not
meaningfully
changed.
So
I
would
love
to
get
to
the
setup
page
and
make
that
as
as
meaningful
as
helpful
and
as
sensible
as
possible
that
we
take
what
is
currently
called
set
up
in
the
documentation
and
get
that
into
a
true
getting
started.
A
Section
and
I
will
basically
like
I
will
hide
bodies
at
this
point
if
it
means
that
we
actually
get
to
do
that
this
year.
That
one
year
from
now
we
say
we
have
a
true
getting
startup
section,
but
that
does
segue
nicely
into
not
only
questions
of
specific
pieces
of
content,
but
how
we
present
our
content
and
so
Jennifer.
You
raised
a
nice,
a
nice
discussion,
so
to
go
back
earlier
to
user
journeys
being
less
than
a
year
old.
A
I
I
think
that
the
to
summarize
the
discussion
about
user
journeys
that
we've
had
over
the
the
past
year,
the
user
journeys
have
been
an
excellent
test
and
it's
time
to
iterate
upon
them.
So
I
know
that
Andrew,
you
have
a
PR
in
the
works
about
changing,
changing
our
landing
page
design,
away
from
user
journeys
and
more
to
a
a
card
design.
A
A
D
A
B
A
A
What
we're
going
to
call
meta
information
architecture,
some
of
the
questions
about
how
we
do
what
we
do
with
content
content,
freshness
I,
would
love
that
into
meta
information,
architecture,
site,
UX
and
accessibility.
This
is
a
lovely
list
of
accomplishments.
Do
we
think
that
we
can
do
all
of
these
in
2019.
B
A
I
will
say
that
I
think
Zack
holds
the
record
for
most
PRS
closed
as
a
PR
Wrangler,
and
the
way
that
you
explained
it
to
me
is
that
at
the
time
is
that
you
had
simply
adopted
Misty's
process
where
you've
passed
it
through
the
sieve
of
filter
by
extra
small/small.
We
can
discuss
the
particulars
of
that
yeah.
A
A
That
seems
like
fairly
reasonable
to
use
the
to
set
milestones
in
the
meeting
in
the
weekly
meeting
and
then
review
them
like,
as
time
comes
as
time
goes
by
I.
Think
that
there's
maybe
some
some
discussion
piece
around
what
those
milestones
should
be
that
can
happen
outside
of
the
context
of
the
meeting,
but
using
using
the
meeting
as
like
a
milestone.
Check-In
time
seems
like
a
reasonable
use
of
time,
but
yeah
we
can
we,
let's
dive
into
that,
but
I
still
want
to
get
consensus
on.
A
A
A
A
A
A
For
administrators,
so
that
was
one
of
the
specific
pieces
that
Chhavi
mentioned
had
heard
feedback
asking
for
so
better.
So
when
you
think
about
like
what
one
of
the
most
important
things
that
an
admin
needs
when
they,
when
they
land
on
kubernetes
dot
IO?
What?
What
are
the
first
things
that
an
admin
needs
to
see.
A
A
D
A
Sure
so
I
will
I
agree
that
this
is
really
important
and
I
also
want
to
point
out
that
this
is.
This
is
a
place
where
crossing
collaboration
is
not
only
good
but
necessary,
like
with
not
steering
sick
architecture.
Specifically,
there
is
I,
don't
know
if
it's
an
actual
cig,
but
there
is
a
group
out
of
architecture
that
is
devoted
to
security,
and
there
is
it's
not
well
exposed,
I,
think
intentionally
so,
but
there
is
a
pathway
for
exposing
for
reporting
security,
security,
vulnerabilities.
A
Right
right,
so
that's
an
opportunity
to
work
with
the
the
security
folks
to
make
sure
that
we
are
surfacing
security
concerns
in
a
way.
That
is
that
that
matches
their
standards
and
matches
best
practices.
But
yes,
but
including
that
intentionally
in
our
release,
bulletins
or
released
in
a
process.
A
A
Sure
so
that's
I
think
that
I
mean
that's
a
that's
a
good
like
meta
architecture.
Question
is
about
what
like
what
are
the
common
tasks
between
developers
and
admins
or
like
cluster
admins
and
and
and
app
developers
talking
about
what
like?
What
are
the?
What
are
the
common
tasks
and
then,
where
do
they
meaningfully
branch?
That's
something
that
I
think
that
user
journeys
captured
well
in
its
essence,
just
I
think
that's
a
like
an
implementation
thing
that
we
can
iterate
on
for
like
a
card
based
design.
But
if
we,
if
we.
F
A
G
A
Let's
see
so
it
Jennifer
is
that
is
that
adequately
specific
for
defining
onboarding
new
developers
or
for
can
we
even
just
back
that
up
and
say
not
just
developers
but
admins
onboarding?
Can
we
can
we
summarize
that
is
that?
Is
that
sufficient
depth
to
talk
about
onboarding
or
do
we
need
to
get
more
specific.
A
So
how
would
we
define
that
is
as
specific
things
to
accomplish
in
q1?
What
what
are
the
first
steps
that
we
need
to
be
able
to
take?
So
if
the
end
goal
is
at
the
end
of
the
year
being
able
to
say
our
docks
are
actually
UX
driven
and
that
things
are
meaningfully
parsed
out?
What
are
the
first
steps
that
we
take
in
q1
to
get
there.
B
A
A
A
Sure-
and
that
sounds
like
an
opportunity
to
work
with
the
overall
release
manager.
They
were
like
picking
out
the
new
themes
of
a
release
that
I
know
from
a
release
manager
standpoint
that
tends
to
happen
like
later
in
the
cycle.
But
that
is
a
good
opportunity
to
to
to
to
coordinate,
to
look
at
the
specific
Doc's
impact.
A
A
There
there's
also
there's
routine
administration
like
I
need
to
build
out
the
PR
wrangling
schedule
for
like
the
next
six
months,
so
like
all
the
the
routine
maintenance
that
goes
into
making
the
cig
run
so
better
onboarding
the
1.14
release
process,
making
a
specific
decision
around
fill
up
with
rocks
cube
control
docks.
What
else
do
we
want
to
focus
on
in
q1?
We
have
some
specifics
from
improving
the
docks
process.
We
have
accessibility,
let's
see
better
security,
documentation
and
bulletins,
and
it's
see
Andrew.
A
You
mentioned
that,
like
better
UX
is
like
doable
in
a
quarter.
Do
you
want
to
out
of
out
of
what
we
have
not
yet
covered?
What
else
do
we
want
to
cover
in
q1
I?
Would
I'm
gonna
vote
for
accessibility,
I
would
say,
let's
at
least
get
started
on
it.
So
if
we're
going
to
start
assigning
owners
to
stuff
Raja,
do
you
want
to
own
accessibility
in
q1.
A
Sure
is
it
reasonable
to
say
like
if
we
could
aim
for
an
overview
of
what
needs
to
happen
with
accessibility
like
in
March?
Would
you
be
willing
to
give
like
a
presentation
about?
This
is
what
excessive
this
is.
The
definition
of
accessibility-
and
these
are
the
specific
things
that
we
need
to
do
to
make
the
site
more
accessible.
Is
that
something
that
you
would
be
willing
to
do?
Okay,
excellent
Thank,
You,
Zack,.
B
A
A
B
A
A
That
I
would
love
I
would
love
to
take
that
on
I
for
for
political
reasons,
I
need
to
be
a
part
of
whatever
happens
there
by
political
reasons.
I
mean
is
probably
not
a
good
idea
for
one
cloud
provider
to
edit
another
cloud
cloud
providers,
description
of
themselves
so
say,
I'm,
sorry
right
so
changing
the
set
up
to
getting
started
is.
A
H
B
B
A
A
A
A
What
let's
talk
about
specific
metrics
for
some
of
these
I?
Don't
know
if
we're
going
to
get
to
all
of
them.
But
let's
talk
about
like
specific
objectives
like
how
will
we
know
whether
or
not
we
have
achieved
a
particular
task
like
what
is
the
done
state
for
each
of
these?
Some
of
those
I
know
that
might
be
particularly
that
might
be
difficult
to
define
for
some
of
these,
like
more
investigative
steps
like
discover,
more
information
and
report
back
but
like
for
gym.
A
A
B
A
Excellent,
so
that
will
look
specifically
like
a
set
of
guidelines
for
for
authoring,
accessible
content,
and
do
you
want?
Do
you
also
want
to
cover
like
site
features
like
things
that
we
need
to
address
in
the
site
itself,
or
not
so
much?
Okay,
so
specific
guidelines
for
authoring,
accessible
content,
excellent.
F
B
A
B
C
B
A
So
a
plan
and
some
meaningful
progress
in
in
authoring,
okay,
so
for
setup
to
getting
started.
Jennifer
Chris
and
Cody
Chris
I
hear
you
asking
for
like
four
specific
structure
so
Jennifer
and
Cody.
Is
it
reasonable
to
ask
like
helping
helping
Chris,
formulate
a
set
of
milestones
that
you
can
take
to
Susan
cloud
provider
and
say
these
are
the
things
that
cloud
provider
sick
cloud
provider
needs
to
do
or
that
cloud
providers
need
to
do
with
their
content?.
B
A
B
D
A
A
That's
good,
alright,
so
release
release
the
release.
Point
book
I
want
to
I
would
like
for
that
to
be
done
like
we
have
the
the
goal
of
that
product
in
q1
is
to
have
a
finished
release.
Playbook
I
think
that
the
the
information
is
there,
there's
enough
pieces
of
it
that
it
doesn't
have
to
be
cut
from
whole
cloth.
It
can
be
assembled
from
various
knowledge
and
like
meaningfully
reasonably
complete
by
the
end
of
March
by
the
end
of
q1
I.
A
Would
say
the
the
contributing
guide?
It's
a
very
thick
so
currently,
like
contribution
is
broken
out
into
basic
intermediate
and
advanced
I
would
say
expert,
but
we
could
add
that
as
a
we
can
figure
out
where
to
where
it
can
specifically
live
in
that
content
hierarchy,
but
I
would
say
contribution.
I
do
think
that
the
release
playbook.
We
can
talk
about
it
offline,
but
I
think
that
there,
in
the
actual
in
the
community
repo
or
in
the
like
the
release
repo.
A
A
A
A
B
A
A
B
A
All
right,
so
if
there
is
no
easy,
if
there's
no
easy,
either
open
source
summit
or
coop
con
attached
in
the
first
part
of
the
year,
I
would
say:
let's,
let's
take
lunch
to
do
some
investigation
and
then
maybe
like
when
we,
when
we
gather
again
at
one
o'clock,
let's,
let's
provide
a
specific
a
specific
time.
If
there
isn't
a
specific
place,
then
let's
provide
a
specific
date
and
time
where
we
can
meet
online.