►
From YouTube: 2023 08 04 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
Thanks
for
being
here,
topics
on
the
list
include
Google
summer
of
code,
open
pull
requests
of
Interest
devops,
World,
Tour
and
possibly
canceling
the
meeting
August
18th
any
other
topics,
you'd
like
to
add
Chris,
no
okay.
So
let's
talk
to
Google
summer
of
code,
first
version
documentation
for
jenkins.io.
So
as
I
understand
it,
Vandy
will
do
a
demo
demo.
The
the
status
at
ux
Sig,
the
14th
of
August,
is
that
right,
16,
August,
16.
yep
great
now,
I
apologize
I
won't
be
there
I'm
out
of
the
office
that
day.
A
B
B
A
A
B
B
But
I
do
have
some
questions
about
like
what
we
should
do
regarding
cooking
existing
versions,
because
we
have
to
accommodate
all
of
them
up
to
where
I
am.
A
B
B
A
A
It's
a
good
question
so
and
that's
certainly
a
good
question
to
ask
in
the
how
many
versions
should
be
in
the
documentation
in
the
list
of
versions,
or
maybe
we
say
it
this
way,
which
versions
should
be
in
the
list
of
versions,
right,
yeah
and
my
thought
was:
Mark
thinks
LTS
Baseline,
so
2.41.1
2.414.1.
A
You
know
that
that's
that's
the
concept
that
one
is
probably
more
accurate
because
we'll
certainly
take
the
snapshot,
we'll
create
the
branch
at
the
dot.
One
branch,
but
it'd,
be
understandable
to
say,
okay,
dot
X.
That
would
be
fine
with
me
either
way.
Okay,
so
I
weekly
seems
too
frequent
and
won't
have
many
changes
between
wouldn't
have
would
not
have
many
changes
between
branches.
B
A
A
A
C
Shoots
there,
can
you
hear
me
now,
yes,
I'd
be
comfortable
with
that
I
mean
we
don't
we
don't
have
that
many
changes
right
that
correct
and
it's
I'm
thinking
that
in
vast
majority
of
the
cases
the
changes
to
the
docs
were
released,
aren't
related
to
software
that
changes
right,
they're,
just
improvements
so
yeah,
that's
it's
always
I
mean
it's
a
temptation
to
be
really
really
precise
about
it,
but
also
that
becomes
mind-boggling.
That
I.
You
know
it's
a
lot
really
easy
to
remember:
2.1
2.2
versus
2.138.3,
you
know
or
something
the
longer
numbers
right.
A
Well,
and
My
worry
is
if
this:
if
this
menu
has
150
entries
in
it,
the
the
reader
will
get
lost
right.
They
right
it's
just
too
many
and
already
with
four
a
year
can,
if
we,
if
we
were
to
do
all
of
them,
we
should
not
I
think
we
should
just
start
Where
We
Are,
but
if
we
were
to
do
all
of
them,
we
would
have
lts's
what
that
would
be
10
years
at
four
per
year.
A
A
Five,
that's
probably
another
good
idea
well
and
and
I
like
their
pattern
here.
I!
Oh,
is
this
one,
no
I
thought
I'd
seen
some
version
documentation
sites
where
they'll
give
you
a
we'll,
show
you
the
first
five
and
then
give
you
a
more
link
or
something
like
that.
Oh.
C
A
There
so
the
book
actually
is
a
real
book
and
so
that
one
I'm
not
sure
they
do
it's.
This
is
this
is
a
representation
of
a
published
book.
Okay
and
so
it's.
This
is
a
physical
book
that
they
who,
for
whose
source
code
is
intentionally
open,
source.
C
A
C
A
A
A
Okay,
good
all
right
so
so
Meg
agrees.
A
C
B
A
Allow
more
or
something
like
that
now:
no
idea,
if
that's
even
possible
in
antora
I,
don't
know
how
what
and
how
antora
thinks
about
this
Chris.
Do
you
have
any
idea?
What
does
antora
do
with
regard
to
many
versions.
A
Well
so
when
you
say
say
manual
effort,
I'm
assuming
Chris,
maybe
you
can.
You
can
certainly
help
I've
missed
the
the
presentations
by
Vandy
with
vacation
and
whatnot
is.
Is
it
dependent
on
just
a
branch
and
then
it
will
build
everything
from
that
Branch,
so
2.1
in
this
example
is
a
different
branch
than
2.2
is
I.
A
Excuse
me
so
Meg
I
think
I
think
to
answer
your
question:
how
manual
is
it
it's
easy
to
create
a
new
Branch?
We
just
get
get
check
out
minus
B
if
the
branch
and
then
push
it
to
the
central
repository
and
probably
add
an
entry
in
some
configuration
file
that
says
read
from
this
branch.
In
addition,
yeah.
A
B
I
think
we
may
be
possible
that
the
feature
I
think
I've
asked
to
ask
to
next
to
the
diet
version
might
be
possible,
but
we
need
to
investigate
so.
C
C
B
Probably
not
much,
except
for
the
fact
that
event
it
still
has
exams.
So
we
have
to
wait
until
he
comes
back
maybe
next
week.
Okay,.
A
So
so
van
did
offline.
Also
this
this
week
great.
That
means
I
all
right,
no
problem
very
good,
so
we
continue
then
I
mean
it.
It
looks.
It
looks
very
attractive.
What
your
sense
is
it
is
there
any
hope
that
it's
going
to
be
ready
for
merge
at
the
end
of
the
project
or
more
likely,
there's
going
to
be
a
lot
of
work.
You
had
to
do
I.
B
Think
I
think
it
might
be
possible.
It
depends
on
in
this
schedule,
because
I'm
I'm
kind
of
worried
like
there
might
be
something
like
some
other,
like
integration
issues
that
you
may
crop
up
towards
the
actor
implementation.
B
A
B
That
I
was
I
was
hoping,
as
your
thoughts
should
show
up.
It
hasn't
well.
A
So
we
did
a
demonstration
last
week
with
ostratosh
for
45
minutes.
Okay
and
then
I
saw
a
demonstration,
a
five
minute
demo
or
a
demo
today
from
Bruno
Marsden
and
he'll
do
another
demo.
Bruno
will
will
do
a
more
detailed
demo.
A
C
Sorry,
I,
muted
myself,
because
I
was
being
noisy,
no
I
thought
it
was
very
very
nicely
done.
I
was
impressed
and
the
way
he
presented
it.
It
was.
A
A
So
in
this
Python
tutorial
on
my
Linux
thing,
first
thing
I
had
to
do
was
paste.
This
command
then
paste
this
command,
then
scroll
down
and
paste.
This
content
to
a
file
then
paste
this
command
and
then
paste
this
command.
Okay,
so
you
can
see
that
there's
this
long
horrible
experience
for
the
user
copy
and
paste
an
awful
lot
of
stuff.
A
Don't
skip
don't
misalign
Etc
and
finally,
after
all,
that
you've
reached
the
post,
install
wizard.
Well
what
what
Bruno's
and
ashutosh's
work
has
done.
So
what
astrotasha's
work
has
done
is
has
changed
this
whole
terrible
thing
into
three
commands:
git
clone,
CD,
Docker
compose
up,
oh
okay,
and
it's
that
simple
and
and
now
inside
the
docker
compose
it's
actually
running
two
Docker
containers.
It
creates
a
dedicated
Jenkins
agent,
that's
used
for
with
the
tool
for
the
particular
demo
so
in
or
for
the
particular
tutorial.
A
A
B
C
A
A
Good,
so,
and-
and
it's
not
just
you
know,
we
say
oh-
is
that
just
one
tutorial?
No,
no!
Actually
it's
installing
Jenkins
in
the
docker
environment
can
show
that
as
well.
Here's
how
you
do
it
with
Docker
compose
instead
of
this
long
horrible
sequence,
and
by
the
way
the
docker
compose
thing
converges
Linux
and
windows
to
use
the
same
command.
C
A
A
B
A
B
A
Plug-In
Health,
score,
Adrian
and
so
jagruti
seems
to
be
seems
to
be
proceeding.
There's
some
concern
there
and
they're
discussing
and
seeing
hey
okay.
What's
next,
how
to
help
Etc
so
moving
forward
good,
okay,
anything
else
on
Google
some
summer
of
code,
oh
upcoming
dates.
A
B
A
A
A
A
A
A
So
the
tool
detected
that
we
needed
to
change
the
python
version
from
3.10.7
to
3.11.4
and
it
targets
it
on
Alpine
318
and
make
sure
this
is
a
valid
container
and
I
just
ran
through
the
entire
tutorial
using
exactly
this
setup,
and
it
worked
great
oh
now,
this
is
a
fun
one.
This
is
a
dramatically
better
setup.
Okay,
this
one
detected
a
a
badly
outdated
python,
so
python
2
and
correctly
gave
it
a
a
modern
python.
A
Python
3
version.
B
C
A
A
Yeah,
so
what
I
think
what
what
update
CLI
will
be
taught
is
use,
something
that
has
a
base
of
18
Dot
and
then
only
increment
the
things
after
the
18..
So
if
there
were
an
18.17
it
would,
it
would
choose
it,
but
19
or
20
it
would
not
choose,
because
those
are
not
lts's.
B
C
A
A
So
that
that
looks
really
really
quite
good,
actually
I'm,
I'm,
truly
thrilled
next
topic
on
the
pull
request
of
interest.
Is
this
kubernetes
outline
from
tanu
Sharma
and
right
now,
there's
been
no
additional,
no
additional
progress
on
it.
We've,
given
our
feedback
and
tanush,
has
has
not
been
back
to
it.
So
we've
there
have
been
four
or
five
commits
that
I
did
that
Kevin
Martins
did
of
things
we
thought
would
help,
but
needs
needs
tanush
to
come
back
before
it.
It
gets
more
time.
Yeah.
A
Okay,
so
next
piece
and
Chris
this
one
for
you,
as
as
in
your
role
as
release,
lead
I,
started
a
conversation
with
the
release
officer
with
all
the
Jenkins
officers
and
the
board
using
this
document.
As
my
oops,
let's
do
this
one
using
this
document
as
my
framework,
so
the
concept
here
is
that
Java
11
will
reach
end
of
public
support
in
October
of
2024.
A
A
So
there's
there's
a
range
but
we're
based
on
Tamarin,
and
so
my
proposal
to
the
board
and
to
Tim
jacome
and
to
Damien
and
to
Kevin
Martens
was:
let's
declare
that
the
Jenkins
project
will
stop
supporting
Java
11
when
Tamarin
stops
supporting
it
at
the
end
of
October
2024.,
and
they
were
generally
receptive
to
that
I
said
yeah.
That
makes
sense
that
follow
that's
consistent
pattern.
A
A
A
A
So
the
proposal
that
I
made
was,
let's
plan
to
release
a
Jenkins
weekly
version
that
supports
Java
21
before
the
end
of
October,
2023.
and
Basel.
Crow
has
agreed
to
do
infrastructure
work
or
not
in
for
to
do
core
and
tooling
work
if
necessary.
Damien
and
the
infra
team
have
agreed
to
do
the
the
work
on
infrastructure
and
Kevin
Martin's
agreed
to
review
and
write
documentation,
changes
as
needed.
C
A
A
000
installations
is
Java
17.,
so
even
without
the
admin
monitor
we're
already
getting
adoption
of
java
17,
but
our
we
would
like
to
dramatically
improve
this
and
start
tapering
Java
11
off
yeah,
and
then
there
was
one
more
question
from
from
Damian
de
portal.
What
about
Java
8
in
our
Jenkins
infrastructure?
Java
8
is
already
not
supported
by
Jenkins,
but
we
keep
it
Java
8
in
the
infrastructure,
because
old
plugins
still
need
to
use
it
to
build.
We
don't
want
to
break
their
build
process
and
what
of
the
status
quote.
A
A
The
other
is
if
there
were
to
come
a
time
when
Java
8
updates
became
just
too
painful
for
the
infra
team,
they
could
tell
us
and
we'd
drop
it.
Then
this
is
just
for
tooling
and
just
on
Jenkins
infrastructure.
Jenkins
still
does
not
support
job
8
and
will
continue
to
not
support
Java,
okay
yeah
any
concerns
on
any
of
those.
C
A
Good
good
question,
so
the
plug-in
Health
score
actually
sees
that
already
today.
So
if
we
were
to
look
at
the
plug-in
Health
score,
we
can
we,
let's
search
for
what
should
we
search
for
how
about
yet
we'll
search
for
plugins
related
to
git?
And
here
we
see
a
plug-in
called
get
parameter
with
a
relatively
lower
Health
score,
see
if
I
can
find
one
even
worse
how
about
GitHub
organization
folder?
This
is
a
good
one,
because
it's
also
a
deprecated
plugin
okay.
A
B
B
A
C
A
Right
exactly,
and
so
what
we've
done
is
we've.
He
has
codified
checks
to
see
those
things
that
we
used
to
say.
Please
check
to
see
if
there's
a
maintainer,
please
check
to
see
if
there
are
a
bunch
of
bugs
reported
against
it.
Please
check
all
those
things
and
when
you,
when
you
go
to
the
health
score,
it
will
tell
you
these.
Oh
yeah,
there's
a
reason.
It
got
a
44
out
of
a
hundred
yeah.
A
A
The
top
topic
that
was
approved
is,
let's
see
how
I've
got
to
remember.
The
exact
title
I
just
was
was
creating
the
slides,
so
it
should
be
right.
On
my
mind,
business
benefits
of
Open
Source
contribution,
oh
and
so
I'm
going
to
talk
to
people
about
why
their
business
will
do
better
if
they
will
intentionally
choose
to
contribute
to
open
source.
Oh
nice
yeah,
it's
a
it's
a
fun
sort
of
controversial,
really
you're
telling
me
I
can
I
can
improve
my
business
by
giving
things
away,
and
the
answer
is
absolutely
selectively.
C
A
Talk
some
some
reasons
why
Etc
I
mean
it's
a
it's
it.
It
includes
several
stories
from
my
life
of
highlighting.
Oh
here's,
why
we
did
this
and
it
was
specifically
because
it
was
benefiting
the
business
and
here's
why
we
did
this.
So
it's
it's
got.
Some
of
Mark
weight
is
old
enough.
Mark
Wait
is
experienced
enough
to
remember
some
things.
Uh-Huh.