►
From YouTube: 2023 08 11 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
Sorry
about
that,
for
the
brief
the
brief
loss
of
consciousness,
there
I
think
it'll
come
back
eventually
great
all
right.
Thanks
topics,
I've
got
Google
summer
of
code,
upcoming,
LTS,
a
question
and
a
document
structure
topic
for
discussion
in
terms
of
how
should
we
structure
this
particular
section?
This
is
one
that
raised
by
Kevin
and
how
to
describe
the
process
of
choosing
a
plug-in
bill
of
materials.
A
C
So
I
I
wanted
to
discuss
about
how
the
how
eventually
will
work
for
documentation
to
update.
A
B
A
A
C
Yes,
right
now
we
are
using
my
personal
Dr
web
repository
purpose.
A
A
C
Yes,
we
have
also
created
a
data
action
files
for
Whenever.
There
are
changes
to
the
talk
of
Docker
files.
It
automatically
creates
and
updates
the
images.
A
B
A
A
C
Yes,
so
I
wanted
to
ask
the
questions
about
how
exactly
should
I
create
the
pull
request.
Like
should
I
create
one
pick,
pull
request
containing
everything
or
should
I
separate
it
out
in
small
batches.
A
A
B
A
B
A
C
One
of
the
tutorials
contains
like
highly
depends
on
the
blue
ocean
plugin,
and
we
we
were
thinking
that
we
will
avoid
using
blue
ocean
plugins,
since
it's
not
being
updated.
C
So
if
you're
thinking,
if
we
should
update
that
that
tutorial
or
not.
A
Yeah
and
well,
while
I
did
the
previous
so
so
my
view
is
even
though
blue
ocean
is
not
actively
developed.
I'd
rather
not
sacrifice,
rather
not
sacrifice
the
tutorial
due
to
Blue
oceans,
less
active
development,
not
yeah,
because
we
expect
them
to
discard
these
container
images
anyway.
No
reason
to
hide
to
to
not
include
blue
ocean
in
the
so
now,
let's
ask
Meg
and
Chris
I
think
the
blue,
the
tutorials
should
include
blue
ocean
and
that
you
should
update
this
one
so
that
we
get
rid
of
Docker
and
Docker
completely.
A
D
D
A
B
The
thing
I
like
is
there's
a
bunch
of
just
tedious
crap.
You
have
to
do
to
get
where
any
you
can
make
anything
happen
and
with
blue
ocean
that
becomes
very
easy
and
you
can
see
what
Jenkins
says
and
I
think
you
pretty
quickly
see.
The
blue
ocean
is
pretty
cumbersome
if
you
want
to
use
it
for
production,
but
right.
A
D
C
Also
thinking
of
including
blue
ocean
and
because
I,
when
I
first
used
Jenkins
I,
the
first
tutorial
I
saw,
was
with
bluish
and
so
yeah.
A
D
And
also,
and
maybe
in
our
demonstration
to
dogs
office
hours-
oh,
oh
good,
okay,
Friday!
So
it's
like
August
18th,
oh.
A
D
I
think
I
think
today
is
the
first
meeting
after
this
exam
that
we're
going
to
talk
about
like
how
to
fix
turn
to
our
site,
because.
A
D
Are
some
issues
with
stone,
but
tomorrow's
meeting
will
carry
on
and
we'll
talk
about
like
how
to
proceed
with
a
block
feature.
A
All
right
thanks,
Chris,
thanks
very
much
for
your
leadership
there
so
on
gitbab,
plug-in
modernization.
Next
meeting
on
that
one
is
in
about
12
hours
and
Mark's.
Testing
still
has
some
questions,
I
just
posted
them,
but
the
code
code
is
working
right.
So
that's
good,
yeah,
two
and-
and
it
looks
up-
looks
positive.
Okay,.
D
D
A
A
A
Okay,
so
now
we've
got
a
structural
question
and
this
one
is
a
Meg
and
Chris
in
particular,
with
your
experience
on
documentation
structure.
This
is
for
for
your
your
consideration,
so
we
have
on
the
Jenkins
documentation
site
a
number
of
documents
that
are
not
directly
linked
into
the
left
side,
navigation.
So,
for
instance,
if
we
look
at
Linux-
and
we
look
at
the
prerequisites
document
here-
you'll
see
at
the
in
the
section
called
prerequisites-
there
are
links
to
Hardware
recommendations,
links
to
software
requirements
and
these
are
useful
and
valuable
policy
documents
right.
A
A
A
Oh
yeah,
so
that's
my
search
Marsh.
My
search
tools
are
my
search.
Skills
are
weak
apparently,
but
the
answer
there
is
this
upgrade
Java
guidelines
and
Java
to
17
is
not
LinkedIn
anywhere
linked
into
the
documentation,
navigation
anywhere,
and
what
Kevin
was
asking
is:
should
we
consider
putting
in
a
section
that
might
be
called
support
policy
underneath
system
administration,
so
in
system
administration
we
have
right
now
us
an
expanding
subsection
called
reverse
proxy
configuration.
A
D
A
A
A
B
D
B
This
is
something
that
that
that
an
advanced
experienced
person
might
need
to
go
to
regularly.
A
Then,
okay,
so
I
I,
confess
platform.
References
would
be
fine
with
me
as
well
platform
reference.
B
That
works
that
works
to
you,
I
could
dance
to
that.
Okay,.
A
So
if
the
idea
then,
would
be
in
the
system,
administration,
section
and
Meg
what
you
said
resonated
with
Kevin
as
well
was
when
I'm
doing
the
install
it's
a
natural
thing
to
read
the
prerequisites
right.
But
when
I'm
after
I've
done
the
install,
it
is
not
natural
to
come
back
here
and
look
at
the
prerequisites
again
right
right
when
I'm
in
system
administration
mode,
it's
natural
to
look
in
the
system,
admin
section
and
the
fact
that
there
isn't
a
platform
information
section
here.
B
B
A
Right
right,
well
and-
and
it
it
fits
this-
is
sort
of
these
are
the
kinds
of
things
that
are
discussed
in
the
platform
special
interest
group.
They
really
are.
Shall
we
shall
we
support
web
browser
XYZ?
Shall
we
support
Windows
version
this
or
that
shall
we
support
this
or
that
Linux
version
and
and
those
those
are
very
much
platform
sigthing
so
using
the
word
platform
feels
really
good
to
me.
Yeah.
A
So
here
I'm
going
to
open
it
and
let's
look
at
it
and
talk
about
it
because
I
want
some
coaching.
The
submitter
on
this
gave
some
good
ideas,
but
but
the
real
challenge
here
is
we're
I'm
trying
to
describe
something
to
a
developer.
A
That
is,
at
least
for
me
in
describing
rather
complicated,
okay,
so
here's
the
story
how
it
goes.
Jenkins,
plugins,
have
versions
right
and
their
versions
have
different
capabilities.
Usually
it's
that
a
new
version
gets
more
capabilities
than
an
old
version
did,
but
versions
are
right
versions,
change
and
those
versions.
A
One
of
the
complications
for
a
plug-in
maintainer
is
that
when
I'm
writing
automated
tests
that
depend
on
other
plugins
I
must
explicitly
list
the
version
number
of
those
other
plugins
and
that
becomes
nightmarish
to
manage,
because
I
have
to
find
the
set
of
plug-in
versions
that
all
work
together.
So
we
have
this
thing
called
a
plug-in
bill
of
materials
that
avoids
that
problem
by
generating
a
set
of
plugins
that
are
known
to
work
together.
B
B
A
So
you've
you
go,
oh
go
ahead!
Question,
oh
yeah,
I
love
it.
This
is
and
in
fact
we
use
it
in
the
gitlab
plugin.
We
use
it
in
many
many
plugins
and
are
very,
very
happy
with
it.
It
works
very
well,
however,
this
this
quite
the
question
came
from
this
person
saying:
what's
the
value
that
I
put
here
because
notice,
the
Ellipsis
there
is
admitting
not
clear
what
value
you
should
put
there.
A
A
And
another
and
and
you'll
notice,
the
release
number
is
not
some
immediately
obvious
number:
it's
complicated,
long
string
of
bits,
and
last
week
there
was
a
release
and
the
week
before
that
there
was
release
and
the
week
before
that.
So
so,
however,
these
releases
are
tied
specifically
to
a
subset
of
the
total
available
versions
and
that's
where
the
explanation
gets
complicated.
A
A
A
A
The
last
version
was
this
and
then
releases
on
that
line
stopped
while
releases
on
361
continued
until
this
point
and
then
375
until
this
point
and
now
387
is
active
and
the
2312
that's
listed
here
is
actually
already
out
of
date.
It's
now
23.29
.,
okay,
so
the
complication
here
is
how
to
describe
how
they
choose
the
version,
and
now
one
idea
is
tell
them
to
use
the
pendabot
and
let
it
do
the
work
for
them
and
I
really
like
that
version
that
that
choice,
because
that
helps
them
get
an
updated
regularly
anyway.
A
Well
and
and
part
of
the
problem
here
is
I.
I
found
this
quite
a
complicated
topic,
as
I
was
learning
it
myself
right
and
I'm,
not
sure
that
I'm
explaining
it
clearly
and
effectively,
even
now
and
I,
feel
like
I
I
grasped
the
concept
very
well,
but
it
might
be
well
suited
to
have
diagrams
or
something
you
know
how.
Sometimes
we
have
stacked
bars
where
there's
a
a
release.
A
Life
cycle,
Ubuntu
18
lives
for
this
long
and
then
the
next
step
is
20
and
then
22
and
these
lines
are
sort
of
like
that
in
that
they
reach
a
point
where
we
stop
doing
any
additional
releases
on
that
line,
and
so
maybe
a
picture
like
that
might
help
people
visualize.
Oh
that's
what
happens
this.
This
one
is
hot.
It's
the
changing
one.
These
others
have
become
immutable.
They
won't
won't
change
any
further.
A
A
A
A
A
They
do
well
and,
and
now
it's
it's-
that's
that's
accurate
as
far
as
it
goes.
So
if
you
look
at
414,
it
has
three
versions
in
it
because
it
didn't
exist
prior
to
this
2278
release.
If
we
look
at
401
you'll,
see,
2278
was
preceded
by
by
Manny,
but
414
didn't
exist
yet
so
when
414
came
into
existence,
this
is
when
it
came
into
existence.
So
so
the
authoritative
place
to
find
these
releases
is
in
this
directory
structure.
A
So
part
of
me
is
tempted
to
just
tell
people
go,
go
navigate
to
this
location
and
read
it
it'll.
Tell
you
what
what
the
the
latest
version
is,
the
other
the
other
technique
I
use,
but
it
it
requires.
Some
some
reading
is
I'll,
go
to
this
site
and
look
at
the
releases,
but
I
have
a
personal
bias
towards
only
supporting
my
plugins
on
hot
versions.
Right
I
plug-ins
that
that
aren't
on
hot
versions
are
not
not
as
interesting
to
me.
So
I
tend
to
base
either
on
387
or
something
newer
than
that.
A
All
right
so
coaching
comments.
What
do
you
think
what's
in
is?
Is
there
a
some
recommendation
on
ways
that
you
think
would
make
it
easier
to
understand
how
to
make
those
choices.
B
A
D
A
Got
a
page
that
guides
them
about:
how
do
you
make
the
compromise
be
between
this
minimum
Jenkins
version
or
that
minimum
Jenkins
version,
and-
and
this
should
probably
link
to
that
to
to
remind
them
choosing
this
thing
is
in
fact
choosing
a
Jenkins
minimum
version.
Also
it
you
should
keep
them
together.
They
should
be
kept
in
lockstep.
B
Yeah,
you
know
I
think
the
way
I
mean
so
you're
not
going
to
cookbook
it,
but
it's
a
general
thing
that
you
could
use
the
way
you
explained
it
I
mean
written
up
is
pretty
good.
It's
a
soft
thing.
You
know
start
with
the
most
current
version.
Try
it
and
see
what
happens.
Do
some
testing
for
bonus
points
use
Robo
got
to
to.
B
B
That's
really
really
hard
to
choose
to
tell
somebody
else,
but
you
let
them
sort
of
watch
how
you
would
do
that
and
maybe
even
take
an
example
of
one-
and
you
say
you
know:
I
did
this,
and
here
was
the
problem
I
found
and
so
by
looking
here
and
here
and
here
I
figured
out
that
this
was
the
cause
of
the
problem
and
so
I
changed.
Okay,.
A
A
We
could
put
another
subsection
here
that
says
earlier
Jenkins
versions
and
then
list
2.361
and
say
this
is
the
first
version
to
support
Java
11.
2.346.
This
is
the
last
version
to
support
Java,
8.
and,
and
that
would
give
then
the
version
in
those
cases
would
be
explicit
and
non-veried
right.
C
A
We
could
we
could
document
that
and
say:
hey
here
is
Java
8
the
final
version,
the
terminal
version
here
is
the
first
version
that
did
Java
11
required
and,
and
this
one
is
the
the
latest
bomb
is
the
preferred
now
another
would
be.
We
could
probably
use
update
CLI
to
script.
This
thing
to
actually
insert
the
explicit
value
there.
A
A
Well,
I'm
I'm
not
going
to
go
there,
but
okay,
that's
so
update
the
the
version
string
explicitly
that
the
benefit
of
that
is
then
it
avoids
any
explanation
right.
We
don't
have
to
tell
people
how
to
choose
it.
We
just
say
copy
and
paste
this
text
you're
set.
A
B
B
A
nice
little
I
mean
you,
the
blogs,
I,
don't
know
blogs
are
so
often
you
know
light
things
with
general
purpose,
but
I
still
think
the
story
of
you
working
through
one
or
two
of
them
might
be
very
nice
and
it
wouldn't
need
to
be
updated.
I
mean
when
you
tell
them
what
you
had
to
do
for
Java
11
or
something
they
can
extrapolate
that
when
they're
looking
at
Java
32.
A
Okay,
well
now,
that's
that's
an
interesting
idea,
because
we
might
use
that
as
seed
material
for
hacktoberfest
right,
because
that's
a
good
point.
Certainly
there
are
plenty
of
places
in
the
Jenkins
plugin
in
plug-in
ecosystem,
where
this
is
not
yet
applied
or
where
it's
been
applied,
but
the
the
contents
have
improved
and
the
plugin
did
not
keep
up
so
they've
they're
they're
specifying
things
they
don't
need
to,
and
and
so
it's
yeah
good
good
idea.
Okay,
good.
B
A
good
you
know,
you
know
you're
you're
more
by
the
book
than
he
is,
but
you
know,
but
something
where
it
identifies
it's
a
Persona,
and
these
are
some
you
know:
here's
Uncle
Mark
sitting
down
and
explaining
how
he
does
this
and
and
it
works,
and
you
might
come
up
with
you
know
not
saying
you
know.
This
is
the
way
you
have
to
do.
Whatever
else
you're
going
to
you
know
be
a
turn
to
the
eighth
circle
of
hell
for
life
or
something
but.