►
From YouTube: 2022 11 17 Docs Office Hours
Description
Includes a 15 minute tutorial on the duties of the Documentation Officer with links and examples of the tasks that Mark Waite has performed. The new Documentation Officer, Kevin Martens, was leading the meeting and has the details in the notes and in this recording.
B
Welcome
everyone
to
the
Jenkins
docs
office
hours.
This
is
the
European
U.S
hours
on
November
17th.
Today
we
have
Mark
Wade
myself,
Bruno,
Brockton
and
Alex.
Brandeis
is
here
as
well.
Welcome
to
everyone
and
thanks
for
joining
on
today's
agenda,
we
have
an
action
item
about
switching
the
docs
mailing
list,
some
information
to
share
about
the
Jenkins
elections,
some
talk
about
in
a
conversation
around
the
documentation
officer,
duties
and
what
that
means.
B
Just
a
couple
updates
on
the
next
LTS
and
weekly
and
then
a
couple
items
about
next
Thursday
Thanksgiving
is
in
the
U.S,
so
status
of
doc's
office
hours
and
another
blog
post
that
will
be
coming
out.
Is
there
anything
else
that
anyone
would
want
to
add
to
the
agenda
today
or
does
that
cover
things
for
today?.
B
Okay,
great,
thank
you
so
much
so.
The
first
thing
is
that
you
are
the
doc's.
Mailing
list
needs
to
be
archived
and
switched
over
to
the
community
Dot
jenkins.io
site.
That
is
something
that
I'll
be
working
on
with
Mark
as
we
transition
into
the
next
term
of
Jenkins
election
winners.
Right
I,
don't
know
how
to
say
it,
but
yeah
on
that
note,
though,
so
the
Jenkins
elections
have
been
officially
announced
today.
B
What
this
means
is
that
we
do
have
all
new
board
members
and
officers
and
because
each
role
only
received
one
nomination
everyone's
a
winner.
So
congratulations
to
Alex
and
Ulrich,
who
are
now
new
board
members
for
the
Jenkins
governance
board
and
for
officers
tinjcon
will
be
staying
in
the
release
officer
role,
as
will
Alyssa
in
the
events
officer,
rule
waddock
will
be
staying
on
a
security
officer.
I
will
be
joining
as
documentation
officer
and
Damian's
going
to
stay
in
infrastructure
officer
for
the
next
term
as
well.
B
B
But
since
we're
not
technically
having
actual
elections
this
year,
yeah
we've
it
may
not
be
as
useful
as
the
blog
post
or
any
other
community
point
for
getting
the
information
but
Community
threat.
Is
there
it's
always
available,
so
we
can
always
discuss
more
on
there
or
talk
about
things
in
the
discourse
thread.
C
Yeah
Kevin
Let
Me
Maybe
add
something
to
that.
Maybe
you
should
add
that
to
the
blog
post
that
we
don't
have
elections
like
last
year
or
the
year
before
in
case
someone
asked
like
where
do
you
need
to?
Where
do
I
need
to
go
to
vote,
because
last
year
and
the
year
before,
we
use
the
third
party
service
for
that
people
may
be
familiar
with,
and
if
we
don't
do
that
this
year,
people
may
be
confused
if
they
need
to
vote.
Where
do
they
cast
their
vote
and
so
on.
B
Right
right,
but
and
typically
we'd,
be
using
the
condorset
voting
system
from
Cornell.
I
I
did
check
with
Mark
about
this
one,
and
he
did
share
that
in
the
in
the
past.
When
a
particular
role
receives
one
nomination,
an
election
is
not
required.
This
year.
We
have
that
exact
situation
happen
for
all
the
board,
members
and
officers,
so
that
is
spelled
out
there.
But
if
there's
some
more
detail
that
can
be
added
or
some
additional
Clarity
that
can
be
provided
I'm
more
than
happy
to
help.
C
B
Yeah-
and
we
can
definitely
like-
we
still
have
to
I-
still
have
to
propose
the
tweet
and
Linkedin
post
to
be
submitted,
so
we
can
definitely
say
specifically,
you
know,
Jenkins
elections
results
or
something
like
that
to
signify
that
there
is
not
a
voting
period
this
year.
So
yeah
definitely
definitely
agree
on
that.
We
can
definitely
make
that
more
clear,
so
yeah.
Thank
you
very
much.
Alex.
Is
there
anything
else
that
you
wanted
to
share
or
add
on
for
the
election
step,
or
is
that
cover
things.
B
B
Okay,
wonderful,
then,
the
next
thing
on
on
the
agenda
is
just
going
over
the
documentation,
officer
duties
so
Mark
and
I
were
talking
earlier,
and
we
wanted
to
just
go
over
this
review,
what
the
documentation
officers
purposes
and
a
little
bit
about
what
they
do
or
I
guess
what
I'll
be
doing
over
the
next
year.
In
my
efforts
to
help
maintain
and
keep
up
Jenkins
as
best
I
can
so
Mark.
As
far
as
this
goes,
do
you
want
to
start?
A
Sure
yeah
well,
if,
if
everybody
else
is
okay,
if
Alex
and
Bruno
don't
mind
listening
as
we
talk
as
I
talk
through
the
the
topic-
let's,
let's
do
it:
okay,
great
so
so,
Bruno
and
and
Alex.
The
idea
here
was:
let's
go
through
and
get
a
recorded
session
that
talks
about
what
are
the
duties
of
the
documentation,
officer
and
I
captured
these
items
as
places
to
discuss
that
way.
Kevin's
got
it
and
we've
got
an
archive
and
then
Kevin
will
put
it
into
the
Jenkins
Jenkins
site
so
that
it's
documented
officially
there.
A
Will
document
that
too?
Yes,
exactly
good
to
talk,
yeah,
okay,
I
got
it
very
good,
that's
correct
yeah,
so
so
they're
at
least
there
are
several
several
areas
right,
Jenkins
documentation
site
is
one
Jenkins
releases
is
another.
There
are
also
those
are
the
two
big
ones
for
and
then
there's
there
are
certainly
sub
subtopics
under
those,
but
those
are
the
two
big
ones
that
were
on
my
mind,
if
others
have
other
areas
of
documentation,
certainly
interested,
but
those
were
the
key
ones
for
me.
Oh
oh
I,
take
it
back.
A
A
B
And
I
actually
I
think
it
was
Eve
that
messaged
me
in
the
last
week
or
so
too,
asking
like
if
that's
if
they
can
just
ping
me
and
let
me
know
when
documentation
is
needed
so
that
I
can
assist
there
and
I
just
want
to
put
that
out
there
as
something
that's
that
falls
in
line
with
all
of
this
as
well.
If
there's
anything
that
doesn't
have
documentation
and
feels
like
it
needs
it,
I
can
constantly
be
reaching
and
I
can
always
help
with
that.
B
A
D
A
You,
okay
Kevin,
if
we
just
go
through
this
piece
piece
by
piece,
because
I
think
it's
worth
us
doing
a
record,
including
in
the
recording.
So
let's
start
all
the
way
up
at
the
top,
the
Jenkins
documentation,
site,
review,
refine,
update
and
merge,
pull
requests,
so
click
that
pull
request,
link
that
takes
us
to
you're
already
doing
this
and
you're
already
comfortable
with
this.
A
What
this
means
is,
you
are
a
member
of
the
the
correct
group
that
allows
you
permission
to
merge
so,
for
instance,
pick
the
automated
change
log
for
379
that
one
and
if
we
look
at
the
bottom
of
this
one,
it
says,
merge,
oh
merging
is
blocked
because
we
haven't
had
any
approval.
Yet
so,
let's
for
the
for
the
fun
of
it,
you're
going
to
approve
this
one,
so
go
up
to
the
top
okay,
eventually
you're
going
to
have
to
approve
it.
So
now
add
your
review
say
approved
and
you
could
put
a
comment
temporary.
A
Right
and
we
won't
merge
it-
we're
just
going
to
see
that
the
button
notice
you've
got
the
green
squash
and
merge
button.
Other
users
don't
get
that
so
that
that
proves
you
have
the
permissions.
You
need
to
do
this
test
so
now
go
back
to
the
Google
Doc,
okay
review
and
act
on
issue
reports.
This
is
we
track
issues
with
the
documentation
on
this
GitHub
issue.
Tracker
and
you'll
see
here
a
list
of
127
open
issues.
A
Now
these
are
relatively
mature,
meaning
they've
been
there
a
long
time
and
there's
lots
to
do
to
improve
on
many
of
them.
But
you
get
to
think
about
hey
which,
which
one
should
we
focus
on?
Why
should
we
focus
on
that?
One
so
scroll
down
a
little
bit
and
I'm
going
to
show
you
one
that
is
of
interest
to
me
whoops
right
there
up
a
little
installing
Linux
page
has
no
upgrade
instructions.
A
This
is
one
that
I
think
would
be
very,
very
nice.
We
had
a
contributor
who
said
I
want
to
do
it,
but
then
he
didn't
do
anything
on
it
and
so
I
think
it
would
be
really
nice
for
us
to
have
instructions
on
how
to
do
an
upgrade
so
back
to
the
doc.
Now
so
issue
tracking
and
pull
request
tracking
there's
another
bookkeeping,
effort
click.
The
docs
issue,
reports
on
jira
thing.
A
So
these
are
issues
that
were
reported
to
the
to
the
jira
site
before
we
switched.
But
what
you
need
to
do
is
periodically
look
and
in
the
top
left
corner
If.
Instead
of
order
by
priority,
you
would
click
that
and
say
order
by
create
created,
okay,
because
what
that
will
tell
us
is
which
ones
are
are
may
have
arrived
recently
in
the
wrong
location.
A
A
It
if
a
new
one
arrives
here,
you
could
you
can
the
first
choice
is:
ask
the
submitter
hey.
Please,
could
you
send
submit
this
as
a
GitHub
issue?
Instead,
if
they
don't
do
it,
then
you
could
do
it
yourself,
okay,
right
I?
Can
it's
actually
easier
for
most
submitters
to
submit
a
GitHub
issue
than
it
is
to
submit
a
jira
issue
because
their
GitHub
issue,
they're
already
using
their
GitHub
account
in
order
to
submit
to
jira
they
have
to
have
a
Jenkins
account,
got.
A
Correct
right:
okay,
so
let's
go
back
to
the
to
the
so
next
now
we're
getting
into
the
place
where
we
may
see
things
in
the
recording
that
are
uncomfortable,
I
apologize.
If
someone's
offended
click
that
page,
let's
open
it
and
the
reason
I
say
it
may
be
offensive-
is
sometimes
people
say
things
or
write
things
in
this
that
are
really
rude
and
and
rude
to
the
point
of
you
know:
I'm
foul
language,
profanity
Etc.
A
D
A
A
You'll
see
here,
improve
this
page
or
report
a
problem.
If
you
click
improve
this
page,
it
will
take
you
right
to
GitHub
good.
If
you
click
report,
a
problem
takes
you
right
to
this.
There
are
some
of
the
pages,
however,
that
have
a
a
survey
on
them.
I,
remember
right,
for
instance,
the
was
this
page
helpful.
Yes
there.
It
is
that
one
if
you
click
that
one.
If
someone
fills
in
this
field,
it
gets
published
the
results
of
that
gets
published
to
this
spreadsheet,
and
so
sometimes
you'll
get
a
useful
bug
report.
A
Sometimes
you
get
people
saying
things
that
are
really
really
foul
right
and,
and
you
just
have
to
ignore
those-
don't
don't
be
offended
by
them,
just
ignore
them
yep
it's.
This
is
completely
Anonymous
feedback
and
if
you
look
for
various
forms
of
profanity
you'll
find
them
in
this
file.
That's
not
the
objective
right.
A
D
A
A
B
D
B
A
Either
way
exactly
and-
and
this
is
not
a
page-
we
worry
about
updating
right,
it's
just
it's
just
a
a
log
of
people's
comments
and
if
sometimes
the
comments
are
helpful,
we
use
those
comments
and
if
they're
not,
we,
we
just
keep
going.
For
instance,
the
page
you're
on
right
now
hasn't
complaint
about
the
git
plug-in,
and
that
was
what
motivated
me
to
do
a
much
better
job
documenting
that
plug-in.
So
there
are
times
when
this
inspires
us.
A
A
It's
encouraging
yeah.
It
is
yes,
but
yeah.
Okay,
so
are
you
comfortable
with
this
page
Kevin
in
terms
of
what
you
do
there
yep
all
right,
so
the
next
next
one
down,
then,
is
create
documentation
that,
when
you've
already
been
doing
it
with
your
additions
to
the
blue
ocean
page
with
your
editions
of
screen
of
videos
that
are
relevant
to
particular
topics,
you
add
those
relevant
videos
in
and
I
think
the
users
we've
got
good
evidence
based
on
click
counts
on
those
videos
that
the
users
appreciate
that
so
so
keep
doing
that.
Okay,.
A
A
B
A
Do
we
really
need
a
top
level
entry
for
Jenkins
remoting?
Probably
not
the
document
Jenkins
on
kubernetes
Project
was
over
about
two
years
ago,
so
it
should
probably
be
removed.
So
so
this
needs
some
cleanup
all
right.
So
so
that's
one
place
that
needs
a
little
bit
of
pruning.
Now
go
to
the
community
drop
down.
That's
right!
Next
to
it
notice
here
that
there's
another
list
of
six
or
eight
things:
advocacy
and
Outreach
documentation,
Google
summer
of
code.
A
Some
of
these
are
inactive.
Others
are
are
still
very
active,
but
what
the
governance
proposal
was
is
hey.
Let's,
let's
switch
from
this
concept
of
two
different
things:
sub-projects
and
special
interest
groups
to
one
thing:
working
groups
and
we'll
put
all
the
working
groups
under
the
sub
projects
menu
and
call
it
working
groups.
B
A
And
remove
them
from
communities
so
that
it's
just
working
groups
and
there
we'll
have
the
platform
Sig.
The
advocacies
will
have
Google
summer
of
code
will
have
any
other
short-term
things
we
create
can
go
there
so
that
Community
becomes
a
shorter
menu
item
and
and
what
would
become
working
groups
is
about
the
same
size
actually,
but
a
little
more
fluid.
B
Right
and
it's
basically,
it's
making
sure
the
community
tab
is
focused
on
the
community
aspect
of
Jenkins
and
then
right
having
the
sub
projects
special
interest
groups,
I
mean
it
from
a
new
person
perspective.
It
doesn't
seem
like
there's
too
too
much
difference
between
the
two
so
make
condensing
that
all
make.
A
Sense
exactly,
and
that
was
Gavin
mogan's
point
in
governance
board
was
release
the
and
Oleg
nanashev
agreed
sub-projects
and
special
interest
groups
are
many
times
indistinguishable
from
each
other.
We
can't
tell
what
why
why
is
something:
a
special
interest
group
and
not
a
sub
project?
Why
is
something
a
sub-project
and
not
a
Sig
yeah?
So
right?
B
A
Okay,
so
then,
now
this
is
one
where
Alex
Alex
is
deeply
involved
here
and
has
been
a
lead
on
multiple
Jenkins
releases,
so
review
revise,
approve
and
merge
the
weekly
change
logs
and
the
LTS
change
logs.
We've
got
the
LTS
2.375.1
with
Alex,
as
the
release,
lead
and
he'll
need
a
change
log
and
an
upgrade
guide.
C
A
B
Honestly,
no,
we
I've
been
working
on
the
LTS
and
change
logs
for
a
little
bit
now,
with
under
your
guidance
of
course,
and
working
with
the
release
leads
on
the
past
few
and
the
rest
of
the
developers.
I
feel
pretty
confident
about
that.
I'm,
comfortable
and
I
know.
I
can
reach
out
to
Alex.
If
I
have
questions
on
this
one
or
if
I
want
to
double
check
anything
from
this
case
or
whoever
the
release
lead
is
in
the
next
one.
A
All
right
good!
So
then,
let's
go
to
the
next
one:
the
wiki
to
GitHub
migration
project
and
and
let's,
let's
be
more
clear,
plug-in
documentation
migration
project
right.
So
this
is
specific
to
plugins,
not
to
other
forms
of
documentation
if
you'll
click
that
hyperlink
track
the
migration
project
and
then
so
what
this
is
is
at
the
top
of
this
we
see
200
892
plug-ins
still
need
to
have
their
documentation
migrated,
but
946
are
done
now.
A
The
nice
thing
here
is:
we've
got
a
tracking
project
that
we're
using
this
is
sort
of
sort
of
a
a
different
experiment,
so
I'm
going
to
link
to
the
tracking
project.
So
if
Kevin
you
can
get
to
it
as
well
from
here.
If
you
scroll
down
past
something
that
says,
okay,
look
for
something
that
says:
PR
merged.
A
A
A
But
what
what
happens
here
is
when
a
new,
when
a
new
pull
request
is
created
to
propose
to
migrate
documentation.
I
will
typically
click
the
plus
sign
above
the
in
progress
column.
So
click
that
and
paste
the
URL
to
that
pull
request
and
then
click
add
you
don't
need
to
do
it
now,
but
what
that
would
then
do
is
now
that
creates
this
entry
that
it's
connected
and
so
now
we'll
get
status.
Reports.
Okay,.
D
A
A
So,
and
in
terms
of
if
you'll
go
back
to
that,
that
report
I
think,
let's
see
which
one
was
it
that
one
yeah,
if
you,
if
you
look
at
this
from
the
high
level,
we're
making
really
pretty
good
progress
because
as
you,
if
you
start
from
the
top
and
scroll
downward,
you
see
that
the
the
the
high
volume
plug-ins
plug-ins
with
more
than
a
hundred
thousand
installations,
are
generally
all
done.
Just
keep
going
down,
keep
going
down
and
whoops,
let's
see
we'll
back
up
okay,
so
here
we
go
no,
even
so
deprecated.
A
A
A
You
won't
be
notified
of
a
need
to
review
these,
although
you
certainly
could,
if
you
wanted
to,
you,
could
review
the
pull,
requests
and
comment
on
them.
So
when
a
PR,
if
you,
if
you
scroll
up
to
the
top,
you
can
sort
based
on
that
status
column,
and
so
then
it
will
group
all
of
the
search
for
PR,
open.
A
So
here
they
are,
you
could
go
review.
These
pull
requests
to
give
your
comments
on
on
these
proposed.
Pull
requests
do
as
far
as
I
can
tell
it
hasn't,
inspired
or
prompted
or
helped
anyone
when
I've
done
that,
so
I've
not
bothered
I've.
If,
if
a
documentation,
pull
request
to
a
plug-in
doesn't
get
merged
pretty
quickly,
it
doesn't
leave
me
very
hopeful
that
it's
going
to
be
merged
anytime
soon.
B
B
A
A
So
then,
on
the
next
topic
advocacy
projects
there
it's
trying
to
watch
for
and
encourage
people
to
do
good
contributions,
documentation
wise
for
Google
summer
of
code.
She
code
Africa,
contributes
on
those
two
are
top
top
of
our
list,
because
we've
done
them
multiple
times,
Google
season
of
docs
we
did
once
and
it
the
management
overhead
for
Google
season
of
docs
was
large
enough.
That
I'm
not
sure
I'd
Lobby.
We
do
it
again
it
just
it
had
it
had.
There
was
more
work
hiding
in
it
than
I
was
ready
to
do.
A
A
B
Know
the
Google
summer
of
code,
2023
proposals
are,
or
those
are
being
looked
for
right
now.
I
think
we
just
actually
had
a
blog
post
yesterday
about
it,
so
yeah
and
I
do
want
to
actually
participate
in
that
and
and
be
a
mentor
as
much
as
I
can
so
I'll
be
sure
to
reach
out
to
John,
Mark
and
Alyssa
about
that
or
John
Mark
I
guess
so.
Yeah
no
and
I've
been
doing
I
I
have
participated
in
helps
with
hacktoberfest
just
the
last
month
and
she
could
Africa
as
well.
B
Yeah
definitely
and
I'm
sure
that
as
I
go
along,
I'll
have
questions
that
you
might
never
thought
of
either
so
we'll
figure
it
out
together,
yes
and
then
yeah
and
like
I
had
mentioned
earlier,
just
to
make
sure
that
it's
on
record
that
if
anyone
needs
help
with
anything,
please
just
reach
out
to
me.
Let
me
know
if
there's
some
place:
I
can
change
or
effect
in
any
way
I'm
more
than
happy
to
help
and
to
collaborate.
So
any
any
ask
no
worries.
B
B
And
then
I
think
this
is
something
the
the
benefits
there.
I
think
are
things
I've
already
been
noticing,
like
we
have
more
clicks
on
the
videos
in
the
documentation,
like
you
stated
earlier,
and
just
I
want
I
want
to
continue
to
encourage
people
and
Empower
compute
Community
as
much
as
possible
to
participate.
However,
they
can
so
yeah
I
mean
my
goals
are
aligned
with
the
benefits
of
it.
So.
B
C
You,
okay,
I,
just
heard
over
the
list.
Again,
if
you
have
a
bullet
point,
called
periodically
check
for
misplaced
stocks.
Issues
on
jira
a
bit
above
is
the
website
project
no
longer
intended
to
be
used
on
Dira,
because
if
that
is
the
case,
we
could
just
archive
it
so
that
new
people,
don't
trade,
is
just
there.
A
Yeah
good
interesting
suggestion,
the
the
experience
I've
had
has
been
that
people
don't
submit
well
and
we
saw
it
in
Kevin's
query.
The
last
submission
to
that
project
was
April
of
2022,
so
I
think
it's
already
well
enough.
Hidden
I'm,
not
sure
that
we
want
to
go
through
the
the
the
risk
of
archiving
it
with
the
risk
that
that
may
hide
things
that
we'd
like
to
keep
publicly
visible.
A
I,
don't
know
of
any
links
that
lead
to
the
to
the
jira
to
the
website
to
submitting
to
the
website
jira
project,
and
if
there
are
any,
we
should
definitely
remove
them.
There
certainly
are
still
links
in
various
locations
that
link
to
existing
website
issues.
You
know
for
documentation
purposes,
that
kind
of
thing.
C
Yeah
there's
a
similar
process
is
what
we
are
doing
when
moving
when
you're
moving
from
Guitar
from
jira
is
used
to
GitHub.
We
basically
just
archive
the
component
that
makes
sure
that
the
submitter
can
no
longer
select
on
the
drop
down,
but
all
issues
and
all
components
are
still
available
for
search
or
in
the
search
query.
A
Yeah
and
my
my
hunch
is
that,
because
this
is
website
as
a
project
at
the
jira
level
and
not
a
not
a
component,
it's
I,
it's
more
difficult,
I
would
assume,
but
I
I
haven't
done
the
research
to
to
find
a
way
to
switch
off
accepting
any
new
issues
in
the
in
the
website
project.
It's
an
interesting
topic.
Kevin.
You
could
put
it
on
the
list
to
see
hey.
Should
we
make
the
jira
website
Project
Read
only
somehow.
B
B
And
then
I
know,
I
think
there
there's
also
been
some
discussion
about
site
generator
and
I've
we've
been
looking
at
stuff
like
antora,
just
due
to
the
versioning
option
that
they
have
for
the
documentation.
So
that's
another
thing
that
I've
been
talking
with
Basel
about
it,
a
little
bit
in
the
last
few
weeks
and
going
forward
it's
something
that
we
want
to
kind
of
investigate
further,
so
that
might
also
fall
under
one
of
these
so
yeah.
It
definitely
falls
under
some
of
this
stuff,
so
cool
all
right.
B
The
Baseline
was
is
2.375,
Alex
is
actually
the
release
lead
so
again,
Alex.
Thank
you
very
much
for
becoming
being
the
release
lead
here
and
as
far
as
documentation
goes,
Mark
and
I
are
going
to
be
working
on
the
changelog
and
upgrade
guide
to
make
sure
that's
taken
care
of,
completed
and
ready
to
review
prior
to
the
end
of
next
week,
most
likely
a
little
bit
earlier
than
that
due
to
Thanksgiving
here
in
the
U.S.
B
B
We
will
resume
the
week
afterwards,
so
just
a
short
break,
but
yeah
the
holiday
in
the
U.S.
Is
it
gonna
hold
things
off
for
us,
and
in
that
vein
we
also
want
to
have
a
blog
post
published
around
Thanksgiving.
That
shows
appreciation
and
thanks
to
all
of
our
sponsors,
the
continued
support,
and
you
know,
resources
that
we've
gotten.
We
want
to
make
sure
that
no
sounds
left
unturned
and
that
everyone
we're
not
leaving
anyone
out
we're
showing
our
appreciation.