►
From YouTube: Docs SIG 2020 02 14
Description
Jenkins documentation special interest group meeting February 14, 2020. Topics include plugin redirects from wiki to https://plugins.jenkins.io , docs conversion progress report, Google Season of Docs introduction, and note that the Docs SIG meetings will switch from every two weeks to every four weeks.
A
A
Hi
everyone-
this
is
Mark,
wait!
Welcome
to
the
Jenkins
special
interest
group
meeting
today,
we'll
talk
about
preview
will
review
previous
action
items.
I'll
do
a
demonstration
of
plug-in
redirects
from
the
wiki
and
how
you
extract
change.
Log
change
Logs
with
the
wiki
exporter
as
a
way
that
highlight
the
progress.
We're
making
on
migrating
plugins
from
wiki
to
to
hosting
their
own
documentation,
talked
briefly
about
google
season
of
docs
and
then
review
the
latest
data
on
contributors
and
contributions
so
get
started
first
with
that
demo.
A
So,
thanks
to
marvelous
work
by
Gavin,
Magan
he's
now
implemented
wiki
redirects
for
most
of
the
plugins
in
the
system,
so
the
wiki
documentation
still
includes
some
general
Docs
like,
for
instance,
this
page
how
to
report
an
issue
and
will
eventually
get
this
page
migrated
as
well,
but
the
wiki
is
still
readable
for
those
who
need
information.
That's
on
it.
However,
if
I
go
looking
for
a
plug-in
like
the
git
client
plug-in
or
the
get
plugin.
So
let's
look
for
git
client
plug-in
in
the
wiki.
A
What
Gavin
has
done
with
the
redirects
to
make
things
simple,
clean
and
fast
plug-in
documentation
now
appears
sooner
is
easier
to
read
and
easier
to
maintain.
So
how
are
we
doing
on
our
progress?
Well,
up
to
this
point,
over
two
hundred
and
sixty
plugins,
you
see
here
to
over
two
hundred
and
sixty
plugins,
have
migrated
completed
the
migration
and
released
a
new
version
using
documentation
from
the
wiki
are
using
patient
from
github,
not
from
the
wiki.
A
Thanks
very
much
we've
had
contributions
from
students
from
plugging
authors,
certainly
contributions
from
many
others
who
were
helping
us
as
we
transition
away
from
the
wiki
for
plugin
documentation
to
plug
in
documentation
inside
the
github
repositories.
The
the
charts
here,
the
page
here
that
shows
us
the
progress-
is
a
great
way
to
find
a
plug-in
where
you
can
help,
and
you
click
one
of
these
and
it'll.
Take
you
to
a
plug-in
that
has
not
yet
been
transferred
transferred.
So
let's
take
the
Javadoc
plug-in,
for
instance
this
one.
A
A
A
I
grabbed
that
page
be
able
to
put
this
into
this
converter
do
convert
and
it
will
read
the
page
from
the
wiki
and
present
me
that
in
this
case,
in
marked
out
here,
it
is
and
notice
here's
the
changelog,
so
I
could
copy
the
content
of
this
change
log
into
a
pull
request
to
the
Javadoc
plugin.
It's
that
easy,
that's
straightforward!
A
A
So
if
you
want
to
find
a
way
to
help
here,
you
could
choose
one
of
these
that
has
not
yet
been
approved,
review
the
pull
request
and
note
your
approval
of
it.
That
way.
The
author,
the
maintainer
of
the
plug-in,
has
one
more
person
who
said
yep,
I've
reviewed
this
documentation.
It
looks
correct
and
is
ready
to
go
so
here's
a
great
chance
to
use
the
wiki
exporter
keep-keep,
add
a
plug,
a
change
log
to
the
plug-in
repository
and
then
update
the
readme
to
refer
to
the
change
log.
A
Now,
in
addition
to
a
google
season
of
Docs,
we've
got
as
a
concluding
item
the
data
on
contributors
and
contributions.
So
this
first
graph
shows
us
that
the
time
from
pull
request,
creation
to
first
engagement
by
a
reviewer
in
giving
comments
or
feedback
on
the
pull
requests.
And
what
you'll
see
is
over
the
last
three
or
more
months.
We've
solidly
kept
the
time
to
give
feedback
under
four
hours
for
over
50%
of
the
of
the
pull
requests
and
in
general
time
for
feedback
right
now
for
the
85th
percentile
is
still
well
under
one
day.
A
Looking
good
poor
request
process
is
healthy
on
Jenkins
thought,
I
hope
we
keep
handling
things
as
they
come
in
get
them
deployed
now
time
from
PR
open
to
PR.
Merge
is
also
holding
nicely
and
looking
good.
Our
median
there
is
that
we're
well
under
10
hours,
probably
on
the
order
of
two
hours
for
our
time
to
from
PR
submission
to
merge
and
at
the
85th
percentile
were
still
well
below
it
one
day,
as
our
typical
and
under
four
days
for
the
last
multiple
months
of
staying
cleanly
below
that
that
four
day
limit.
A
In
addition,
we've
had
good
pull
requests
and
all
have
merged.
In
the
last
month,
we've
had
84
pull
requests,
merge
from
30
different
authors
and
very
grateful
for
those
contributions
from
all
sorts
of
contributors
to
the
community.
We
have
eight
open,
pull
requests
currently
and
have
over
the
lifetime
of
the
Jenkins
at
I/o
site.
Close
2,800
pull
requests
thanks
to
everyone.
Thanks
very
very
much-
and
this
concludes
our
meeting
today.