►
From YouTube: Docs SIG 2020 09 25
Description
Jenkins documentation special interest group meeting September 25, 2020. Topics included Hacktoberfest plans, Google Season of Docs, and latest graphs and charts showing areas of strength and weakness in our documentation review team and process
A
A
Last
year
we
had
really
great
results:
multiple
meetups
and
good
sessions,
great
contributions
this
year,
we're
expecting
a
little
bit
less,
but
we're
trying
to
to
staff
up
and
be
ready
for
it.
So
we've
we've
created
a
set
of
github
issues
thanks
to
jonathan
morais,
for
that
and
those
issues
now
need
to
be
triaged
so
that
they
can
be
assigned
some
of
them
anyway.
The
good
first
issue
label
makes
what
we
do
by
triaging.
A
A
We
will
likely
propose
a
hacktoberfest
docs
meetup
during
to
help
hold
during
the
month
of
october,
so
that
we
can
review
how
people
can
contribute
to
dogs,
jonathan
morise,
vlad
silverman,
and
I
are
willing
to
host
that
and
we'll
will
highlight
some
of
the
progress.
That's
being
made
some
of
the
easy
ways
that
there
are
to
contribute
to
jenkins
through
documentation.
A
A
Like
system
administration
or
another
part
like
in
using
or
various
places
like
that
and
create
github
issues
for
a
portion
of
those
sub-trees
based
on
a
reasonable
account
of
the
the
offending
word
in
the
sub-tree,
the
idea
is
that
we
don't
want
to
create
a
single
monster
issue
that
would
require
someone
to
make
many
many
many
changes.
Rather,
let's
create
several
smaller
issues
with
assigned
subsets
and
those
people
can
work
on
the
subset.
A
Take
it
up
complete
it,
submit
the
pull
request
and
go
on.
We
don't
want
the
subsets
to
be
a
change
of
a
single
word
in
a
single
file,
but
rather
some
reasonable
size
set,
and
the
size
of
reasonable
remains
to
be
seen
by
doing
the
the
triage
exercise
after
creating
those
we'd
still
like
someone
else
to
review
the
issue
to
decide
if
it's
a
valid
good
first
issue
and
if
it
is
then
we'll
assign
the
good
first
issue
label
to
it.
A
A
We
had
this
kind
of
hall
of
fame
for
the
jenkins
ui
hack
fest,
and
it
was
exceptional.
It
made
things,
work
smooth,
it
helped
us
highlight
who
was
contributing,
how
they
were
contributing.
Unfortunately,
it
doesn't
look
like
we're
going
to
have
the
capacity
to
create
this
hackfest
repository
this
time.
A
We
jonathan
is
investigating
it,
but
I'm
a
little
worried
that
the
issue
efforts
are
more
crucial
than
having
the
repository
to
track
next
topic.
Google
season
of
docs,
xenop
abu
bakar
has
been
approved
and
is
now
working
on
documenting
jenkins
and
kubernetes
or
jenkins
on
kubernetes
and
that
documentation
progress
is
going
forward.
She's
actually
sent
out
a
draft
and
is
inviting
people's
review
of
her
draft.
A
A
Very
grateful
for
the
help
all
around
there
we're
also
holding
weekly
docs
office
hours.
We've
actually
got
them
scheduled
twice
weekly
and
with
that
twice
weekly
schedule,
we
regularly
have
four
of
us
that
attend
the
monday
office
hours
and
meeting
notes
there
remind
us
of
how
we're
making
progress
a
significant
portion
of
that
has
been
identifying
and
finding
ways
to
make
progress
on
the
wiki
conversion.
A
We
also
coordinated
the
jenkins
2.249.01
lts
testing
in
the
doc
sig
special
thanks
to
vlad
for
his
help.
With
that
thursday
office
hours
we
found
are
rarely
used
since
they're
on
demand.
That's
not
a
problem
just
be
aware
that
many
times
we
will
list
them
as
on
demand
and
when
no
one
appears
we
don't
hold
them.
It's
not
an
issue
in
terms
of
our
progress
and
data
on
contributors
and
contributions.
A
A
It's
it's
not
an
indication
of
degraded
quality
or
anything
like
that.
It's
just
a
hint
that
there's
still
lots
and
lots
of
work
to
do
on
the
time
from
pr
submission
to
engagement
here
on
this
graph.