►
From YouTube: 2023 03 16 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
the
Jenkins
documentation
officer
office
hours
today
is
March
16th,
and
this
is
the
EU
US
edition.
Today
we
have
myself
and
Mark
Waite
and
if
anyone
else
joins
we'll
be
sure
to
add
them
and
welcome
them
as
we
go
on
the
agenda
today,
we
have
some
action
items
of
blog
posts
that
have
been
recently
published,
just
quick
updates
on
the
LTS
release
last
week
and
our
weekly
releases
documentation
transition
from
java
11
to
Java
17.
A
This
is
something
we've
been
discussing
for
a
few
weeks
and
we'll
revisit
adding
books
to
jenkins.io,
as
this
has
become
something
that's
popping
up
more
and
more
now,
and
we
want
to
figure
out
alignment
and
standards
for
that
improving
end-of-life
notifications
and
how
we
can
better
provide
users
with
this
information.
How
can
we
increase
the
visibility
of
this?
A
How
can
we
make
sure
that
everything
is
seamless
as
possible,
because
it's
hard
sometimes
and
some
things
yeah,
take
people
by
surprise,
there's
the
prep
for
cento7
end
of
life,
which
ties
into
the
end
of
life
notifications?
A
This
is
something
that
we've
been
discussing
for
a
bit
now
and
so
potentially
is
going
to
be
removed
from
this
sentence,
and
we
have
moved
doc's
office
hours
an
hour
earlier
in
the
day
to
account
for
your
daylight
savings
time
in
the
US
and,
more
importantly,
making
sure
that
this
is
available
and
accessible
for
our
compatriots
on
the
EU.
This
is
it's
just
way
later
in
the
day
than
it
needs
to
be,
and
we
want
to
keep
that
in
mind
and
be
respectful
at
everyone's
time.
A
Good,
wonderful
and-
and
we
have
okay,
so
we'll
start
with
the
action
items,
so
two
recent
blog
posts
by
Bruno
regarding
the
mini
gen,
which
is
an
awesome
little
controller
machine,
if
you
have
not
seen
it
yet
or
if
you
weren't
at
fossism,
definitely
take
a
time
to
check
these
out.
Bruno
gives
a
background
about
what
minigen
actually
is
and
what
it's
capable
of
and
has
written
another
blog
post
about
how
it
ties
into
risk
me
and
other
architecture
and
usage.
He
gives
some
background
on
how
this
came
to
be.
A
It's
just
a
really
nice
insight
into
what
is
possible
with
Jenkins
and
just
the
really
out
there
uses
that
can
come
from
it
and
kudos
to
Bruno.
For
you
know
putting
all
this
together.
Making
this.
This
is
a
lot
of
just
kind
of
I
would
say,
passion
work
at
this
point,
but
yeah
hi
Bruno.
Welcome.
Thank
you.
Thank.
A
Course,
but
sorry
for
being
late,
no
worries
at
all,
no
but
yeah
and
just
I.
These
are
really
great
blog
posts
and
I
think
they
do
a
really
good
job
of
just
showing
showcasing
how
unique
and
different
each
Jenkins
usage
can
be
and
just
the
different
ways
that
we
can
achieve
the
same
goals
so.
C
A
Worries
at
Alberto
I
always
happy
to
help.
The
next
post
was
just
an
update
from
Mark
about
our
atlassian
atlassian
partnership
and
sponsorship.
So
we
are
going
to
continue
to
have
jira
available
for
Jenkins
as
a
atlassian
has
is
continuing
to
provide
that
for
us,
and
so
we
will
continue
to
have
Jenkins
jira
tracking.
There
was
an
update
this
past
Saturday.
That's
now
done,
of
course,
and
everything
should
be
working
as
it
was
before.
A
A
quick
update,
so
the
Jenkins
Awards
voting
period
is
officially
open
as
of
last
Wednesday.
The
recent
blog
post
here
just
shows
what
the
awards
the
Jenkins
awards
are
and
the
nominees
for
them.
You
can
use
this
Google
The
Google
form
attached
or
LinkedIn
the
sheet
here
to
vote.
A
You
do
need
a
GitHub
account,
but
this
is
where
you
can
go
and
make
your
voice
heard
and
I've
also
linked
it
here
in
the
docs
notes,
just
so
that
if
anyone
is
looking
for
it,
they
can
get
to
it
very
easily
and
again,
these
voting
will
be
open
until
March
28th
and
the
winners
will
be
announced
at
cdcon
this
year.
A
So
if
you
haven't
yet,
please
by
all
means,
take
a
minute
check
out
the
voting
and
there
are
additional
issues
that
show
the
awards
and
a
little
bit
more
information
about
them.
So
if
you
are
curious,
you
can
get
some
more
info
about
that
as
well.
A
And
finally,
we
did
publish
our
February
newsletter
last
week,
so
this
has
now.
This
is
now
live
on
the
blog,
highlighting
a
bunch
of
awesome
things
that
we
got
to
do
in
January
February,
including
fazm
2023,
which
we
have
a
separate
blog
post
from
our
attendees
and
participants
that
share
some
insights
and
just
some
great
reflection
on
fosdum,
which
was
really
exciting
to
be
back
in
person
this
year.
So
thank
you
to
everyone
who
attended
and
helped
out
with
the
Jenkins
booth.
A
Next
up,
just
a
quick
update
on
the
releases
we've
had
recently
so
last
week
we
had
LTS
2.38
7.1
and
we
also
had
2.375.4
and
2.394
come
out,
2.394
being
the
weekly,
but
the
security
team
actually
assisted
in
putting
a
lot
of
these
together
and
putting
them
putting
together
the
change,
log
and
release
notes
for
these
releases,
so
huge
thanks
to
them
for
all
their
assistance.
With
that
and
yeah
this
week,
we've
also
released
2.395
successfully
and
something
that
we
noted.
A
We
have
not
seen
any
regressions
for
the
new
releases
as
of
yet
so
we're
doing
really
well.
This
is
it's
great
to
see
next
up
on
the
list.
Here
we
have
the
documentation
transition
from
java
11
to
Java
17.
At
the
point
of
wm-12's
release,
now
I
want
to
be
clear:
Debian
12's
release
is
not
going
to
include
Java
11
but
Java
17.
A
Instead,
however,
we're
going
to
look
to
transition
the
documentation,
regardless
of
the
Debian
release,
to
make
sure
that
we're
giving
everyone
the
best
Baseline
possible
to
work
from
providing
the
correct
resources
and
instructions
based
on
what
seems
to
work
best.
Job
11
will
still
be
supported.
That's
not
getting
dropped
until
2024
at
the
very
earliest,
and
the
Strava
17
is
fully
supported
as
of
last
August
or
September
September,
so
there's
no
reason
not
to,
and
it
provides
extra
further
functionalities
and
testing
that
just
doesn't
exist
in
Java
11..
A
A
What
we're
using
for
that
I've
emailed
Tim
Jacob
so
he's
aware
of
the
the
transition
and
on
board
with
it,
and
one
of
the
things
that
I
just
thought
of
was
that
we
need
to
also
make
sure
that
any
issues
that
are
present
in
Java
17
are
taken
care
of
before
we
transition
the
docs,
so
that
if
we
do
provide
that
instruction
no
surprises.
A
So.
But
this
will
happen
sometime
in
April
or
May
so
coming
up
soon.
But
we
still
have
time
to
figure
out
what
that's
going
to
look
like
and
again
adding
books
to
jenkins.io
is
something.
B
That
Kevin,
actually
before
before
we
go
off
that
topic,
there's
a
remind
you.
You
said
something
there
that
was
crucial
and
I
learned
of
a
an
issue
yesterday,
that
is
was
specific
to
Java
17,
and
so
you
highlighted
that
we
need
to
be
sensitive
to.
We
need
to
continue
watching
for
Java
17
specific
issues
because
they
might
persuade
us
to
to
delay
upgrade
on
on
of
change
of
that
documentation.
B
Right
now,
I
think
the
issue
is
resolved,
but
it
was
a
particularly
complicated
issue
that
Basel
Crow
had
to
investigate
that
was
specific
to
to
Java
17.
he's
investigated
it
I
don't
know
yet
if
the
fix
is
released
thanks,
but
we've
got
to
be
continue.
Monitoring
bug
reports
to
see
if
there
are
any
that
are
specific
to
Java
17
that
might
cause
us
to
say.
Oh,
we
need
to
delay
this
a
little
bit
right
now.
I
think
we're
on
track,
April
or
May.
A
B
B
So
there
are,
there
are
companies
that
run
huge
Jenkins
controllers
and
job
DSL
is
very
important
for
them,
so
if
they
would
have
been
blocked
from
going
to
Java
17,
because
this
job
DSL
bug
made
it
simply
not
work
on
Java
17.
C
Maybe
it's
too
early,
maybe
it's
not
necessary,
but
do
we
have
a
jiram,
epic
or
something
in
place
somewhere
and
the
documentation
where
we
could
list
all
the
problems
we
are?
We
have
with
GDK
17.
B
We
do
there's
a
what
Basel
had
created
is
a
set
of
three
phases
for
the
Java
17
project.
Just
like
he
created
a
five-phase
epics
for
each
of
those
three
phases
and
yeah.
There
are
epics
for
each
of
the
five
phases
that
we
went
through
for
Java
11.,
so
we
have
an
epic
that
we
can
attach
there.
It's
a
good
suggestion.
Let
me
put
the
yeah
thank.
B
Your
question
was
not
stupid
at
all.
Your
question
was
a
very
good
question.
It's
just
a
delight
to
say:
yes
that
was
that
was
considered
and,
yes,
we've
got
a
way
to
do
it,
but
yeah
I
haven't
checked
to
see
if
this
job
DSL
bug
is
actually
attached
to
a
Java,
17
epic,
because
that
may
have
been
missed
and
if
it
was
missed,
it'd
be
a
good
thing
to
attach
it
yeah
very
good
question.
Thank
you.
Yeah.
A
B
B
We
are
one
two,
six,
four
good
and
so
and
that's
there's
a
there's,
an
issue:
where
was
it
that
was
that
has
a
Jenkins
issue
associated
with
it
and
we
can
link
to
that
Jenkins
issue
and
see
if
that
Jenkins
issue
is
correctly
attached
into
the
into
the
Epic,
and
it
is
it's
attached
to
Java
17
support
Phase
One
support
Java
17.
good,
but
we
should.
We
should
put
that
epic
because
we
don't
know
how
bugs
will
arrive
and
and
not
arrive.
B
So
when
we
announce
this
change
through
a
blog
post,
for
instance,
we
should
probably
put
a
link
to
that
epic
so
that
people
can
see
it
saying:
hey,
look,
we've
switched
and
here's
the
here's,
the
point
of
Pride.
That
shows
you
can
go
here
if
you
think
that
there's
something
that
doesn't
support,
Java
17.
A
And
that's
exactly
like:
we
had
for
Java
11
too,
if
anything
right.
B
A
Thank
you
very
much
Mark
for
all
the
additional
context
that
helps
a
lot
in
Bruno
for
a
sparking
conversation
messages
like
I
said:
I
had
no
idea.
This
was
great.
A
Anything
else
on
that
one
as
far
as
Pluto
or.
A
Thank
you.
So
the
next
topic
on
the
agenda
is
adding
books
to
jenkins.io.
This
is
something
that's
been
coming
up
a
lot
more
recently,
folks
are
looking
to
contribute
to
jenkins.io
and
adding
a
book
is
a
pretty
easy
way
to
go
about
contributing
right
now.
The
books
page
looks
like
this,
so
we
have
just
all
the
books
laid
out.
The
numbering
in
the
list
is
going
to
be
removed.
A
Pending
my
pull
request,
I've
submitted
a
request
to
just
get
rid
of
the
number
order
so
that
it's
more
General
and
not
giving
any
sort
of
appearance
of
ranking,
but
what
I've
been
seeing
too
is
that
with
the
books
and
missions,
there's
potential
to
update
the
layout
or
provide
a
little
bit
less
or
more
succinct
book
summary
here.
Some
of
these
can
be
a
little
bit
longer,
but
the
idea
is
we
want
to
make.
A
We
want
to
drive
people
to
interact
with
that
book
itself,
not
give
them
the
book
on
the
page.
So
I
was
looking
around
and
I
did
find
this
example.
So
openstack
has
a
books,
Resource
page,
and
it's
really
clean,
really
simple.
It's
just
a
cover
image
title.
The
author
or
publisher
and
then
a
really
really
short
summary
of
what
the
book's
about
and
then
the
link
takes
you
either
to
The
Pact
in
these
cases,
page
for
it
or
in
other
cases
it
can
take
you
just
right
to
the
Amazon
page.
A
Or
this
one
takes
you
the
V
scaler,
so
it's
just
a
nice
simple
way
to
list
the
books
and
something
like
this
I
think
would
be
a
little
more
aligned
with
what
we
want
for
the
books
page
and
then
the
how
to
add
this.
A
How
to
add
a
book
entry
is
something
that
needs
to
be
added
to
the
Jenkins
contributing
guide
once
we've
determined
all
of
this,
and
once
we
have
decided
that
this
is
what
we
want
it
to
look
like
this
is
how
long
we
should
have
the
summaries
be
Etc
once
we
have
that
we'll
be
putting
that
into
the
contributing
guide
so
that
it's
available
for
everyone.
C
Kevin
I
finally
had
the
time
today
to
have
a
look
at
that.
I
was
intrigued
because
I
wanted
to
know
more
about
what
could
I
find
in
a
book
about
gen,
kids,
so
I
think
the
first
thing
that
striked
me
is
that
how
am
I
supposed
to
go
directly
from
the
front
page
to
this
book,
page
I,
didn't
find
it.
I
had
to
use
a
search
bar.
B
And
finally,
sorry,
that's
really
embarrassing
to
say,
but
it's
it
was.
It
was
an
experiment
launched
to
see
how
it
would
pan
out
and
and
the
experiment
has
turned
into
actually
quite
a
useful
thing.
Right.
I
mean
I,
think
I
think
there's
interest
here,
but
I
don't
think
it's
ready
for
prime
time
yet,
particularly
because
of
the
numbers
on
the
top
left
that
the
one
two
three
Etc,
because
they
they
mistakenly
lead
people
to
think
we've
somehow
ranked
these
or
prioritize
them.
Yeah.
C
I
I
was
ready
to
buy
something,
but
the
thing
is
the
latest.
One
is
not
a
subject:
I'd
like
to
address
as
soon
as
possible.
I
would
have
been
yeah
Jenkins
2
up
and
running
if
it
wasn't
from
218
2018
sorry,
because
so
much
things
have
changed
in
Jenkins
lately
that
I'd
like
something
from
last
month.
B
A
No
worries,
thank
you
very
much
Bruno
for
bringing
all
that
up
yeah-
and
this
was
actually
part
of
hacktoberfest,
if
I'm
not
mistaken,
initially,
and
something
that
Chris
stern
was
had
originally
pitched
and
followed
through
on
so
I
and
I,
and
this
was
around
the
time
that
Gavin
Mogan
was
working
on
the
web
components
for
the
header
and
footer.
So
I
think-
and
this
is
just
me
speculating
on
what
I
can
see
from
in
front
of
me.
I
think
it
was
just
like
a
perfect
timing
of
the
books.
A
Page
was
created,
but
then
the
web
IO,
the
components
were
created
and
they
just
didn't
have
each
other.
So
we
have
the
lovely
components-
the
header
and
footer,
but
unfortunately
it's
not
listed
in
the
about
link
like
it
was
intended
to
so
for
right.
Now,
it's
there
but
you're
right.
It's
not
really
readily
available
as
a
navigation
point,
so
something
we
need
to
fix.
A
But
but
yeah
like
Mark
said:
I
want
to
make
sure
that
everything
is
impartial
and
in
line
with
how
we
want
to
present
the
books.
I
want
to
make
sure
that
the
formatting
and
text
is
okay.
These
number
lists
that
are
not
formatted
as
a
numbered
list
kind
of
take
away
from
that.
So
there
are
a
couple
things
that
need
to
be
adjusted
but
yeah.
A
This
is
something
that
I've
noticed
coming
in
a
lot
more
of
and
with
the
amount
of
response
people
are
getting
providing
for
this
I
think
it
would
be
very
good
to
just
have
that
kind
of
guidelines
in
the
contributing
guide
too
so
and
I
I,
think
time
or
date
of
publication
or
the
publication
date
and
stuff
like
that
is
absolutely
crucial
when
we're
putting
these
books
on
the
page,
because
we
do
want
to
make
sure
that
it's
relevant
information
up
to
date.
A
Some
you
know
nothing
misinformed
or
perhaps
referring
to
older
versions
that
are
simply
not
supported.
So
these
the
books
do
need
to
be
vetted
a
bit
better.
How
we
go
about
doing.
That
is
another
question,
but
that's
you
know
that's
again,
something
we
can
absolutely
figure
out
as
we
go
along.
This
isn't
make
or
break
to
the
Jenkins
experience.
Thankfully,
so
we
can
take
our
time
a
little
bit
but
and
anything
else
on
the
books
topic
from
Bruno.
A
Thank
you
next
up
on
the
list
is
the
Improvement
of
end
of
life
notifications
and
in
tandem
with
that,
the
prep
for
the
Cent
07
end
of
life,
so
the
weight
since
right
now
is
right.
Now,
when
things
reach
end
of
life,
we
don't
necessarily
have
a
way
to
communicate
that
properly
to
our
user
base.
We
want
to
change
that,
of
course,
and
make
sure
that
users
are
notified,
if
anything
that
they're
using
is
hit
going
to
be
hitting
their
end
of
life
soon
and
later.
A
We
have
some
examples
right
now,
so,
for
instance,
Ubuntu
18.04
is
one
of
those
candidates,
the
blue
ocean
container
page,
the
Centos
7
container
image,
the
Arch
Linux
agent
container
image.
There
are
several
things
that
we
can
consider
coming
up
on
end
of
life,
that
these
are
things
we
want
to
notify
people
of
and
give
them
the
best
chance
to
take
care
of.
Before
it
becomes
end
of
life.
A
We
need
to
figure
out
how
that
modification
would,
you
know,
be
delivered
and
how
it
would
look
and
how
it
would
give
that
information.
But
we
do
have
this
really
nice
site
end
of
life.date.
That
is
it's:
it's
got
an
API
guide,
so
it
also
it's
open
and
interactable,
so
that
could
be
something
that
is
potentially
automated
down
the
line.
It
also
has
end
of
life
for
most
things
that
you
run
into
contact
with,
while
using
Jenkins,
including
Jenkins
itself,
so
lots
of
great
info
there,
but
utilizing
that
leveraging.
A
That
would
be
a
good
way
to
get
this
information
out.
We
also
are
considering
blog
posts,
other
announcements
within
meetings,
just
multiple
Avenues,
to
get
this
information
out
and
deliver
it
to
the
user
base.
B
So
the
Okay
Kevin-
you
just
you
just
reminded
me-
there's
something
that
needs
to
be
fixed
on
the
end
of
life
date,
page
and
I'm,
not
sure
how
how
we
explore
that
with
them.
You
you
right
there.
That's
the
perfect
page
notice
that
it
shows
2.375,
that's
correct
and
it
is
in
fact
a
a
valid
version,
but
2.387
is
not
listed
here.
So
we're
missing
the
current
LTS.
A
B
A
B
B
A
B
A
Got
it
okay,
that
makes
way
more
sense,
good
to
know
okay,
great,
thank
you
very
much
Mark
so
and
in
tandem
with
the
notifications,
cento7
is
nearing
end
of
life.
Next
June,
it's
been
a
maintenance
mode
since
2020,
however,
and
it
is
looking
at
older
versions
of
git
and
SSH,
so
two
things
that
are
crucial
to
plugins
working
and
operating
properly,
that
it
just
does
not
necessarily
have
it's
not
supported
by
the
Jenkins
RPM
installer
and
not
maintained
in
its
own
container
image.
A
At
this
point,
the
end
of
life
is
June
2024..
So
again,
like
there's
several
reasons
why
pushing
this
to
end
of
life
now
or
sooner
than
later
is
the
right
call.
A
This
is
something
that
Mark's
been
proposing
and
will
be,
if
not
he's
already
created
a
jet
for
and
so
we're
gonna
capture
the
end
of
life
in
Centos
7
in
The,
Epic
announce
the
deprecation
before
it
happens.
Stop
that
making
sure
to
stop
running
automated
tests
in
Cento,
7
and
just
in
general,
making
sure
that
we
can
remove
all
the
Centos
7
information
from
the
documentation.
This
has
started.
We
are.
A
There
have
been
a
few
places
where
Rocky
Alma,
eight
and
nine
are
suggested,
as
opposed
to
Centos
7,
and
there
are
a
couple
other
options
here.
I
forget
what
they
are
off
top
of
my
head
right
now,
but
there
are
multiple
Alternatives
that
we
can
recommend
instead
of
Centos
that
were
utilize
instead
of
Centos
7
and
so
making
sure
that
the
correct
versions
and
up-to-date
options
are
present
in
the
documentations
is
one
of
the
the
next
big
tasks
as
well.
A
Okay,
no
worries
not
no
issue
there
yeah
and
the
last
thing
on
the
agenda
and
again
we're
just
gonna
move
the
doc's
office
hours
to
an
earlier
time,
one
hour
earlier,
making
sure
that
this
is
readily
available
for
everyone
in
the
EU
us
this.
It's.
If
we
stick
to
crazy
daylight
savings
time
here
on
my
East
Coast,
it's
going
to
be
way
too
late
and
I
don't
feel
comfortable
with
that
for
the
whole
rest
of
the
world.
So
we're
going
to
adjust
that
and
today's
the
first
day
so
yeah.
A
C
No
I
don't
think
so
I'm
as
lost
as
you
are,
and
yesterday
I
discovered
that
in
Phoenix
Arizona
they
don't
change
with
summer
time
and
winter
time.
I
didn't
know
that
which
is
kind
of
funny
to
me
and
10
days
from
now.
It
will
be
one
hour
later
in
France,
so
it
will
be
about
7
30
p.m.
So
the
time
is
fine
with
me
for
this
week
and
even
in
two
weeks
from
now,
that's
really
perfect.
Thanks
a
lot
for
thinking
of
us
European.
C
Yes,
but
you
need
some
time
to
eat
if
it's
1
pm,
McCarron
I,
don't
know.
A
B
A
Yeah
I'm,
the
one
suggesting
it
I
I,
definitely
am
okay
with
it,
and
I
already
made
sure
it
doesn't
conflict
with
anything
from
me
as
well,
so
yeah.
We
can
just
keep
it
at
that
time
and
just
make
life
easier
for
everyone
involved.
A
Awesome
that
takes
care
of
everything
on
the
agenda.
I
just
realize
we're
over
time
by
a
couple
minutes.
So
we'll
call
things
here
again.
Thanks
for
joining
I
appreciate
it,
the
video
will
be
available
in
24
to
48
hours
and
take
care,
and
until
next
week.