►
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
Something
like
that,
I
guess:
I'm,
not
gonna,
stand
up
on
the
podium.
I
don't
have
slides.
This
is
strictly
impromptu.
I
didn't
realize
that
in
fact,
well
I've
been
vaguely
suspecting
for
one
or
two
releases.
Now
that
somehow,
where
I
thought
we
were
headed
with
released
notes
was
not
in
fact
where
the
releases
were
headed
and
that
at
least
some
communication
had
gotten
lost
somewhere
along
the
way.
So
what
I
want
to
do
is
tell
my
story
of
involvement
with
the
release
notes,
with
an
eye
to
explaining
with
that
story.
A
Why
I
think
this
is
an
issue
for
the
room
as
a
whole
to
think
about
and
consider
for
future
involvement,
so
I
started
contributing
to
this
kubernetes
documentation.
Sometime
in
the
summer
of
2017
and
in
late
August,
early
September
I
became
aware
that
the
release
team
was
working
on
release
notes
in
a
somewhat
different
way
up
through
release.
A
1
7
in
Andrew
can
correct
me
because
he
was
the
Ducks
Meister
for
that
release,
but
my
understanding
is
that
up
through
1
7,
the
release
lead
had
been
responsible
for
shepherding
the
release
notes
through
to
publication,
and
it
had
been
a
chaotic,
last-minute
painful
wrangling.
Nobody
was
very
happy
with
the
output
and
so
I
went
back
and
looked
up
in
my
slack
history.
A
Kaleb
miles
came
up
with
the
idea
that
there
be
someone
actually
assigned
to
responsibility
for
release,
notes
separately
and
individually,
with
release
1.8
well
Caleb's,
not
a
technical
writer,
and
he
had
Radek
anair
on
his
team
and
she
became
involved
with
the
release
notes
around
the
same
time
that
I
became
aware
of
this
need,
and
so
we
had
this
kind
of
informal
agreement
that
Radhika
and
I
would
work
together
on
the
release
notes.
Also
for
the
first
time
in
1.8.
A
We
we
didn't
use
the
process
that
some
of
you
may
be
familiar
with
now,
whereby
the
release
notes
are
pulled
out
of
the
strings
in
the
code
poll,
requests
dumped
into
a
Google,
Doc,
massage
there
and
then
eventually
dumped
back
into
a
markdown
file
in
github.
Instead,
we
had,
we
were
working
from
a
raw
markdown
file
and
all
the
release
notes
were
generated
for
the
first
time
there.
Sometimes
that
involved
release
contributors
copy
pasting,
what
they
put
in
pull
requests.
Often
it
involved
that,
but
there
was
no
automation.
A
It
was
an
entirely
manual
process
and
Radhika
and
I
sort
of
team
tagged
editing
that
markdown
file
and
we
spent
12-hour
days
the
last
week
of
the
release.
Getting
it
cleaned
up
for
release,
it
was
actually
kind
of
fun.
I
mean
it
was
a
substantial,
well
different,
well,
bounded
sort
of
set
of
tasks,
and
there
was
there
was
a
lot
of
very
clear,
obvious
work
to
clean
all
of
those
release
notes
up
so
that
they
made
sense
and
provided
useful
information
for
1.9
I
was
the
release,
notes
lead.
A
It
was
a
kind
of
obvious
extension
of
this
last
minute.
Informal
engagement
that
I
was
part
of
I
mean
only
part
of
I
stress
that
this
was
really
a
kind
of
collective
effort
for
one
eight,
four
one,
nine
I
was
the
release,
notes
lead
and
we
I
believe
one.
Nine
was
the
first
time
we
tried
for
the
Google
Doc
approach,
because
the
problem
with
the
markdown
file
is
you
can't
do
collab.
You
know
real-time
collaborative
editing,
we
weren't
importing
from
the
pull
request.
A
A
If
I'm
understanding
it
correctly
is
the
addition
of
the
sig
based
themes
that
was
an
that
was
an
innovation
for
one
eight.
Also,
there
had
been
released
teams
before
that.
We
didn't
really
have
a
release
team
for
one
eight.
It
was
supposed
to
be
a
maintenance
release.
Remember
when
maintenance
releases
and
kubernetes
were
thing
which
they
aren't
anymore.
Well,
I
never
really
were
right,
but
they
were
eight.
They
were
a
fiction
that
was
maintained
until
it
was
finally
abandoned,
but
but
anyway
that
content
is
added
and
I
guess
you
know
at
least
with
1:13.
A
It's
a
little,
not
a
lot,
but
a
little
like
the
other
things
that
have
happened
in
cig
docks
in
2018,
where
we've
gotten
so
concerned.
We've
done
a
lot
of
amazing
work
with
tooling
and
process
and
infrastructure
at
the
expense
of
sufficient
attention
to
content.
Now,
that's
not
to
say
that
was
a
bad
idea.
I
think
it's
a
good
idea,
but
the
time
has
come
I
think
to
turn
our
attention
to
content
again
and
I
would
really
like
to
see
cigars
return.
Do
what
I
see
at
you?
A
B
A
That
wouldn't
be
a
bad
thing,
I
think
at
least
having
the
release
notes
lead.
You
know,
report
into
sigdoc,
you
know
not
necessarily
every
week
but
regularly
and
maybe
more
frequently
toward
the
end
of
the
release
would
be
good,
I'd,
love
to
see
and
I.
Don't
know
how
to
make
this
happen.
Right,
I
can
think
of
ways
to
try
to
help
improve
the
quality
of
the
original
release.
Note
content
I
did
actually
get
merged.
One
PR
to
provide
a
little
bit
more
guidance
about
how
to
relate
how
to
write
a
release.
A
A
Is
there's
better
sorting
of
release
notes
now,
so
you
don't
have
obscure
low-level
bug,
fixes
mixed
in
with
oh
there's
a
new
feature,
so
so
I
think
that
the
that
the
kind
of
you
know
the
kind
of
critter
a
release
note
refers
to
that
stuff's
better
sorted
now
and
that's
it.
That's
a
huge
improvement,
but
the
actual
content
of
the
individual
release
notes,
at
least
in
draft
form,
is
still
low.
A
A
Well,
yes,
because
right,
oh
yeah,
the
themes
come
in
all
at
the
end,
but
I'm
thinking
more
in
terms
of
individual
PR
release,
notes
right!
That's
where
I
see
I
mean
I
do
think
we
should
have
editorialized
on
those
sig
written
themes
and
have
that
be
a
more
systematic
thing
and
I
think
that
one's
pretty
simple
to
do
it's
the
individual
PR
release,
notes
that
are
a
harder
nut
to
crack.
I
think.
C
C
A
There
is
a
release,
notes
Meister,
as
a
member
of
the
release
notes
as
a
member
of
the
release
team
Yeah
right
that
exists,
but
the
staffing
of
that
has
drifted
away
from
being
at
Oxford
and
putting
two
people
on
it
seems
like
well
that
would
be
lovely,
but
it's
an
open
source
project.
That's
probably
overkill!
A
C
D
So
I
think
at
the
very
least
for
114
what
I'm
hearing
around
the
room
is.
It
wouldn't
hurt
to
check
in
at
the
beginning
of
the
release
in
the
middle
release,
at
the
end
of
the
release
and
to
say:
hey,
I'm,
Jim
angel,
we're
doing
Docs,
and
let's
talk
for
this
release.
It
doesn't
something
to
solve
any
immediate
problems
today,
but
at
least
is
gonna
open.
A
communication
has
exed
there's
no
communication
to
begin
with,
so
I
think
opening
up
that
door
and
then
in
q2
for
115,
maybe
improving
that
process.
A
A
C
We
all
looked
pretty
cooked,
so
all
right,
thank
you.
Everyone,
I,
so
I'm,
going
to
as
soon
as
this
is
done
as
soon
as
I
fly
back
to
Portland
I'm
out
for
like
a
month,
so
I'm
gonna
wish
you
all
the
happiest
of
holidays
and
say
again
what
a
joy
and
a
pleasure
and
a
privilege
it's
been
to
work
with
you
over
the
past
year
and
I'm
looking
forward
to
the
year
to
come.
So
thank
you
for
everything
that
you
do.
This
is
a
really
amazing
cig.