►
From YouTube: 2020 09 28 Docs Office Hours
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
So
recording
has
started.
This
is
office
hours
for
september,
28th,
jenkins,
documentation.
Let's
take
a
look
at
the
agenda.
First,
jonathan
thanks
so
much
for
your
marvelous
preparation
for
it
we
keep
conversion
progress,
summary
top
item.
This
is
going
to
be
a
great
topic
to
discuss,
and
then
I've
got
a
brief
topic
on
terminology
updates.
With
proposal
for
how
we
approach
it.
So
anything
else
that
should
be
on
the
agenda.
B
Mark
just
wanted
to
like
clarify
oktoberfest
participation.
Can
we
participate
before
our
september
30th
or
just
on
september
30th?
We
need
to
join.
A
A
C
No
okay,
let's
move
on!
Well,
I
guess
we
have
finished
the
work.
Migration
issues
register.
Okay,
so
summary
most
of
the
issues
from
spreadsheets
were
registered
as
they
issue
github.
C
So
now
we
have
a
lot
of
issues
to
work
on
just
about
the
31
issues.
I
can
figure
out
the
destination
page,
so
I
put
a
need
to
to
map
them
so
maybe
someday
you
can
help
with
me
to
figure
out
and
so.
C
Okay,
all
right,
so
some
issues
are
really
old
and
I
can't
figure
out
the
destination.
Are
the
issues
showed
the
broken
link
to
plugins,
for
example?
C
So
so,
for
example,
the
what
line
130
all
swap
dependency
check
again,
if
you
visit
the
page,
the
link
is
to
program
it's
broken
and
I
I
can't
find
them
on
the
plugin
with
research,
page,
okay,.
A
Interesting
yeah
so
well
shall
we
take
a
look
at
that
one.
Just
I'm
curious
because
oh
wasp
is
is
very
much
used,
but
I
don't
know
if
this
this
particular
plug-in
may
be
a
dead
plug-in
that
they've
removed
and
replaced
with
something
else.
Maybe
okay,
so
you
say
that
this
link
is
just
broken.
No
there's
a
wasp.
A
Well-
and
it
may
be
that
the
plugin
site
was
having
some
issues
so
so
this
looks
like
it's
a
redirect
is
the
and
it
looks
like
the
content
is
largely
there
good,
okay,
double
check,
maybe
they've
already
implemented
documentation
as
code.
A
A
C
Okay,
so
let's
back
to
agenda,
please
all
right,
okay,
so
the
next
topic
we
have
and
the
list
below
shows.
I
I
put
the
link
there.
So
we
have
49
issues
eligible
to
go
the
first
issue,
so
I
I
put
the
link
for
all
of
them.
A
C
So
now
we
have
30
percent
of
work
done
and
almost
40
available
issues
to
work
on,
and
then
we
can
start
another
follow
another
strategy
to
work
with
documentation.
A
C
A
A
Okay,
so
then,
then,
this
is
a
place
where
any
anyone
else
so
me
or
vlad
or
mag
could
consider
working
through
these
lists
that
you've
already
assigned
that
you've
already
identified
as
good
first
issue.
Do
another
triage
yup
ready
for
the
good
first
issue
label
I'll
work
through
them.
Others
are
welcome
to
assist
if
they'd
like
that's
really
great.
This
is
brilliant.
A
So
so
this
feels
like
a
great
a
great
thing
for
us
to
highlight
if
we
were
to
do
a
a
jenkins
online,
meetup
fairly
early
in
october,
to
highlight
how
people
can
contribute
to
jenkins
documentation
during
oktoberfest,
we
could
show
hey.
Look
here
are
the
things
that
are
ready
for
you
all
sorts
of
great
things
that
are
here.
We've
guessed.
We've
got
some
few
left
that
we
need
to
triage
still,
but
we
have
a
hundred
and
it's
157
right.
C
Yeah
and
it's
a
all
the
49
issues,
it's
about
hydroxy
operations,
but
it's
a
a
good
start
for
newcomers.
C
C
That
have
become
happy
when
they
help.
So
it's
a
simple
question
issue:
it's
a
civil
problem
to
solve,
but
they
can
taste
the
how
it's
available,
help
others
and
community.
A
A
It
well
and
just
just
to
give
my
my
my
technique
as
I
work
through
the
triage
process,
so
I
opened
this
one
and
said:
okay,
I'm
gonna
gonna
change
the
description.
Oh
no,
this
one,
this
one,
I
checked,
and
it's
already
done
so
I
when
I
click
this
link.
It
opens
up
to
the
same
page
that
this
one
does
so
the
redirect.
I
assume
you
or
somebody
else
has
implemented.
So
I
just
close
the
issue
very
nicely
to
them.
C
Yeah
yesterday,
let's
take
the
number
here
someone
sent
me
a
mail.
C
Yeah,
I
can't
I
I
don't
know
how
to
say
his
name,
but
he
said
he's
speaking
about
the
a
plug-in
and
he
was
working
on,
so
he
already
sent
the
pull
request
to
redirect
them.
A
All
right,
thank
you,
thank
you
and
now
the
spin.
I
could
also
had
also
pointed
to
the
see
there.
There
is
a
github
issue:
isn't
there
that
tracks
tracks
some
of
these
things
as
in
a
different
way?
So
so
that's
we've
got
additional
opportunities
for
people
to
help
there,
where,
even
if
it
didn't
reach
yet
into
our
list
of
pages
to
migrate,
there
are
still
plenty
of
plugins
that
need
documentation
migrated
to
github
from
wherever.
A
C
But
how
exactly
works?
The
the
plugins
administration,
for
example,
the
volunteer,
who
wrote
the
plugin
it's
responsible
to
documentation
or
not
the
community,
need
to
stay
there
documenting
everything.
A
A
A
A
A
I
looked
for
the
word
master
in
the
in
the
jenkins.io
repository
and
realize
there
are
some
references
in
the
style
guide
and
contributing
that
we
need
to
be
sure
that
those
instructions
are
ready
before
we
point
people
to
them.
Likewise,
there
are
sensitive
documents
like
in
the
roadmap,
where
there
are
references
that
we
may
need
to.
We
may
need
to
also
correct
those.
A
A
So
my
thought
was:
each
of
these
bullets
would
be
a
bug,
an
issue
in
github
and
then
I'll
list,
the
pro
the
file
that
they're
to
edit
to
to
to
make
that
change
this
one
had.
I
think
it
was
on
the
order
of
10
references,
and
so
it's
it's
enough
of
a
change
that
it's
not
a
trivial
operation.
It's
not
changing
one
word
and
this
one
I
think
likewise
so
now
to
to
the
rest
of
you
as
a
group.
Does
that
seem
like
a
reasonable
approach
to
attack
this
without
to
attack
this?
C
A
It
as
far
as
I
can
tell
it
is
more
than
that,
because
there
are
times,
for
instance,
one
of
the
things
when
I
did
my
initial
search
oops.
When
I
did
my
initial
search,
I
just
looked
for
the
word
master
and
of
course
the
word
master
occurs
in
a
github
repository
url
that
refers
to
the
master
branch
and
if
they
do
a
find
and
replace
on
that,
they
will
break
the
hyperlink
completely.
C
A
Because
there's
just
too
many
hyperlinks
that
depend
on
that,
that
word
master,
but
I
can
see
them
saying
that
for
new
repositories
for
new
repositories,
instead
of
master
will
remain
yeah
or
ease
some
transition,
great
good
for
them,
but
but
this
is
a
place
where,
if
we're
very
dedicated
right,
if
we
do
wholesale
replacement,
we
will
spend
more
time
if
we
do
mechanical
replacement.
Without
thinking,
we
will
spend
more
time
for
reviewers
to
fix
problems
than
we
gained
by
having
people
help
us.
A
A
C
Yeah,
maybe
it's
a
a
nice
approach
just
to
resist
the
issues
and
wrote,
write
something
warning
about
the
danger
of
changing
urls
and
so
do
a
nice
pr
review
faster,
so
reject.
If
I
did
something
wrong
or
just
ask
for
adjustment
right,
we
need
to
try.
Maybe
a
finger
can
do
everything
in
the
good
hands
with
the
good
hands
and
do
the
good
work.
A
Sorry,
are
you
willing
to
review
a
draft
of
that
issue
proposing
what
the
text
should
be.
B
Yeah-
and
I
guess
you
are
absolutely
right-
mark
that
it
should
not
be
mechanical
or
automated
in
any
way,
because
there
is
we
need
to
say
there
is
distinction
between
updating
documentation
for
terminology
inside
documentation
and
inside
the
code.
So
probably
we
should
make
a
note
somewhere
saying
that
all
the
documentation
is
changed
to
new
terminology.
A
A
And
then
we
can
change
the
documentation.
We
don't
want
to
confuse
users
by
presenting
documentation
of
something
that
hasn't
yet
changed
in
the
actual
ui.
B
Good,
okay,
so
yeah
did
you
go
headline
besides
ui
when
we
are
referring
to,
let's
say
docker
images
sometimes
were
referring
to
them.
They
are
named
still.
Some
images
are
named
within
old
terminology,
so
it
may
be
not
necessarily
related
to
ui,
but
you
are
right.
Your
eye
may
be
predominant
like
when
happens.
A
That's
that's
a
very
good
point:
that's
one
that
inside
a
tutorial,
for
instance,
if
we
name
if
we
name
the
volume
jenkins
master
volume
that
we
can
probably
safely
change,
but
if
they,
if
there's
a
risk
that
they
persisted
that
volume
and
kept
it
for
long
term,
then
I
I
suspect
we
have
to
warn
them.
Then
hey
this
used
to
be
named
this
because
they
may
have
to
do
a
transition
for
themselves.
If
they
have
that
volume
they
created
a
year
ago
and
they're
still
using
it
and
now
we've
changed
the
instructions,
good
insight,
okay,.
A
B
Now
did
that
answer
your
question?
Yes,
absolutely
mark
and
related
to
this
one
about
specifically
registration
for
digital
ocean,
a
digital
ocean.
It's
when
the
digital
ocean.
They
mentioned
this
oktoberfest,
it's
not
clear
enough.
Should
we
do
registration
after
september
31st
starting
from
october
one
or
we
can
reach
this
with
digital
ocean
before.
A
A
A
Okay,
to
get
a
shirt,
you
must
make
four
pull
requests
between
october
1
and
31
in
any
time
zone,
okay
to
any
public
repo,
so
that
we
qualify
and
now,
let's
see
now,
where
was
the
registration.
A
Here
it
is
so
it
was,
I
think
it
is.
We
just
click
the
start,
hacking.
It
will
then
ask
me:
okay,
who
am
I
logging
in,
as
I
am
a
maintainer
in
the
u.s.
A
A
B
A
A
B
A
I
I
don't,
I
I
think
a
pull
request
to
a
public
repository,
at
least
for
me
was
almost
infectious.
It
was
so
so
fun
it
was
oh
wow.
I
just
contributed
something
to
somebody,
because
I
felt
like
doing
it
and
I
I
got
addicted
to
it
and
couldn't
stop,
and
I
think
we
hope
the
same
thing
for
other
people
that
they'll
just
just
become
attached
to
the
idea
that
they
should
help
open
source
projects.
A
A
Yeah,
yes,
as
far
as
I
understand
they
will
mail
the
they
mail,
the
shirt
by
post,
oh
right,
yeah,
and
I
think
that's
why
that's
why
it's
been
so
crucial
to
them,
that
they've
got
it
presented
by
digitalocean
and
intel
and
dev.
So
they've
got
digitalocean
as
a
hosting
sponsor
and
intel
the
processor
giant,
and
I
assume
it's
very
expensive
for
them
to
do
this,
but
we're
very
grateful
that
they
do.
C
A
Right
well,
and
I
think
they
may
have
set
an
upper
bound
on
how
many
shirts
they're
willing
to
deliver,
but
but
it
was
a
very
large
number,
if
I
recall
correctly
thinking
a
hundred
thousand
or
something
so,
at
least,
if
I
recall
past
years,
they
had
set
some
upper
bound
so
that
so
that
everybody
in
the
world
did
not
get
a
t-shirt,
but
that
this
is
it's
a
very
positive
thing.
Absolutely.
C
Well,
I
I
don't
know
if
my
english
is
good
enough
for
a
large
presentation.
A
No,
I
was
thinking
we
will
have
you
actually
show
how
our
process
worked
with
these
things,
because
I
think
this
is
is
interesting
and
fun
for
people
to
know.
I
can
do
the
part
about
hey.
This
is
how
you
do
a
pull
request
for
documentation.
Here's
the
demonstration,
but
I
think
it
would
be
really
great
to
have
slides
that
say,
look
contributing.
I
I'm
jonathan.
I
contributed
to
open
source
by
helping
prepare
for
this
event
and
hear
the
things
that
I
prepared.
A
A
C
Okay,
so
if
I
wrote
a
write,
a
proposal,
I
need
to
send
before
each
october.
A
A
A
B
Yeah,
you
are
talking
about
this
meetup,
which
you
ask.
B
Well,
I
was
thinking
about
showing
the
process
of
actually
building
and
running
jenkins
iosite
starting
doing
make
run,
make
my
build
starting
of
your
local
machine,
verifying
that
everything
works
and
after
they
are
doing
like
checking,
if
your
local
fix
will
work
and
submitting
this
issue
and
pull
request
this
kind
of
the
entire
process,
so
people
who
may
be
new
to
the
quotation
may
figure
out
how
to
do
this.
I.
A
B
That
the
reason
for
that
is
like
some
time
ago,
I
guess
earlier
summer
or
spring
time
frame,
I
created
the
list
of
broken
links
inside
jenkins,
higher
representation
kind
of
simple.
But
like
several
hundreds,
I
guess-
and
so
somebody
started
working
on
that
and
after
that,
another
person
wanted
to
work.
But
eventually
nobody
continued
working
on
this
and
my
guess
they
didn't
know
the
entire
process.
B
How
to
it
looks
simple,
like
broken
link,
how
to
fix,
but
maybe
they
should
be
educated
about
the
entire
process,
how
to
approach
something
that
you
taught
me
and
everybody
else
at
the
beginning,
like
one
of
the
first
sessions
and
it
was
marvelous
job.
A
C
A
A
C
A
It
would
likely
be
the
week
of
october
12
because
or
we
could
do
it-
the
ninth
friday,
the
ninth-
if
we
did
it
morning,
it's
it's
not
typical
that
we
get
great
attendance
on
a
friday
afternoon
at
the
jenkins
online
meetup.
That
would
surprise
me.
Most
people
want
to
be
doing
something
different
on
a
friday
afternoon.
A
Those
those
would
be
very
good
dates
for,
for
me,
would-
and
I
thinking
about
it
I
suspect
the
advocacy
team
will
say
hey
if
you
could
do
it
in
the
in
the
european
afternoon,
north
and
south
america
earlier
morning.
That
would
be
better.
Would
that
work
for
you,
jonathan
and
vlad?
Could
it
work
for
you
on
the
13th,
14th
or
15th
to
do
a
an
earlier
in
the
day,
nursing.
A
13.
october
13,
14
or
15
very
earlier
in
the
end
of
european
day,
would
be
okay.
A
C
Well,
maybe
this
topic
is
it's
a
good
one
to
vlad
too,
because
after
they
assembly
the
local
jinx
io
site
you
you,
you
show
how
to
do
in
the
next
day
or
the
next
session.
C
C
I
I
suggested
separate
because
just
baby,
the
first
one
a
big
long
enough,
maybe
near
to
one
hour
to
handle
the
house
environment-
oh
good
point,
yeah.
Sometimes
things
go
wrong,
so
you
need
to
fix
some
on
live
yeah.
A
A
Okay,
very
good,
so
first
session,
something
like
this
intro
preparing
the
issues
for
that
for
hacktoberfest,
jonathan,
that
you
present
and
then
vlad
building
and
running
the
jenkins
I
o
site
locally
and
then
a
second
a
later
session.
Another
intro
and
welcome
terminology
updates
and
transferring
documentation
from
wiki.
C
A
A
A
C
C
A
Now
I
need
to
find
a
chat
this.
Oh
yes
right
and
this
one
this
one
this
one,
this
page
will
take
a
while
to
load,
but
it's
a
fascinating,
fascinating
way
to
highlight
the
progress.
So
it's
going
to
load
and
show
us
progress
towards
the
migration
of
over
1
000
jenkins
plug-ins
from
wiki
documentation
to
hosting
the
documentation
in
github.
A
This
is
absolutely
100
related
to
plug-in
migration.
This
was
the
original,
the
original
page
and
process
that
started
us
on
this
gavin
mogan
created
a
this
page
and
has
been
maintaining
and
improving
it
and
ins
behind
this
page
is
the
export
tool
that
will
let
you
input
a
confluence,
wiki
url
and
get
back
from
it,
the
converted
page
as
either
markdown
or
ascii
daw
it's
it's
a
marvelous
tool.
C
Okay,
so
someone
often
it's
okay
and
maybe
means
that
it's
done
all
right,
so
we
need
we
need
to
work
on
it.
A
Nothing
to
be
done
if
it
says
here
that
it's
okay,
then
that
means
it's,
the
documentation
has
been
converted.
The
pull
request
has
been
or
the
the
pull
request
was
created.
The
documentation
has
been
converted,
the
new
release
of
the
plug-in
has
been
delivered
and
is
now
visible
on
the
plug-in
site.
A
Available
to
do
to
do
correct
so
so,
let's,
let's
go
down
the
list
here
so
pr
this
one
says
that
the
plugin
has
a
pull
request
pending,
which
would
correct
it,
but
has
not
yet
been
released
with
that
with
that
change.
So
if
we
look
here,
you
can
see
the
the
pull
request
has
actually
been
merged,
but
there
has
not
been
a
release,
since
this
pull
request
was
merged
and
therefore
it's
it's
not
yet
complete.
A
This
work,
it's
the
plug-in
maintainers
are
the
ones
who
decide
if
they'll
merge,
a
pull
request
and
gavin
is
just
extracting
this
information
from
from
the
from
the
github
repositories.
A
A
Done,
oh,
so
what
needs
to
be
done
here
is
if
we
look
at
this
palm.xml
for
this
plugin,
we
look
inside
of
it
and
we'll
see
a
url,
and
that
url
is
pointing
to
the
wiki
documentation
that
documentation
is,
is
read
only
it
cannot
be
changed,
and
so
that's
not
a
place
for
us
to
keep
documentation
long
term.
So
we
need
to
transform
this
to
instead
use
local
documentation.
That's
inside
the
plugin
repository
like
well,
this
this
one
doesn't
have
a
readme,
so
we
would
need
to
create
a
readme
that
contains
this.
A
C
A
Actually,
the
there's
no
there's
no
need
to
do.
The
problem
is
not
the
the
redirect
because
the
redirect's
already
in
place
right,
because
if
I
take
this,
I
take
the
slash
away.
It
will
take
me
to
the
plugins
page,
so
the
redirect
is
already
there.
It's
that
the
maintainer
as
of
maintainers
of
this
plugin,
cannot
improve
that
documentation
because
they
can't
modify.
B
C
Okay
and
there
there
is
there
some
for
some
feature
that
captured
the
content
from
readme
to
jank's
page.
A
A
Oh,
yes,
that's!
That's!
That's
a
standard
part
of
the
of
the
that's
a
standard
part
of
this
plugins
page
it.
It
uses
github's
generation
of
the
readme
to
create
this
page.
C
A
B
A
A
That's
what
this
installs
column
is
intended
to
help
us
with
oops,
and
I
just
sort
it
to
zero.
So
what
it
does
is
plug-ins
with
more
installs
are
higher
on
the
list
and
we
rely
on
people
to
scroll
down
and
it's
it's
quite
exciting,
actually
to
see
how
well
we've
done
at
progressing
through
these
right.
The
first
time
we
reach
a
line
that
that
has
no
progress
on.
It
is
something
with
21
000
installations,
and
that
is
less
than
10
of
the
jenkins
installed
base
is
using
this
plug-in.
C
A
Thank
you
well
and
that's
a
that's
a
fun
one
to
review.
That
is
a
really
good
one
to
review.
To
show
people
hey.
There
is
a
lot
yet
to
be
done
and
it's
to
be
done
in
places
that
will
help
many
many
people,
even
even
a
small
use.
Even
one
of
these
lower
usage
plugins
is
still
installed
at
18
000
locations.