►
From YouTube: 2023 08 31 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
A
Google
summer
of
code
and
I
think
we
should
move
this
one
much
higher
on
the
list,
because
it's
actually
got
real
action,
existing
requirements
document,
then
some
bookkeeping
items
and
devops
World.
Anything
else,
Bruno!
No!
Thank
you!
Mark!
Okay.
So
let's
look
at
the
blog
post
first
and
see
what
we've
got
an
impressive
array
of
blog
posts
that
arrived
over
the
course
of
the
last
few
days.
A
B
A
We've
got
the
risk
5
blog
post
from
Bruno.
A
A
C
So
we're
almost
at
the
end.
We
are
in
the
last
week
of
Google
some
of
code
for
these
projects,
so
the
goal
was
to
modify
the
existing
documentation
for
the
tutorials
and
to
simplify
them
quite
a
lot
and
to
get
rid
also
of
Docker
in
Docker
in
these
tutorials,
because
it
was
very
intimidating
for
first-time
users.
C
We
are
at
the
end
of
the
project
and
we
haven't
been
able
to
integrate
the
new
documentation
into
jenkins.io
yet,
and
we
haven't
been
able
to
insert
our
Docker
images
for
these
tutorials
in
the
Jenkins
Docker
Hub
repo
either,
but
we
all
we
have
all
the
material
to
do
so.
The
thing
is
the
time
frame
was
kind
of
short
to
get
all
of
this
done
and
we
can't
integrate
the
documentation
as
long
as
we're
not
using
the
Jenkins
infra
Hub.
C
So
it's
a
chicken
egg
problem,
but
all
it
there
and
we
do
hope
to
be
able
to
integrate
everything
into
jenkins.io
and
the
Jenkins
CI
infra
by
oktoberfesto,
so
so
by
the
end
of
September.
If
all
planets
get
aligned
correctly
we'll
see
but
hey
now,
we
have
now
four
or
five
five
tutorials
working
with
just
one
command,
which
I
find
beautiful.
It's
just
darker
compose
up
in
the
name
of
the
tutorial
and
Bam
you've
got
a
working
Jenkins
instant
with
an
agent
and
ready
to
go.
You
want
to
start
with
node
your
we've
got.
C
C
Yes,
in
fact,
we
tried
to
get
it
as
up-to-date
as
possible,
so
you
we
are
using
the
Jenkins
LTS
version,
of
course,
but
as
for
the
plugins,
we
have
something
that
runs
every
day
and
proposes
a
new
plug-in
versions.
If
ever
they
exist
so
you're
guaranteed
that
you're,
using
the
latest
versions
of
plugins
and
of
the
Jenkins
LTS,
that's
pretty
cool.
C
But
yes,
the
problem
is
it's
still
on
ashutosh,
Docker,
Hub
repo
and
not
on
Jenkins,
and
that's
why
people
could
be
afraid
of
using
that
and
that's
why
we
can't
put
that
in
the
official
documentation
yet,
but
the
PRS
should
arrive.
You
know
for
Jenkins.
I
o
website
should
arrive
next
week,
hopefully,
and
we
won't
be
able
to
merge
them
of
course,
but
they
will
be
there.
We
can
discuss
for
a
few
weeks
and
then
hopefully
integrate
them
into
the
website
ones.
That
Jenkins
infra
has
our
images
in
there
Docker
help
repo.
B
C
Yes,
the
trick
is
you
have
to
do
a
Docker
compose
down
minus
V
if
I'm
not
mistaken,.
C
Two
and
that's
all,
and
if
ever
you
had
forgotten
about
that,
you
know
if
you
run
Docker
compose
up
without
shutting
down
the
first
one.
You
will
get
an
error
message
that
tells
you
oh
it
looks
like
you
have
forgotten
to
do
the
docker
compose
down
minus
V.
So
that's
pretty
much
self-explanatory.
That
should
be
easy
for
the
end
user.
Hopefully.
A
A
A
A
A
We've
extended,
the
the
project
has
been
extended
for
a
little
bit
extended
a
few
weeks
for
a
few
weeks
for
Bundy's
benefit.
He
was
able
to
continue
the
additional
work
and
moving
forward.
C
Yeah
I've
seen
that
lady
has
been
struggling
with
Gatsby
I
think
but
Gavin
Morgan
came
to
the
rescue
and
I
think
they
will
solve
the
issue.
A
Good
all
right
anything
else
on
Google
summer
of
code.
No
thank
you!
Okay.
So
we
have
an
open
one
on
how
to
describe
the
process
of
choosing
a
plug-in
bill
of
materials.
Version.
I've
made
no
progress
this
week.
As
a
reminder,
the
the
question
was
raised
by
a
Jenkins
contributor
from
I.
Think
Salesforce,
yes,
Kyle
Leonard,
and
the
question
was:
how
do
I
choose
the
bomb
version
and
there
are
a
number
of
comments
there.
We
discussed
it
in
doc's
office
hours.
Asia
came
to
some
conclusions
and
now
it
just
needs
to
be
implemented.
A
A
We
could
static
reference,
older
versions,
in
addition
to
the
most
recent
release.
Etc
and
a
blog
post,
was
a
suggestion
that
we
had
yeah
and
now
on
the
Java
next
topic:
Java
11,
Java,
17
and
Java
21,
there's
more
work
needed
there
and
that
work
continues.
I've
got
it
scribbled
on
my
whiteboard
behind
me,
but
haven't
yet
turned
it
into
something.
I
can
discuss
with
the
Jenkins
Community.
We've
got
interesting
challenges,
hiding
there
more
more
happening,
hopefully
later
this
week,.
C
Mark
the
first
time
you
explained
that
in
that
I
listened
I
thought
it
was
PT's
straightforward,
but
then
you
discovered
some
hidden
things.
B
A
Definitely
not
straightforward,
and
so,
if
there's
that's
why
the
diagrams
are
are
I.
Think
so
crucial
here
is
to
show
look,
here's
what
we've
done
in
the
past.
Here's
what
we're
doing
what
we
think
we
should
do
now
and
here's
where
I
think
we
should
go
in
the
in
the
future
say
two
years
from
now,
and
each
of
those
is
a
step
on
this
progression
process,
so
I'll
I'll
get
those
together
and
start
sharing
them.
A
Thank
you
for
that.
Next
topic
was.
We
had
had
a
discussion
with
Kevin
about
possibly
embedding
the
so
we've
got
a
document
here
when
we
look
at
installing
Jenkins
and
we
look
on
Linux.
For
instance,
there's
a
section
here
called
software
requirements
and
it
links
to
separate
pages
related
to
Java
requirements
to
web
browser
compatibility
to
Windows
support
policy,
Linux
all
all
very
useful
things,
but
only
available
through
links
embedded
inside
these
Pages.
It's
never
visible
over
here.
On
the
left
hand,
navigation
contents
and
Kevin
Kevin
observed
really.
A
A
C
A
C
C
B
C
But
that's
an
important
thing:
yeah
yeah,
that's
something
interesting
and
that
may
we
may
discover
it
on
that.
Some
other
things
are
missing
right,
but
we
have
to
yeah.
We
have
to
start
somewhere,
that's
cool
thanks.
A
C
Else
for
today
it's
for
today,
but
it
for
tomorrow,
I
think
you
will
see
ashutosh
tomorrow
in
the
Asia
docs
office
hours.
Oh.