►
From YouTube: 2023 08 25 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
everyone:
it's
the
25th
of
August.
This
is
documentation,
office
hours,
Asia
topics
on
my
list,
Google
summer
of
code,
choosing
a
plug-in,
Billet
materials
version.
Add
the
existing
requirements
and
support
policy
to
a
new
chapter.
I
can
show
you
a
prototype
of
that
and
then
veil.sh
a
command
line
for
making
suggestions
on
text
and
devops
World
Tour.
A
A
Right
and
the
project
is
the
Docker
compose
project.
C
A
Great
okay
and
then
the
others
get
lab
plugin
modernization
that
is
not
as
directly
if
directly
related
to
documentation
and
the
fourth
was
or
is.
C
A
C
I
think
it's
like
we,
oh
we're,
still
working
out
the
details
for
the
Gatsby
blog
for
the
new
layout
or
alternative
building
tool
project
so
that
that
was
like
just
like
my
idea
is
to
have
like
the
process
automated
and
stuff
like
having
to
use
them
the
strappy,
because
they
were
going
to
use
like
all
on
gathers
organization
of
Gatsby,
Dodger,
guys
and
also
strappy
as
a
back
end
before
restoring
the
data.
But
normally
it's
like
that.
They
have
this
platform
or
portal
for
strappy.
You
have
to
use.
It's
called.
C
It's
called
again
that
means
dashboard,
but
the
thing
is
that
I
want
to
retain
the
current
flow
of
like
processing
blog
posts,
but
I'm
not
sure
if
they're
sustainable.
C
It
does,
but
it
wouldn't
be
going
to
like
the
current
like
it
would
be
very
different
from
the
way
we're
doing
it
now.
Some
people
can
do
it
like
not.
Everyone
can
do
it.
A
C
A
C
And
also
it's
like
it
has
to
be
done
to
read
the
portal,
so
it's
like
or
dashboard
says
it's
kind
of
hot
harder
to
have
that
arrange
that
way,
but
we
can
we
can
make
it
work
somehow
to
to
have
the
existing
process
preserved,
but
that
would
take
some
work
to
integrate
like
the
whole
setup
with
GitHub.
A
Okay,
so
they've
got
they've,
got
a
front.
They've
got
some
form
of
front-end
integrated
to
their
back
end.
That
is
not
a
GitHub
pull
request.
Yeah.
Okay,
all
right.
C
Pull
requests
yeah
some
some
of
them.
It's
like
in
I
think
sometimes
it's
in
until
why
some
other
than
Gatsby,
oh
okay,
they
should
be
they
should
there
wouldn't
be
a
part
of
the
blog.
So
it's
like
I
think.
Hopefully
we
can
set
up
so
so
I'm
going
to
block
this
to
be
that
way,
but
maybe
the
like
anything
done
with
gas
me
to
so
I'm,
not
sure,
and
they
figure
out.
C
Also,
like
there's
still
a
lot
of
work
to
to
transition
to
the
new
workflow
and
new
tooling,
but
we
have
to
figure
out
the
logistics
of
things.
Oh
wow.
They
didn't
see
him
right.
A
A
C
A
A
A
C
A
Okay,
so
I
guess
I
can
give
you
some
status
of
what
I
know
about
the
the
docker
compose
project
the
it
needs
it
needs
one
or
more
new
Docker
new
Docker
repositories.
A
And
the
infra
team
can't
take
on
can't
do
those
docker
repositories.
Currently
they
just
they're
they've
got
too
many
urgent
things
that
have
got
to
happen
instead,
so
we
could
do.
We
could
create
a
prototype
that
uses
ashitosha's
or
Bruno's
personal
repository
personal
containers
for
now
not
published
to
the
Jenkins
site.
We
just
we
should
not
publish
something
to
the
Jenkins
site.
That
depends
on
a
private
repository.
That's
that's
a
personal
repository.
That's
a
mistake!
Yeah.
C
B
A
C
A
Oh,
that
would
be
great
is,
do
you
think
harsh
is
interested
in
being
a
co-maintainer.
A
C
A
That
that
sounds
good
to
me.
If,
if
I
would
love
to
have
harsh
harsh
remain
somehow
connected
to
the
Jenkins
project,
but
I
I
agree
with
you
that
education
is
his
first
priority.
It's
most
important
that
he
finished
that
University
education
successfully,
but
I'm
fully
supported
if
you'd
like
to
continue
to
be
involved.
Yeah.
A
A
So
this
is
from
K
Leonard,
first
name,
I
think
is
yes
Kyle
from
Kyle
Leonard,
so
Kyle
is
a
plug-in
maintainer.
So
that's
the
Persona
we're
dealing
with
Kyle
likes
to
use
the
Jenkins
plug-in
bill
of
materials
and
the
plug-in
biller
materials
is
a
great
choice
because
it
allows
you
to
avoid
declaring
explicitly
which
versions
of
plugins
are
in
your
dependency
list.
Instead,
you
just
declare
I
depend
on
this
plug-in
and
you
rely
on
the
plug-in
bill
of
materials.
This
thing
to
provide
the
version
number
so
Chris
I
know
you
already
know
this.
A
This
is
mostly
for
Meg's
benefit
all
right,
so
so
that
I
appreciate
it.
This
is
the
the
thing
that
they
insert
this
little
block
of
text
into
their
plug-in
pom
file,
but
Kyle
correctly
asked:
what's
the
value
that
I
put
here,
the
Ellipsis
there
tells
us
it's
not
a
known
thing,
Kyle
said
well,
which
one
is
it
and
why
would
I
choose
that
one,
and
so
here's,
here's
the
it's
okay,
what
version
and
should
I
just
go
here
and
select
the
latest
without
caring
about
what
version
of
Jenkins
I
put
here.
A
Because
this
number
2.387.x
is
derived
from
a
Jenkins
LTS
Baseline
right,
so
it
can
be
either
2.361
or
2.387
or
2.332
or
2.401
or
2.415
and
and
which
version
you
choose
there.
Does
that
somehow
have
a
relationship
to
this
version
number,
and
the
answer
is
yes,
it
does
okay.
So
any
questions
on
the
setup
to
the
to
the
problem
statement.
A
for
361,
the
newest
version
is
2102.
That's
when
we
stopped
updating
that
one
375.
The
newest
version
is
21.98
Method
dot,
whatever
now
387
and
401
the
newest
version.
This
is
actually
no
longer
the
newest
version,
because
this
one
is
still
being
updated
and
the
newest
version
number
is
a
larger
number
than
that.
B
C
A
When
I
wrote
this
comment
two
weeks
ago
at
that
moment
in
time,
this
was
the
latest
version.
Now,
however,
if
I
instead
look
at
the
latest
version,
let's
go
look
at
it
just
to
to
show
proof
that
in
fact,
the
the
newest
version
is
2357,
not
2312.,
so
there
have
been
45
changes
since
the
point
when
I
took
this
I
answered
this
question
two
weeks
ago,
so
this
number
just
keeps
increasing
on
lines
of
the
bill
of
materials
that
are
actively
being
updated.
C
A
Right
so
then,
now,
okay,
now
this
is
where
it's
it's
a
challenge
right,
because
we've
got
some
lines
where
we
can
give
the
answer
with
confidence.
It
will
never
change
right
this
line,
if
you,
if
you
chose
346,
that's
the
correct
version,
no
need
to
update
it,
no
need
to
revise
it
in
any
way.
If
you
choose
361,
this
is
the
correct
version.
It
will
never
change,
because
we've
stopped
updating
that
version
this
one.
A
It
changes
at
least
once
a
week,
because
we
released
a
new
version
of
the
bill
of
materials
pretty
much
once
a
week,
so
my
thought
was
okay.
We
could-
and
this
was
what
I
had
put
in
the
we
could
put
into
the
documentation
of
this
Repository
into
its
readme.
Here.
It
talks
about
usage
right.
We
could
extend
this
thing
by
saying
giving
examples
for
each
of
those
versions:
387..
Here's
a
specific
example
361.,
here's
another
specific
example,
346
and
notice
that
I
named
these,
because
they
have
certain
significance
right.
A
A
A
So
it's
called
choosing
a
Jenkins
version
to
build
against,
and
here
this
is
where
Jesse,
Glick
and
Daniel
Beck
and
others
have
helped
us
formulate
guidelines
to
choose
what
should
be
your
Jenkins
Baseline.
And
when
you
choose
your
Jenkins
Baseline,
that's
the
same
version.
You
should
choose
for
the
bill
of
materials.
A
Now,
how
do
we
do
the
descriptions
and
where
all
right,
so
my
thought
was
the
easy
one
is
put
them
in
the
readme
in
this
files
readme
and
put
specific
examples
with
the
option
to
write
some
update
CLI
code
to
automatically
insert
the
version
number
here
shortly
after
a
release,
and
then
it
would
truly
be
as
a
plug-in,
developer,
I
just
copy
and
paste
this
section
and
paste
it
into
my
code,
no
need
to
teach
people
anything
just
say
copy.
This.
A
And
for
me,
that's
a
that's
a
an
attractive
option.
I
suspect
the
coding
to
do
that
may
be
more
complicated
unless
we
do
something
like
split
split
it
out
to
a
separate
file,
swear
okay,
there's
a
file
for
three
for
the
last
last
Java
version.
There's
another
file,
and
each
of
them
is
a
different
readme
at
the
top
level
here,
because
there'd
be
a
readme
yeah.
Whatever
that
way,
then
update
CLI
only
sees
one
version
tag
and
only
has
to
process.
One
version
tag
that
I
need
to
talk
to
Bruno
about.
B
B
A
No,
that
you're
not
being
pedantic
at
all,
but
that
is
much
more
verbiage
than
needs
to
than
the
the
expressing
the
concepts
you're
trying
to
express
needs
to
happen
in
this
page.
Okay,
because
this
page
describes
the
many
different
Alternatives
that
might
cause
you
to
choose
one
Jenkins
version
or
another
as
your
minimum
Baseline.
So
so
this
thing
is
giving
you
the
what
I'd
call
the
engineering
compromises
between
should
I
choose
a
newer
version
should
I
choose
an
older
version?
What's
the
impact
if
I
choose
a
newer
version?
A
B
A
A
C
B
A
This
was
released
right,
so
this
is
this
is
relatively
recent,
but
not
not
brand,
not
the
newest,
so
so
it
I'm
using
2.387.3.
That's
my
my
dependency
I
say
you
must
have
at
least
that
that's
the
oldest,
that
I
will
ever
test
with
or
support
you
on
now.
Some
change
happens
in
Jenkins,
2.414.1
and
I
decide.
I
want
to
consume
that
change.
I
want
to
be
able
to
use
that
change.
Then
I
will
increment.
This
version
number
to
2.414.1
and
I
then
have
to
change
this
to
2.414.x.
A
B
A
A
A
A
A
There
we
go
okay
and
New
Branch.
So
let's
call
this
link
to
to.
A
A
A
A
A
A
B
A
Okay
and
I
can
do
that
separately.
We
don't
need
to
do
that
during
this
session.
Then
then,
Joseph
Peterson
asked
the
question
hey
shouldn't.
We
also
have
something
about
choosing
the
bomb
version
in
this
page
and
the
more
I
thought
about
it.
I
thought
probably
not,
but
we
ought
to
have
a
link
from
here
to
the
to
the
bomb
instructions.
Then
the
question
is
which
bomb
instruction
should
we
take
them
to,
because
the
precisely
detailed
bomb
instructions
are
here
in
the
in
the
bomb
readme?
A
These
are
the
most
accurate,
the
most
precise,
the
best
engineering
description.
There's,
an
alternative
which
is
here
in
the
in
the
tutorial
for
developers
in
the
developer
guide,
improve
a
plug-in
there's
this
thing
with
a
video
that
talks
about
use
the
plug-in
bill
of
materials,
but
it
is
not
nearly
as
detailed
as
and
in
this
case
at
the
moment,
it's
actually
wrong
right.
It's
this
thing
is
manually
maintained
and
needs
to
be
upgraded
from
2.375
to
2.387.3
and
needs
to
have
a
new
version
number
here.
B
Would
why
not
both
you
know
for,
for
the
full
explanation,
go
to
the
readme
file?
If
this
is
your
first
time,
if
you're
just
getting
started
here
and
want
a
tutorial
go
here,.
B
A
B
A
A
A
And
to
the
documentation
in
this
Repository,
my
fat
fingers
in
F10.
A
C
A
Okay,
so
next
topic
is,
we
had
talked
last
week
or
several
weeks
ago
about
a
concept
of
adding
the
existing
requirements
and
support
policy
documentation
to
a
new
chapter
of
the
user
handbook
so
for
reminders
sake:
here's
the
user
handbook.
It
looks
like
this,
so
it's
got
installing
using
managing
system,
admins
scaling
and
troubleshooting,
but
in
addition
to
all
those
things
hiding
under
installing
here,
the
Linux
page
has
links
to
Java
requirements.
A
A
So
the
idea
that
we
had
discussed
several
weeks
ago
was,
let's
put
create
a
new
chapter
and
the
I
the
where
the
the
Prototype
has
put.
It
is
right
after
troubleshooting,
Jenkins,
called
platform
information
and
what
I
wanted
to
do
was
show
that
to
you.
So
you
can
see
how
it's
going,
and
we
talked
further
about
structure
you.
Okay,
with
that.
A
A
Okay.
So
let's
go
to
the
user
guide,
and
here
we
see
already
now
there's
platform,
information,
yay,
okay,
so
so
first
Victory
now,
let's
jump
into
it
a
little
deeper
by
going
to
various
places,
let's
go
to
any
one
of
them
and
it
stays
there.
So
it
travels
up
and
down
as
we'd
hope.
So
here's
the
platform,
information,
section,
foreign
S,
one
called
Java
and
Java-
has
three
pages
in
it.
Right
now,
Java
requirements
Java
8
to
11
Java
11
to
17.
It
will
have
a
fourth
upgrade
Java
from
17
to
21.
A
A
B
A
They
are
effectively
subsections
yeah,
oh
yeah,
that's
good
Chris's
experience
with
the
the
new
new
thing.
You
know
this
very
good
okay,
so
so
the
thought
was
with
Java.
We've
also
got
subsections
and
now
the
the
navigation.
There
is
a
little
surprising
for
me
in
that
it
expanded
both
when
I
clicked
on
one
of
them.
C
It
could
be
me
so
I
may
be
able
to
fix
it,
but
can
I
take
a
look
at
the
pl.
A
C
C
C
A
Look
if
I
remember
it
is
nope.
Docs
hang
on
I've
got
to
go
navigating
now:
content,
okay,
doc.
C
A
I'm
going
to
use
this
as
my
excuse
to
ask
a
different
question,
then
what
if
we
attempted
to
flatten
this
into
a
single
list
rather
than
Java
and
support
policies?
What
if
it
was
everything
at
the
top
level,
Java
requirements,
upgrading
8
to
11
11
to
17
17
to
21,
Linux
support
policy
and
platform
information
only
had
things
one
level,
one
one
level
down
in
it.
What
would
the
two
of
you
think
in
terms
of
how
does
that
feel
structurally.
A
Are
four
items
right?
Those
there
are
four
items
and
those
items
I
don't
expect
to
add
many
more
to
them,
because
this
thing
it's
very
slow
for
us
to
add
something
to
it.
We
added
we
started
with
a
Windows
support
policy.
Some
years
ago,
I
knock
I
caved
and
did
the
Linux
support
policy.
We
realized
we
needed
browser
and
servlet
container
and
that's
sort
of
reached
the
limit,
and
here
Java
requirements.
We
get
general
purpose
Java
and
then
upgrade
for
each
transition.
So
8
to
11
is
1.
A
B
B
But
what
I
can
see
is
because
I
do
like
what
you're
saying
if
it
started
to
get
too
long
long,
it
could
be
a
hybrid,
so
we
could
have
like
Java
upgrades
right.
A
There
is
there
is,
there
is.
Certainly
there
is
an
excuse
that
would
say
hey.
We
could
do
nesting,
but
as
I
look
at
Kevin's
prototype
here,
I
wonder:
should
we
even
bother
with
nesting?
Let's
do
what,
if
we
just
remove
support
policies
and
instead
put
these
four
items
at
the
at
the
immediate
level
below
platform
information.
C
A
Yeah,
that
okay
good,
so
so
that
was
you
you
sort
of
expressed
my
concern
as
well
is
the
nesting
here,
particularly
when,
when
they
the
two
of
them,
expand
at
the
same
time
it
it
doesn't
do
the
information
hiding
that
I
might
have
been
hoping
for
right.
So
the
the
current
expand
and
contract
Behavior
I
would
have
thought.
Oh
support
policies.
I
only
want
to
look
at
support
policies,
but
it's
expanding
more
than
that.
A
Right
right
it
this,
the
Java
requirements,
could
could
easily
be
rephrased
as
Java
support
policy
and
then
they're
all
support
policies,
and
maybe
it's.
If
we're
looking
to
the
Future,
then
we
say
in
a
future
day:
it
might
be
support,
policies
and
upgrades
and
but
then
then
again,
if
it's
upgrade
I
might
want
to,
we
might
want
a
chapter.
Upgrading
Jenkins,
just
like
we've
got
a
chapter
installing
Jenkins
yeah,
okay,
so
I
think
what
I'm
hearing
from
the
two
of
you
is
you'd,
be
okay,
if
this
were
flattened.
Yes,.
C
A
Right
well,
and
that
would
that
would
be
more
more
akin
to
what
this
thing
is
doing,
where
we've
got.
One
very
special
case,
reverse
proxy
configuration,
and
it
really
is
a
very
special
case
right.
These
are
specializations
where
you
choose
only
one
of
them
as
a
user.
You
don't
pick
you
don't
say.
Oh
I'm,
gonna
do
two
different,
reverse
proxies.
Now
you
you
choose
one
and
you
stick
with
that
exact
one
right.
A
Right
this
in
terms
of
simple
policies,
you
probably
have
Linux
and
windows.
You
certainly
care
about
browser
compatibility.
So
three
of
these
items
under
support
policies
plus
Java
requirements.
You
care
about
four
of
the
five
for
sure.
Now,
servlets.
We
hope
you,
you
just
use
the
server
that
we
provide,
but
the
other
other
things
really
choosing
a
Linux
version
is
a
big
deal.
Choosing
a
Windows
version
is
a
big
deal.
B
A
B
B
When
I
say,
if
I
see
a
list
that
has
Linux
and
windows,
isn't
the
next
thing
I
have
a
moment
we're
saying:
oh,
they
don't
support
Windows
yeah.
For
me,
it's
usually
the
other
way
around.
It's
like
Windows,
there's
no
Linux
there.
It's
like
yeah,
but
you
know,
but
that
because
those-
and
if
you
did,
if
we
did
have
to
sub
Nest
I
mean
there
could
come
a
time.
Maybe
we
have
we
pick
up
iOS
or
some.
You
know
right.
A
Yeah
I
guess
I
guess
I
could
see
I,
certainly
Bruno
Marsden,
for
instance,
has
done
experiments
trying
to
run
Jenkins
on
Android
as
an
opera
and
running
it
native
on
Android.
Now
that
that
experiment's
kind
of
a
dark
kind
of
experiment
right
because
I'm
not
especially
interested
in
running
directly
on
that
any
more
than
I'm
interested
in
running
directly
on
other,
more
exotic
things
like
assistant.
B
390
VM
system
but
I,
see
but
I
see
the
future.
These
you
know
because
I
kind
of
don't
do
as
much
on
my
cell
phone
as
lots
of
people
do
I
hate
my
computers
and
I.
Do
things
on
the
cell
phone
and
I
think
that's
gonna
have
to
wait
till
I'm
in
front
of
a
real
computer,
but
people
are
doing
everything
on
them,
so
it
could
happen.
It.
A
C
And
also
that
I
have
something
to
raise
so
since,
like
we
are
like
migrating
to
us
from
a
building
website
so
like
maybe
by
the
time
we
need
to
upgrade
if
we're
using
a
toy,
it's
a
lot
easier.
C
And
I
also
found
the
culpit
for
the
code
like
why
it's
not
working
because
right,
oh
you
did
on
the
chat,
yeah.
A
A
A
A
B
A
C
A
So
feel
free
to
use
weave,
instead
of
we
have
avoid
using
will
so.
B
A
B
It
seemed
from
what
I
know
and
I
am
not
a
style
guide.
Expert
except
I've
become
extraordinarily
good
at
avoiding
exercises
and
creating
a
new
style
guide.
I've
done
that
just
enough
to
they
don't
want
to
do
it
again,
but
there's
a
lot
of
people
who
seem
to
believe
in
that
it's
the
Microsoft
style
guide
that
was
handled
down
at
Mount
Sinai,
I
kind
of
like
the
Google
better.
A
B
But
they're
because
a
lot
I
mean
a
lot
of
it
is
just
good
sense.
The
big
one
that
I
look
for
is
header
capitalization,.
B
I,
don't
care
to
ever
participate
in
another
discussion,
I
have
sort
of
what
I
prefer
I
can
live
with
any
of
it.
Whoever
feels
strongest,
you
win,
I'm
done
right,
but
but
what
I
do
hate
and
I
do
this?
All
the
time
is
create
a
document
that
has
a
mix
but
because
we
I'm
not
working
under
a
style
guide
that
specifies
it
so
some
days,
I
do
one
thing
some
days:
I
do
another
thing:
Someday
I'm,
reviewing
somebody's
text
and
I
make
them
change
it
other
days,
I
say
let
it
go
right.
A
Cool
all
right,
that's
all
that
I
had
I
have
to
forewarn.
There
will
be
some
time
since
September
and
October,
where
I'm
unavailable,
because
I'm
a
speaker
at
devops
world
tour
in
New,
York,
Chicago
and
Santa
Clara,
Oh
yay,
and
if
you're
in
the
Santa
Clara
area,
sometime
mag
I
may
send
ping
you
and
say:
hey
I'm
in
town,
I.
B
A
A
B
Before
you
hang
up,
I
have
a
very
quick
question
for
you.
Yes,.
A
B
A
So
so
I'd
worry,
it
depends
on
depends
on
how
often
you're
willing
to
upgrade
so
22.10
has
I
think
a
six
month,
life
cycle,
or
maybe
it's
a
12
month.
Life
cycle
and
2204
has
a
10-year
life
cycle.
C
B
A
B
A
B
B
A
Very
good
yeah
I'm,
actually
Mark's
got
some
really
hot
topics
about
this
thing:
Java
11,
17
and
21
discussion
that
yeah
we've
got
a
some
very
interesting
conversations
about
the
next
three
to
four
years,
how
they
will
look
for
Java
support
in
Jenkins.