►
From YouTube: 2023 02 09 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
Thank
you
welcome
everyone.
This
is
the
9th
of
February,
it's
Jenkins
documentation,
office
hours,
topics
that
I
have
on
the
agenda
action
items,
LTS,
release,
fostom,
summary
documentation,
transition,
prep
for
Centos,
7,
end
of
life,
interacting
with
candidate
contributors
from
gsoc,
and
pull
requests
of
note.
Now
sayantan.
Since
you
joined
us,
there
may
be
topics
you'd
like
to
add
to
the
agenda.
Are
there
any
specific
topics
you
wanted
to
bring.
B
A
Okay,
all
right,
so
so
that's
a
that's
a
good
question
I
mean
given
that
that's
not
quite
on
the
documentation
topic
if
you're,
okay,
with
it
I'm
going
to
get
us
through
the
other
topics,
and
if
we've
got
time
we'll
get
to
get
to
that
one.
Would
that
be
all
right,
yeah
of
course,
okay,
great
all
right!
So.
A
And
how
to
become
more
involved-
good,
okay,
good
yeah,
so
I'm
not
I'm,
not
especially
skilled
in
it,
but
we
may
be
able
to
answer
some
of
your
questions
and
answering
questions
sometimes
is
all
that
it
takes
for
someone
who's
interested
to
then
make
further
progress.
So,
let's,
let's
take
that
but
I
propose.
We
still
take
it
at
the
end.
A
We
just
released
the
long-term
support,
release,
2.375.3
the
changelog
and
upgrade
guide
was
out,
but
I
I
realized.
There
was
a
a
miss,
so
it
looks
like
we
missed
a
at
least
one
LTS
candidate
in
the
in
the
back
ports,
meaning
it
was
included
in
the
Jenkins
issue,
tracker
or
labeled
in
the
Jenkins
issue.
Tracker.
A
A
The
next
LPS
Baseline
has
been
selected
2.387.1
and
will
look
promising
so
that'll
happen.
March
March,
8
2023
is
the
release
date.
C
So
it
feels
the
same
process
as
you
explained
the
other
day.
Looking
at
the
number
of
problems,
a
release
has
to
know
if
it's
a
good
release
candidate
or
not
right.
C
And
the
ratings
are
only
people
complaining,
oh,
not
complaining,
sending
a
report
when
something's
going
wrong
with
a
weekly
release.
A
Actually,
it's
it's
a
little
more
than
that.
So
if
we
look
at
the,
if
we
look
at
the
page,
we
go
to
the
and
I'll
put
a
link
on
to
this
page.
We
go
to
the
changelog
page
for
weekly
releases.
The
rating
system
that
I'm
referencing
is,
is
this
system
of
clouds
and
sunshine
yeah
and
and
that
those
clouds
and
sunshine
we
get.
We
only
get
a
cloud.
We
only
get
Sunshine
if
someone
reports
a
positive
item.
A
A
A
A
Pause
them
summary
so
Bruno,
maybe
you
can
give
a
brief
summary
of
of
things
that
went
on
to
Foster
and
how
it
Reef
will
be
difficult.
C
It's
very
intense,
it's
a
two
days
in
Brussels
where
all
the
people
from
around
the
world
imply
involved
in
open
source
come
discuss.
Prison
share,
show
wow
whatever,
so
we
had
a
booth.
We
were
five
six
seven,
depending
on
the
hours
around
the
booth
from
the
Jenkins
project
and
trying
to
answer
no
succeeding
in
answering
all
the
questions
people
had,
but
most
of
the
time
people
were
just
coming
to
say,
hello.
We
do
love
Jenkins
and
we
use
it
and
we
yeah.
C
C
So
as
I'd
like
to
know
if
something
is
cooking
or
if
we'll
just
keep
the
old
HTML
we're
all
used
to,
and
unfortunately
we
had
I,
don't
know
if
it's
demo
proof
of
concept
or
just
a
mock
from
Jan
and
Tim
I
guess
which
was
running,
and
that
was
which
we
shown
people,
because
lots
of
people
were
also
loving
blue
ocean.
C
You
know,
and
they
wanted
to
know,
what's
going
to
happen
with
blue
ocean,
and
lots
of
them
were
kind
of
sad,
but
we
were
telling
them
no
new
features,
only
security
updates
and
fixes,
but
that's
all
you
should
think
of
changing
or
just
leading
letting
that
alone,
and
they
were
pretty
sad
about
that.
But
when
we
shown
them,
the
proposed
revamp
of
the
UI
were
relieved.
In
fact,
so
they
knew
that
Jenkins
is
still
going
strong.
We've
spent
some
time
cleaning
up
the
UI
UI
exit.
C
Now
it's
almost
ready
for
the
new
generation
of
UI
and
ux,
and
that's
important
and
yeah.
That's
the
part
that
people
are
not
super
happy
with.
You
know
just
your
UI
ux,
which
is
getting
old,
but
it's
getting
better
and
better
every
month,
I
should
say
even
now,
not
with
a
prototype,
but
just
what
we
can
see
from
now
since
last
year.
It
has
changed
dramatically
already
and
it
will
get
better
and
better.
C
We
didn't
get
any
angry
people
about
Jenkins,
but
people
loved
Jenkins,
not
happy
or
sticker.
You
know
the
one
with
the
flame,
that's
known
you
get
when
you
go
to
500
euro
or
something
in
10,
kids,
just
love
it
and
yeah.
Most
of
the
time
people
were
just
saying
hello.
We
love
drinking.
Your
project,
rocks
your
T-shirt
rock.
Your
stickers
are
over
the
top,
your
fantastic
crowded.
C
Are
of
course
the
project
is
18
years
old
or
something
like
that,
and
it's
still
rocking.
What
could
you
say?
A
lot
of
people
wanted
to
interact
with
us
to
propose
some
partnership
between
different
communities.
They
wanted
to
testify
about
their
use
of
Jenkins.
For
example,
we
had
the
CERN
CER
and
some
people
from
the
turn,
so
the
place
where
the
World
Wide
Web
got
invented,
saying
that
they
were
using
Jenkins
to
collect
and
process
their
iot
data.
C
For
example,
some
people
from
Big
Automotive
companies
also
were
testifying
about
their
use
of
Jenkins
and
so
on
and
so
on.
It
was
amazing.
I
knew
already
that
there
were
lots
of
different
Industries
using
Jenkins,
but
real
people
in
front
of
me
saying
in
front
of
my
face.
That
was
a
whole
another
experience
that
was
super
cool
and
not
linked
to
Jenkins,
but
what
I
attended
there
was
people
interacting
with
each
other,
trying
to
help
each
other
to
share
some
knowledge.
C
A
Thanks
very
much
Bruno.
Thank
you.
Next
topic,
then
documentation
transition
to
Java
11..
So
this
conversation
started
a
month
or
two
ago
when
we
realized
that,
when
Debian
12
releases
in
April
or
May
of
2023,
it
will
not
include
Java
11..
It
won't
be
available
from
the
the
standard
Debian
12
package
manager
at
all.
A
You
can
only
get
Java
17
at
that
point
for
for
Debian
12
from
the
Debian
project,
and
because
of
that,
we
don't
want
to
have
one
document
that
says
this
is
how
you
install
on
Debian
12
and
we
fully
support
Java
17.
So
the
decision
is
that
with
that
release
or
about
the
time
of
that
release,
we'll
transition
the
installation
documentation
from
java
11
to
Java
17.
A
that
has
progressed
further.
We've
further
decided
we're
going
to
do
that
for
both
windows
and
Linux,
because
Java
17
is
supported
on
Linux
and
windows
by
the
Jenkins
project,
no
problem,
it
keeps
things
consistent
and
encourages
people
to
move
to
Java
17
sooner
so
that
they
they
can
get
more
experience
and
understand
and
get
the
benefits
of
java
17.
C
Yes,
we
even
see
I've
seen
some
performance
increase
when
using
Java
17.
If
I'm
not
mistaken,
I
think
I
read
something
for
Basil,
saying
that
it's
not
totally
linked
to
that,
but
we
talked
the
other
day
about
the.
There
is
no
reference
to
chevron's
time
being
in
the
documentation
is
tamarind.
You
know,
oh
right
and
I,
don't
know
if
it's
an
open
action
item
or
whatever
but
I
know
if
it's
still
relevant.
C
So
do
we
plan
on
writing
something
somewhere
in
the
documentation
related
to
our
use
of
steamerin,
of
course,
we're
using
Tamarind
for
our
containers.
But
I
don't
know
if
that
makes
sense
to
tell
about
Tamarind,
because
we'll
rewrite
all
the
documentation
for
open,
jdk,
17.
A
A
I
don't
know
well,
but
let's
this
is
supposed
to
be
a
working
session.
Let's
just
create
the
issue
yeah,
let's,
let's
go
ahead,
because
there
is
no
reason
why
we
should
not
acknowledged
that
okay
Tamarind
here
should
we
add
that
we
had
the
open
question,
but
it
looks
like
we
didn't
ever
address
the
question
with
a
specific
action.
So
let's
make
an
action
yeah.
Let's
do.
A
But
but
oh,
oh,
no!
No!
Look!
I'm!
Looking
in
the
wrong
I'm!
Looking
at
the
wrong
repository
just
a
moment,
let's
find
the
correct
repository.
We
don't
want
core.
We
want
jenkins.io
and
here.
If
we
look
for
tamarin
I
would
hope
we'll
find
an
issue.
Oh
no,
okay,
good!
So
let's
create
an
issue,
and
this
is
a
documentation
item
which
should
be
note.
The.
A
A
Or
builds
and
tests
right,
the
controller
builds.
A
A
A
B
A
C
Of
course
I've
been
using,
you
know
the
use
before
I
was
using
a
extensive,
vcenter
S7,
because
I
was
forced
to
and
it
was
a
mess.
I
had
to
recombine
curl
get
lots
of
things
to
keep
seeing
almost
secure
exactly.
A
Well,
and
and
it's
it's-
it
was
deprecated
or
it's
it's
in.
It
entered
maintenance
phase
yeah
three
years
ago,
two
and
a
half
years
ago
at
least
it
will
be
officially
end
of
life
from
the
Santos
project
in
June
of
2024.,
I
think,
and
it's
already
not
supported
by
our
RPM
installer,
since
the
change
to
system
d
yeah
and
the
container
image
that
provides
centos7
and
that
we
use,
as
our
bases
was
deprecated
late
last
year.
A
A
So
there
are,
there
are
several
different
Replacements
right.
It's
a
good
good
point.
Replacements
include.
A
A
A
A
Cool,
so
so
there
are
lots
of
lots
of
options
to
to
replace
them
now.
None
of
them
use,
Ancient
command
line
get,
and
none
of
them
use
the
ancient
SSH,
and
so,
if
You
Were
Somehow
critically
dependent
on
those
ancient
versions.
They
won't
do
that
because
they've
all
long
ago,
upgraded
from
those
ancient
versions
of
something
more
modern
cool.
C
A
A
We
can
replace
it
with
one
that
does
eight
or
nine,
because
I
think
Darren's
created
that
video
as
well,
but
that
video
should
be
removed
right.
It
should
be
replaced
and
I'm
confident
there
are
other
things
like
that,
scattered
throughout
the
documentation
where
we
need
to
seek
and
replace
any
mentions
of
Centos
7
with
Centos
8
or
better
yet
Santos
nine,
so
shoot.
B
A
Here
we've
got
the
the
Linux
requirements,
page
talks
about
hey,
supported
and
not,
and-
and
so
in
this
case
at
the
moment,
cento7
by
this
definition
is
level
one
supported,
because
maybe
I
don't
know,
maybe
we
don't
run
automated
package
manager,
installation
tests,
so
that's
another
thing
for
us
to
check
is
so
check
that
automated
packaging
tests,
or
maybe
what
we
should
say,
is
stop
running
Automated
Packaging
Automated
Packaging
tests
of
Centos
7..
A
A
Good
all
right
any
objections
to
that
idea.
Bruno,
no,
not
at
all.
That's
perfect,
okay,
good!
We
are
nearly
running
out
of
time,
I!
Suppose
we
skip
to
the
end
and
let's
see
if
we
can
answer
some
of
sayantan's
questions
about
plug-in,
Health
score
and
skip
the
other
topics.
Are
you?
Okay,
with
that
Bruno.
A
B
Yeah
so
I
I
started
contributing
by
and
by
pulling
small
apis
in
the
login
site,
so
two
of
them
were
merged,
even
though
they
were
small
changes.
I
mean
it
was
quite
exciting
and
there
are
two
still
to
be
reviewed,
so
I
thought
about
I
should
start
contributing
to
a
major
project.
B
So
dheeraj
told
me
to
take
a
look
in
that
project
plug
and
help
scoring
and
I'm
going
through
the
comments
one
by
one
so
which
were
done
in
the
previous
G-Shock
and
I'm
understanding
the
code
a
bit
but
I'm
not
able
to
understand.
Where
should
I
start
from?
Where
should
I
start
contributing?
So
can.
A
You
help
me
in
there
sure
well
so
I'm
going
to
I'm
going
to
offer
some
ideas
of
first.
First,
let's
look
at
what
does
plug-in
Health
score.
Tell
us
today,
because
if
you
haven't
seen
it
yet
so
plug
in
health.jenkins.io
shows
us
the
current
state
of
the
plug-in
health
system
so
see
the
current
site
at
this
location.
Right.
A
And
and
then,
if
I
look
at
this
talks
about
which
probes
are
available
and
if
we
go
to
a
the
results,
page
talks
about
okay,
which
how
many
plugins
are
having
a
problem
or
or
of
hit
that
particular
probe.
So
we
have
294
plug-ins
that
are
using
this
229
and
almost
1
800
have
a
correct
setting
for
SCM.
So
that's
that's
gives
some
indication
now.
A
A
So
now
I'm
not
sure
it's
scientan,
that
any
of
that
has
helped
you
as
much
as
as
you
might
have
wanted,
but
that
gives
you
some
overview
of
what
you're
looking
at
first
and
now
back
to
your
question,
it
was:
are
you
are
you
wanting
to
know?
How
would
you
approach
adding
a
new
probe
like
one
of
these
simple
probe
ideas,
or
are
you
thinking
how?
How
would
you
compile
the
code?
How
do
you
interact
with
it?
What
what
which.
B
Questions
I'm
thinking
I
mean
how
should
I
approach
a
problem
because
I'm
new
to
Java
and
I
really
don't
know
what
I
should
contribute
right
now
and
there
are
not
many
issues.
I
can
work
on
in
the
GitHub
paid,
so
I'm
really
confused.
Where
should
I
start.
A
A
So,
for
example,
these
are
existing
probes,
but
we
have.
We
have
plenty
of
things
that
we
might
say.
Oh,
what
are
some,
what
are
other
things
we
might
ask
about.
What's
the
quality
of
a
particular
plug-in,
how
good
or
bad
is
it
so
and
and
that's
how
you
would
choose
to
write
a
probe?
So
the
idea
here
was:
let's
see,
let's
look
at
this.
Some
of
the
things
does
the
probe
have
a
cons?
Does
the
Jenkins
plug-in
have
a
contributing
guide?
A
A
A
Okay,
so
first
first
the
key
things
are
answer:
what's
what's
a
what's
a
plug-in
and
what
components
why
maybe
this
one?
Why
why
do
we
care
about
the
score
of
a
plug-in.
A
B
Me
if
I'm
wrong
so
plugins
are
like
we
use
them
in
the
Jenkins
to
make
our
work
easier
and
they
are
available
in
the
plugin
site
and
the
plugin
plug-in
Health
score
is
evaluated
using
probes,
which
are
many
factors
like
if
if
a
plugin
has
a
SCM
or
it's,
it
has
been
updated
regularly
or
it
has
a
depend
award.
So
the
plug-inth
health
score
is
evaluated
between
0
and
1.
A
Very
good,
you
got
it
exactly
right,
excellent,
okay!
So
so
then,
let's
take
the
next
step,
what
which
scores
or
which
probes
might
be
useful
to
add
right
so
which
things
might
contribute
towards
a
the
score
of
a
plug
to
towards
our
deciding
if
a
plug-in
is
well
maintained
or
not.
Now,
this
is
where
we
could.
A
A
And
so
we
read
this
tutorial
and
it
says
a
contributing
guide.
Has
the
file
name
contributing.md,
all
right?
So
all
the
probe
has
to
do
is
ask
GitHub.
Does
this
plug-in
have
a
file
in
its
repository
name
contributing.md
and
if
not
the
score
should
be
zero
or
that
not
the
score?
The
the
probe
says
no
contributing
guide.
Otherwise
it
says.
Oh
yes,
has
a
contributing
guide,
so
does.
Does
that
give
you
does
that
give
you
sort
of
an
end-to-end
at
least
starting
picture.
C
A
A
C
A
Exactly
Bruno's
right:
this
is,
this
is
okay.
We
just
we
went
through
the
thought
process
found
two
that
were
reasonable
and
now
he's
found
the
best.
This
is
the
best
one,
because
it
does
exactly
the
same
check.
It
looks
instead
of
for
a
contributing.md,
it's
looking
for
a
file
named
Jenkins
file
in
the
GitHub
repository,
so
so
the
probe
would
be
do
what
Jenkins
file
probe
does,
but
instead
of
checking
for
a
file
named
Jenkins
file
check
for
a
file
named
contributing.md.
A
C
Yeah
right
and
sayant
and
I
put
the
link
into
the
meeting
chat.
You
should
have
a
chat
button
somewhere.
If
you
click
on
it,
you
will
have
the
Three
Links.
We
talked
about
during
this
meeting
just
before
the
meeting
end
and
the
league
disappear
forever
or
you
will
find
them
in
the
document
that
Mark
was
written,
Reading,
Writing,
yeah
right.
B
C
A
A
All
right
thanks,
everybody,
the
recording,
will
be
available
in
about
well
I
hope
within
24
hours,.