►
From YouTube: 2021 09 13 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
Welcome
to
jenkins
documentation,
office
hours,
it's
the
13th
of
september,
reminder
that
we
follow
the
jenkins
code
of
conduct
so
be
nice
to
each
other,
while
we're
in
the
in
the
session
here
are
the
topics
that
I
had
so
the
change
log
review
for
tomorrow's
jenkins
weekly
release,
a
review
of
the
changelog
proposal
that
I've
done
for
the
2.310
release
that
we
skipped
devops
world
is
a
possible
topic
contributor
summit
as
a
possible
topic.
A
A
A
A
A
B
So
this
did
not.
This
was
not
published
because
the
release
build
failed.
A
Right,
correct,
yeah
so
and
the
release
build
failed
because
we
were
blocking
uploads
to
the
to
the
release.
Repository.
A
A
I
tell
you
this:
this
changelog
automation
is
working
brilliantly.
C
A
And
ready
for
review
and
merge
by
someone
else.
B
Great
and
this
jenkins,
2.312
changelog
will
be
published
seven
days
from
now
right.
A
B
Oh,
I
think
because
oh
I
thought,
since
tim
just
merged
the
previous
one
yesterday,
so
there
has
to
be
seven
days
gap.
That's
why
oh.
A
Oh
good,
so
yeah
you're
absolutely
correct
the
the
delay
on
this
merge.
This
thing
only
merged
less
than
24
hours
ago,
but
it
actually
released
five
or
more
days
ago.
We
just
we
didn't
get
it
merged,
and
so
we
had
that
awkward
phase.
Where
there
was
this
changelog
entry
didn't
exist,
even
though
we
were
already
delivering
2.311.
A
A
A
A
A
A
D
A
And,
and
even
that
isn't
particularly
required,
okay,
because
the
ascii
dock
already
exists
now
that
so
what
we're?
What
you
see
here
is
the
ansible
page.
A
And
this
previously,
I
think,
would
have
said
something
about.
Oh
hey,
go
see,
go
read
the
wiki,
but
gavin
mogan
has
made
the
transformation
already,
and
so
now
it
may
be
as
actually
we
may
need
to
improve
our
description.
A
A
Right
right,
exactly
it's,
it's
the
the
videos
assumed
the
existence
of
the
wiki
site.
A
It's
gone
now
right.
There
is
a,
I
think,
it's
already
a
conversion
site
that
the
plug-in
site
is
reading.
So
now
we've
got
a.
We
may
need
to
ask
gavin
hey
what
what
is
the
process,
because
if
I
open
this
github
repository,
I'm
sure
I'll
see
in
the
palm.
A
A
A
D
E
C
Adding
anything
different
so
meg,
if
you
were
making
this
conversion
they
wouldn't
be
like.
Oh,
can
you
detail
this
process
that
you
know
right
you're
not
going
to
have
it's
like
no
context
into
the
plugin,
because
you
know
you've
never
used
it
before
or
anything
like
that,
and
it's
like.
I
can't
do
that
so
it'd
just
be
good.
It's
like
look.
I'm
just
doing
this
we're
copying
over.
If
you
have
any
other
suggestions
now
you
you
can,
that
was
a.
D
C
C
D
C
Help
prompt
some
of
these
plug-in
maintainers
to
even
you
know
you.
If
it's
out
of
in
another
place
out
of
sight
out
of
mind
it's
a
good
idea.
You
have
a
chance
now
to
go
and
I
was
like.
Oh,
this
is
a
good
time
to
review
our
dock,
like,
let's
make
sure
now
that
it's
here,
let's
make
sure
it's
accurate.
So
it's
nice.
A
Right,
yeah
and
that's
that's
at
least
been
the
thing
for
me
with
the
git
plug-in
has
been
oh
because
it's
there,
I
can
put
myself
a
reminder,
be
sure
you
update
the
docs
when
you,
when
you
add
new
capabilities
and
there's
a
regular
reminder
now,
for
me,
that's
awesome
yeah.
So
this
this
okay.
So
let's
I'm
going
to
capture
this
into
the
notes.
A
A
Okay
then
fork
the
repository.
A
A
And
then,
if
I
remember
right,
there's
something
about
tag,
the
pull
request
for
hacktoberfest
kristen.
Can
you
help
me
with
that
one?
How
is
is
there's
there's
some
marker.
We
apply
to
it
or
something
like
that.
D
A
A
A
And
this
shows
me
the
documentation
from
the
plug-in
site,
that's
good
and
then,
if
I
find
over
here
in
the
link
section,
the
github
link
I'll
open
it
in
there
and
I
go
to
pull
requests
and
here
in
pull
requests.
I
was
worried.
Oh
here's.
This
pull
request
from
two
years
ago
now
move
docs
to
github.
Oh,
maybe
somebody's
already
started
this
well,
let's
look
and
see
so
move
docs
to
github.
What
was
the
total
change
made?
This
one
change
in
the
oh
guess,
what
there's
a
step
missing.
A
A
A
A
A
A
A
A
C
Okay,
I
was
like
I
was
almost
gonna
say
I'm
not
entirely
sure,
because
it's
so
much
and
if
they're
just
doing
one.
A
They
may
be
able
to
just
copy
things
from
the
webpage
yeah.
Okay,
let's
go
with
that
and
and
we'll
we
can.
We
can
certainly
show
as
an
advanced
topic
hey.
This
is
how
you
do
it,
but
the
easy
way
is
just
copy
it
from
the
web
page
because.
C
Yeah,
it's
very
much
as
easy.
Yes,
I
just
want
to
encourage
people
to
go
like
to
make
it
less
of
a
load
yeah
I
don't
know-
or
at
least
like
my
opinion-
is
like
the
less.
They
have
to
try
to
figure
out
how
to
install
the
better
like
you're,
just
kind
of
like
encourage
people
to
move
stuff
over
really.
A
E
A
A
A
A
A
A
A
E
E
B
Also,
we
can
check
the
links
that
direct
us
to
the
ansible
website,
whether
they
work.
Oh.
A
A
A
Oh,
oh
here
we
go
okay,
ssh
credentials,
plug-in
that
should
work,
but
then
we're
going
to
get
one.
That's
broken
very
soon.
Here
this
one
sourceforge.
E
A
A
A
A
A
A
A
A
Okay,
so
we've
got
some
more
work
to
do
while
we're
here
readme
palm,
and
this
one
update
no
use
github
for
docs.
A
A
A
A
Submission
right
right,
exactly:
okay,
good
to
move
documentation
from
jenkins
wiki
to
github
all
right
describe
what
you
did
linked
to
relevant
issues,
so
there's
no
relevant
issues,
so
I
can
put
an
x
here
and
the
reason
for
the
x
here
is:
it
will
fill
in
the
check
box
link
to
pull
requests.
Don't
need
to
do
that.
Provide
tests,
don't
have
anything
that
provide
needs
to
do
tests.
A
A
C
A
The
material
that
was
there
and
here's-
oh,
the
change
log,
looks
horrific.
Okay,
I'm
sorry
that
change
like
has
to
be
fixed.
That's
not
exactly
that's
one
of
the
benefits
of
doing
this.
Look
at
it!
Now
we
see
oh
boy
that
looks
awful.
Let's
fix
it,
so
we'll
go
fix
that,
but
also
sorry
go
back
to
what
go
back
to
the
image
in
this
page.
A
G
Oh
dear
odha,
well
then,.
A
C
A
Good,
okay,
so
we're
good
all
right
super.
Then,
let's
see
there
was
something
else
we
said
there
was
something
that
looked
horrible
here.
What
was
it?
It
was
change
logs
right.
Okay.
So
if
we
look
at
the
change
log,
yeah
notice
that
it's
got
three
three
levels
of
indentation-
that's
just
that's
just
immoral!
We
need
to
fix
that.
Okay,
so
change
log,
all
right!
Oh
yeah,
okay,
and
we
can
see
why.
E
A
A
A
A
A
A
Oh
good,
no!
Let's
do
that
so
check
the
formatting
of
the
documentation
on
github
fix
as
needed,
so
that
it
looks
reasonable,
don't
make
the
maintainer.
B
C
Yeah
I
put
a
link
to
the
oktoberfest
getter
and
then
also
one
about
like
the
hacked,
the
official
yeah,
the
request
reviews.
C
It
looks
like
it's
a
tag
thing,
but
I
think
that
this
again
we're
really
early
on
top
of
it
at
least
we'll
alert
the
hacktoberfest
coordinators.
A
A
B
I
think
it
looks
good
just
I
have
one
generic
question,
so
what
we
have
done
is
we
have
so
the
problem
initially
was
the
everything
was
on
the
wiki
site
and
we
didn't
want
it
to
be
there.
You
want
to
to
shift
it
from
there
to
each
plugins,
github
repositories,
readme
file,
and-
and
now,
if
you
talk
about
it,
we
have
a
repository
called
plugins
wiki
docs,
where
all
the
plugins
have
their
documentations
in
the
readme
file.
A
Yes,
you
said
it
brilliantly:
okay,
I
got
it
now.
It
makes
sense
great
yeah,
it's
it's
very
someone
might
say,
oh,
but
why
don't
we
just
maintain
things
in
that
transition
repository,
because
there
are
hundreds
and
hundreds
there
are
over
a
thousand
plug-ins.
In
that
thing
it's
just
unmanageable,
whereas
if
we
do
it
in
the
individual
plug-in,
it's
very
close
to
the
plug-in
near
it's
it's
its
own
changes
good
just
makes
sense
all
right.
Well,
art.
I
didn't
realize
how
much
time
we
taken
or
we've
passed
our
time.
A
I
think
we
should
call
this
done
for
today,
thanks
very
much
for
helping
go
through
the
steps.
I
will.
I
will
capture
a
copy
of
this
and
that
way
we've
got
it
ready.
We
can
always
consider
doing
a
a
re-record
or
having
a
session
where
we
talk
to
each
other
and
invite
others
to
join
us.
I
think
we've
got
a
good
mix.