►
From YouTube: 2022 09 22 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
Okay,
welcome
to
the
Jenkins
docs
office
hours.
Eu
Edition
today
is
September
22nd.
We
have
quite
a
few
items
on
our
agenda
today.
We
have
some
action
items
that
Mark
and
I
will
give
some
updates,
for
we
have
just
a
quick
mention
of
devops
world
2022,
which
is
next
week.
We
have
the
upcoming
October
LTS
release.
A
A
Is
there
any
other
items
that
we
should
add
to
the
list
before
we
get
started?
Actually.
A
Then,
as
far
as
the
action
items
go
Mark
any
updates
on
the
ones
under
your
name.
B
Yeah,
so
upcoming
blog
post
I
propose
to
drop
that
action
item
completely
and
just
admit
that
I've
failed.
My
blog
posts
are
not
going
to
happen
for
those
topics.
B
A
Makes
sense
and
well
deserved
time
off
as
well
so
yeah.
So
on
that
note,
I
we
had
a
blog
post
that
was
published
on
Monday,
that
I
wrote
regarding
our
digital
ocean
sponsorship.
A
Digitalocean
is
the
organizer
and
Main
sponsor
of
hacktoberfest,
and
they
actually
just
recently
granted
I'll,
say
in
just
over
eighteen
thousand
dollar
sponsorship
with
which,
in
addition
to
their
earlier
sponsorship,
this
year
brings
us
to
just
over
20
000,
big
big,
thank
you
to
digitalocean
for
all
of
their
sponsorship
and
assistance
and
dedication
for
making
to
help
make
Jenkins
as
great
as
possible.
A
A
It's
called
prep
Timber,
which
is
exciting
and
yeah
a
couple
weeks
left
before
that
actually
finishes
out,
and
we
start
and
then
one
of
the
biggest
things
we
actually
have
published
the
adopt
and
improve
plugin
tutorial,
the
there's
a
blog
post
showing
facing
that,
and
this
is
going
to
be
the
content.
That's
used
during
the
devops
world
Workshop,
so
firsthand
experience
big,
thank
you
to
Mark
and
diraj,
and
everyone
who
contributed
to
this.
A
This
has
been
a
long
time
coming
in
a
process
that
was
started
since
DeVos
World
last
year,
so
having
it
finally
come
to
fruition
is
really
really
nice
to
see,
and
just
it
says
it
just
goes
a
long
way
of
and
reinforcing
the
community
aspect
and
having
people
join
in
to
the
the
contributions
as
they.
A
Mark
did
you
want
to
have
it
did?
Was
there
any
other
notes?
You
want
to
share
about
the
tutorial
or.
B
A
Awesome
and
yeah
as
a
newer
Jenkins
user
for
me,
adopting
a
plug-in,
seemed
very
daunting
that
tutorial
made
everything
easy
I
just
had
to
make
sure
that
I
was
following
the
steps
and
taking
my
time
with
it.
So
a
little
patience
goes
a
long
way
here.
C
Yeah
same
for
me,
I
was
really
scared.
I
don't
want
to
adopt
the
plugin,
even
if
that
would
be
fine
and
now,
after
trying,
the
steps
described
in
this
tutorial
for
a
few
plugins
I
could
become
maybe
a
maintainer
for
one
plugin.
That's
not
that
big
of
a
deal.
A
Yeah,
it
definitely
takes
some
of
the
scariness
away
for
it
so
yeah
very,
very
much
so
thank.
C
A
Great
next
up
on
our
list,
I
just
again
mentioned
that
devops
world
2022
is
happening
next
week,
which
is
over
27th
to
the
29th
I
know
a
surprise
right
now
out.
A
That
does
also
mean
that,
with
nearly
everyone
on
the
community
team
being
at
devops
world
next
week,
most
of
the
events
have
been
canceled.
If
not
all
of
them
have
been
canceled
but
does
include
doc's
office
hours.
We
have
already
shared
that
information
with
the
Asia
docs
offer
hours
participants
and
wanted
to
make
sure
that
that
was
brought
up
here
as
well.
So
next
Thursday
we
will
not
have
doc's
office
hours.
A
It
will,
however,
start
back
up
the
week
after
and
we'll
be
really
just
getting
into
Oktoberfest
at
the
at
that
point
in
time.
So
it's
going
to
be
really
exciting
and
all
new
so
definitely
keep
posted
on
that
next
next
month,
coming
up
in
a
couple
weeks,
we
also
have
our
2.361.2
LTS
release,
so
that'll
be
happening.
October
5th
I've
created
a
changelog
and
upgrade
guide
entry
for
this
it's
available
and
open
for
feedback
and
suggestions.
A
If
you
have
a
chance,
take
a
look
see
if
there's
anything
that
might
need
updating
or
any
kind
of
changing,
please
by
all
means
I'm
more
than
happy
to
where
I
can
figure
that
all
out
on
the
release
line.
Note
I'm
also
starting
to
do
the
weekly
release
line
reviews
this
past
this
week
we
had
two
that
2.370,
which
was
a
security
release,
so
we're
already
keeping
eyes
on
next
week
for
2.371,
and
the
pull
request
for
the
changelog
already
has
an
update
to
it.
A
So
we'll
I'll
be
keeping
an
eye
on
that,
and
while
everyone
is
at
devops,
World
I'll
be
reviewing
and
editing
that
as
we
go
I'll
be
out
towards
the
end
of
the
week
next
week
as
well.
So
I'll
make
sure
this
is
taken
care
of
before
I
head
out,
so
that
no
worries
no
anything
left
hanging
after
the
fact
and
finally,
the
biggest
piece
of
their
agenda
today,
hacktoberfest
is
coming
up.
A
In
a
couple
weeks,
Mark
and
I
have
been
working
alongside
the
community
and
everyone
in
doc's
office
hours
to
go
through
and
confirm
the
issues
that
we
want
to
have
and
make
sure
that
the
topics
available
are
spanning
both
Jenkins
and
non-jenkins
experience
and
documentation.
Otherwise,
Etc
the
it's
really
a
cornucopia
of
ideas,
and
we
we
just
really
are
excited
to
have
people
join
up
and
participate
again.
The
two
set
of
topics
are
good
first
issues
where
no
Jenkins
experience
is
required.
A
This
will
include
things
like
updating
some
of
the
documentation
based
on
current
versions,
making
sure
that
the
sections
are
in
the
correct
order,
more
low
level
or
low
impact
documentation,
work,
and
then
we
also
have
the
Oktoberfest
section,
which
is
going
to
include
topics
that
have
a
little
bit
more
Jenkins
experience
involvement,
so
not
necessarily
going
to
be
for
the
everyone.
But
if
someone
does
have
Jenkins
experience,
we
want
to
make
sure
that
they
can
leverage
that
to
their
advantage,
and
you
know
make
a
meaningful
contribution.
A
If
that's
what
they're
looking
to
do
so
we'll
be
continuing
to
refine
this
a
little
bit
more
as
we
go
along,
but
for
the
most
part
we
do
have
the
topics
categorized
and
labeled.
So
pretty
much.
What's
there
is
going
to
continue
to
be
there
as
we
move
towards
Oktoberfest,
there's
also
going
to
be
an
option
for
plug-in
document
documentation
migration.
A
A
So
using
these
as
the
first
Choice
plugins,
these
are
going
to
be
reviewed
and
maintained
by
people
that
are
active
right
now,
so
the
pull
requests
are
going
to
get
actioned
upon
other
plugins
that
have
maintainers
that,
while
they
might
be
interested
in
Oktoberfest,
may
not
want
their
plug-in
being
part
of
this,
so,
whereas
others
are
going
to
have
the
hectarefest
label
on
their
plug-in.
This
is
the
place
where
you
can
submit
to
those
those
maintainers.
A
However,
if
they
are
not
active,
if,
for
whatever
reason
they
just
don't
get
a
chance
to
review
the
pull
request
within
the
month
of
October,
it's
going
to
just
sit
there,
so
we
want
to
try
and
avoid
that
limbo
as
much
as
possible
for
all
the
pull
requests.
So
we
have
a
migration
report
that
lists
all
the
plugins
that
need
to
be
migrated.
We
have
the
documentation
page
that
describes
the
task
and
Mark.
A
Will
we
have
a
list
or
what's
going
to
be
the
easiest
way
for
people
to
make
sure
that
the
plugin
is
a
good
choice,
maybe
owned
by
yourself,
Bruno
or
John
Mark.
B
It's
a
it's
a
good
question,
so
I
think
the
if
you
look
at
that
worksheet
sorted
by
various
attributes
down
at
the
bottom
of
the
list.
Let's
open
that
and
let's
talk
about
to
see
what,
because
maybe
it's
as
simple
as
we
put
this
one
is:
is
this
the
topic
you
were
thinking,
Kevin.
A
Yeah
yeah.
B
A
Yeah,
so
I
was
thinking
more,
so
we
have
the
first
choice
of
you,
jean-mark
and
Bruno
having
the
plugins.
The
second
choice
is
asking
maintainers
to
review.
I
was
thinking.
Is
there
a
place
that
has
these
ones
specifically
listed
so
that
we
know
for
sure
which
ones
to
contribute
to
versus?
A
C
B
C
C
Is
a
yeah,
the
list
of
the
plugins
will
be
on
the
deck
ready
to
merge,
pull
request
or
make
some
reviews,
and
so
on.
A
B
Yeah,
so
the
the
thought
was
hey:
let's,
here's,
here's
a
list
of
plugins
that
we
know
the
maintainers
are
willing
to
review
pull
requests
now.
These
are
these
are
willing
to
review,
pull
requests
of
a
more
General
nature
right.
These
pull
requests
are
not
just
docs
transformation,
they're
they're,
anything,
for
example.
Anything
in
that
modernize,
a
plug-in
tutorial,
would
be
a
good
candidate
for
these.
A
Awesome
yeah
I
mean
they
can
see
like
the
get
lab,
authentication
and
a
couple
of
the
other.
The
other
ones
I
didn't
see
as
far
as
documentation
goes
so
yeah
I
see
we're
having
this
just
be
available,
as
for
the
community
would
be
nice
to
have
it's
just
informative
purposes.
At
the
end,.
B
Go
back
to
the
go
back
to
the
sheet
that
was
there
before
the
yeah
that
one
Yep
this
one
is
specific
to
docs,
migration,
okay
and
and
the
reason,
let's
see,
let
me
make
it.
Let
me
make
it
editable
to
you,
but
the
reason
that
that
specific
to
docs
migration
might
matter
is
what
I
was
looking.
B
What
I
was
seeking
was
which
plugins
seem
like
the
maintainers
are
more
likely
to
be
willing
to
evaluate
a
pull
request
and
my
guess
on
which
ones
there
would
be
more
likely
to
evaluate
is
which
ones
have
the
newer
release
date
right.
So
this
is
sorted
by
date
of
release
with
count
of
installs
on
the
right,
but
not
it's
ignoring
count
of
installs
and
and
for
me
that
was
okay.
The
for
instance,
the
deployment
notification
plugin
released
less
than
a
month
ago.
B
A
B
Right,
we
could
certainly
ask
a
question
on
the
plug-in
on
the
you
know,
as
in
a
plug-in
pull
request
or
something
like
that,
but
if
they,
if
they
ignore
us,
we
haven't
gained
much
right.
So.
A
Okay,
that
makes
a
lot
of
sense,
and
this
this
cleans
up
very
well
shows
everything
that
I
was
curious
about
and
I
think
it
would
be
a
great
resource
for
Community.
Thank.
B
C
And
Mark,
if
ever
we
don't
get
them
all
modernized
during
the
workshop
shouldn't,
we,
after
the
workshop,
create
a
series
of
issues
for
each
of
these
plugins
saying
you
know:
labeling
them
with
Oktoberfest
and
modernizing
you
know
the
issue
being
modernizing
the
plugin,
because
we
are
there,
we
can
help,
we
can
merge,
pull
requests,
but
people
have
to
know
what
to
do
so.
Maybe
we
should
create
after
the
workshop,
if
they
aren't
all
modernized.
C
B
Of
that
good
suggestion,
I
like
that,
yes,
because
then
then
we
could
open
that
issue
and
label
it
good
first
issue.
We
could
even
at
that
point,
if
we
have
a
sample
of
that
thing,
we
could
point
to
it
and
say:
look
here.
You
can
look
at
this
for
an
example:
good
yeah
I,
like
that
good
suggestion.
Thank
you.
Yeah
I.
A
Like
that
a
lot
too
Bruno,
thank
you
for
bringing
that
up
and
having
that
that's
yeah,
because
and
as
Mark
said,
we
can
set
it
as
good
first
issue.
We
can
set
up
the
labels
on
it
so
that
it
comes
up
as
we
want
them
to,
and
that
would
also
have
a
little
Focus
for
the
user,
the
person
contributing
where
they
want
to
go
and
what
they
want
to
do
so.
Yeah,
no
I,
think
that's
a
I.
Think
that's
a
wonderful
idea!.
B
I
was
just
going
to
tell
you
several
of
these
on
the
list
that
that
have
that
so
row
number
seven,
a
conditional
build
step
needs
stocks,
converted,
oh
no,
no,
no,
no,
sorry,
it
doesn't
artifact
employer,
which
is
a
little
further
down.
Oh
okay.
So
what
this
hints
is
probably
most
of
these
have
already
got
their
documentation.
Updated,
artifact,
deployer
is
definitely
one
that
needs
it.
I
know
it
does
others
I'm,
not
as
sure
of
and
in
the
top
six
or
seven
none
of
them
needed.
A
B
Lot,
oh,
no!
We
we
certainly
can
any
one
of
these.
The
challenge
with
the
challenge
with
this
list
is,
we
don't
have
control
of
these
repositories,
so
we
can't
merge
the
proposed
change,
whereas
the
other
list-
Bruno,
John,
Mark
and
I-
are
reviewers
on
it
and
we
can
merge
the
changes
immediately
right.
Okay,.
A
At
least
we'll
know,
so
we
can
share
that
with
people
and
I
think
we'll
be
okay
at
the
end
of
the
day,
I
don't
think
that's
going
to
deter
anyone
or
anything
from
happening
during
Oktoberfest,
but
yeah
yeah.
These
are
all
just
I'm
just
curious.
Thank
you
for
sharing
all
that
I
appreciate
it
and
I
think
that
helps
clarify
a
lot
for
all
of
us
that,
like
what
we're
gonna
be
able
to
do
and
achieve
it.
C
Mark,
you
showed
us
earlier
today
in
the
outreaches
advocacy
Sig
meeting
a
link
that
would
list
all
the
kind
of
contributions
people
can
make
to
during
hacktoberfest
for
Jenkins,
and
some
of
them
were
translation.
For
example,
could
you
please
share
once
more
that
link,
because
I
thought
that
it
was
well
written
all
the
list
of
things
that
people
could
do?
Would
translation
be
valid
for
Oktoberfest
and
documentation?
I
mean
it
is
a
subject
we
should
address
in
here
in
documentation,
sync
or
not
at
all.
B
C
B
Buddies
of
water-
oh
no,
that's!
This
is
great!
So
now,
if
you
look
under
I,
think
it's
under
community
hacktoberfest,
no
okay,
try
events
yeah
there!
You
go
great!
So
yes,
so
here
we
go
so
as
you
as
you
scroll
down.
What
you'll
see
is
here,
is
a
list
of
issue,
queries
and
then
featured
projects
and
between
those
two
lists:
the
list
of
issue
queries
and
the
list
of
feature
projects.
So
if
you
click
good
first
issues
on
GitHub,
we
should
see
the
it's
the
very
bottom
most
one.
B
Now
go
back
to
that
page
because
then,
if
we
look
at
the
Jenkins
website,
let's
see
there's
not
one
there.
Okay,
maybe
Kevin.
This
is
when
we
ought
to
update
okay.
So
here
what
you
see
is
it
says
Hey
here
it
offers
some
suggestions
of
ways
you
can
contribute,
but
it
does
oh,
no
there.
It
is
the
good
first
issues
link.
B
Now
we
may
want
to
mutate
this
to
be
good.
First
issue:
I,
don't
know
yeah.
That's
that's
actually
a
good
choice,
because
any
one
of
these
that
someone
decides
they're
going
to
to
work.
We
are
willing
to
label
it
hacktoberfest
right.
If,
if
they
do
it
during
October,
we
can
certainly
label
it
act
overfest.
If,
if
that's
a
concern
for
them,
we
say
hey.
Why
do
why?
Isn't
it
labeled
Oktoberfest,
good,
okay,.
B
So
back
to
that
page,
so,
okay,
so
Jenkins
website
is
one
documentation
location
as
you
scroll
downwards.
Then
there
are
others
and
I
think
we've
got
one
further
down
that
talks
about
yeah.
Here's
a
good
one,
non-inclusive
terminology
cleanup
all
right.
This
one
is
a
needs,
a
sweep
across
all
sorts
of
places.
Looking
for
non-inclusive
terminology,
so
I'm
not
sure
we
want
this
one
in
our
in
this
particular
page.
It's
just
too
complicated
for
a
new
contributor
to
find
those
locations
successfully.
B
A
B
B
B
A
Then
yeah
there's
there's
this
section
specifically
for
French
translation,
which
is
what
Bruno
had
men
or
not
specifically
the
French,
but
this
there
is
one
for
this
translation
specifically
and
then
some
internationalization
documentation.
A
I
also
know
that
we
have
crowded
Enterprise
too
so
and
I
know
like
I
If
I
recall
there
was
questions
before
about
how
to
make
sure
people
get
credit
or
recognized
for
the
translations.
They're
doing
and.
B
That's
a
part
that
I'm
not
I,
haven't
read
the
the
hacktoberfest
instructions.
Well
enough
to
understand
how
things
that
are
not
submitted
as
pull
requests
to
a
GitHub
repository
can
be
counted
Bruno.
Maybe
you
can
give
us
an
overview
of
how
they?
How
do
they
do
that,
accounting?
How
do
I?
How
do
I
tell
them?
I
submitted
a
translation
through
crowd
in
that's.
C
A
program
for
the
time
being,
I
haven't
read
the
detailed
details
of
that
I,
don't
know
because
they
also
talked
about
writing
a
blog
post.
B
B
It
okay,
so
so
you've
got
the
same.
Open
question
I
do
is
is
for
me
the
French
translation
topic
is
is
interesting.
If
a
team
were
to
decide
as
a
group
hey,
we
want
to
work
on
French
or
we
want
to
work
on
German
or
Italian
or
Spanish
or
Brazilian
Portuguese.
Any
one
of
those
would
be
would
be
great,
but
it
sort
of
needs
it.
It
needs
more
than
one
person.
This
really
isn't
well
suited
to
a
single
individual
approaching
it,
because
they're
they're
likely
some
problems
hiding
here.
C
Yeah-
and
there
may
be
some
prerequisite
too,
because
you
were
talking
about
the
crowding
Kevin
and
somebody
has
to
configure
that
in
the
plugin
before
starting
the
translation.
So
exactly-
and
my
second
question
was:
can
we
dread
that
subject
within
that
documentation
of
these
hours
because
link
to
documentation?
But
it's
not
really
documentation.
B
C
Of
course,
because
we
have
to
find
the
maintainers
to
accept
our
first
pull
request
for
going
to
crowding
and
we
have
first
of
all
to
convince
them.
This
is
used
for
flight
plugin,
and
so
no
I
don't
have
any
expectations.
But.
A
Yep
and
and
Bruno
two
someone
actually
else
has
brought
up
the
translation
stuff
during
our
hacktoberfest
prep
meeting.
So
that
is
something
that
other
people
have
been
considering.
It
doesn't
hasn't,
come
up
as
part
of
the
docs
topic,
specifically
it's
kind
of
considered
its
own
thing
and
they
had
similar
questions.
So
yeah
I
think
it's
something
that
is
a
little
maybe
outside
of
the
scope
to
some
degree.
A
A
A
So,
in
that
case,
I
think
we've
gone
over
all
of
our
Oktoberfest
information.
Was
there
anything
else
that
you
wanted
to
add
on
that
Mark
or
anything
that
you
wanted
to
share.
B
A
B
A
Fair
enough
I
appreciate
that,
if
that's
the
case,
is
there
anything
else
that
we
would
like
to
be
brought
up
today
and
I'm
here,
if
not
great,
we'll
stop
the
recording
in
a
minute
the
recording
will
be
available
in
24
or
48
hours
and
as
always,
thank
you
to
everyone
for
all
the
hard
work
and
joining
there's
been
there's
numerous
contributions
coming
through
every
day
and
I'm
very
happy
that
I
get
to
be
a
part
of
this
and
help
with
the
community.
So
thank
you.
Everyone
always
thank
you.