►
From YouTube: Jenkins Governance Meeting May 15, 2023
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
Budget
and
expenses
Kevin
Martin's
absence
for
a
month
as
documentation
officer
application
to
Ampere
for
arm
Hardware
proposal
to
cancel
the
mag
29
governance
meeting
in
two
weeks
and
Community
activity.
Any
other
topics
that
anyone
wants
to
be
sure
we
add
to
the
agenda.
A
Oh,
oh,
actually,
I
missed
one
in
the
news
section
cdcon!
Oh
it's
already
here
good
cdcon
completed
good.
All
right,
then,
let's
go
ahead.
So
by
way
of
news,
we've
got
a
2.401
release
candidate
scheduled
for
Wednesday,
thanks
very
much
Alexander
for
your
willingness
to
act
as
release
leads
as
the
release
lead.
Thank
you
thank
you
and
thanks
to
Basel
Crow
Basel.
Thank
you.
So
much
for
the
Prototype
JS
work
that
you
and
Tim
Jacob
have
been
doing.
A
The
blog
post
is
live
and
it
guides
people
who
may
not
be
experienced
with
Jenkins
or
who
want
to
learn
more
about
JavaScript.
Hey
here's
a
chance
to
do
it
and
do
it
in
a
way
that
really
helps
the
Jenkins
project.
Thanks
very
much.
We've
got
four
Google
summer
of
code
projects
that
have
started
thanks
in
advance
to
the
mentors
and
to
the
contributors,
and
congratulations
on
the
Jenkins
Awards
to
the
three
Award
winners
to
Jan
farajik,
to
Daniel
Beck,
and
to
me
tomorrow.
We've
got
a
plug-in
security
advisory.
A
Thanks
to
the
Jenkins
security
team,
they
sent
the
announcement
out
forewarning
Jenkins
administrators
that
they'll
be
seeing
some
updates
to
plugins
related
to
security
tomorrow
and
plugins.jenkins.io
now
shows
Health
scores,
so
the
the
scores
are
visible
at
the
bottom
of
each
card.
Telling
you
how
healthy
or
unhealthy
a
particular
plugin
is
guiding
you
on
whether
or
not
you
should
install
it.
A
A
Governance
meeting
archive
sorry,
that's
no
further
progress
on
that.
We've
got
answers
with
from
the
infra
team
that
will
place
it
in
Jenkins,
infra.
A
I've
started
the
retrospective
on
the
signing
certificate
renewal
process,
capturing
the
notes
in
that
Google
doc.
After
a
week
or
two
of
me,
Gathering
timelines
and
other
details
we'll
we'll
actually
host
a
formal
meeting
where
we,
where
the
players
in
the
session
talk
about
it
and
go
through
it
and
the
last
one.
The
reimbursement
process
for
the
code.
Signing
certificate
is
continuing
and
made
new
progress.
Today,
any
questions
on
any
of
the
action
items.
B
A
B
The
for
the
retrospective
are
you,
including
in
that
the
conversations
you
had
with
the
Linux
Foundation
folks
about
the
I.
Remember
the
last
meeting
you
you
had
mentioned
that
you
talked
to
them
and
they
had
given
you
some
ideas
about
different
ways
that
this
could
be
done.
For
example,
I
think
one
of
them
was
having
a
dedicated
package
that
simply
updates
certificates.
I,
remember
you
mentioning
that
they
had
seeded.
B
That
idea,
since
you
mentioned
that
I
I
noticed
that
some
of
the
software
that
I
use
on
my
own
desktop
is
using
the
same
techniques.
B
A
B
I
think
they
had
I,
don't
know
if
it
was
vs
code
or
some
other
program.
I
use,
but
but
I
saw
the
same
technique
being
applied
there
with
this
kind
of
dedicated
package
for
updating
certificates
or
keys
and
I
thought.
It
would
be
interesting
to
learn
more
about
that.
So,
if
is
that
being
included
in
the
retrospective
or
is
that
a
different
topic.
A
A
Okay,
next
topic,
then,
is
on
budget
and
expenses,
so
the
1500
U.S
that
I
spent
for
the
digital
code
signing
certificate
is
now
in
progress.
The
the
expense
report
has
been
submitted
to
the
Jenkins
projects
designated
single
Finance
person
and
that
I
think
right
now
is
Oleg,
so
I'll
ping
him
separately
after
this
meeting
to
let
him
know
that
he
should
have
seen
an
email
that
invites
him
to
approve
it.
Once
his
approval
is
generated,
then
it
goes
to
the
Linux
foundation
and
their
netsuite
system,
where
they
send
it
out
for
disbursement.
B
A
A
A
For
instance,
he's
been
working
on
the
change
from
java
11
to
Java
17
in
the
documentation
in
the
install
docs.
Let's
just
accept
that
will
be
delayed
and
others
are
welcome
to
help
documentation,
pull
requests.
We
invite
all
the
documentation
contributors
to
help
there
and
I'll
volunteer
to
take
on
the
change
logs
and
the
upgrade
guides
Alex.
Does
that
work?
Okay
for
you
from
the
perspective
of
the
2.401.1
release,
lead
absolutely
okay,
great
any
concerns
there
on
the
plan
for
what
to
do
during
Kevin's
absence.
A
Okay,
next
topic,
then,
was
I,
sent
a
request
to
the
board
about
three
or
four
weeks
ago,
suggesting
that
we'd
had
an
opportunity
presented
to
do
us
by
Ampere.
Ampere
is
a
a
hardware
vendor
they
s
they
created
and
sell
systems
based
on
arm
64-bit
server
class
processors
and
their
equipment,
they're
used
at
Oracle
for
their
Cloud,
hosting
and
I
believe
at
one
or
more
other
Cloud
vendors
and
they'd
offered
the
that
hey.
A
They
donate
to
open
source
projects
that
are
interested
in
using
their
Hardware
to
do
some
validation,
and
this
was
a
an
offer
of
physical
hardware,
and
it
happens
that
I
already
have
physical
Hardware
at
my
house,
so
I
prepared
an
application
and
sent
it
out
to
the
board
two
or
three
weeks
ago.
Two
weeks
ago,
it
got
approvals
in
various
places,
from
Alex
and
from
Uli,
so
I
went
ahead
and
forwarded
on
to
Ampere
any
concerns
that
want
to
be
expressed
about
that.
A
A
A
Okay.
Next
topics,
then
our
community
activity
topics,
and
here
I
think
it
might
be-
might
be
good
to
give
Basel
some
time
to
share.
If
you'd,
like
Basel
on
the
Prototype
JS
work
on
the
artifactory
work,
we're
making
progress
I
need
to
schedule
a
session
with
jfrog.
To
summarize,
our
latest
results
and
talk
in
more
detail
with
them
about
next
steps.
I'll
do
that
and
have
something
to
report
at
our
next
meeting.
Did
you
want
to
give
any
further
details
on
Prototype
puzzle.
B
I,
don't
have
too
much
to
add
to
the
blog
post,
there's
a
developer
mailing
list
thread
where
I
listed
a
number
of
plugins.
That
I've
identified
that,
in
my
in
my
quick
search
to
look
for
common
keywords
that
are
associated
with
prototype.
But
I
am
planning
to
do
a
more
thorough
search
in
the
next
couple
of
weeks.
B
There's
a
lot
of
low-hanging
fruit
that
I
wanted
to
get
out
of
the
way
first,
and
that
includes
the
dozen
or
so
pull
requests
that
I've
already
filed
against
some
of
the
most
popular
plugins
and
that
low-hanging
fruit
effectively
makes
it
more
difficult
to
find
the
higher
hanging
fruit
because
it
gets
in
your
way.
So
I
am
planning
on
doing
a
more
thorough
search
and
when
I,
when
I
do
get
to
that,
which
is
probably
going
to
be
the
next
couple
of
weeks.
B
I'll
create
a
some
kind
of
spreadsheet
or
tracking
system,
and
that
would
be.
That
would
be
a
good
way
to
coordinate,
to
coordinate
efforts
to
fix
plugins
I.
Think
the
I've
done
a
couple
of
these
types
of
spreadsheets,
where
I
have
the
plugins
sorted
by
popularity
and
use
different
colors
to
indicate
status
such
as
whether
a
release
has
been
done
or,
if
you're
still
waiting
on
the
Polar
quest
to
be
merged
Etc.
B
B
But
at
this
point
the
best
because
I
had
a
number
of
people
have
asked
me
like,
where
do
I
start
and
that
mailing
list
thread
the
list
of
plugins
there
is,
is
the
best
place
to
start
right
now,
like
I,
said
I'll
make
that
a
more
formal
in
a
spreadsheet
once
I
get
the
chance
to
do
a
more
thorough
search.
A
A
Okay,
then,
let's
go
ahead.
Next
topic,
then,
was
Google
summer
of
code.
Congratulations.
The
Jenkins
project
has
been
approved
for
four
Google
summer
of
code
projects.
Each
of
the
project
has
projects,
has
a
designated
lead
mentor
and
two
or
three
additional
mentors
to
help
help.
That
contributor
be
sure
that
they
are
successful
thanks
very
much
to
John
Mark,
to
Chris,
to
Alyssa
and
to
Bruno
for
their
work
as
organization
admins.
A
On
infrastructure,
we've
got
an
active
effort
going
on
to
reduce
infrastructure
costs.
Damian
de
Porto
De
le
mure
and
Stefan
Merrill
have
each
been
working
on
various
aspects
of
this,
including
things
like
looking
at
better
choices
of
machines
to
be
used
that
are
more
cost
effective
or
switching
some
tasks
from
AMD
64
to
arm
64
or
reducing
bandwidth
demands
when
bandwidth
is
a
high
cost
item
thanks
to
them.
For
for
that
ongoing
work,
it's
it's
very,
very
promising.
It's
looking
really
good.
A
Then
I've
got
an
ongoing
project
to
propose
an
early
end
of
life
for
Centos
7
in
the
Jenkins
project
and
there's
a
developer
mailing
list
thread
on
it.
It
will
be
continuing
it's
probably
several
months
before
it
will
get
to
the
point
of
being
ready
to
announce
with
blog
posts
Etc,
but
I'm
determined
we're
going
to
get
that
thing.
End
of
life
before
June
30th
well
before
June
30th
of
2024.
A
Hey
last
topic,
then,
was
launchable
experiments,
so
Basel
has
been
leading
an
effort
to
to
test
drive
ways
to
reduce
the
number
of
tests
that
we
use
and
still
get
high
quality
results
from
our
tests
using
launchable
a
product
or
a
company's
a
product
from
the
company
that
kosuke
kawaguchi
is
part
of
now
Basel.
Anything
that
you
want
to
talk
to
on
this
one
in
terms
of
ongoing
or
thoughts.
Yeah.
B
The
next
step
in
this
project
is
to
enable
it
for
Windows
tests
in
Jenkins
core
and
then,
after
that,
I
plan
on
adding
a
launchable
subset
of
ath
to
Jenkins
core
as
well.
B
B
You
know
I
know
that
the
infrastructure
team
has
been
trying
to
reduce
costs
in
ath
itself,
so
that's
also
an
option
if
they
wanted
to,
because
I
know
that
they
were
talking
about
you
know,
do
we
need
to
run
all
ath
tests
for
all
dependency
updates.
You
know,
similarly
to
bomb
and
launchable
could
be
used
to
implement
subsetting
there
in
much
the
same
way.
So
that's
another
option.
C
I
do
have
a
couple
of
items,
I
didn't
add
on
the
agenda
before
the
first
is:
maybe
you
already
noticed
it
I
enrolled
the
Jenkins,
CI
and
Jenkins
in
for
organization
into
the
private
GitHub
activity,
beta
thingy
I
posted
on
guitar
a
couple
of
hours
ago.
C
A
C
C
No
problem,
the
other
item
was
regarding
our
jira
instance,
I'm,
not
sure
how
much
you
tracked,
the
jira
support
and
end-of-life
cycle.
However,
we
are
currently
on
jira
8,
which
will
be
end
of
live
and
actually
end
of
support
within
the
next
five
months
and
I
was
wondering
if
the
Linux
Foundation
plans
an
upgrade
or
if
we
need
to
request
an
upgrade
from
the
Linux
Foundation
from
the
current
LTS
to
the
next
LTS.
A
C
The
end
of
live
between
Mid
of
October
this
year
and
09.4
or
9.2
would
be
end
of
life
in
late
2025,
and
that
is
the
current
LTS
version,
which
we
likely
would
go
to.