►
From YouTube: 2020 06 15 Jenkins Docs Office Hours
Description
Jenkins documentation office hours June 15, 2020 with discussions of Google Season of Docs, user feedback summaries, a dashboard that assists with reviewing and understanding user feedback, and examples of alternate techniques to present technical documentation.
A
Also
was
trying
to
well
just
don't
understand,
fully
in
discussion
how
our
terminology
is
related
to
URLs,
because
this
is
not
well
completely
clear
to
me,
for
instance,
if
well
in
case,
if
don't
complex
term
for
master,
let's
say
Jenkins
server,
how
your
ELLs
will
be
dependent
on
this.
This
is
something
that
well
I,
don't
understand
and
would
be
interested
in
understanding.
More
can.
B
A
B
There
was
James
Nord
the
way
he
described
it
was
hey,
that's
quite
ambiguous,
it's
not
clear
what
this
thing
is,
and
so
now
we
have
to
put
a
lot
of
extra
words
into
every
time.
We
use
the
phrase
Jenkins
server
because
we
would
say
Jenkins
server,
and
by
this
we
mean
the
Jenkins
process
or
Jenkins
server,
and
by
this
we
mean
the
host
name
of
the
computer,
hosting
the
Jenkins
process
or
a
Jenkins
server,
and
by
this
we
mean
the
Java,
the
Java
executable.
That's
running
them.
You
know,
therefore,
his
his
concern
was
hey.
B
That's
just
not
precise
enough
and
and
one
of
the
one
of
the
what
I
think
is
a
cool
and
a
very
positive
idea
from
the
terminology.
Discussions
is
what,
if
we,
what
if,
as
part
of
this
made
our
terminology,
more
exact,
more
precise,
so
daniel
beck
noted
that
if
instead,
we
consider
two
different
contexts,
one
context
is
the
thing
that
we
called
master,
which
was
the
Jenkins
process
executing
somewhere,
and
the
other
thing
that
we
called
master
is
the
node
that
is
automatically
allocated
by
Jenkins
on
the
root
server.
B
So
the
the
root
node
is
called
the
master,
node
and
Daniel's
note
was
those
are
two
different
concepts
and
we
don't
want
people
using
the
master
node
to
execute
much.
We
we
guide
them
specifically
do
work
on
agents
not
on
the
master
know,
but
when
we
need
to
refer
to
the
the
top
level
process,
we'd
call
it
the
master
process
or
we
just
call
it
the
master,
and
so
in
both
cases,
it's
a
good
chase,
a
chance
to
drop
the
word
master
and
replace
it
with
something
more
precise.
C
B
Yeah
and
it's
clarity,
clarity
is
helped
right,
particularly
particularly
for
for,
for
instance,
for
non-native
speakers
yeah.
When
we
use
ambiguous
terms,
it
makes
it
even
more
difficult
for
someone
to
comprehend
as
they're
going
crossing
the
language
barrier
as
they're
to
making
the
transformation
from
English
to
whatever
their
their
their
common
languages.
B
So
yes,
so
the
Chinese
I
don't
know
how
they
deal
with
some
of
our
phrasal
verbs
I,
don't
know
how
they
never
ever
handled
the
fact
that
we
we
speak
so
freely,
and
we
use
the
word
get
so
often
with
an
extra
word
over/under
get
by
get
through
and
each
one
of
those
is
an
entirely
different
verb.
So
think
so.
Yes,
there
are
lots
of
lots
of
places
like
that,
where
we,
we
can
be
much
more
precise
and
benefit
not
just
not
just
the
local
language
people,
but
everybody
with
more
precision.
B
Did
that
answer
it
flat?
Is
that
yes,
absolutely
okay?
Now
now
you
you
mentioned
earlier
that
you
had
shared
your
proposal
only
with
the
admins
and
I
think
one
of
the
one
of
the
goals
had
been
to
encourage
people
to
share
it
publicly,
so
others
can
see
it.
Was
it
intentional
that
you
only
shared
it
with
a
narrow
set
of
people
rather
than
making
it
publicly
visible,
or
is
it
publicly
visible.
A
A
A
A
couple
or
weeks
ago,
during
office
hours,
you
introduced
the
spreadsheet,
which
you
put
up
together
some
time
ago
about
different
feedbacks
to
our
issues
are
in
documentation
and
there
was
one
list
of
different
issues
and
I
put
together
the
tool
to
transform
these
issues
from
the
spreadsheet
into
the
github,
which
is
using
not
API
but
hub.
Something
that
you
shared.
D
A
B
I
would
avoid
batch
creating
them
because
many
of
those
feedback
items
have
long
ago
been
resident
been
addressed.
So
if
you
batch
create
an
issue
for
something
that
was
reported
a
year
ago
on
one
of
the
tutorials
as
an
example,
we
saw
that
feedback.
We
acted
on
the
feedback,
we
corrected
the
problem.
So
now,
if
you
raise
an
issue
in
github
with
a
tool
with
a
script,
we
will
just
go
in
and
fairly
quickly,
then
close
it
out
and
be
annoyed
that
you
raised
an
issue
that
was
already
resolved.
B
A
B
A
B
Because,
as
much
as
as
much
as
we
talked
earlier
about
the
master/slave
terminology,
potentially
offending
others,
I'm
personally
quite
offended
by
certain
English
words
that
are
used
commonly
in
places
where
I
find
them
disconcerting
right,
so
profanity
is
not
acceptable
to
me
and
therefore
I
get
involved
very
quickly
on
things
like
that.
Maybe
I
overreact,
but
it's
one
of
those
where
I
get
offended
by
by
profane
language
in
in
my
in
my
tongue.
B
So
so
yes,
definitely
if
someone,
if
someone
drops
the
f-bomb
in
a
or
mate
uses,
it
uses
a
profane
word
in
in
a
bug.
Report.
I
will
do
all
sort,
take
all
sorts
of
steps
to
fix
that,
including
asking
to
ban
them
those
sorts
of
things.
It's
just.
It's
not
acceptable.
The
community
is
very
gracious
in
terms
of
its
its
style
of
communication,
its
conversation
and
the
the
the
contributor
covenant
actually
covers
that
kind
of
thing.
B
B
D
I
yesterday,
I
I
share
my
proposal
at
the
group,
our
groups
to,
and
there
I
put
the
links
to
a
dashboard
that
I
import
all
feedbacks.
So
in
that
dashboard
we
can
see
by
category
each
one
and
helpful
to
help
you
and
me
do
evaluations
and
in
the
monster
case
the
user
are
asking
for
samples,
yeah,
video
samples
and
for
more
more
elaborate
explanations
about
how
to
use
the
comments
or
to
resolve
some
and
big
and
big
O's
terms.
B
A
B
Because
I
thought
it
was
an
interesting
idea,
but
a
concept
that
we
might
get.
For
instance,
I,
think
you
had
done
some
data
analysis
to
see
what
portion
of
the
of
the
feedback
was
not
helpful
versus
somewhat
helpful
versus
and
I
forget
even
the
terms,
but
but
there's
there's
data
in
there.
That
I
think
would
be
good
for
us
to
see
and
consider
yeah.
B
D
D
D
D
D
B
D
C
D
D
So
here
we
can
see
all
the
subjects
requests
provide
the
falls,
it's
the
few
options
for
each
fuge
provide,
with
which
kind
of
returns
and
the
day
on
move
on.
Here
we
can
see
a
time
frame.
Richie
a
peerage
receive
more
and
low
requests,
so
our
more
activity
it.
It
was
this
month,
April
19
and
that
space
here
and
you
can,
for
example,
click
on
them.
D
D
B
Thank
you,
nice
thanks
very
much
Jonathan
yeah!
That's
that's
quite
so
so
it
looks
like
there
are
some
high
high
frequency
areas
and
they
seem
to
be
okay.
Pipeline
builds
tips
over
so
pipeline,
three
three
of
the
tours
yeah
and
that
and
that
truly
amazes
me,
because
three
of
those
I'll
have
to
double
check,
but
I
think
those
three
tours
are
now
all
functioning,
but
but
they
were
still
high
feedback
points
and
then
the
get
plugin
okay
I've
tried
my
very
best
to
fix
that
one.
So
that
was
one
that
was
laced
with
profanity.
B
Absolutely
there
are
lots
where
people
said
I
want
this.
So
give
me
examples,
give
me
and
so
I
wrote
examples
and
they've
been
posted
and
and
they're
now
part
of
the
documentation.
Now
actually,
for
my
benefit,
could
you
zoom
in
on
git
I'd
like
to
see
if
look
at
the
timeline
or
Lonnie
back
on
the
get
page
feedback.
B
B
B
D
Another
important
point
and
I
believe
the
our
dogs,
it's
right
and
for
more
experienced
users,
so
we
need
to
write
a
new
way
to
embrace
the
new
ones.
For
simple
it's
a
here.
It's
say
a
exactly
example.
Good
example
for
a
beginner
would
be
good
if
they're
at
least
small
samples,
maybe
because
we
have
a
lot
of
experience
in
our
career.
It's
easy
to
read
and
understand.
The
topics
are
the
main
concepts
about
the
defect
about
Dane
Jenks.
Okay,
maybe
we
need
more
beginner
samples.
D
C
B
Really
can't
because
they,
the
sheet,
is
right
only
so
the
the
process
that
maintains
the
sheet
appends
to
the
sheet
and
no
one,
but
that
process
has
permission
to
write
to
the
sheet
and
we
don't.
We
intentionally
do
not
show
the
contents
of
the
sheet
to
anyone,
because
because
the
content
is
completely
unfiltered
and
has
no
safeguards
on
it
right.
So
if.
B
C
B
C
C
B
Is
correct
but
I
think
I
think
long
term
and
it's
already
the
transition
has
already
actively
started
long
term.
We
will
switch
more
and
more
people
to
give
us
github
issue
reports
for
their
for
their
problems
for
the
page
rather
than
submitting
to
this
feedback,
so
Jonathan
I'm
gonna,
stop
your
sharing
and
I'm
gonna
bring
up
okay,
bring
up
the
share
of
mine
so
that
we
can
look
at
what
one
of
the
pages
look
like
and
see
the
the
the
different
ways
that
people
can
give
feedback.
Okay.
B
C
B
B
B
So
so
what
we
see
is
things
like
list
get
branches
which
is
completely
unrelated
to
matrix
combination,
parameter
value
and
and
therefore
yes,
it's
this
thing
is
complicated
and
dependent
on
each
plug-in
having
good
documentation
that
then
gets
contributed
to
this
thing.
So
this
is
a
step
which
generates
a
build,
and
now
each
plug-in
that
can
contribute
to.
It
has
some
some
piece
so,
for
instance,
the
clearcase
UCM
baseline
parameter
value
has
has
that
or
boolean
per
am
yeah,
so
I
can
understand
why
their
feedback
on
this
page
would
be.
But
now
what
are
the?
B
What
are
the
a
leaner
yeah?
Yes,
now?
What
are
the
things?
The
places
where
they
can
give
feedback
to
us
was
this
page
helpful
that
opens
up
the
form
that
takes
them
to
the
to
the
the
data
entry
form
for
the
spreadsheet,
so
this
will
put
data
into
the
spreadsheet,
and
this
should
open
the
sheet
to
show
me.
Okay.
Here
it
is
yeah.
It
does
now
what
we've
got
instead
on
pages
that
are
not
generated
like
on,
let's
go
to
installing
Jenkins,
so
uninstalling
Jenkins
at
the
very
bottom
you'll
see.
B
Was
this
page
helpful,
but
we've
also
got
improve
this
page
and
report
a
problem
and
if
I
click
improve
this
page,
it
will
take
me
to
github
and
I'm
right
in
the
source
code
of
the
page.
So
that's
if
you
want
to,
if
you
want
to
help
us,
improve
the
page,
here's
your
chance
now,
if
I
instead
click
the
report,
a
problem,
it
takes
me
into
github
issues
and
now
I'm
ready
to
report
a
bug.
B
The
reason
that
the
build
step
does
not
do.
That
is
because,
in
order
to
fix
a
bug
in
the
build
step
page
in
order
to
fix
a
bug
and
actually
any
one
of
these
so
but
in
the
build
step
page,
we
had
it
here
in
order
to
fix
a
problem
in
these
descriptions.
I
have
to
go
to
the
plugin,
that's
contributing
each
of
these
sections.
B
B
But
see
my
worry
is
I,
don't
I
wouldn't
want
to
distract
the
reader
from
the
this
is
generated
rather
the
thing
that
does
the
generating
it
would
be
best
if
it
could
create
links
somewhere
somehow
inside
the
page.
That
say
go
here
to
fix
this
page.
So
here's
the
the
link
to
the
plug-in
on
the
plug-in
site,
and
so
this
tells
me
which
plug-in
repository
is
contributing
the
route
description.
C
Grade,
but
this
is
really
a
page
for
experts
and
up
at
the
top
of
the
page,
it
has
reference
them
to
the
the
other
steps
reference
page,
the
first
one
you
have
right,
that's
really
buried
I
have
to
really
go
looking
for
that
mm-hmm
and
I'm
thinking
that
a
lot
of
these
that
want
more
examples
and
stuff.
It's
like
you
shouldn't
be
on
this
page.
You
should
be
on
that
page
right.
B
D
D
D
D
D
B
B
D
D
D
B
D
B
D
C
C
B
Is
but
the
challenge
of
those
is
those
are
truly
honor
and
executing
Jenkins
instance,
and,
and
my
hunch
was
that
the
project
is
probably
not
ready
to
fund
an
unlimited
number
of
Jenkins
instances,
even
small
ones,
running
for
for
purposes
of
teaching
so
but
I'm
fascinated
by
the
idea.
So
this
really
is
showing
static
pages
that
are
highlighting
highlighting
different
capabilities
and
then
the
question
is:
could
we
do
something
similar
with
static
pages
for
the
Jenkins
documentation?
Interesting.
B
D
A
Talking
to
mark
your
previous
page,
which
you
addressed
with
all
which
is
generated
from
all
different
plugins
in
case,
it
is
possible
to
not
collapse
but
expand
all
these
different
steps.
I'm,
not
sure
how
significant
this
effort
is
and
use.
Ctrl
F
the
users
will
be
able
to
switch
within
this
large
dynamic
region.
11:00.
B
And
tentative
out
and
note
that
the
page
originally
started
with
everything
expanded
and
the
users,
the
users
were
were
quite
vocal
that
this
page
is
unacceptably
long
and-
and
this
page
is
actually
a
small
page
compared
to
if
we
look
at
I'm
gonna
terrify
everyone
now
by
loading
this
page
the
check
out
step.
Let's
do
it
separate
tab
because
it
takes
a
while
if
we
load
the
check
out
step
its
oops,
let's
find
the
right
page
steps,
but
it's
huge
it's
it
makes
it
makes
the
build
step.
Look
tiny,
it's
so
big!.
B
It
check
out
check
out
okay
there,
there,
alright,
so
here's
the
general
s
Yemen
and
while
we're
sitting
in
this
meeting,
just
wait,
we'll
we'll
watch
and
eventually
this
will
collapse
itself.
It
will
collapse
itself
when
the
page
has
finished
loading.
The
page
we'll
finish
loading
two
or
more
megabytes
of
data
into
it.
So
it's
it's
in
and
you
see
the
list.
The
list
of
SCM
providers
is
probably
50
percent
longer
than
than
a
list
of
build
targets,
and
each
of
these
things
has
let's
expand.
B
This
one
has
a
huge
page
of
more
expandable
things,
so
so
absolutely
there's
gotta
be
a
way
to
do
this
better
and
Jonathan's
idea
of
making
it
some
have
more
interactive,
more
searchable,
more
comfortable
and
feels
like
a
big
win
so
so
Jonathan
using
that
concept
from
from
beautify,
for
instance,
seems
like
they've
got
shorter
pages.
Let's,
let's
leave
it's
a
grid,
although
they
aren't,
they
aren't
terribly
short
because
as
I
look
at
them,
the
scroll
bars
is
there's
plenty
of
content
about
grid
there.
D
D
D
B
B
B
D
D
B
A
Related
to
frequently
asked
questions,
we
have
every
Q
for
specific
sections,
but
during
our
discussions
online
in
chat
rooms,
for
instance,
mark
is
very
often
answering
very
interesting
questions,
providing
answers
and
I
thought.
Maybe
it
makes
sense
to
collect
all
these
different
topics,
answers
questions
and
start
creating
general
FAQ
section
for
entire,
using
all
Jenkins
overall
and
so
I'm
not
sure.
Yet
how
to
organize
this.
But
maybe
it
will
start
recovering
the
entire
all
different
aspects
of
using.
B
B
Too,
and
so
and
I
think,
questions
that
are
asked
are
are
an
interesting
source
of
data
for
us
to
to
gather
and
consider
what
should
we
put
into
the
material
I?
Don't
think
we
would
want
to
become
a
stack
overflow,
but
I
see
no
reason
why
we
could
not
mine
or
gather
for
good
questions
from
stack
overflow
and
say:
hey
look
here:
are
these
questions
collect
the
questions,
group,
sort,
shuffle,
categorize
them
and
say
hey?
If
we
had
wanted
to
answer
that
question
on
Jenkins
that
IO
instead
of
Stack
Overflow?
B
Where
would
we
have
put
the
documentation?
And
let's,
let's
do
that,
because,
because
there
are
excellent
question
and
answer
sites
already
out
there,
that
are
impressively
populated
with
Jenkins
answers.
If,
if
you
look
at
the
the
Stack
Overflow
Jenkins
tag
and
the
Jenkins
pipeline
tag,
it's
amazing
the
number
of
questions
that
are
there
and
and
many
times
it's
a
question
without
an
answer
or
a
question
with
a
dare
very
deep
and
involved
very,
very
thorough
answer.
So
so
a
good
good
point
I'm,
not
sure
that
FAQ
is
the
way
I
would
frame
it.
Personally.
B
I
was
thinking
that
it
would
be
more
of
a
book
here.
Are
these
here?
Are
these
questions
that
are
asked
I
think
our
goal
should
be
to
make
the
answers
already
be
available
in
Jenkins.
That
I
owe
so
that
we
could
point
them
to
the
answer
in
that
page
and
say:
here's
where
it
answers
this,
but
this
would
cover
this
right
and
there
are
plenty
of
things
where
we
we
don't
don't
yet
have
an
answer
right.
B
A
B
D
D
B
So,
for
me,
I
think
continue
continue
contributing
to
the
project
so
that
you
get
a
sense
for
how
does
the
project
work?
What
are
the
things
that
will
help
it?
You
might
now,
because
we're
we're
tending
to
run
out
of
the
initial
set
of
of
tickets
that
we
had
created
for
for
transformation.
It
may
be
time
to
go
into
the
triage
page,
the
triage,
spreadsheet
and
start
looking
at
those
things
and
doing
some
triage
so
check
out
a
page.
B
B
I'll
get
some
time
this
week
to
triage
a
few
more
pages
in
so
that
by
the
end
of
the
week,
we'll
have
some
additional
material
that,
but,
but
you
could
do
the
triage
almost
as
well
as
I
could,
particularly
given
that
you've
both
had
time
looking
through
the
documentation.
So
you've
got
a
sense
now
of
where
things
are
described
and
where
they're
not
described
so
I'd
suggest
take
triage
triage
one
or
two
of
the
existing
wiki
pages
that
haven't
yet
been
transformed
and
and
choose
one.