►
From YouTube: 2023 02 10 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
So
action
items
Google
summer
of
code,
preparation,
docs,
transition
to
Java,
17
prep
for
Centos,
7,
end
of
life
and
pull
requests
of
note
are
all
possible
topics
for
today
anything
Chris
you
had
added
gstock
preparation,
anything
else
you
want
to
add
no
okay,
then,
let's
go
ahead
with:
let's
go
ahead
with
Google
summer
of
code
preparation
because
there
are
no
action
items
I
like
that.
A
B
It
was,
let's
see
your
which,
which
one
oh
yeah,
this
one
so
many
times,
two
improvements:
okay,
yeah.
Let's
look
at
that.
B
Maybe
it's
like
it's
kind
of
like
I
can
see
a
lot
of
at
these
house.
We
expect
the
outcomes,
but
maybe
for
for
the
opposite
upper
part.
So
if
you
go
back
to
background,
maybe
we
can
beef
it
up
a
bit.
A
A
B
A
B
A
B
B
A
A
A
A
Sure
well,
and
there
is
a
not
just
a
GitHub
repo.
There
is
also
there's
a
project
page
for
it
on
the
Jenkins
site
and
it
might
might
help
people
if
they
would
read
that
to
understand
what
it
had
to
say
right.
So,
let's
take
a
look
at
it.
Let's
look
at
previous
years,
so
here
is
my
page
previous
years,
2019
and.
A
A
A
B
Oh
wait
is
that
extra
space
like
before
image,
okay,
I,
see
something
it's
one
space
or
two
spaces.
A
A
Oh
okay,
this
is
this
is
just
a.
This
is
a
promotional
video
talking
about
her
experience,
no
harm,
but
it's
not
really
about
it's,
not
about
the
project
itself.
It's
more
about
the
her
experience
as
a
what
else
do
we
have
any
others?
Videos,
no
control
contributing
to
Jenkins.
You
too,.
A
B
A
B
A
A
And
precated
actions
need
update.
Oh,
why
that's
GitHub
actions
got
it.
Okay,
new
issues,
so
this,
let's
call
it
documentation
and
a
move
developer.
Instructions
to.
A
What
else
yeah
yeah,
let's
see
so?
Okay,
three
dots
got
it
all
right.
A
Now,
one
of
the
things
we
probably
ought
to
do
is
check
to
see
that
these
issues
are
still
still
open,
because
you
and
I
created
this
list
a
while
ago,
and
some
of
these
may
be
closed,
yeah,
okay,
so
the
first
one
is
still
open.
B
A
A
A
B
A
B
A
B
A
A
It
runs
a
set
of
compatibility
tests
and
a
rather
large
set
of
compatibility
tests
to
check
that
the
plug
these
this
defined
subset
of
plugins
test
together
that
they
pass
their
tests
still
when
they're
all
together
in
the
same
Jenkins
and
and
what
the
suggestion
here
is,
allow
an
option
that
says
I'm
going
to
give
you
a
version
of
the
Jenkins
plugin
bill
of
materials
and
I.
Want
you
to
go.
Get
me
plugins,
based
on
the
versions
in
the
plugin
bill
of
materials.
B
A
C
B
A
Plug-In
singular
yep,
okay,
good,
very
good.
All
right!
Let's
do
that
next,
one
again!
No,
that
is
the
wrong
one.
This
one
we
want
here,
okay,
good
now,
so
we've
talked
about
that
one:
improve
management
of
transient
dependencies.
A
Oh
oh,
okay,
I
see
this
says
this
says:
I'm
I
want
an
option
that
says:
I
must
give
you
every
plugin
I
will
accept
no
plugins
that
are
a
transitive
dependency
and
I.
Didn't
tell
you
the
version
number
when,
if
you
find,
if
I
mentioned,
if
I
said
I've,
given
you
the
full
list
and
and
the
plug-in
installation
manager
finds
no
I
forgot
one,
it
should
just
error
out.
Okay.
C
A
A
They're,
really,
there
are
two
almost
two
things
here:
one
is
allow
a
mode
that
says
fail
if
all
plugins
are
not
resolved
are
not
defined.
All
the
plugins
necessary
are
not
defined
in
my
plugins.text
file
or
my
plugin
Channel
file.
That's
that's.
This
first
part
fail.
If
signal
and
error,
if
a
transitive
dependency
is
not
explicitly
listed,
so
the
git
plugin
depends
on
the
get
client
plugin
if
I
list
the
git
plugin
and
do
not
list
get
client
fail
and
tell
me
failed
because
git
client
plugin
was
missing.
A
A
A
A
A
Usually,
this
type
of
message
is
due
to
a
a
Gateway,
a
let's
see
a
proxy
server
or
other
intermediary
corrupting
the
data.
B
B
A
A
A
C
A
And
I'm
not
sure,
oh
okay,
yeah
I,
think
I
can
see
what
this
would
mean.
It
is
add
an
option
to
do
not
fail
on
error
right,
some
sort
of
a
their
their
options
like
that
to
many
many
programs
where
they
say
well
to
junit
friends
or
to
Maven
that
says:
Don't
Fail
the
process
when
tests
fail
because
Jenkins
will
then
later
decode
will
read
the
test
failures
and
mark
the
job
as
unstable,
rather
than
failed.
Okay,
so
add
a
command
line:
option
to.
A
How
would
we
say
it
even
if
plug-in
download
fails.
B
B
A
Once
again,
I
keep
popping
that
screen
up.
Sorry
Chris
here.
B
A
A
B
A
C
A
B
Hey
I
think
I
saw
like
do.
We
have
like
oh
an
issue
like
that
before
I
get
up
not
sure.
A
B
A
A
Always
tell
which
okay,
this
is
as
far
as
I
know
what
it
does
it
always
down?
Well,
no!
No!
This
is
not
what
it
does.
If
the
plugin
is
already
downloaded,
it
doesn't
download
it
and
I,
don't
think
it
should
so
I
disagree
with
this
assertion.
This
statement
always
download.
No,
if,
if
the,
if
the
pl,
if
the
plugin
already
exists
locally,
don't
download
it
yep
now
for
requested
plugins.
B
B
A
B
A
Yeah
well,
I
think
what
what
the
submitter
is
saying
is,
while
the
plug-in
installation
manager
tool
today
does
not
does
not
handle
does
not
treat
this
case
he's.
The
submitter
is
saying
should
treat
the
case
and
then
offer
either
fail
or
pick
the
greatest
of
the
two
versions:
yeah,
okay
or
dependency
plugins
choose
the
version
using
them.
A
A
B
A
Interesting,
okay
right
so
so
this
says
instead
of
caching
in
the
plugins
directory
cash,
also
in
the
M2
M2
repository
directory
and
and
that's
that's
not
a
bad
idea,
although
I
think
she's
right
that
there
are
complications
there
doing
that
so,
but
that
certainly
would
reduce
bandwidth
requirements
right.
That
would
reduce
the
demand
on
the
servers,
because,
if
you're,
if
you're
a
developer,
you've
already
got
those
things
in
the
M2
cache
all
right
so
use
the
maven.
A
How
about
this
cash
downloaded
plug-in
files
in
the
maven
cash?
A
C
A
B
A
C
A
A
A
C
B
A
C
C
A
A
C
A
C
A
A
B
A
A
Like
right,
okay,
well
and
it,
it
may
be
I'm
not
sure,
given
that
this
had
lots
of
interactions,
yeah.