►
From YouTube: Jenkins Governance Meeting July 24, 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
Welcome
all
this
is
the
24th
of
July
2023.
This
is
the
Jenkins
governance
meeting
topics
I've
got
on.
The
list
include
news
report
on
action
items
then
Jenkins
board
and
officer
elections
in
2023
and
Community
activity,
including
several
items
there,
artifactory
bandwidth
reduction,
prototype.js
HTML
unit
3.,
any
other
topics
that
need
to
go
on
the
agenda
today.
A
Okay,
then,
let's
go
ahead
with
the
news
items:
thanks
we're
looking
forward
to
the
release
Wednesday
of
2.41.3,
it
will
be
a
security
release,
as
announced
in
the
advisory's
mailing
list.
So
that
means
the
weekly
will
also
be
a
security
release
and
to
make
that
job
easier
right
now,
MERS
or
merges
are
paused
to
the
master
branch
of
Jenkins.
Core
Alex
did
I.
A
A
A
A
B
Alex,
go
ahead,
Mark,
just
a
great
presentation
of
why
I'm
not
a
big
fan
of
the
Google
Doc,
if
it
loads
it
takes
years,
at
least
for
me
to
load
the
I
think
200
Pages
we
have
at
the
moment
and
the
idea
to
use
would
be
hack
MD.
That's
the
same.
The
infra
team
uses
allowing
features
like
pushing
directly
to
the
to
their
repository,
and
we
could
configure
it
to
push
with
the
governance
repository
and
retire,
the
Google
Doc
totally
to
simplify
the
workflow.
But
if,
given
it's
marked,
who
does
take
the
notes?
A
Yeah
I've
found
hack
MD
to
be
more
difficult
for
me,
at
least
during
note,
taking
but
I'm
I'm
open
to
it.
It's
it's
easy
enough
to
truncate
this
document
or
to
create
a
new
one
so
that
we
don't
have
a
a
very
long
document
like
we
do
right
now,
I'm
hesitant
to
go
to
hack
MD
unless
others
find
compelling
reasons
just
because
I
find
it
more
difficult
to
to
watch
and
view
the
note
taking
from
hackmd
than
from
then
from
a
Google
doc.
A
Comments
from
others
do
you
feel
feel
like
hey.
That
would
be
an
improvement.
C
We
could
gain
a
little
bit
on
the
speed,
of
course,
and
but
for
the
ease
of
use,
I'm,
not
so
sure,
also
use
icmd
and
frankly,
I'm
struggling
more
with
XMD
that
I'm
struggling
with
Google
Docs,
but
I'm
struggling
also
with
Google
Talks
Of
course.
You
know
as
long
as
soon
as
you
want
to
change.
You
know
the
zoom
ratio,
for
example,
you
lose
some
of
the
commands
and
so
on.
It's
not
that
good,
a
thing,
but
maybe
I'm
not
investing
enough
time
into
icmd
to
manage
to
do
it.
C
I
so,
Damien
week
after
week,
entering
text
into
the
fmd
document
without
suffering.
D
C
B
C
But
you
know
when
somebody
is
trying
to
modify
document
while
you're
taking
notes.
You
have
to
interrupt
your
flow
in
order
to
accept
if
the
people
are
not
yet
part
of
the
document
editing.
You
know
on
Google
Docs
right.
There
I
made
the
modification
earlier
in
the
meeting
and
you
would
have
to
click
OK.
C
If
you
know
earlier
up
or
apparent
document-
and
you
know
it
kind
of
breaks
the
flow
of
editing,
because
you
have
to
accept
modifications
supplied
by
the
other
users
in
icmd.
C
A
Yeah
we've
and
one
of
the
one
of
the
things
we
dreamed
of
years
ago
from
Google
Docs
was
non-non
editors
being
able
to
make
useful
contributions,
but
the
reality
has
been
just
doesn't
happen
and
therefore
there's
there's
no
no
value
to
to
something
that
never
happens.
Good.
Let's
try
hack
MD
next
in
two
weeks
and
we'll
see
how
it
goes.
A
Okay,
so
the
next
one
is
a
retrospective
on
the
signing
certificate
renewal
process,
I've
not
made
progress
in
the
last
two
weeks
on
this
one.
It's
I've
got
some
notes
in
the
in
the
retrospective,
but
it
needs
many
more
there's
a
detailed
list
of
timeline
for
MSI
and
timeline
for
Linux
and
already
in
the
timeline.
There
are
some
points
of
oh
wow.
That
was
a
mistake.
It
shouldn't
have
happened
so
late.
Just
the
start
of
this
timeline
is
dismayingly
late,
and
so
so
there
there
are
things
to
improve
there.
That
already
are
obvious.
A
A
A
Next
topic,
then,
was
Jenkins
Borden
officer
elections,
I'd
like
to
get
us
started
early
on
this
one.
Last
year
we
were
a
little
late,
getting
started
on
it.
So
it's
we're
now
in
July
about
to
enter
August
and
in
November
we
would
run
the
elections
so
that
their
results
can
be
announced
in
December
and
new
officers
and
new
board
members
can
take
take
up
those
possession
positions.
A
Last
year
we
had
Damian
deportal,
run
it
because
well,
because
the
infra
officer
had
typically
run
it
this
year.
I'd
propose,
since
neither
Alex
nor
I
are
up
for
election
this
year.
Let's
have
the
two
of
us
run
it
rather
than
Damien.
Who
is
up
for
election
Alex?
Would
you
be
willing
to
join
me
in
this.
A
A
A
Artifactory
bandwidth
reduction
project,
it
has
been
an
infra
project
for
many
months.
What
happened
was
we'd
we've
detected
that
some
abusers
had
been
misusing
Jenkins
repo
dot,
jenkinsci.org
bandwidth
to
the
point
where
we
were
able
to
block
one
IP
address
and
save
20
terabytes
a
month,
but
jfrog
has
asked
for
further
reductions,
and
their
next
recommendation
is
please
password
protect
the
mirrors
like
Maven,
Central
and
Jake
it
and
others
that
we
use
to
mirror
other
repositories.
A
There
is
now
a
proposal
out
for
a
limited
approach
to
that
to
password
protect
our
cache
of
Maven
Central
and
rely
on
the
defaults
that
Maven
provides
to
always
be
willing
to
pull
from
Maven
Central
without
having
to
list
it.
As
a
repository
I've
scheduled
a
session
to
talk
with
the
security
team
in
the
infra
team
on
Wednesday
about
the
topic
with
this
idea
to
see
if
we
can
get
agreement
that
it
makes
sense
to
to
immediately
stop
mirroring
Maven
Central
through
a
public
repository,
and
then
we
can
revisit
whether
we
should
marry
the
others.
A
The
data
results
show
that
Maven
Central
is
about
75
or
80
percent
of
the
volume
that
we
do
compared
to
what
Jenkins
releases
are
so
there's
a
chance
that
this
will
already
be
enough
for
jfrog
to
say:
hey
good
enough,
you
don't
have
to
password
protect
others.
If
we
have
to
password
protect
others,
then
Maven
Central
it's
more
complicated,
because
then
we
must
change,
pump
files,
questions
or
comments
on
the
bandwidth
reduction
project.
A
So
I'm
happy
to
to
give
my
description
of
it.
It
is
that
we're
we're
seeing
progress.
The
tracking
sheet
shows
that
progress,
the
credentials,
plugin
and
I
thought
I
had
seen
this
one
actually
now
released,
so
maybe
I'm
mistaken
there.
But
there
was
the
dictionary.
E
A
One
of
the
concerns
that
that,
for
me,
is
worth
worth
a
little
bit
of
worry
is
that
some
of
the
company
maintained
plug-ins
that
are
relatively
high
on
the
list
are
not
things
that
we
can
test
and
in
order
to
implement
these,
we
really
owe
it
to
ourselves
to
test
the
implementation
interactively
the
artifactory
plug-in
the
fortify
plug-in
coverity,
the
X-ray
plug-in
for
jira
and
q-test
are
all
examples
of
plugins
that
look
to
be
owned
by
companies
and
or
owned
by.
E
I
always
wanted
to
say
thank
you
to
Rahul
for
implementing
the
Prototype
fixes
for
get
parameter
and
active
choices,
because
both
of
those
were
difficult,
PRS
to
file
and
they've
both
been
released
now.
A
Next
topic,
then,
was
HTML
unit,
3
upgrades
and
there
it
it
looks
like
it's
continuing,
although
the
the
pace
is
not
as
as
rapid
as
with
prototype,
Js
I'm,
not
I'm,
not
overly
concerned
by
it.
In
that
it's
testing
upgrades
not
upgrades
in
core
function
or
in
functionality,
that's
visible
to
end
users.
A
Okay,
last
item
is
just
a
reminder
that
the
midterm
evaluations
are
complete
for
Google
summer
of
code
projects.
Continuing
we've
got
about
another
four
or
five
weeks
before
the
end
of
the
projects,
any
other
topics
we
need
to
bring
to
the
meeting
Uli.
You
had
a
comment
earlier,
possibly
on
the
elections.
Was
there
a
concern
there.
D
Yes,
it's
my
microphone
or
right
now,
working
great
so
from
the
bot
document.
It
looks
like
Alex
and
I
were
elected
last
year.
That
means
that
the
other
three
people
are
up
for.