►
From YouTube: Docs SIG 2019 05 24
Description
Jenkins documentation special interest group meeting recording from May 24, 2019. Topics included web site improvements, progress on bug reports, progress on pull requests, and a review of the available feedback data for pages on the Jenkins.io documentation site
A
Hi
I'm
mark
wait.
Welcome
to
the
Jenkins
documentation.
Special
interest
group
today
wanted
to
do
a
brief
summary
of
our
progress
in
the
last
two
weeks
over
the
Jenkins
documentation.
So
first
topic
previous
action
items,
the
docs,
a
pull
request
has
been
submitted
to
the
blog
post,
has
been
created.
I
have
one
action
item
open
that
the
docs
project
ID
is
need
to
be
included
in
a
pull
request.
A
A
Shows
on
the
left,
unresolved
status
on
the
on
the
bottom
left
and
web
site
unresolved
as
a
filter
on
the
right
thanks
very
much
Sarada
component
for
creating
that
page.
Beautiful
word
welcome
Kristin,
so
we've
got
John,
Hawes
blog
post
is
done
and
or
rather
than
contributing
dog
for
Jenkins
X
is
done,
and
participants
have
begun.
Reviewing,
pull
requests
grateful
for
help
from
Roddick
from
make
make
McRoberts
and
others
Oleg's
also
completed
their
mentor
instructions
as
a
pull
request
to
Jenkins
that
IO
Kristen.
A
Okay,
so
we've
got
action
proposals
that
we
would
like
to
cover
we'll
take
these
another
week
or
another.
Two
weeks
weeks
from
now,
Oleg
is
unable
to
attend
today.
Likewise,
for
the
community
bridge
status
report
in
terms
of
a
toxic
infrastructure
status
report,
jet
for
progress
is
on
track,
looks
good.
There
are
a
few
items
left
to
do.
We
will
continue
reporting,
at
least
once
a
month
to
the
to
the
Jenkins
governance
project
website.
Bug
reports
have
been
reviewed
and
we've
made
really
good
progress
on
clearing
them
up.
Tidying
them
up.
A
We
could
really
use
help
from
other
team
members
in
the
doc
suit
to
review
those
bug,
reports
and
especially
identify
ones
that
are
newbie
friendly.
Will
we've
got
another
topic
here
on
the
plugins
site.
Reviewing
strengths
and
weaknesses
will
prefer
this
for
another
two
weeks
and
then
I
wanted
to
take
some
time
here
today
to
talk
about
prioritization
and
prioritizing
our
documentation
effort
with
data.
So
one
of
the
things
that
had
been
created
a
year
or
two
ago
was
a
page
feedback
mechanism
for
sub
pages
on
the
Jenkins
IO
site,
and
we've
now
got
results.
A
So
the
page
is
most
voted,
not
helpful.
Our
the
Jenkins
pipeline
get
step.
Okay
is
the
maintainer
of
that
plugin.
Shame
on
me:
that's
one
to
work
on
a
hello
world
tour
and
the
environment
tour.
Those
those
get
plug-in.
I.
Think
I,
understand
that
particular
step
is
syntactic
sugar
and
should
be
pointed
to
check
out.
But
hello,
world
and
environment
are
both
intentionally
structured
to
help
students
help
readers
get
benefit,
and
yet
they
have
strong,
no
votes.
The
staining
page
is
empty,
so
getting
not
helpful
on
an
empty
page
is
no
shock.
A
The
build
step
is
a
seedings,
Lee,
complicated
and
so
strong,
no
votes.
There
knows
no
surprise.
That's
a
project
idea
we
should
probably
put
in
the
nodes
page
is
also
empty.
So
for
me
that
page
feedback
results
gives
us
some
hints
of
possible
project.
Ideas
that
we
can
put
into
the
system
will
capture
those
in
an
upcoming
pull
request
to
Jenkins
that
IO
and
put
each
of
them
in
there
as
an
idea
of
someplace
that
could
be
approved.
Improved
now,
I've
got
some
really
good
news.
A
Let's
look
at
the
at
the
graph
here
in
the
last
month.
We've
dramatically
increased
both
the
number
of
contributors
and
the
number
of
contributions
to
the
Jenkins,
not
I/o
site.
We've
also
had
some
significantly
positive
contributions
from
in
the
area
of
social
media,
helps
that
make
our
pages
more
attractive
when
presented
through
social
media.
So
when
there's
a
Twitter
link
now,
for
instance,
there
will
be
a
picture
associated
with
it
that
will
be
included
in
the
Twitter
feed
only
indicates
there's
more
work.
A
We
can
do
to
further
improve
that,
but
this
is
a
nice
step
in
just
the
two
or
four
weeks
since
we
started
the
platform.
The
documentation
special
interest
group
as
another
positive,
our
open
pool
requests
count
is,
has
dropped
dramatically.
We've
resolved
many
many
pull
requests
we're
under
10
and
have
been
under
10,
open,
pull
requests
for
3
or
4
weeks
now.
So
thanks
very
much
to
those
doing
poor
reviews
of
pull
requests.
A
There's
some
other
surprises
here
which,
in
the
data
which
I
didn't
quite
understand,
but
I
would
like
to
highlight
the
second-highest
referring
site
to
the
our
github
repository
for
Jenkins.
Io
is
actually
Wilson.
Mars
blog
and
he's
got
a
page
there's
a
set
of
pages
there
that
our
Jenkins
tutorials
they
are
more
frequently
referring
to
the
source
code.
A
B
No,
not
really,
but
I
did
notice
when
you
were
talking
about
the
pages
that
were
not
as
helpful.
Two
of
them
are
part
of
a
that
are
could
be
related
to
a
sub
project.
That
would
be
you
fixing
the
pipeline
steps
documentation,
which
is
something
that
we
hit
book
two
you
have
as
a
google
Summer
of
Code
project,
or
it
could
be
like
a
season
of
Docs
project
eventually,
but
yeah
there's
like
a
lot
that
could
be
done.
There
didn't
prove
that
so
excellent.
A
B
So
the
one
that
says
that
the
build
step
it
stopped
so
see
there
they're
part
of
the
steps,
Auto
generation,
so
there's
some
work
that
could
be
done
there.
So
it's
interesting
I
agree
with
you
about
the
hello
world
tour
in
the
environment.
Tour.
It's
interesting
that
they.
It
is
there
a
way
that
we
can
see
more
about
why
they
said
it
wasn't
helpful
or
is
it
just
kind
of
it
was.
A
B
A
B
All
good
I
think
some
of
the
parts
of
that
is
it's
just
difficult
to
figure
out.
What's
going
on
in
general,
with
the
plug-in
steps
and
so
much
easier,
just
have
the
pipeline
or
the
general
generation.
Let
the
snippet
generator
inside
bake
Jenkins
itself.
It's
a
lot
easier
to
see.
What's
going
on
there,
but
yeah.
A
That's
and
that's
so
I'm
delighted
this
was
the
work
originally
of
Giles
Gaskell.
It
was
almost
two
years
ago.
They
did
this
initiative
and
I'm
really
thrilled
that
it's
still
gathering
the
data
and
we
can
use
the
data
I
find
it
interesting.
It's
it's
also
it's
another
piece
of
data
that
I
haven't
yet
extracted
is
how
many
pages
got
votes
at
all.
You
know
aggregate
total,
because
that
may
hint,
which
pages
are
most
heavily
heavily
viewed,
mm-hmm.